------------------------------------------------------------------------------------------------------
***DESCRIPTION***
I've just moved from a 1080ti to a 3070 and I'm experiencing an issue ONLY during benchmarks. Game-wise, everything is smooth as butter; I have yet to find a game where it crashes. I tested the 3070 in my wife's PC, and the benchmarks finish without issue. I've also re-tested my 1080ti in my PC, and the benchmark runs fine.
I’ve checked the mini dumps and found that the crash is caused by an nvlddmkm.sys failure every time. Typical driver issue from what I have read. I’ve run DDU clean and restarted in safe mode. I freshly installed the latest Nvidia driver and even tried the previous version for good measure—no joy.
I've tried several other troubleshooting steps, but I’m lost as to whether this is a faulty card, conflicting software, or a dodgy driver. I’m hoping the community here might have some insights or suggestions for the root cause. Below is a detailed breakdown of the scenario, what I've tried, and all the relevant specs.
------------------------------------------------------------------------------------------------------
***SPECS***
Main PC:
- CPU: Ryzen 7 5800X
- GPU: Gigabyte RTX 3070 Gaming OC 8GB GDDR6 (rev 2.0)
- RAM: Corsair Dominator Platinum RGB 32 GB (4 x 8 GB) DDR4 3600 MHz
- Motherboard: MPG X570S CARBON MAX WIFI
- PSU: Seasonic Focus GX 850W
- OS: Windows 11 Pro
Test PC:
- CPU: Ryzen 5 5600X
- GPU: MSI GTX 1080 Ti GAMING X 11GB
- RAM: Corsair Vengeance 2x8GB 3200MHz - White
- Motherboard: ROG STRIX B550-A Gaming
- PSU: RM650 80 Plus Gold
- OS: Windows 11 Pro
------------------------------------------------------------------------------------------------------
***CRASHING SCENARIO***
Running 3D Mark Demo Steel Nomad Test
* Soon after the benchmark starts, the screen goes black as shown in this VIDEO. This is followed by an auto-reboot after 2 minutes. The minidump contains nvlddmkm.sys.
Running Benchmark Test on Unreal Engine Heaven
* This can vary, but it seems to black screen around scene 20, followed by a reboot after 2 minutes. (Max GPU temp 80 degrees, CPU 70)
Though I've only had the GPU for 24 hours, I've played Teardown on modded maps, a few other games, and COD to intensify the GPU load, but with no crashes so far.
------------------------------------------------------------------------------------------------------
***WHAT I'VE TRIED***
- Ran DDU clean and restarted in safe mode, clean installed the latest Nvidia driver, and also tried the previous version (with WIFI OFF).
- Checked the BIOS; PCIE is set to Auto, manually set to Gen4 for testing.
- Disabled Nvidia Container LS, enabled Low Latency Mode.
- Yet to flash Windows 11 on a drive to test.
- Confirmed it works on another machine, and the former GPU can run a benchmark as well.
- No overclocking.
Mini toolkit output
------------------------------------------------------------------------------------------------------
***CONCLUSION***
Given the steps I’ve taken and the comparison between different PCs, I’m leaning towards this being a firmware/software issue. However, I’m not entirely sure how to prove or resolve this.
I would appreciate any suggestions. If anyone has experienced something similar or has any advice, it would be greatly appreciated!
Thanks in advance for your help!
***DESCRIPTION***
I've just moved from a 1080ti to a 3070 and I'm experiencing an issue ONLY during benchmarks. Game-wise, everything is smooth as butter; I have yet to find a game where it crashes. I tested the 3070 in my wife's PC, and the benchmarks finish without issue. I've also re-tested my 1080ti in my PC, and the benchmark runs fine.
I’ve checked the mini dumps and found that the crash is caused by an nvlddmkm.sys failure every time. Typical driver issue from what I have read. I’ve run DDU clean and restarted in safe mode. I freshly installed the latest Nvidia driver and even tried the previous version for good measure—no joy.
I've tried several other troubleshooting steps, but I’m lost as to whether this is a faulty card, conflicting software, or a dodgy driver. I’m hoping the community here might have some insights or suggestions for the root cause. Below is a detailed breakdown of the scenario, what I've tried, and all the relevant specs.
------------------------------------------------------------------------------------------------------
***SPECS***
Main PC:
- CPU: Ryzen 7 5800X
- GPU: Gigabyte RTX 3070 Gaming OC 8GB GDDR6 (rev 2.0)
- RAM: Corsair Dominator Platinum RGB 32 GB (4 x 8 GB) DDR4 3600 MHz
- Motherboard: MPG X570S CARBON MAX WIFI
- PSU: Seasonic Focus GX 850W
- OS: Windows 11 Pro
Test PC:
- CPU: Ryzen 5 5600X
- GPU: MSI GTX 1080 Ti GAMING X 11GB
- RAM: Corsair Vengeance 2x8GB 3200MHz - White
- Motherboard: ROG STRIX B550-A Gaming
- PSU: RM650 80 Plus Gold
- OS: Windows 11 Pro
------------------------------------------------------------------------------------------------------
***CRASHING SCENARIO***
Running 3D Mark Demo Steel Nomad Test
* Soon after the benchmark starts, the screen goes black as shown in this VIDEO. This is followed by an auto-reboot after 2 minutes. The minidump contains nvlddmkm.sys.
Running Benchmark Test on Unreal Engine Heaven
* This can vary, but it seems to black screen around scene 20, followed by a reboot after 2 minutes. (Max GPU temp 80 degrees, CPU 70)
Though I've only had the GPU for 24 hours, I've played Teardown on modded maps, a few other games, and COD to intensify the GPU load, but with no crashes so far.
------------------------------------------------------------------------------------------------------
***WHAT I'VE TRIED***
- Ran DDU clean and restarted in safe mode, clean installed the latest Nvidia driver, and also tried the previous version (with WIFI OFF).
- Checked the BIOS; PCIE is set to Auto, manually set to Gen4 for testing.
- Disabled Nvidia Container LS, enabled Low Latency Mode.
- Yet to flash Windows 11 on a drive to test.
- Confirmed it works on another machine, and the former GPU can run a benchmark as well.
- No overclocking.
Mini toolkit output
------------------------------------------------------------------------------------------------------
***CONCLUSION***
Given the steps I’ve taken and the comparison between different PCs, I’m leaning towards this being a firmware/software issue. However, I’m not entirely sure how to prove or resolve this.
I would appreciate any suggestions. If anyone has experienced something similar or has any advice, it would be greatly appreciated!
Thanks in advance for your help!