Post Reply 
Thread Rating:
  • 0 Votes - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
DPC Watchdog Violation
08-01-2016, 04:23 AM
Post: #1
DPC Watchdog Violation
My Windows 10 clean install often crashes giving me the "DPC Watchdog Violation" and I know it has to do when the Drobo S Gen 3 is connected via eSata. USB 3.0 connection doesn't work. The drobo will often not be recognized when the computer boots up and I have to unplug the eSata connection from the drobo then reconnect it. Sometimes the computer will recognize it then. When the drobo isn't attached when I boot up, the computer boots up really quickly (SSD C: drive). However when it is connected at boot up, it can often prolong the time required to boot up.

Sometimes recently the computer loses the connection with the drobo after it has already recognized it.

Anyone else have this issue? Any ideas?
Find all posts by this user
Quote this message in a reply
08-05-2016, 03:29 PM
Post: #2
RE: DPC Watchdog Violation
hi sturgessdm, can i check is this on the same computer as the one you posted here about?

am not sure if watchdog is part of windows 10 but there might be a bios setting about dpc watchdog you could check.
what happens if you try the clean install (without the drobo being attached, such as shutting it down with dashboard and then disconnecting it and trying the clean install?)

(btw i have XP home SP2, a Drobo v1 with 2x 1TB/2x 1.5TB WD greens, & a bkp Drobo v2 with the same + a DroboShare: unused)
& a DroboS v2 with 3xWD15EADS &2x1TB in DDR mode on win7, & a drobo5D (all usb)
  • btw i did a sustained (write) operation for about 6 hours, and got 13.2MB / sec ...objection? "sustained" :)
    (16.7MB/s on a v2 & 47-96MB/s drobo-s)
Find all posts by this user
Quote this message in a reply
Post Reply 

Forum Jump: