Windows 8 and 8.1 Forums


Daily BSOD: 0x133, MsMpEng.exe SINGLE_DPC_TIMEOUT_EXCEEDED

  1. #1


    Posts : 18
    Windows 8.1

    Daily BSOD: 0x133, MsMpEng.exe SINGLE_DPC_TIMEOUT_EXCEEDED


    So I am having a daily problem of my computer blue screening. It almost always happens at night, and it is not consistent at the same time and it can skip days.

    This problem has survived a complete reinstall of my operating system. I'm hoping it is still a driver issue and not a hardware issue, because I reinstalled basically everything to get it back where I needed it. Almost all software was reinstalled. After reinstalling Windows, the problem stopped for about a week. Once it started again, there was no defining reason for it. All of my drivers I would use were installed a week before. The error code was the same as before, no real change.

    I have replaced hardware to attempt to fix this issue (and simply upgrade). The following items were upgraded when I reinstalled my operating system on this computer:

    - New SSD (Samsung SSD 850 Pro replaced a SanDisk SSD. The SanDisk still resides in my computer, but I did have it removed for a few days and the bluescreen still occured)
    - New Video Cards (2x nVidia 670 replaced for 2x nVidia 780. Neither video card setup runs in SLI since I drive 6 monitors with them)
    - New Memory (12gb upgraded to 24gb. DIMMs have not been mixed and matched. It was a full pull and replace of all memory. 24gb is the max this motherboard supports)

    Download of BSOD Zip File Requested: Attachment 56999

    Please note that I have edited the hosts.txt file to remove some sensitive data. I use that file to test out DNS changes for work. I have also included a "windbg-analysis.txt" file where I ran `!analyze -v` in WinDBG on the MEMORY.DMP in the \Windows folder.

    Edit: I have also run stress tests on the processor and video card for over 12 hours each. Both tests and the memory diagnostics passed with flying colors.

    Edit 2: I have double checked the firmware on each SSD I have installed in my system. All are up to date and current as of a month ago.

    Edit 3: Just installed the latest version of the nvidia video driver. (again after an update from nvidia). Blue screen occured 2 hours later.
    Last edited by slickplaid; 28 Jan 2015 at 08:00.

      My System SpecsSystem Spec

  2. #2


    India
    Posts : 2,097
    Windows 8.1 Industry Pro B-)


    Hi Slickplaid & Welcome to the forums ^_^,

    I have analysed your dump files and below has been provided an analysis of the same for informative purposes :-

    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: 0000000000000000
    So, according to the Bugcheck, the DPC (Deferred Procedure Call) or the ISR (Interrupt Service Routine) took 501 ticks to respond but the system only allowed 500 ticks to respond and hence the bugcheck.

    Below is a stack trace of the dump file -
    Code:
    1: kd> knL
     # Child-SP          RetAddr           Call Site
    00 ffffd001`80dfec88 fffff800`cfba93c8 nt!KeBugCheckEx
    01 ffffd001`80dfec90 fffff800`cfab92a1 nt! ?? ::FNODOBFM::`string'+0x2c418
    02 ffffd001`80dfed20 fffff800`d01b87b5 nt!KeClockInterruptNotify+0x91
    03 ffffd001`80dfef40 fffff800`cfafd4b3 hal!HalpTimerClockIpiRoutine+0x15
    04 ffffd001`80dfef70 fffff800`cfb6df2a nt!KiCallInterruptServiceRoutine+0xa3
    05 ffffd001`80dfefb0 fffff800`cfb6e89b nt!KiInterruptSubDispatchNoLockNoEtw+0xea
    06 ffffd000`948a1da0 fffff800`cfb2bcc2 nt!KiInterruptDispatchNoLockNoEtw+0xfb
    07 ffffd000`948a1f30 fffff800`cfb703f7 nt!MiJumpStackTarget+0x72
    08 ffffd000`948a1f80 fffff800`cfb703bd nt!KxSwitchKernelStackCallout+0x27
    09 ffffd001`80df7a70 fffff800`cfa5c48d nt!KiSwitchKernelStackContinue
    0a ffffd001`80df7a90 fffff800`cfb2bc3b nt!KeExpandKernelStackAndCalloutInternal+0x2fd
    0b ffffd001`80df7b80 fffff800`cfac9580 nt!MiDoStackCopy+0xbb
    0c ffffd001`80df7be0 fffff800`cfac8837 nt!KiExecuteAllDpcs+0x1b0
    0d ffffd001`80df7d30 fffff800`cfb6fbd5 nt!KiRetireDpcList+0xd7
    0e ffffd001`80df7fb0 fffff800`cfb6f9d9 nt!KxRetireDpcList+0x5
    0f ffffd000`9580ac10 00000000`00000000 nt!KiDispatchInterruptContinue
    Seems like we are out of luck because the dump file did not catch the faulting driver. Below is a list of 3rd party drivers present on your system -
    Code:
    **************************Sun Jan 25 16:05:11.143 2015 (UTC + 5:30)**************************
    PxHlpa64.sys                Tue Apr 24 22:56:29 2012 (4F96E245)
    Rt630x64.sys                Fri May 10 15:29:08 2013 (518CC4EC)
    rtwlanu.sys                 Wed Jul 10 20:18:31 2013 (51DD743F)
    ceusbaud.sys                Tue Jul 16 22:30:10 2013 (51E57C1A)
    intelppm.sys                Thu Aug 22 14:16:35 2013 (5215CFEB)
    dump_storahci.sys           Thu Aug 22 17:10:39 2013 (5215F8B7)
    nvhda64v.sys                Thu Nov 28 19:08:09 2013 (52974741)
    nvlddmkm.sys                Wed Jul  2 23:12:02 2014 (53B4446A)
    wachidrouter.sys            Tue Oct  7 05:16:58 2014 (543329F2)
    wacomrouterfilter.sys       Tue Oct  7 05:17:05 2014 (543329F9)
    VBoxEhciR0.r0               Fri Nov 21 19:33:50 2014 (546F4646)
    VBoxDDR0.r0                 Mon Nov 24 16:36:09 2014 (54731121)
    VBoxDD2R0.r0                Mon Nov 24 16:36:09 2014 (54731121)
    VBoxNetAdp.sys              Mon Nov 24 16:36:09 2014 (54731121)
    VBoxNetFlt.sys              Mon Nov 24 16:36:09 2014 (54731121)
    VBoxUSBMon.sys              Mon Nov 24 16:36:09 2014 (54731121)
    VMMR0.r0                    Mon Nov 24 16:37:16 2014 (54731164)
    VBoxDrv.sys                 Mon Nov 24 16:37:17 2014 (54731165)
    http://www.carrona.org/drivers/driver.php?id=PxHlpa64.sys
    http://www.carrona.org/drivers/driver.php?id=Rt630x64.sys
    http://www.carrona.org/drivers/driver.php?id=rtwlanu.sys
    ceusbaud.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
    http://www.carrona.org/drivers/driver.php?id=intelppm.sys
    http://www.carrona.org/drivers/driver.php?id=dump_storahci.sys
    http://www.carrona.org/drivers/driver.php?id=nvhda64v.sys
    http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
    http://www.carrona.org/drivers/driver.php?id=wachidrouter.sys
    http://www.carrona.org/drivers/driver.php?id=wacomrouterfilter.sys
    VBoxEhciR0.r0 - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
    http://www.carrona.org/drivers/driver.php?id=VBoxDDR0.r0
    http://www.carrona.org/drivers/driver.php?id=VBoxDD2R0.r0
    http://www.carrona.org/drivers/driver.php?id=VBoxNetAdp.sys
    http://www.carrona.org/drivers/driver.php?id=VBoxNetFlt.sys
    http://www.carrona.org/drivers/driver.php?id=VBoxUSBMon.sys
    http://www.carrona.org/drivers/driver.php?id=VMMR0.r0
    http://www.carrona.org/drivers/driver.php?id=VBoxDrv.sys

    Kindly follow the below steps, one step at a time -


    1. Kindly disconnect the CEntrance USB Audio Device physically from the system till we are troubleshooting the system.
    2. Did you experience this issue while using Windows 7 as well? I am asking this because the BIOS is very old on your system and it may not be compatible with Windows 8.1.
    3. Update the drivers highlighted in BLACK,BOLD & Underline.


    Let me know how it goes ^_^

    -Pranav
      My System SpecsSystem Spec

  3. #3


    Posts : 18
    Windows 8.1


    1. I have disconnected the CEntrance USB Audio device (HiFi-M8) and will not reconnect it until it has been ruled out.
    2. I did experience some issues in Windows 7. They were related to an older video card setup that I had, when I was previously using ATI graphics cards, and once I switched to nVidia all problems ceased.
    3. The following drivers have been updated:
      1. http://www.carrona.org/drivers/driver.php?id=Rt630x64.sys - Upgraded to version 8.36.826.2014
      2. http://www.carrona.org/drivers/driver.php?id=rtwlanu.sys - Upgraded driver, and also unplugged the USB module until troubleshooting is resolved.
      3. ceusbaud.sys - Current, no update available. CEntrance Driver. Product disconnected until troubleshooting is resolved.
      4. http://www.carrona.org/drivers/driver.php?id=dump_storahci.sys - Windows update ran. Unsure if driver was updated or not.
      5. http://www.carrona.org/drivers/driver.php?id=nvhda64v.sys - Used nVidia's update manager to update this driver.
      6. http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys - Used nVidia's update manager to update this driver.
      7. Wacom Tablet Software up-to-date
        1. http://www.carrona.org/drivers/driver.php?id=wachidrouter.sys
        2. http://www.carrona.org/drivers/driver.php?id=wacomrouterfilter.sys

      8. VirtualBox is the most up-to-date version. The following are part of this application:
        1. VBoxEhciR0.r0 - VirtualBox, I have the latest version installed.
        2. http://www.carrona.org/drivers/driver.php?id=VBoxDDR0.r0
        3. http://www.carrona.org/drivers/driver.php?id=VBoxDD2R0.r0
        4. http://www.carrona.org/drivers/driver.php?id=VBoxNetAdp.sys
        5. http://www.carrona.org/drivers/driver.php?id=VBoxNetFlt.sys
        6. http://www.carrona.org/drivers/driver.php?id=VBoxUSBMon.sys
        7. http://www.carrona.org/drivers/driver.php?id=VMMR0.r0
        8. http://www.carrona.org/drivers/driver.php?id=VBoxDrv.sys

    4. ​The following drivers were not updated or an upgrade could not be found:
      1. http://www.carrona.org/drivers/driver.php?id=intelppm.sys - Ran Intel's driver update utility. Was unable to find a proper update canidate for this driver.
      2. http://www.carrona.org/drivers/driver.php?id=PxHlpa64.sys
        Unknown which program is supplying this driver. The only software application in that list I have installed is Adobe Lightroom, and it is currently at the newest version available according to Adobe's update manager. I do not have Roxio or any other application in that list.

    Once another crash happens, I will run the data gathering utility again with the new dump information for review.
      My System SpecsSystem Spec

  4. #4


    Posts : 18
    Windows 8.1


    Just had my computer bluescreen again.

    Here is the crash info, along with some information from WinDBG:

    Code:
    7: 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: 0000000000000000
    
    
    Debugging Details:
    ------------------
    
    
    
    
    DPC_TIMEOUT_TYPE:  SINGLE_DPC_TIMEOUT_EXCEEDED
    
    
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    
    
    BUGCHECK_STR:  0x133
    
    
    PROCESS_NAME:  chrome.exe
    
    
    CURRENT_IRQL:  d
    
    
    ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre
    
    
    LAST_CONTROL_TRANSFER:  from fffff8038a40b3c8 to fffff8038a3ceaa0
    
    
    STACK_TEXT:  
    ffffd001`f0feac88 fffff803`8a40b3c8 : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx
    ffffd001`f0feac90 fffff803`8a31b2a1 : 00000000`00000000 00000000`0066f8c5 ffff252e`91230969 fffff801`4143a226 : nt! ?? ::FNODOBFM::`string'+0x2c418
    ffffd001`f0fead20 fffff803`8a2167b5 : 0000ff9a`3b98b196 00000000`00000000 0000ff9a`3b98f057 00000000`00000000 : nt!KeClockInterruptNotify+0x91
    ffffd001`f0feaf40 fffff803`8a35f4b3 : ffffd000`2857f000 00000000`00000000 ffffd001`f135cb40 fffff803`8a3cfb87 : hal!HalpTimerClockIpiRoutine+0x15
    ffffd001`f0feaf70 fffff803`8a3cff2a : ffffe001`ffa01500 ffffd000`26a8e1c0 ffffd001`f0fe3bb0 ffffd000`2857f000 : nt!KiCallInterruptServiceRoutine+0xa3
    ffffd001`f0feafb0 fffff803`8a3d089b : ffffe002`01c01000 ffffd001`f0fe3ce0 00000000`00000000 00000000`00000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xea
    ffffd001`f0fe39a0 fffff803`8a38dcc2 : 00000000`00000000 ffffd001`f0fb2180 00000000`00000000 fffff801`413d10fa : nt!KiInterruptDispatchNoLockNoEtw+0xfb
    ffffd001`f0fe3b30 fffff803`8a38dbf9 : ffffd000`2857f000 ffffd000`26a8e400 ffffd001`f0fe3ce0 ffffd001`f0fe3e70 : nt!MiJumpStackTarget+0x72
    ffffd001`f0fe3b80 fffff803`8a32b580 : ffffd001`f1cbf0b0 fffff803`8a27e000 fffff803`8a538520 ffffd001`f0fb0f44 : nt!MiDoStackCopy+0x79
    ffffd001`f0fe3be0 fffff803`8a32a837 : 00000000`00000005 00000000`00000000 ffffc001`4a479ef0 00000000`00000002 : nt!KiExecuteAllDpcs+0x1b0
    ffffd001`f0fe3d30 fffff803`8a3d1bd5 : 00000001`00000011 ffffd001`f0fb2180 00000000`00000000 00000000`0000038b : nt!KiRetireDpcList+0xd7
    ffffd001`f0fe3fb0 fffff803`8a3d19d9 : 00000000`00000000 fffff803`8a3da138 000000d8`0cf623e0 fffff803`8a3d3c45 : nt!KxRetireDpcList+0x5
    ffffd000`6e6a3c10 fffff803`8a3d3afa : 00000000`00000001 000000d8`0cf614b0 00000000`00000001 ffffe002`0335e310 : nt!KiDispatchInterruptContinue
    ffffd000`6e6a3c40 00007ffe`61e5d55c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDpcInterrupt+0xca
    000000d8`10e3f500 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffe`61e5d55c
    
    
    
    
    STACK_COMMAND:  kb
    
    
    FOLLOWUP_IP: 
    nt! ?? ::FNODOBFM::`string'+2c418
    fffff803`8a40b3c8 cc              int     3
    
    
    SYMBOL_STACK_INDEX:  1
    
    
    SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+2c418
    
    
    FOLLOWUP_NAME:  MachineOwner
    
    
    MODULE_NAME: nt
    
    
    IMAGE_NAME:  ntkrnlmp.exe
    
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  545167e0
    
    
    BUCKET_ID_FUNC_OFFSET:  2c418
    
    
    FAILURE_BUCKET_ID:  0x133_DPC_nt!_??_::FNODOBFM::_string_
    
    
    BUCKET_ID:  0x133_DPC_nt!_??_::FNODOBFM::_string_
    
    
    ANALYSIS_SOURCE:  KM
    
    
    FAILURE_ID_HASH_STRING:  km:0x133_dpc_nt!_??_::fnodobfm::_string_
    
    
    FAILURE_ID_HASH:  {12e2b1b6-39a2-9cfe-dc70-25086917b8e2}
    
    
    Followup: MachineOwner
    ---------
    New Dump File: Attachment 57204

    Please note I've included an HTML page with the diff of the analysis from the previous dump vs this newest dump.
      My System SpecsSystem Spec

  5. #5


    India
    Posts : 2,097
    Windows 8.1 Industry Pro B-)


    Hi SlickPlaid ^_^,

    Unfortunately, the dump files don't contain much information. Kindly turn on Driver Verifier according to this **GUIDE**. Once it is turned on, make sure that you let it crash the system for few times. Once the system has crashed for few times, kindly re-run the SF Diagnostic Tool and upload a freshly generated diagnostic ZIP file.

    Let me know how it goes ^_^
    -Pranav
      My System SpecsSystem Spec

  6. #6


    Posts : 18
    Windows 8.1


    Driver Verification Troubleshooting


    Attempt #1


    • Actions


    • Result
      • No blue screen, but computer will not boot.
      • Hangs after the Windows loading screen finishes, but before heading into the login screen.
      • Computer forcibly restarted until Windows 8.1 decided to go into Automatic Repair.
      • Safe mode activated and disabled driver verification to try a new run.

    Attempt #2



    • Actions

      • Same settings as before
      • Selectively chose a smaller subset of drivers:
        • Realtek - rt630x64.sys
        • Corel Corporation - pxhlpa64.sys


    • Results
      • Computer ran slow at boot, but now seems to be running completely stable. No issues for over an hour.


    Attempt #3




    • Actions

      • Same settings as before
      • Choosing different drivers for this test:
        • Adobe Systems Incorporated - atmfd.dll
        • CEntrance, Inc. - ceusbaud.sys
        • Wacom Technology - wachidrouter.sys
        • Wacom Technology - wacomrouterfilter.sys


    • Results
      • Blue screen on boot. Attempting to reduce driver testing on next go-around.

    Attempt #4




    • Actions
      • Same settings
      • Choosing three of the four drivers above:
        • Adobe Systems Incorporated - atmfd.dll
        • Wacom Technology - wachidrouter.sys
        • Wacom Technology - wacomrouterfilter.sys


    • Results
      • Computer behaving normally, some slowness but otherwise working normally.



    Attempt #5




    • Actions
      • Same settings
      • Choosing the remaining driver not included above:
        • CEntrance, Inc. - ceusbaud.sys


    • Results
      • Blue screen on boot.


    Here is the packaged result testing for the attempts above and the blue screen dumps: Attachment 57308

    Here are the three blue screens that were recorded today:
    Code:
    3: 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: 0000000000000000
    
    
    Debugging Details:
    ------------------
    
    
    
    
    DPC_TIMEOUT_TYPE:  SINGLE_DPC_TIMEOUT_EXCEEDED
    
    
    CUSTOMER_CRASH_COUNT:  1
    
    
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    
    
    BUGCHECK_STR:  0x133
    
    
    PROCESS_NAME:  System
    
    
    CURRENT_IRQL:  d
    
    
    ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre
    
    
    LAST_CONTROL_TRANSFER:  from fffff8001e59a3c8 to fffff8001e55daa0
    
    
    STACK_TEXT:  
    ffffd000`923f8c88 fffff800`1e59a3c8 : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx
    ffffd000`923f8c90 fffff800`1e4aa2a1 : ffffdd87`455cb485 00000000`008e3a1e ffffe001`ef0005b0 ffffe001`f07bfec0 : nt! ?? ::FNODOBFM::`string'+0x2c418
    ffffd000`923f8d20 fffff800`1eba97b5 : 00016106`54e0599d 00000000`00000000 00016106`54e09c8c 00000000`00000000 : nt!KeClockInterruptNotify+0x91
    ffffd000`923f8f40 fffff800`1e4ee4b3 : ffffe001`efea1080 00000000`00000000 ffffd000`92949780 fffff800`1e55eb87 : hal!HalpTimerClockIpiRoutine+0x15
    ffffd000`923f8f70 fffff800`1e55ef2a : ffffe001`ef000500 00000000`c4208e0e 00000000`80000000 ffffe001`efea1080 : nt!KiCallInterruptServiceRoutine+0xa3
    ffffd000`923f8fb0 fffff800`1e55f89b : fffff800`1e6c38a0 00000000`00000000 ffffd000`923ea920 fffff800`1e536789 : nt!KiInterruptSubDispatchNoLockNoEtw+0xea
    ffffd000`923ea800 fffff800`1e4f4f1e : 0000007f`ffffffff fffff800`a017d16c ffffd000`923c0180 00000000`00000f44 : nt!KiInterruptDispatchNoLockNoEtw+0xfb
    ffffd000`923ea990 fffff800`1e4ba580 : ffffd000`923c2f00 ffffd000`923eaad0 ffffd000`923eac60 ffffd000`923c51a0 : nt!KiSwapDirectoryTableBaseTarget+0x62
    ffffd000`923ea9d0 fffff800`1e4b9837 : 40100000`00000000 00000000`00000000 400ff5c2`8f5c28f6 00000000`00000000 : nt!KiExecuteAllDpcs+0x1b0
    ffffd000`923eab20 fffff800`1e5615ea : ffffd000`923c0180 ffffd000`923c0180 ffffd000`923cc3c0 ffffe001`ffc0f880 : nt!KiRetireDpcList+0xd7
    ffffd000`923eada0 00000000`00000000 : ffffd000`923eb000 ffffd000`923e5000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a
    
    
    
    
    STACK_COMMAND:  kb
    
    
    FOLLOWUP_IP: 
    nt! ?? ::FNODOBFM::`string'+2c418
    fffff800`1e59a3c8 cc              int     3
    
    
    SYMBOL_STACK_INDEX:  1
    
    
    SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+2c418
    
    
    FOLLOWUP_NAME:  MachineOwner
    
    
    MODULE_NAME: nt
    
    
    IMAGE_NAME:  ntkrnlmp.exe
    
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  545167e0
    
    
    IMAGE_VERSION:  6.3.9600.17476
    
    
    BUCKET_ID_FUNC_OFFSET:  2c418
    
    
    FAILURE_BUCKET_ID:  0x133_DPC_nt!_??_::FNODOBFM::_string_
    
    
    BUCKET_ID:  0x133_DPC_nt!_??_::FNODOBFM::_string_
    
    
    ANALYSIS_SOURCE:  KM
    
    
    FAILURE_ID_HASH_STRING:  km:0x133_dpc_nt!_??_::fnodobfm::_string_
    
    
    FAILURE_ID_HASH:  {12e2b1b6-39a2-9cfe-dc70-25086917b8e2}
    
    
    Followup: MachineOwner
    ---------
    Code:
    0: kd> !analyze -v*******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    
    DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
    A device driver attempting to corrupt the system has been caught.  This is
    because the driver was specified in the registry as being suspect (by the
    administrator) and the kernel has enabled substantial checking of this driver.
    If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
    be among the most commonly seen crashes.
    Arguments:
    Arg1: 0000000000020003, ID of the 'IrqlDispatch' rule that was violated.
    Arg2: fffff8005fca2250, A pointer to the string describing the violated rule condition.
    Arg3: 0000000000000000, Reserved (unused).
    Arg4: 0000000000000000, Reserved (unused).
    
    
    Debugging Details:
    ------------------
    
    
    
    
    DV_VIOLATED_CONDITION:  KeAcquireSpinLockAtDpcLevel should only be called at IRQL >= DISPATCH_LEVEL.
    
    
    DV_MSDN_LINK: http://go.microsoft.com/fwlink/?LinkId=216020
    
    
    DV_RULE_INFO: 0x20003
    
    
    BUGCHECK_STR:  0xc4_IrqlDispatch_XDV
    
    
    CUSTOMER_CRASH_COUNT:  1
    
    
    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
    
    
    PROCESS_NAME:  System
    
    
    CURRENT_IRQL:  0
    
    
    ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre
    
    
    LAST_CONTROL_TRANSFER:  from fffff8005fc9a258 to fffff80329f56aa0
    
    
    STACK_TEXT:  
    ffffd001`dcf94ab8 fffff800`5fc9a258 : 00000000`000000c4 00000000`00020003 fffff800`5fca2250 00000000`00000000 : nt!KeBugCheckEx
    ffffd001`dcf94ac0 fffff800`5fc8e105 : 00000000`00000000 00000000`00000000 ffffd001`dcf8f000 ffffd001`dcf95000 : VerifierExt!SLIC_abort+0x5c
    ffffd001`dcf94b00 fffff800`5fc8e13b : ffffe001`d1447180 00000000`00000000 00000000`00000005 fffff803`29ee0920 : VerifierExt!SLIC_KeAcquireSpinLockAtDpcLevel_entry_IrqlDispatch+0x31
    ffffd001`dcf94b30 fffff803`2a4918f0 : ffffcf81`e840ecb8 00000000`00000000 fffff800`625d55f0 fffff803`00000000 : VerifierExt!KeAcquireSpinLockAtDpcLevel_wrapper+0x33
    ffffd001`dcf94b80 fffff800`625d3469 : ffffcf81`e840ed10 ffffcf81`e840ed10 ffffe001`d1447140 00000000`00000000 : nt!VerifierKeAcquireSpinLockAtDpcLevel+0xa4
    ffffd001`dcf94bc0 ffffcf81`e840ed10 : ffffcf81`e840ed10 ffffe001`d1447140 00000000`00000000 ffffcf81`e7cb4b50 : ceusbaud+0x5469
    ffffd001`dcf94bc8 ffffcf81`e840ed10 : ffffe001`d1447140 00000000`00000000 ffffcf81`e7cb4b50 fffff800`625d5619 : 0xffffcf81`e840ed10
    ffffd001`dcf94bd0 ffffe001`d1447140 : 00000000`00000000 ffffcf81`e7cb4b50 fffff800`625d5619 fffff800`625d55f0 : 0xffffcf81`e840ed10
    ffffd001`dcf94bd8 00000000`00000000 : ffffcf81`e7cb4b50 fffff800`625d5619 fffff800`625d55f0 ffffcf81`e7cb4b50 : 0xffffe001`d1447140
    
    
    
    
    STACK_COMMAND:  kb
    
    
    FOLLOWUP_IP: 
    ceusbaud+5469
    fffff800`625d3469 ??              ???
    
    
    SYMBOL_STACK_INDEX:  5
    
    
    SYMBOL_NAME:  ceusbaud+5469
    
    
    FOLLOWUP_NAME:  MachineOwner
    
    
    MODULE_NAME: ceusbaud
    
    
    IMAGE_NAME:  ceusbaud.sys
    
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  51e57c1a
    
    
    FAILURE_BUCKET_ID:  0xc4_IrqlDispatch_XDV_VRF_ceusbaud+5469
    
    
    BUCKET_ID:  0xc4_IrqlDispatch_XDV_VRF_ceusbaud+5469
    
    
    ANALYSIS_SOURCE:  KM
    
    
    FAILURE_ID_HASH_STRING:  km:0xc4_irqldispatch_xdv_vrf_ceusbaud+5469
    
    
    FAILURE_ID_HASH:  {55e8c89a-d66c-e484-aebc-e59d9827f500}
    
    
    Followup: MachineOwner
    ---------
    Code:
    4: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    
    DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
    A device driver attempting to corrupt the system has been caught.  This is
    because the driver was specified in the registry as being suspect (by the
    administrator) and the kernel has enabled substantial checking of this driver.
    If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
    be among the most commonly seen crashes.
    Arguments:
    Arg1: 0000000000020003, ID of the 'IrqlDispatch' rule that was violated.
    Arg2: fffff80098364250, A pointer to the string describing the violated rule condition.
    Arg3: 0000000000000000, Reserved (unused).
    Arg4: 0000000000000000, Reserved (unused).
    
    
    Debugging Details:
    ------------------
    
    
    
    
    DV_VIOLATED_CONDITION:  KeAcquireSpinLockAtDpcLevel should only be called at IRQL >= DISPATCH_LEVEL.
    
    
    DV_MSDN_LINK: http://go.microsoft.com/fwlink/?LinkId=216020
    
    
    DV_RULE_INFO: 0x20003
    
    
    BUGCHECK_STR:  0xc4_IrqlDispatch_XDV
    
    
    IMAGE_NAME:  ceusbaud.sys
    
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  51e57c1a
    
    
    MODULE_NAME: ceusbaud
    
    
    FAULTING_MODULE: fffff8009834a000 VerifierExt
    
    
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    
    
    PROCESS_NAME:  System
    
    
    CURRENT_IRQL:  0
    
    
    ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre
    
    
    LAST_CONTROL_TRANSFER:  from fffff8009835c258 to fffff8016f162aa0
    
    
    STACK_TEXT:  
    ffffd000`2598dab8 fffff800`9835c258 : 00000000`000000c4 00000000`00020003 fffff800`98364250 00000000`00000000 : nt!KeBugCheckEx
    ffffd000`2598dac0 fffff800`98350105 : 00000000`00000000 00000000`00000000 ffffd000`25988000 ffffd000`2598e000 : VerifierExt!SLIC_abort+0x5c
    ffffd000`2598db00 fffff800`9835013b : ffffe000`5424a9c0 00000000`00000000 00000000`00000005 fffff801`6f0ec920 : VerifierExt!SLIC_KeAcquireSpinLockAtDpcLevel_entry_IrqlDispatch+0x31
    ffffd000`2598db30 fffff801`6f69d8f0 : ffffcf81`aa9d0cb8 00000000`00000000 fffff800`99a2e5f0 fffff801`00000000 : VerifierExt!KeAcquireSpinLockAtDpcLevel_wrapper+0x33
    ffffd000`2598db80 fffff800`99a2c469 : ffffcf81`aa9d0d10 ffffcf81`aa9d0d10 ffffe000`5424a980 00000000`00000000 : nt!VerifierKeAcquireSpinLockAtDpcLevel+0xa4
    ffffd000`2598dbc0 fffff800`99a2e619 : fffff800`99a2e5f0 ffffcf81`aa960b50 ffffe000`5424a880 fffff801`6f045209 : ceusbaud+0x5469
    ffffd000`2598dbf0 fffff801`6f0901ac : ffffcf81`aa95afb0 ffffc001`0000000f 00000000`00000000 fffff801`6f2fe748 : ceusbaud+0x7619
    ffffd000`2598dc20 fffff801`6f08facc : 00000000`00000000 fffff801`6f09012c ffffcf81`aa95afb0 ffffe000`00000003 : nt!IopProcessWorkItem+0x80
    ffffd000`2598dc90 fffff801`6f113440 : ffffd000`295a23c0 ffffe000`5424a880 00000000`00000080 ffffe000`5424a880 : nt!ExpWorkerThread+0x28c
    ffffd000`2598dd40 fffff801`6f1690c6 : ffffd000`29596180 ffffe000`5424a880 ffffd000`295a23c0 00037548`00041380 : nt!PspSystemThreadStartup+0x58
    ffffd000`2598dda0 00000000`00000000 : ffffd000`2598e000 ffffd000`25988000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
    
    
    
    
    STACK_COMMAND:  kb
    
    
    FOLLOWUP_IP: 
    ceusbaud+5469
    fffff800`99a2c469 488b4b08        mov     rcx,qword ptr [rbx+8]
    
    
    SYMBOL_STACK_INDEX:  5
    
    
    SYMBOL_NAME:  ceusbaud+5469
    
    
    FOLLOWUP_NAME:  MachineOwner
    
    
    FAILURE_BUCKET_ID:  0xc4_IrqlDispatch_XDV_VRF_ceusbaud+5469
    
    
    BUCKET_ID:  0xc4_IrqlDispatch_XDV_VRF_ceusbaud+5469
    
    
    ANALYSIS_SOURCE:  KM
    
    
    FAILURE_ID_HASH_STRING:  km:0xc4_irqldispatch_xdv_vrf_ceusbaud+5469
    
    
    FAILURE_ID_HASH:  {55e8c89a-d66c-e484-aebc-e59d9827f500}
    
    
    Followup: MachineOwner
    ---------
    Last edited by slickplaid; 31 Jan 2015 at 11:37. Reason: Update
      My System SpecsSystem Spec

  7. #7


    Posts : 18
    Windows 8.1


    My follow-up question:

    Since this looks to be the fault of the CEntrance Universal Driver for my CEntrance HiFi-M8 (a rather expensive piece of hardware that I use every day for work), what information would be best sent to the developer of that driver to assist them in applying a fix for my situation?

    Are the mini-dumps enough? Should I run something else to gather more information for the developer?

    Edit: I have sent the kernel dumps to the author/developer and he's taking a look at it. I'll report back with my findings in case anyone else has this issue in the future.

    Edit 2: An updated driver (7.4.9) has been created for me to test. So far so good, no BSoD.
    Last edited by slickplaid; 04 Feb 2015 at 08:06.
      My System SpecsSystem Spec

  8. #8


    Posts : 18
    Windows 8.1


    Another crash, another day.

    This one seems to have a lot more specific information pointing to a USB device or USB host driver.

    Dump file: Attachment 57617

    Code:
    Microsoft (R) Windows Debugger Version 6.3.9600.17298 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    
    
    Loading Dump File [C:\Windows\MEMORY.DMP]
    Kernel Bitmap Dump File: Only kernel address space is available
    
    
    
    
    ************* Symbol Path validation summary **************
    Response                         Time (ms)     Location
    Deferred                                       SRV*C:\Windows\symbol_cache*http://msdl.microsoft.com/download/symbols
    Symbol search path is: SRV*C:\Windows\symbol_cache*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 9600.17476.amd64fre.winblue_r5.141029-1500
    Machine Name:
    Kernel base = 0xfffff801`7227b000 PsLoadedModuleList = 0xfffff801`72554250
    Debug session time: Sat Feb  7 07:26:37.268 2015 (UTC - 6:00)
    System Uptime: 3 days 0:41:34.984
    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, 0}
    
    
    *** ERROR: Module load completed but symbols could not be loaded for ceusbaud.sys
    Probably caused by : USBPORT.SYS ( USBPORT!USBPORT_IsochTransfer+30c )
    
    
    Followup: MachineOwner
    ---------
    
    
    1: 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: 0000000000000000
    
    
    Debugging Details:
    ------------------
    
    
    
    
    DPC_TIMEOUT_TYPE:  SINGLE_DPC_TIMEOUT_EXCEEDED
    
    
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    
    
    BUGCHECK_STR:  0x133
    
    
    PROCESS_NAME:  System
    
    
    CURRENT_IRQL:  d
    
    
    ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre
    
    
    LAST_CONTROL_TRANSFER:  from fffff801724083c8 to fffff801723cbaa0
    
    
    STACK_TEXT:  
    ffffd001`b73fec88 fffff801`724083c8 : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx
    ffffd001`b73fec90 fffff801`723182a1 : fffff801`7225fd00 00000000`00ff8fbf 00027a23`1198d1d6 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x2c418
    ffffd001`b73fed20 fffff801`722137b5 : 00027a56`c78a1fd8 00000000`00000000 00027a56`c78a4645 00000000`00000000 : nt!KeClockInterruptNotify+0x91
    ffffd001`b73fef40 fffff801`7235c4b3 : ffffd001`b766a000 00000000`00000000 ffffd001`b7fe5780 fffff801`723ccb87 : hal!HalpTimerClockIpiRoutine+0x15
    ffffd001`b73fef70 fffff801`723ccf2a : fffff801`7225fd00 ffffd000`acba2d90 ffffd001`b73f7bb0 ffffd001`b766a000 : nt!KiCallInterruptServiceRoutine+0xa3
    ffffd001`b73fefb0 fffff801`723cd89b : db92349c`4b77260d c8c580a7`e4144179 096591a1`6e99b2db 96591a16`e99b2db0 : nt!KiInterruptSubDispatchNoLockNoEtw+0xea
    ffffd000`accf7da0 fffff801`7238acba : ea4cc691`13772633 f9645695`f3fafe8f 3f360467`879cf1ad df2eb09f`ee21a6c6 : nt!KiInterruptDispatchNoLockNoEtw+0xfb
    ffffd000`accf7f30 fffff801`723cf3f7 : ffffd001`b766a000 ffffd000`accf7fd0 ffffd001`b73f7ce0 ffffe000`47feb880 : nt!MiJumpStackTarget+0x6a
    ffffd000`accf7f80 fffff801`723cf3bd : ffffd000`294aea00 00000000`00000000 00000000`00000002 fffff801`722bb48d : nt!KxSwitchKernelStackCallout+0x27
    ffffd001`b73f7a70 fffff801`722bb48d : 00000000`00000006 ffffd000`294aea00 00000000`00000006 ffff0a15`4f925ae5 : nt!KiSwitchKernelStackContinue
    ffffd001`b73f7a90 fffff801`7238ac3b : fffff801`7238ac50 ffffd001`b73f7bb0 00000000`00000000 00000000`00000020 : nt!KeExpandKernelStackAndCalloutInternal+0x2fd
    ffffd001`b73f7b80 fffff801`72328580 : 00000000`00000001 fffff801`7227b000 fffff801`72535520 ffffd001`b73c0f44 : nt!MiDoStackCopy+0xbb
    ffffd001`b73f7be0 fffff801`72327837 : 0231948a`8b842e09 7810b330`00000000 010ab6f7`c747f7e6 acf2649c`ad00407a : nt!KiExecuteAllDpcs+0x1b0
    ffffd001`b73f7d30 fffff801`723cebd5 : 674a6501`00230aeb ffffd001`b73c6180 00000000`00000000 00000000`00000103 : nt!KiRetireDpcList+0xd7
    ffffd001`b73f7fb0 fffff801`723ce9d9 : ffffd000`00000000 00001f80`00520200 ffff9324`7882660d ffffe000`3e7943f0 : nt!KxRetireDpcList+0x5
    ffffd000`acf68650 fffff801`723d0afa : ffffe000`3f07411c ffffd001`b73c6180 ffffd001`b73c8f00 00000000`00000801 : nt!KiDispatchInterruptContinue
    ffffd000`acf68680 fffff801`722fe543 : fffff801`2e6814ec ffffd000`acf688c1 00000000`00000001 00000000`00000000 : nt!KiDpcInterrupt+0xca
    ffffd000`acf68818 fffff801`2e6814ec : ffffd000`acf688c1 00000000`00000001 00000000`00000000 00000000`ffffffff : nt!KzLowerIrql+0x7
    ffffd000`acf68820 fffff801`2e67fe5b : ffffe000`3e793001 ffffe000`3df3e8a0 ffffe000`3f074010 ffffe000`3ef7a4e0 : USBPORT!USBPORT_IsochTransfer+0x30c
    ffffd000`acf68910 fffff801`2e67f4bc : 00000000`70627375 ffffe000`3df3ea90 00000000`00000008 00000000`00000000 : USBPORT!USBPORT_ProcessURB+0x70b
    ffffd000`acf68a60 fffff801`2e83744f : 00000000`42554855 ffffe000`3df3ea90 ffffe000`3ef1d1b0 ffffe000`3ef1d060 : USBPORT!USBPORT_Dispatch+0x19c
    ffffd000`acf68ac0 fffff801`2e83720c : 00000000`496f3034 00000000`4f494449 ffffe000`3f0531a0 00000000`00000000 : usbhub!UsbhPdoInternalDeviceControl+0x1ef
    ffffd000`acf68b30 fffff801`2c445332 : ffffe000`3f0531a0 ffffe000`3f0533e0 00000000`00000000 ffffe000`3f0533e0 : usbhub!UsbhGenDispatch+0x3c
    ffffd000`acf68b60 fffff801`2c44548d : ffffe000`3f0531a0 fffff801`7252d200 00000000`00000082 ffffe000`40b10270 : ceusbaud+0x5332
    ffffd000`acf68b90 fffff801`2c445619 : 00000000`00000103 ffffe000`3f0533e0 fffff801`2c447800 00000000`00000000 : ceusbaud+0x548d
    ffffd000`acf68bc0 fffff801`2c447829 : fffff801`2c447800 ffffe000`3f022748 ffffe000`47feb880 fffff801`722ae209 : ceusbaud+0x5619
    ffffd000`acf68bf0 fffff801`722f91ac : ffffe000`4b63ecc0 fffff801`00000000 ffffd001`b73c6180 00000000`00000000 : ceusbaud+0x7829
    ffffd000`acf68c20 fffff801`722f8acc : fffff801`2c877860 fffff801`722f912c ffffe000`4b63ecc0 ffffe000`47feb880 : nt!IopProcessWorkItem+0x80
    ffffd000`acf68c90 fffff801`7237c440 : 00000000`00000000 ffffe000`47feb880 00000000`00000080 ffffe000`47feb880 : nt!ExpWorkerThread+0x28c
    ffffd000`acf68d40 fffff801`723d20c6 : ffffd001`b7740180 ffffe000`47feb880 ffffd001`b774c3c0 00000000`00000000 : nt!PspSystemThreadStartup+0x58
    ffffd000`acf68da0 00000000`00000000 : ffffd000`acf69000 ffffd000`acf63000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
    
    
    
    
    STACK_COMMAND:  kb
    
    
    FOLLOWUP_IP: 
    USBPORT!USBPORT_IsochTransfer+30c
    fffff801`2e6814ec 8bc7            mov     eax,edi
    
    
    SYMBOL_STACK_INDEX:  12
    
    
    SYMBOL_NAME:  USBPORT!USBPORT_IsochTransfer+30c
    
    
    FOLLOWUP_NAME:  MachineOwner
    
    
    MODULE_NAME: USBPORT
    
    
    IMAGE_NAME:  USBPORT.SYS
    
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  53897701
    
    
    IMAGE_VERSION:  6.3.9600.17195
    
    
    BUCKET_ID_FUNC_OFFSET:  30c
    
    
    FAILURE_BUCKET_ID:  0x133_DPC_USBPORT!USBPORT_IsochTransfer
    
    
    BUCKET_ID:  0x133_DPC_USBPORT!USBPORT_IsochTransfer
    
    
    ANALYSIS_SOURCE:  KM
    
    
    FAILURE_ID_HASH_STRING:  km:0x133_dpc_usbport!usbport_isochtransfer
    
    
    FAILURE_ID_HASH:  {8dcf70ae-a511-b3b4-9470-78d5e079686a}
    
    
    Followup: MachineOwner
    ---------
    Searching here on these forums for more information yielded the following solutions:
    BSOD crash usbport.sys suspected, please help with dump file analysis Solved - Windows 7 Help Forums
    and
    How to Diagnose and Fix High DPC Latency Issues with WPA (Windows Vista/7/8) - Sysnative Forums

    I have disconnected any extraneous USB devices in the mean time. I do have a 3rd party (not integrated into motherboard) USB 3.0 controller (PCI-e), but no devices are currently attached to it. I am leaving it installed for now. The blue screen issue occured before that was purchased and installed.

    Here is the result of `sfc /verifyonly`:

    Code:
    C:\WINDOWS\system32>sfc /verifyonly
    
    
    Beginning system scan.  This process will take some time.
    
    
    Beginning verification phase of system scan.
    Verification 100% complete.
    
    
    Windows Resource Protection did not find any integrity violations.
    I have also run `xperf -on DiagEasy -BufferSize 256`, `xperf -d %userprofile%\Desktop\trace.etl`, and `xperf %userprofile%\Desktop\trace.etl`.
    I increased the buffer size, because it said it dropped events and needed to be larger.

    I'm relatively sure I'd need to run these when the issue happens to be of diagnostic use, but here they are.

    Here is the result:

    Attachment 57619Attachment 57620
      My System SpecsSystem Spec

  9. #9


    India
    Posts : 2,097
    Windows 8.1 Industry Pro B-)


    Hi Slickplaid ^_^,

    Sorry for the delay. I just needed a break. Anyways, I have analysed your dump files and it was not helpful at all

    Although while analysing your latest dump files, it seems that the "ceusbaud.sys" is still loading. Could you please disconnect all the USB Devices and then rename this driver to "ceusbaudbak.sys". Once you have renamed the driver, reboot your system and see if it crashes or not.


    Also, according to your reports, you have installed only 5 updates. I strongly suggest you to download and install all of the updates from Windows Update (It might take you several trips to Windows Updates).

    Let me know how it goes ^_^

    -Pranav
      My System SpecsSystem Spec

  10. #10


    Posts : 18
    Windows 8.1


    Hello Pranav,

    Thanks for the response

    Quote Originally Posted by blueelvis View Post
    Also, according to your reports, you have installed only 5 updates. I strongly suggest you to download and install all of the updates from Windows Update (It might take you several trips to Windows Updates).
    I have been running Windows update and have made sure that all updates have been installed. A new update must have been released today. I will install it now.

    Attachment 57659


    Quote Originally Posted by blueelvis View Post
    Although while analysing your latest dump files, it seems that the "ceusbaud.sys" is still loading. Could you please disconnect all the USB Devices and then rename this driver to "ceusbaudbak.sys". Once you have renamed the driver, reboot your system and see if it crashes or not.
    I am currently in contact with the developers of that driver and they have been tracking my BSoD as well. If you know of any useful information to pass on to them, let me know. They wanted me to install a new version to see if the BSoD persists, and it has. We are not 100% sure it is their device/driver that is causing it, but it is extremely helpful to them to get this information.

    Please note that this BSoD occured even with the device unplugged. I will rename the driver and make sure it isn't loaded to see if the BSoD still occurs. It is very intermittent, so it could be hours or days before it occurs again with no real pattern, which makes this so incredibly difficult to debug.

    Just for my note, would you guess that last BSoD dump narrowed it down to a USB device or controller? It would help me to know exactly what you're thinking when you look at that dump.

    I will keep up-to-date on the updates and completely remove that device to see if it is the root of the cause.

    Thanks!
      My System SpecsSystem Spec

