Recently, when i switched on computer in the morning, i have BSOD when loading system. However, the computer was reset, and the second time turn on normally. That was for about 2 weeks.
I thought it was a breeze. And finally (yesterday) BSOD performed at every turn on your computer (http://ifotos.pl/zobacz/Beztytuuj_rrwxnhq.jpg/). After a few restart, computer was turn on. To correct the problem i had reinstall the network adapter drivers TP-Link WN 722N.
My computer was overcloacking - from 2.2ghz to 2.6ghz. But, was stable. Temperature was around from 38 to 40 degrees Celsius. However the northbridge is very warm. I checked by hand. And motherboard with cpu, have already been over 4 years.
BSOD is very random situation...try to bump your processor voltage more.
but if it cannot solve your problem..
according to your explanation, maybe you have problem with your powersupply,
Check your cable from psu to mobo, reseat it well, and try to assemble your computer outside casing.
and dont forget try to swap your psu with other psu.
I have all settings in default values. I reset the BIOS.
I forgot to write. Two times i have this message from BIOS: Warning! The previous performance of overclocking is failed, and the system is restored to the defaults setting.
But the settings were default.
Yeah, i still have 7B bsod. I also try to increase only voltage of cpu.
Oh, capacitor / condenser are not swollen / ventricose. I dont know how to write this
I have all settings in default values. I reset the BIOS.
I forgot to write. Two times i have this message from BIOS: Warning! The previous performance of overclocking is failed, and the system is restored to the defaults setting.
But the settings were default.
Yeah, i still have 7B bsod.
Since your BIOS has reset to default BIOS settings, see if your SATA ports are now using AHCI instead of IDE. 0x07B is usually an inaccessible boot device error in most of my personal experiences it results from the BIOS being set to use AHCI while Windows hasn't had the AHCI drivers installed.
Without knowing the error code that caused this exception, not much more I can do. The fact a system thread crashed is an indication of a possible HDD/RAM problem though.
Bug Check 0x7B: INACCESSIBLE_BOOT_DEVICE
Quote :
This bug check indicates that the Microsoft Windows operating system has lost access to the system partition during startup.
Points to the HDD.
I'd look at the picture of the SMART warning you got, but access to the site is blocked at work. But I'm guessing HDD at this point.
Also, you can't just swap HDD's and expect windows to boot without a problem (due to dirvers and the like). At the very least, you need to make sure the BIOS is pointing to the correct HDD...
Message edited by gamerk316 on 02-03-2012 at 02:23:22 PM
Im think, thats HDD is ok, but i could be wrong. I dont know about smart values, but mhdd scan not detect any problems. Maybe smart showed problem with HDD...
And, this is important: i can read data from hdd, when i connect it to another computer.
I've installed windows 7 on other disk, and it looks like it works. I dont know, where problem is: software or hardware. But, if its hardware new disk should dont work. Maybe it breaks down soon...
Message edited by obelix94 on 02-03-2012 at 11:37:35 PM
Like you said though, it does seem like a hardware failure somewhere because it gets worse overtime. As the faulty hardware keeps corrupting data that it writes back to your hard drive, like bad RAM would do, it will eventually corrupt your installation of Windows to the point where it can't boot or run properly.
However, it would take replacement parts for several components and probably a reinstall of Windows, or using an image of a fresh install, for every component you wanted to test to figure out which one is the problem.
------------------------------AIM: arson94
WOW/BFBC2/SWTOR: Weinerchili
Steam: Raider Von Poon
Xbox Live: Raider Von Pewn Reply to arson94
Well, 0x7B errors indicate the OS can't see the HDD for whatever reason; shoddy SATA cable prehaps? Might also be a BIOS problem though; this might be one of those rare situations where a BIOS update might fix the issue.