Question I get BSODs in various scenarios, but the cause is always the same ---> ntoskrnl.exe ?

[pickupmysoup]

Hey guys,
Having trouble lately, after building new PC. Getting BSODs mostly while alt-tabing from game to lets say browser. Not instantly, but after few minutes. I even got BSOD without playing games.
PC specs: 9800x3D, 64GB DDR5 RAM, PNY RTX 5080 OC, ASRock B850 Riptide WiFi. RM850x, Windows 11 Pro.
Did memtest86, so RAM is ok, tested CPU with Cinebench and OCCT, no errors or crashes, did OCCT VRAM test - no errors. Tried installing newest geforce driver 576.66 and uninstalling old with DDU.

BTW For a brief time, I had RTX 5080 in my old setup (5600x, 32GB DDR4, TUF B550-plus, RM850x, Windows 11 Pro) didn't recall getting any BSODs.

Also getting game crashes, mostly from KCD2, don't know if they are related but here is what Event viewer says:
The description for Event ID 153 from source nvlddmkm cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

\Device\Video3
Error occurred on GPUID: 100

The message resource is present but the message was not found in the message table


Going to put few .dmp files in Gdrive:
https://drive.google.com/file/d/1QLYWZ-yqgD7-RN0G8QYCDfaG6zq7-BMK/view?usp=drive_link

060525-7671-01.dmp

drive.google.com

https://drive.google.com/file/d/1us9KAM573aZaIU7Ed4r8oNJCh7vJM_kC/view?usp=sharing

Tried talking to Nvidia support, wrote message to ASRock and PNY. NVidia support is terrible, and still nothing from ASRock and PNY. So at this point I really don't know what to do.

 

[ubuysa]

The first thing I'd suggest is to remove the RAM overclock and see whether it's stable then. Your RAM is clocked at 6000MHz, which is it's maximum design speed, but that's still an overclock. Please remove all XMP profiles and run it at its SPD speed of 4800MHz.

Let us know how that goes.

 

[pickupmysoup]

The first thing I'd suggest is to remove the RAM overclock and see whether it's stable then. Your RAM is clocked at 6000MHz, which is it's maximum design speed, but that's still an overclock. Please remove all XMP profiles and run it at its SPD speed of 4800MHz.

Let us know how that goes.

Ok, RAM is at 4800mhz. But now, potentially reverting to stock speeds fixes BSODs, what them? Am I supposed to run my RAM like cheap **** [Moderator edit to remover profanity. Remember that this is a Family Friendly forum.] RAM and get worse performance basically at anything? This doesn't sound right.
Plus don't know when next BSOD will occur. It might be soon, it might not. Not always playing games 😀

 

[Ralston18]

Also look in Reliability History/Monitor for error codes, warnings, and even informational events that are being captured just before or at the time of the BSODs.

Reliability History/Monitor presents a timeline format that can reveal patterns.

Manually download drivers directly from the applicable manufacturer's website. Install and configure as required. No third party installers or tools.

Use "dism" and "sfc /scannow" to look for, find, and hopefully fix any corrupted or buggy files that may be involved.

 

[johnbl]

first fix attempt would be to update amd chipset driver to a version 7.01.08.129 or newer. motherboard website has a new version dated 4/15/2025. I would look at the list of drivers and check for other updates you might need. Start with the Chipset drivers.

looks like you updated the bios but failed to install the updated AMD chipset drivers:
https://pg.asrock.com/mb/AMD/B850 Riptide WiFi/index.asp#Download

your install is mostly generic with microsoft plug and play grabbing some old versions of drivers.
you might run the installer for the killer network driver. your driver is dated 4/15/2024 and the installer package for your motherboard is 11/25/2024. I would run the update package since this driver often has bugs/issues.

looks like windows installed three generic drivers for
arturiaminifuseusbaudio you might want to see if you can install the current custom drivers for your device.

