We’ve all experienced it before. Whether we’re hard at work sending an important email or in the middle of an online game with friends, we’ve all fallen victim to the Blue Screen of Death. The Blue Screen of Death, also known as a BSOD or, officially, the Windows Exception Error, occurs when the Windows operating system encounters a critical problem and is unable to recover from it. And, unfortunately, there are many different factors that can trigger a BSOD. So today, we’re going to help you diagnose your BSOD in order to help prevent it from occurring in the future and hopefully improve the health of your PC.
BSOD, or simply blue screen, refers to the generic sets of error messages that Windows computers display whenever the system encounters a critical problem that causes the entire operating system to fail. A blue screen means that the system can no longer continue, and is forced to restart itself completely. In addition to displaying a blue screen, the screens will also give a “stop code,” which describes the type of problem that caused the BSOD to occur.
While there are many different factors that could potentially cause them, the most common causes of blue screens generally have to do with a computer’s hardware, or with the hardware driver software. Generally, regular applications, such as Microsoft Word or Google Chrome, usually aren’t the cause of BSODs; if an app crashes, it should do so without causing the entire operating system down with it.
BSODs are caused whenever Windows encounters a “Stop Error,” which is a critical failure in the Windows OS that makes it crash and cease to function. Whenever this occurs, Windows has no other option other than simply restarting the entire system. This often can result in data loss, as programs won’t have the chance to save any open data. Fortunately, whenever BSODs occur, Windows automatically creates a “minidump” file that contains any information about the crash and saves it to your hard drive. You can view the minidumps in order to help identify the cause of your BSOD.
There are many different BSOD error messages that could appear on your computer, but here are the ten most common ones:
● DATA_BUS_ERROR - This error message is caused by memory failure. The solution to fixing this message is fixing your RAM memory; that means you’ll need to check your RAM stick function with the application MemTest and replace the hardware if needed.
● INACCESSIBLE_BOOT_DEVICE - This error code is caused when the system is missing the necessary drive. In order to fix this error message, you’ll need to update the driver or install it if it isn’t installed on the system.
● UNEXPECTED_KERNEL_MODE_TRAP - This error message can either be caused by a hardware error or from the system’s temperatures getting too high. If the problem is the former, you’ll need to uninstall and then reinstall the device driver. If the issue is the former, you should check your system’s fan performance, clean your computer, or see if there are any environmental factors negatively affecting your PC’s cooling efficiency.
● NTFS_FILE_SYSTEM - This error message is caused by high CPU memory usage. To fix this problem, you should check to see which programs are using the most CPU memory in Task Manager. If necessary, try uninstalling/reinstalling the programs in question and see if it improves CPU usage. Another option is to check your hard drive that Windows is installed on and see if there are any errors in Windows processes.
● IRQL_NOT_LESS_OR_EQUAL - Caused by incompatible or outdated device drivers. To fix this error, deactivate drivers of recently installed devices through the device manager, and then install the newest version of the driver from the device’s manufacturer and install it.
● BAD_POOL_CALLER - Caused by unwanted memory access. Deactivate drivers for recently installed devices and obtain the newest version of the driver from the device’s manufacturer and install it on your system.
● FAT_FILE_SYSTEM - This error is caused by a corrupt file system. To fix it, check your hard drive function; from the Start menu, search “chkdsk” and run it.
● OUT_OF_MEMORY - Caused by memory failure. Check your RAM stick function with MemTest, and replace your RAM if needed.
● PAGE_FAULT_IN_NON_PAGED_AREA - Like the previous error message, this is caused by memory failure. Likewise, you’ll need to check your RAM with MemTest. If needed, you’ll need to replace your RAM hardware.
● UNABLE_TO_LOAD_DEVICE_DRIVER - This error is caused by defective software. To fix this problem, you’ll need to uninstall and then reinstall the newest or most compatible version of the software.
There are many different steps that you can take in order to help diagnose and prevent future BSODs. Here are some of the most effective ways for you to help solve system errors, and prevent future ones from occurring.
Uninstall Incompatible Software
This is one of the most common causes of BSODs, and also the simplest to solve. While the BSOD doesn’t always explicitly state the cause of its occurrence, be sure to pay attention to see if it happens when using a particular program. If you do get a BSOD whilst using a particular program, then that program could very well be the culprit. If there’s an update available for said program, be sure to upgrade to it. If not, try uninstalling that app and see if the problem stops. Alternatively, take a look at what other programs you were actively using when the BSOD occurred. Try uninstalling any software that was running every time a BSOD occurred, and see if it fixes the problem.
Run a Memory Checker
Defective RAM (Random Access Memory) is another somewhat common cause of a BSOD, and it’s also a fairly easy problem to identify with the memory-checking tool built into Windows. To access it, go to the Start search box and type “Memory” and then click “Windows Memory Diagnostic.” Click the option “Check for problems the next time I start my computer” and then restart your PC. Upon booting, your computer will run the test.
After restarting, you’ll need to find the test result. To do so, go to the Start search box again and type “Event Viewer” and click on the application of the same name when it pops up. In the left pane, click “Windows Logs” and then click “System.” In the right pane, click “Find” and search for “Memory Diagnostic.” You should then see the test results -- if there are any sort of problems to report, then your system’s BSOD may have been caused by defective memory. In this case, you should replace your RAM sticks.
Check for Hard Drive Issues
Additionally, hard drive-related issues are another common cause of BSODs. To check for errors, go to the Start search box and type “this PC” and click it when it appears in search results. Right-click on your “C” drive and select “Properties.” Next, click on the “Tools” tab in the hard drive’s Properties window. Under the “Error checking” section, you’ll want to click “Check” and then follow the instructions given in order to manually check the hard drive.
Make Sure Your PC Isn’t Overheating
It’s also very possible that your computer could be overheating; this problem can occur whenever your PC is working too hard, whilst receiving ineffective cooling from the CPU cooler or fans. Every PC needs to have an effective way of cooling itself, by having enough fans that properly ventilate the unit and should be in an environment that allows it to breathe. More often than many assume, BCODs occur because of overheating. Make sure your PC isn’t overheating by inspecting it.
Perform a Clean Install
If none of the prior tips have successfully corrected your BSOD issue, then you are essentially left with two basic possibilities: either you have a software issue that you have yet to properly isolate, or you have a critical hardware problem with your computer that cannot be easily replaced or repaired.
In order to figure out whether your problem is the former, you should try performing a clean install of Windows. You should only attempt this after trying all other aforementioned steps, as performing a clean install will erase all of the content from your hard drive. In addition to losing all of your personal data, you will also lose all of your installed programs on the computer.
To do this, you’ll first want to click the Start search box and type “reset.” Click “Reset this PC” and then follow the directions to reinstall Windows, and keep your files if you so wish. Once completed, you’ll have a fresh version of Windows without any of the software or drivers that may have been causing the BSOD. Moving forward, try to only install and use the most essential software and drivers until you can determine whether your problem has been solved.
Bring your PC to Micro Center!
The alternative to all this is to simply bring your PC to Micro Center. We’ve got skilled technicians who are happy to take a look at your PC and help diagnose any problems or questions you may have so you can get back to gaming, working, or streaming without breaking a sweat! Find out more here.
We hope that this guide has been of some use to you, and hopefully your BSOD problem is properly solved by following these tips!
More from the Micro Center Community:
Looking for more troubleshooting help? We’ve got Community Subsections, as well as articles on Updating your Video Card Drivers, and Blue Screen Frequently Asked Questions. And if you can’t find what you’re looking for, don’t hesitate to post a new discussion and the Community will be happy to help!
Oh boy... I am uncertain if my will is strong enough to tackle the ignorance that is this "crash course", but for the sake of our future tech enthusiasts, I'll endure.
We’ve all experienced it before. Whether we’re hard at work sending an important email or in the middle of an online game with friends, we’ve all fallen victim to the Blue Screen of Death.
This is a bold way to start this guide, given ALL of the information that proceeds this sentence lacks any experience of any kind. I am aware this is quite the claim to make given the volume of "information" in this guide, but that's what makes it all the more alarming, and my involvement in correcting this misinformation all the more necessary.
The Blue Screen of Death, also known as a BSOD or, officially, the Windows Exception Error, occurs when the Windows operating system encounters a critical problem and is unable to recover from it.
This might be nitpicking to start it out, but it's definitely off to a bad start when we begin by confusing titles/general nomenclature. BSOD's were not officially called "Windows Exception Errors", they were known as "Fatal Exception Errors", and even this is considered a dated definition and has since been changed to encompass a larger array of stop codes encountered during crashes. Either way, let's avoid adding "officially" to something if we do not get it right.
While there are many different factors that could potentially cause them, the most common causes of blue screens generally have to do with a computer’s hardware, or with the hardware driver software.
I am going to need you to cite your sources here as this sounds completely made up by somebody that doesn't understand the concept of stop codes or their origin. A stop code can manifest through software conflicts (stack overflows, buffer underflows/underflows, conflicting memory access within the same address/row/column while another application is attempting to access that area/page, etc) just as commonly as it can via hardware issues. This claim is already dubious at best, and that's before we even begin with this list of "common BSOD's"...
Fortunately, whenever BSODs occur, Windows automatically creates a “minidump” file that contains any information about the crash and saves it to your hard drive.
Windows will attempt to do this, but it is not always successful in doing so. It is important to make that distinction as this useful troubleshooting tool will not always be readily available and one will have to rely on alternative logs in the event that a minidump fails to be written at the time of a crash.
I honestly do not know where you googled this list, but I am dumbfounded as to how anyone believes these are the 10 most common BSOD's. I've been in this field for over two decades and have not encountered 70% of the BSOD's on this list. I can name 20 off the top of my head that are far more common that I can induce instantly that the average user would encounter before ever seeing the vast majority of these.
This error CAN be caused by memory, but memory is not the ONLY cause. Failing L2/L3 cache can cause this error, failing VRAM (video frame buffer) can cause this error, and dying storage could cause this error. Speaking so definitively about this being memory related is simply inaccurate when there are several pieces of hardware that can easily produce this uncommon error. Also, please do not add "RAM Memory" to the list of RAS syndrome phrases we commonly use on a daily basis. Use DIMM, memory, or RAM. People will know what you are talking about. Same with "RAM Stick". If we are going to be writing guides, lets use the industry standard technical terms like "DIMM" or "Memory Module". Anything is better than "RAM stick". Lastly, what MemTest application are you referring to? HCI MemTest? MemTest86? Windows Memory Diagnostic? Each of these do very different things and will have very different results.
Okay, this one is rough. First and foremost, INACCESSIBLE_BOOT_DEVICE is not caused by a "missing drive". If your drive is missing, you can't BSOD in the first place because you have no Windows environment to boot to, and you can't BSOD without a bootable Windows environment. Secondly, installing a driver for a missing drive? What kind of paradox are we trying to create here? Assuming you meant "driver" in the first sentence (in which case, proof reading before submitting guides goes a very long way in preventing posts like these), that's still only applicable if we are talking AHCI vs RAID and someone forgot to install their RAID driver or swap back to AHCI after breaking a RAID array. Either way, there are tons of other culprits that cause this BSOD and solutions to fix them as they arise. It should also be noted that this would not be the BSOD you'd see if you had a missing RAID driver, that would typically be DRIVER_PNP_WATCHDOG.
Again, this is not a common BSOD, it's only ever found on Intel CPU's by design. I am honestly not even sure where you got the information you wrote because the official page that houses this BSOD information doesn't even list CPU temperatures as a culprit and I can't imagine you made this up (given most of your other "error" definitions were found in the first post of Google). https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0x7f--unexpected-kernel-mode-trap. To clarify that article, this BSOD commonly occurs when you mix incompatible memory on Intel platforms. Why only Intel platforms? Intel deploys a unique memory solution known as "Flex Channel Memory" that allows you to mix different sized DIMM's and run them in a mixed single/dual channel configuration. You can go further than this, mixing different ranks & IC's, which is what leads to instability and this BSOD in question. This happens to be one of the BSOD's you've listed that I've encountered. Those of you mixing memory for performance should instead just OC the memory you already have. There happens to be a guide written by a very handsome memory OCing expert on this very forum and it can be found here (#humblebrag): https://community.microcenter.com/discussion/8683/intel-memory-overclocking-performance-tuning-guide
Not even close... The hint for this one is in the name: https://en.wikipedia.org/wiki/NTFS. Now I am known to have stupidly high memory capacities, but even I wouldn't create a RAM disk and format it to NTFS, given the volatile nature of memory. Once again I am very confused where this misinformation came from because even Googling this error doesn't result in something as spectacularly wrong as what was described here. Those of you encountering this (again, rare) BSOD, it is actually found more commonly on older HDD's with failing drive sectors. You may encounter this on SSD's (especially if you defrag them as you're not supposed to do so, or any SSD with a ton of write wear in general), as well as simple corruption in the NTFS file system (great, another RAS syndrome example). Honestly, go here for more information as it's far more accurate and should have been the source used to answer this question in the first place: https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0x24--ntfs-file-system
Okay, this happens to be one of my most encountered BSOD's. Anyone that overclocks memory as a hobby is well aware of this BSOD and will encounter it half a dozen times in a single memory OCing session if they are playing on the edge of stability. Now I won't say it can't be caused by incompatible drivers (in theory, drivers accessing incorrect memory addresses could induce this crash), but this is far more commonly associated with memory. Either failing memory modules, or unstable overclocking. To not mention this at all, when it's far more common of an issue, only adds to my concern for this "crash course". Also, for the love of all that is holy, do not "deactivate" your drivers when you install the wrong one. Uninstall it like a normal person and install the correct drivers.
Not caused by "unwanted memory access", but rather by incorrectly attempting to free memory that has already been freed, meaning it's trying to give away resources it no longer possesses. What frustrates me the most about this is that you correctly deduce this BSOD is related to memory, but not IRQL_NOT_LESS_OR_EQUAL when they are in the same family of stop codes. Again, don't deactivate your drivers, uninstall them responsibly.
FAT_FILE_SYSTEM - This error is caused by a corrupt file system. To fix it, check your hard drive function; from the Start menu, search “chkdsk” and run it.
Technically correct, however a failing drive in general can also cause this error. You uh... also forgot a very important parameter in order to "fix" the disk with CHKDSK. Definitely worth throwing in a /f or /r for good measure: https://docs.microsoft.com/en-us/windows-server/administration/windows-commands/chkdsk
First and foremost, wherever you Googled this one from, the source is old. We call this one "MEMORY_MANAGEMENT" now. Secondly, it's not caused exclusively by memory failure. In fact, memory failure is probably the rarest cause of this error as you'll likely encounter a CPU memory controller failure or BIOS memory training issue before the DIMM itself is at fault for this specific error. RAM errors are seldom ever consistent, as the name implies, "random" is the name of the game here.
It CAN be a memory failure, but it's not limited entirely to memory as the only culprit. You also have your CPU (cache, memory controller) as well as software (drivers, antivirus conflicts on live software/drivers, etc). Again, we need to be careful about being definitive telling people they have specific hardware failure when we are not even certain that is the case.
Now like I said earlier, I've been doing this for a couple of decades now, but I've never encountered this BSOD. Are you sure you don't mean "THREAD_STUCK_IN_DEVICE_DRIVER? That one is actually a bit more common and would make sense. Frankly, I am not even sure if what you are listing here is a real stop code as I can't even find it in Microsoft's database of stop codes. I'd even settle for DRIVER_VIOLATION as I've actually seen that one come up a few times lately, but yeah... No idea what this even is or why it is in this list. I genuinely feel like this list came from some dated source written by someone that may not have known what they were talking about but didn't have anyone around to fact check them.
Now we move on to preventative measures!
This is one of the most common causes of BSODs, and also the simplest to solve.
Wait a minute... Earlier in the thread, it was said that the most common BSOD's were related to computer hardware and "hardware driver software". Now we are being told that incompatible software is one of the most common causes. At this point, it seems like everything is a common cause for a BSOD...
Fun fact about the Windows Memory Diagnostic Tool: It's quite old and not designed to perform all that well with modern CPU IMC designs and memory capacities. You'll encounter many false positives (or in some instances, failure to catch bad memory) due to the poor design of this "test". I would strongly advise against using this as a test, and would instead recommend alternatives such as HCI Memtest, Memtest86 or TestMem5. These are designed to reach every address/row/column and can also accurately stress your CPU's memory controller simultaneously while providing accurate logs on what failed and where.
Might be worth adding that modern drives include S.M.A.R.T information that is readily available in many hardware monitoring applications (AIDA64, HWiNFO64, etc) and can provide some forewarning about your drives health without constantly throwing a check disk at it out of the blue.
Fun fact: Overheating computer components (with the exception of RAM) do not cause BSOD's. They lead to thermal throttling and thermal shutdown, but not BSOD's. In the specific case of RAM, overheating memory can cause a BSOD but only in the event that you adjust your TREFI value too high and the DIMM's get too warm. When your DIMM's get too warm, TREFI wants to recharge quicker, and a lackluster motherboard will likely fail to recharge them in time, resulting in corruption and a BSOD. Another fun fact: Overheating can occur even when your PC isn't working hard. Poor cooling is the only requirement for overheating and can occur even when the system is at idle. Do not be fooled by low system load and assume that an idle system cannot overheat.
We are going to ignore the first bolded part, because if none of the prior tips successfully corrected the BSOD issue, that means the reader followed the instructions of this "guide" exactly as written and fell victim to misinformation. Luckily I returned in time to save the day,
Okay... the second half that is bolded is important to note, because it's more misinformation. This is NOT a clean install. This is a "reset this PC" with "keep my files" selected. This is the exact opposite of a clean install. Here is a third party definition to help clarify: https://www.pcmag.com/encyclopedia/term/clean-install#:~:text=A%20completely%20new%20installation%20of,is%20formatted%20and%20completely%20erased.&text=Installing%20an%20OS%20on%20a,%22in%2Dplace%20upgrade.%22
The reason we do a "clean install" is to rule out ANY possible corruption from the source of the drive. Resetting the PC from the potentially corrupted OS can potentially reintroduce the very corruption you are trying to remove. The drive needs to be completely formatted and installed from bootable media in order to successfully perform a clean installation.
In all honestly, I wouldn't be as annoyed had this not been presented as a source material to help others that are less informed on this subject. Writing a guide from a place of ignorance just does more harm than good and further perpetuates ignorance and a general lack of understanding the longer you let something like this go on. There needs to be some accountability here, some form of proof reading to ensure you are not intentionally (or unintentionally) condemning your audience to failure with their troubleshooting simply because you are rushing out articles with zero thought as to what is conveyed within them. At the end of the day, there is just no excuse for how poorly researched this article is given the age we live in and how readily available this information is online.
Submit photos and a description of your PC to our build showcase
See other custom PC builds and get some ideas for what can be done
Services starting at $149.99
