Question Memory Management BSOD - ntoskrnl.exe

[czzzk]

Hello,

I've been having trouble with intermittent Memory Management BSODs. They are always caused by the ntoskrnl.exe driver, but show different Parameter 1's in BlueScreenView. It used to only occur when playing demanding video games, but most recently it occured when I had only my Firefox browser open with 5 tabs.

The following is a Google Drive link to the saved dumps (please let me know if these are not the correct dumps to share):

https://drive.google.com/drive/folders/1xNqaWh66Yy2HwcqFKfKdTdYQdMQoF4oA?usp=drive_link

I am running Windows 10.
I have recently replaced (as of May 25, 2024) my old 4x4gb RAM from 2011 with new 2x8gb RAM. I have experienced the BSODs with both my old RAM and now my new RAM.
I have an ASUS P8Z68-V PRO GEN3 motherboard, an overclocked 2600k processor (4.5ghz @ 1.35v), and a stock Nvidia 2070 graphics card.

How can I resolve this issue?

Your help is greatly appreciated, thank you!

 

[Bob.B]

Hello,

I've been having trouble with intermittent Memory Management BSODs. They are always caused by the ntoskrnl.exe driver, but show different Parameter 1's in BlueScreenView. It used to only occur when playing demanding video games, but most recently it occured when I had only my Firefox browser open with 5 tabs.

The following is a Google Drive link to the saved dumps (please let me know if these are not the correct dumps to share):

https://drive.google.com/drive/folders/1xNqaWh66Yy2HwcqFKfKdTdYQdMQoF4oA?usp=drive_link

I am running Windows 10.
I have recently replaced (as of May 25, 2024) my old 4x4gb RAM from 2011 with new 2x8gb RAM. I have experienced the BSODs with both my old RAM and now my new RAM.
I have an ASUS P8Z68-V PRO GEN3 motherboard, an overclocked 2600k processor (4.5ghz @ 1.35v), and a stock Nvidia 2070 graphics card.

How can I resolve this issue?

Your help is greatly appreciated, thank you!

Just to get it out of the mix.

Test with no overclock of the cpu.

Run a pass of memtest86.

 

[czzzk]

Just to get it out of the mix.

Test with no overclock of the cpu.

Run a pass of memtest86.

Thanks for the reply.

I have done both of the above as well as adjusted one of my heatsink fans that was making contact with the RAM. Four passes on Memtest86 gave no errors. I believe resetting my BIOS to Optimized Defaults was what did the trick.

I am now noticing that when I first boot my PC, it shuts off after ~5 seconds, before booting again successfully. Could this be related, or is it a separate issue?

I will monitor my system stability over the next several days and update if anything changes.

Cheers!

 

[ubuysa]

For the future please upload the dump files themselves, not the (usually useless) output from WhoCrashed/BlueScreenView/or similar.

 

[czzzk]

For the future please upload the dump files themselves, not the (usually useless) output from WhoCrashed/BlueScreenView/or similar.

I had a feeling those .txt files may have been worthless, thanks for letting me know. I found the .dmp files and have added them to the Google Drive link.

 

[Roland Of Gilead]

Hey there,

What bios are you currently running? With just swapping out the memory, this issue could be just an incompatibility in the bios. Updating it may solve the issue.

 

[czzzk]

Hey there,

What bios are you currently running? With just swapping out the memory, this issue could be just an incompatibility in the bios. Updating it may solve the issue.

Checking in SysInfo, it shows version 3402. It looks like version 3802 is the most recent. I'll download it to a USB for future use in case I run into issues.

 

[ubuysa]

Thanks for the dumps, taking them as a whole this looks very much like bad RAM to me. I can see that you've replaced older RAM with newer ram and had BSODs with both.

Firstly, is the new ram on the QVL for the motherboard and CPU? If it's not it doesn't mean it won't work but it does mean it's not been tested and verified, so with BSODs like this non-QVL compliance is a worry.

Secondly, were the two RAM sticks purchased as a matched pair (in a single pack)? If not, that could well be the problem.

Thirdly, can you try each of those two sticks on their own. Check the motherboard manual to ensure you're using the correct slot for just one stick.

 

[czzzk]

Thanks for the dumps, taking them as a whole this looks very much like bad RAM to me. I can see that you've replaced older RAM with newer ram and had BSODs with both.

Firstly, is the new ram on the QVL for the motherboard and CPU? If it's not it doesn't mean it won't work but it does mean it's not been tested and verified, so with BSODs like this non-QVL compliance is a worry.

Secondly, were the two RAM sticks purchased as a matched pair (in a single pack)? If not, that could well be the problem.

Thirdly, can you try each of those two sticks on their own. Check the motherboard manual to ensure you're using the correct slot for just one stick.

Thanks for checking them out! No new dumps to add so far today, hopefully that stability will continue.

1. The new ram is not on the QVL, and this could very well be the culprit.

2. They were indeed purchased as a matched pair.

3. I will do this if I run into any issues. Am I able to run Memtest86 without having my CPU heatsink installed? I have to remove it to access my RAM (Noctua NH-D15).

 

[ubuysa]

I would not advise powering the PC on with no CPU heatsink installed. That's unfortunate but I know of no other way to reliably test each RAM stick.

Are they in the correct slots?

 

[czzzk]

I would not advise powering the PC on with no CPU heatsink installed. That's unfortunate but I know of no other way to reliably test each RAM stick.

Are they in the correct slots?

Understood, thank you.

Yes, they are currently in the correct slots. Initially they were not (i.e. A1 and A2), but shortly before following Bob.B's instructions, I reseated them in the correct slots (i.e. A2 and B2) as per my motherboard's manual. This could have been the problem/a contributing factor when I experienced BSODs after installing the new RAM.

Stability is still very good, no new BSODs to report.

Still experiencing some strange behaviour on initial bootup (i.e. runs for 5 seconds, turns off, runs for 5 seconds, turns off, then boots normally), but otherwise running well.

 

[ubuysa]

Do you see that run/turn-off behaviour if you boot in Safe Mode?