RtUsbA64.sys Tue Jul 9 23:28:55 2024 looks like it was installed as a generic plug and play download. This is for a usb audio device, you might want to install the current drivers for the device directly.

this is a common overclock driver:
C:\Program Files (x86)\Kingston FURY\FuryCTRL_SDK\NTIOLib_X64.sys Tue Feb 20 23:00:49 2024

(are you using it for RBG light control? or actual overclocking? )



pretty old driver installed:

TrafficMonitor.sys Sat Jul 26 06:29:37 2008

path:
C:\Users\Ego\AppData\Local\Microsoft\WinGet\Packages\zhongyang219.TrafficMonitor.Full_Microsoft.Winget.Source_8wekyb3d8bbwe\TrafficMonitor\TrafficMonitor.sys Sat Jul 26 06:29:37 2008

8: kd> !sysinfo machineid
Machine ID Information [From Smbios 3.4, DMIVersion 0, Size=1925]
BiosMajorRelease = 5
BiosMinorRelease = 35
BiosVendor = American Megatrends International, LLC.
BiosVersion = 3.26
BiosReleaseDate = 05/16/2025
SystemManufacturer = ASRock
SystemProductName = B850 Riptide WiFi
BaseBoardManufacturer = ASRock
BaseBoardProduct = B850 Riptide WiFi

: kd> !sysinfo cpuinfo
[CPU Information]
~MHz = REG_DWORD 4691
_RESOURCE_DESCRIPTOR ff,ff,ff,ff,ff,ff,ff,ff,0,0,0,0,0,0,0,0
Identifier = REG_SZ AMD64 Family 26 Model 68 Stepping 0
ProcessorNameString = REG_SZ AMD Ryzen 7 9800X3D 8-Core Processor
Update Status = REG_DWORD 6
VendorIdentifier = REG_SZ AuthenticAMD

 

[pickupmysoup]

first fix attempt would be to update amd chipset driver to a version 7.01.08.129 or newer. motherboard website has a new version dated 4/15/2025. I would look at the list of drivers and check for other updates you might need. Start with the Chipset drivers.

looks like you updated the bios but failed to install the updated AMD chipset drivers:
https://pg.asrock.com/mb/AMD/B850 Riptide WiFi/index.asp#Download

your install is mostly generic with microsoft plug and play grabbing some old versions of drivers.


pretty old driver installed:

TrafficMonitor.sys Sat Jul 26 06:29:37 2008

path:
C:\Users\Ego\AppData\Local\Microsoft\WinGet\Packages\zhongyang219.TrafficMonitor.Full_Microsoft.Winget.Source_8wekyb3d8bbwe\TrafficMonitor\TrafficMonitor.sys Sat Jul 26 06:29:37 2008

8: kd> !sysinfo machineid
Machine ID Information [From Smbios 3.4, DMIVersion 0, Size=1925]
BiosMajorRelease = 5
BiosMinorRelease = 35
BiosVendor = American Megatrends International, LLC.
BiosVersion = 3.26
BiosReleaseDate = 05/16/2025
SystemManufacturer = ASRock
SystemProductName = B850 Riptide WiFi
BaseBoardManufacturer = ASRock
BaseBoardProduct = B850 Riptide WiFi

: kd> !sysinfo cpuinfo
[CPU Information]
~MHz = REG_DWORD 4691
_RESOURCE_DESCRIPTOR ff,ff,ff,ff,ff,ff,ff,ff,0,0,0,0,0,0,0,0
Identifier = REG_SZ AMD64 Family 26 Model 68 Stepping 0
ProcessorNameString = REG_SZ AMD Ryzen 7 9800X3D 8-Core Processor
Update Status = REG_DWORD 6
VendorIdentifier = REG_SZ AuthenticAMD

But I already installed newest chipset drivers. Ant that TrafficMonitor is a software to monitor network and internals. I mean I can install these drivers again, but I believe it won't make any difference

 

[johnbl]

But I already installed newest chipset drivers. Ant that TrafficMonitor is a software to monitor network and internals. I mean I can install these drivers again, but I believe it won't make any difference

