Please help! CLOCK_WATCHDOG_TIMEOUT ntoskrnl.exe BSOD while gaming

processor 4 was hung but you need to change your memory dump type to kernel memory dump to allow the debugging info not be stripped out.
I would also start cmd.exe as an admin and run
verifier.exe /standard /all
and change the memory dump type to kernel dump and reboot and reproduce the problem.

last bugcheck took 5 days 2 hours.
I would guess it is your video card driver (chrome using hardware acceleration)
looks like you also have overclocking drivers installed RTCore64.sys
and maybe a pirate version of windows.

I would remove the overclocking driver and see if you still get the bugcheck.
the I would also boot with verifier but just to see if it catches a bad driver but you most likely will not want to run it for 5 days to reproduce the problem.
so you can use
verifier.exe /reset
to turn it off. the kernel memory dump should have the required info.
(or just assume it was your overclock driver, remove it and reboot)


 
processor 4 was hung but you need to change your memory dump type to kernel memory dump to allow the debugging info not be stripped out.
I would also start cmd.exe as an admin and run
verifier.exe /standard /all
and change the memory dump type to kernel dump and reboot and reproduce the problem.

last bugcheck took 5 days 2 hours.
I would guess it is your video card driver (chrome using hardware acceleration)
looks like you also have overclocking drivers installed RTCore64.sys
and maybe a pirate version of windows.

I would remove the overclocking driver and see if you still get the bugcheck.
the I would also boot with verifier but just to see if it catches a bad driver but you most likely will not want to run it for 5 days to reproduce the problem.
so you can use
verifier.exe /reset
to turn it off. the kernel memory dump should have the required info.
(or just assume it was your overclock driver, remove it and reboot)


 

OldGreg

Reputable
Aug 7, 2015
3
0
4,510
0



Thank you for the reply!

I ran verifier as suggested and got repeaded BSOD's related to a IO manager violation.
Here is the dump for that.
https://www.sendspace.com/file/81yu98

I went back in to verifier and enabled custom settings with IO checks off and got the WATCHDOG_TIMEOUT BSOD again. Here is the dump for that.
https://www.sendspace.com/file/4kcg1u

To the best of my knowledge its a legit copy but this is a hand me down rig so not 100%, will be upgrading to WIN 10 soon in all likelihood.
I removed EVGA precision X which was the over clocking driver I believe.
I also checked and verified it's a kernel memory dump.

Thank you again for looking at this, it's so maddening when i'm hauling loot back in Rust and crash then get back and wake up on the beach :p
 
second bugcheck was a clock_watchdog_timeout on processor 4
change the memory dump type to kernel and I can tell you what failed.
here is info on how to make the change:https://www.sophos.com/en-us/support/knowledgebase/111474.aspx
(just slecte the kernel memory dump type, then reboot.)

unable to read debug details because they were removed from the mini memory dump, you have to change the memory dump type to kernel in order for the info not to be stripped out.
-----------
remove overclocking driver:
C:\Program Files (x86)\EVGA Precision X\RTCore64.sys Sun Mar 10 22:32:06 2013

------------


io manager violation, corrupted the stack was caused by
Logitech Gamepanel Virtual HID Device Driver
\SystemRoot\system32\drivers\LGVirHid.sys Mon Nov 23 17:36:48 2009
remove or update:http://support.logitech.com/en_us/home

machine info:
BIOS Version 4102
BIOS Release Date 09/09/2013
Manufacturer ASUSTeK Computer INC.
Product P8Z68-V LE
Version Rev X.0x
Processor Version Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz
Processor Voltage 8ah - 1.0V
External Clock 100MHz
Max Speed 3800MHz
Current Speed 3320MHz





 

ASK THE COMMUNITY

TRENDING THREADS