[Win10] CLOCK_WATCHDOG_TIMEOUT / IRQL_NOT_LESS_OR_EQUAL

W

Wildfire

Active member
Joined
Nov 3, 2015
Posts
28
Lately, I've been getting regular BSOD's. I've seen CLOCK_WATCHDOG_TIMEOUT and IRQL_NOT_LESS_OR_EQUAL bluescreens. They seem to occur only when playing games and occasionally when exiting ZoomPlayer while it's playing a video. Heavy loads, like x264 encoding with VidCoder (Handbrake) can run for days without problems. It seems to be video related, at least that's what I think.

In the past, this forum has been of excellent help in figuring out BSOD's I was having. At that time, Malwarebytes Anti-Malware was the culprit. Hopefully, this time the reason for the BSOD's can be found also...


For your information:

- Self-built desktop system
- ASUS Maximus Hero VIII motherboard (BIOS 3101 beta, issues present with previous non-beta BIOS too)
- Intel Core i7-6700K (slightly overclocked by having all cores on 45x turbo multiplier)
- Corsair AX760 PSU
- ASUS GeForce GTX 980 Ti STRIX
- SoundBlaster ZxR
- 32 GB RAM (2x G.Skill 16 GB DDR4-2666 Kit, F4-2666C15D-16GVR, Ripjaws V, XMP 2.0), rated 2666 MHz, clocked at 2400 MHz
- Intel 750 SSD (PCI Express, 400GB)
- Samsung 840 Evo 500GB (SATA)
- 2x Western Digital Green 2TB (SATA)

Intel SSD and ASUS videocard approximately 1.5 year old. Motherboard/CPU/RAM approximately 1 year old. PSU approximately 2.5 years old. Soundcard approximately 3 years old. Western Digital harddrives approximately 3.25 years old. Samsung SSD, well no idea honestly, I'd guess approximately 3 years old.



Windows 10 x64 Pro N (with Media Player add-on package, fully up-to-date as of today)
Clean install performed a month ago. Issues were present before.

Other possibly relevant software: Kaspersky Internet Security 2017 / SuperAntispyware Professional / Hitman Pro Alert.

All software up-to-date (checked by Secunia PSI, Ruckzuck and Filehippo App Manager). Drivers should also all be up-to-date.


GeForce drivers 378.66 (isssues present with previous driver versions too)

Intel SSD seems to be okay, as per the full diagnostic scan of Intel's SSD Toolbox. // Samsung SSD has not yet been checked, I don't know a program to check it correctly, although per Samsung Magician at least the SMART info is okay (EDIT: SSD Life gives the SSD an OK too) // The Western Digital hard drives are okay also, as tested by WD Diagnostics. // Memory has been checked using Memtest86 (latest version from Memtest86.com) during three quarters of day, no errors found.

I also tried running EVGA OC Scanner X v3 (64-bit) for stresstesting the GPU. I had it run for three hours without problems, no crashes and also no artifacts detected...


I'll be running Driver Verifier, so should another crash occur I'll have more info to offer.

Unfortunately enough, I had wiped the minidump folder recently so for now I've only got the one minidump of today's crash to offer...


Thanks in advance for any help!
 

Attachments

Re: Windows 10 BSOD's -- CLOCK_WATCHDOG_TIMEOUT / IRQL_NOT_LESS_OR_EQUAL

Also, per SFC /SCANNOW no errors in Windows system files.

-- Edit: I have just noticed that enabling Driver Verifier results in Hitman Pro Alert being disabled. The HitmanPro.Alert Support Driver cannot be loaded and as a result, the HitmanPro.Alert service also cannot be loaded. So if Hitman Pro Alert were to be the cause of my issues, it cannot be tracked while Driver Verifier is active...
 
Re: Windows 10 BSOD's -- CLOCK_WATCHDOG_TIMEOUT / IRQL_NOT_LESS_OR_EQUAL

