Windows 8 and 8.1 Forums


BSOD On computer boot DPC_WATCHDOG

  1. #1


    Posts : 3
    win8.1

    BSOD On computer boot DPC_WATCHDOG


    Hi All-

    Recently I started getting a blue screen upon my laptops boot and using bluescreenview has linked it to igdkmd64.sys. I have tried installing intels latest drivers, as well as installing MSI's last driver build and the error still happens.

    Oddly enough the reboot after the blue screen works perfectly, then the next day when I boot up again blue screened and reboot fine same cycle.

    The laptop is a MSI GT60 0NE

    I have attached the crash dump and would appreciate any further ideas or guidance on how to rid myself of this issue

    Thanks,
    Brian

      My System SpecsSystem Spec

  2. #2


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


    In the old days issues with hibernation/sleep were only caused by video drivers.
    More recently, they are caused by things like chipset drivers, storage drivers, even networking drivers (and, of course, video drivers)

    Please provide this information so we can provide a complete analysis (from the Pinned Topic at the top of the forum): Blue Screen of Death (BSOD) Posting Instructions Please use Option 1 as it provides Event Viewer logs.

    Looks to me that it's your Bluetooth drivers - but it's hard to tell with only one memory dump. Please provide the info above in order to help us figure this out. Please be sure to update the Bluetooth drivers from the MSI website to the latest, Win8.1 compatible version (some Win8.1 systems have BSOD issues with Bluetooth drivers from Win8)

    There are also known BSOD problems with the Killer Network Manager that dates from 2013. Please visit the MSI website and get the latest update to this program (a version from 2014 is needed). I presume that your Killer Network Manager dates from the problem period as you Killer network drivers date from 2013 also.
    FYI - here's the canned speech I made up for this:
    At times the Killer Network Manager may cause BSOD problems:
    NOTE: See this link first: BSOD while playing on msi gt70 dragon edition 2 (thanks to kaelaan) It appears that the Killer Service problem was solved with the latest release of the Qualcomm versions of the drivers (so try updating to a version dated from later in 2014).
    The Qualcomm Atheros Killer Service/KillerNetManager is known to cause BSOD's. Please follow the workaround instructions here:
    First, open the Run dialog (Win + R keys) and type in "services.msc" (without the quotes) and press Enter
    Scroll down and locate the "Qualcomm Atheros Killer Service" and right click on it. Select "Stop"
    Right click on it again and this time select "Properties"
    In the dropdown box for "Startup type", select "Disabled", then click on the "OK" button at the bottom of the window

    Next, open Task Manager (right click on TaskBar and select "Task Manager")
    Click on the "More details" dropdown (if present)
    Click on the "Startup" tab
    Scroll down and locate the "KillerNetManager" entry, right click on it and select "Disable"
    There may also be an Install Shield (with the Killer gaming K next to it), if so Right click on it and select "Disable"
    Finally, restart the system in order for the changes to take affect.
    At times the Killer Network Manager will continue to load. If so, it's usually listed in the MSINFO32...Software Environment...Startup Programs section. If it is, please try this:
    It may be that the instructions aren't stopping everything.
    In some cases, there's a program running out of the Program Files/Program Files (x86) directory.
    "c:\program files\qualcomm atheros\killer network manager\killer~1.exe" (NOTE: killer~1.exe is most likely killernetmanager.exe)
    In other cases, there's a program running out of c:\windows\installer\{Long string of letters, numbers, and dashes}\networkmanager.exe_130c27d738f34c89bddf21bcfd74b56d.exe (the long string of letters and numbers may change)

    Here's some things to try
    1) Please see if there are any entries in the Startup tab of Task Manager that are related to Qualcomm/Atheros/Killer Network Manager (and NOT the card itself) and disable them (please let us know what you find) Be careful as the wrong selection can disable the network card.
    2) Check in "msconfig" for any entries that aren't in the Startup tab of Task Manager. Let us know if you find any Qualcomm/Atheros/Killer entries there (we'll disable them differently if they are there).
    3) Locate the "c:\program files\qualcomm atheros\killer network manager\killer~1.exe" and rename the .exe to .BAD (the killer~1 is actually a filename that starts with killer and ends with .exe) There will be an error in event viewer, but it'll stop the bugger from loading.
    4) Locate the "c:\windows\installer\{Long string of letters, numbers, and dashes}\networkmanager.exe_130c27d738f34c89bddf21bcfd74b56d.exe" entry and rename the last .exe to .BAD (the long string of letters and numbers may change)

    Just FYI - here are the MSI workaround instructions: MSI USA - Online Technical Support FAQ
    Please note the drivers below that date from before the release of Windows 8.1 (17 Oct 2013) - check to see that each and every one is compatible w/Windows 8.1 (at the manufacturer's website). If not, you must either remove the device and it's software - or locate a Windows 8.1 compatible update on the web. Removing some drivers may make the system unstable - so if you're unable to find updates, post back for info on the one's that can/cannot be safely removed.

    No need to update the one's that are struckout

    Analysis:
    The following is for informational purposes only.
    Code:
    **************************Thu Aug 28 00:02:21.676 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\082714-7468-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.17085.amd64fre.winblue_gdr.140330-1035
    System Uptime:1 days 5:33:33.389
    *** ERROR: Module load completed but symbols could not be loaded for netbt.sys
    Probably caused by :netbt.sys ( netbt+3079 )
    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_netbt+3079
    CPUID:        "Intel(R) Core(TM) i7-3840QM CPU @ 2.80GHz"
    MaxSpeed:     2800
    CurrentSpeed: 2794
      BIOS Version                  E16F3IMS.30M
      BIOS Release Date             07/06/2012
      Manufacturer                  Micro-Star International Co., Ltd.
      Product Name                  GT60
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    
    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:
    **************************Thu Aug 28 00:02:21.676 2014 (UTC - 4:00)**************************
    MBfilt64.sys                Thu Jul 30 23:40:32 2009 (4A7267B0)
    IntcDAud.sys                Tue Jun 19 10:40:51 2012 (4FE08F73)
    RtsPStor.sys                Tue Jul  3 21:52:57 2012 (4FF3A1F9)
    dump_iaStorA.sys            Sat Sep  1 21:01:24 2012 (5042AFE4)
    iaStorA.sys                 Sat Sep  1 21:01:24 2012 (5042AFE4)
    RTKVHD64.sys                Tue Sep 11 09:57:45 2012 (504F4359)
    SynTP.sys                   Thu Nov 15 14:51:07 2012 (50A547AB)
    Smb_driver_Intel.sys        Thu Nov 15 14:52:55 2012 (50A54817)
    HECIx64.sys                 Mon Dec 17 14:32:21 2012 (50CF7345)
    e22w8x64.sys                Wed Mar 20 17:24:01 2013 (514A28F1)
    SYMEVENT64x86.SYS           Fri Jul 26 22:26:58 2013 (51F32FF2)
    SRTSPX64.SYS                Fri Jul 26 22:45:06 2013 (51F33432)
    Ironx64.SYS                 Mon Jul 29 20:59:35 2013 (51F70FF7)
    SYMDS64.SYS                 Tue Jul 30 19:29:08 2013 (51F84C44)
    intelppm.sys                Thu Aug 22 04:46:35 2013 (5215CFEB)
    ctxusbm.sys                 Mon Sep  9 12:02:22 2013 (522DF10E)
    ccSetx64.sys                Mon Sep 23 23:58:04 2013 (52410DCC)
    NETwew00.sys                Thu Oct 31 10:01:47 2013 (527262CB)
    SRTSP64.SYS                 Mon Feb 10 18:04:55 2014 (52F95B17)
    SYMNETS.SYS                 Thu Feb 13 06:25:14 2014 (52FCAB9A)
    SYMEFA64.SYS                Thu Feb 27 18:32:07 2014 (530FCAF7)
    IDSvia64.sys                Tue Mar  4 23:30:47 2014 (5316A877)
    iwdbus.sys                  Thu Mar 13 17:59:14 2014 (53222A32)
    EraserUtilRebootDrv.sys     Thu Mar 20 12:30:59 2014 (532B17C3)
    eeCtrl64.sys                Thu Mar 20 12:30:59 2014 (532B17C3)
    nvvad64v.sys                Fri Mar 28 09:32:06 2014 (533579D6)
    igdkmd64.sys                Sat May 17 00:17:35 2014 (5376E2DF)
    rzudd.sys                   Mon May 19 02:43:44 2014 (5379A820)
    rzvkeyboard.sys             Mon May 19 02:43:57 2014 (5379A82D)
    rzdaendpt.sys               Mon May 19 02:44:07 2014 (5379A837)
    nvpciflt.sys                Wed Jul  2 13:34:06 2014 (53B4428E)
    nvlddmkm.sys                Wed Jul  2 13:42:02 2014 (53B4446A)
    Hamdrv.sys                  Mon Jul 21 12:08:13 2014 (53CD3AED)
    NvStreamKms.sys             Fri Jul 25 07:35:56 2014 (53D2411C)
    BHDrvx64.sys                Wed Aug  6 22:26:33 2014 (53E2E3D9)
    EX64.SYS                    Mon Aug 11 06:19:41 2014 (53E898BD)
    ENG64.SYS                   Mon Aug 11 06:25:04 2014 (53E89A00)
    
    http://www.carrona.org/drivers/driver.php?id=MBfilt64.sys
    http://www.carrona.org/drivers/driver.php?id=IntcDAud.sys
    http://www.carrona.org/drivers/driver.php?id=RtsPStor.sys
    http://www.carrona.org/drivers/driver.php?id=dump_iaStorA.sys
    http://www.carrona.org/drivers/driver.php?id=iaStorA.sys
    http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys
    http://www.carrona.org/drivers/driver.php?id=SynTP.sys
    http://www.carrona.org/drivers/driver.php?id=Smb_driver_Intel.sys
    http://www.carrona.org/drivers/driver.php?id=HECIx64.sys
    http://www.carrona.org/drivers/driver.php?id=e22w8x64.sys
    http://www.carrona.org/drivers/driver.php?id=SYMEVENT64x86.SYS
    http://www.carrona.org/drivers/driver.php?id=SRTSPX64.SYS
    http://www.carrona.org/drivers/driver.php?id=Ironx64.SYS
    http://www.carrona.org/drivers/driver.php?id=SYMDS64.SYS
    http://www.carrona.org/drivers/driver.php?id=intelppm.sys
    http://www.carrona.org/drivers/driver.php?id=ctxusbm.sys
    http://www.carrona.org/drivers/driver.php?id=ccSetx64.sys
    http://www.carrona.org/drivers/driver.php?id=NETwew00.sys
    http://www.carrona.org/drivers/driver.php?id=SRTSP64.SYS
    http://www.carrona.org/drivers/driver.php?id=SYMNETS.SYS
    http://www.carrona.org/drivers/driver.php?id=SYMEFA64.SYS
    http://www.carrona.org/drivers/driver.php?id=IDSvia64.sys
    http://www.carrona.org/drivers/driver.php?id=iwdbus.sys
    http://www.carrona.org/drivers/driver.php?id=EraserUtilRebootDrv.sys
    http://www.carrona.org/drivers/driver.php?id=eeCtrl64.sys
    http://www.carrona.org/drivers/driver.php?id=nvvad64v.sys
    http://www.carrona.org/drivers/driver.php?id=igdkmd64.sys
    http://www.carrona.org/drivers/driver.php?id=rzudd.sys
    http://www.carrona.org/drivers/driver.php?id=rzvkeyboard.sys
    http://www.carrona.org/drivers/driver.php?id=rzdaendpt.sys
    http://www.carrona.org/drivers/driver.php?id=nvpciflt.sys
    http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
    http://www.carrona.org/drivers/driver.php?id=Hamdrv.sys
    http://www.carrona.org/drivers/driver.php?id=NvStreamKms.sys
    http://www.carrona.org/drivers/driver.php?id=BHDrvx64.sys
    http://www.carrona.org/drivers/driver.php?id=EX64.SYS
    http://www.carrona.org/drivers/driver.php?id=ENG64.SYS
      My System SpecsSystem Spec

  3. #3


    Posts : 3
    win8.1


    I actually have an intel 6300 and do not have the killer wireless only Ethernet, and only the driver no management console. Since I have the 6300 I don't actually have a bluetooth module


    I have uploaded everything from the option one as requested
      My System SpecsSystem Spec

  4. #4


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


    The previous analysis was based off of the lone memory dump (and the assumptions that I made from the little info it contained). Here is a much more thorough analysis thanks to the reports that you submitted.

    Your BIOS dates from 2012. Please check at the manufacturer's website to see if there are any BIOS updates available for your system. Also check the readme file to see if they apply to the problems that you are having. Please be advised that flashing the BIOS is a very unforgiving process - and one mistake can physically damage your motherboard. If possible, use the "inside Windows" flash mechanism (if your OEM provides one).

    E: drive only has about 6% free space. Windows likes 15% free space in order to perform stuff "behind the scenes" without adversely affecting the system's performance. Please free up 15% on ALL hard drives (you can get away with 10% on larger drives and won't notice a large performance penalty)

    MSINFO32 shows a lot of netbt.sys errors (STOP 0x133's). These aren't necessarily bluetooth errors - but rather they are network transport errors (errors communicating within the different networking protocols on the system).

    Please ensure that you have ALL available Windows Updates. MSINFO32 shows a bunch of Windows Update failures - so you'll have to make sure that it's working properly. If not, post back and we'll send you over to the Windows Updates forums for further assistance with that.

    Please uninstall Razer Game Booster as it's known to cause BSOD's on some Windows systems

    MSI Afterburner and Riva Tuner (along with EVGA Precision) are known to cause BSOD's in some Windows systems (it's driver is usually RTCore64.sys). Please un-install them immediately!

    If you're overclocking, please stop the overclock while we're troubleshooting. Feel free to resume the overclock once the system has been stabilized.

    Please note the drivers below that date from before the release of Windows 8.1 (17 Oct 2013) - check to see that each and every one is compatible w/Windows 8.1 (at the manufacturer's website). If not, you must either remove the device and it's software - or locate a Windows 8.1 compatible update on the web. Removing some drivers may make the system unstable - so if you're unable to find updates, post back for info on the one's that can/cannot be safely removed.
    Ignore those that are struckout - as there aren't updates for them.

    If all of this doesn't stop the BSOD's, please run Driver Verifier according to these instructions: Driver Verifier Settings

    Analysis:
    The following is for informational purposes only.
    Code:
    **************************Thu Aug 28 00:02:21.676 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\082714-7468-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.17085.amd64fre.winblue_gdr.140330-1035
    System Uptime:1 days 5:33:33.389
    *** ERROR: Module load completed but symbols could not be loaded for netbt.sys
    Probably caused by :netbt.sys ( netbt+3079 )
    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_netbt+3079
    CPUID:        "Intel(R) Core(TM) i7-3840QM CPU @ 2.80GHz"
    MaxSpeed:     2800
    CurrentSpeed: 2794
      BIOS Version                  E16F3IMS.30M
      BIOS Release Date             07/06/2012
      Manufacturer                  Micro-Star International Co., Ltd.
      Product Name                  GT60
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Tue Aug 26 18:19:55.686 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\082614-6718-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.17085.amd64fre.winblue_gdr.140330-1035
    System Uptime:0 days 18:11:38.398
    *** ERROR: Module load completed but symbols could not be loaded for netbt.sys
    Probably caused by :netbt.sys ( netbt+3079 )
    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_netbt+3079
    CPUID:        "Intel(R) Core(TM) i7-3840QM CPU @ 2.80GHz"
    MaxSpeed:     2800
    CurrentSpeed: 2794
      BIOS Version                  E16F3IMS.30M
      BIOS Release Date             07/06/2012
      Manufacturer                  Micro-Star International Co., Ltd.
      Product Name                  GT60
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Mon Aug 25 23:51:12.148 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\082514-7375-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.17085.amd64fre.winblue_gdr.140330-1035
    System Uptime:0 days 2:10:56.859
    *** ERROR: Module load completed but symbols could not be loaded for netbt.sys
    Probably caused by :netbt.sys ( netbt+21ea )
    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_netbt+21ea
    CPUID:        "Intel(R) Core(TM) i7-3840QM CPU @ 2.80GHz"
    MaxSpeed:     2800
    CurrentSpeed: 2794
      BIOS Version                  E16F3IMS.30M
      BIOS Release Date             07/06/2012
      Manufacturer                  Micro-Star International Co., Ltd.
      Product Name                  GT60
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sun Aug 24 00:13:51.672 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\082314-6859-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.17085.amd64fre.winblue_gdr.140330-1035
    System Uptime:0 days 8:49:24.385
    *** ERROR: Module load completed but symbols could not be loaded for netbt.sys
    Probably caused by :netbt.sys ( netbt+3079 )
    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_netbt+3079
    CPUID:        "Intel(R) Core(TM) i7-3840QM CPU @ 2.80GHz"
    MaxSpeed:     2800
    CurrentSpeed: 2794
      BIOS Version                  E16F3IMS.30M
      BIOS Release Date             07/06/2012
      Manufacturer                  Micro-Star International Co., Ltd.
      Product Name                  GT60
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sat Aug 23 15:23:57.131 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\082314-7468-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.17085.amd64fre.winblue_gdr.140330-1035
    System Uptime:2 days 23:25:40.844
    *** ERROR: Module load completed but symbols could not be loaded for netbt.sys
    Probably caused by :netbt.sys ( netbt+3079 )
    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_netbt+3079
    CPUID:        "Intel(R) Core(TM) i7-3840QM CPU @ 2.80GHz"
    MaxSpeed:     2800
    CurrentSpeed: 2794
      BIOS Version                  E16F3IMS.30M
      BIOS Release Date             07/06/2012
      Manufacturer                  Micro-Star International Co., Ltd.
      Product Name                  GT60
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sun Aug 17 15:23:36.134 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\081714-6937-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.17085.amd64fre.winblue_gdr.140330-1035
    System Uptime:0 days 0:00:51.847
    *** ERROR: Module load completed but symbols could not be loaded for netbt.sys
    Probably caused by :netbt.sys ( netbt+3079 )
    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_netbt+3079
    CPUID:        "Intel(R) Core(TM) i7-3840QM CPU @ 2.80GHz"
    MaxSpeed:     2800
    CurrentSpeed: 2794
      BIOS Version                  E16F3IMS.30M
      BIOS Release Date             07/06/2012
      Manufacturer                  Micro-Star International Co., Ltd.
      Product Name                  GT60
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sat Aug 16 02:40:42.647 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\081714-7640-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.17085.amd64fre.winblue_gdr.140330-1035
    System Uptime:1 days 2:47:20.359
    *** ERROR: Module load completed but symbols could not be loaded for netbt.sys
    *** ERROR: Module load completed but symbols could not be loaded for tdx.sys
    *** ERROR: Module load completed but symbols could not be loaded for tcpip.sys
    *** WARNING: Unable to verify timestamp for NETwew00.sys
    *** ERROR: Module load completed but symbols could not be loaded for NETwew00.sys
    Probably caused by :netbt.sys ( netbt+1ef4 )
    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_netbt+1ef4
    CPUID:        "Intel(R) Core(TM) i7-3840QM CPU @ 2.80GHz"
    MaxSpeed:     2800
    CurrentSpeed: 2794
      BIOS Version                  E16F3IMS.30M
      BIOS Release Date             07/06/2012
      Manufacturer                  Micro-Star International Co., Ltd.
      Product Name                  GT60
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Thu Aug 14 21:34:09.662 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\081414-8000-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.17085.amd64fre.winblue_gdr.140330-1035
    System Uptime:6 days 23:58:59.375
    *** ERROR: Module load completed but symbols could not be loaded for netbt.sys
    Probably caused by :netbt.sys ( netbt+3079 )
    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_netbt+3079
    CPUID:        "Intel(R) Core(TM) i7-3840QM CPU @ 2.80GHz"
    MaxSpeed:     2800
    CurrentSpeed: 2794
      BIOS Version                  E16F3IMS.30M
      BIOS Release Date             07/06/2012
      Manufacturer                  Micro-Star International Co., Ltd.
      Product Name                  GT60
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Thu Aug  7 21:34:35.276 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\080714-7875-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.17085.amd64fre.winblue_gdr.140330-1035
    System Uptime:8 days 0:05:50.876
    *** ERROR: Module load completed but symbols could not be loaded for netbt.sys
    *** ERROR: Module load completed but symbols could not be loaded for tdx.sys
    *** ERROR: Module load completed but symbols could not be loaded for tcpip.sys
    *** WARNING: Unable to verify timestamp for NETwew00.sys
    *** ERROR: Module load completed but symbols could not be loaded for NETwew00.sys
    Probably caused by :netbt.sys ( netbt+1ef4 )
    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_netbt+1ef4
    CPUID:        "Intel(R) Core(TM) i7-3840QM CPU @ 2.80GHz"
    MaxSpeed:     2800
    CurrentSpeed: 2794
      BIOS Version                  E16F3IMS.30M
      BIOS Release Date             07/06/2012
      Manufacturer                  Micro-Star International Co., Ltd.
      Product Name                  GT60
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    
    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:
    **************************Thu Aug 28 00:02:21.676 2014 (UTC - 4:00)**************************
    MBfilt64.sys                Thu Jul 30 23:40:32 2009 (4A7267B0)
    IntcDAud.sys                Tue Jun 19 10:40:51 2012 (4FE08F73)
    RtsPStor.sys                Tue Jul  3 21:52:57 2012 (4FF3A1F9)
    dump_iaStorA.sys            Sat Sep  1 21:01:24 2012 (5042AFE4)
    iaStorA.sys                 Sat Sep  1 21:01:24 2012 (5042AFE4)
    RTKVHD64.sys                Tue Sep 11 09:57:45 2012 (504F4359)
    SynTP.sys                   Thu Nov 15 14:51:07 2012 (50A547AB)
    Smb_driver_Intel.sys        Thu Nov 15 14:52:55 2012 (50A54817)
    HECIx64.sys                 Mon Dec 17 14:32:21 2012 (50CF7345)
    e22w8x64.sys                Wed Mar 20 17:24:01 2013 (514A28F1)
    SYMEVENT64x86.SYS           Fri Jul 26 22:26:58 2013 (51F32FF2)
    SRTSPX64.SYS                Fri Jul 26 22:45:06 2013 (51F33432)
    Ironx64.SYS                 Mon Jul 29 20:59:35 2013 (51F70FF7)
    SYMDS64.SYS                 Tue Jul 30 19:29:08 2013 (51F84C44)
    intelppm.sys                Thu Aug 22 04:46:35 2013 (5215CFEB)
    ctxusbm.sys                 Mon Sep  9 12:02:22 2013 (522DF10E)
    ccSetx64.sys                Mon Sep 23 23:58:04 2013 (52410DCC)
    NETwew00.sys                Thu Oct 31 10:01:47 2013 (527262CB)
    SRTSP64.SYS                 Mon Feb 10 18:04:55 2014 (52F95B17)
    SYMNETS.SYS                 Thu Feb 13 06:25:14 2014 (52FCAB9A)
    SYMEFA64.SYS                Thu Feb 27 18:32:07 2014 (530FCAF7)
    IDSvia64.sys                Tue Mar  4 23:30:47 2014 (5316A877)
    iwdbus.sys                  Thu Mar 13 17:59:14 2014 (53222A32)
    EraserUtilRebootDrv.sys     Thu Mar 20 12:30:59 2014 (532B17C3)
    eeCtrl64.sys                Thu Mar 20 12:30:59 2014 (532B17C3)
    nvvad64v.sys                Fri Mar 28 09:32:06 2014 (533579D6)
    igdkmd64.sys                Sat May 17 00:17:35 2014 (5376E2DF)
    rzudd.sys                   Mon May 19 02:43:44 2014 (5379A820)
    rzvkeyboard.sys             Mon May 19 02:43:57 2014 (5379A82D)
    rzdaendpt.sys               Mon May 19 02:44:07 2014 (5379A837)
    nvpciflt.sys                Wed Jul  2 13:34:06 2014 (53B4428E)
    nvlddmkm.sys                Wed Jul  2 13:42:02 2014 (53B4446A)
    Hamdrv.sys                  Mon Jul 21 12:08:13 2014 (53CD3AED)
    NvStreamKms.sys             Fri Jul 25 07:35:56 2014 (53D2411C)
    BHDrvx64.sys                Wed Aug  6 22:26:33 2014 (53E2E3D9)
    EX64.SYS                    Mon Aug 11 06:19:41 2014 (53E898BD)
    ENG64.SYS                   Mon Aug 11 06:25:04 2014 (53E89A00)
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Tue Aug 26 18:19:55.686 2014 (UTC - 4:00)**************************
    IntcDAud.sys                Fri Feb 21 08:50:26 2014 (530759A2)
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Mon Aug 25 23:51:12.148 2014 (UTC - 4:00)**************************
    iwdbus.sys                  Thu Sep 26 17:38:04 2013 (5244A93C)
    igdkmd64.sys                Wed Dec 18 15:49:12 2013 (52B20A48)
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sun Aug 24 00:13:51.672 2014 (UTC - 4:00)**************************
    BHDrvx64.sys                Tue May  6 03:04:20 2014 (53688974)
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sun Aug 17 15:23:36.134 2014 (UTC - 4:00)**************************
    tap0901.sys                 Thu Aug 22 08:40:01 2013 (521606A1)
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sat Aug 16 02:40:42.647 2014 (UTC - 4:00)**************************
    EX64.SYS                    Thu Aug 22 16:36:51 2013 (52167663)
    ENG64.SYS                   Thu Aug 22 16:38:20 2013 (521676BC)
    
    http://www.carrona.org/drivers/driver.php?id=MBfilt64.sys
    http://www.carrona.org/drivers/driver.php?id=IntcDAud.sys
    http://www.carrona.org/drivers/driver.php?id=RtsPStor.sys
    http://www.carrona.org/drivers/driver.php?id=dump_iaStorA.sys
    http://www.carrona.org/drivers/driver.php?id=iaStorA.sys
    http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys
    http://www.carrona.org/drivers/driver.php?id=SynTP.sys
    http://www.carrona.org/drivers/driver.php?id=Smb_driver_Intel.sys
    http://www.carrona.org/drivers/driver.php?id=HECIx64.sys
    http://www.carrona.org/drivers/driver.php?id=e22w8x64.sys
    http://www.carrona.org/drivers/driver.php?id=SYMEVENT64x86.SYS
    http://www.carrona.org/drivers/driver.php?id=SRTSPX64.SYS
    http://www.carrona.org/drivers/driver.php?id=Ironx64.SYS
    http://www.carrona.org/drivers/driver.php?id=SYMDS64.SYS
    http://www.carrona.org/drivers/driver.php?id=intelppm.sys
    http://www.carrona.org/drivers/driver.php?id=ctxusbm.sys
    http://www.carrona.org/drivers/driver.php?id=ccSetx64.sys
    http://www.carrona.org/drivers/driver.php?id=NETwew00.sys
    http://www.carrona.org/drivers/driver.php?id=SRTSP64.SYS
    http://www.carrona.org/drivers/driver.php?id=SYMNETS.SYS
    http://www.carrona.org/drivers/driver.php?id=SYMEFA64.SYS
    http://www.carrona.org/drivers/driver.php?id=IDSvia64.sys
    http://www.carrona.org/drivers/driver.php?id=iwdbus.sys
    http://www.carrona.org/drivers/driver.php?id=EraserUtilRebootDrv.sys
    http://www.carrona.org/drivers/driver.php?id=eeCtrl64.sys
    http://www.carrona.org/drivers/driver.php?id=nvvad64v.sys
    http://www.carrona.org/drivers/driver.php?id=igdkmd64.sys
    http://www.carrona.org/drivers/driver.php?id=rzudd.sys
    http://www.carrona.org/drivers/driver.php?id=rzvkeyboard.sys
    http://www.carrona.org/drivers/driver.php?id=rzdaendpt.sys
    http://www.carrona.org/drivers/driver.php?id=nvpciflt.sys
    http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
    http://www.carrona.org/drivers/driver.php?id=Hamdrv.sys
    http://www.carrona.org/drivers/driver.php?id=NvStreamKms.sys
    http://www.carrona.org/drivers/driver.php?id=BHDrvx64.sys
    http://www.carrona.org/drivers/driver.php?id=EX64.SYS
    http://www.carrona.org/drivers/driver.php?id=ENG64.SYS
    http://www.carrona.org/drivers/driver.php?id=IntcDAud.sys
    http://www.carrona.org/drivers/driver.php?id=iwdbus.sys
    http://www.carrona.org/drivers/driver.php?id=igdkmd64.sys
    http://www.carrona.org/drivers/driver.php?id=BHDrvx64.sys
    http://www.carrona.org/drivers/driver.php?id=tap0901.sys
    http://www.carrona.org/drivers/driver.php?id=EX64.SYS
    http://www.carrona.org/drivers/driver.php?id=ENG64.SYS
      My System SpecsSystem Spec

  5. #5


    Posts : 3
    win8.1


    Just wanted to share uninstalled hamachi with got rid of the virtual network adapter... and it stopped.
      My System SpecsSystem Spec

  6. #6


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


    That's great news! Thanks for letting us know!
      My System SpecsSystem Spec

BSOD On computer boot DPC_WATCHDOG
Related Threads
Getting DPC_watchdog error, my computer makes a loud noise while it happens, it has happened while playing Counter strike global offensive, League of legends and when just browsing the internet. I have uploaded the file this link told me to...
i encounter this bsod while im flashing my nokia n8. some problem i googled was caused by the usb ports and solution is change the ports. but didnt work out for me. i didnt have the kernel problem before but the dpc_watchdog. care to help me fix? 52638
BSOD playing WoW - DPC_Watchdog / nvlddmkm.sys in BSOD Crashes and Debugging
Hey! Just updated to the latest stable nVidia drivers the other day, and since I've gotten 3 BSOD while playing WoW citing a DPC_Watchdog_Violation. Right before the BSOD, the game would minimize to the tray a few times before the actual BSOD occured. Maybe I need to roll back? Not sure, but...
I have been having seemingly random BSOD DPC_WATCHDOG ever since I updated to Windows 8.1. This can occur either when I'm playing games, using Visual Studio 2012, or browsing the web. Any help would be great.
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 :)
bsod/dpc_watchdog mainly among others in BSOD Crashes and Debugging
happens while playing games. if u could take a look at my dmp file would be appreciated; thanks!
Bsod dpc_watchdog-violation in BSOD Crashes and Debugging
Hope someone can help here. I am starting to wish I stuck with Win 7 Professional which was stable and running well. Have had nothing but problems with Win8 and hard to believe this will be released commercially soon. I am getting somewhat random BSOD screens, but it does seem to happen more...
Eight Forums Android App Eight Forums IOS App Follow us on Facebook