watchdog violation and driver power state failture

Vicissitude · Sep 30, 2014

I just moved and im getting both of these errors on startup. When i get home i turn my computer on, it gives these errors and says i need to restart, then the computer works fine until i turn it on the next day. I never got these errors before i moved, from what i know about watchdog on processors is it monitors clocking speeds/digital signal quality. Im wondering if its because my computer is plugged into a power outlet that is for whatever reason putting out a bad signal.
Ive read that these errors can be associated with hard drive drivers/intel RST. I have the current version of intel RST. And as far as i know seagate doesnt even have drivers/firmware for their hybrid drives as ive scoured the internet for them.

Dark Lord of Tech · Sep 30, 2014

It usually is a driver issue.

Vicissitude · Oct 2, 2014

is there anything i can do to provide more specifics? I tried using another power socket and getting a power monitoring strip which didnt do anything.

Paul NZ · Oct 2, 2014

If its crashing upload the dmp files somewhere then post the link

Pinhedd · Oct 2, 2014

Vicissitude :

A watchdog timer is used to ensure that a piece of hardware in the system is responsive. The device (or the device driver) periodically resets the watchdog timer (kicks the dog) so that it does not elapse, but if the reset does not occur before the timer expires the timer generates an interrupt which is sent upstream. In the case of a PC peripheral, the interrupt is usually sent to the interrupt controller on the microprocessor which is then handled by the operating system. The operating system can then try and recover the device, disconnect it, and attempt to preserve its own state. In many cases though the OS can't safely recover from a hung device (eg, a disconnected boot device) and must halt.

Vicissitude · Oct 8, 2014

Pinhedd :

Vicissitude :

A watchdog timer is used to ensure that a piece of hardware in the system is responsive. The device (or the device driver) periodically resets the watchdog timer (kicks the dog) so that it does not elapse, but if the reset does not occur before the timer expires the timer generates an interrupt which is sent upstream. In the case of a PC peripheral, the interrupt is usually sent to the interrupt controller on the microprocessor which is then handled by the operating system. The operating system can then try and recover the device, disconnect it, and attempt to preserve its own state. In many cases though the OS can't safely recover from a hung device (eg, a disconnected boot device) and must halt.

by peripheral i take it you mean things like printers, mice, keyboards? because ive had issues previously with my printer affecting my computer.

how do i find this dmp file?

Pinhedd · Oct 8, 2014

Vicissitude :

Pinhedd :

by peripheral i take it you mean things like printers, mice, keyboards? because ive had issues previously with my printer affecting my computer.

how do i find this dmp file?

That's correct. There are tons of devices in the PC which may have watchdog timers built-in or associated with them.

In many cases, hardware failure can be handled gracefully from the perspective of the operating system. That is, a printer failure won't destabilize the kernel and cause a BSoD. The printer would simply be disconnected and an error presented. However, the same is not true for something that the kernel depends on, such as the boot drive.

johnbl · Oct 8, 2014

Almost every time I end up debugging a this particular error code, it turn out to be cause by a USB device driver failing to correctly install via the windows plug and Play system. Most of the time It is caused by a USB wireless Ethernet thumb drive being plugged in. The default driver that the Plug and play attempts to install hangs on the install and just re tries over and over on one CPU core, while another core is waiting for the Ethernet driver to become active. After some time the system bugchecks because the hardware never responds.

-you update BIOS to get firmware USB fixes,
-up update CPU chipset driver to get microcode fixes for the cpu and primary USB driver updates.
- update secondary USB 3.0 chipset driver (lots of custom versions with lots of bugs)

and now you get to your actual wireless USB device, Look for a driver date later from 2013 or newer. The old ones were just broken.

Note: note: usbview.exe from the windows standalone debugging tools is usefull in seeing if a USB port is having Issues.

- removing the driver from the system is also useful but people forget to turn off the Plug and play system and the driver gets installed again a few seconds latter.
You have to use control panel, turn off plug and play, uninstall the old usb wireless driver, install the new usb driver, turn plug and play back on.

if you don't do that you can have various versions working on your system and it is not the last version that you install that might be sleeted.
(you have to dig thru various menus, and find the correct version and select it, and the menu option is in a stupid place, some where in the "I have a disk" menu subtree.

Vicissitude · Oct 8, 2014

johnbl :

Almost every time I end up debugging a this particular error code, it turn out to be cause by a USB device driver failing to correctly install via the windows plug and Play system. Most of the time It is caused by a USB wireless Ethernet thumb drive being plugged in. The default driver that the Plug and play attempts to install hangs on the install and just re tries over and over on one CPU core, while another core is waiting for the Ethernet driver to become active. After some time the system bugchecks because the hardware never responds.

-you update BIOS to get firmware USB fixes,
-up update CPU chipset driver to get microcode fixes for the cpu and primary USB driver updates.
- update secondary USB 3.0 chipset driver (lots of custom versions with lots of bugs)

and now you get to your actual wireless USB device, Look for a driver date later from 2013 or newer. The old ones were just broken.

Note: note: usbview.exe from the windows standalone debugging tools is usefull in seeing if a USB port is having Issues.

- removing the driver from the system is also useful but people forget to turn off the Plug and play system and the driver gets installed again a few seconds latter.
You have to use control panel, turn off plug and play, uninstall the old usb wireless driver, install the new usb driver, turn plug and play back on.

if you don't do that you can have various versions working on your system and it is not the last version that you install that might be sleeted.
(you have to dig thru various menus, and find the correct version and select it, and the menu option is in a stupid place, some where in the "I have a disk" menu subtree.

That could very well be the issue. When i moved i couldnt get powerline to work so im using a usb wifi device, which is when i started getting these errors on startup. Next time i start my comp up i will unplug it from the usb and see what happens.

johnbl · Oct 8, 2014

usb devices still get loaded, they just hide them when they are unplugged.
you have to tell device manager to display hidden devices and delete the device.

Vicissitude :

johnbl :

That could very well be the issue. When i moved i couldnt get powerline to work so im using a usb wifi device, which is when i started getting these errors on startup. Next time i start my comp up i will unplug it from the usb and see what happens.

Search

watchdog violation and driver power state failture

Vicissitude

Distinguished

johnbl

Dark Lord of Tech

Retired Moderator

Vicissitude

Distinguished

Paul NZ

Polypheme

Pinhedd

Champion

Vicissitude

Distinguished

Pinhedd

Champion

johnbl

Polypheme

Vicissitude

Distinguished

johnbl

Polypheme

TRENDING THREADS

Latest posts

Moderators online

Share this page