Windows 8 and 8.1 Forums


Daily BSOD: 0x133, MsMpEng.exe SINGLE_DPC_TIMEOUT_EXCEEDED

  1. #11


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


    Hi slickplaid ^_^,

    I am astonished to see that you are seeing only 1 available update. On my system (Also Windows 8.1 Pro), there are more than 60 updates installed. At this point of time, I would suggest you to use the device on another Windows 8.1 machine and see if you are still getting the BSOD or not. This is because there are very very few updates installed on the system and that could be causing problems.

    Could you please do one thing?
    Please open up that Complete MEMORY.DMP in WinDBG and once the terminal is open, type in the below command and paste back the output -
    Code:
    lmvm usbport
    Kindly paste back the output you get.

    Did the author say anything else as well? See if he could get some clues from this thread

    Let me know how it goes ^_^
    -Pranav

      My System SpecsSystem Spec

  2. #12


    Pranav there's no use running lmvm usbport, because usbport.sys is the functional device object on the USB 2.0 device stack, provided by Microsoft. It's most likely a USB 2.0 device if the the problem is passing through usbport.sys
    Code:
    1: kd> .bugcheck
    Bugcheck code 00000133
    Arguments 00000000`00000000 00000000`00000501 00000000`00000500 00000000`00000000
    
    1: kd> kn
     # Child-SP          RetAddr           Call Site
    00 ffffd001`b73fec88 fffff801`724083c8 nt!KeBugCheckEx
    01 ffffd001`b73fec90 fffff801`723182a1 nt!KeAccumulateTicks+0x2c418
    02 ffffd001`b73fed20 fffff801`722137b5 nt!KeClockInterruptNotify+0x91
    03 ffffd001`b73fef40 fffff801`7235c4b3 hal!HalpTimerClockIpiRoutine+0x15
    04 ffffd001`b73fef70 fffff801`723ccf2a nt!KiCallInterruptServiceRoutine+0xa3
    05 ffffd001`b73fefb0 fffff801`723cd89b nt!KiInterruptSubDispatchNoLockNoEtw+0xea
    06 ffffd000`accf7da0 fffff801`7238acba nt!KiInterruptDispatchNoLockNoEtw+0xfb
    07 ffffd000`accf7f30 fffff801`723cf3f7 nt!MiJumpStackTarget+0x6a
    08 ffffd000`accf7f80 fffff801`723cf3bd nt!KxSwitchKernelStackCallout+0x27
    09 ffffd001`b73f7a70 fffff801`722bb48d nt!KiSwitchKernelStackContinue
    0a ffffd001`b73f7a90 fffff801`7238ac3b nt!KeExpandKernelStackAndCalloutInternal+0x2fd
    0b ffffd001`b73f7b80 fffff801`72328580 nt!MiDoStackCopy+0xbb
    0c ffffd001`b73f7be0 fffff801`72327837 nt!KiExecuteAllDpcs+0x1b0
    0d ffffd001`b73f7d30 fffff801`723cebd5 nt!KiRetireDpcList+0xd7
    0e ffffd001`b73f7fb0 fffff801`723ce9d9 nt!KxRetireDpcList+0x5
    0f ffffd000`acf68650 00000000`00000000 nt!KiDispatchInterruptContinue
    It's difficult to say what the cause is, most likely a poor DPC routine that isn't expiring the timer and releasing the threads associated with it, something has probably gone wrong in the process and hed up the system.
    A full memory dump will help, a lot.
      My System SpecsSystem Spec

  3. #13


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


    I am just curious as to how come the system has got only 5 updates installed and the system is showing that there are no further updates. Sure this driver is provided by Microsoft but there is, very well a chance where the base operating system files were updated.

    @Slick - I see loads of errors in your updatelog.txt. Could you please upload a freshly generated SF Diagnostic ZIP file along with the required file asked by Mysers please?

    -Pranav
      My System SpecsSystem Spec

  4. #14


    Posts : 18
    Windows 8.1


    Thanks for the responses, Pranav and Mysers Briggs.

    I will turn on full memory dumps now and report back once I get another BSoD.

    This is a relatively new install of Windows 8.1. I'm not sure if that could be the cause or reason for the low amount of updates. Windows 8.1 might package all of them into a single update. I can absolutely guarantee to the best of my knowledge that Windows Update is showing no updates and is reporting that everything is up-to-date as of 2015-02-09 @ 16:22 CST.

    There also have been no visible errors when checking for updates from Microsoft.

    Attachment 57762Attachment 57763

    Here is the latest diagnostic tool dump:

    Attachment 57765

    One BSoD occured while I was working and had that device that might be causing the BSoD plugged in to use it. I have been unplugging it and trying to track those BSoDs rather than the ones that occur with the device plugged in (following your instructions).

    Would me running WinDBG with `analyze -v` and copying the output be enough or do you need the whole file? I would prefer only hosting it for a short amount of time so it's public exposure is low, considering it could expose sensitive information in the wrong hands. If you could give me the commands you want run on it, I would be happy to copy/paste the output to you.

    As a last resort (direct linking through PM) would I give out the full contents of the memory working on my work computer. I hope I'm not being overly protective on that point.

    Thanks!
      My System SpecsSystem Spec

  5. #15


    AFAIK, there is no sensitive information saved in dump files, certainly not from what I've seen.
    This dump file, again, isn't much help as with most minidumps, because there's hardly any information saved to debug.
      My System SpecsSystem Spec

  6. #16


    Posts : 5,139
    Win8.1Pro - Finally!!!


    Just my 2в here -
    The BIOS/UEFI dates from 2011. While not being excessively old, I have seen problems with Gigabyte boards - so I'd strongly suggest updating to the latest version. Presuming that your board is a rev 1.0 and not a rev 2.0 board - your system is using a beta BIOS. There is one further beta BIOS available (F8a) - and there's always the possibility of reverting to a non-beta BIOS. Here's the link that I found: GIGABYTE - Motherboard - Socket 1366 - GA-X58A-UD5 (rev. 1.0)

    Also, please note that Gigabyte doesn't offer Win8/8.1 drivers for neither the rev 1.0 nor the rev 2.0 boards. This is a hint (IMO) that the board may not be 100% compatible w/Win8/8.1

    Also note that there is hal.dll present in the stack text. While not a 100% diagnostic - this usually shows up when an incompatibility is suspected.

    First I'd suggest this tutorial as it may help to identify the cause(s) within your system: How to Diagnose and Fix High DPC Latency Issues with WPA (Windows Vista/7/8) - Sysnative Forums

    Please uninstall Virtual Box while we're testing. It's easily reinstalled if needed, but it excessively complicates the BSOD analysis when it's present (and it's a bit buggy w/Win8/8.1 IME). I've had issues on my system with the Virtual Box Ethernet adapter and have disabled it in Device Manager (and, funny thing, my network still works in the VM's).

    Did removing the USB audio device and it's drivers stop the BSOD's?

    Driver Verifier stresses drivers. As you've changed the USB audio driver and still have issues - I'd suggest running Driver Verifier again with the same settings EXCEPT FOR - DO NOT TEST the USB audio drivers. Let's see if verifier can pick up on another driver.

    Another thing to try is using other USB ports to see if the problem is replicated on all ports (USB 2 and 3).

    Another thing to try is letting verifier stress Windows drivers - then compare your versions with the updated versions on other systems.
    I would also strongly suggest that you start a topic in the Windows Updates & Activation forum here: https://www.eightforums.com/windows-updates-activation/ IMO there is a strong possibility that missing Windows Updates could be contributing to this problem.
    FYI - the typical Win8.1 installation has over 100 updates.

    Just FYI - you have 11 drivers whose name starts with USB in the driver report, I have 18 on my system (and I use a USB port). Your drivers appear to have the same datestamps as mine.

    USB wifi devices also have a history of BSOD problems. As it appears that yours is disabled, please uninstall it's drivers and then physically remove the device from the system. That's one less possible problem - and it may reduce the BSOD's also.

    You seem have about 10 hard drives (and I didn't include the NAS). What is the make/model/wattage and age of your Power Supply?

    The WER section of MSINFO32 shows many, many problems with the vid_18D1&pid_ 4ee1 device. This is most likely an Android USB device - maybe a Nexus phone? Please uninstall the software for this device and then physically remove it from your system.

    Although that was the major problem - there's lot's of other USB driver issues with other devices in the WER section of MSINFO32 - which makes me wonder if there's a USB issue rather than an issue with a specific device. I read at one point that you had a USB 3 card installed. Could you remove that (and it's drivers) and test to see if that stops the BSOD's?

    Interesting to note - out of the last 20 memory dumps, 2 were verifier enabled 0xC2's and one was 0x50 - which blamed your video drivers.
    The rest were STOP 0x133's

    Please uninstall Gigabyte Easy Saver, it's gdrv.sys driver is known to cause BSOD's on some Windows systems.
    Also uninstall the Gigabyte EasyTune software (if installed) as it causes BSOD's also.

    Analysis:
    The following is for informational purposes only.
    Code:
    **************************Mon Feb  9 11:58:16.995 2015 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\020915-14343-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.17476.amd64fre.winblue_r5.141029-1500
    System Uptime:2 days 3:29:52.312
    Probably caused by :ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+2c418 )
    BugCheck 133, {0, 501, 500, 0}
    BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
    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
    BUGCHECK_STR:  0x133
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x133_DPC_nt!_??_::FNODOBFM::_string_
    CPUID:        "Intel(R) Core(TM) i7 CPU         920  @ 2.67GHz"
    MaxSpeed:     2670
    CurrentSpeed: 2665
      BIOS Version                  F7j
      BIOS Release Date             03/07/2011
      Manufacturer                  Gigabyte Technology Co., Ltd.
      Product Name                  X58A-UD5
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sat Feb  7 08:26:37.268 2015 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\020715-14421-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.17476.amd64fre.winblue_r5.141029-1500
    System Uptime:3 days 0:41:34.984
    Probably caused by :ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+2c418 )
    BugCheck 133, {0, 501, 500, 0}
    BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
    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
    BUGCHECK_STR:  0x133
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x133_DPC_nt!_??_::FNODOBFM::_string_
    CPUID:        "Intel(R) Core(TM) i7 CPU         920  @ 2.67GHz"
    MaxSpeed:     2670
    CurrentSpeed: 2665
      BIOS Version                  F7j
      BIOS Release Date             03/07/2011
      Manufacturer                  Gigabyte Technology Co., Ltd.
      Product Name                  X58A-UD5
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sat Jan 31 11:05:58.412 2015 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\013115-14906-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.17476.amd64fre.winblue_r5.141029-1500
    System Uptime:0 days 0:00:14.199
    *** WARNING: Unable to verify timestamp for ceusbaud.sys
    *** ERROR: Module load completed but symbols could not be loaded for ceusbaud.sys
    Probably caused by :ceusbaud.sys ( ceusbaud+5469 )
    BugCheck C4, {20003, fffff80098364250, 0, 0}
    BugCheck Info: DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
    DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
    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).
    BUGCHECK_STR:  0xc4_IrqlDispatch_XDV
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0xc4_IrqlDispatch_XDV_VRF_ceusbaud+5469
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sat Jan 31 10:35:05.514 2015 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\013115-14812-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.17476.amd64fre.winblue_r5.141029-1500
    System Uptime:0 days 0:00:22.303
    *** WARNING: Unable to verify timestamp for ceusbaud.sys
    *** ERROR: Module load completed but symbols could not be loaded for ceusbaud.sys
    Probably caused by :ceusbaud.sys ( ceusbaud+5469 )
    BugCheck C4, {20003, fffff8005fca2250, 0, 0}
    BugCheck Info: DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
    DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
    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).
    BUGCHECK_STR:  0xc4_IrqlDispatch_XDV
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0xc4_IrqlDispatch_XDV_VRF_ceusbaud+5469
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sat Jan 31 05:29:14.753 2015 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\013115-14328-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.17476.amd64fre.winblue_r5.141029-1500
    System Uptime:1 days 16:27:20.469
    Probably caused by :ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+2c418 )
    BugCheck 133, {0, 501, 500, 0}
    BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
    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
    BUGCHECK_STR:  0x133
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x133_DPC_nt!_??_::FNODOBFM::_string_
    CPUID:        "Intel(R) Core(TM) i7 CPU         920  @ 2.67GHz"
    MaxSpeed:     2670
    CurrentSpeed: 2665
      BIOS Version                  F7j
      BIOS Release Date             03/07/2011
      Manufacturer                  Gigabyte Technology Co., Ltd.
      Product Name                  X58A-UD5
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Thu Jan 29 13:00:12.362 2015 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\012915-14515-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.17476.amd64fre.winblue_r5.141029-1500
    System Uptime:1 days 5:17:23.078
    Probably caused by :ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+2c418 )
    BugCheck 133, {0, 501, 500, 0}
    BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
    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
    BUGCHECK_STR:  0x133
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  chrome.exe
    FAILURE_BUCKET_ID: 0x133_DPC_nt!_??_::FNODOBFM::_string_
    CPUID:        "Intel(R) Core(TM) i7 CPU         920  @ 2.67GHz"
    MaxSpeed:     2670
    CurrentSpeed: 2665
      BIOS Version                  F7j
      BIOS Release Date             03/07/2011
      Manufacturer                  Gigabyte Technology Co., Ltd.
      Product Name                  X58A-UD5
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Wed Jan 28 07:41:13.969 2015 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\012815-15953-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.17476.amd64fre.winblue_r5.141029-1500
    System Uptime:1 days 2:31:48.686
    *** WARNING: Unable to verify timestamp for nvlddmkm.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
    Probably caused by :nvlddmkm.sys ( nvlddmkm+3739de )
    BugCheck 50, {ffffe001a0d6c480, 0, fffff801a3fc79de, 0}
    BugCheck Info: PAGE_FAULT_IN_NONPAGED_AREA (50)
    Arguments: 
    Arg1: ffffe001a0d6c480, memory referenced.
    Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
    Arg3: fffff801a3fc79de, If non-zero, the instruction address which referenced the bad memory
        address.
    Arg4: 0000000000000000, (reserved)
    BUGCHECK_STR:  AV
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: AV_nvlddmkm+3739de
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Tue Jan 27 05:07:52.111 2015 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\012715-14218-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.17476.amd64fre.winblue_r5.141029-1500
    System Uptime:0 days 19:00:06.828
    Probably caused by :ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+2c418 )
    BugCheck 133, {0, 501, 500, 0}
    BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
    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
    BUGCHECK_STR:  0x133
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x133_DPC_nt!_??_::FNODOBFM::_string_
    CPUID:        "Intel(R) Core(TM) i7 CPU         920  @ 2.67GHz"
    MaxSpeed:     2670
    CurrentSpeed: 2665
      BIOS Version                  F7j
      BIOS Release Date             03/07/2011
      Manufacturer                  Gigabyte Technology Co., Ltd.
      Product Name                  X58A-UD5
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Mon Jan 26 10:06:12.651 2015 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\012615-14734-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.17476.amd64fre.winblue_r5.141029-1500
    System Uptime:0 days 21:22:05.765
    Probably caused by :ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+2c418 )
    BugCheck 133, {0, 501, 500, 0}
    BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
    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
    BUGCHECK_STR:  0x133
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  chrome.exe
    FAILURE_BUCKET_ID: 0x133_DPC_nt!_??_::FNODOBFM::_string_
    CPUID:        "Intel(R) Core(TM) i7 CPU         920  @ 2.67GHz"
    MaxSpeed:     2670
    CurrentSpeed: 2665
      BIOS Version                  F7j
      BIOS Release Date             03/07/2011
      Manufacturer                  Gigabyte Technology Co., Ltd.
      Product Name                  X58A-UD5
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sun Jan 25 05:35:11.143 2015 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\012515-14781-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.17476.amd64fre.winblue_r5.141029-1500
    System Uptime:0 days 11:29:55.859
    Probably caused by :ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+2c418 )
    BugCheck 133, {0, 501, 500, 0}
    BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
    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
    BUGCHECK_STR:  0x133
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  MsMpEng.exe
    FAILURE_BUCKET_ID: 0x133_DPC_nt!_??_::FNODOBFM::_string_
    CPUID:        "Intel(R) Core(TM) i7 CPU         920  @ 2.67GHz"
    MaxSpeed:     2670
    CurrentSpeed: 2665
      BIOS Version                  F7j
      BIOS Release Date             03/07/2011
      Manufacturer                  Gigabyte Technology Co., Ltd.
      Product Name                  X58A-UD5
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Thu Jan 22 06:23:21.502 2015 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\012215-15671-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.17476.amd64fre.winblue_r5.141029-1500
    System Uptime:2 days 18:36:39.218
    Probably caused by :ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+2c418 )
    BugCheck 133, {0, 501, 500, 0}
    BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
    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
    BUGCHECK_STR:  0x133
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x133_DPC_nt!_??_::FNODOBFM::_string_
    CPUID:        "Intel(R) Core(TM) i7 CPU         920  @ 2.67GHz"
    MaxSpeed:     2670
    CurrentSpeed: 2665
      BIOS Version                  F7j
      BIOS Release Date             03/07/2011
      Manufacturer                  Gigabyte Technology Co., Ltd.
      Product Name                  X58A-UD5
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Wed Jan 14 07:15:11.470 2015 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\011415-14093-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.17476.amd64fre.winblue_r5.141029-1500
    System Uptime:0 days 23:11:19.187
    Probably caused by :ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+2c418 )
    BugCheck 133, {0, 501, 500, 0}
    BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
    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
    BUGCHECK_STR:  0x133
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  MsMpEng.exe
    FAILURE_BUCKET_ID: 0x133_DPC_nt!_??_::FNODOBFM::_string_
    CPUID:        "Intel(R) Core(TM) i7 CPU         920  @ 2.67GHz"
    MaxSpeed:     2670
    CurrentSpeed: 2665
      BIOS Version                  F7j
      BIOS Release Date             03/07/2011
      Manufacturer                  Gigabyte Technology Co., Ltd.
      Product Name                  X58A-UD5
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Tue Jan 13 08:00:40.862 2015 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\011315-14171-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.17476.amd64fre.winblue_r5.141029-1500
    System Uptime:1 days 1:46:26.578
    Probably caused by :ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+2c418 )
    BugCheck 133, {0, 501, 500, 0}
    BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
    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
    BUGCHECK_STR:  0x133
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x133_DPC_nt!_??_::FNODOBFM::_string_
    CPUID:        "Intel(R) Core(TM) i7 CPU         920  @ 2.67GHz"
    MaxSpeed:     2670
    CurrentSpeed: 2665
      BIOS Version                  F7j
      BIOS Release Date             03/07/2011
      Manufacturer                  Gigabyte Technology Co., Ltd.
      Product Name                  X58A-UD5
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Mon Jan 12 06:11:18.565 2015 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\011215-14109-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.17476.amd64fre.winblue_r5.141029-1500
    System Uptime:1 days 0:19:17.281
    Probably caused by :ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+2c418 )
    BugCheck 133, {0, 501, 500, 0}
    BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
    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
    BUGCHECK_STR:  0x133
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x133_DPC_nt!_??_::FNODOBFM::_string_
    CPUID:        "Intel(R) Core(TM) i7 CPU         920  @ 2.67GHz"
    MaxSpeed:     2670
    CurrentSpeed: 2665
      BIOS Version                  F7j
      BIOS Release Date             03/07/2011
      Manufacturer                  Gigabyte Technology Co., Ltd.
      Product Name                  X58A-UD5
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sun Jan 11 05:49:57.329 2015 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\011115-18312-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.17476.amd64fre.winblue_r5.141029-1500
    System Uptime:9 days 19:01:17.500
    Probably caused by :ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+2c418 )
    BugCheck 133, {0, 501, 500, 0}
    BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
    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
    BUGCHECK_STR:  0x133
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x133_DPC_nt!_??_::FNODOBFM::_string_
    CPUID:        "Intel(R) Core(TM) i7 CPU         920  @ 2.67GHz"
    MaxSpeed:     2670
    CurrentSpeed: 2665
      BIOS Version                  F7j
      BIOS Release Date             03/07/2011
      Manufacturer                  Gigabyte Technology Co., Ltd.
      Product Name                  X58A-UD5
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sun Dec 28 06:30:59.892 2014 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\122814-21765-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.17476.amd64fre.winblue_r5.141029-1500
    System Uptime:2 days 4:10:49.609
    Probably caused by :ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+2c418 )
    BugCheck 133, {0, 501, 500, 0}
    BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
    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
    BUGCHECK_STR:  0x133
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x133_DPC_nt!_??_::FNODOBFM::_string_
    CPUID:        "Intel(R) Core(TM) i7 CPU         920  @ 2.67GHz"
    MaxSpeed:     2670
    CurrentSpeed: 2665
      BIOS Version                  F7j
      BIOS Release Date             03/07/2011
      Manufacturer                  Gigabyte Technology Co., Ltd.
      Product Name                  X58A-UD5
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Fri Dec 26 02:17:53.205 2014 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\122614-36640-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.17476.amd64fre.winblue_r5.141029-1500
    System Uptime:0 days 17:02:51.921
    Probably caused by :ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+2c418 )
    BugCheck 133, {0, 501, 500, 0}
    BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
    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
    BUGCHECK_STR:  0x133
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x133_DPC_nt!_??_::FNODOBFM::_string_
    CPUID:        "Intel(R) Core(TM) i7 CPU         920  @ 2.67GHz"
    MaxSpeed:     2670
    CurrentSpeed: 2665
      BIOS Version                  F7j
      BIOS Release Date             03/07/2011
      Manufacturer                  Gigabyte Technology Co., Ltd.
      Product Name                  X58A-UD5
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Thu Dec 25 09:12:19.769 2014 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\122514-39062-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.17476.amd64fre.winblue_r5.141029-1500
    System Uptime:5 days 2:04:49.484
    Probably caused by :ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+2c418 )
    BugCheck 133, {0, 501, 500, 0}
    BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
    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
    BUGCHECK_STR:  0x133
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x133_DPC_nt!_??_::FNODOBFM::_string_
    CPUID:        "Intel(R) Core(TM) i7 CPU         920  @ 2.67GHz"
    MaxSpeed:     2670
    CurrentSpeed: 2665
      BIOS Version                  F7j
      BIOS Release Date             03/07/2011
      Manufacturer                  Gigabyte Technology Co., Ltd.
      Product Name                  X58A-UD5
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sat Dec 20 07:05:08.729 2014 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\122014-19796-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.17476.amd64fre.winblue_r5.141029-1500
    System Uptime:5 days 18:58:16.531
    Probably caused by :ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+2c418 )
    BugCheck 133, {0, 501, 500, 0}
    BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
    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
    BUGCHECK_STR:  0x133
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  svchost.exe
    FAILURE_BUCKET_ID: 0x133_DPC_nt!_??_::FNODOBFM::_string_
    CPUID:        "Intel(R) Core(TM) i7 CPU         920  @ 2.67GHz"
    MaxSpeed:     2670
    CurrentSpeed: 2665
      BIOS Version                  F7j
      BIOS Release Date             03/07/2011
      Manufacturer                  Gigabyte Technology Co., Ltd.
      Product Name                  X58A-UD5
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sun Dec 14 02:11:06.977 2014 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\121314-21359-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.17476.amd64fre.winblue_r5.141029-1500
    System Uptime:0 days 3:02:34.766
    Probably caused by :ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+2c418 )
    BugCheck 133, {0, 501, 500, 0}
    BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
    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
    BUGCHECK_STR:  0x133
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x133_DPC_nt!_??_::FNODOBFM::_string_
    CPUID:        "Intel(R) Core(TM) i7 CPU         920  @ 2.67GHz"
    MaxSpeed:     2670
    CurrentSpeed: 1999
      BIOS Version                  F7j
      BIOS Release Date             03/07/2011
      Manufacturer                  Gigabyte Technology Co., Ltd.
      Product Name                  X58A-UD5
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    
    3rd Party Drivers:
    The following is for information purposes only.
    Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.
    Code:
    **************************Mon Feb  9 11:58:16.995 2015 (UTC - 5:00)**************************
    PxHlpa64.sys                Tue Apr 24 13:26:29 2012 (4F96E245)
    intelppm.sys                Thu Aug 22 04:46:35 2013 (5215CFEB)
    dump_storahci.sys           Thu Aug 22 07:40:39 2013 (5215F8B7)
    Rt630x64.sys                Tue Aug 26 02:24:06 2014 (53FC2806)
    nvhda64v.sys                Thu Oct  9 13:02:27 2014 (5436BFA3)
    wachidrouter.sys            Sat Oct 25 16:51:40 2014 (544C0D5C)
    wacomrouterfilter.sys       Sat Oct 25 16:51:47 2014 (544C0D63)
    nvvad64v.sys                Thu Nov 20 10:33:54 2014 (546E09E2)
    VBoxEhciR0.r0               Fri Nov 21 09:03:50 2014 (546F4646)
    VBoxUSBMon.sys              Mon Nov 24 06:06:09 2014 (54731121)
    VBoxDDR0.r0                 Mon Nov 24 06:06:09 2014 (54731121)
    VBoxDD2R0.r0                Mon Nov 24 06:06:09 2014 (54731121)
    VBoxNetAdp.sys              Mon Nov 24 06:06:09 2014 (54731121)
    VBoxNetFlt.sys              Mon Nov 24 06:06:09 2014 (54731121)
    VMMR0.r0                    Mon Nov 24 06:07:16 2014 (54731164)
    VBoxDrv.sys                 Mon Nov 24 06:07:17 2014 (54731165)
    ceusbaud.sys                Wed Dec 10 13:47:18 2014 (54889536)
    nvlddmkm.sys                Fri Jan  9 17:22:06 2015 (54B0548E)
    NvStreamKms.sys             Mon Jan 12 12:56:42 2015 (54B40ADA)
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sat Jan 31 11:05:58.412 2015 (UTC - 5:00)**************************
    ceusbaud.sys                Tue Jul 16 13:00:10 2013 (51E57C1A)
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Thu Jan 29 13:00:12.362 2015 (UTC - 5:00)**************************
    gdrv.sys                    Thu Mar 12 23:22:29 2009 (49B9D175)
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Wed Jan 28 07:41:13.969 2015 (UTC - 5:00)**************************
    Rt630x64.sys                Fri May 10 05:59:08 2013 (518CC4EC)
    nvhda64v.sys                Thu Nov 28 08:38:09 2013 (52974741)
    nvlddmkm.sys                Wed Jul  2 13:42:02 2014 (53B4446A)
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sun Jan 25 05:35:11.143 2015 (UTC - 5:00)**************************
    rtwlanu.sys                 Wed Jul 10 10:48:31 2013 (51DD743F)
    wachidrouter.sys            Mon Oct  6 19:46:58 2014 (543329F2)
    wacomrouterfilter.sys       Mon Oct  6 19:47:05 2014 (543329F9)
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sun Dec 28 06:30:59.892 2014 (UTC - 5:00)**************************
    wacomrouterfilter.sys       Thu Dec 20 17:19:54 2012 (50D38F0A)
    wachidrouter.sys            Tue Apr 30 13:16:27 2013 (517FFC6B)
    
    http://www.carrona.org/drivers/driver.php?id=PxHlpa64.sys
    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=Rt630x64.sys
    http://www.carrona.org/drivers/driver.php?id=nvhda64v.sys
    http://www.carrona.org/drivers/driver.php?id=wachidrouter.sys
    http://www.carrona.org/drivers/driver.php?id=wacomrouterfilter.sys
    http://www.carrona.org/drivers/driver.php?id=nvvad64v.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=VBoxUSBMon.sys
    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=VMMR0.r0
    http://www.carrona.org/drivers/driver.php?id=VBoxDrv.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=nvlddmkm.sys
    http://www.carrona.org/drivers/driver.php?id=NvStreamKms.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=gdrv.sys
    http://www.carrona.org/drivers/driver.php?id=Rt630x64.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=rtwlanu.sys
    http://www.carrona.org/drivers/driver.php?id=wachidrouter.sys
    http://www.carrona.org/drivers/driver.php?id=wacomrouterfilter.sys
    http://www.carrona.org/drivers/driver.php?id=wacomrouterfilter.sys
    http://www.carrona.org/drivers/driver.php?id=wachidrouter.sys
      My System SpecsSystem Spec

  7. #17


    Posts : 18
    Windows 8.1


    The BIOS/UEFI dates from 2011. While not being excessively old, I have seen problems with Gigabyte boards - so I'd strongly suggest updating to the latest version. Presuming that your board is a rev 1.0 and not a rev 2.0 board - your system is using a beta BIOS. There is one further beta BIOS available (F8a) - and there's always the possibility of reverting to a non-beta BIOS. Here's the link that I found: GIGABYTE - Motherboard - Socket 1366 - GA-X58A-UD5 (rev. 1.0)
    I have updated the BIOS when this first started happening with no change. That is when the BIOS was updated to the beta version. I will upgrade the BIOS to that newer version later tonight or tomorrow.

    First I'd suggest this tutorial as it may help to identify the cause(s) within your system: How to Diagnose and Fix High DPC Latency Issues with WPA (Windows Vista/7/8) - Sysnative Forums
    I actually found that earlier when searching around and tried running through some of the possible solutions and diagnostic utilities. Nothing stuck out and if you would like to look them over, I can happily supply the logging files that are created whilst running it.

    Please uninstall Virtual Box while we're testing. It's easily reinstalled if needed, but it excessively complicates the BSOD analysis when it's present (and it's a bit buggy w/Win8/8.1 IME). I've had issues on my system with the Virtual Box Ethernet adapter and have disabled it in Device Manager (and, funny thing, my network still works in the VM's).
    I will have to do that over the weekend to test this out, as I need it for work during the week.

    Did removing the USB audio device and it's drivers stop the BSOD's?
    Both times in the past few days that a BSoD has occured was while I was at work, which I needed to use that USB device. There has not been a time yet where the device was removed and a BSoD occured, but the time scale and infrequency of the BSoDs are impossible to predict or reproduce without time. I am continuing to remove the device and drivers, rebooting, and leaving the computer on all night to attempt to test this situation.

    Another thing to try is using other USB ports to see if the problem is replicated on all ports (USB 2 and 3).
    The USB Device is now plugged into another port.

    Another thing to try is letting verifier stress Windows drivers - then compare your versions with the updated versions on other systems.
    I would also strongly suggest that you start a topic in the Windows Updates & Activation forum here: https://www.eightforums.com/windows-updates-activation/ IMO there is a strong possibility that missing Windows Updates could be contributing to this problem.
    FYI - the typical Win8.1 installation has over 100 updates.


    I will do this when I have some time to devote to it.

    What is the make/model/wattage and age of your Power Supply?
    It is an Corsair AX1200i, bought I believe about 1-2 years ago as an upgrade to an AX860i. Please note that adding and/or removing drives have made no difference in the frequency of BSoDs.

    The WER section of MSINFO32 shows many, many problems with the vid_18D1&pid_ 4ee1 device. This is most likely an Android USB device - maybe a Nexus phone? Please uninstall the software for this device and then physically remove it from your system.
    I believe that is probably a virtual nexus android device from the ADB/ADT. The BSoDs occured before that was installed. If it is a nexus device, it very well could be either my Nexus 5, 6, 7, 9, or 10.

    I read at one point that you had a USB 3 card installed. Could you remove that (and it's drivers) and test to see if that stops the BSOD's?
    I will remove it when I have a chance to complete the other longer time intensive tasks.

    Please uninstall Gigabyte Easy Saver, it's gdrv.sys driver is known to cause BSOD's on some Windows systems.
    Also uninstall the Gigabyte EasyTune software (if installed) as it causes BSOD's also.
    Could these have been installed through Window's driver installer utility to match drivers to my motherboard? I don't remember installing either of them when I reinstalled Windows.

    The long and the short of it is I will have to devote some time either this week or weekend when I have said free time to test. I will report back with any new findings as I come across them.

    Thanks for taking the time to look at this, usasma!
      My System SpecsSystem Spec

  8. #18


    Posts : 5,139
    Win8.1Pro - Finally!!!


    I understand that this is a lot to ask, and that it will take a lot of time to accomplish.
    I'll be patient awaiting results.

    I don't need the info on the High DPC Latency stuff - you've done a great job so far, and I have confidence in your abilities.

    The Gigabyte drivers don't come on Windows installation media AFAIK.
    From what I recall, they're bundled with Gigabyte utilities and it may not be obvious that you're installing them.
    It's my preference that drivers be removed by uninstalling the application that installed them - but I do have suggestions for those cases where you can't locate an uninstaller (but prefer not to use it).

    My point about the Nexus device was not only that it was having a lot of problems - but also that it was a USB device, and you've got lot's of errors with USB devices in the WER section of MSINFO32.

    As such, I suspect a USB problem - but am not sure exactly what's causing it.
    Right now I don't even have enough info to guess between hardware and software.
    And normally we discount the possibility of Windows problems - but there's evidence of a problem with your Windows Updates, so it could also be a Windows problem.

    Back when Win8.1 first came out, it was having problems counting the updates. This problem was so obvious that I started cautioning people to not rely on the number of updates. That problem seems to have gone away as 8.1 matured - but I have to wonder if your system is still affected by it. I call this into question because the drivers starting with USB are very similar to mine - and if your system was so far out of date, then I'd suspect to see more problems with older drivers in the memory dumps. FYI - the kernel (ntkrnlmp.exe) is dated from Wed Oct 29 18:19:12 2014 - on my system it's dated from Oct 30, 2014.

    Good luck!
      My System SpecsSystem Spec

  9. #19


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


    Thanks everyone for coming with guns blazing

    @John - I believe that the time difference is not a significant one. Are you implying that it is same? If not, then it could be very well different due to the different time zones.

    @Slick - Kindly keep us updated on how it goes ^_^

    -Pranav
      My System SpecsSystem Spec

  10. #20


    Posts : 5,139
    Win8.1Pro - Finally!!!


    The time zone difference between date stamps on drivers is a complicated one. We decided to stop using date/time stamps in the DRT mainly due to that issue.

    What I think is that the system is fully updated - but Windows isn't displaying an appropriate number of drivers.
    The few Windows drivers that I've looked at are all updated to approximately the same level as my system.
    But there is the issue about 8.1 not displaying all updates - so this may actually be normal for this copy of the OS.
    And there is the issue of Windows Updates errors in the WER section of MSINFO32 - but the majority of the errors were from 13/14 Dec 2014, with only 2 on 25Dec2014, only 2 on 01Jan2015, and only 2 on 19Jan2015.

    I'd like to see if the Windows Update & Activation experts can tell us if the system is fully updated.

    I'd also suggest running DISM and SFC.EXE /SCANNOW - just in case:
    Then please run the following DISM commands to see if there's any problems with the system (from an elevated (Run as administrator) Command Prompt). Press Enter after each one:
    Code:
    Dism /Online /Cleanup-Image /ScanHealth
    Code:
    Dism /Online /Cleanup-Image /CheckHealth
    Code:
    Dism /Online /Cleanup-Image /RestoreHealth
    FYI - I have repaired systems using the last command even though problems weren't found with the first 2 - so I suggest running them all.

    From this article: Repair a Windows Image

    You can also run sfc.exe /scannow from an elevated (Run as administrator) Command Prompt to check for further corruption.
      My System SpecsSystem Spec

Page 2 of 4 FirstFirst 1234 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