• Competitor rules

    Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.

Hyburnates cry for help - System freezes / clock watchdog BSOD's

Caporegime
Joined
29 Jul 2011
Posts
36,705
Location
In acme's chair.
Hypernuts has been having some issues with his PC locking up, sometimes hard freezes which requite a hard re-boot, and sometimes (Less often) BSOD's which state 'clock-watchdog-error' which I believe is CPU power related.

He has changed his RAM for another set which has stopped this from happening as frequently, but it is still happening around once a day as opposed to twice a day or more.

We have raised the QPI/VTT voltage in case it is memory controller related, and raised the VCORE too, neither of which seem to have changed anything. We also added a couple of increments to a few other voltages.

It seems to happen under a mix of load types, and doesn't seem to be particularly consistent, but he seems to be playing World of Tanks most of the time when it happens, I'm sure he can correct me if I'm wrong.

System consists of a stock 2500K on an ASRock P67 Fatal1ty Pro, some sort of generic pre-build RAM (used to be something else...) and a GTX760.

Event log just has the usual critical kernel power events and unclean shutdown events. There are also a few "The system firmware has changed the processor's memory type range registers (MTRRs) across a sleep state transition (S4). This can result in reduced resume performance." events, but these don't seem to match up with the times the system freezes.

Calling Wazza300, you helped me loads with my Sandybridge issues! :D

Don't ask me why I'm making this thread, I think Hypernuts might have given up on technology and has buried the computer in the garden already.

Syslog - https://www.dropbox.com/s/mcu6t525a8w2u2l/Fail log.evtx?dl=0
 
Last edited:
Yeah I had nipped out hence the sleep state as it's a fresh OS and no power saving settings have been changed.

Might be worth mentioning this used to happen back on Win7, Win8.1 and Win10 and I'm now on a fresh install on a Samsung 860 or something (I don't really care for specs), however it used to happen on a mech HDD.

It used to happen on Photoshop mostly, however now it'll do it whenever. The most recent crash has the CPU at 46C and 40% usage, RAM usage wasn't too high either although I don't actually have a figure.
 
Back
Top Bottom