Windows 10: CLOCK_WATCHDOG_TIMEOUT BSOD among a multitude of other problems

Man, I don't even know what to do with this computer anymore... Just a few days ago, out of the blue, my laptop blue screens with the CLOCK_WATCHDOG_TIMEOUT error every other startup, literally. Google Chrome is refusing to open. I have done a System Restore, a sfc /scannow, Windows and driver updating, but to no avail. I apologize if I'm being a bit of a pain by not supplying vital information that I did not type here, but it seems my story of PC problems will be perpetual, this one being another in a series of odd problems with my laptop.

Half the time, upon opening games, the laptop lags severely then just freezes.

I've heard this error can appear from a virus, and I'm fully aware that viruses could strike me anytime with the quantity of potentially harmful things I download. Bitdefender, however, has supposedly cleaned out all viruses.

:)

 

Memory diagnostic results

My pc crashes on a multitude of games, while on others it never seems to crash at all. Most of the time it simply crashes to desktop while other times I get IRQL_NOT_LESS_OR_EQUAL bsod.

 

Multiple BSOD Problems (maybe caused by Hardware, Driver)

And another BSOD. This time "CLOCK_WATCHDOG_TIMEOUT (101)". I uploaded the DMP File to the Subfolder.

 

A couple of suggestions. Check to see that laptop air vents are not blocked and that the fan inside your laptop is working properly. If the laptop is on battery, it may be time to replace that battery pack.

Ak

 

Tried a couple of decently intensive tasks that did not kill the PC, as well as adjust the fan speeds from inside the HP Omen Control application. The fans seem to be working fine. If it is the battery, I'm confused about why it's lifespan is ending just 1.5 years after it was bought.

 

If your laptop is plugged in then it is not the battery pack. As for the battery lifespan I think it depends how many times the batteries have been recharged.

Good luck solving the problem. I just had a similar problem clock watchdog timeout with my main PC and it was caused by faulty software controlling my cpu and case fans.

Ak

 

The dump indicates a problem with Netwbw02.sys.
Code: ffff8200`2d329228 fffff806`2a261fd1*** WARNING: Unable to verify timestamp for Netwbw02.sys *** ERROR: Module load completed but symbols could not be loaded for Netwbw02.sys Netwbw02+0x161fd1[/quote] That belongs to your Intel(R) Wireless-N 7260 driver dated 2015-02-22.

You have a HP OMEN Notebook PC 15 laptop, what is the full model number, 15-??????

Need to check for a newer driver for the Intel device.

 

I updated the Intel Wireless driver, and it seems the issue(s) are fixed for now (I have no idea how that works). The laptop's exact model is HP OMEN Notebook - 15-5002nx (ENERGY STAR)

Edit: However, Google Chrome is still refusing to launch. It may not be related to this at all, but that seems unlikely.

 

Uninstall Chrome via Control Panel, Programs and Features then download and install the latest Chrome, see if that helps.

See here: Uninstall Google Chrome

 

Chrome is now working. Unfortunately, I have found out absolutely for sure that the blue screen happens every two startups the hard way. The startup in which I said the PC is now working fine was in one of the startups where it did not bluescreen. I'm just about ready to smash this stubborn thing, it's forcing me to revive this thread, too.

I have to type this because the forum thinks I didn't type anything.

 

It seems the CPU is having a issue with staying with the workload usually this happens when the cpu is unstable or been overclocked

Your CPU may be giving up the Ghost just saying

 

Run dm_log_collector and post the zip file if you have more BSODs.

 

We have a newcomer on the BSOD scene, along with the watchdog timeout. "DRIVER_IRQL_NOT_LESS_OR_EQUAL (netwbw02.sys)

Random freezing for absolutely no reason while doing mundane tasks, too.

The CPU cannot be dying so early (it has never been overclocked), though I will say that the laptop suffered physical damage to the screen upon an unfortunate knocking off the desk, but has been working fine otherwise for months until now.

 

Dump from 2/4 9:46AM shows a problem with Netwbw02.sys.
Code: BugCheck D1, {118, 2, 0, fffff80e7c299dca} *** WARNING: Unable to verify timestamp for Netwbw02.sys *** ERROR: Module load completed but symbols could not be loaded for Netwbw02.sys Probably caused by : Netwbw02.sys ( Netwbw02+39dca )[/quote] Driver Description: Intel® Wireless WiFi Link Driver - Intel® Wireless WiFi Link Adapter
Driver Update Site: Downloads for Intel® Dual Band Wireless-N 7260

The one you have now, Intel(R) Wireless-N 7260, is dated Tue Nov 3 09:30:10 2015. The web site has a 1/18/2017 driver available. Download and install that, see if it helps.

 

Sorry to bother everyone with these periodic updates, but the CLOCK_WATCHDOG_TIMEOUT BSOD just happened two times in a row while starting up. I'm afraid my laptop will eventually enter an infinite boot loop or the likes.