Anonymous edits have been disabled on the wiki. If you want to contribute please login or create an account.

Difference between revisions of "Blue Screen of Death (BSOD)"

From PCGamingWiki, the wiki about fixing PC games
(Added a link to my tech wiki at Lunarsoft for STOP errors/BSoDs. Link has error code documentation, generic solutions and more information.)
m (→‎Troubleshooting: updated microsoft docs link. I must say I'm really surprised by the amount of detail they have there.)
(22 intermediate revisions by 15 users not shown)
Line 1: Line 1:
[[File:Windows XP BSOD.png|200px|thumb|right|A Windows XP BSOD showing a Page Fault]]
+
[[Image:BSoD_in_Windows_8.png|300px|thumb|right|Blue Screen of Death in Windows 8, including a sad emoticon]]
A Blue Screen of Death (a.k.a BSOD or Bluescreen) is an error screen that [[Windows_(Operating_System)|Windows]] produces when it encounters an error that it cannot recover from. They can be caused by any number of problems, and can be problematic to troubleshoot. Thus, knowing the different parts of a BSOD can aid you in figuring out the cause.
 
  
==Enabling BSODs==
+
'''Key points'''
By default, most current versions of windows won't show a BSOD at all. They will simply reset upon experiencing a showstopping problem. This is fine if the PC is working great, but is annoying if a system is experiencing repeated problems. To prevent Windows from starting automatically and display the BSOD, follow these steps:
+
{{ii}} BSODs are usually caused by third-party drivers or hardware problems.
 +
{{ii}} Do a web search with the name of the file and the STOP error to find solutions.
  
'''Windows XP'''
+
'''General information'''
Navigate to the Start Menu, and open the Control Panel. Go to System, open the Advanced tab. Under Startup and Recovery, Click settings. On the window that comes up, make sure that the box next to Automatically Restart is unchecked, then click Ok. 
+
{{mm}} [[Wikipedia:Blue Screen of Death|BSOD article on Wikipedia]]
 +
{{mm}} [http://wiki.lunarsoft.net/wiki/STOP_errors STOP errors on the Lunarsoft Wiki]
  
'''Windows Vista/Windows 7'''
+
==Disable automatic restarts==
Navigate to the Start Menu, and open the Control Panel. Go to System, and choose Advanced system settings on the left side. Under Startup and Recovery, Click settings. On the window that comes up, make sure that the box next to Automatically Restart is unchecked, then click Ok.
+
{{ii}} [[Microsoft Windows|Windows]] often restarts instead of showing a BSOD. The steps below will override this, allowing you to see the BSOD when it happens.
  
==Parts of a BSOD==
+
{{Fixbox|description=Disable automatic restarts|fix=
'''Caused by'''
+
# Open System Properties:
In the picture above, the second section of text says "The problem seems to be caused by this file:". If windows is able to detect which file the problem occurred in, it may list that file here. This does not always show up in a BSOD, and doesn't appear to show up in BSOD's for Windows Vista or Windows 7 at all.
+
#* Open the Start screen/Start menu, type <code>SystemPropertiesAdvanced.exe</code> and press {{key|Enter}}.
 +
#* Windows XP: press {{key|Win|R}}, type <code>sysdm.cpl</code> and press {{key|Enter}}, click the Advanced tab.
 +
# Under Startup and Recovery, click the Settings button.
 +
# Under system failure, uncheck automatically restart.
 +
# Press OK to save the change then close the remaining windows.
 +
}}
  
'''Error Name'''
+
==Troubleshooting==
In the picture above, the third section of text says "PAGE_FAULT_IN_NON_PAGED_AREA". This section is the error name, and can help give you a better example of what caused the BSOD. This part of a BSOD shows up in every BSOD from Windows XP and on.  
+
Download and run [http://www.nirsoft.net/utils/blue_screen_view.html BlueScreenView] to examine the BSOD minidump. The highlighted files (if any) give an indication of which drivers contributed to the crash. Doing a web search for the Bug Check Code will often lead to someone with the same problem and hopefully a solution. Searching for the STOP values is also helpful.
  
==Troubleshooting Suggestions==
+
If the file that caused the crash is part of a third-party driver or program, consider reverting it to a version that was working in the past or updating to a newer version if one exists. If that doesn't resolve the problem you could also try uninstalling it altogether.
What can be maddening about BSODs is the fact that even if you are given both a 'caused by' and 'error name' on the BSOD, it can prove to be annoying to research.  
 
  
Your first step is to google the 'error name' and the 'caused by'. There is a good chance that someone on the internet has encountered at least a BSOD with the same error name. This will lead you to a bunch of websites. Attempt to find one that describes both the type of BSOD you experienced, as well as a similar build. You may luck out and find out the exact solution to your problem.
+
If the different Microsoft websites don't show up in your search, it might help to search [https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/blue-screen-data Microsoft Docs] for your error name.  
 
 
If the different Microsoft websites don't show up in your search, it might behoove you to search [http://technet.microsoft.com/en-us/ Technet] for your error name, and the [http://msdn.microsoft.com/en-us/windows/hardware MSDN] might have info on your problem as well.
 
  
 
Finally, if you are unable to find any info on your specific situation, your next best bet is to find a reputable and thriving tech website with a forums, or a website focused on troubleshooting computers. Start a thread, outline your specific BSOD, current rig, and hope that somebody will help you.
 
Finally, if you are unable to find any info on your specific situation, your next best bet is to find a reputable and thriving tech website with a forums, or a website focused on troubleshooting computers. Start a thread, outline your specific BSOD, current rig, and hope that somebody will help you.
  
 +
===RAM automatic clock incorrectly set===
 +
{{ii}} Manually setting the [[Glossary:RAM|RAM]]'s clock value in the BIOS might stop any BSODs from happening.
  
==Viewing BSOD Dump Files==
+
[[Category:Troubleshooting]]
When a BSOD occurs, Windows will dump the contents of memory to a file on disk called a dump file. These are the files that are often requested if you post about a BSOD problem on forums online. There exist utilities, like [http://www.nirsoft.net/utils/blue_screen_view.html this one,] that allow you to grab some of the information about your specific BSOD from the dump file, which may aid in researching the problem.
 
 
 
Some forums also have technicians who analyze dump files to help pinpoint the root of the STOP errors or BSoDs. A technician favorite is WinDbg, a popular utility to use as well though it is not as user friendly as some third party memory dump viewers.
 
 
 
==BCCodes and possible solutions==
 
BSOD Codes for i7 x58 chipset
 
 
 
0x101 = increase vcore
 
 
 
0x124 = increase/decrease QPI/VTT first, if not increase/decrease vcore...have to test to see which one it is
 
 
 
on i7 45nm, usually means too little VVT/QPI for the speed of Uncore
 
 
 
on i7 32nm SB, usually means too little vCore
 
 
 
0x0A = unstable RAM/IMC, increase QPI first, if that doesn't work increase vcore
 
 
 
0x1E = increase vcore
 
 
 
0x3B = increase vcore
 
 
 
0x3D = increase vcore
 
 
 
0xD1 = QPI/VTT, increase/decrease as necessary, can also be unstable Ram, raise Ram voltage
 
 
 
0x9C = QPI/VTT most likely, but increasing vcore has helped in some instances
 
 
 
0x50 = RAM timings/Frequency or uncore multi unstable, increase RAM voltage or adjust QPI/VTT, or lower uncore if you're higher than 2x
 
 
 
0x109 = Not enough or too Much memory voltage
 
 
 
0x116 = Low IOH (NB) voltage, GPU issue (most common when running multi-GPU/overclocking GPU)
 
 
 
0x7E = Corrupted OS file, possibly from overclocking. Run sfc /scannow and chkdsk /r
 
 
 
BSOD Codes for SandyBridge
 
 
 
0x124 = add/remove vcore or QPI/VTT voltage (usually Vcore, once it was QPI/VTT)
 
 
 
0x101 = add more vcore
 
 
 
0x50 = RAM timings/Frequency add DDR3 voltage or add QPI/VTT
 
 
 
0x1E = add more vcore
 
 
 
0x3B = add more vcore
 
 
 
0xD1 = add QPI/VTT voltage
 
:0x9C = QPI/VTT most likely, but increasing vcore has helped in some instances
 
 
 
0X109 = add DDR3 voltage
 
 
 
0x0A = add QPI/VTT voltage
 
 
 
==External links==
 
[http://en.wikipedia.org/wiki/Blue_Screen_of_Death BSOD article on Wikipedia]
 
[http://wiki.lunarsoft.net/wiki/STOP_errors STOP errors on the Lunarsoft Wiki]
 
 
 
[[Category:Guide]]
 

Revision as of 22:06, 20 February 2019

Blue Screen of Death in Windows 8, including a sad emoticon

Key points

BSODs are usually caused by third-party drivers or hardware problems.
Do a web search with the name of the file and the STOP error to find solutions.

General information

BSOD article on Wikipedia
STOP errors on the Lunarsoft Wiki

Disable automatic restarts

Windows often restarts instead of showing a BSOD. The steps below will override this, allowing you to see the BSOD when it happens.
Disable automatic restarts
  1. Open System Properties:
    • Open the Start screen/Start menu, type SystemPropertiesAdvanced.exe and press Enter.
    • Windows XP: press Win+R, type sysdm.cpl and press Enter, click the Advanced tab.
  2. Under Startup and Recovery, click the Settings button.
  3. Under system failure, uncheck automatically restart.
  4. Press OK to save the change then close the remaining windows.

Troubleshooting

Download and run BlueScreenView to examine the BSOD minidump. The highlighted files (if any) give an indication of which drivers contributed to the crash. Doing a web search for the Bug Check Code will often lead to someone with the same problem and hopefully a solution. Searching for the STOP values is also helpful.

If the file that caused the crash is part of a third-party driver or program, consider reverting it to a version that was working in the past or updating to a newer version if one exists. If that doesn't resolve the problem you could also try uninstalling it altogether.

If the different Microsoft websites don't show up in your search, it might help to search Microsoft Docs for your error name.

Finally, if you are unable to find any info on your specific situation, your next best bet is to find a reputable and thriving tech website with a forums, or a website focused on troubleshooting computers. Start a thread, outline your specific BSOD, current rig, and hope that somebody will help you.

RAM automatic clock incorrectly set

Manually setting the RAM's clock value in the BIOS might stop any BSODs from happening.