Question BSOD caused by ntoskrnl.exe ?

[verglas]

Hiya everyone. I'm new to this forum so I'll keep it direct.

I have been facing multiple BSODs months ago since at least June. On June, I figured one of the 8GB RAM sticks has a problem (it made clicking sounds when i pressed on it) so I replaced it and done two reset of my PC but the problem still kept on going. Couldn't figure out if the RAM stick causes the BSOD or its a driver issue.

On July, I play a game (VNs and FPS games) in Steam, my BSOD is bound to blue screen after playing (after 3 hours or so). Nowadays, it chooses to blue screen at random intervals when I leave it idle. Last Sunday, I used MemTest86 on both RAMs (though ended the test nearly when its done since I didn't had time) and it detected no errors. I reseated both RAMS again and it blue screens much faster when I leave it idle. I turned off sleep mode and fast startup, updated my BIOS (maxsun a520m), and my graphics driver (NVIDIA GTX 1660 Ti).

I feel like it could be overheating, but I have no idea why. Is it because of the PC case? The case of the PC case is broken and my hardware doesn't look too dirty but I'll have it cleaned next week if it is truly the problem.

Computer was a gift in 2023.

BSODs (July to August) minidumps and speccy
all caused by ntoskrnl.exe
• IRQL_NOT_LESS_OR_EQUAL
• ATTEMPTED_EXECUTE_OF_NO_EXECUTE MEMORY

 

[ubuysa]

You're running with mismatched RAM and from the dumps that looks to be the most likely source of your problems. The RAM part numbers you have are...

Ramaxel 8GB RMUA5110ME78HAF-2666
Teamgroup 8GB TEAMGROUP-UD4-3600

Mixing different RAM models is a well known cause of BSODs. Typically differences in internal timings is the cause. Always buy RAM in a pack of matched sticks.

I would remove one stick and run on just the one for a few days, or until you get a BSOD. Then swap the sticks over and run on just the other for a few days, or until you get a BSOD. You will most probably find that they run perfectly on their own, but you get BSODs with them installed together.

In that case I would ditch both RAM sticks (you may be able to sell them on) and buy a pack of matched sticks suitable for your motherboard. The Qualified Vendor List of tested RAM can be found in the support section of your motherboard page, buy new RAM in a pack from this list.

 

[verglas]

You're running with mismatched RAM and from the dumps that looks to be the most likely source of your problems. The RAM part numbers you have are...

Ramaxel 8GB RMUA5110ME78HAF-2666
Teamgroup 8GB TEAMGROUP-UD4-3600

Mixing different RAM models is a well known cause of BSODs. Typically differences in internal timings is the cause. Always buy RAM in a pack of matched sticks.

I would remove one stick and run on just the one for a few days, or until you get a BSOD. Then swap the sticks over and run on just the other for a few days, or until you get a BSOD. You will most probably find that they run perfectly on their own, but you get BSODs with them installed together.

In that case I would ditch both RAM sticks (you may be able to sell them on) and buy a pack of matched sticks suitable for your motherboard. The Qualified Vendor List of tested RAM can be found in the support section of your motherboard page, buy new RAM in a pack from this list.

I understand. But I have a question. Why does the original RAM stick (I had 2 Teamgroup 8GB TEAMGROUP-UD4-3600) caused the BSODs before I replaced it?

 

[beyondlogic]

I understand. But I have a question. Why does the original RAM stick (I had 2 Teamgroup 8GB TEAMGROUP-UD4-3600) caused the BSODs before I replaced it?

Run the ram at 3200 not 3600 higher speeds then 3200 aren't guaranteed and become unstable.

Also it can be a corrupt windows installation

 

[verglas]

Run the ram at 3200 not 3600 higher speeds then 3200 aren't guaranteed and become unstable.

Also it can be a corrupt windows installation

Corrupt windows installation?