How Do I Stop DPC Watchdog Violation Blue Screen?

Anonymous
2014-03-01T07:22:04+00:00

I have been receiving pop up messages for the last month of so saying I should download Windows 8.1. Today, I went on my computer to check a couple things and it popped up again so I just decided to finally get it since I could let it download while I slept for a few hours. Now, ever since I got that, I keep on getting the DPC Watchdog Violation Blue Screen every time I get into a game of League of Legends. I haven't had this update long enough to see what else will cause it. This is getting extremely frustrating and I would like to know how to stop this. I have never been a huge fan of Windows 8, unfortunately, and this update so far isn't helping much. =/ 

P.S. I don't know if this makes a difference, but my computer is the HP Envy M6.

Windows for home | Previous Windows versions | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

62 answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2014-03-13T06:23:46+00:00

    OK, I'll have my roommate look at the stuff sometime this week, and if he doesn't have the time then I will look it up this weekend. I don't believe it deleted the old drivers before it brought in the new ones, I know we didn't delete them manually. If it did, then it didn't restart after deleting the old ones, just after it finished installing the new drivers.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2014-03-13T05:29:53+00:00

    Thanks! Still an 0x133 bug check as we've seen.

    2: kd> knL

     # Child-SP          RetAddr           Call Site

    00 ffffd000205c6e38 fffff8006fbeff7c nt!KeBugCheckEx

    01 ffffd000205c6e40 fffff8006fad281b nt! ?? ::FNODOBFM::`string'+0x13ddc

    02 ffffd000205c6ed0 fffff8006fc513a3 nt!KiUpdateRunTime+0x57

    03 ffffd000205c6f10 fffff8006fa15f85 nt!KeClockInterruptNotify+0xe3

    04 ffffd000205c6f40 fffff8006fb14343 hal!HalpTimerClockIpiRoutine+0x15

    05 ffffd000205c6f70 fffff8006fbcd12a nt!KiCallInterruptServiceRoutine+0xa3

    06 ffffd000205c6fb0 fffff8006fbcd50f nt!KiInterruptSubDispatchNoLockNoEtw+0xea

    07 ffffd000205b7a10 fffff8006fab69c4 nt!KiInterruptDispatchLBControl+0x11f

    08 ffffd000205b7ba0 fffff800002e34b9 nt!KxWaitForLockOwnerShip+0x34

    09 ffffd000205b7bd0 fffff800700f02c7 VerifierExt!KeAcquireInStackQueuedSpinLockAtDpcLevel_wrapper+0x121

    0a ffffd000205b7c20 fffff80001d2a19f nt!VerifierKeAcquireInStackQueuedSpinLockAtDpcLevel+0xc3

    0b ffffd000205b7c60 **fffff80001dee974** igdkmd64!hybDriverEntry+0x6dcf

    0c ffffd000205b7d10 fffff80001d0e2a3 igdkmd64!hybDriverEntry+0xcb5a4

    0d ffffd000205b7d70 fffff80001d18289 igdkmd64+0x492a3

    0e ffffd000205b7db0 fffff80001d619f5 igdkmd64+0x53289

    0f ffffd000205b7ee0 fffff80001cde400 igdkmd64!hybDriverEntry+0x3e625

    10 ffffd000205b7f60 fffff80001853137 igdkmd64+0x19400

    11 ffffd000205b8130 fffff8000179826b dxgkrnl!ADAPTER_DISPLAY_DdiSetVidPnSourceAddress+0x67

    12 ffffd000205b8160 fffff8006fbcc932 dxgmms1!VidSchiExecuteMmIoFlipAtISR+0x2f

    13 ffffd000205b8190 fffff80001852c0f nt!KeSynchronizeExecution+0x42

    14 ffffd000205b81d0 fffff8000178d961 dxgkrnl!DpSynchronizeExecution+0xaf

    15 ffffd000205b8220 fffff8000178ecc9 dxgmms1!VidSchiExecuteMmIoFlip+0x241

    16 ffffd000205b85d0 fffff8000179174e dxgmms1!VidSchUnwaitFlipQueue+0x219

    17 ffffd000205b8630 fffff80001790933 dxgmms1!VidSchiProcessDpcCompletedPacket+0x62e

    18 ffffd000205b8740 fffff80001790804 dxgmms1!VidSchiProcessDpcDmaPacket+0xb3

    19 ffffd000205b8790 fffff80001852e6b dxgmms1!VidSchDdiNotifyDpc+0xf4

    1a ffffd000205b87e0 fffff80001ddca65 dxgkrnl!DxgNotifyDpcCB+0x6b

    1b ffffd000205b8890 fffff80001d8aa97 igdkmd64!hybDriverEntry+0xb9695

    1c ffffd000205b88c0 fffff80001cf4680 igdkmd64!hybDriverEntry+0x676c7

    1d ffffd000205b8920 fffff8000185309b igdkmd64+0x2f680

    1e ffffd000205b8950 fffff8006fad8d10 dxgkrnl!DpiFdoDpcForIsr+0x3b

    1f ffffd000205b89a0 fffff8006fad89f0 nt!KiExecuteAllDpcs+0x1b0

    20 ffffd000205b8af0 fffff8006fbcf7ea nt!KiRetireDpcList+0xd0

    21 ffffd000205b8c60 0000000000000000 nt!KiIdleLoop+0x5a

    2: kd> ub fffff800`01dee974

    igdkmd64!hybDriverEntry+0xcb581:

    fffff80001dee951 eb07            **jmp**     **igdkmd64!hybDriverEntry**+0xcb58a (fffff80001dee95a)

    fffff800`01dee953 48899a60010000  mov     qword ptr [rdx+160h],rbx

    fffff800`01dee95a 33f6            xor     esi,esi

    fffff800`01dee95c 83bdc021000002  cmp     dword ptr [rbp+21C0h],2

    fffff80001dee963 0f85e7000000    **jne**     **igdkmd64!hybDriverEntry**+0xcb680 (fffff80001deea50)

    fffff800`01dee969 458bcf          mov     r9d,r15d

    fffff800`01dee96c 458bc4          mov     r8d,r12d

    fffff80001dee96f e8bcb7f3ff      call    igdkmd64!hybDriverEntry+0x6d60 (fffff80001d2a130)

    igdkmd64!hybDriverEntry is in a loop and it caused a deadlock, therefore the 0x133 bugcheck occurred.

    With this said, still being caused by the graphics drivers (verifier detecting them in violation). Did you uninstall the old drivers and restart before installing the new ones?

    Also, your laptop may have dual-graphics (i.e Intel Graphics + nVidia or AMD for example). Ensure all video related drivers are up to date via HP's website.

    Regards,

    Patrick

    Was this answer helpful?

    0 comments
  3. Anonymous
    2014-03-13T05:11:36+00:00

    Oh, actually, i think this is what you were asking for?

    https://onedrive.live.com/redir?resid=860CC7F682A271F0%21802

    Was this answer helpful?

    0 comments
  4. Anonymous
    2014-03-13T05:05:20+00:00

    Those files are what I've been giving you this whole time. Where are the other ones found?

    Was this answer helpful?

    0 comments
  5. Anonymous
    2014-03-13T04:15:48+00:00

    I'll need the Kernel-Dump, it's an 0x133.

    Regards,

    Patrick

    Was this answer helpful?

    0 comments