Question BSOD: ntoskrnl.exe+412740 ?

[Inerald]

Hi, lately, a BSOD appears on my computer every time after startup.
I have Windows 11 (Version 10.0.22621.2428) installed on my computer, but BSODs also happen on Windows 10, and BSODs also happen on liveusb.

Processor: Intel Core i5-13600KF

Graphic card: Palit GeForce RTX 4070 Ti GamingPro [NED407T019K9-1043A].

Motherboard: MSI MAG Z690 TOMAHAWK WIFI (MS-7D32 VER:3.0). The latest BIOS version (E7D32IMS.HM1), but there were BSOD errors on another BIOS version as well.

Memory (RAM): OCPC Pista RGB Titan MMPT2K32GD552C36T 16+16 DDR5 5200MHz
DIMMA2: Micron MMPT2K32GD552C36 with 16 GB and DIMMB2: Micron MMPT2K32GD552C36 with 16 GB = Current DRAM size 32768 MB.

Storage(SSD/HDD): Any.

Default BIOS setting. XMP OFF, Game Boost Mode Off, OC mode off
64-bit operating system.
Reinstalling Windows does not help.

Please help.

Minidump Folder: https://drive.google.com/drive/folders/1sgC0_NX5bCNIry54nA3XbaUJQ_VQt4D3

 

[ubuysa]

I would strongly suspect bad RAM here. That's because two of the dumps fail with 0xEF (CRITICAL_PROCESS_DIED) bugchecks - that's almost always a hardware problem, usually RAM. That it fails with other OSs also suggests a hardware cause. The remaining dumps could also easily be caused by bas RAM, so that's where I'd start.

RAM tester software, like Memtest86, will take a long time to run on 32GB and you won't be able to use the PC whilst it's running. They can never find 100% of issues in any case. A better way to test your RAM will be to remove one stick for a few days, or until you get another BSOD. Then swap sticks and run on just the other stick for a few days, or until you get a BSOD. Make sure the single stick is in the right slot for your board (typically A2).

See how that goes.

 

[Inerald]

I would strongly suspect bad RAM here. That's because two of the dumps fail with 0xEF (CRITICAL_PROCESS_DIED) bugchecks - that's almost always a hardware problem, usually RAM. That it fails with other OSs also suggests a hardware cause. The remaining dumps could also easily be caused by bas RAM, so that's where I'd start.

RAM tester software, like Memtest86, will take a long time to run on 32GB and you won't be able to use the PC whilst it's running. They can never find 100% of issues in any case. A better way to test your RAM will be to remove one stick for a few days, or until you get another BSOD. Then swap sticks and run on just the other stick for a few days, or until you get a BSOD. Make sure the single stick is in the right slot for your board (typically A2).

See how that goes.

Thank you for your reply. I used MemTest86 and MemTest86+. I checked each RAM module individually and together, but these utilities did not find any errors.

 

[johnbl]

update bios (you are 12 versions behind)

https://www.msi.com/Motherboard/MAG-Z690-TOMAHAWK-WIFI/support#bios

after the update, if you can boot windows, then turn off virtual memory to delete the pagefile.sys, then turn it back on.

then update the motherboard drivers to the version that matches your motherboard bios.

each bugcheck took less than 30 seconds system uptime. does that seem correct? if you think you were running longer then you might have a power issue resetting your cpu.

in any case, update the bios is the next step.

bugchecks : reading registry, running windows error reporting, stack gauard

best guess is bios needs to be updated and current motherboard drivers applied.
(unless motherboard power protection circuits were triggered, only hint would be your system seemed to be running longer than 30 seconds before the bugchecks)