-
1
×InformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center. -
-
1
×InformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center. -
- HP Community
- Notebooks
- Notebook Operating System and Recovery
- Microsoft Watchdog Timer Driver

Create an account on the HP Community to personalize your profile and ask a question
03-30-2017 12:51 PM - edited 03-30-2017 12:52 PM
I have a Pavilion x360 notebook that i put Windows 7 on. Everything looked good until i noticed that every time i restarted or shut down the maachine, it would BSOD. I ran WhoCrashed and found the error was caused by the wd.sys (Microsoft Watchdog Timer Driver). I uninstalled the driver and rebooted - no more BSOD, however, the driver came right back and next time i did a reboot, the BSOD was back. I checked the driver version and it is the correct/up to date version for Win 7 (6.1.7600.16385), so since i can't remove or change the driver, i have no idea how to fix the issue.
On Wed 3/29/2017 8:43:21 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\032917-20498-01.dmp
This was probably caused by the following module: wd.sys (wd+0x1A46)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF88001DF4A46, 0xFFFFF880041BD878, 0xFFFFF880041BD0D0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\wd.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Watchdog Timer Driver
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
Solved! Go to Solution.
Accepted Solutions
03-30-2017 05:05 PM
Disabling the driver again resolved the issue, not sure why it didn't work the first time i disabled it but everything is all good now.