DPC Watchdog Violation. Laptop won't boot up.

spunk said:

this is an indication of a failing HDD with too many bad sectors. The Drive needs to be replaced.

I think the reason for the is i did chkdsk /f /r which scans the entire hard drive. two much of a coincidence for two people to have the issue on the same day and same laptop. I think it was an update. There were a bunch of items updated on 9/26/16

spunk said:

If the Check Disk (chkdsk /R) stalls at 11% then it is trying to move data from a Bad Sector to a good sector near by. If there are too many bad sectors, Check Disk will stall for long periods of time, possibly overnight or Fail. A Drive with no Bad Sectors, updated or not, will finish within an hour or two.

I also ran it from the safe mode command prompt and it showed me each step of the way. it came up with no bad sectors and wasn't trying to move anything. It just scanned everything

I think i am going to scan it with spinrite next...

jdbrady441 said:

I think the reason for the is i did chkdsk /f /r which scans the entire hard drive. two much of a coincidence for two people to have the issue on the same day and same laptop. I think it was an update. There were a bunch of items updated on 9/26/16

+1
I am another "coincidence" with Dell Latitude E6520, whose laptop won't boot with this error since yesterday (9/29/16)

I am going to work on the laptop hard over the next two days. I haven't been able to find any hardware issues of any kind. The hard drive is less than a year old.... if you log into safe mode and look at programs, are there a bunch of updates on 9/29/16?

I gave up on this - restoring the system to Win7.

In Safe Mode, under the MS updates I saw a few from 9/26/16 (not 9/29).
Removed most of them, but couldn't uninstall 1 - the "uninstall" button wouldn't appear for that one.
Didn't help.

Do you remember what it was that you couldn't uninstall?

This one kb3176936

spunk said:

this is an indication of a failing HDD with too many bad sectors. The Drive needs to be replaced.

I am 42 hours into a spinrite scan and it has not found any errors. Do you still think this is a hard drive error issue?