BSoD, Friend or foe?

BSoD (Blue Screen of Death) Friend or foe? an interesting question that was raised by one of my colleagues around the proverbial water cooler this week and the inspiration I needed to dig through all my bookmarks and compile this post. Described on Wikipedia as the the Blue Screen of Death, known officially as a Stop Error or a bug check, is the error screen displayed by the Microsoft Windows family of operating systems upon encountering a critical error, of a non-recoverable nature, that causes the system to “crash”

Usually due to faulty hardware or a driver related issue, for the average Joe, when a BSoD is encountered the PC is taken in for repairs. The associated repair cost is almost always a grudge purchase and is never expected thus making the BSoD a foe for the average Joe.

For the overclocker the story changes and the BSoD should be considered your friend. Although a friend that is extremely frustrating to see, with the right knowledge the BSoD can be used as a tool to guiding you in the right direction highlighting why or where your hardware is failing. Hopefully once your finished reading this post you will have enough knowledge to turn that frown upside down the next time you see a BSoD during your OC sessions.

Above is an example of my OC Log where various BSoD’s were encountered
 The Base for this list was from a post started by /eVo/HaMMeR=GoM= over at XS and added to by various members in the thread. a lot of the suggestions are not my own and credit must be passed to those who have contributed. One last caution, BelowZer0 does not take any responsibility for any damage that might be caused while trying these suggestions. If you are unsure of the risks rather don’t try it.
 

0x101: Increase vCore
0x1E: Increase vCore
0x3B: Increase vCore
0x3D: Increase vCore

0x0A: Unstable RAM/IMC, increase QPI first, if that doesn’t work increase vCore

0x124: First increase/decrease QPI/VTT, if not increase/decrease vCore. you 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

0x1A: Memory management error. It usually means a bad stick of Ram. Test with Memtest and RMA your bad module. Try raising your Ram voltage.

0xD1: QPI/VTT, increase/decrease as necessary, can also be unstable Ram, raise Ram voltage

0x9C: on i7 45nm most likely QPI/VTT on i7 32nm (SB) most likely vCore.

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 OR SATA controller in incorrect mode for installed OS (IDE/AHCI/Raid)


If you have tried everything and nothing seems to resolve the BSoD then here is the bad news, you most likely just found the maximum potential of the hardware.

Now that you are empowered with some knowledge, what do you think, is the BSoD a Friend or Foe?

I plan to keep this post updated when new BSoD solutions are discovered so add it to your favorites and check back every now and again.

Thanks for reading and until next time Happy Benching.

Credits:

/eVo/HaMMeR=GoM= over at XS along with the various members at XS who contributed.
The Microsoft KB and various other sources found on Google

Leave a Reply

Your email address will not be published. Required fields are marked *