Diagnosiing Windows BSOD Stop code (possibly bad CPU)
Posted on 2006-06-01
I posted a question last week regarding a hardware disaster with my PC (the title of the thread was "Narrowing down the bad component in a system that won't power on." Per the responses I received, I ordered a new motherboad and new RAM. I also bought a new power supply.
This evening, I reassembled the PC with a new mobo, new RAM, new power supply, and was pleased that it posted the way it ought to, detected the CPU correctly, detected the RAM correctly, detected all my drives correctly. However, it would not start Windows: instead, just as it finished the posting process and was about to load Windows, it would reboot itself. (NB: I have Recovery Console installed on the hard drive, so I do get to the screen that gives me the choice between starting Windows and starting Recovery Console. Then, when I choose Windows, it goes into the reboot.)
After a cycle of that, I tried to get it to start in Safe mode, but that didn't make a difference. Then I tried to get it to start in Last Known Good Configuration. That didn't help either. Finally, I tried booting from a Bart PE CD, and that's when i got far enough to get a BSOD (after Bart PE gave me the message about checking system configuration):
A problem has been detected and windows has been shut down to prevent damage to your computer.
If this is the first time you've seen this Stop error screen, restart your computer. If this screen appears again, follow these steps:
Check for viruses on your computer. Remove any newly installed hard drives or hard drive controllers. Check your hard drive to make sure it is properly configured and terminated. Run CHKDSK /F to check for hard drive corruption, and then restart your coomputer
STOP: 0x0000007B (0xF8984528, 0xC0000034, 0X00000000, 0X00000000)
I doubted that there was a virus involved, but I did restart the PC, and the same thing happened -- I got the same BSOD with exactly the same Stop code.
Finally, i disconnected my hard drive and tried booting again off the Bart PE CD. Got the same BSOD and the same Stop code. That indicates to me that the problem is not the hard drive at all.
Since everything else is new, and since I get the stop code even without a hard drive as part of the system, my conclusion is that the CPU got fried, along with everything else in my computer. Is there some other explanation I am missing? I searched this site and I found that this kind of Stop code can occur when a hard drive is inaccessible, or the mobo is swapped out, but if that were the cause in this case, then the PC would be able to run Bart PE without problem. Moreover, the solution recommnded when swapping the mobo is to do a repair install of Windows -- which I don't think I'll be able to do given the inability to even get Bart PE running. However, I will try that and report back here.