I can not tell the version installed from the dump, just the dates.
Sometimes installer is updated to a new date and the drivers still have the old dates on them.
I could not determine the actual cause of the bugcheck, so I was just looking at the build of windows you were using.

the bugcheck took 3 hours. you might consider turning on verifier.exe testing to force the system to bugcheck faster.

if you do so, you might add the bootmode switch to prevent a boot bugcheck loop.
something like:
verifier.exe /all /bootmode resetonbootfail
(you can add /driver.exclued yourdrivername
to make verifier skip drivers from testing, useful since some drivers always fail testing but are not the cause of the problem you are looking for)

when done with testing run verifier.exe /reset
(or your system will run slowly until you do)

You can change the memory dump type to kernel to provide more debugging info. they dump file will be memory.dmp and is much larger.
https://learn.microsoft.com/en-us/windows-hardware/drivers/devtest/verifier-command-line

this tool can help show the driver packages on your system.
https://github.com/lostindark/DriverStoreExplorer

 

[pickupmysoup]

I can not tell the version installed from the dump, just the dates.
Sometimes installer is updated to a new date and the drivers still have the old dates on them.
I could not determine the actual cause of the bugcheck, so I was just looking at the build of windows you were using.

the bugcheck took 3 hours. you might consider turning on verifier.exe testing to force the system to bugcheck faster.

if you do so, you might add the bootmode switch to prevent a boot bugcheck loop.
something like:
verifier.exe /all /bootmode resetonbootfail
(you can add /driver.exclued yourdrivername
to make verifier skip drivers from testing, useful since some drivers always fail testing but are not the cause of the problem you are looking for)

when done with testing run verifier.exe /reset
(or your system will run slowly until you do)

You can change the memory dump type to kernel to provide more debugging info. they dump file will be memory.dmp and is much larger.
https://learn.microsoft.com/en-us/windows-hardware/drivers/devtest/verifier-command-line

this tool can help show the driver packages on your system.
https://github.com/lostindark/DriverStoreExplorer

I'm sorry, but I didn't understand anything you just said except for last bit about drivers, and mine came directly from manufacturers website.

But never even heard of that verifier.exe and that microsoft link didn't help to understand.

 

[ubuysa]

Ok, RAM is at 4800mhz. But now, potentially reverting to stock speeds fixes BSODs, what them? Am I supposed to run my RAM like cheap **** [Moderator edit to remover profanity. Remember that this is a Family Friendly forum.] RAM and get worse performance basically at anything? This doesn't sound right.
Plus don't know when next BSOD will occur. It might be soon, it might not. Not always playing games 😀

I understand your frustration, but please remember that we're troubleshooting here and that often means suffering a bit of performance degradation whilst we isolate the problem. We're not done yet.

That removing the RAM overclock seems to have stopped the BSODs is encouraging but I would like to be certain that they've stopped so that we don't go off down a rabbit hole. Can you let us know whether it stays free of BSODs at 4800MHz for a couple of game playing days? It is VERY important that we establish with certainty whether it's fully stable at 4800MHz, so please do have a little patience.

 

[pickupmysoup]

I understand your frustration, but please remember that we're troubleshooting here and that often means suffering a bit of performance degradation whilst we isolate the problem. We're not done yet.

That removing the RAM overclock seems to have stopped the BSODs is encouraging but I would like to be certain that they've stopped so that we don't go off down a rabbit hole. Can you let us know whether it stays free of BSODs at 4800MHz for a couple of game playing days? It is VERY important that we establish with certainty whether it's fully stable at 4800MHz, so please do have a little patience.

Thanks for encouraging reply 😊 Having been playing a lot, but still while playing I was trying to get BSOD as much as possible - alt-tab to browser, multiple times. I know for sure that this caused me few BSODs 😀
But lets say I have stable system at 4800MHz. Should I try EXPO profile but with 5600-5800MHz?

 

