Windows 8 and 8.1 Forums


Windows 8.1 Freezes and Blue Screen

  1. #11


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


    I understand that you are eager to fix this, but it's going to take some time.
    Most BSOD's take 2 pages worth of posts to fix - some take 4 or 5 pages

    Clock Watchdog BSOD's are sometimes the most difficult to analyze (and may require the larger memory dumps)

    I don't fix SFC.EXE issues - but you can get assistance over in the Windows Updates forum from an expert in this.

    All the memory dumps are STOP 0x101 (Clock Watchdog). I'll start downloading the large memory dump now, but it may not complete before I have to leave this location (so I'll finish it later on) - We'll see if it contains any additional info for us.

    Notice (below) the drivers dated before Oct2013 - these are the ones that we guess aren't updated for Win8.1 - so I suggest that you check for 8.1 compatible drivers to replace the older one's (just FYI - the 8.1 RTM drivers actually date from 22 Aug 2013 in most cases)

    Next is this, a common BSOD issue:
    AMD OverDrive (AODDriver2.sys) is either a stand-alone application, or a component of the AMD VISION Engine Control Center. This driver is known to cause BSOD's on some Windows systems.
    Please un-install all AMD/ATI video stuff from Control Panel...Programs...Un-install a program
    Then, download (but DO NOT install) a fresh copy of the ATI drivers from http://ati.amd.com (in the upper right corner of the page)
    Use this procedure to install the DRIVER ONLY: ATI video cards - DRIVER ONLY installation procedure - Sysnative Forums

    If the device (AODDriver or AODDriver4.01) remains a problem, open Device Manager, select the "View" item.
    Then select "Show hidden devices" and scroll down to the Non-Plug and Play Drivers section.
    Locate the AODDriver entry, right click on it and select "Un-install". Reboot for changes to take affect.
    Sometimes the driver remains and continues to cause BSOD's. If this is the case for you, post back and we'll give further instructions for safely removing it.

    If overclocking, please stop. Remove the overclock and return the system to stock/standard values while we're troubleshooting. Once the system is stable again, feel free to resume the overclocking.

    Analysis:
    The following is for informational purposes only.
    Code:
    **************************Mon Nov 18 04:53:01.537 2013 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\111813-7343-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.16422.amd64fre.winblue_gdr.131006-1505
    System Uptime:0 days 0:37:08.281
    Probably caused by :Unknown_Image ( ANALYSIS_INCONCLUSIVE )
    BugCheck 101, {18, 0, ffffd000207d0180, 1}
    BugCheck Info: CLOCK_WATCHDOG_TIMEOUT (101)
    Arguments: 
    Arg1: 0000000000000018, Clock interrupt time out interval in nominal clock ticks.
    Arg2: 0000000000000000, 0.
    Arg3: ffffd000207d0180, The PRCB address of the hung processor.
    Arg4: 0000000000000001, 0.
    BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_8_PROC
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: ZEROED_STACK
      BIOS Version                  F12
      BIOS Release Date             09/03/2013
      Manufacturer                  Gigabyte Technology Co., Ltd.
      Product Name                  GA-970A-D3
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Mon Nov 18 04:14:47.303 2013 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\111813-7296-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.16422.amd64fre.winblue_gdr.131006-1505
    System Uptime:0 days 0:43:00.047
    Probably caused by :Unknown_Image ( ANALYSIS_INCONCLUSIVE )
    BugCheck 101, {18, 0, ffffd000208a5180, 3}
    BugCheck Info: CLOCK_WATCHDOG_TIMEOUT (101)
    Arguments: 
    Arg1: 0000000000000018, Clock interrupt time out interval in nominal clock ticks.
    Arg2: 0000000000000000, 0.
    Arg3: ffffd000208a5180, The PRCB address of the hung processor.
    Arg4: 0000000000000003, 0.
    BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_8_PROC
    PROCESS_NAME:  uTorrent.exe
    FAILURE_BUCKET_ID: ZEROED_STACK
      BIOS Version                  F12
      BIOS Release Date             09/03/2013
      Manufacturer                  Gigabyte Technology Co., Ltd.
      Product Name                  GA-970A-D3
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Thu Nov 14 21:10:56.702 2013 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\111513-7500-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.16422.amd64fre.winblue_gdr.131006-1505
    System Uptime:0 days 1:12:42.447
    Probably caused by :Unknown_Image ( ANALYSIS_INCONCLUSIVE )
    BugCheck 101, {18, 0, ffffd00020924180, 4}
    BugCheck Info: CLOCK_WATCHDOG_TIMEOUT (101)
    Arguments: 
    Arg1: 0000000000000018, Clock interrupt time out interval in nominal clock ticks.
    Arg2: 0000000000000000, 0.
    Arg3: ffffd00020924180, The PRCB address of the hung processor.
    Arg4: 0000000000000004, 0.
    BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_8_PROC
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE
      BIOS Version                  F12
      BIOS Release Date             09/03/2013
      Manufacturer                  Gigabyte Technology Co., Ltd.
      Product Name                  GA-970A-D3
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    
    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 Nov 18 04:53:01.537 2013 (UTC - 5:00)**************************
    TuneUpUtilitiesDriver64.sys   Fri May 25 06:28:19 2012 (4FBF5EC3)
    Rt630x64.sys                  Tue Jun 12 09:37:53 2012 (4FD74631)
    RTKVHD64.sys                  Tue Jun 19 04:50:56 2012 (4FE03D70)
    usbfilter.sys                 Tue Jun 19 07:07:40 2012 (4FE05D7C)
    amd_sata.sys                  Mon Jul 23 14:34:48 2012 (500D9948)
    amd_xata.sys                  Mon Jul 23 14:34:52 2012 (500D994C)
    AODDriver2.sys                Wed Nov 21 02:44:04 2012 (50AC8644)
    AtihdWB6.sys                  Sat Jun 22 22:19:48 2013 (51C65B44)
    SamsungRapidDiskFltr.sys      Mon Jul 29 14:55:38 2013 (51F6BAAA)
    SamsungRapidFSFltr.sys        Mon Jul 29 14:55:39 2013 (51F6BAAB)
    xusb22.sys                    Thu Aug 22 07:38:23 2013 (5215F82F)
    atikmpag.sys                  Tue Oct  8 08:27:46 2013 (5253FA42)
    atikmdag.sys                  Tue Oct  8 09:51:03 2013 (52540DC7)
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Thu Nov 14 21:10:56.702 2013 (UTC - 5:00)**************************
    RXBSKNL.SYS                   Sun Apr 15 02:19:06 2012 (4F8A685A)
    dtsoftbus01.sys               Thu Jun 20 03:22:51 2013 (51C2ADCB)
    rxfcv.sys                     Mon Oct 28 13:54:15 2013 (526EA4C7)
    
    http://www.carrona.org/drivers/driver.php?id=TuneUpUtilitiesDriver64.sys
    http://www.carrona.org/drivers/driver.php?id=Rt630x64.sys
    http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys
    http://www.carrona.org/drivers/driver.php?id=usbfilter.sys
    http://www.carrona.org/drivers/driver.php?id=amd_sata.sys
    http://www.carrona.org/drivers/driver.php?id=amd_xata.sys
    http://www.carrona.org/drivers/driver.php?id=AODDriver2.sys
    AtihdWB6.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.
    SamsungRapidDiskFltr.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.
    SamsungRapidFSFltr.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=xusb22.sys
    http://www.carrona.org/drivers/driver.php?id=atikmpag.sys
    http://www.carrona.org/drivers/driver.php?id=atikmdag.sys
    RXBSKNL.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=dtsoftbus01.sys
    rxfcv.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.

      My System SpecsSystem Spec

  2. #12


    Okay now I've unistalled the 13.9 (9/18/2013) amd driver and installed the 13.11 Beta driver (11/7/2013). I've did not updated this and stated this in the comments before because I had the latest stable drivers(for win 8.1) for amd, but maybe it's gona be allright with the latest beta drivers. I hope it fixes the BSOD's. If not I let you know
      My System SpecsSystem Spec

  3. #13


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


    I prefer not to use beta drivers during troubleshooting as they may still have bugs in them.
    But, as you've already installed them, test them out and see if they help.
    The biggest thing here is that AMD Overdrive is uninstalled.
      My System SpecsSystem Spec

  4. #14


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


    I tried to download the large memory dump 4 times today - and each time it failed to extract due to a CRC error.
    I suspect that the file was corrupted during the upload, so please zip up and upload another copy for us to try and download.
      My System SpecsSystem Spec

  5. #15


    Okay, I've uninstalled every amd component exacly as your guide sad and installed only the latest amd video driver in the device manager, but it still installed the AMD catalyst controll center without my permission. You sad that AMD overdrive which is the part of AMD catalyst controll center needs to be uninstalled, but I cannot install the AMD drivers without AMD catalyst controll center no matter how I do it because it still installs it in the background :/

    Also I've repacked the big MEMORY.DMP file and uploaded it to my dropbox. I've tested it so this must be good. Here is my share link for it:
    https://www.dropbox.com/s/mbn7vbgtmnynxho/MEMORY.rar
      My System SpecsSystem Spec

  6. #16


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


    Most of the replacement stuff for video drivers is just cautionary - it's not required.
    The only thing required is that you get rid of AMD OverDrive - that's the component that causes the BSOD's
    EDIT: don't worry about it. If it shows up in subsequent BSOD's, I'll provide instructions on how to rip it out by the roots!

    I'm downloading the large memory dump and will analyze it later on today. If I forget, you may not hear from me until Friday/Saturday (conference party tonight, then I fly out tomorrow at 5am and have to work early on Friday). Reply back in order to "bump" the topic and get a notice in my email.''
      My System SpecsSystem Spec

  7. #17


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


    Got it to work this time. The bad news is that it doesn't offer any significant info.
    Code:
    Microsoft (R) Windows Debugger Version 6.3.9600.16384 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\John\Downloads\MEMORY\MEMORY.DMP]
    Kernel Bitmap Dump File: Only kernel address space is available
    
    
    ************* Symbol Path validation summary **************
    Response                         Time (ms)     Location
    Deferred                                       SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
    Deferred                                       srv*c:\SymcachePublic*http://ctxsym.citrix.com/symbolsad/symbols
    Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols;srv*c:\SymcachePublic*http://ctxsym.citrix.com/symbolsad/symbols
    Executable search path is: 
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 9600.16422.amd64fre.winblue_gdr.131006-1505
    Machine Name:
    Kernel base = 0xfffff800`2620a000 PsLoadedModuleList = 0xfffff800`264ce990
    Debug session time: Thu Nov 14 21:10:56.702 2013 (UTC - 5:00)
    System Uptime: 0 days 1:12:42.447
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ...........................
    Loading User Symbols
    
    Loading unloaded module list
    .............
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 101, {18, 0, ffffd00020924180, 4}
    
    Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
    
    Followup: MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    CLOCK_WATCHDOG_TIMEOUT (101)
    An expected clock interrupt was not received on a secondary processor in an
    MP system within the allocated interval. This indicates that the specified
    processor is hung and not processing interrupts.
    Arguments:
    Arg1: 0000000000000018, Clock interrupt time out interval in nominal clock ticks.
    Arg2: 0000000000000000, 0.
    Arg3: ffffd00020924180, The PRCB address of the hung processor.
    Arg4: 0000000000000004, 0.
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_8_PROC
    
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  d
    
    ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
    
    STACK_TEXT:  
    fffff800`27c4cc58 fffff800`2637bf13 : 00000000`00000101 00000000`00000018 00000000`00000000 ffffd000`20924180 : nt!KeBugCheckEx
    fffff800`27c4cc60 fffff800`2625e81b : 00000000`00000001 fffff800`264f8180 00000000`00028a0e fffff800`264f8180 : nt! ?? ::FNODOBFM::`string'+0x13d83
    fffff800`27c4ccf0 fffff800`2625e48c : 00000000`00000001 fffff800`27c4cd70 fffff800`27c4ce30 fffff800`264a4920 : nt!KiUpdateRunTime+0x57
    fffff800`27c4cd30 fffff800`263dd30c : fffff800`264d6390 fffff800`26264813 fffff800`264f8180 00000000`0000000c : nt!KiUpdateTime+0x63c
    fffff800`27c4cf10 fffff800`26991e5f : 00000000`00000000 fffff800`264f8180 00000000`0000004c 00000000`00000000 : nt!KeClockInterruptNotify+0x5c
    fffff800`27c4cf40 fffff800`262a0343 : fffff800`269de900 fffff800`2630ccd3 fffff800`00000000 00000000`00000000 : hal!HalpTimerClockInterrupt+0x4f
    fffff800`27c4cf70 fffff800`2635912a : fffff800`269de900 fffff800`264f8180 00000000`00000000 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa3
    fffff800`27c4cfb0 fffff800`26359a9b : 00000000`00000000 00000000`342941cd fffff800`264f8180 00000000`00000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xea
    ffffd000`20bfb330 fffff800`26259c2f : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0xfb
    ffffd000`20bfb4c0 fffff800`26259add : 00000000`00000000 00000000`00000000 fffff799`40000000 00000000`00000001 : nt!KxFlushEntireTb+0xb7
    ffffd000`20bfb500 fffff800`26250dfe : fffff799`40000000 00000000`00000001 00000000`00000000 00001f80`000000c9 : nt!KeFlushTb+0x21d
    ffffd000`20bfb620 fffff800`26259730 : 00000e67`9923eb79 fffff800`26254693 00000000`00000000 00000000`00000212 : nt!KeFlushMultipleRangeTb+0x2fe
    ffffd000`20bfb770 fffff800`262550c4 : 00000000`00000000 fffff800`26550080 fffff800`264cdea0 00000000`00000000 : nt!MiFlushTbList+0x2c
    ffffd000`20bfb7a0 fffff800`2626e6bd : fffff800`26550080 00000000`00000000 00000000`00000002 00000000`ffffffff : nt!MiAgeWorkingSet+0xce4
    ffffd000`20bfb9b0 fffff800`2626e2ba : 00000000`00000000 ffffd000`20bfba79 fffff800`26550098 00000000`00000000 : nt!MiTrimOrAgeWorkingSet+0xa1
    ffffd000`20bfb9f0 fffff800`262ca6f6 : 00000000`00000000 ffffe000`002ac880 00000000`00000001 00000000`00000001 : nt!MiProcessWorkingSets+0x1a6
    ffffd000`20bfbae0 fffff800`2633eeda : 00000000`00000008 00000000`00000008 ffffe000`0000000c 00000000`0000000c : nt!MmWorkingSetManager+0x4a
    ffffd000`20bfbb10 fffff800`262972e4 : ffffe000`002ac880 00000000`00000000 00000000`00000080 00000000`00000000 : nt!KeBalanceSetManager+0x122
    ffffd000`20bfbb80 fffff800`2635e2c6 : ffffd000`209a4180 ffffe000`002ac880 ffffd000`209b0340 00000000`00000000 : nt!PspSystemThreadStartup+0x58
    ffffd000`20bfbbe0 00000000`00000000 : ffffd000`20bfc000 ffffd000`20bf5000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
    
    
    STACK_COMMAND:  kb
    
    SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: Unknown_Module
    
    IMAGE_NAME:  Unknown_Image
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    IMAGE_VERSION:  
    
    FAILURE_BUCKET_ID:  CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE
    
    BUCKET_ID:  CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:clock_watchdog_timeout_8_proc_analysis_inconclusive
    
    FAILURE_ID_HASH:  {f60c102e-9b2c-017b-9309-e4af1999e360}
    
    Followup: MachineOwner
    ---------
    
    0: kd> !prcb 0
    PRCB for Processor 0 at fffff800264f8180:
    Current IRQL -- 13
    Threads--  Current ffffe000002ac880 Next 0000000000000000 Idle fffff80026550a80
    Processor Index 0 Number (0, 0) GroupSetMember 1
    Interrupt Count -- 01a5b001
    Times -- Dpc    00001a90 Interrupt 000019fb 
             Kernel 0004167a User      00002c21 
    0: kd> !prcb 4
    PRCB for Processor 4 at ffffd00020924180:
    Current IRQL -- 0
    Threads--  Current ffffe000054a6080 Next 0000000000000000 Idle ffffd00020930340
    Processor Index 4 Number (0, 4) GroupSetMember 10
    Interrupt Count -- 000acb3b
    Times -- Dpc    00000033 Interrupt 0000002d 
             Kernel 00041bbd User      00002445 
    0: kd> !irql 0
    Debugger saved IRQL for processor 0x0 -- 13
    0: kd> !irql 4
    Debugger saved IRQL for processor 0x4 -- 0 (LOW_LEVEL)
    0: kd> kv
    Child-SP          RetAddr           : Args to Child                                                           : Call Site
    fffff800`27c4cc58 fffff800`2637bf13 : 00000000`00000101 00000000`00000018 00000000`00000000 ffffd000`20924180 : nt!KeBugCheckEx
    fffff800`27c4cc60 fffff800`2625e81b : 00000000`00000001 fffff800`264f8180 00000000`00028a0e fffff800`264f8180 : nt! ?? ::FNODOBFM::`string'+0x13d83
    fffff800`27c4ccf0 fffff800`2625e48c : 00000000`00000001 fffff800`27c4cd70 fffff800`27c4ce30 fffff800`264a4920 : nt!KiUpdateRunTime+0x57
    fffff800`27c4cd30 fffff800`263dd30c : fffff800`264d6390 fffff800`26264813 fffff800`264f8180 00000000`0000000c : nt!KiUpdateTime+0x63c
    fffff800`27c4cf10 fffff800`26991e5f : 00000000`00000000 fffff800`264f8180 00000000`0000004c 00000000`00000000 : nt!KeClockInterruptNotify+0x5c
    fffff800`27c4cf40 fffff800`262a0343 : fffff800`269de900 fffff800`2630ccd3 fffff800`00000000 00000000`00000000 : hal!HalpTimerClockInterrupt+0x4f
    fffff800`27c4cf70 fffff800`2635912a : fffff800`269de900 fffff800`264f8180 00000000`00000000 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa3
    fffff800`27c4cfb0 fffff800`26359a9b : 00000000`00000000 00000000`342941cd fffff800`264f8180 00000000`00000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xea (TrapFrame @ fffff800`27c4ce70)
    ffffd000`20bfb330 fffff800`26259c2f : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0xfb (TrapFrame @ ffffd000`20bfb330)
    ffffd000`20bfb4c0 fffff800`26259add : 00000000`00000000 00000000`00000000 fffff799`40000000 00000000`00000001 : nt!KxFlushEntireTb+0xb7
    ffffd000`20bfb500 fffff800`26250dfe : fffff799`40000000 00000000`00000001 00000000`00000000 00001f80`000000c9 : nt!KeFlushTb+0x21d
    ffffd000`20bfb620 fffff800`26259730 : 00000e67`9923eb79 fffff800`26254693 00000000`00000000 00000000`00000212 : nt!KeFlushMultipleRangeTb+0x2fe
    ffffd000`20bfb770 fffff800`262550c4 : 00000000`00000000 fffff800`26550080 fffff800`264cdea0 00000000`00000000 : nt!MiFlushTbList+0x2c
    ffffd000`20bfb7a0 fffff800`2626e6bd : fffff800`26550080 00000000`00000000 00000000`00000002 00000000`ffffffff : nt!MiAgeWorkingSet+0xce4
    ffffd000`20bfb9b0 fffff800`2626e2ba : 00000000`00000000 ffffd000`20bfba79 fffff800`26550098 00000000`00000000 : nt!MiTrimOrAgeWorkingSet+0xa1
    ffffd000`20bfb9f0 fffff800`262ca6f6 : 00000000`00000000 ffffe000`002ac880 00000000`00000001 00000000`00000001 : nt!MiProcessWorkingSets+0x1a6
    ffffd000`20bfbae0 fffff800`2633eeda : 00000000`00000008 00000000`00000008 ffffe000`0000000c 00000000`0000000c : nt!MmWorkingSetManager+0x4a
    ffffd000`20bfbb10 fffff800`262972e4 : ffffe000`002ac880 00000000`00000000 00000000`00000080 00000000`00000000 : nt!KeBalanceSetManager+0x122
    ffffd000`20bfbb80 fffff800`2635e2c6 : ffffd000`209a4180 ffffe000`002ac880 ffffd000`209b0340 00000000`00000000 : nt!PspSystemThreadStartup+0x58
    ffffd000`20bfbbe0 00000000`00000000 : ffffd000`20bfc000 ffffd000`20bf5000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
    0: kd> ~4
    4: kd> kv
    Child-SP          RetAddr           : Args to Child                                                           : Call Site
    00000000`00000000 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0
    4: kd> r if
    if=0
    Let's just wait for further BSOD's and work from there.
      My System SpecsSystem Spec

  8. #18


    Here all of my minidump files if it's help. You can find in there new minidump files because I had some BSOD in the week.
      My System SpecsSystem Spec

  9. #19


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


    AMD Overdrive is still installed.
    If the device (AODDriver or AODDriver4.01) remains a problem, open Device Manager, select the "View" item.
    Then select "Show hidden devices" and scroll down to the Non-Plug and Play Drivers section.
    Locate the AODDriver entry, right click on it and select "Un-install". Reboot for changes to take affect.
    Sometimes the driver remains and continues to cause BSOD's. If this is the case for you, post back and we'll give further instructions for safely removing it.

    If overclocking, please stop. Remove the overclock and return the system to stock/standard values while we're troubleshooting. Once the system is stable again, feel free to resume the overclocking.[/QUOTE]

    Safely removing the AODDriver2.sys driver (if needed):
    1) Create a Restore Point using System Restore
    2) Create a Repair disc:
    Win7 - Go to Start...All Programs...Maintenance...Create a System Repair Disc
    Win8 - Press "WIN" and "R" to open the Run dialog...type "RECDISC" (without the quotes) and press ENTER
    3) Test the System Repair disc to make sure that you can get to the System Restore entry when you boot from the disk (you may also want to try actually using System Restore to make sure that it works)
    4) Download this free program (Autoruns for Windows) and use it to disable any instances of AODDriver2.sys that are starting (or any other AMD Overdrive entries) (DO NOT DELETE - only disable by removing the checkmark in the left hand column)
    5) Check in Device Manager (to include showing hidden devices from the View menu item) and ensure that any instances of AODDriver2.sys (or any other AMD Overdrive entries) are "Uninstalled" (DO NOT DISABLE THESE).
    6) Check in the Services applet (services.msc) to be sure any instances of AODDriver2.sys or any other AMD Overdrive entries are disabled.
    7) Go to C:\Windows\System32\drivers and rename the AODDriver2.sys driver to AODDriver2.BAD (search the hard drive for it if it's not in C:\Windows\System32\drivers).


    In the event that the system doesn't boot:

    1) Boot from the System Repair disc and use the Command Prompt option to rename hssdrv6.BAD to hssdrv6.sys
    Code:
    ren C:\Windows\System32\drivers\AODDriver2.BAD C:\Windows\System32\drivers\AODDriver2.sys
    2) Boot from the System Repair disc and use the System Restore option to restore the system to a point before the changes were made.

    Good luck!
    Please note the drivers below that date from before the release of Windows 8.1 (26 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.



    Analysis:
    The following is for informational purposes only.
    Code:
    **************************Tue Nov 19 18:12:09.067 2013 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\112013-8156-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.16422.amd64fre.winblue_gdr.131006-1505
    System Uptime:0 days 0:50:12.812
    Probably caused by :Unknown_Image ( ANALYSIS_INCONCLUSIVE )
    BugCheck 101, {18, 0, ffffd00020924180, 4}
    BugCheck Info: CLOCK_WATCHDOG_TIMEOUT (101)
    Arguments: 
    Arg1: 0000000000000018, Clock interrupt time out interval in nominal clock ticks.
    Arg2: 0000000000000000, 0.
    Arg3: ffffd00020924180, The PRCB address of the hung processor.
    Arg4: 0000000000000004, 0.
    BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_8_PROC
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: ZEROED_STACK
      BIOS Version                  F12
      BIOS Release Date             09/03/2013
      Manufacturer                  Gigabyte Technology Co., Ltd.
      Product Name                  GA-970A-D3
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Tue Nov 19 12:34:34.552 2013 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\111913-7359-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.16422.amd64fre.winblue_gdr.131006-1505
    System Uptime:0 days 0:27:35.296
    Probably caused by :Unknown_Image ( ANALYSIS_INCONCLUSIVE )
    BugCheck 101, {18, 0, ffffd000207d0180, 1}
    BugCheck Info: CLOCK_WATCHDOG_TIMEOUT (101)
    Arguments: 
    Arg1: 0000000000000018, Clock interrupt time out interval in nominal clock ticks.
    Arg2: 0000000000000000, 0.
    Arg3: ffffd000207d0180, The PRCB address of the hung processor.
    Arg4: 0000000000000001, 0.
    BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_8_PROC
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: ZEROED_STACK
      BIOS Version                  F12
      BIOS Release Date             09/03/2013
      Manufacturer                  Gigabyte Technology Co., Ltd.
      Product Name                  GA-970A-D3
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Tue Nov 19 05:32:48.810 2013 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\111913-7765-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.16422.amd64fre.winblue_gdr.131006-1505
    System Uptime:0 days 1:16:52.555
    Probably caused by :Unknown_Image ( ANALYSIS_INCONCLUSIVE )
    BugCheck 101, {18, 0, ffffd00020a61180, 7}
    BugCheck Info: CLOCK_WATCHDOG_TIMEOUT (101)
    Arguments: 
    Arg1: 0000000000000018, Clock interrupt time out interval in nominal clock ticks.
    Arg2: 0000000000000000, 0.
    Arg3: ffffd00020a61180, The PRCB address of the hung processor.
    Arg4: 0000000000000007, 0.
    BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_8_PROC
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: ZEROED_STACK
      BIOS Version                  F12
      BIOS Release Date             09/03/2013
      Manufacturer                  Gigabyte Technology Co., Ltd.
      Product Name                  GA-970A-D3
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Mon Nov 18 17:07:39.693 2013 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\111813-10406-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.16422.amd64fre.winblue_gdr.131006-1505
    System Uptime:0 days 3:14:18.438
    Probably caused by :Unknown_Image ( ANALYSIS_INCONCLUSIVE )
    BugCheck 101, {18, 0, ffffd00020924180, 4}
    BugCheck Info: CLOCK_WATCHDOG_TIMEOUT (101)
    Arguments: 
    Arg1: 0000000000000018, Clock interrupt time out interval in nominal clock ticks.
    Arg2: 0000000000000000, 0.
    Arg3: ffffd00020924180, The PRCB address of the hung processor.
    Arg4: 0000000000000004, 0.
    BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_8_PROC
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: ZEROED_STACK
      BIOS Version                  F12
      BIOS Release Date             09/03/2013
      Manufacturer                  Gigabyte Technology Co., Ltd.
      Product Name                  GA-970A-D3
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    
    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:
    **************************Tue Nov 19 18:12:09.067 2013 (UTC - 5:00)**************************
    TuneUpUtilitiesDriver64.sys   Fri May 25 06:28:19 2012 (4FBF5EC3)
    Rt630x64.sys                  Tue Jun 12 09:37:53 2012 (4FD74631)
    RTKVHD64.sys                  Tue Jun 19 04:50:56 2012 (4FE03D70)
    amd_sata.sys                  Mon Jul 23 14:34:48 2012 (500D9948)
    amd_xata.sys                  Mon Jul 23 14:34:52 2012 (500D994C)
    AODDriver2.sys                Wed Nov 21 02:44:04 2012 (50AC8644)
    AtihdWB6.sys                  Sat Jun 22 22:19:48 2013 (51C65B44)
    SamsungRapidDiskFltr.sys      Mon Jul 29 14:55:38 2013 (51F6BAAA)
    SamsungRapidFSFltr.sys        Mon Jul 29 14:55:39 2013 (51F6BAAB)
    xusb22.sys                    Thu Aug 22 07:38:23 2013 (5215F82F)
    atikmpag.sys                  Thu Nov  7 10:49:55 2013 (527BB6A3)
    atikmdag.sys                  Thu Nov  7 11:47:15 2013 (527BC413)
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Tue Nov 19 12:34:34.552 2013 (UTC - 5:00)**************************
    usbfilter.sys                 Tue Jun 19 07:07:40 2012 (4FE05D7C)
    AODDriver2.sys                Wed Sep 11 23:36:40 2013 (523136C8)
    AtihdWB6.sys                  Tue Sep 24 20:24:38 2013 (52422D46)
    AMDACPKSL.SYS                 Tue Sep 24 20:24:41 2013 (52422D49)
    
    http://www.carrona.org/drivers/driver.php?id=TuneUpUtilitiesDriver64.sys
    http://www.carrona.org/drivers/driver.php?id=Rt630x64.sys
    http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys
    http://www.carrona.org/drivers/driver.php?id=amd_sata.sys
    http://www.carrona.org/drivers/driver.php?id=amd_xata.sys
    http://www.carrona.org/drivers/driver.php?id=AODDriver2.sys
    AtihdWB6.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.
    SamsungRapidDiskFltr.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.
    SamsungRapidFSFltr.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=xusb22.sys
    http://www.carrona.org/drivers/driver.php?id=atikmpag.sys
    http://www.carrona.org/drivers/driver.php?id=atikmdag.sys
    http://www.carrona.org/drivers/driver.php?id=usbfilter.sys
    http://www.carrona.org/drivers/driver.php?id=AODDriver2.sys
    AtihdWB6.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.
    AMDACPKSL.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.
      My System SpecsSystem Spec

  10. #20


    I did not find any AMD Overdrive drivers in the deice manager(I checked to show hidden drivers). Also I dont see any independent AMD Overdrive software. As far as I know AMD Overdrive is the part of AMD catalyst controll center, It's just a little tab uder the performance menu in AMD catalyst controll center. I've also never did any overclocking in my life because I never needed it, so I never used AMD Overdrive on sytem.


    Also I had the exact same computer setup with windows 8.1 from the day it has came out and never experienced any BSOD's. All of the BSOD's started rifght after i buyed my new samsung evo ssd and installed windows 8.1 on it.
    Attachment 32082
      My System SpecsSystem Spec

Page 2 of 3 FirstFirst 123 LastLast
Windows 8.1 Freezes and Blue Screen
Related Threads
My laptop froze; had to turn off. When it came back up it gets as far as the login screen and then freezes. Cursor will move but will not let me type anything. I reloaded the OS; it came up fine. Left it for awhile, came back to black screen. Shut off and it does the same thing as...
windows update freezes at 64% on blue screen. in Windows Updates & Activation
My windows 8.1 downloaded some automatic updates, and while installing, froze at 64%. (going on two hours). I tried turning off and turning on the wifi, as someone suggested. nothing. Any suggestions? This is a Dell Inspiron.
I've having an issue that I think some ppl had, windows 8 crashing going to blue screen of death or blank black screen and then it restarts by itself, also I have noticed that it says repairing disk in D:/ I have one SSD 120gb in the C:/ which it host the operating system and some minnor...
Windows 8.1 Blue Screen in Performance & Maintenance
:party: Blue screen never goes away... Attached is my event log for the events around the last blue screen. Any help is appreciated. There are a lot of CFRD warnings, whatever that means!
Hi, recently i installed windows 8.1 pro x64 on my laptop which is acer 5755g.but i've a very strange problem with that.when i want to go afk before leaving laptop i press windows + l key and go to lock screen everything is ok now but when i'm coming back in few hours laptop is freezes and must...
Windows 8 keeps getting 0x00000109 blue screen in BSOD Crashes and Debugging
Hi, I have had a problem lately since installing windows 8 my machine gives me random blue screens, rarely I get watchdog blue screen and lately I have been getting 0x00000109 almost every day, even when the computer is sleeping. The wired thing is when I use the machine play a game etc the...
I get a blue screen error of "driverirql_not_less_equal" when my laptop monitor dims. Specs: OS: Windows 8 Professional (64 bit) Intel i7 2640M 8 Gb Ram 1T HD The attached screen capture is the location of my error.
Eight Forums Android App Eight Forums IOS App Follow us on Facebook