Wraith
Bettyswollocks
Blue screens of death, otherwise known as BSOD or Windows stop errors, these appear as result of hardware or driver failure.
I'm not about to fix every BSOD that crosses my path but I can point you in the right direction and help you work out the root cause, and hopefully set your system back on the straight and narrow.
A BSOD followed by a instant reboot, this usually does not give you enough time to see the actual stopcode and generally leaves you wondering what the hell just happened, well windows is automatically configured to reboot immediately after a serious issue has occured this can be rectified by disablling the automatic "restart on system failure" Follow the path below also pictured.
Control Panel\System\Advanced system setting\Advanced\Startup and Recovery and uncheck the "Automatically restart" check box.
Now when your system crashes it will remain on the blue screen indefinitely until you reboot giving you plenty of time to take some notes.
Once you have your stop code which should look something like this 0x00000051 (Registry_error), you can then begin your journey narrowing down what went wrong.
To figure out what each code means, you can do this by visiting Microsofts "Bug Check Code Reference page"
Alternatively you can download BlueScreenView and view the minidump file created by the BSOD, this actually yields more information than simply searching Microsofts code list as it will show you the drivers and their addresses located in the crash stack pin pointing the issues at hand. Click the image for a link to BlueScreenView download.
I could go through every code and eventuality that arises from a bluescreen crash but I'm not going to as this thread would be enormous and TTL doesn't pay me enough :lol: what I will do though is run through the most common causes of Bluescreen which should help point you in the right direction and hopefully save us some time on the forums when helping people with future issues.
STOP 0x0000000A: IRQL_NOT_LESS_EQUAL
Stop code 0xA is the most common BSOD error code, it is also the most annoying error. It occurs when one of the device drivers on the computer attempts to interrupt the CPU with a priority that is too high. To fix it, you are generally advised to reinstall or disable device drivers until you find the offending component. Some virus scanning software can also cause the issue.
STOP 0x00000024: NTFS_FILE_SYSTEM
STOP code 0x24 is quite self-descriptive, but may still plague you; an issue in the NTFS file system causes it. This usually means that the file system on one of the hard drives attached to your computer is corrupt or damaged. Running chkdsk and using a SMART utility to check for faulty hard disks like HDTune should help you fix the issue.
STOP 0x0000007B: INACCESSIBLE_BOOT_DEVICE
STOP code 0x7B is always caused when the computer is booting, and can be the most frustrating BSOD error code. It simply means that while the computer was reading from the system partition on one of the hard disks, the read was interrupted and the computer cannot boot. Most of the time, this means that the disk is damaged, sometimes irrevocably. After verifying that a boot into safe mode and running chkdsk does not work, you need to replace the disk and reinstall Windows.
STOP 0x0000002E: DATA_BUS_ERROR
Stop code 0x2E may annoy you if you have an older computer. This error is almost always caused by faulty RAM, and it is comparatively one of the easiest to fix. Mismatched or bad RAM can cause the issue. Remove one stick of RAM and see if the problem persists. If it does, replace the stick you removed and remove the other one. You can either leave your computer with one RAM module or replace it at your convenience.
So whether it be Hardware, Software, Overheating, bad Overclocks or simply a Virus, BSODs should be a little less taxing now (I hope) and your new best friend who'll give you all the information you need to solve the problem.
I hope this gives just a little insight into the wonderful world of Blue Screen errors and puts a few minds at ease, if you have any issues or questions, start a new thread and ask away we are just a click away.
EDIT: For those in the OC fraternity
The Overclock BSOD Codes are as follows.
0x101 = increase vcore
0x124 = increase/decrease QPI/VTT first, if not increase/decrease vcore
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
0x1A = Memory management error. It usually means a bad stick of Ram. Test with Memtest or whatever you prefer. Try raising your Ram voltage
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
I'm not about to fix every BSOD that crosses my path but I can point you in the right direction and help you work out the root cause, and hopefully set your system back on the straight and narrow.
A BSOD followed by a instant reboot, this usually does not give you enough time to see the actual stopcode and generally leaves you wondering what the hell just happened, well windows is automatically configured to reboot immediately after a serious issue has occured this can be rectified by disablling the automatic "restart on system failure" Follow the path below also pictured.
Control Panel\System\Advanced system setting\Advanced\Startup and Recovery and uncheck the "Automatically restart" check box.
Now when your system crashes it will remain on the blue screen indefinitely until you reboot giving you plenty of time to take some notes.
Once you have your stop code which should look something like this 0x00000051 (Registry_error), you can then begin your journey narrowing down what went wrong.
To figure out what each code means, you can do this by visiting Microsofts "Bug Check Code Reference page"
Alternatively you can download BlueScreenView and view the minidump file created by the BSOD, this actually yields more information than simply searching Microsofts code list as it will show you the drivers and their addresses located in the crash stack pin pointing the issues at hand. Click the image for a link to BlueScreenView download.
I could go through every code and eventuality that arises from a bluescreen crash but I'm not going to as this thread would be enormous and TTL doesn't pay me enough :lol: what I will do though is run through the most common causes of Bluescreen which should help point you in the right direction and hopefully save us some time on the forums when helping people with future issues.
STOP 0x0000000A: IRQL_NOT_LESS_EQUAL
Stop code 0xA is the most common BSOD error code, it is also the most annoying error. It occurs when one of the device drivers on the computer attempts to interrupt the CPU with a priority that is too high. To fix it, you are generally advised to reinstall or disable device drivers until you find the offending component. Some virus scanning software can also cause the issue.
STOP 0x00000024: NTFS_FILE_SYSTEM
STOP code 0x24 is quite self-descriptive, but may still plague you; an issue in the NTFS file system causes it. This usually means that the file system on one of the hard drives attached to your computer is corrupt or damaged. Running chkdsk and using a SMART utility to check for faulty hard disks like HDTune should help you fix the issue.
STOP 0x0000007B: INACCESSIBLE_BOOT_DEVICE
STOP code 0x7B is always caused when the computer is booting, and can be the most frustrating BSOD error code. It simply means that while the computer was reading from the system partition on one of the hard disks, the read was interrupted and the computer cannot boot. Most of the time, this means that the disk is damaged, sometimes irrevocably. After verifying that a boot into safe mode and running chkdsk does not work, you need to replace the disk and reinstall Windows.
STOP 0x0000002E: DATA_BUS_ERROR
Stop code 0x2E may annoy you if you have an older computer. This error is almost always caused by faulty RAM, and it is comparatively one of the easiest to fix. Mismatched or bad RAM can cause the issue. Remove one stick of RAM and see if the problem persists. If it does, replace the stick you removed and remove the other one. You can either leave your computer with one RAM module or replace it at your convenience.
So whether it be Hardware, Software, Overheating, bad Overclocks or simply a Virus, BSODs should be a little less taxing now (I hope) and your new best friend who'll give you all the information you need to solve the problem.
I hope this gives just a little insight into the wonderful world of Blue Screen errors and puts a few minds at ease, if you have any issues or questions, start a new thread and ask away we are just a click away.
EDIT: For those in the OC fraternity
The Overclock BSOD Codes are as follows.
0x101 = increase vcore
0x124 = increase/decrease QPI/VTT first, if not increase/decrease vcore
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
0x1A = Memory management error. It usually means a bad stick of Ram. Test with Memtest or whatever you prefer. Try raising your Ram voltage
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
~Wraithguard~
Last edited:
