F5F Stay Refreshed Hardware Desktop BSOD has occurred after installing the 582.83 drivers several months back.

BSOD has occurred after installing the 582.83 drivers several months back.

BSOD has occurred after installing the 582.83 drivers several months back.

T
The8BITBURGER
Junior Member
9
10-21-2025, 09:14 AM
#1
Hey everyone,
PC Specifications;
CPU: Ryzen 7 9700x
Motherboard: AsRock X870 Pro RS WiFi
RAM: 32GB Corair 5200mHz (XMP) (2x 16GB)
GPU: ASUS Prime 5080
Power Supply: Lian-Li Edge 1000W (new, 4 months)
SSDs: 1TB Crucial P3 Gen4 drive, 4TB WD Black Gen4 drive (both not nearly full. 1tb has 700GB free, 4TB has 2TB free. Both are brand new and only installed recently)
Wired network
Peripherals;
-Writing 80HE keyboard
- Logitech G Pro Superlight Mouse
- Logitech G Pro Wireless Headset
- Elgato Stream Deck (Neo)
- 2 monitors, 1 monitor with 144hz Gsync VA Panel (via DisplayPort), 1 monitor with 60hz IPS panel (via HDMI)
I’m unsure what to do. I’ve been experiencing problems for months. After installing the 572.83 drivers initially, I started seeing inconsistent crashes and full BSODs without clear reasons. Occasionally I play games or just use my desktop, but sometimes it’s a complete failure. I’ve swapped out most components temporarily to test, yet the issue persists. I’ve also reused several drives, reinstalled Windows, and updated drivers, but it still happens. Occasionally I manage a week without any crashes, though other problems appear. Some friends with similar 5080 models report higher frame rates (80fps in CS2, 60fps in Space Marine 2) compared to mine.
Is this a recognized problem? I recall Gamers Nexus mentioning permanent GPU damage in a video about the problematic driver.
I’d like to know if I can file a warranty claim with the seller or if there’s a known fix I’m missing.
Any advice would be greatly appreciated.
Thanks to all.
Side note: I have a BSOD viewer and can share error codes if needed, but they mostly point to ntoskrnl.exe and ntoskrnl.exe+5017d0.
T
The8BITBURGER
10-21-2025, 09:14 AM #1

Hey everyone,
PC Specifications;
CPU: Ryzen 7 9700x
Motherboard: AsRock X870 Pro RS WiFi
RAM: 32GB Corair 5200mHz (XMP) (2x 16GB)
GPU: ASUS Prime 5080
Power Supply: Lian-Li Edge 1000W (new, 4 months)
SSDs: 1TB Crucial P3 Gen4 drive, 4TB WD Black Gen4 drive (both not nearly full. 1tb has 700GB free, 4TB has 2TB free. Both are brand new and only installed recently)
Wired network
Peripherals;
-Writing 80HE keyboard
- Logitech G Pro Superlight Mouse
- Logitech G Pro Wireless Headset
- Elgato Stream Deck (Neo)
- 2 monitors, 1 monitor with 144hz Gsync VA Panel (via DisplayPort), 1 monitor with 60hz IPS panel (via HDMI)
I’m unsure what to do. I’ve been experiencing problems for months. After installing the 572.83 drivers initially, I started seeing inconsistent crashes and full BSODs without clear reasons. Occasionally I play games or just use my desktop, but sometimes it’s a complete failure. I’ve swapped out most components temporarily to test, yet the issue persists. I’ve also reused several drives, reinstalled Windows, and updated drivers, but it still happens. Occasionally I manage a week without any crashes, though other problems appear. Some friends with similar 5080 models report higher frame rates (80fps in CS2, 60fps in Space Marine 2) compared to mine.
Is this a recognized problem? I recall Gamers Nexus mentioning permanent GPU damage in a video about the problematic driver.
I’d like to know if I can file a warranty claim with the seller or if there’s a known fix I’m missing.
Any advice would be greatly appreciated.
Thanks to all.
Side note: I have a BSOD viewer and can share error codes if needed, but they mostly point to ntoskrnl.exe and ntoskrnl.exe+5017d0.

H
Hydroforce33
Senior Member
550
10-21-2025, 09:14 AM
#2
Update your post with complete hardware details and operating system information. Provide the power supply specifications, including voltage, amperage, age, and condition (original, build, refurbished, used). List the disk drive specifications such as make, model, and capacity, along with current usage. Include a description of all connected peripherals. Specify whether the network connection is wired or wireless.
H
Hydroforce33
10-21-2025, 09:14 AM #2

Update your post with complete hardware details and operating system information. Provide the power supply specifications, including voltage, amperage, age, and condition (original, build, refurbished, used). List the disk drive specifications such as make, model, and capacity, along with current usage. Include a description of all connected peripherals. Specify whether the network connection is wired or wireless.

D
Denaos5208
Member
68
10-21-2025, 09:14 AM
#3
Thank you, Ive updated it now
D
Denaos5208
10-21-2025, 09:14 AM #3

Thank you, Ive updated it now

M
mollytom
Junior Member
28
10-21-2025, 09:14 AM
#4
Check Reliability History/Monitor and Event Viewer for any error codes, alerts, or informational events recorded just before or during the BSODs. Look for references to ntoskrnl or other possible causes.
Drivers: Install drivers directly from the manufacturer's official site. Perform your own setup and configuration. (Avoid third-party tools.)
Ensure the driver source website is genuinely from the relevant manufacturer. A name in the URL doesn't guarantee authenticity.
= = = =
Run "dism" and "sfc /scannow".
These utilities can detect and fix corrupted or faulty files.
https://www.windowscentral.com/how-use-d...s-10-image
https://www.lifewire.com/how-to-use-sfc-...es-2626161
M
mollytom
10-21-2025, 09:14 AM #4

Check Reliability History/Monitor and Event Viewer for any error codes, alerts, or informational events recorded just before or during the BSODs. Look for references to ntoskrnl or other possible causes.
Drivers: Install drivers directly from the manufacturer's official site. Perform your own setup and configuration. (Avoid third-party tools.)
Ensure the driver source website is genuinely from the relevant manufacturer. A name in the URL doesn't guarantee authenticity.
= = = =
Run "dism" and "sfc /scannow".
These utilities can detect and fix corrupted or faulty files.
https://www.windowscentral.com/how-use-d...s-10-image
https://www.lifewire.com/how-to-use-sfc-...es-2626161