F5F Stay Refreshed Hardware Desktop Error occurs when PC is powered down and linked to XMP storage.

Error occurs when PC is powered down and linked to XMP storage.

Error occurs when PC is powered down and linked to XMP storage.

C
147
02-17-2018, 01:07 PM
#1
Good evening, sir. I see you have a few observations to share. First, I do have a workaround, so this isn’t a high-priority concern. However, it still puzzles me as I try to figure out why this occurs. When I put my PC to sleep and then restart it, I often encounter BSODs. Even after a full reboot, these crashes continue. Here’s what I’ve noticed:

1. Removing one of the two memory sticks from the motherboard makes the system stable again, but adding the second stick brings it back to BSODs.
2. Running without XMP settings (using two sticks) works smoothly.
3. Disabling and then re-enabling XMP also results in stable operation.

As a result, I disabled automatic sleep on my PC recently. I forgot about these settings and put it to sleep manually, hoping it would highlight the problem. While I don’t mind the issue much, understanding its root cause is important. It seems memory might be the culprit. I ran a memory test (memtest) during the incident, and it flagged something incorrect, yet the system worked when I stopped sleeping.

My rig specs are: AMD X470 AORUS Trident Z RGB DDR4-3200MHz CL16-18-18-38, 16GB (2x8GB), 2nd Gen Ryzen™ 7 2700X.
C
CadentAlphadog
02-17-2018, 01:07 PM #1

Good evening, sir. I see you have a few observations to share. First, I do have a workaround, so this isn’t a high-priority concern. However, it still puzzles me as I try to figure out why this occurs. When I put my PC to sleep and then restart it, I often encounter BSODs. Even after a full reboot, these crashes continue. Here’s what I’ve noticed:

1. Removing one of the two memory sticks from the motherboard makes the system stable again, but adding the second stick brings it back to BSODs.
2. Running without XMP settings (using two sticks) works smoothly.
3. Disabling and then re-enabling XMP also results in stable operation.

As a result, I disabled automatic sleep on my PC recently. I forgot about these settings and put it to sleep manually, hoping it would highlight the problem. While I don’t mind the issue much, understanding its root cause is important. It seems memory might be the culprit. I ran a memory test (memtest) during the incident, and it flagged something incorrect, yet the system worked when I stopped sleeping.

My rig specs are: AMD X470 AORUS Trident Z RGB DDR4-3200MHz CL16-18-18-38, 16GB (2x8GB), 2nd Gen Ryzen™ 7 2700X.

D
damojosh
Member
200
02-19-2018, 07:19 AM
#2
The system is displaying blue screen of death errors.
D
damojosh
02-19-2018, 07:19 AM #2

The system is displaying blue screen of death errors.

R
RTz_Ribruti
Junior Member
1
02-19-2018, 10:09 AM
#3
Two BSODs occurred before implementing a workaround. The memory server was previously affected too. A driver attempted to access an invalid page at an interrupt level, likely due to incorrect addresses. If a kernel debugger is available, obtain a stack trace. Key details: the exception code was 0x80000003, which often points to a hard-coded breakpoint or assertion. Keep track of this address and the driver image release date. Common issues involve this exception code, and it usually indicates a problem in the boot process or driver handling. Ensure a debugger is connected and debugging mode is enabled to diagnose the cause.
R
RTz_Ribruti
02-19-2018, 10:09 AM #3

Two BSODs occurred before implementing a workaround. The memory server was previously affected too. A driver attempted to access an invalid page at an interrupt level, likely due to incorrect addresses. If a kernel debugger is available, obtain a stack trace. Key details: the exception code was 0x80000003, which often points to a hard-coded breakpoint or assertion. Keep track of this address and the driver image release date. Common issues involve this exception code, and it usually indicates a problem in the boot process or driver handling. Ensure a debugger is connected and debugging mode is enabled to diagnose the cause.

M
MarPs
Member
126
02-19-2018, 11:15 AM
#4
I also had a driver_irql installed on my PC, and it became clear that my BIOS wasn<|pad|>, not supplying sufficient voltage for my RAM (1.2V versus the required 1.35V). Perhaps verify the recommended voltage for your RAM and confirm it receives adequate power. Have you attempted using the Windows memory diagnostic tool?
M
MarPs
02-19-2018, 11:15 AM #4

