Well, it's my first time overclocking and I'm getting worried about my hardware and how it's BSODing.
I managed to OC my GTX 970 to +500MHz Memory and +210 Core, ran Benchmarking for a good, solid while with no crashes or artifacts.
Restarted, went into BIOS. Set up XMP for RAM so that it runs at 2133MHz now, and messed with the CPU (i5-4690k) just a tiny bit, nothing major, just a few drop box options and choosing "Performance Mode" on the ASRock A-Tuning.
Restarted, tried to play some Overwatch. All's fine and well until 45 seconds into the match. Screen goes one solid color, I get an error message from the .exe crashing. I thought to dial back my GPU OC, but then I got hit with a WHEA. I ran back into another WHEA after restarting and trying Prime95. Fantastic.
Restart again, hangs up on while opening a program, and now I get a CLOCK_WATCHDOG_TIMEOUT . Man, I don't feel like explaining the BSODs anymore.
During the two WHEA crashes, both hal.dll and ntoskrnl.exe failed. However, during the CLOCK error, ntsokrnl alone failed.
I figure it's my voltage going awry in the OC, but I did hear some reports about an MSI GTX 970 (my GPU) using these values with no added voltage.
I managed to OC my GTX 970 to +500MHz Memory and +210 Core, ran Benchmarking for a good, solid while with no crashes or artifacts.
Restarted, went into BIOS. Set up XMP for RAM so that it runs at 2133MHz now, and messed with the CPU (i5-4690k) just a tiny bit, nothing major, just a few drop box options and choosing "Performance Mode" on the ASRock A-Tuning.
Restarted, tried to play some Overwatch. All's fine and well until 45 seconds into the match. Screen goes one solid color, I get an error message from the .exe crashing. I thought to dial back my GPU OC, but then I got hit with a WHEA. I ran back into another WHEA after restarting and trying Prime95. Fantastic.
Restart again, hangs up on while opening a program, and now I get a CLOCK_WATCHDOG_TIMEOUT . Man, I don't feel like explaining the BSODs anymore.
During the two WHEA crashes, both hal.dll and ntoskrnl.exe failed. However, during the CLOCK error, ntsokrnl alone failed.
I figure it's my voltage going awry in the OC, but I did hear some reports about an MSI GTX 970 (my GPU) using these values with no added voltage.
Facebook
Twitter
Instagram