Windows 8 and 8.1 Forums

BSOD-Watchdog Restart; Automatic Repair Loop after updates

  1. #1

    Posts : 4
    Windows 8.1 - 64bit

    BSOD-Watchdog Restart; Automatic Repair Loop after updates

    The title says it all. I included my .zip from the SF Diagnostic Tool.

    I initially had a different processor and motherboard, but after changing both of those due to failures, everything is now working fine, until I do a restart.

    The main restart issue is that it gets stuck in an automatic repair loop until I can get to Safe Mode and then restarting from there somehow undoes the updates from Windows Update.

    If I keep those updates off, though, and just try to do a general restart, I get a BSOD Watchdog error. I'll include that log, just in case. It'll be in since I'm including the whole CBS folder from Windows\Logs.

    I'm really not sure what's wrong here. Thanks for your help and I'll update this post or post more info, if need be. Thanks again.

      My System SpecsSystem Spec

  2. #2

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

    We'll try to fix the BSOD issues. If that doesn't work, then I'll send you over to the Windows Updates & Activation forums for some expert assistance with your CBS logs.

    Your BIOS dates from 2013. 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).

    SAlpham64 is blamed in the WER section of MSINFO32. This belongs to your SteelSeries Keyboard Driver. Please uninstall it immediately. Also, if you're able, try another keyboard. After the system is stabilized, feel free to download and install a fresh copy of the latest, Win8.1 compatible version of the keyboard drivers.

    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.

    The drivers that are struckout don't have updates available (AFAIK).
    DO NOT delete them, just leave them be.

    Only 56 Windows Updates installed. Most systems have 70 to 90 or more. Please visit Windows Update and get ALL available updates (it may take several trips to get them all).

    Don't worry about the specific number, it's just important that you have checked and installed any updates that were available (and didn't experience any errors).

    The following is for informational purposes only.
    **************************Tue Sep 23 17:34:56.841 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\092314-12531-01.dmp]
    Windows 8 Kernel Version 9600 MP (4 procs) Free x64
    Built by: 9600.17041.amd64fre.winblue_gdr.140305-1710
    System Uptime:0 days 0:32:58.547
    *** WARNING: Unable to verify timestamp for SAlpham64.sys
    *** ERROR: Module load completed but symbols could not be loaded for SAlpham64.sys
    *** ERROR: Module load completed but symbols could not be loaded for Wdf01000.sys
    *** ERROR: Module load completed but symbols could not be loaded for USBXHCI.SYS
    Probably caused by :SAlpham64.sys ( SAlpham64+3570 )
    BugCheck 133, {0, 501, 500, 0}
    BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
    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
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x133_DPC_SAlpham64+3570
    CPUID:        "Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz"
    MaxSpeed:     3400
    CurrentSpeed: 3400
      BIOS Version                  P2.80
      BIOS Release Date             07/01/2013
      Manufacturer                  To Be Filled By O.E.M.
      Product Name                  To Be Filled By O.E.M.
    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.
    **************************Tue Sep 23 17:34:56.841 2014 (UTC - 4:00)**************************
    HECIx64.sys                 Mon Jul  2 18:14:58 2012 (4FF21D62) - Intel Management Engine
    ISCTD64.sys                 Tue Nov 27 14:52:34 2012 (50B51A02) - Intel Smart Connect
    k57nd60a.sys                Tue Jan 29 19:48:55 2013 (51086DF7) - networking driver
    eamonm.sys                  Thu Aug 15 10:53:50 2013 (520CEB7E) - antivirus driver
    ehdrv.sys                   Thu Aug 15 10:54:11 2013 (520CEB93)- antivirus driver
    epfwwfpr.sys                Thu Aug 15 10:55:17 2013 (520CEBD5)- antivirus driver
    edevmon.sys                 Mon Aug 19 09:00:54 2013 (52121706)- antivirus driver
    intelppm.sys                Thu Aug 22 04:46:35 2013 (5215CFEB)
    dump_storahci.sys           Thu Aug 22 07:40:39 2013 (5215F8B7)
    iwdbus.sys                  Thu Mar 13 17:59:14 2014 (53222A32)
    igdkmd64.sys                Sat May 17 00:17:35 2014 (5376E2DF)
    SteelBus64.sys              Tue May 27 12:42:05 2014 (5384C05D)
    SAlpham64.sys               Tue May 27 12:46:34 2014 (5384C16A)
    nvhda64v.sys                Mon Jul 21 10:17:53 2014 (53CD2111)
    nvvad64v.sys                Thu Sep  4 13:10:48 2014 (54089D18)
    NvStreamKms.sys             Sat Sep  6 00:37:11 2014 (540A8F77)
    nvlddmkm.sys                Sat Sep 13 15:59:50 2014 (5414A236)
      My System SpecsSystem Spec

  3. #3

    Posts : 4
    Windows 8.1 - 64bit

    There were no BIOS updates. I'm fully up to date on that.

    I updated Intel Management, Smart Connect, and the Broadcom networking driver.

    The Steelseries keyboard is definitely the issue. I uninstalled the Steelseries keyboard driver, tried to reinstall them when it was unplugged and then restarted, plugged it back in, restarted again, and got watchdog.

    The issue lies in the software, Steelseries Engine. For some reason, after uninstalling that, I'm able to plug in and use my keyboard with no watchdog error. I'll send a new zip file so you can see if there's something I can do for Steelseries Engine. I really want to use it so I can change my colors on my mouse and keyboard.

    All the Windows Updates worked after I uninstalled Steelseries Engine, by the way! Thank you very much!

    If at all possible, can you help me with the Steelseries Engine problem? I'll send you my new diagnostics with everything working as it should.
      My System SpecsSystem Spec

  4. #4

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

    I'd suggest that you work with the people in the Drivers & Hardware - Windows 8 Forums
    They are more familiar with these sort of issues than I am (I specialize in BSOD's).

    My only 2 suggestions are:
    - try another SteelSeries keyboard to see if this one is broken
    - contact the SteelSeries website for additional tech support assistance.

    Good luck!
      My System SpecsSystem Spec

  5. #5

    Posts : 4
    Windows 8.1 - 64bit

    Thank you very much. I will do that soon. You are very helpful!
      My System SpecsSystem Spec

BSOD-Watchdog Restart; Automatic Repair Loop after updates
Related Threads
Automatic Repair Loop in General Support
Okay, so I booted my friend's laptop and began to get her software to get her laptop more secure (after finding tons of stuff on her daughter's laptop). Well, as I went to install one, before even clicking a thing, the screen starts flickering to the point it looks like constant loading. Can't even...
Hello, last night, I was using my computer fine, playing a few League of Legends games before I turned off my PC and went to bed. This morning, I tried to turn on my computer and lo and behold, I encountered Windows 8.1 trying to "automatically repair" and it wouldn't boot me to the desktop. I have...
Stuck in the 'Automatic Repair' loop! Tried sfc with the offbootdir & offwindir options & get the reply that it's found things wrong, but can't fix them.
Hello. I was using my PC earlier and I noticed my Skype and other programs I had open that were installed on my C: Drive (OCZ Vertex 3 SSD) started locking up. I even had troubles opening the task manager. After locking up for several seconds, I just restarted but the problems resumed. The very...
Automatic Repair Loop in General Support
Hi Everyone, I'm stuck in an automatic repair loop. One suggestion has been to use a USB recovery disk but I can't create one now that I don't have access to Windows 8. Any suggestions?
I have had crashing in the past few days (not sure what caused it - that's what I'm hoping to figure out). It started with the PC not shutting down. I would shut down and it would just restart instead. Afterwards it again BSOD'd on me twice - the second time it went into an automatic repair...
Windows 8 automatic repair loop in BSOD Crashes and Debugging
I Just bought a new computer with Windows 8 already installed, started using it, and every 30 minutes after i booted it, it crashed. So i tried to restore the initial definitions of the computer by using the option to do so. While the computer was being restored, it crashed, and then started my...
Eight Forums Android App Eight Forums IOS App Follow us on Facebook