locked
0x00000133 BSOD RRS feed

  • Question

  • I came back from my friend's house about an hour ago and I booted up my laptop, but once it booted up to the desktop, my laptop hung and gave me a BSOD. I booted it up again and nothing happened, but I then turned it off and turned it back on just incase and it gave me the same BSOD. Any help?

    I have a Toshiba Satellite C75-A-13N

    Intel Core i3-4000M 2.40GHz

    8GB ram 

    Intel HD 4600

    Windows 8.1

    I also have the two dump files here:
    http://1drv.ms/1lTHyT2

    http://1drv.ms/1lTHDGt

    Many thanks 

    -Jacob

    Saturday, April 26, 2014 6:35 PM

Answers

  • Hi Jacob,

    Both of the attached DMP files are of the DPC_WATCHDOG_VIOLATION (133) bug check.

    This bug check indicates that the DPC watchdog executed, either because it detected a single long-running deferred procedure call (DPC), or because the system spent a prolonged time at an interrupt request level (IRQL) of DISPATCH_LEVEL or above.

    Generally with 0x133 bug checks, you'll need a kernel-dump to sift through the different processor call stacks to see what driver caused this, but in your case, it may not be necessary.

    2: kd> k
    Child-SP          RetAddr           Call Site
    ffffd001`ab562c98 fffff803`39997ad6 nt!KeBugCheckEx
    ffffd001`ab562ca0 fffff803`398b8678 nt! ?? ::FNODOBFM::`string'+0x2f626
    ffffd001`ab562d30 fffff803`39f9567f nt!KeClockInterruptNotify+0x788
    ffffd001`ab562f40 fffff803`398d3363 hal!HalpTimerClockInterrupt+0x4f
    ffffd001`ab562f70 fffff803`3995942a nt!KiCallInterruptServiceRoutine+0xa3
    ffffd001`ab562fb0 fffff803`3995980f nt!KiInterruptSubDispatchNoLockNoEtw+0xea
    ffffd001`ab5396c0 fffff803`398a9c20 nt!KiInterruptDispatchLBControl+0x11f
    ffffd001`ab539850 fffff803`398d0512 nt!KxWaitForLockOwnerShip+0x30
    ffffd001`ab539880 fffff800`c7512079 nt!IoAcquireCancelSpinLock+0x56
    ffffd001`ab5398b0 fffff800`c7511236 netbt!MSnodeCompletion+0x359
    ffffd001`ab539960 fffff803`3985d810 netbt!TimerExpiry+0x66
    ffffd001`ab5399b0 fffff803`3995baea nt!KiRetireDpcList+0x4f0
    ffffd001`ab539c60 00000000`00000000 nt!KiIdleLoop+0x5a
    

    ^^ netbt.sys (MBT Transport driver) appears to be the possible problematic driver here.

    2: kd> .trap ffffd001`ab5396c0
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=fffff80339b50c41 rbx=0000000000000000 rcx=ffffd001ab525860
    rdx=fffff80339aea860 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff803398a9c20 rsp=ffffd001ab539850 rbp=ffffe001b1338e10
     r8=fffff80339b50c40  r9=0000000000000389 r10=0000000000000801
    r11=ffffd001ab5398a0 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei ng nz na po nc
    nt!KxWaitForLockOwnerShip+0x30:
    fffff803`398a9c20 488b4708        mov     rax,qword ptr [rdi+8] ds:00000000`00000008=????????????????
    

    2: kd> u @rip
    nt!KxWaitForLockOwnerShip+0x30:
    fffff803`398a9c20 488b4708        mov     rax,qword ptr [rdi+8]
    fffff803`398a9c24 a801            test    al,1
    fffff803`398a9c26 75e8            jne     nt!KxWaitForLockOwnerShip+0x20 (fffff803`398a9c10) <- jump
    fffff803`398a9c28 8bc3            mov     eax,ebx
    fffff803`398a9c2a 488b5c2430      mov     rbx,qword ptr [rsp+30h]
    fffff803`398a9c2f 4883c420        add     rsp,20h
    fffff803`398a9c33 5f              pop     rdi
    fffff803`398a9c34 c3              ret
    

    ^^ netbt.sys calls nt!IoAcquireCancelSpinLock which synchronizes cancelable-state transitions for IRPs in a multiprocessor-safe way. Afterwards, it appears that we're waiting for lock ownership, but it never happens, therefore we get the inevitable 0x133 bug check. With this said, something 3rd-party network related is likely causing conflicts.

    ----------------------

    Remove and replace McAfee with Windows 8's built-in Windows Defender for temporary troubleshooting purposes as it's likely causing NETBIOS conflicts:

    McAfee removal - http://service.mcafee.com/FAQDocument.aspx?id=TS101331

    Windows Defender (how to turn on after removal) - http://www.eightforums.com/tutorials/21962-windows-defender-turn-off-windows-8-a.html

    Regards,

    Patrick

    “Be kind whenever possible. It is always possible.” - Dalai Lama

    • Marked as answer by Jacob '-' Monday, April 28, 2014 12:41 PM
    Saturday, April 26, 2014 6:51 PM

All replies

  • Hi Jacob,

    Both of the attached DMP files are of the DPC_WATCHDOG_VIOLATION (133) bug check.

    This bug check indicates that the DPC watchdog executed, either because it detected a single long-running deferred procedure call (DPC), or because the system spent a prolonged time at an interrupt request level (IRQL) of DISPATCH_LEVEL or above.

    Generally with 0x133 bug checks, you'll need a kernel-dump to sift through the different processor call stacks to see what driver caused this, but in your case, it may not be necessary.

    2: kd> k
    Child-SP          RetAddr           Call Site
    ffffd001`ab562c98 fffff803`39997ad6 nt!KeBugCheckEx
    ffffd001`ab562ca0 fffff803`398b8678 nt! ?? ::FNODOBFM::`string'+0x2f626
    ffffd001`ab562d30 fffff803`39f9567f nt!KeClockInterruptNotify+0x788
    ffffd001`ab562f40 fffff803`398d3363 hal!HalpTimerClockInterrupt+0x4f
    ffffd001`ab562f70 fffff803`3995942a nt!KiCallInterruptServiceRoutine+0xa3
    ffffd001`ab562fb0 fffff803`3995980f nt!KiInterruptSubDispatchNoLockNoEtw+0xea
    ffffd001`ab5396c0 fffff803`398a9c20 nt!KiInterruptDispatchLBControl+0x11f
    ffffd001`ab539850 fffff803`398d0512 nt!KxWaitForLockOwnerShip+0x30
    ffffd001`ab539880 fffff800`c7512079 nt!IoAcquireCancelSpinLock+0x56
    ffffd001`ab5398b0 fffff800`c7511236 netbt!MSnodeCompletion+0x359
    ffffd001`ab539960 fffff803`3985d810 netbt!TimerExpiry+0x66
    ffffd001`ab5399b0 fffff803`3995baea nt!KiRetireDpcList+0x4f0
    ffffd001`ab539c60 00000000`00000000 nt!KiIdleLoop+0x5a
    

    ^^ netbt.sys (MBT Transport driver) appears to be the possible problematic driver here.

    2: kd> .trap ffffd001`ab5396c0
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=fffff80339b50c41 rbx=0000000000000000 rcx=ffffd001ab525860
    rdx=fffff80339aea860 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff803398a9c20 rsp=ffffd001ab539850 rbp=ffffe001b1338e10
     r8=fffff80339b50c40  r9=0000000000000389 r10=0000000000000801
    r11=ffffd001ab5398a0 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei ng nz na po nc
    nt!KxWaitForLockOwnerShip+0x30:
    fffff803`398a9c20 488b4708        mov     rax,qword ptr [rdi+8] ds:00000000`00000008=????????????????
    

    2: kd> u @rip
    nt!KxWaitForLockOwnerShip+0x30:
    fffff803`398a9c20 488b4708        mov     rax,qword ptr [rdi+8]
    fffff803`398a9c24 a801            test    al,1
    fffff803`398a9c26 75e8            jne     nt!KxWaitForLockOwnerShip+0x20 (fffff803`398a9c10) <- jump
    fffff803`398a9c28 8bc3            mov     eax,ebx
    fffff803`398a9c2a 488b5c2430      mov     rbx,qword ptr [rsp+30h]
    fffff803`398a9c2f 4883c420        add     rsp,20h
    fffff803`398a9c33 5f              pop     rdi
    fffff803`398a9c34 c3              ret
    

    ^^ netbt.sys calls nt!IoAcquireCancelSpinLock which synchronizes cancelable-state transitions for IRPs in a multiprocessor-safe way. Afterwards, it appears that we're waiting for lock ownership, but it never happens, therefore we get the inevitable 0x133 bug check. With this said, something 3rd-party network related is likely causing conflicts.

    ----------------------

    Remove and replace McAfee with Windows 8's built-in Windows Defender for temporary troubleshooting purposes as it's likely causing NETBIOS conflicts:

    McAfee removal - http://service.mcafee.com/FAQDocument.aspx?id=TS101331

    Windows Defender (how to turn on after removal) - http://www.eightforums.com/tutorials/21962-windows-defender-turn-off-windows-8-a.html

    Regards,

    Patrick

    “Be kind whenever possible. It is always possible.” - Dalai Lama

    • Marked as answer by Jacob '-' Monday, April 28, 2014 12:41 PM
    Saturday, April 26, 2014 6:51 PM
  • I uninstalled McAfee when I first got my laptop (December 25th 2013) so I don't see how that could be causing it.

    I do have McAfee Central though. I'm not sure if that is what you are talking about.

    Thanks -Jacob


    • Edited by Jacob '-' Saturday, April 26, 2014 7:01 PM Another McAfee app was found
    Saturday, April 26, 2014 6:59 PM
  • There are a fair bit of McAfee drivers listed and loaded, so possibly. If you run the removal tool, are there options to remove? If so, run it. If not, uninstall McAfee Central.

    Regards,

    Patrick

    “Be kind whenever possible. It is always possible.” - Dalai Lama

    Saturday, April 26, 2014 7:04 PM
  • The McAfee remover is still going. It's been going on for about an hour. Is that normal?
    Saturday, April 26, 2014 8:02 PM
  • No, cancel it and boot into Safe Mode and run it there.

    Regards,

    Patrick

    “Be kind whenever possible. It is always possible.” - Dalai Lama

    Saturday, April 26, 2014 8:08 PM
  • It won't cancel because the bar is full but it is saying

    'Removing product MSC'

    EDIT

    The bar has moved back a fraction and still says 'Removing product MSC'

    • Edited by Jacob '-' Saturday, April 26, 2014 8:15 PM
    Saturday, April 26, 2014 8:11 PM
  • Ctrl+Shift+Esc > Details > sort by Name (aka Process/Image name) > find the process relating to the McAfee removal tool > right-click and End Task. If it stalls for a moment, keep attempting to end it until it asks you if you'd like to close program, and then click that. After that, boot into Safe Mode and run the removal tool.

    Regards,

    Patrick

    “Be kind whenever possible. It is always possible.” - Dalai Lama


    Saturday, April 26, 2014 8:15 PM
  • I ran the removal tool insafe mode. It said it could not get all of the permissions.

    EDIT

    The tool removed the software and I am now rebooting

    • Edited by Jacob '-' Saturday, April 26, 2014 8:38 PM
    Saturday, April 26, 2014 8:35 PM
  • Great work, Jacob. Please keep me updated now that McAfee is removed.

    Regards,

    Patrick


    “Be kind whenever possible. It is always possible.” - Dalai Lama

    Saturday, April 26, 2014 8:47 PM
  • Thanks man, you are amazing. I haven't had a BSOD at all since I used the tool :)

    Thanks

    -Jacob

    Sunday, April 27, 2014 10:42 AM
  • Thank you for the kind words, it was my pleasure! I am very glad to hear you are crash-free.

    If and when you are comfortable and feel your issue has been solved, I'd recommend marking the post of mine that answered your question as answered so this thread no longer shows up as requiring an answer.

    Regards,

    Patrick

    “Be kind whenever possible. It is always possible.” - Dalai Lama

    • Proposed as answer by ZigZag3143x Thursday, May 1, 2014 11:39 PM
    Sunday, April 27, 2014 6:02 PM