How to Fix the Memory Related BSOD Errors

Bluescreen of death or BSOD is a common problem. Recently moving to Windows 11 causing me a lot of trouble. My PC shuts off automatically when trying to play games or running many applications same time. My PC is a bit old and it worked perfectly all these time, but recently it just got very unstable. Even I upgraded the GPU with RTX 3050, CPU Ryzen 5 5600x processor and PSU Cooler Master 550 Watt. But still my PC is failing to run properly.

After gathering many information from the posts and threads that are available on Microsoft forums and other places, I realized that one of my memory is causing the problem. Possibly Graphics Card, or RAM or the two SSDs I have. 

Though GPU is brand new, and also my SSDs are in good health and also in good condition, I think in my case the culprit is RAM. When BSOD happens, windows creates minidump files with which you can check or ask to Microsoft support by sharing those files exactly what caused your PC crash. I am going to share the information about those dump files here - 

Crash dump file 1 - 



Bugcheck code:  0x50(0xFFFFF801850D56D0, 0x10, 0xFFFFF801850D56D0, 0x2) 

Bugcheck name: PAGE_FAULT_IN_NONPAGED_AREA 

Bug check description: This indicates that invalid system memory has been referenced. This can be caused by a faulty driver. Antivirus software can also trigger this error, as can a corrupted NTFS volume. It can also be caused by faulty hardware, (in particular faulty or overheated RAM or video RAM) or an overheated system component.  

Crash dump file 2 - 





Bugcheck code:  0x1E(0xFFFFFFFFC0000005, 0xFFFFF8011B8460FA, 0x0, 0xFFFFFFFFFFFFFFFF) 
Bugcheck name: KMODE_EXCEPTION_NOT_HANDLED 
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch. This could be caused by either a software or hardware problem.
Hardware failure is often caused by overheating. Read this article on thermal issues 

Crash dump file 3 -  

Bugcheck code:  0x50(0xFFFFF801850D56D0, 0x10, 0xFFFFF801850D56D0, 0x2) 
Bugcheck name: PAGE_FAULT_IN_NONPAGED_AREA 
Bug check description: This indicates that invalid system memory has been referenced. This can be caused by a faulty driver. Antivirus software can also trigger this error, as can a corrupted NTFS volume. It can also be caused by faulty hardware, (in particular faulty or overheated RAM or video RAM) or an overheated system component.  


Crash dump file 4 - 




Bugcheck code:  0x101(0x10, 0x0, 0xFFFFBD0195ED1180, 0x1) 
Bugcheck name: CLOCK_WATCHDOG_TIMEOUT 
Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval. This can be caused by non-responding hardware or by a overheated CPU (thermal issue). 

Crash dump file 5 - 

Bugcheck code:  0x101(0x10, 0x0, 0xFFFF9400BFFB4180, 0x7) 
Bugcheck name: CLOCK_WATCHDOG_TIMEOUT 
Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval. This can be caused by non-responding hardware or by a overheated CPU (thermal issue). This is likely caused by a hardware problem, but there is a possibility that this is caused by a misbehaving driver. This bugcheck indicates that a timeout has occurred. This may be caused by a hardware failure such as a thermal issue or a bug in a driver for a hardware device.


All these errors indicate that there might be a problem with hardware. Most of the time, when I saw something like this keeps happening to me, its because of a hardware. Either it got corrupted or maybe its not inserted properly. 

