Random 0x133 BSODs Solved

Page 2 of 2 FirstFirst 12
  1. philc43's Avatar
    Posts : 3,824
    64bit Win 10 Pro ver 1809 Build 17763.253 and W10 Insider Build 18312
       1 Week Ago #11

    Providing the memory.dmp file was useful - it allows you to display the deferred procedure call (DPC) queues for the processor.

    Code:
    0: kd> !dpcs
    CPU Type      KDPC       Function
     0: Normal  : 0xffffa8031cc550e0 0xfffff8054574fd1c nvlddmkm
     0: Normal  : 0xfffff80538f83568 0xfffff8053aa999e0 nt!KiEntropyDpcRoutine
     0: Normal  : 0xfffff8053ae1eb60 0xfffff8053ab3ec50 nt!PpmCheckPeriodicStart
     0: Normal  : 0xfffff8053ae301e0 0xfffff8053aa95d40 nt!KiBalanceSetManagerDeferredRoutine
     0: Normal  : 0xffffa8031c99d788 0xfffff805424a66b0 ndis!ndisInterruptDpc
    The 0x133 stop code had first parameter = 1 which tells you that there are DPCs running from more than one driver and the one that shows up in the stack is not always the one responsible for the crash.

    If you continue to get BSOD events I would start looking at your network drivers since the other DPC was related to ndis.sys which is triggered by the network.
      My ComputersSystem Spec


  2. Posts : 22,677
    windows 10 professional version 1607 build 14393.969 64 bit
       1 Week Ago #12

    The ndis was also seen in the live kernel dump but there was no new network driver seen.

    So its a waiting period to see whether it was only the Nvidia GPU driver.

    The logs displayed only one bugcheck: 133 and there were many crashes.
    The logs displayed only one live kernel event: 144 and there were many crashes.

    More often when there is more than one misbehaving driver other bugchecks are seen.



    Code:
    0: kd> !running -t
    
    System Processors:  (000000000000000f)
      Idle Processors:  (0000000000000000)
    
           Prcbs             Current         (pri) Next            (pri) Idle
      0    fffff80419707180  ffffc9881c8a7080 (13)                       fffff8041b811400  ................
    
     # Child-SP          RetAddr           Call Site
    00 ffff8087`e2da7320 fffff804`1b8185c2 nt!IopLiveDumpEndMirroringCallback+0x7e
    01 ffff8087`e2da7370 fffff804`1b829f47 nt!MmDuplicateMemory+0x26e
    02 ffff8087`e2da7400 fffff804`1bad1bed nt!IopLiveDumpCaptureMemoryPages+0x7f
    03 ffff8087`e2da74c0 fffff804`1bac54b2 nt!IoCaptureLiveDump+0x289
    04 ffff8087`e2da7660 fffff804`1bac5bd0 nt!DbgkpWerCaptureLiveFullDump+0x13a
    05 ffff8087`e2da76c0 fffff804`1bac5301 nt!DbgkpWerProcessPolicyResult+0x30
    06 ffff8087`e2da76f0 ffff9c46`73bad112 nt!DbgkWerCaptureLiveKernelDump+0x1a1
    07 ffff8087`e2da7740 ffff9c46`73de99d5 win32kfull!CheckSessionPoolAllocations+0x8eaa2
    08 ffff8087`e2da7850 fffff804`1b9776d4 win32kbase!Win32KDriverUnload+0x525
    09 ffff8087`e2da7880 fffff804`1b91a34b nt!MiDereferenceSessionFinal+0x88
    0a ffff8087`e2da7920 fffff804`1b93b87e nt!MiDereferenceSession+0x3f
    0b ffff8087`e2da7950 fffff804`1b8984dd nt!MmCleanProcessAddressSpace+0x24a
    0c ffff8087`e2da79d0 fffff804`1b87de88 nt!PspRundownSingleProcess+0x129
    0d ffff8087`e2da7a50 fffff804`1b8a29b3 nt!PspExitThread+0x5c8
    0e ffff8087`e2da7b50 fffff804`1b34263f nt!PspTerminateThreadByPointer+0x53
    0f ffff8087`e2da7b90 fffff804`1b46bf9c nt!PspSystemThreadStartup+0x6f
    10 ffff8087`e2da7be0 00000000`00000000 nt!KiStartSystemThread+0x1c
    
      1    ffff9e817d869180  ffffc98810ca1680 (15)                       ffff9e817d879100  ................
    
     # Child-SP          RetAddr           Call Site
    00 ffff8087`df837c20 fffff804`1b3723a7 nt!IopLiveDumpCorralDpc+0x42
    01 ffff8087`df837c60 fffff804`1b3719ee nt!KiExecuteAllDpcs+0x2e7
    02 ffff8087`df837da0 fffff804`1b46b9a5 nt!KiRetireDpcList+0x1ae
    03 ffff8087`df837fb0 fffff804`1b46b790 nt!KxRetireDpcList+0x5
    04 ffff8087`dfff0220 fffff804`1b46ae7c nt!KiDispatchInterruptContinue
    05 ffff8087`dfff0250 fffff800`eb3babb6 nt!KiDpcInterrupt+0x2dc
    06 ffff8087`dfff03e0 fffff800`eb3bb54a dxgmms2!VIDMM_GLOBAL::EvictTemporaryAllocations+0x7a
    07 ffff8087`dfff0440 fffff800`eb3b5725 dxgmms2!VIDMM_GLOBAL::PageInOneAllocation+0x10a
    08 ffff8087`dfff0550 fffff800`eb3c531f dxgmms2!VIDMM_GLOBAL::InitContextAllocation+0x8d
    09 ffff8087`dfff0710 fffff800`eb3d3b64 dxgmms2!VIDMM_GLOBAL::ProcessDeferredCommand+0xa4f
    0a ffff8087`dfff0970 fffff800`eb3d3219 dxgmms2!VIDMM_WORKER_THREAD::Run+0x934
    0b ffff8087`dfff0b60 fffff804`1b342625 dxgmms2!VidMmWorkerThreadProc+0x9
    0c ffff8087`dfff0b90 fffff804`1b46bf9c nt!PspSystemThreadStartup+0x55
    0d ffff8087`dfff0be0 00000000`00000000 nt!KiStartSystemThread+0x1c
    
      2    ffff9e817d980180  ffffc98812e38040 (12)                       ffff9e817d990100  ................
    
     # Child-SP          RetAddr           Call Site
    00 ffff8087`df847c20 fffff804`1b3723a7 nt!IopLiveDumpCorralDpc+0x42
    01 ffff8087`df847c60 fffff804`1b3719ee nt!KiExecuteAllDpcs+0x2e7
    02 ffff8087`df847da0 fffff804`1b46b9a5 nt!KiRetireDpcList+0x1ae
    03 ffff8087`df847fb0 fffff804`1b46b790 nt!KxRetireDpcList+0x5
    04 ffff8087`e5d77490 fffff804`1b46ae7c nt!KiDispatchInterruptContinue
    05 ffff8087`e5d774c0 fffff800`e9201abf nt!KiDpcInterrupt+0x2dc
    06 ffff8087`e5d77650 fffff800`e92003f8 ndis!Ndis::BindRules::ReEnableTemporaryUnbind+0x4f
    07 ffff8087`e5d77730 fffff800`e920036e ndis!Ndis::BindRules::Apply+0x50
    08 ffff8087`e5d77830 fffff800`e9208533 ndis!Ndis::BindEngine::EndPolicyUpdates+0x22
    09 ffff8087`e5d77860 fffff800`e9208153 ndis!ndisMSetMiniportReadyForBinding+0x73
    0a ffff8087`e5d778a0 fffff804`1b99a1c1 ndis!ndisMiniportDeviceReadyNotification+0x123
    0b ffff8087`e5d77920 fffff804`1b9a0fc7 nt!PnpNotifyDriverCallback+0x7d
    0c ffff8087`e5d779d0 fffff804`1b86f180 nt!PnpNotifyDeviceClassChange+0x183
    0d ffff8087`e5d77a70 fffff804`1b36d91a nt!PnpDeviceEventWorker+0x2a0
    0e ffff8087`e5d77af0 fffff804`1b342625 nt!ExpWorkerThread+0x16a
    0f ffff8087`e5d77b90 fffff804`1b46bf9c nt!PspSystemThreadStartup+0x55
    10 ffff8087`e5d77be0 00000000`00000000 nt!KiStartSystemThread+0x1c
    
      3    ffff9e817da40180  ffffc988116c8040 (14)                       ffff9e817da50100  ................
    
     # Child-SP          RetAddr           Call Site
    00 ffff8087`df857c20 fffff804`1b3723a7 nt!IopLiveDumpCorralDpc+0x42
    01 ffff8087`df857c60 fffff804`1b3719ee nt!KiExecuteAllDpcs+0x2e7
    02 ffff8087`df857da0 fffff804`1b46b9a5 nt!KiRetireDpcList+0x1ae
    03 ffff8087`df857fb0 fffff804`1b46b790 nt!KxRetireDpcList+0x5
    04 ffff8087`e598f450 fffff804`1b46ae7c nt!KiDispatchInterruptContinue
    05 ffff8087`e598f480 fffff804`1b2ed939 nt!KiDpcInterrupt+0x2dc
    06 ffff8087`e598f610 fffff804`1b2edbd0 nt!ExAcquireFastMutexUnsafe+0xf9
    07 ffff8087`e598f660 fffff800`e8949f01 nt!FsRtlUninitializeOplock+0x50
    08 ffff8087`e598f6d0 fffff800`e8949cbe Ntfs!NtfsDeleteScb+0xd1
    09 ffff8087`e598f720 fffff800`e885b675 Ntfs!NtfsRemoveScb+0xbe
    0a ffff8087`e598f790 fffff800`e89499fd Ntfs!NtfsPrepareFcbForRemoval+0x75
    0b ffff8087`e598f7d0 fffff800`e885c5ea Ntfs!NtfsTeardownStructures+0x9d
    0c ffff8087`e598f850 fffff800`e894ce04 Ntfs!NtfsDecrementCloseCounts+0xaa
    0d ffff8087`e598f890 fffff800`e895b3df Ntfs!NtfsCommonClose+0x464
    0e ffff8087`e598f970 fffff800`e895b1f2 Ntfs!NtfsFspCloseInternal+0x1df
    0f ffff8087`e598fac0 fffff804`1b36d91a Ntfs!NtfsFspClose+0x12
    10 ffff8087`e598faf0 fffff804`1b342625 nt!ExpWorkerThread+0x16a
    11 ffff8087`e598fb90 fffff804`1b46bf9c nt!PspSystemThreadStartup+0x55
    12 ffff8087`e598fbe0 00000000`00000000 nt!KiStartSystemThread+0x1c
      My ComputerSystem Spec

  3.    1 Week Ago #13

    It has been a few days and I haven't had any crashes yet. Looks like either updating the UEFI or completely wiping and reinstalling GPU drivers did the trick. Thank you for the assistance!
      My ComputerSystem Spec

  4. philc43's Avatar
    Posts : 3,824
    64bit Win 10 Pro ver 1809 Build 17763.253 and W10 Insider Build 18312
       1 Week Ago #14

    That's good news - hopefully it is sorted but if you do get any new BSOD just post a new set of log files and we will take another look.
      My ComputersSystem Spec


  5. Posts : 22,677
    windows 10 professional version 1607 build 14393.969 64 bit
       1 Week Ago #15

    Nice to see it sorted.
    You are welcome.
      My ComputerSystem Spec


 
Page 2 of 2 FirstFirst 12

Related Threads
Random BSODs in BSOD Crashes and Debugging
Hello, i was hoping somebody could help me with some issues i've been having, this is the second BSOD i have had in a while, they both seem to come at random, what doesn't change however is the error code; DPC Watchdog Violation. From what i can...
Hi, I would really appreciate it if anyone could shed any light on this. The PC was originally Windows 7 and I upgraded to Windows 10 last year. The crashes seem to be random, sometimes when it's sitting idle, sometimes whilst I'm working. ...
Random BSODs on new PC in BSOD Crashes and Debugging
Hi, i'm getting random BSOD erros, on a new computer. I already ran the memtest 86, no erros, and i can't seem to solve the problem. Here is the dump files...
Random bsods in BSOD Crashes and Debugging
Recently i started having random bsods...tried reseting windows and deleting and reinstalling video drivers and still nothing...i attached minidump files...pls help
Random BSODs in BSOD Crashes and Debugging
Hi folks! I installed Win 10 on my home server and it keeps crashing all the time with random BSODs (with a bunch of different error messages). Before that, it was running fine on Win Home Server 2011. I tried a bunch of driver combinations...
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 20:38.
Find Us