[SOLVED] New build, random BSOD in Overwatch 2, then consistent BSODs in OCCT ?

Lairiak

Reputable
May 31, 2020
10
0
4,510
Firstly I apologize if this is in the wrong section of the forums, but I'm posting here because I was getting OCCT errors.

I've recently built a new rig, like literally 4 days ago. Specs are:

GPU: RTX 4070
CPU: Ryzen 7 7700x
CPU Cooler: NZXT Kraken Z73
RAM: G.Skill Trident Neo 32GB 6000MHz 2x16
MOBO: ASUS B650-E F Gaming Wifi
CASE: NZXT H9 Flow
SSDs: 2TB Samsung 980 PRO w/Heatsink, 250GB Samsung 960 Evo
HDD: some 2tb toshiba hdd
PSU: Corsair RM850x

To add a few things, I'm normally running with Eco Mode enabled in the BIOS, with EXPO Profile 1. The only other thing I've changed is fan curves. That is it. I also transferred my C: drive from an old rig with different hardware(2060 super, 3600x, b450 tomahawk, 32gb 3200 mhz corsair ram 4x8 running at 3000 mhz). I did not reinstall windows as it was running fine without it. I'm aware it may be an issue here, but I'm waiting in case anyone possibly has other solutions.

Today, I crashed randomly while playing Overwatch 2. The BSOD was KMODE_EXCEPTION_NOT_HANDLED. Unfortunately, I don't remember what driver/file was at fault and it also didn't create a dmp or log file of any kind, which I don't really understand why, but it sucks. Immediately I'm sorta panicking because it's a brand new build that I spent a lot of money on, and I kinda hate computer problems. So I try to do a CPU Large OCCT test, and, literally not even a half second in, PC locks up, and crashes. CLOCK_WATCHDOG_TIMEOUT is the error code. I tried without Eco Mode, same error. I tried without EXPO, same error, although it ran a little longer before crashing. I tried a couple more times with previous settings enabled just to see if it were some sort of fluke, but to no luck. It consistently crashes upon trying to do OCCT.

I also tried Cinebench R23, but it was only for like 30 seconds before I stopped the run because it ran fine before and it didn't crash within that timeframe, so, yeah. Before when I'd run Cinebench with these settings, I'd run the default 10 min test with a score of 18778 or something like that.

I haven't experienced any other errors yet, but I'm hesitant to try different games or another test.

I'm kind of in a predicament here because I spent a lot of money on this rig and it's pretty new. Is there anything I can do to remedy this?

Things I've tried:
Running OCCT without EXPO and/or Eco Mode(instant BSOD)
Cinebench(ran fine)
Clean boot into Windows and running OCCT(instant BSOD)
Windows Memory Diagnostic (no errors)

Things I've considered but haven't tried yet:
Clearing CMOS or resetting BIOS settings and running OCCT
Reseating RAM
Reseating CPU
Messing with voltages(I don't really know how to do this in my BIOS which is why I haven't done it)
Fresh install of Windows (Last resort)

If anyone knows anything, please help me out. I'm 99% sure it's a software issue and not a hardware issue, but I guess I can't be fully sure. I appreciate any guidance/advice any of you can give me.

DMP File for most recent error (CLOCK_WATCHDOG_TIMEOUT): https://drive.google.com/file/d/1-drk_bBWr4YnR5gDg9UuorC66jpSZdDe/view?usp=sharing
 
Last edited:
I fixed it, I reinstalled Windows and set BIOS settings to defaults, now OCCT works fine with no errors. I think it was Eco Mode causing the instability and crashes, but it doesn't really make sense considering it's supposed to be stable.