I experience BSODs under different conditions, yet the root issue remains consistent ---> ntoskrnl.exe?

F5F Stay Refreshed Software Operating Systems I experience BSODs under different conditions, yet the root issue remains consistent ---> ntoskrnl.exe?

I experience BSODs under different conditions, yet the root issue remains consistent ---> ntoskrnl.exe?

I experience BSODs under different conditions, yet the root issue remains consistent ---> ntoskrnl.exe?

Pages (2): 1 2 Next

K

KTHEDEVASTATOR
Junior Member

16

10-19-2021, 04:55 PM

#1

Hey everyone,

I've been experiencing some issues recently after setting up a new PC. I frequently encounter BSODs, especially when switching tabs using alt-tab from a game to a browser. These crashes happen gradually over a few minutes, not immediately. Even without playing games, I've seen BSODs occur.

PC specifications: 9800x3D, 64GB DDR5 RAM, PNY RTX 5080 OC, ASRock B850 Riptide WiFi. RM850x, Windows 11 Pro.

I ran memtest86 and confirmed the RAM is fine. The CPU passed tests with Cinebench and OCCT without any errors or crashes. I also performed a VRAM test on OCCT and everything worked perfectly. I updated the GeForce driver to 576.66 and reinstalled it using DDU.

Additionally, I had an RTX 5080 in my previous system (5600x, 32GB DDR4, TUF B550-plus, RM850x, Windows 11 Pro) without any BSODs. However, I'm currently facing game crashes, mainly from KCD2. The Event Viewer logs show an issue with the description for Event ID 153 from nvlddmkm. It seems the component triggering this event isn't installed or the installation might be corrupted. You can try installing or repairing it locally.

If the event happened on another machine, make sure to save display information with it.

I've attached a few .dmp files for reference:
- https://drive.google.com/file/d/1QLYWZ-y...drive_link
- https://drive.google.com/file/d/1us9KAM5...sp=sharing

I reached out to Nvidia support and contacted ASRock and PNY, but their responses were unhelpful. I'm at a loss about what to do next.

K

KTHEDEVASTATOR

10-19-2021, 04:55 PM #1

Hey everyone,

I've been experiencing some issues recently after setting up a new PC. I frequently encounter BSODs, especially when switching tabs using alt-tab from a game to a browser. These crashes happen gradually over a few minutes, not immediately. Even without playing games, I've seen BSODs occur.

PC specifications: 9800x3D, 64GB DDR5 RAM, PNY RTX 5080 OC, ASRock B850 Riptide WiFi. RM850x, Windows 11 Pro.

I ran memtest86 and confirmed the RAM is fine. The CPU passed tests with Cinebench and OCCT without any errors or crashes. I also performed a VRAM test on OCCT and everything worked perfectly. I updated the GeForce driver to 576.66 and reinstalled it using DDU.

Additionally, I had an RTX 5080 in my previous system (5600x, 32GB DDR4, TUF B550-plus, RM850x, Windows 11 Pro) without any BSODs. However, I'm currently facing game crashes, mainly from KCD2. The Event Viewer logs show an issue with the description for Event ID 153 from nvlddmkm. It seems the component triggering this event isn't installed or the installation might be corrupted. You can try installing or repairing it locally.

If the event happened on another machine, make sure to save display information with it.

I've attached a few .dmp files for reference:
- https://drive.google.com/file/d/1QLYWZ-y...drive_link
- https://drive.google.com/file/d/1us9KAM5...sp=sharing

I reached out to Nvidia support and contacted ASRock and PNY, but their responses were unhelpful. I'm at a loss about what to do next.

U

Ulrica_Seven
Member

51

10-19-2021, 05:05 PM

#2

The initial recommendation is to eliminate the RAM overclock and check for stability. Your RAM operates at 6000MHz, which is its maximum design frequency, though still an overclock. Take away all XMP settings and operate it at its SPD speed of 4800MHz. Inform us about the outcome.

U

Ulrica_Seven

10-19-2021, 05:05 PM #2

The initial recommendation is to eliminate the RAM overclock and check for stability. Your RAM operates at 6000MHz, which is its maximum design frequency, though still an overclock. Take away all XMP settings and operate it at its SPD speed of 4800MHz. Inform us about the outcome.

B

bchbum83
Junior Member

19

10-19-2021, 09:51 PM

#3

RAM is running at 4800mhz. But if we go back to the default speeds, it might resolve the BSOD issues, right? What should I do with my RAM? Should I just use it at a lower speed? This seems confusing. I'm not sure when the next BSOD will happen. It could come soon or not at all. Not always during games.

B

bchbum83

10-19-2021, 09:51 PM #3

RAM is running at 4800mhz. But if we go back to the default speeds, it might resolve the BSOD issues, right? What should I do with my RAM? Should I just use it at a lower speed? This seems confusing. I'm not sure when the next BSOD will happen. It could come soon or not at all. Not always during games.

J

JesperSlagroom
Member

71

10-20-2021, 02:49 AM

#4

Also check Reliability History/Monitor for error codes, alerts, and events recorded just before or during BSODs.
The tool offers a timeline view that helps identify trends.
Manually download drivers from the manufacturer's site, install and set up as needed. Avoid third-party installers.
Use "dism" and "sfc /scannow" to locate, detect, and potentially resolve corrupted files.

J

JesperSlagroom

10-20-2021, 02:49 AM #4

