I built this computer just a few weeks ago, but had to work so couldn't game, when I first started gaming I immediately got an nvlddmkm crash even when low-ish graphics or cutscenes/opening scenes, though I don't get this when running benchmarks such as TimeSpy (2450ish score, better than 41%, whereas PC mark I had better than 81%, I did these benchmarks when I first completed the build, and again now, and nothing changed: they are both within normal range for the build when comparing to others' results). Computer appears to run perfectly otherwise. I reinstalled all NVidia drivers (though manually, not with DDU), replicated the issue on multiple games, tried everything in settings in multiple games, messed about with Power Settings on the PC, messed about with NVidia ControlPanel etc. I'm now worried it may be hardware.
Build:
CPU: i5 8600k
CPU Cooler: Cryorig H7
Motherboard: ASRock Z370 Pro4
Memory: Corsair Vengeance LPX 8G (DDR4-3600)
Storage: Crucial MX300 275GB 2.5" SSD (Windows installed)
Storage: Seagate BarraCuda 1TB 3.5" 7200RPM (Games installed)
GPU: Zotac - GeForce GTX 1060 6GB
Case: NZXT S340 Elite
PSU: Corsair RMx 550W 80+ Gold Certified Fully Modular
Case Fans: Corsair CO-9050016-BLED 52.2 CFM 120 mm blue led case fans.
Operating System: Windows 10
Monitor: Samsung S25HG50 144hz 1ms
The Corsair Vengeance 3600 I bought because it was the same price as lower ones, but I haven't overclocked anything so they are at 2133.
I have run TimeSpy without problems just now with HWMonitor on and got these readings (anything out of the ordinary?): https://imgur.com/a/F5WQV? Idle temperatures (like now) are normally around 27C for me, I just realised I didn't allow it to go idle when HWMonitor was on to take these readings.
These are the errors that I get in Eventviewer after a game inevitably crashes:
Error (Source: nvlddmkm, Event 13); General: The description for Event ID 13 from source nvlddmkm cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer. If the event originated on another computer, the display information had to be saved with the event. The following information was included with the event: \Device\UVMLiteProcess2 Graphics Exception: ESR 0x405840=0x82040200 the message resource is present but the message is not found in the string/message table
Same top text for the next three, but with these errors:
\Device\UVMLiteProcess2 Graphics Exception: Shader Program Header 18 \Device\UVMLiteProcess2 Graphics Exception: Shader Program Header 9 Error \Device\UVMLiteProcess2 Graphics Exception: ESR 0x405848=0x80000000
These are the latest errors and somewhat different from the original errors which were:
\Device\0000006f Graphics Exception: ESR 0x405848=0x80000000 \Device\Video3 Graphics Exception: ESR 0x405848=0x80000000 \Device\Video3 Graphics Exception: Shader Program Header 9 Error
while the initial errors were:
Display driver nvlddmkm stopped responding and has successfully recovered.
ALSO: I know messing with TDR settings in Windows may solve this, but only in the sense that it tries to make the system ignore the error; however I should not be getting the error in the first place: the same games e.g. run perfectly on the less powerful Ryzen 1600 build with same GPU that I built for my fiancée. So that's not a long term solution. Same thing with underclocking my GPU, as it's at factory clock I shouldn't nerf it. Advice very welcome, though!
NEXT STEPS:
-Run DDU in safe mode and uninstall reinstall drivers (windows seems to automatically reinstall them when on computer).
-Check whether the problem is the same with a non-144hz monitor, in case that causes it -Reinstall Windows
-If the above three steps fail, replace my graphics card with the identical one (1060 6GB) I recently used to build a Ryzen 5 1600 build for my fiancée and see whether the problem persists
-If so, weep, as my Amazon return window has closed for the GPU.
Submitted February 03, 2018 at 11:02PM by PCNewBuildProblem http://ift.tt/2GKOhA0
0 komentar:
Post a Comment