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): Previous 1 2
E
eastland97
Senior Member
644
10-26-2021, 02:05 AM
#11
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.
E
eastland97
10-26-2021, 02:05 AM #11

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.

K
Ks34_MisteR
Member
245
11-02-2021, 07:41 AM
#12
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.
K
Ks34_MisteR
11-02-2021, 07:41 AM #12

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.

Z
Zerstouerneun
Member
186
11-02-2021, 12:34 PM
#13
No tool can detect every RAM problem. Memtest86 gives a sense of security, but it doesn’t guarantee perfect results. Taking out one module confirms a fault.
Z
Zerstouerneun
11-02-2021, 12:34 PM #13

No tool can detect every RAM problem. Memtest86 gives a sense of security, but it doesn’t guarantee perfect results. Taking out one module confirms a fault.

R
redstoneur
Member
57
11-02-2021, 01:39 PM
#14
Currently I'm maintaining a speed of 5800 mt/s on day two, no BSOD or crashes, so far.
R
redstoneur
11-02-2021, 01:39 PM #14

Currently I'm maintaining a speed of 5800 mt/s on day two, no BSOD or crashes, so far.

T
TraPPkingOG
Member
70
11-15-2021, 01:59 AM
#15
Received reply from ASRock and they suggested specific adjustments:
Adjust processor ODT impedance to 60ohm using OC Tweaker/DRAM Configuration/DRAM Bus Control Configuration while EXPO profile is active
Raise SoC voltage to 1.25V
Activate SoC/Uncore OC mode via AMD Overclocking page
After retrying, system stabilized at 6000MHz; it functioned normally with tests that typically caused BSODs or crashes (though I suspect they did occur).
In the morning when attempting to power on, I encountered a POST failure, getting stuck on a green (yellow-green) indicator. The system displayed a BOOT error, pressed the restart button, and after several minutes it returned to green, though red and yellow lights flashed briefly before resuming. After restarting again, the same sequence occurred.
I assumed this might be a one-time glitch, so I powered off the PC and tried again—still facing the same issue. The recurring green light persisted, needing two restarts to clear.
From my research, many users experience this problem without knowing its cause. However, it seems this only began after applying the settings recommended by ASRock.
Perhaps someone can clarify what triggers this behavior? ASRock’s response usually takes a week or longer. 😀
T
TraPPkingOG
11-15-2021, 01:59 AM #15

Received reply from ASRock and they suggested specific adjustments:
Adjust processor ODT impedance to 60ohm using OC Tweaker/DRAM Configuration/DRAM Bus Control Configuration while EXPO profile is active
Raise SoC voltage to 1.25V
Activate SoC/Uncore OC mode via AMD Overclocking page
After retrying, system stabilized at 6000MHz; it functioned normally with tests that typically caused BSODs or crashes (though I suspect they did occur).
In the morning when attempting to power on, I encountered a POST failure, getting stuck on a green (yellow-green) indicator. The system displayed a BOOT error, pressed the restart button, and after several minutes it returned to green, though red and yellow lights flashed briefly before resuming. After restarting again, the same sequence occurred.
I assumed this might be a one-time glitch, so I powered off the PC and tried again—still facing the same issue. The recurring green light persisted, needing two restarts to clear.
From my research, many users experience this problem without knowing its cause. However, it seems this only began after applying the settings recommended by ASRock.
Perhaps someone can clarify what triggers this behavior? ASRock’s response usually takes a week or longer. 😀

D
DC24ZZ
Junior Member
13
11-16-2021, 06:19 PM
#16
You can determine if the unusual boot sequence is linked to those BIOS updates by resetting those values back to their original settings (or whatever they were before). If the strange boot problem disappears, then it was resolved.
D
DC24ZZ
11-16-2021, 06:19 PM #16

You can determine if the unusual boot sequence is linked to those BIOS updates by resetting those values back to their original settings (or whatever they were before). If the strange boot problem disappears, then it was resolved.

Pages (2): Previous 1 2