I also had a driver_irql installed on my PC, and it became clear that my BIOS wasn<|pad|>, not supplying sufficient voltage for my RAM (1.2V versus the required 1.35V). Perhaps verify the recommended voltage for your RAM and confirm it receives adequate power. Have you attempted using the Windows memory diagnostic tool?

B
BunnyFucker
Member
172
02-20-2018, 06:25 AM
#5
I'm working with an XMP profile that sets the voltage to 1.35V. I ran memtest and it reported problems only after putting the PC to sleep. Once I reset the XMP profile, testing passed. More details: After clearing CMOS and reloading it from the drive, the issue persisted. To resolve it, I had to disable XMP profile boot in BIOS, shut down, restart, and then re-enable it.
B
BunnyFucker
02-20-2018, 06:25 AM #5

I'm working with an XMP profile that sets the voltage to 1.35V. I ran memtest and it reported problems only after putting the PC to sleep. Once I reset the XMP profile, testing passed. More details: After clearing CMOS and reloading it from the drive, the issue persisted. To resolve it, I had to disable XMP profile boot in BIOS, shut down, restart, and then re-enable it.

S
Stealsz
Member
126
02-20-2018, 12:40 PM
#6
Perhaps a glitch is affecting your BIOS while the computer is in sleep mode. It might help to turn off fast startup if you haven't already, as this can lead to problems on certain systems. https://help.uaudio.com/hc/en-us/article...Windows-10
S
Stealsz
02-20-2018, 12:40 PM #6

Perhaps a glitch is affecting your BIOS while the computer is in sleep mode. It might help to turn off fast startup if you haven't already, as this can lead to problems on certain systems. https://help.uaudio.com/hc/en-us/article...Windows-10

M
MrCm
Senior Member
636
02-21-2018, 12:15 PM
#7
I've already attempted that too. I kept it turned off because it's simpler to access BIOS without it.
M
MrCm
02-21-2018, 12:15 PM #7

I've already attempted that too. I kept it turned off because it's simpler to access BIOS without it.

J
JaSoN_Z
Member
58
02-22-2018, 05:16 PM
#8
Well then, I'm not sure what to do. I've tried everything I know to solve similar issues before. This one seems to need someone with more technical skills than me. Thanks for understanding—I can't assist further.
J
JaSoN_Z
02-22-2018, 05:16 PM #8

Well then, I'm not sure what to do. I've tried everything I know to solve similar issues before. This one seems to need someone with more technical skills than me. Thanks for understanding—I can't assist further.

Z
zPrisonPvP
Member
62
02-24-2018, 10:41 AM
#9
Thanks for your patience. I’m not a specialist, but I think I’ve handled this before. Don’t stress too much—just make sure my PC isn’t resting too much. As long as I’m running, everything seems okay. More important than fixing it is understanding why it happened. Could be a BIOS issue or something with the RAM connections? It’s strange, but removing one component and the system works even when it sleeps. Maybe the memory controller is the culprit?
Z
zPrisonPvP
02-24-2018, 10:41 AM #9

Thanks for your patience. I’m not a specialist, but I think I’ve handled this before. Don’t stress too much—just make sure my PC isn’t resting too much. As long as I’m running, everything seems okay. More important than fixing it is understanding why it happened. Could be a BIOS issue or something with the RAM connections? It’s strange, but removing one component and the system works even when it sleeps. Maybe the memory controller is the culprit?

G
GGoGGio_
Junior Member
6
02-24-2018, 12:54 PM
#10
TL;DR; The fix involved lowering the RAM voltage to 1.31V and VTT to 0.655V. After some trial and error, I found the issue by adjusting voltage slightly and observed stability at 3066 MHz. Eventually, setting VDD to 1.34V worked perfectly. The problem seemed linked to VRM issues on the X470 AORUS motherboard.
G
GGoGGio_
02-24-2018, 12:54 PM #10

TL;DR; The fix involved lowering the RAM voltage to 1.31V and VTT to 0.655V. After some trial and error, I found the issue by adjusting voltage slightly and observed stability at 3066 MHz. Eventually, setting VDD to 1.34V worked perfectly. The problem seemed linked to VRM issues on the X470 AORUS motherboard.