Oratian 2017 年 3 月 17 日 下午 7:20
BSOD error
For nearly a month, I've been having CLOCK_WATCHDOG_TIMEOUT BSoDs on my computer.
I've reinstalled windows, updated my drivers, and done just about everything that can be done.
Usually the error is caused by ntoskrnl.exe.
Some info (from WhoCrashed)

On Fri 3/17/2017 2:11:34 PM your computer crashed
crash dump file: C:\Windows\Minidump\031717-5171-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0x101 (0x30, 0x0, 0xFFFFF800DE34E180, 0x0)
Error: CLOCK_WATCHDOG_TIMEOUT
file path: C:\Windows\system32\ntoskrnl.exe

Forums are the last thing I can think of for help (even microsoft didn't help, go figure), and I'm doing it here because I don't want spam email from websites. Please help, and thanks in advance. If anyone needs additional information just ask.
< >
目前顯示第 1-15 則留言,共 23
The Giving One 2017 年 3 月 17 日 下午 7:23 
Post the model number and exact model of this computer. If custom built, the motherboard insetad.

Post the operating system.

Post if the OS is 32 or 64 bit also. Thanks.
Oratian 2017 年 3 月 17 日 下午 7:25 
引用自 The Giving One
Post the model number and exact model of this computer. If custom built, the motherboard insetad.

Post the operating system.

Post if the OS is 32 or 64 bit also. Thanks.
Asus Z170-A
Windows 10 64 bit.
The Giving One 2017 年 3 月 17 日 下午 7:27 
All drivers are up to date from here only, correct ?

https://www.asus.com/us/Motherboards/Z170-A/HelpDesk_Download/

And you have the latest BIOS installed by chance ? If you are not sure, caution needs to be used when updating BIOS, but ASUS and that board probably has E-Z flash utility anyway.
Oratian 2017 年 3 月 17 日 下午 7:29 
引用自 The Giving One
All drivers are up to date from here only, correct ?

https://www.asus.com/us/Motherboards/Z170-A/HelpDesk_Download/

And you have the latest BIOS installed by chance ? If you are not sure, caution needs to be used when updating BIOS, but ASUS and that board probably has E-Z flash utility anyway.
Everything should be up to date. I use driver booster for that. And yes the BIOS should be up to date. Just did that a few days ago but still got crashes.
The Giving One 2017 年 3 月 17 日 下午 7:30 
"Should" be ?

Don't use that to update your drivers. Download them and install them yourself from the official manufacturer's website only. In this case, ASUS.
Oratian 2017 年 3 月 17 日 下午 7:33 
引用自 The Giving One
"Should" be ?

Don't use that to update your drivers. Download them and install them yourself from the official manufacturer's website only. In this case, ASUS.
I didn't use Driver Booster to update my bios. Did it through EzFlash. And I just checked and they're all up to date. Again, ntoskrnl.exe is what is responsible.
The Giving One 2017 年 3 月 17 日 下午 7:36 
引用自 Caucaϟoid
I didn't use Driver Booster to update my bios. Did it through EzFlash. And I just checked and they're all up to date. Again, ntoskrnl.exe is what is responsible.
I was talking about not using Driver Booster for updating your drivers. But if you are sure they are all up to date, that is good, as well as the BIOS.

Here is a Tom's thread on the issue. I assume you have seen this maybe ?

http://www.tomshardware.com/forum/id-3023677/bsod-caused-ntoskrnl-exe.html

EDIT..The OP of that thread seems to say it was a faulty stick of RAM.

Originally posted by myattsnider Apr 13, 2016, 7:39 PM

"An update for everyone.

I found out that I had a faulty stick of ram, and that it was causing the computer to have errors be created from being misinterpreted by the ram and thus cause the crash. Since removing it I haven't had a single crash.

PS, I wiped the boot drive just to get the faulty files off. All is well :D "
最後修改者:The Giving One; 2017 年 3 月 17 日 下午 7:48
Oratian 2017 年 3 月 17 日 下午 7:40 
引用自 The Giving One
引用自 Caucaϟoid
I didn't use Driver Booster to update my bios. Did it through EzFlash. And I just checked and they're all up to date. Again, ntoskrnl.exe is what is responsible.
I was talking about not using Driver Booster for updating your drivers. But if you are sure they are all up to date, that is good, as well as the BIOS.

Here is a Tom's thread on the issue. I assume you have seen this maybe ?

http://www.tomshardware.com/forum/id-3023677/bsod-caused-ntoskrnl-exe.html
I have. I've done some Memory Tests and everything has come out fine.
The Giving One 2017 年 3 月 17 日 下午 7:41 
What about running in safe mode and maybe reinstalling the drivers, as also covered in that thread ?
Oratian 2017 年 3 月 17 日 下午 7:42 
引用自 The Giving One
What about running in safe mode and maybe reinstalling the drivers, as also covered in that thread ?
Did that. Didn't work.
Oratian 2017 年 3 月 17 日 下午 7:45 
The Giving One 2017 年 3 月 17 日 下午 7:46 
Found this also...

https://msdn.microsoft.com/en-us/library/windows/hardware/ff557211(v=vs.85).aspx

Cause

The specified processor is not processing interrupts. Typically, this occurs when the processor is nonresponsive or is deadlocked.
Oratian 2017 年 3 月 17 日 下午 7:55 
引用自 The Giving One
Found this also...

https://msdn.microsoft.com/en-us/library/windows/hardware/ff557211(v=vs.85).aspx

Cause

The specified processor is not processing interrupts. Typically, this occurs when the processor is nonresponsive or is deadlocked.
Got nothing from the scan.
The Giving One 2017 年 3 月 17 日 下午 7:59 
But you (so far) have had no issues in safe mode with this BSOD error, of course, right ?

If you have, I might be more suspicious as to the CPU possibility, that I just linked above.

EDIT..

Or still, maybe a RAM issue.
最後修改者:The Giving One; 2017 年 3 月 17 日 下午 8:01
< >
目前顯示第 1-15 則留言,共 23
每頁顯示: 1530 50

張貼日期: 2017 年 3 月 17 日 下午 7:20
回覆: 23