Also check Reliability History/Monitor for error codes, alerts, and events recorded just before or during BSODs.
The tool offers a timeline view that helps identify trends.
Manually download drivers from the manufacturer's site, install and set up as needed. Avoid third-party installers.
Use "dism" and "sfc /scannow" to locate, detect, and potentially resolve corrupted files.

N

nooneepic27
Member

227

10-20-2021, 06:11 AM

#5

The initial step would involve updating the AMD chipset driver to version 7.01.08.129 or later. The motherboard website lists a newer release dated April 15, 2025. I should review the available drivers and identify any additional updates required. Begin with the chipset drivers.

It seems the BIOS was updated, but the AMD chipset drivers weren’t installed correctly. You can find the latest version on the motherboard site. Check the driver list for further necessary updates.

Start with the chipset drivers.

N

nooneepic27

10-20-2021, 06:11 AM #5

The initial step would involve updating the AMD chipset driver to version 7.01.08.129 or later. The motherboard website lists a newer release dated April 15, 2025. I should review the available drivers and identify any additional updates required. Begin with the chipset drivers.

It seems the BIOS was updated, but the AMD chipset drivers weren’t installed correctly. You can find the latest version on the motherboard site. Check the driver list for further necessary updates.

Start with the chipset drivers.

I

IPresTiGez
Junior Member

15

10-20-2021, 07:04 PM

#6

However, I've already set up the latest chipset drivers. TrafficMonitor is a program for checking network and internal systems. I think reinstalling these drivers shouldn't change anything.

I

IPresTiGez

10-20-2021, 07:04 PM #6

However, I've already set up the latest chipset drivers. TrafficMonitor is a program for checking network and internal systems. I think reinstalling these drivers shouldn't change anything.

N

neokoner
Junior Member

6

10-23-2021, 08:15 AM

#7

I don’t know which version was installed from the dump, only the dates.
Occasionally the installer gets updated to a new date, yet drivers still display old dates.
I wasn’t able to pinpoint the exact reason for the bugcheck issue, so I examined the Windows build you were using.
The bugcheck process took three hours. You might try enabling verifier.exe testing to speed it up.
If you do that, you could add the bootmode switch to stop a boot bugcheck loop.
For example:
verifier.exe /all /bootmode resetonbootfail
(you can also add /driver.exclued yourdrivername to skip certain drivers during testing.)
After testing, run verifier.exe /reset.
Your system may then run more slowly until you finish.
You can switch the memory dump type to kernel for more detailed debugging info. The resulting file is called memory.dmp and is significantly larger.
For further assistance, see:
https://learn.microsoft.com/en-us/window...mmand-line
This tool can reveal driver packages on your system.
https://github.com/lostindark/DriverStoreExplorer

N

neokoner

10-23-2021, 08:15 AM #7

I don’t know which version was installed from the dump, only the dates.
Occasionally the installer gets updated to a new date, yet drivers still display old dates.
I wasn’t able to pinpoint the exact reason for the bugcheck issue, so I examined the Windows build you were using.
The bugcheck process took three hours. You might try enabling verifier.exe testing to speed it up.
If you do that, you could add the bootmode switch to stop a boot bugcheck loop.
For example:
verifier.exe /all /bootmode resetonbootfail
(you can also add /driver.exclued yourdrivername to skip certain drivers during testing.)
After testing, run verifier.exe /reset.
Your system may then run more slowly until you finish.
You can switch the memory dump type to kernel for more detailed debugging info. The resulting file is called memory.dmp and is significantly larger.
For further assistance, see:
https://learn.microsoft.com/en-us/window...mmand-line
This tool can reveal driver packages on your system.
https://github.com/lostindark/DriverStoreExplorer

_

_NeoBl0X_
Senior Member

635

10-23-2021, 07:29 PM

#8

I'm sorry, but I didn't grasp anything else but the part about drivers. My information came straight from the manufacturer's site. The verifier.exe and the Microsoft link didn't clarify anything further.

_

_NeoBl0X_

10-23-2021, 07:29 PM #8

I'm sorry, but I didn't grasp anything else but the part about drivers. My information came straight from the manufacturer's site. The verifier.exe and the Microsoft link didn't clarify anything further.

H

hoempapa21
Member

162

10-25-2021, 10:10 AM

#9

I acknowledge your concern and appreciate your caution. We're still working through this issue, and sometimes performance may temporarily affect stability. Please let us know if the system remains free from BSODs at 4800MHz during several game sessions. Your confirmation is crucial to ensure we reach a solid solution.

H

hoempapa21

10-25-2021, 10:10 AM #9

I acknowledge your concern and appreciate your caution. We're still working through this issue, and sometimes performance may temporarily affect stability. Please let us know if the system remains free from BSODs at 4800MHz during several game sessions. Your confirmation is crucial to ensure we reach a solid solution.

S

Sheep_VeNoM
Member

112

10-26-2021, 01:03 AM

#10

Thanks for the feedback.
I’ve been using a lot of games, but I kept trying to trigger BSOD by repeatedly pressing alt-tab to the browser. I’m sure this caused several crashes.
If my system is stable at 4800MHz, should I switch to an EXPO profile with a higher frequency range like 5600-5800MHz?

S

Sheep_VeNoM

10-26-2021, 01:03 AM #10

Thanks for the feedback.
I’ve been using a lot of games, but I kept trying to trigger BSOD by repeatedly pressing alt-tab to the browser. I’m sure this caused several crashes.
If my system is stable at 4800MHz, should I switch to an EXPO profile with a higher frequency range like 5600-5800MHz?

Pages (2): 1 2 Next