F5F Stay Refreshed Hardware Desktop Error message indicates a persistent issue, preventing gameplay beyond 30 minutes.

Error message indicates a persistent issue, preventing gameplay beyond 30 minutes.

Error message indicates a persistent issue, preventing gameplay beyond 30 minutes.

Pages (2): Previous 1 2
E
Ender_Craft47
Posting Freak
866
05-23-2025, 09:31 PM
#11
It seems stable on these tests, but could a motherboard or component problem be the cause?
E
Ender_Craft47
05-23-2025, 09:31 PM #11

It seems stable on these tests, but could a motherboard or component problem be the cause?

V
Velizar06
Posting Freak
865
05-23-2025, 09:31 PM
#12
V
Velizar06
05-23-2025, 09:31 PM #12

A
AKC03
Junior Member
49
05-23-2025, 09:31 PM
#13
No, I don't use a PCIe riser cable.
A
AKC03
05-23-2025, 09:31 PM #13

No, I don't use a PCIe riser cable.

L
lSticKl
Member
211
05-23-2025, 09:31 PM
#14
Sorry to hear you're facing this problem. It seems like the issue might be related to the PCIe slot or BIOS settings rather than the CPU or RAM. You've already considered those, which is good. Disabling resizable BAR and switching from PCIe 4 to PCIe 3 could help identify the root cause. This situation can definitely be frustrating, but you're on the right track by checking these areas.
L
lSticKl
05-23-2025, 09:31 PM #14

Sorry to hear you're facing this problem. It seems like the issue might be related to the PCIe slot or BIOS settings rather than the CPU or RAM. You've already considered those, which is good. Disabling resizable BAR and switching from PCIe 4 to PCIe 3 could help identify the root cause. This situation can definitely be frustrating, but you're on the right track by checking these areas.

A
Aleshop777
Member
153
05-23-2025, 09:31 PM
#15
The GPU is connected straight to the single PCIe port on the motherboard. I've learned that using riser cables might lead to the nvlddmkm 153 error.
A
Aleshop777
05-23-2025, 09:31 PM #15

The GPU is connected straight to the single PCIe port on the motherboard. I've learned that using riser cables might lead to the nvlddmkm 153 error.

G
GK_Wolves_15
Member
161
05-23-2025, 09:31 PM
#16
I believe I’m running out of fresh angles for this. I came across a Reddit discussion that might be relevant—seems others are facing similar challenges with various causes and possible fixes.
G
GK_Wolves_15
05-23-2025, 09:31 PM #16

I believe I’m running out of fresh angles for this. I came across a Reddit discussion that might be relevant—seems others are facing similar challenges with various causes and possible fixes.

S
SkyInsane
Senior Member
718
05-23-2025, 09:31 PM
#17
Thanks. I ran into this reddit thread, and it seems like some people spend months trying to figure out what is going on. I did some more digging and found out about Latency Monitor. I enabled Low Latency mode in the Nvidia Control Panel and then set the Power Plan to Maximum Performance. Booted up Marvel Rivals, and for the first time in a week I was able to play two full matches. Then I booted up Overwatch 2, and I was able to play one match before crashing. The weird thing is, the Event Viewer didn't return any nvlddmkm errors. Not sure if this is an Event Viewer bug or something else. The system appears a bit more stable now, but I haven't tested many games yet to confirm this.
S
SkyInsane
05-23-2025, 09:31 PM #17

Thanks. I ran into this reddit thread, and it seems like some people spend months trying to figure out what is going on. I did some more digging and found out about Latency Monitor. I enabled Low Latency mode in the Nvidia Control Panel and then set the Power Plan to Maximum Performance. Booted up Marvel Rivals, and for the first time in a week I was able to play two full matches. Then I booted up Overwatch 2, and I was able to play one match before crashing. The weird thing is, the Event Viewer didn't return any nvlddmkm errors. Not sure if this is an Event Viewer bug or something else. The system appears a bit more stable now, but I haven't tested many games yet to confirm this.

B
BooyaLuver19
Member
77
05-23-2025, 09:31 PM
#18
I switched back to 566.14 and everything worked fine for me rtx 4070 ti super 9800x3d windows 10 ent 22H2
B
BooyaLuver19
05-23-2025, 09:31 PM #18

I switched back to 566.14 and everything worked fine for me rtx 4070 ti super 9800x3d windows 10 ent 22H2

Pages (2): Previous 1 2