Question BSOD ntoskrnl.exe crashing computer

[Aciddragon]

I've recently updated my PC's parts and have been having frequent but random crashes. I have tried updating drivers, removing peripherals, checking system files for corrupted files, repairing drives, doing memtest86, I even tried reseating my CPU and RAM but that hasn't helped either. It can happen when I boot or when I'm playing a game or when I'm just using a browser, or even when the computer isn't doing anything. It also always crashes when waking up from sleep mode after a random amount of time.

My computer's specs are
Motherboard: MSI pro A260M-E
CPU: AMD Ryzen 5 8500G
Graphics card: Nividia Geforce RTX 3070 ROG STRIX GAMING OC
RAM: two sticks Patriot Signature Line DDR5 8gb

I also copied my main drive onto a 2TB SSD

The crashes tend to have different names but they allows point to ntoskrnl.exe as the reason for the crash. Here are the logs here I didn't know if I should save them as txt files but it wouldn't let me upload the dmp files directly.
The crashes also only started a bit after running the PC for a while so I'm not sure if the problem is old drivers, new software, or hardware

 

[Lutfij]

Welcome to the forums, newcomer!

I've recently updated my PC's parts and have been having frequent but random crashes.
When posting a thread of troubleshooting nature, it's customary to include your full system's specs. Please list the specs to your build like so:
CPU:
CPU cooler:
Motherboard:
Ram:
SSD/HDD:
GPU:
PSU:
Chassis:
OS:
Monitor:
include the age of the PSU apart from it's make and model. BIOS version for your motherboard at this moment of time. Since you mentioned updating/upgrading your parts, please pass on the parts you've recycled from your older build.

To also add, you picked the wrong board for your system. You should've looked into a motherboard with a better VRM design.

I also copied my main drive onto a 2TB SSD
If you cloned your older OS drive onto the new drive, this is your mistake, reinstall the OS and you should be clear waters.

I didn't know if I should save them as txt files but it wouldn't let me upload the dmp files directly.
You can host your .dmp files onto a site akin to DropBox and then pass on a link for us to see here.

 

[johnbl]

I've recently updated my PC's parts and have been having frequent but random crashes. I have tried updating drivers, removing peripherals, checking system files for corrupted files, repairing drives, doing memtest86, I even tried reseating my CPU and RAM but that hasn't helped either. It can happen when I boot or when I'm playing a game or when I'm just using a browser, or even when the computer isn't doing anything. It also always crashes when waking up from sleep mode after a random amount of time.

My computer's specs are
Motherboard: MSI pro A260M-E
CPU: AMD Ryzen 5 8500G
Graphics card: Nividia Geforce RTX 3070 ROG STRIX GAMING OC
RAM: two sticks Patriot Signature Line DDR5 8gb

I also copied my main drive onto a 2TB SSD

The crashes tend to have different names but they allows point to ntoskrnl.exe as the reason for the crash. Here are the logs here I didn't know if I should save them as txt files but it wouldn't let me upload the dmp files directly.
The crashes also only started a bit after running the PC for a while so I'm not sure if the problem is old drivers, new software, or hardware

files not shared for public access.

 

[Aciddragon]

files not shared for public access.

I just fixed that now sorry

 

[johnbl]

note: your cpu came out jan 2024
windows version is strange:
Major Version : 15
Minor Version : 19041 (may 2020 release)
not sure why major version is 15 rather than 10
minor version, first part indicates a 2019 build
maybe updates not being applied? (microsoft amd cpu specific dll might not be loaded for your newer cpu)


you have to ignore the bugchecks that have access violation for the error code. (number 1 and 5 below)

ignore the bugcheck with the undocumented error code #2
that leaves #3 and #4 as the most helpful bugchecks
number 4 is most common with a overheated cpu or a bad overclock or underclock. first thing I would look for is a cpu fan that is controlled by a usb port. IE your system goes to sleep but the port does not wake up and the fan does not restart.
Second thing would be having more than one CPU overclocking drivers installed. (debug command lmiftsm shows the list of drivers installed)
third thing to look for: make sure the GPU supplemental power connectors are connected to the GPU. if the GPU does not get proper power, it will pull to much power thru the PCI/e bus and the motherboard power protection circuit will reset the CPU. if this is the case you want to look in the debugger and look at the system up time. If the time is short (under 15 seconds) it indicated the motherboard reset the CPU but the power supply did not hold the cpu from restarting, this causes the system to reboot and immediately restart with low power on the CPU pins. It can then lead the cpu to detect errors and call a bugcheck.

the errors relating to the PTE or PFN could be cpu errors or errors caused by power fluctuations but then saved to virtual memory (pagefile.sys) you will want to google "how to make windows delete the pagefile.sys on system reboot" make the registry changes and reboot. (just to prevent confusion as to the cause of the error)

The virtual memory error can also happen with overheated cpu, bad overclock to cpu, bad voltage to the CPU/gpu and bad firmware in a ssd or need to update CPU chipset drivers.

best guess is overheated cpu (assuming you do not have two copies of a overclocking driver installed, and no bios overclock and your voltages from your PSU are within spec.
if you have a all in one cooling for your CPU that is connected to a usb port. go into windows control panel device manager, find the usb port, right mouse click to bring up properties then find the power management tab and uncheck the option to let windows turn off the device to save power. short burst of no cooling fan on a cpu could cause overheating of cpu.
providing actual minidump.dmp file can help eliminate some of the causes of this error. But the interesting bugcheck are panic bugcheck from the CPU and may not have all of the proper data stored.


notes:

1) 040325-5859-01.txt error code = access violation

2) 040325-5781-01.dmp bugcheck 0x139 error code undocumented

3) 040325-5718-01.dmp bugcheck 0x1a error code 0x888a
Internal memory management structures (likely the PTE or PFN) are corrupted.

4) 040325-5609-01.dmp bugcheck 0x1000007f UNEXPECTED_KERNEL_MODE_TRAP error code 8
error code 8 is a double fault. (error happened then a error handler also got a error)
(could be a stack overflow/corruption)


5) 040325-5515-01.dmp bugcheck because a service died due to access violation

note: also, if you can not find a cause of this problem, make sure you update the bios and motherboard drivers. some versions of the CPU were unstable during low power mode that new windows sleep functions use. (two low of voltage, bios updates fix this, also the fixes are put in certain version of cpu specific drivers, (ryzen master driver can override bios default voltages)

note: bugcheck with access violation error code:
can indicate a bad value for memory timing. best to update the bios, set your memory profile and run memtest86 to confirm your memory timings.
(I would skip this if you have run the test before and it passes. (since you mentioned that problem happen mostly after sleep)