How to Fix Blue Screen Errors
Blue screen errors, or blue screen of death (BSOD) errors, are the most severe errors Windows can encounter. Since Windows can not recover from this kernel level error, a blue screen is displayed with the error details. The error details contain a STOP error code, which indicates the type of error.
There are a lot of possible causes for blue screen errors, but most of them relate to the computer hardware. The cause of a BSOD error can be a temperature problem, a timing error, a resource conflict, hardware failure, a corrupt registry, a virus or simply a device incompatibility or driver error.
How to analyze blue screen errors
The first thing to do to analyze a blue screen error is to check the meaning of the STOP error code. You need to stop Windows from rebooting when a STOP error is encountered. Once the blue screen of death is shown, you can check the meaning of the STOP error code. Together with the filename of the driver or module, this will give an indication of the error cause.
Another option to analyze the cause of the blue screen error is to look at the Windows system event log or to debug the memory dump (minidump) that Windows created when the error occurred. The event log can be viewed using the event viewer. Right-click Computer in the Start menu, and then select Manage. In the Computer Management window select Event Viewer. The information in the event log can be of great help to isolate the cause of the blue screen error.
Within the Event Viewer, use the right-hand pane to create a custom view and select a date range or specific event category to nowwor down the events relating to the blue screen error.
Windows can also be configured to create a minidump of the current state when a critical error happens. Reading the minidump requires a bit more technical knowledge, but Microsoft has tools to read the minidump. Read more about how to analyze Windows minidump files if you want to use the crash dump file to find the cause of a Windows stop error.
The most common cause of blue screen errors
In reality, the most common cause of blue screen errors is a device driver problem. Outdated, incorrect or corrupt drivers can cause the system to encounter a STOP error, resulting in the BSOD.
So the easiest way to try and fix a blue screen error is to reinstall and update your system’s device drivers. This will ensure that all driver bugs are fixed and that all hardware has the correct driver.
If you know which device caused the error, you can update or reinstall that driver first. The file name in the blue screen of death can help identify the driver. Look for a file with the .SYS extension and search for that file name.
If you do not have the drivers for all devices, or are not comfortable updating your PC’s drivers manually, you can use a driver update tool to find, download and update all device drivers for you. Such tools will accurately identify your computer hardware, including any device causing an error, and automatically install the latest drivers for it.
In most cases updating or reinstalling drivers will solve your blue screen errors.
Other causes of blue screen errors
However, if updating device drivers does not fix the blue screen error, there are a number of additional things to try:
- Load the default BIOS values – resource conflicts and timing issues can be caused by incorrect BIOS settings.
- Update the BIOS – especially after adding new hardware or installing a Windows service pack this can help fix issues.
- Update Windows – missing updates, including service packs can be a source of stop errors.
- Check your system – run a virus scan after updating your definition files.
- Run a memory test to check your computer’s RAM. Memory faults can easily cause blue screen errors, so see if your RAM is error free. Vista and later Windows versions have a built-in option to test the memory, for XP you can use a program called memtest86.
- Driver rollback – if you have recently updated a driver, you can use the driver rollback to revert back to the previous driver version.
List of STOP Errors Causing BSOD:
- Stop 0x00000003 UNSYNCHRONIZED_ACCESS
- Stop 0x0000000A IRQL_NOT_LESS_OR_EQUAL
- Stop 0x0000001E KMODE_EXCEPTION_NOT_HANDLED
- Stop 0x00000023 FAT_FILE_SYSTEM
- Stop 0x00000024 NTFS_FILE_SYSTEM
- Stop 0x0000002E DATA_BUS_ERROR
- Stop 0x0000003F NO_MORE_SYSTEM_PTES
- Stop 0x00000044 MULTIPLE_IRP_COMPLETE_REQUESTS
- Stop 0x00000050 PAGE_FAULT_IN_NONPAGED_AREA
- Stop 0x0000006B PROCESS1_INITIALIZATION_FAILED
- Stop 0x00000073 CONFIG_LIST_FAILED
- Stop 0x00000074 BAD_SYSTEM_CONFIG_INFO
- Stop 0x00000076 PROCESS_HAS_LOCKED_PAGES
- Stop 0x00000077 KERNEL_STACK_INPAGE_ERROR
- Stop 0x00000079 MISMATCHED_HAL
- Stop 0x0000007A KERNEL_DATA_INPAGE_ERROR
- Stop 0x0000007B INACCESSIBLE_BOOT_DEVICE
- Stop 0x0000007E SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
- Stop 0x0000007F UNEXPECTED_KERNEL_MODE_TRAP
- Stop 0x0000008E KERNEL_MODE_EXCEPTION_NOT_HANDLED
- Stop 0x0000009C MACHINE_CHECK_EXCEPTION
- Stop 0x0000009F DRIVER_POWER_STATE_FAILURE
- Stop 0x000000BE ATTEMPTED_WRITE_TO_READONLY_MEMORY
- Stop 0x000000C2 BAD_POOL_CALLER
- Stop 0x000000C4 DRIVER_VERIFIER_DETECTED_VIOLATION
- Stop 0x000000CA PNP_DETECTED_FATAL_ERROR
- Stop 0x000000CB DRIVER_LEFT_LOCKED_PAGES_IN_PROCESS
- Stop 0x000000CE DRIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS
- Stop 0x000000D1 DRIVER_IRQL_NOT_LESS_OR_EQUAL
- Stop 0x000000D5 DRIVER_PAGE_FAULT_IN_FREED_SPECIAL_POOL
- Stop 0x000000D8 DRIVER_USED_EXCESSIVE_PTES
- Stop 0x000000DA SYSTEM_PTE_MISUSE
- Stop 0x000000EA THREAD_STUCK_IN_DEVICE_DRIVER
- Stop 0x000000ED UNMOUNTABLE_BOOT_VOLUME
- Stop 0x000000F2 HARDWARE_INTERRUPT_STORM
- Stop 0x000000F4 CRITICAL_OBJECT_TERMINATION
- Stop 0x000000FC ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
- Stop 0x000000FE BUGCODE_USB_DRIVER
- Stop 0xC0000218 UNKNOWN_HARD_ERROR
- Stop 0xC000021A STATUS_SYSTEM_PROCESS_TERMINATED
- Stop 0xC0000221 STATUS_IMAGE_CHECKSUM_MISMATCH
- Stop 0xC0000244 STATUS_AUDIT_FAILED
A complete list of error codes can be found on the Microsoft MSDN website.
Please share your own experiences with blue screen of death errors, including possible solutions. New insights can help others, or maybe we can help you with specific STOP errors.
@Rene Celibataire of course they exist. Im with XP , blue screens appear often.
Ive heard that you can see blue screens on Vista too , is it true ?
Yes it seems that Anthony have missed some errors , but anyway really useful post.
it`s SATA
actually it started getting error after 2-3 months
and thanks for help
@kunal – From the fact that you only started having problems with the new disk, it is more likely that this new disk is causing some kind of problem. Is it a IDE or SATA disk?
One possible solution for stop error 0x00000003 is a Microsoft hotfix: http://support.microsoft.com/kb/841005
This is assuming you are running XP of course.
And also make sure you Windows updates are all installed, so all possible patches applicable to the system are present.
Regarding the disk, a disk check should tell you if it is still okay. To make sure, do a full format (not quick), so all bad areas are marked and excluded for data storage.
Anthony
hi anthony
i recently added a new hdd to my pc , it worked well for months then the pc started getting hanged every now and then , then it would ask for : to repair windows , it worked for days then again it woud`nt even repair i reinstalled windows several times but same problem , so thinking that the old hdd might be the problem (since during chkdsk errors wer found) i reinstalled th windo in the nu hdd (making it master) just after i reinstalled all my softwares it showed BSOD giving
0*00000003 , 89c62150 ,0*89c622c4 ,0*805d1142 error
plzz help!! also is the old hdd realy useless(any way 2 know that)
thanks
Do Blue Screen errors still exist? i haven’s seen one since Windows ’98!!!
The vetefile.sys file is part of Antivirus software by Computer Associates, so maybe that is causing your problems. You can try uninstalling and then reinstalling that, or maybe try switching to AVG ( http://free.avg.com/ ) to see if that help.
Stop error 0x07E really indicates a driver problem, so this is related to the VETEFILE.SYS you indicate. This driver file is part of the Vet File Scan Engine, which listed in the Device Manager under Non-Plug and Play Drivers (make sure to select the ‘View hidden devices’ option in the View menu).
Anthony
Anthony,
I successfully ran the disk check a few days ago, but today when I booted up my computer, I received a STOP 0x07E blue screen error. It also read:
VETEFILE.SYS Address AA2DB30E base at AA2D8000 DateStamp 482a3efc.
I reloaded optimal BIOS settings, but what else can I do to to try to fix this? Please help!
Thanks so much!
@Nicki – the stop error you list is actually a disk or file system error. Quite often you can fix that by running a “chkdsk /f” at the command prompt (with admin rights). This will check the disk and file system and correct any error found.
Some more on this: http://support.microsoft.com/kb/228888
So I do not think the .NET framework nor the AV software has to be the cause, it could be that .NET update is using a part of the disk that has errors.
Anthony
Anthony,
I recently booted my computer with normal startup (I had it on selective with the anti-virus turned off). I received a new BSOD moments after an update was successfully installed: Update to.NET Framewok 3.5 Service Pack 1 for the .NET Framework Assistant 1.0×86(KB963707).
I received the blue screen error:
STOP 0x00000024
Ntfs.sys address F84DE886 base at F84B9000, DateStamp 4800be5
Is the cause the anti-virus software or could it be the update? If it’s the update, how can I re-install it?
Any help would be appreciated.
@Rose – You can configure Windows not to automatically reboot on a BSOD error.
In the Control Panel go to System. Select the Advanced tab, and under Startup and Recovery select the Settings button. Now you see a checkbox called Automatic restart under System failure. Make sure that is cleared and click OK (this is Windows XP, Vista has the same option).
Next time a blue screen error occurs, the screen will stay and Windows will not automatically reboot.
Anthony
What do you do if the BSOD flashes too fast for you to see and then automatically reboots again and again and again (does the same for safe mode)
@Janice – I’d recommend you run a memory test, because that could explain the erratic symptoms. Another option is a temperature problem. Try cleaning the system inside and make sure there is sufficient airflow around it.
Hope it helps!
Anthony
I have had so much trouble with BSOD, tried several diff things, reinst WIN XP SP 3, remove SP 3, change antiV software, each time comp – Media Centre AMD Emachine would run fine then months later would BSOD with diff codes reappears. Last code was 0*000000C5, before that just shutdowns, before that o…8E, before that – 0…7F. Any ideas before I start buying new mem, MoBd, & HD? Thanx, Jan
Anthony,
Thanks SOOO much for your help! So far the BIOS settings worked! The memory test came up negative, but I plan on running the extended one soon.
Thank you! Thank you! Thank you!
@Nicki – The SFC command will automatically replace corrupted system files with the original ones, so there should not be any follow up report.
The Bios default selection is indeed correct.
The best is really to use memtest86, but you can also try the Windows Memory Diagnostic from http://oca.microsoft.com/en/windiag.asp
Anthony
Anthony,
I ran “sfc/scannow” in the command prompt, and after the protected files were scanned, the window closed. Should I have received a positive or negative follow-up report? I also pressed F2 during boot and selected “Load Optimal Default” in the BIOS. Is that correct? The BIOS boot version is EV91510A.15A.0123.
Lastly, is there another memory test available? I appreciate all your help.
@Nicki – Your system seems unstable overall. The common causes for this type of BSOD errors is memory and a corrupt Windows installation.
I suggest you check your memory with something like memtest86. Also try loading the default bios settings (in most cases F2 during boot will bring you in the bios). This will reset all memory timing to default.
Another thing I’d suggest is to run “sfc /scannow” in the command prompt. This will verify and correct your Windows system files.
I do not expect it is the antivirus software.
Anthony
I forgot to mention that the first is the most common, and the only applicable file/program mentioned is win32k.sys. I’ve scanned for viruses several times and they’re all negative, and I’m wondering if it’s the anti-virus software. I really need some help before I decide to just get a new computer.
By the way, I have a 4 year-old Gateway with Windows XP.
Hey there! Major problem: I receive an array of stop errors, varying from starting IE or MS Word to browsing the internet to turning on my computer. Some include:
IRQL_NOT_LESS_OR_EQUAL
PAGE_FAULT_IN_NONPAGED_AREA
BAD_POOL_CALLER
BAD_POOL_HEADER
@Tim – The nv4_disp is related to the n4v_disp.dll file which is part of the Nvidia device drivers for your video card. The most common solution to that problem is to get the latest drivers from the Nvidia support site ( http://www.nvidia.com/Download/index.aspx?lang=en-us ) and download your video card drivers.
In the Control Panel, select System, select the Hardware tab and click the Device Manager button. Then open up Display Adapters, right click your video card and select Update Driver in the popup menu. Make sure to select the location for the drivers manually (not let Windows search), and pick the downloaded Nvidia drivers.
Hope it helps.
Anthony
Morgan,
My BSOD says that there is a problem with file: nv4_disp
It states that the device driver got stuck in an infinite loop. What do I do next?
Thanks for your help!
Tim
@Morgan – The BSOD error you are describing is caused by a corrupt registry. Microsoft has a knowledge base article on recovering from a corrupt registry that pertains to the c0000218 error.
http://support.microsoft.com/kb/307545/en-us
Did you try those steps?
Anthony
My blue screen of death isnt any of the ones you listed. It is a blue screen that says: STOP: c0000218 {Registry File Failure} The registry cannot load the hive (file): \SystemRoot\System32\Config\SOFTWARE or its log or its alternate. It is corrupt, absent, or not writeable. Please someone help me!