Windows 10: BugCheck 133, {0, 501, 500, fffff80208a51378}

Discus and support BugCheck 133, {0, 501, 500, fffff80208a51378} in Windows 10 BSOD Crashes and Debugging to solve the problem; Bonjour à la communauté, Voici ci-dessous un MEMORY.DMP que je n'arrive pas à vraiment analyser et trouver la source du pb. L'utilisateur a ce pb... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by Meda Eric, Jul 5, 2019.

  1. Meda Eric Win User

    BugCheck 133, {0, 501, 500, fffff80208a51378}


    Bonjour à la communauté,


    Voici ci-dessous un MEMORY.DMP que je n'arrive pas à vraiment analyser et trouver la source du pb. L'utilisateur a ce pb chaque jour. Est-ce que quelqu'un(e) pourrait me conseiller. Merci d'avance. Eric


    Hello to the community,

    Below is a MEMORY. DMP that I can not really analyze and find the source of the pb. The user has this pb every day. Could someone advise me? Thank you in advance. Eric.


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


    Microsoft (R) Windows Debugger Version 10.0.17763.132 X86
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\Users\emeda\Desktop\Simon\MEMORY.DMP]
    Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.

    Symbol search path is: srv*
    Executable search path is:
    Windows 10 Kernel Version 17134 MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 17134.1.amd64fre.rs4_release.180410-1804
    Machine Name:
    Kernel base = 0xfffff802`08605000 PsLoadedModuleList = 0xfffff802`089b2170
    Debug session time: Fri Jul 5 10:24:14.436 2019 (UTC + 2:00)
    System Uptime: 0 days 23:54:58.547
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ................................................................
    ..........................................
    Loading User Symbols

    Loading unloaded module list
    .............................
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 133, {0, 501, 500, fffff80208a51378}

    Page 20018cbf8 too large to be in the dump file.
    *************************************************************************
    *** ***
    *** ***
    *** Either you specified an unqualified symbol, or your debugger ***
    *** doesn't have full symbol information. Unqualified symbol ***
    *** resolution is turned off by default. Please either specify a ***
    *** fully qualified symbol module!symbolname, or enable resolution ***
    *** of unqualified symbols by typing ".symopt- 100". Note that ***
    *** enabling unqualified symbol resolution with network symbol ***
    *** server shares in the symbol path may cause the debugger to ***
    *** appear to hang for long periods of time when an incorrect ***
    *** symbol name is typed or the network symbol server is down. ***
    *** ***
    *** For some commands to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: TickPeriods ***
    *** ***
    *************************************************************************
    Probably caused by : hidusb.sys ( hidusb!HumInternalIoctl+267 )

    Followup: MachineOwner
    ---------

    0: kd> !analyze -v
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    DPC_WATCHDOG_VIOLATION (133)
    The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
    or above.
    Arguments:
    Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
    component can usually be identified with a stack trace.
    Arg2: 0000000000000501, The DPC time count (in ticks).
    Arg3: 0000000000000500, The DPC time allotment (in ticks).
    Arg4: fffff80208a51378, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
    additional information regarding this single DPC timeout

    Debugging Details:
    ------------------

    *************************************************************************
    *** ***
    *** ***
    *** Either you specified an unqualified symbol, or your debugger ***
    *** doesn't have full symbol information. Unqualified symbol ***
    *** resolution is turned off by default. Please either specify a ***
    *** fully qualified symbol module!symbolname, or enable resolution ***
    *** of unqualified symbols by typing ".symopt- 100". Note that ***
    *** enabling unqualified symbol resolution with network symbol ***
    *** server shares in the symbol path may cause the debugger to ***
    *** appear to hang for long periods of time when an incorrect ***
    *** symbol name is typed or the network symbol server is down. ***
    *** ***
    *** For some commands to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: TickPeriods ***
    *** ***
    *************************************************************************

    KEY_VALUES_STRING: 1


    STACKHASH_ANALYSIS: 1

    TIMELINE_ANALYSIS: 1


    DUMP_CLASS: 1

    DUMP_QUALIFIER: 401

    BUILD_VERSION_STRING: 17134.1.amd64fre.rs4_release.180410-1804

    SYSTEM_MANUFACTURER: HP

    SYSTEM_PRODUCT_NAME: HP ProBook 430 G5

    SYSTEM_SKU: 1LR38AV

    BIOS_VENDOR: HP

    BIOS_VERSION: Q85 Ver. 01.06.00

    BIOS_DATE: 01/03/2019

    BASEBOARD_MANUFACTURER: HP

    BASEBOARD_PRODUCT: 8377

    BASEBOARD_VERSION: KBC Version 02.32.00

    DUMP_TYPE: 1

    BUGCHECK_P1: 0

    BUGCHECK_P2: 501

    BUGCHECK_P3: 500

    BUGCHECK_P4: fffff80208a51378

    DPC_TIMEOUT_TYPE: SINGLE_DPC_TIMEOUT_EXCEEDED

    CPU_COUNT: 8

    CPU_MHZ: 7c8

    CPU_VENDOR: GenuineIntel

    CPU_FAMILY: 6

    CPU_MODEL: 8e

    CPU_STEPPING: a

    CPU_MICROCODE: 6,8e,a,0 (F,M,S,R) SIG: 9A'00000000 (cache) 9A'00000000 (init)

    BLACKBOXBSD: 1 (!blackboxbsd)


    BLACKBOXPNP: 1 (!blackboxpnp)


    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

    BUGCHECK_STR: 0x133

    PROCESS_NAME: System

    CURRENT_IRQL: d

    ANALYSIS_SESSION_HOST: DSI-9018414

    ANALYSIS_SESSION_TIME: 07-05-2019 11:23:58.0766

    ANALYSIS_VERSION: 10.0.17763.132 x86fre

    TRAP_FRAME: fffff8020bcbeac0 -- (.trap 0xfffff8020bcbeac0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=00000013bf630003 rbx=0000000000000000 rcx=fffff802064cee40
    rdx=ffff9184aee9b720 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff802087b7777 rsp=fffff8020bcbec50 rbp=fffff8020bcbece9
    r8=ffff9184aee9b720 r9=ffff91842ddfaaa0 r10=fffff802064cee40
    r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0 nv up ei ng nz na pe nc
    nt!ExpInterlockedPopEntrySListFault:
    fffff802`087b7777 498b08 mov rcx,qword ptr [r8] ds:ffff9184`aee9b720=????????????????
    Resetting default scope

    LAST_CONTROL_TRANSFER: from fffff80208800da1 to fffff802087afab0

    STACK_TEXT:
    fffff802`0bcceb78 fffff802`08800da1 : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx
    fffff802`0bcceb80 fffff802`0869a8bd : 00003f25`c1942a39 fffff802`064ce180 00000000`00000246 00000000`005414a3 : nt!KeAccumulateTicks+0x1629c1
    fffff802`0bccebe0 fffff802`0869b9a3 : fffff780`00000340 00000000`00000000 00000000`005414a3 00000000`00000000 : nt!KiUpdateRunTime+0x5d
    fffff802`0bccec30 fffff802`08f5a883 : 00003f25`c194191a 00000000`00000098 00000000`00000000 fffff802`0bcbe930 : nt!KeClockInterruptNotify+0x8f3
    fffff802`0bccef40 fffff802`0860f925 : fffff802`08fbd000 ffff9184`14ba1700 ffff9184`14ba1700 fffff802`087b112b : hal!HalpTimerClockInterrupt+0x63
    fffff802`0bccef70 fffff802`087b136a : fffff802`0bcbe9b0 fffff802`08fbd000 00000000`55646948 00000000`00000200 : nt!KiCallInterruptServiceRoutine+0xa5
    fffff802`0bccefb0 fffff802`087b1857 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xea
    fffff802`0bcbe930 fffff802`087bd191 : fffff802`0bcbead0 0000000f`5155c543 00000001`ffffffff fffffff6`00000002 : nt!KiInterruptDispatchNoLockNoEtw+0x37
    fffff802`0bcbeac0 fffff802`087b7777 : fffff802`064cee40 fffff802`088f0086 fffff802`0bcbed29 fffff802`0868b561 : nt!KiPageFault+0x2d1
    fffff802`0bcbec50 fffff802`088f0086 : fffff802`0bcbed29 fffff802`0868b561 00000000`00000103 fffff80e`b8661c4e : nt!ExpInterlockedPopEntrySListFault
    fffff802`0bcbec60 fffff80e`bc7b1277 : 00000000`00000000 fffff802`0bcbee50 ffff9184`55646948 fffff802`0868c0bb : nt!ExAllocatePoolWithTag+0x2f6
    fffff802`0bcbed50 fffff80e`bb1a76a2 : ffff9184`31ff5820 fffff80e`bb1a96d0 ffff9184`4211c1b0 00006e7b`cfdcc302 : hidusb!HumInternalIoctl+0x267
    fffff802`0bcbf040 fffff80e`bb1aa100 : ffff9184`4211c1d0 fffff80e`bb1ba1f0 ffff9184`3cce1010 fffff802`0bcbf0c8 : HIDCLASS!HidpCallDriver+0xa2
    fffff802`0bcbf0b0 fffff80e`bb1a9b93 : ffff9184`4211c1d0 00000000`00000007 ffff9184`3cce1010 ffff9184`00000008 : HIDCLASS!HidpSubmitInterruptRead+0x124
    fffff802`0bcbf120 fffff802`0868b01f : ffff9184`3cce1010 ffff9184`3cce1010 fffff802`0bcbf201 ffff9184`3cce1400 : HIDCLASS!HidpInterruptReadComplete+0x493
    fffff802`0bcbf1c0 fffff802`0868aee7 : ffff9184`1d447e10 00000000`00000200 fffff80e`b85fde40 00000000`0000000a : nt!IopfCompleteRequest+0x11f
    fffff802`0bcbf2e0 fffff80e`b8559627 : ffff9184`2db048e0 ffff9184`3cce1010 00000000`00000002 ffff9184`414c2a80 : nt!IofCompleteRequest+0x17
    fffff802`0bcbf310 fffff80e`b85572fb : fffff802`00000001 fffff80e`00000000 00000000`ffffff02 ffff9184`00000010 : Wdf01000!FxRequest::CompleteInternal+0x247 [minkernel\wdf\framework\shared\core\fxrequest.cpp @ 869]
    fffff802`0bcbf3d0 fffff80e`be6bf336 : 00000000`ffffff02 ffff9184`2db048e0 ffff9184`414c2e60 ffff9184`414c2e60 : Wdf01000!imp_WdfRequestComplete+0x8b [minkernel\wdf\framework\shared\core\fxrequestapi.cpp @ 436]
    fffff802`0bcbf430 fffff80e`be6bd469 : ffff9184`2db04a80 00000000`00000001 ffff9184`2db04b10 fffff802`0bcbf718 : USBXHCI!Bulk_Transfer_CompleteCancelable+0x182
    fffff802`0bcbf490 fffff80e`be6bbde0 : 00000000`00000001 ffff9184`1d02e710 fffff802`064d3f00 fffff802`0869e1c5 : USBXHCI!Bulk_ProcessTransferEventWithED1+0x40d
    fffff802`0bcbf550 fffff80e`be6b12c3 : 000001a3`a1bb9867 00000000`00000006 ffffa0fa`ba9d13f3 fffff802`08744187 : USBXHCI!Bulk_EP_TransferEventHandler+0x10
    fffff802`0bcbf580 fffff80e`be6a4608 : fffff802`064ce180 00000000`00000004 ffff9184`1d43b2f0 fffff802`0bcbf681 : USBXHCI!TR_TransferEventHandler+0x17
    fffff802`0bcbf5b0 fffff80e`be6c37ae : fffff802`0bcbf718 fffff802`0bcbf6e8 00000000`00000000 fffff802`0bcbf6f0 : USBXHCI!Endpoint_TransferEventHandler+0x148
    fffff802`0bcbf640 fffff80e`be6a744d : ffff9184`1d43b220 fffff802`0bcbf739 ffff9184`1d43b2f0 00000000`0000001b : USBXHCI!UsbDevice_TransferEventHandler+0x92
    fffff802`0bcbf6a0 fffff80e`be6a7e6c : 00000000`064ce180 00000000`00000001 00000000`00140001 ffff9184`1d43b020 : USBXHCI!Interrupter_DeferredWorkProcessor+0x4c5
    fffff802`0bcbf7a0 fffff80e`b8551fad : 00000000`00000001 fffff802`08876b05 fffff802`064ce180 ffff9184`2b652040 : USBXHCI!Interrupter_WdfEvtInterruptDpc+0xc
    fffff802`0bcbf7d0 fffff802`08698d97 : 000000c8`6ad09500 fffff802`0bcbf910 00000000`0002621a fffff802`08642e0a : Wdf01000!FxInterrupt::_InterruptDpcThunk+0x9d [minkernel\wdf\framework\shared\irphandlers\pnp\km\interruptobjectkm.cpp @ 410]
    fffff802`0bcbf810 fffff802`086983eb : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExecuteAllDpcs+0x2e7
    fffff802`0bcbf950 fffff802`087b31ea : 00000000`00000000 fffff802`064ce180 00000000`001a6560 fffff802`08a6f400 : nt!KiRetireDpcList+0x1db
    fffff802`0bcbfb60 00000000`00000000 : fffff802`0bcc0000 fffff802`0bcb9000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a


    THREAD_SHA1_HASH_MOD_FUNC: 678b46f91a9f0350262204d52322187bcb8c6baa

    THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 033c468eccd0781a514f5a32f3bb73e19decd74b

    THREAD_SHA1_HASH_MOD: 7c5f273d5a4e752ffaf5e3ceb2b5eb5ed43d4464

    FOLLOWUP_IP:
    hidusb!HumInternalIoctl+267
    fffff80e`bc7b1277 488bd8 mov rbx,rax

    FAULT_INSTR_CODE: 48d88b48

    SYMBOL_STACK_INDEX: b

    SYMBOL_NAME: hidusb!HumInternalIoctl+267

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: hidusb

    IMAGE_NAME: hidusb.sys

    DEBUG_FLR_IMAGE_TIMESTAMP: 6c1deea7

    STACK_COMMAND: .thread ; .cxr ; kb

    BUCKET_ID_FUNC_OFFSET: 267

    FAILURE_BUCKET_ID: 0x133_DPC_hidusb!HumInternalIoctl

    BUCKET_ID: 0x133_DPC_hidusb!HumInternalIoctl

    PRIMARY_PROBLEM_CLASS: 0x133_DPC_hidusb!HumInternalIoctl

    TARGET_TIME: 2019-07-05T08:24:14.000Z

    OSBUILD: 17134

    OSSERVICEPACK: 0

    SERVICEPACK_NUMBER: 0

    OS_REVISION: 0

    SUITE_MASK: 272

    PRODUCT_TYPE: 1

    OSPLATFORM_TYPE: x64

    OSNAME: Windows 10

    OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS

    OS_LOCALE:

    USER_LCID: 0

    OSBUILD_TIMESTAMP: 2019-06-07 07:21:36

    BUILDDATESTAMP_STR: 180410-1804

    BUILDLAB_STR: rs4_release

    BUILDOSVER_STR: 10.0.17134.1.amd64fre.rs4_release.180410-1804

    ANALYSIS_SESSION_ELAPSED_TIME: ebd

    ANALYSIS_SOURCE: KM

    FAILURE_ID_HASH_STRING: km:0x133_dpc_hidusb!huminternalioctl

    FAILURE_ID_HASH: {270658f1-eec8-fcb0-8033-b5ec94c2add6}

    Followup: MachineOwner

    :)
     
    Meda Eric, Jul 5, 2019
    #1
  2. 新艳刘 Win User

    DPC_WATCHDOG_VIOLATION (133) IntcDAud.sys ntkrnlmp.exe firefox.exe

    *******************************************************************************

    * *

    * Bugcheck Analysis *

    * *

    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 133, {0, 501, 500, fffff801725fe348}

    Probably caused by : ntkrnlmp.exe ( nt!KeAccumulateTicks+124ea2 )

    Followup: MachineOwner
     
    新艳刘, Jul 5, 2019
    #2
  3. Ztruker Win User
    Silent BSOD: bugcheck was: 0x00000133


    Dump indicates a problem with nldrv.sys.
    Code:
    Code:
    BugCheck 133, {0, 501, 500, 0} *** WARNING: Unable to verify timestamp for nldrv.sys *** ERROR: Module load completed but symbols could not be loaded for nldrv.sys
    This belongs to Locktime Software NetLimiter. Uninstall it and see if the problem goes away.
     
    Ztruker, Jul 5, 2019
    #3
  4. lifetec Win User

    BugCheck 133, {0, 501, 500, fffff80208a51378}

    Daily BSOD in hal.dll with bugcheck code 133 since last windows update


    All 5 dumpfiles from december blame:
    Code:
    Code:
      BugCheck 133, {0, 501, 500, 0}  *** WARNING: Unable to verify timestamp for nvstor.sys *** ERROR: Module load completed but symbols could not be loaded for nvstor.sys Probably caused by : nvstor.sys ( nvstor+7468 )
    Timestamp: Mon Apr 21 20:34:03 2014
    Driver Description: nVidia Storage Drivers
    Driver Update Site: Download Drivers | NVIDIA
    First look on the supportpage of your mobo.
     
    lifetec, Jul 5, 2019
    #4
Thema:

BugCheck 133, {0, 501, 500, fffff80208a51378}

Loading...
  1. BugCheck 133, {0, 501, 500, fffff80208a51378} - Similar Threads - BugCheck 133 501

  2. BugCheck 133, {0, 501, 500, fffff8001dafb320}

    in Windows 10 Gaming
    BugCheck 133, {0, 501, 500, fffff8001dafb320}: Hello All,I had BSOD on a Dell Precision Tower 5810 frequently. I have the dump file, but it is not clear for me what occurs the BSOD. I assume that it can be some GPU or USB driver, but could you please help me to understand the problem?Microsoft R Windows Debugger Version...
  3. BugCheck 133, {0, 501, 500, fffff8001dafb320}

    in Windows 10 Software and Apps
    BugCheck 133, {0, 501, 500, fffff8001dafb320}: Hello All,I had BSOD on a Dell Precision Tower 5810 frequently. I have the dump file, but it is not clear for me what occurs the BSOD. I assume that it can be some GPU or USB driver, but could you please help me to understand the problem?Microsoft R Windows Debugger Version...
  4. BugCheck 133, {0, 501, 500, fffff8001dafb320}

    in Windows 10 BSOD Crashes and Debugging
    BugCheck 133, {0, 501, 500, fffff8001dafb320}: Hello All,I had BSOD on a Dell Precision Tower 5810 frequently. I have the dump file, but it is not clear for me what occurs the BSOD. I assume that it can be some GPU or USB driver, but could you please help me to understand the problem?Microsoft R Windows Debugger Version...
  5. SK hynix BC 501

    in Windows 10 Gaming
    SK hynix BC 501: HelloI have a new warning message on my HP Pavillion laptop Windows 11 : "SK Hynix BC501 HFM512GDJTNG-8310 Fiabilité détérioréeDurée restante estimée : 4%"What does it mean please ? what will I do ?Thank you for your helpHelene...
  6. SK hynix BC 501

    in Windows 10 Software and Apps
    SK hynix BC 501: HelloI have a new warning message on my HP Pavillion laptop Windows 11 : "SK Hynix BC501 HFM512GDJTNG-8310 Fiabilité détérioréeDurée restante estimée : 4%"What does it mean please ? what will I do ?Thank you for your helpHelene...
  7. Event 41 Bugcheck code 0

    in Windows 10 BSOD Crashes and Debugging
    Event 41 Bugcheck code 0: Hello, I am writing because I have been having intermittent Event 41 Bugcheck code 0s for the past several months since building my computer. I recently got a blue screen crash with event 41 bugcheck code 80 which is when I noticed the issues and dug into the event viewer....
  8. BSOD - error codes 109, a, 133, 133, 133

    in Windows 10 BSOD Crashes and Debugging
    BSOD - error codes 109, a, 133, 133, 133: I have a new gaming pc just got delivered and it's BSOD 5 times. specs: Device name DESKTOP-3RG8SD0 Processor IntelR CoreTM i9-10900K CPU @ 3.70GHz 3.70 GHz Installed RAM 16.0 GB 15.9 GB usable GPU : Nvidia 3070 System type 64-bit operating system, x64-based...
  9. Windows 10 Volume MAK Licensing 0/500 Seats?

    in Windows 10 Updates and Activation
    Windows 10 Volume MAK Licensing 0/500 Seats?: I am looking at my Volume Licensing page at https://www.microsoft.com/Licensing/servicecenter/home.aspx# and it shows under my licensing agreement that we have multiple windows 10 MAKs with 0/500 keys, how do i find out if these are valid keys? [ATTACH]...
  10. HRESULT 0x80040210 UPnP error 501

    in Windows 10 Drivers and Hardware
    HRESULT 0x80040210 UPnP error 501: Whenever I try to transmit any video file to my smart TV I get this error: HRESULT: 0x80040210 UPnP error: 501 I click on the file and use the transmit option, and my TV shows up on the device list, but it won`t start, just give me that error. What does that mean?...

Users found this page by searching for:

  1. BugCheck 133 {0 501 500

    ,
  2. fffff80208a51378