How to Fix the Memory Related BSOD Errors in Short Steps :-

  • From my personal experience, if BSOD happens and you see any of these errors, first you have to do is - remove your GPU, RAM and all other stuff and clean them properly and safely. Then put it back properly together. Most of the time when BSOD happens, its generally because of hardware failure.

  • If you have two RAM sticks, and you keep getting this error. My suggestion to you is check the single sticks one at a time, and see if each memory working properly. By doing this, you can find out if a single RAM stick is creating this error or not. Also try to use the sticks with default speed, do not activate extreme memory profile. Sometimes depending on your motherboard and CPU, using the RAM with its full memory clock speed may can crash your system. 

  • Make sure you installed the RAM sticks (if you have two) in the proper slots. Learn about your motherboard RAM slots, you can find it from the motherboard's manufacturer website. As for me, I have Gigabyte AB 350 gaming motherboard and the slots are distributed like this - DDR4 1(red), DDR4 3(black), DDR4 2(red), DDR4 4(black). So, to enable the dual channel memory properly, you have to install the RAM sticks at number 1 and number 2 slots or number 3 or number 4 slot. Which means either the red color slots or the black color slots. You use one red color and one black color slot, it may not going to show you any problem normally, but when you try to speed up the RAM or in long run, you may face BSOD errors.

  • For AMD GPU's, AMD drivers always messes the things a lot. So when you see your AMD driver is ready to install another update, just don't update. Wait with the one that's causing no problem. You can install the current AMD driver after like 1 month later. In case you installed the driver already and you see the pc crashing or giving BSOD, uninstall the driver first. Open the GPU and clean it a bit then put it back. Then find the old driver which worked for you earlier and install and you are not going to have any problem.
If you think your hardware's are in good state and a recently installed program causing the crash, then search the internet and you can find a lot of videos and Microsoft support forum topics where they gave countless solutions to the BSOD problems, maybe one of those will help. 

For any questions, just ask in the comment section. Thanks for reading my blog. Have a great day.


Comments

Post a Comment

Popular posts from this blog

An Update is Required to Continue Please Restart Fortnite Problem - Solved !!

Image
Hello everyone, if you ended up in my blog I am really glad that you did. I'll make sure not to disappoint. So are you having this weird problem when you are trying to play Fortnite? Every time you start the game and you see a message "an update is required to continue. Please restart Fortnite to download the latest patch". Well yeah, I have faced this problem twice now so I am sure its not me alone. Many of you can have this problem. So let's get straight to the solution how you can fix it - 1) Verify Fortnite files. I am sure you know how to do it. But in case you don't know, just go to your Epic Library and click on the gear symbol beside Fortnite launch bar and you'll see the option verify. Click there and wait till it gets completed and then restart the game and you'll see it's gone. A recent image of epic games from where you can verify Fortnite files 2) Log out from epic, restart your computer and log in again. Restart t
Read more

Failed to Open Descriptor File Uproject Problem - Solved !! Part 2

Image
 Hello Everyone, Hope you all are doing good. Now I am going to tell you how to solve the Failed to open descriptor file problem again. Previously I already wrote a post about this, it can help you fix the problem for your game, try it first, you can read it here .  Now, I have came up with this problem again. And this time it was a little different and my previous solution is unable to solve this problem. I was trying to play Rogue Company a few days ago. And I saw this problem failed to open descriptor file showed up again. But this time it has a message under the error, it was showing a file location that creating problem I guess, which is - RogueCompany/RogueCompany.uproject . I was trying to run this game from Epic Games Library. And every time I tried, the game Rogue Company crashed without launching giving this descriptor file .uproject problem. The thing is , it acted weirdly when I tried to solve it with the previous methods I mentioned on the other post . I tried a l
Read more

Failed to Open Descriptor File Problem - Fortnite | Solved !!

Okay, so are you getting this error message all of a sudden or after installing Fortnite or after updating the game? It can be frustrating when this "failed to open descriptor file" problem keeps coming when you try to run the game and can't find the solution. So what does this failed to open descriptor file means? It means that some of your game files are corrupted or missing. Somehow a sudden crash or a new update can cause this problem. So how do you solve it? In the case of Fortnite, all you have to do is go to your epic games library, find Fortnite and click on the option right beside the Launch and then click the verify button and wait. This process will verify all the files in the game and I am pretty sure after the verification is done, the descriptor file failed to open won't pop up again. This is an easy fix for Fortnite. About other games, if you have this problem, well if possible, see if you can find any option to verify the install
Read more