Page 1 of 4 123 ... LastLast
Daily BSOD: 0x133, MsMpEng.exe SINGLE_DPC_TIMEOUT_EXCEEDED
Related Threads
Solved BSOD DPC_WATCHDOG 0x133 in BSOD Crashes and Debugging
Hi i have this bsod but can't understand why.. i can stay ok for 1 week.. and today i had 3 bsod in 20min... it is totally random. Pls help me :)
Hey guys, At some stage last night my PC must have restarted as I saw the vanilla error message in the morning. It's a new machine, no GPU installed at the moment and very little drivers. Downloaded WinDbg and had a quick look but I'm new to all the drivers so not really sure on what is the...
More than one BSOD daily. in BSOD Crashes and Debugging
I keep having a few BSOD daily, I can't pin point what it is. My recent one was PAGE_FAULT_IN_NONPAGED_AREA. Here is the SF Diag: http://db.tt/6dbdS7jg EDIT: If you don't trust dropbox, I added a attachment! Any help would be appreciated. Thanks!
Daily BSOD in hall.dll 0x133 in BSOD Crashes and Debugging
Hi everyone, I am experiencing regular BSODS, at least 1 a day. They are occurring randomly, not necessarily under stress. I'm a newbie so I have no idea what is wrong. When it bsods, I get DPC_WATCHDOG_VIOLATION. According to bsodviewer the error is in hal.dll. I am running Windows 8 64. ...
Windows 8 Bsod 0x133 in BSOD Crashes and Debugging
Hello Can someone help me with this Bsod Error? Pc freeze for some minutes and then appear Windows 8 error page with this error: dpc_watchdog_violation Thank you
BSOD error 0x133 in BSOD Crashes and Debugging
I've been receiving seemingly random BSOD's with Windows 8. I've tried doing a completely clean install of it, but still have the same issue. Thanks in advance.
BSOD in hall.dll 0x133 in BSOD Crashes and Debugging
Hi, on my Windows 8 x64 System I have daily crashes in hal.dll. I can't find a reason for this. The crashes happens mainly not under workload ? The other crash in the zip 0x21c happens after a corrupt system device. I restored Windows 8 with the new restore feature. I have attached Windos...
Eight Forums Android App Eight Forums IOS App Follow us on Facebook