This is an automated archive.
The original was posted on /r/overclocking by /u/SNaCNE on 2023-08-31 21:01:23+00:00.
For the past day or so, I have been fine tuning my OC profile in MSI Afterburner using a combination of MSI Kombustor and Heaven Benchmark.
I found the sweet spot of a 100Mhz core clock and 900Mhz memory clock with max voltage and power that keeps temps below 80°C and has no artifacts or crashing in either Kombustor or Heaven and my games also reflect this.
However when I went to run stress tests and benchmarks in 3DMark, things started to go very wrong.
Anything besides the base Fire Strike benchmark and stress test would result in graphical artifacts and then a crash in the first five to 10 minutes or an error code while overclocking with Afterburner, usually the first instant the program is run with some exceptions. Resetting the core clock to zero fixes this.
I’ve run the following steps of troubleshooting based on google searches of my problem, leading me to several public threads on Reddit, 3DMark’s support pages and forums as well as their Steam pages, and several YouTube videos to fix my issue to no avail.
- Reinstalling graphics drivers with DDU in safe mode
- Resetting NVidia Control Panel settings
- Updating Motherboard BIOS and other drivers
- Using “sfc /scannow” in elevated command prompt
- Going into the Registry Editor and resetting some settings
- Checking DirectX version with DxDiag
- Updating Windows
- Making sure any programs are not running in the background that will affect the test
- Making sure the XMP profile is running
Since this problem is only contained to 3DMark and everything else is running perfectly fine to my knowledge, what should I do in this situation? Should I continue troubleshooting with 3DMark or leave things as is? Is this a sign of a larger problem with my GPU as I’ve owned it now for four years as of this September and should I be worried?
I’ve also attached a zipped folder containing all the benchmarks I’ve run using my OC profile as well as my DxDiag file containing my computer’s specs and the NVidia Control Panel settings that I use, in case anybody requires them to analyze my issue (Note: you’ll need 3DMark to see the benchmarks that I ran using 3DMark).
Edit: Ran 3DMark a few more times, this time opening Windows Event Viewer after every crash and recording all the errors, warnings and other messages that were thrown at that point in time. First the display driver nvlddmkm stops responding and Windows ends it automatically. This causes D3DDRED to stop working and a Live Kernal Event happens causing the crash. After the crash, nvlddmkm reboots successfully.