Hi Wildfire,

Your first minidump provided a 0xD1, but there's barely anything in the stack trace, so it's not very helpful.
Code: 
2: kd> kL
 # Child-SP          RetAddr           Call Site
00 ffffa700`2803ac58 fffff801`8b5cf829 nt!KeBugCheckEx
01 ffffa700`2803ac60 fffff801`8b5cde07 nt!KiBugCheckDispatch+0x69
02 ffffa700`2803ada0 00000000`00000000 nt!KiPageFault+0x247

The second minidump isn't Verifier Enabled, as if it were, the stop code would be 0xC4. Instead, it's a STOP 0xA. The stack in this case references intelppm, which is an Intel processor driver.
Code: 
2: kd> kL
 # Child-SP          RetAddr           Call Site
00 ffff9d01`48f7aca8 fffff800`741e3829 nt!KeBugCheckEx
01 ffff9d01`48f7acb0 fffff800`741e1e07 nt!KiBugCheckDispatch+0x69
02 ffff9d01`48f7adf0 fffff800`7417843e nt!KiPageFault+0x247
03 ffff9d01`48f7af80 fffff800`741d9d40 nt!KiEndThreadAccountingPeriod+0x5e
04 ffff9d01`48f7afb0 fffff800`741da1b7 nt!KiInterruptSubDispatchNoLockNoEtw+0xc0
05 ffff9d01`48f6b640 fffff802`1a142832 nt!KiInterruptDispatchNoLockNoEtw+0x37
06 ffff9d01`48f6b7d8 fffff802`1a141320 [COLOR=#ff0000]intelppm!C1Halt[/COLOR]+0x2
07 ffff9d01`48f6b7e0 fffff800`7415a933 intelppm!AcpiCStateIdleExecute+0x20
08 ffff9d01`48f6b810 fffff800`7415a13a nt!PpmIdleExecuteTransition+0x643
09 ffff9d01`48f6ba80 fffff800`741db74c nt!PoIdle+0x33a
0a ffff9d01`48f6bbe0 00000000`00000000 nt!KiIdleLoop+0x2c
Code: 
start             end                 module name
fffff802`1a140000 fffff802`1a16b000   intelppm   (pdb symbols)          c:\symbols2\intelppm.pdb\37985D1B9E444A7F9EDD9BFCE6CB88A71\intelppm.pdb
    Loaded symbol image file: intelppm.sys
    Mapped memory image file: c:\symbols2\intelppm.sys\578997A32b000\intelppm.sys
    Image path: intelppm.sys
    Image name: intelppm.sys
    Browse all global symbols  functions  data
    Timestamp:        Fri Jul 15 22:10:43 2016 (578997A3)
    CheckSum:         0002E623
    ImageSize:        0002B000
    File version:     10.0.14393.0
    Product version:  10.0.14393.0
    File flags:       0 (Mask 3F)
    File OS:          40004 NT Win32
    File type:        3.7 Driver
    File date:        00000000.00000000
    Translations:     0409.04b0
    CompanyName:      Microsoft Corporation
    ProductName:      Microsoft® Windows® Operating System
    InternalName:     intelppm.sys
    OriginalFilename: intelppm.sys
    ProductVersion:   10.0.14393.0
    FileVersion:      10.0.14393.0 (rs1_release.160715-1616)
    FileDescription:  Processor Device Driver
    LegalCopyright:   © Microsoft Corporation. All rights reserved.

There is also a newer version of your BIOS available, but the description doesn't suggest relevance to this issue (though it is a stable/non-beta release). I would start by removing your overclock and/or updating your Intel chipset drivers. As for Verifier, I would try it again using the instructions found here if you hadn't already.
 
Re: Windows 10 BSOD's -- CLOCK_WATCHDOG_TIMEOUT / IRQL_NOT_LESS_OR_EQUAL

Xer said:
Hi Wildfire,

Your first minidump provided a 0xD1, but there's barely anything in the stack trace, so it's not very helpful.
Code: 
2: kd> kL
 # Child-SP          RetAddr           Call Site
00 ffffa700`2803ac58 fffff801`8b5cf829 nt!KeBugCheckEx
01 ffffa700`2803ac60 fffff801`8b5cde07 nt!KiBugCheckDispatch+0x69
02 ffffa700`2803ada0 00000000`00000000 nt!KiPageFault+0x247

The second minidump isn't Verifier Enabled, as if it were, the stop code would be 0xC4. Instead, it's a STOP 0xA. The stack in this case references intelppm, which is an Intel processor driver.
Code: 
2: kd> kL
 # Child-SP          RetAddr           Call Site
00 ffff9d01`48f7aca8 fffff800`741e3829 nt!KeBugCheckEx
01 ffff9d01`48f7acb0 fffff800`741e1e07 nt!KiBugCheckDispatch+0x69
02 ffff9d01`48f7adf0 fffff800`7417843e nt!KiPageFault+0x247
03 ffff9d01`48f7af80 fffff800`741d9d40 nt!KiEndThreadAccountingPeriod+0x5e
04 ffff9d01`48f7afb0 fffff800`741da1b7 nt!KiInterruptSubDispatchNoLockNoEtw+0xc0
05 ffff9d01`48f6b640 fffff802`1a142832 nt!KiInterruptDispatchNoLockNoEtw+0x37
06 ffff9d01`48f6b7d8 fffff802`1a141320 [COLOR=#ff0000]intelppm!C1Halt[/COLOR]+0x2
07 ffff9d01`48f6b7e0 fffff800`7415a933 intelppm!AcpiCStateIdleExecute+0x20
08 ffff9d01`48f6b810 fffff800`7415a13a nt!PpmIdleExecuteTransition+0x643
09 ffff9d01`48f6ba80 fffff800`741db74c nt!PoIdle+0x33a
0a ffff9d01`48f6bbe0 00000000`00000000 nt!KiIdleLoop+0x2c
Code: 
start             end                 module name
fffff802`1a140000 fffff802`1a16b000   intelppm   (pdb symbols)          c:\symbols2\intelppm.pdb\37985D1B9E444A7F9EDD9BFCE6CB88A71\intelppm.pdb
    Loaded symbol image file: intelppm.sys
    Mapped memory image file: c:\symbols2\intelppm.sys\578997A32b000\intelppm.sys
    Image path: intelppm.sys
    Image name: intelppm.sys
    Browse all global symbols  functions  data
    Timestamp:        Fri Jul 15 22:10:43 2016 (578997A3)
    CheckSum:         0002E623
    ImageSize:        0002B000
    File version:     10.0.14393.0
    Product version:  10.0.14393.0
    File flags:       0 (Mask 3F)
    File OS:          40004 NT Win32
    File type:        3.7 Driver
    File date:        00000000.00000000
    Translations:     0409.04b0
    CompanyName:      Microsoft Corporation
    ProductName:      Microsoft® Windows® Operating System
    InternalName:     intelppm.sys
    OriginalFilename: intelppm.sys
    ProductVersion:   10.0.14393.0
    FileVersion:      10.0.14393.0 (rs1_release.160715-1616)
    FileDescription:  Processor Device Driver
    LegalCopyright:   © Microsoft Corporation. All rights reserved.

There is also a newer version of your BIOS available, but the description doesn't suggest relevance to this issue (though it is a stable/non-beta release). I would start by removing your overclock and/or updating your Intel chipset drivers. As for Verifier, I would try it again using the instructions found here if you hadn't already.
Click to expand...

Thanks for your reply.

Driver Verifier is enabled, I just verified it to be sure. So for some reason it wasn't triggered when the 2nd crash occured.

I'm already on the latest Intel chipset drivers (v10.1.1.42).

I'll see about removing the slight overclock on turbo boost. I doubt it's the cause, but it's better to be sure...

By the way, on the previous BIOS (non-beta) the issues were present also. I actually updated hoping it would alleviate the problem...
 
Re: Windows 10 BSOD's -- CLOCK_WATCHDOG_TIMEOUT / IRQL_NOT_LESS_OR_EQUAL

Wildfire said:
Driver Verifier is enabled, I just verified it to be sure. So for some reason it wasn't triggered when the 2nd crash occured.
Click to expand...

Okay, just wanted to be sure. Given that the first crash was a 0xD1, I'm thinking it's more likely to be a driver issue than overclocking as well, so if we can get Verifier to generate an enabled dump, that would be very helpful.
 
Re: Windows 10 BSOD's -- CLOCK_WATCHDOG_TIMEOUT / IRQL_NOT_LESS_OR_EQUAL

Xer said:
Wildfire said:
Driver Verifier is enabled, I just verified it to be sure. So for some reason it wasn't triggered when the 2nd crash occured.
Click to expand...

Okay, just wanted to be sure. Given that the first crash was a 0xD1, I'm thinking it's more likely to be a driver issue than overclocking as well, so if we can get Verifier to generate an enabled dump, that would be very helpful.
Click to expand...

I've just switched back to non-overclocked settings. Turbo Boost multiplier settings are at automatic again, as is core voltage.

Let's see how things go. :)
 
Re: Windows 10 BSOD's -- CLOCK_WATCHDOG_TIMEOUT / IRQL_NOT_LESS_OR_EQUAL

Moin,

it's not the small overclocking, but i saw Intels rapid Storage beside NVMe driver, so get rid of Intel Rapid Sorage first, well known intels problem if an NVMe is in the System.

next you should eliminate SUPERAntiSpyware by the company SUPERAdBlocker.com and SUPERAntiSpyware.com (SUPERAntiSpyware | Remove Malware | Remove Spyware - AntiMalware, AntiSpyware, AntiAdware!), it is from 2011 and may not play fair with win10.

as Xer stated, the Stack does not contain enough info to track it down, either Verifier reveals the driver or a full memory.dmp might be required.
 
Re: Windows 10 BSOD's -- CLOCK_WATCHDOG_TIMEOUT / IRQL_NOT_LESS_OR_EQUAL

MichaelB said:
Moin,

it's not the small overclocking, but i saw Intels rapid Storage beside NVMe driver, so get rid of Intel Rapid Sorage first, well known intels problem if an NVMe is in the System.

next you should eliminate SUPERAntiSpyware by the company SUPERAdBlocker.com and SUPERAntiSpyware.com (SUPERAntiSpyware | Remove Malware | Remove Spyware - AntiMalware, AntiSpyware, AntiAdware!), it is from 2011 and may not play fair with win10.

as Xer stated, the Stack does not contain enough info to track it down, either Verifier reveals the driver or a full memory.dmp might be required.
Click to expand...

Actually, SuperAntispyware isn't from 2011. It's being actively maintained and the most recent release is just from a few weeks ago.

And why should I remove Intel RST? I've still got two SATA HDD's and one AHCI SSD in my system. I've never heard of Intel's RST drivers of causing problems alongside a NVMe drive...
 
Re: Windows 10 BSOD's -- CLOCK_WATCHDOG_TIMEOUT / IRQL_NOT_LESS_OR_EQUAL

Let's see what is in your System :huh:

NVMe Intel SSDPEDMW40
Samsung Evo 850, WDC HDD
Code: 
Browse full module list
start             end                 module name
fffff802`95d00000 fffff802`95d0a000   [COLOR=#b22222]SASKUTIL64[/COLOR]   (deferred)             
    Image path: SASKUTIL64.SYS          // SuperAntispyware beside Kaspersky
    Image name: SASKUTIL64.SYS
    Browse all global symbols  functions  data
    Timestamp:        [COLOR=#ff0000]Tue Jul 12 23:00:01 2011[/COLOR] (4E1CB5D1)
    CheckSum:         00009495
    ImageSize:        0000A000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
2: kd> lmDvmSASDIFSV64
Browse full module list
start             end                 module name
fffff802`95d10000 fffff802`95d1a000   [COLOR=#b22222]SASDIFSV64[/COLOR]   (deferred)             
    Image path: SASDIFSV64.SYS
    Image name: SASDIFSV64.SYS // SuperAntispyware beside Kaspersky
    Browse all global symbols  functions  data
    Timestamp:        [COLOR=#b22222]Fri Jul 22 01:03:00 2011 [/COLOR](4E28B024)
    CheckSum:         00010523
    ImageSize:        0000A000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
2: kd> lmDvmElbyCDIO
Browse full module list
start             end                 module name
fffff802`95da0000 fffff802`95dac000   [COLOR=#b22222]ElbyCDIO[/COLOR]   (deferred)             
    Image path: ElbyCDIO.sys // Elby
    Image name: ElbyCDIO.sys
    Browse all global symbols  functions  data
    Timestamp:        Thu Dec 18 00:30:51 2014 (5492122B)
    CheckSum:         000153B4
    ImageSize:        0000C000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
2: kd> lmDvmiaStorA
Browse full module list
start             end                 module name
fffff802`93da0000 fffff802`9426f000   [COLOR=#b22222]iaStorA[/COLOR]    (deferred)             
    Image path: iaStorA.sys // IRST from Intel, Rapid Storage
    Image name: iaStorA.sys
    Browse all global symbols  functions  data
    Timestamp:        Thu Nov 17 12:02:14 2016 (582D8E36)
    CheckSum:         000C42C4
    ImageSize:        004CF000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
2: kd> lmDvmAnyDVD
Browse full module list
start             end                 module name
fffff802`979b0000 fffff802`979dc000   [COLOR=#b22222]AnyDVD[/COLOR]     (deferred)             
    Image path: AnyDVD.sys
    Image name: AnyDVD.sys
    Browse all global symbols  functions  data
    Timestamp:        Mon Jul 11 18:57:48 2016 (5783D00C)
    CheckSum:         0002C45B
    ImageSize:        0002C000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
2: kd> lmDvmIaNVMe
Browse full module list
start             end                 module name
fffff802`93600000 fffff802`9361b000   [COLOR=#b22222]IaNVMe[/COLOR]     (deferred)             
    Image path: IaNVMe.sys         // Intels NVMe driver
    Image name: IaNVMe.sys
    Browse all global symbols  functions  data
    Timestamp:        Tue Oct 25 10:16:09 2016 (580F14C9)
    CheckSum:         000241DC
    ImageSize:        0001B000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

VirtualBox also installed, a lot of Filterdrivers within the Filesystem

as my HP Z840 with NVme and SSD doesn have any hickup and according an internal HP Whitepaper states to remove IRST for stability, you can give it a try.

it's your machine crashing, not mine / ours.
 
Re: Windows 10 BSOD's -- CLOCK_WATCHDOG_TIMEOUT / IRQL_NOT_LESS_OR_EQUAL

ElbyCDIO/AnyDVD - is from Redfox AnyDVD HD which I use to rip my DVD and Blu-rays so I can convert them for storage on my NAS. So they're necessary.

I have uninstalled SuperAntispyware and as said, the slight overclock has also been removed. If after a while still no BSOD's have occured I'll put the slight overclock back to see if it changes anything.
 
Re: Windows 10 BSOD's -- CLOCK_WATCHDOG_TIMEOUT / IRQL_NOT_LESS_OR_EQUAL

A few days later and still no crashes. Cautiously optimistic that it was either the overlock or SuperAntispyware causing the issues. I'll be putting back my slight overclock soon to see how things go then...
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top