F5F Stay Refreshed Hardware Desktop Problem with driver BSOD since installing the 582.83 drivers several months back

Problem with driver BSOD since installing the 582.83 drivers several months back

Problem with driver BSOD since installing the 582.83 drivers several months back

Pages (2): 1 2 Next
E
entech
Member
210
02-15-2016, 12:27 PM
#1
Hey everyone, I'm dealing with the ASUS Prime 5080 and have been facing some frustrating problems for months. After installing the 572.83 drivers initially, I've noticed inconsistent crashes and BSODs without clear reasons. It varies depending on whether I'm playing a game or just browsing. I've tried swapping out components temporarily, reinstalling Windows, and updating drivers, but the issue persists. I've also had friends with similar setups experiencing high frame rates in some games versus lower ones in others. I recall hearing about potential permanent GPU damage from Gamers Nexus in a video discussing the problematic driver. Do you think I should file a warranty claim with the manufacturer? Are there any fixes I'm missing out on? Any advice would be really helpful. Thanks!
E
entech
02-15-2016, 12:27 PM #1

Hey everyone, I'm dealing with the ASUS Prime 5080 and have been facing some frustrating problems for months. After installing the 572.83 drivers initially, I've noticed inconsistent crashes and BSODs without clear reasons. It varies depending on whether I'm playing a game or just browsing. I've tried swapping out components temporarily, reinstalling Windows, and updating drivers, but the issue persists. I've also had friends with similar setups experiencing high frame rates in some games versus lower ones in others. I recall hearing about potential permanent GPU damage from Gamers Nexus in a video discussing the problematic driver. Do you think I should file a warranty claim with the manufacturer? Are there any fixes I'm missing out on? Any advice would be really helpful. Thanks!

_
_VeKoRiS_
Junior Member
4
02-19-2016, 05:07 AM
#2
You haven't changed the driver setting anywhere?
_
_VeKoRiS_
02-19-2016, 05:07 AM #2

You haven't changed the driver setting anywhere?

T
Tijeyd
Member
189
02-19-2016, 09:52 AM
#3
Hi Smile, At first I encountered problems with the driver, so I went back to the last known working version, which was December 2024 (sorry, I can't recall the exact number). After that, I rolled back to that driver and haven't used the 572.83 version since. I waited for the next update that addressed the issues with 572.83, but no matter which driver I tried, the same problems persisted from that driver. Right now, I'm using the latest release from Nvidia.
T
Tijeyd
02-19-2016, 09:52 AM #3

Hi Smile, At first I encountered problems with the driver, so I went back to the last known working version, which was December 2024 (sorry, I can't recall the exact number). After that, I rolled back to that driver and haven't used the 572.83 version since. I waited for the next update that addressed the issues with 572.83, but no matter which driver I tried, the same problems persisted from that driver. Right now, I'm using the latest release from Nvidia.

J
John_Scarce
Junior Member
45
02-26-2016, 01:04 PM
#4
Yes, the older driver is still operational and effective in its current role.
J
John_Scarce
02-26-2016, 01:04 PM #4

Yes, the older driver is still operational and effective in its current role.

_
_LilacSoul
Member
183
02-26-2016, 01:34 PM
#5
_
_LilacSoul
02-26-2016, 01:34 PM #5

R
Redstoner137
Posting Freak
811
02-26-2016, 02:36 PM
#6
The initial stable driver from 2024 also didn’t work afterward. It seems the problem might not be with the GPU, but possibly with RAM, since the BSOD isn’t linked to GPU usage. What’s the current RAM setting?
R
Redstoner137
02-26-2016, 02:36 PM #6

The initial stable driver from 2024 also didn’t work afterward. It seems the problem might not be with the GPU, but possibly with RAM, since the BSOD isn’t linked to GPU usage. What’s the current RAM setting?

A
acekiller990
Member
70
03-17-2016, 07:15 AM
#7
RAM is a 32GB Corsair 5200mHz (XMP profiled). I ran memtest and it reported no problems, but that doesn't always cover everything. It's worth mentioning I used this RAM before installing the 572.83 driver and had no issues then. I'm not trying to say it wasn't my RAM, and I appreciate your help. There haven't been any clear signs pointing to my specific unit. The errors I see—ntoskrnl.exe and ntoskrnl.exe+5017d0—don't seem to be linked to GPU drivers, though that's not confirmed. People online usually connect those issues to graphics card drivers, but it's not a definitive conclusion.
A
acekiller990
03-17-2016, 07:15 AM #7

RAM is a 32GB Corsair 5200mHz (XMP profiled). I ran memtest and it reported no problems, but that doesn't always cover everything. It's worth mentioning I used this RAM before installing the 572.83 driver and had no issues then. I'm not trying to say it wasn't my RAM, and I appreciate your help. There haven't been any clear signs pointing to my specific unit. The errors I see—ntoskrnl.exe and ntoskrnl.exe+5017d0—don't seem to be linked to GPU drivers, though that's not confirmed. People online usually connect those issues to graphics card drivers, but it's not a definitive conclusion.

M
mart1994
Junior Member
46
03-17-2016, 07:58 AM
#8
Just skip the RAM and check if the issue resolves on its own without running any tests
M
mart1994
03-17-2016, 07:58 AM #8

Just skip the RAM and check if the issue resolves on its own without running any tests

N
nightwolfcl
Junior Member
39
04-08-2016, 02:21 AM
#9
Are there any diagnostics you can run to check RAM or GPU performance? These tests might help identify the cause of your issue. Your situation is unclear, so any guidance on running such checks would be very useful.
N
nightwolfcl
04-08-2016, 02:21 AM #9

Are there any diagnostics you can run to check RAM or GPU performance? These tests might help identify the cause of your issue. Your situation is unclear, so any guidance on running such checks would be very useful.

S
Surplefosh
Member
57
04-09-2016, 01:40 PM
#10
Start by halting the overclocking when the system crashes. If that doesn’t help, take out one RAM module and test it with just one stick. Check each stick separately to determine which provides better stability.
S
Surplefosh
04-09-2016, 01:40 PM #10

Start by halting the overclocking when the system crashes. If that doesn’t help, take out one RAM module and test it with just one stick. Check each stick separately to determine which provides better stability.

Pages (2): 1 2 Next