[ubuysa]

If you look at the spec for your AMD Ryzen 7 9800X3D and expand the Connectivity section, you'll see that the maximum guaranteed RAM speed that the CPU will tolerate is 5600MHz. Most CPUs will tolerate RAM speeds much higher than this, but there is no guarantee that they will be stable.

I suggest, as you say, that you try the 5600MHz XMP profile and test thoroughly to ensure that it's stable there.

If it is stable at 5600MHz then you can try increasing the XMP speed, in single steps, to find the highest RAM speed at which your system is stable.

If it's not stable at 5600MHz then remove one 32GB RAM stick and see whether it's stable at 5600MHz on just the one. (Ensure it's in the correct slot). Then swap RAM sticks and see whether it's stable at 5600MHz on the other stick.

If it's stable on one stick but not the other then RMA the RAM under warranty. RMA both sticks, you want a matched set.

If it's not stable on either stick then it's most likely the CPU and you'll need to talk to AMD about a warranty RMA.

 

[pickupmysoup]

If you look at the spec for your AMD Ryzen 7 9800X3D and expand the Connectivity section, you'll see that the maximum guaranteed RAM speed that the CPU will tolerate is 5600MHz. Most CPUs will tolerate RAM speeds much higher than this, but there is no guarantee that they will be stable.

I suggest, as you say, that you try the 5600MHz XMP profile and test thoroughly to ensure that it's stable there.

If it is stable at 5600MHz then you can try increasing the XMP speed, in single steps, to find the highest RAM speed at which your system is stable.

If it's not stable at 5600MHz then remove one 32GB RAM stick and see whether it's stable at 5600MHz on just the one. (Ensure it's in the correct slot). Then swap RAM sticks and see whether it's stable at 5600MHz on the other stick.

If it's stable on one stick but not the other then RMA the RAM under warranty. RMA both sticks, you want a matched set.

If it's not stable on either stick then it's most likely the CPU and you'll need to talk to AMD about a warranty RMA.

Thanks. But if there is something wrong with RAM, shouldn't be there an errors while doing memtest? Because I've done few and there were none.

 

[ubuysa]

No memory tester can ever find 100% of RAM issues. The results of Memtest86 is a confidence boost, not proof that the RAM is good. Removing one stick is proof positive of a RAM issue.

 

[pickupmysoup]

Right now I'm running at 5800 mt/s, second day, no BSOD, no game crashes, so far...

 

[pickupmysoup]

Got email back from ASRock and they told me to try these settings:

1. Set Processor ODT Impedance to 60ohm from OC Tweaker/ DRAM Configuration/ DRAM Bus Control Configuration while EXPO profile loaded
2. Increase SoC voltage to 1.25V
3. Enable SoC/ Uncore OC mode from AMD Overclocking page

Got back to 6000MHz, and system seemed to be fine, tested with things that usually caused BSODs or game crashes (at least I believe that they did), BUT....

In the morning when I tried to turn my PC on, I couldn't get through POST, got stuck on green (yellow-green) light - BOOT is dysfunctional, pressed restart button, then for few minutes red and yellow lights been flashing and again got stuck on green, after second time I pressed restart there were red and yellow lights flashing again, but I got through post.

I thought that maybe was one time system hiccup of some sorts, so I turned my PC off, then tried to turning it on again, and what do you expect? this green light thing all oven again, exactly the same, also required 2 restarts.

And as far as I researched this, many people get this bug, for unknown reasons. But for me this only started after I applied these settings recommended by ASRock.

Maybe someone can explain what causes this? ASRock replies takes like one week or even more 😀

 

[ubuysa]

You can prove whether or not the strange boot sequence is related to those BIOS changes by resetting those values to their defaults (or whatever they were before). If the strange boot sequence issue stops then that's what it was.

TBH if the system is stable with the RAM running at 5800MHz, as in post #14 then I would leave things alone. Remember, AMD only guarantee 5600MHz with that CPU...