Two different systems, two different problems

[Eastman51]

Alright, I figure I should knock out both of my the issues I'm getting plagued with.

First Issue:

I have a PC that hard locks (freezes up, with a buzzing sound from speakers/headphones) and then turns off after a few minutes. Then it tries to power back itself back on, but shuts off before even trying to clear POST. If I hit the reset button before the PC shuts off, it reboots normally. If I wait for it to shut itself off and fail consecutive boot attempts, I have to turn off the PSU and wait a few seconds; then I can boot normally.

While in Windows, the PC behaves perfectly fine. CPU temps and usage are normal, GPU temps are good. Everything runs fine, except the trouble game. Whenever I play Forza Horizon 4, I get this problem. The game runs great for a solid 4-5 minutes before the PC locks up. There's nothing in event viewer, drivers and BIOS are up to date, Windows itself is up to date and is good. I might swap the RAM around a little, I don't have exact matches per channel (zebra stripes), but the system works so idk if it would fix anything. What's just as strange is that this PC ran the game without this issue last week. 

Specs:

i5-4670k (no OC)

Asus Q87M-E/CSM

32 GB Kingston HyperX (2x8 black, 2x8 white) DDR3

1TB WD Blue SSD (C:)

1TB WD Blue HDD (7200rpm, game install location)

Asus GTX 960 Turbo 4GB

EVGA 700B PSU

I kind of remember having a similar (or maybe identical issue, not sure) with Forza Horizon 3 on this same config at one point (could have been different CPU/mobo though). I was running the 960 off a molex to PCIe 6-pin on a 350W PSU; I solved whatever issue I was having by upgrading to the EVGA PSU that's in there now. Could be PSU related?

 

 

Second Issue:

I've been getting the CLOCK_WATCHDOG_TIMEOUT BSOD every now and then on my Ryzen system. I'll be playing a game, or something, and then about a minute after system load goes down, BAM. I added more memory about a week ago, and this is the first time I've gotten the BSOD since; I had it maybe 2 or 3 times before that (PC was built in/around August). I have a feeling it's RAM related; my CPU has no OC and all I've done is enable virtualization, my GPU has never been touched (was in another system before without issues), but I HAVE OC'ed this RAM. I'm not sure if the new kit of RAM has these issues, since I've seen this BSOD before on the existing RAM. 

The last time I got this BSOD (with just the original RAM kit), I downloaded and ran memtest86. It ran about 4 or 5 passes with no errors. After I got this one, I ran memtest86 again and did 1 pass with 0 errors (32GB of RAM takes forever to run). I have not tried lowering the OC yet as the system seems to run well enough, these BSODs are very infrequent.

Specs:

Ryzen 5 2600x

Asus Strix B350-F

16GB Corsair Vengeance LPX 3000MHz black heat spreaders (original RAM)

16GB Corsair Vengeance LPX 3000MHz white heat spreaders (new RAM)

Asus Strix 1070

Samsung 860 EVO boot drive

Toshiba 1TB and 4TB HDDs

Seagate 2TB SSHD

Samsung 970 EVO games drive (installed in a PCIe card, not on the motherboard)

Asus Xonar DGX sound card

NZXT Hue+

Seasonic Focus+ Platinum 750W

On a, maybe, unrelated note: Windows takes 5 or more minutes to shutdown (when both shutdown and restart is selected), no idea why but it's kind of annoying when you're troubleshooting. I may just need a reinstall, but idk. I also wouldn't be surprised if it was the RAM; I've had a poor experience with Corsair products, and I only got that kit at the time because it was the cheapest/was highly recommended to me.

[zombieshy_guy81]

Ok so for system 1, try installing Forza on your second drive as the one the game is running off of may be giving up the ghost and do you have the same issue when you try to run any other games?

 

As for system 2 try putting the Ram clock back down to stock and see if that fixes it. And since you said you upgraded your Ram are you sure that the models of ram are the same? If not that can cause some issues. Also try going to your motherboards product page on the Asus website and see the list of compatible Ram, Ryzen is EXTREMELY picky about what Ram you use.

[Eastman51]

4 hours ago, zombieshy_guy81 said:

Ok so for system 1, try installing Forza on your second drive as the one the game is running off of may be giving up the ghost and do you have the same issue when you try to run any other games?

 

As for system 2 try putting the Ram clock back down to stock and see if that fixes it. And since you said you upgraded your Ram are you sure that the models of ram are the same? If not that can cause some issues. Also try going to your motherboards product page on the Asus website and see the list of compatible Ram, Ryzen is EXTREMELY picky about what Ram you use.

I have the exact same model of RAM in the Ryzen system.  The ONLY difference is the color of the heat spreaders. I was thinking about lowering the clocks one tick, maybe the first kit I had just doesn't OC well.

 

The PC that is having issues with Forza had brand new drives (less than 3 weeks old). I could migrate it to the SSD and see what happens.

[asand1]

Clock_watchdog_timeout is absolutely an OC instability. Less speed or more voltage..

[Eastman51]

1 minute ago, asand1 said:

Clock_watchdog_timeout is absolutely an OC instability. Less speed or more voltage..

I'll try knocking the RAM down to 2933MHz and see what happens. It could take days or weeks before I get the crash again though, Memtest86 could yield results faster; but even that is slow with 32GB of RAM.

[Eastman51]

On 1/14/2019 at 3:02 PM, asand1 said:

Clock_watchdog_timeout is absolutely an OC instability. Less speed or more voltage..

We're almost to the end of the week without a crash now (3000MHz down to 2933MHz).

 

I'm chalking the other PC up to the fact that Forza is just messed up. After a game update, and nvidia driver update, the game still causes the PC to hard crash (the crash is partially different, but still quite similar).