Comments on: How to Fix Blue Screen Errors

By: Paul

Paul — Fri, 12 Mar 2010 15:23:51 +0000

I just got a SOD on my xp pro and I didn’t write down the error. I turned off the computer and turned it back on and the monitor won’t display anything, it is completely black. Now what???

By: Anthony

Anthony — Fri, 12 Mar 2010 00:37:37 +0000

@kayla – If the recovery option does not work, I am afraid the only thing left is a reinstall.

@shady336 – Can you provide any more details? Does the Safe Mode still work?

@Almin – Stop error 0×0000007E in most cases is a driver error. Check the Device Manager for any problematic devices, or use the system restore option to revert back to a previous configuration. This is of course assuming you can still boot into Safe Mode.
If not, you need to boot from a Windows setup or recovery CD and try the Repair option.

By: Almin

Almin — Thu, 11 Mar 2010 10:41:22 +0000

Hi I have Windows 7 Ultimate, my STOP ERROR is: Stop 0 × 0000007E SYSTEM_THREAD_EXCEPTION_NOT_HANDLED. How Dow I fix it. Help please!!! Thnx…

By: shady336

shady336 — Tue, 09 Mar 2010 03:58:15 +0000

I have Windows XP on my laptop and its been 2 days been trying to fix that bludy blue screen of death.

By: kayla

kayla — Thu, 04 Mar 2010 01:44:17 +0000

I have Windows vista and I’m trying to do system restore using f8.

I’m fairly certain my computer has a virus and I’ve tried everything! My problem now is that when I select “repair your computer” after hitting f8, I get a blue screen and have to start over. At this point I want to restore to factory settings and erase everything… I have everything important on an external hard drive. Is there any other way to get past the blue screen?

By: Anthony

Anthony — Wed, 03 Mar 2010 22:44:24 +0000

@yourstruli – If you get so many, seemingly random, blue screen errors, it generally has to do with the memeory (RAM) or the motherboard. You can try running a memory test with memtest86 (see instructions in earlier comments), or you can try switching the memory modules on the motherboard. Be careful with that though.

By: yourstruli

yourstruli — Wed, 03 Mar 2010 03:56:18 +0000

Hi Anthony,

I performed a clean install of Windows XP SP3, but during the installation I received these stop errors:

STOP: 0X000000D1 (0XF77A1E0E, 0X00000007, 0X00000001, 0XF72EAE0)

nvatabus.sys address F72EAEAO, base F72E9000, 444d72c9

STOP: 0X0000000A (0X0302806E, 0X00000007, 0X00000000, 0X806E78FE)

STOP: 0X0000008E (0X80000004, 0X806E6526, 0XF78B2BE0, 0X00000000)

Any suggestions on how to fix these?

Thanks! I really appreciate all your help. =)

By: Anthony

Anthony — Tue, 02 Mar 2010 03:18:33 +0000

@yourstruli - Microsoft has a knowledge base article about that stop error. Even from that it seems clear the error is rather serious. A disk problem might even cause it. See if you can run a "chkdsk /f" at the command prompt.

By: yourstruli

yourstruli — Mon, 01 Mar 2010 19:35:35 +0000

I can’t run “scf /scannow” on cmd.exe

It said something like this:

Windows File Protection could not initiate a scan..

The specific error code is 0×000006ba [The RPC server is unavailable']

Also whenever I shut down my computer from safe mode (since this is the only way I can use my computer without all the BSODs) this message will appear:

STOP: c000021a {Fatal System Error} The Windows Logon Process system process terminated unexpectedly with a status of 0xc00000000 (0×00000000 0×0000000)

The system has been shut down.

What do you best possible solution for all of this? Do you think that having a clean install of Windows could fix all of my blue screens? If you have other solutions in mind please let me know… Clean Installation is my VERY LAST option.

By: Anthony

Anthony — Sun, 28 Feb 2010 14:11:41 +0000

@dallas – You should format the disk before you reinstall Windows. In the setup program you have to select where to install Windows. There you can also select to do a full format. If that does not fix it, you are better off with a new hard disk indeed.
With the new disk, there is nothing to do to prevent this, other than be careful when handling the disk. Bouncing can cause damage of course.

@terry houston – First try pressing F8 during the boot to see if the startup menu still comes up. If it does, you can try the “Last known good configuration” option or the “Safe Mode” option.
If the startup menu does not come up, try inserting a Windows setup CD/DVD and see if it boots from that. If it does, you can try the Repair option in the setup menu.

@ron c – If you have access to another system, you can download memtest86, create a bootable CD from it and then boot your problematic system with that to do a memory test. If not, you can try switching around the memory modules if there are multiple, but be very careful with that as static electricity can actually destroy them.

@yourstruli – Try a system file scan and see if that corrects the errors. Type “sfc /scannow” at a command prompt (with admin level access).
You might be asked for the original Windows files during that process.