Windows 8 and 8.1 Forums


Windows 8.1 Freezes and Blue Screen

  1. #21


    I've also noticed that when I play games (for example:Elder Scrolls Skyrim, Rome 2 Total War, Crysis 3) I dont get any BSOD's at all . I only experience the when I download something with Opera browser and utorrent, when I unpack archives(for example: rar, zip) or when my computer doesnt do anything.

      My System SpecsSystem Spec

  2. #22


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


    If the only thing that you changed was your SSD - then you've gotta look at the SSD.

    If you install Windows Updates, the system changes. If you have incompatible software installed, it may work at first - but when it encounters the incompatibility (such as a Windows Update changing something) it may then cause errors.

    You also have 3rd party software installed - and it dates from before Win8.1 came out. If it is incompatible and it encounters changes in the system related to that - then it won't work there either.

    2 choices here:
    - start uninstalling things to see if you can identify the problem.
    - reinstall Windows "clean" (without extra programs) to see if the system is stable then.

    Start by uninstalling TuneUp Utilities, Samsung Rapid Disk programs, the USB XBox controller software (and physically remove the device from your system), and follow the instructions to safely remove the AODDriver2.sys driver

    Or, if you want to start with a "clean" install - please follow the instructions here: Canned Speeches - Clean Install
      My System SpecsSystem Spec

  3. #23


    -I have uninstalled daemon tools, TuneUp Utilities, Samsung Rapid Disk programs
    -Uplugged the xbox 360 controller and unistalled
    USB XBox controller driver
    -removed the
    AODDriver2.sys driver exacly as your guide sad
    -unplugged all system fans and all non os hdds
    but I still getting BSOD's with clock_watchdog_timeout
    It's like I'm being cursed :/

    Here are my newest minidump and memory.dmp files:
    http://www.dropbox.com/s/mbn7vbgtmnynxho/MEMORY.rar
      My System SpecsSystem Spec

  4. #24


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


    There are 3 possible problems that cause BSOD's:
    - 3rd party drivers (~90% of BSOD's)
    - hardware(<10% of BSOD's)
    - Windows drivers(<1% of BSOD's - if system is fully up to date w/Windows Updates)

    Primarily classed within the "hardware" section are these types of errors:
    - borked (broken) hardware (several different procedures used to isolate the problem device)
    - BIOS issues (check for updates at the motherboard manufacturer's website)
    - overclocking/overheating - You'll know if you're overclocking or not. If uncertain we can suggest things to check.
    - compatibility issues
    - low-level driver problems
    - or even malware (scanned for when we ask for hardware diagnostics from Initial Hardware Diagnostics or Hardware Diagnostics ).
    These typically have either hardware-type error codes or error code patterns - so we look for those when analyzing the memory dumps.

    The Clock Watchdog errors can be of this type. We've seen a lot of them with Win8.1 installs - and I blame most of them on incompatibilities. I'm learning more and more about analyzing the large memory dumps for these types of errors - but am still a novice when it comes to them.

    The presence of hal.dll in the stack is a "hint" that there may be compatibility issues. Hal.dll controls the communication between the hardware and Windows - so incompatibilities may cause it to show up in the stack (but that's not the only reason). In reaching conclusions about BSOD's we rely heavily on these hints as they are often the only thing that we have to go on to try to fix a system.

    Finally, we analyze BSOD's using the percentages. We work on the most likely stuff and move down to the less likely as things progress. So we'll rule out all the 3rd party drivers first. We still have to ensure that the drivers dated before 26 Oct 2013 are indeed compatible with Win8.1. Once that is done, then we'll move on to hardware diagnostics and Windows reinstalls.

    I'm downloading the large memory dump now and will post back when it's done.....
      My System SpecsSystem Spec

  5. #25


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


    Finally done! It looks to me like it's the network driver - Rt630x64.sys. I've seen lots of mentions of it and ndis.sys (a Windows networking driver) in the memory dump.

    The driver dates from 12 Jun 2012 - so it may not be compatible w/Win8.1
    Try the driver from here: Realtek
    Pick the one that says "Win8 and Win8.1 Auto Installation Program (SID:1624014)" The driver will be dated from 15 Aug 2013

    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 = 0xfffff803`f1e18000 PsLoadedModuleList = 0xfffff803`f20dc990
    Debug session time: Mon Nov 25 17:43:10.614 2013 (UTC - 5:00)
    System Uptime: 0 days 3:51:35.359
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ...................
    Loading User Symbols
    
    Loading unloaded module list
    ..........
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 101, {18, 0, ffffd000201d8180, 1}
    
    *** ERROR: Module load completed but symbols could not be loaded for Rt630x64.sys
    Page 219006 not present in the dump file. Type ".hh dbgerr004" for details
    Page 21935e not present in the dump file. Type ".hh dbgerr004" for details
    Page 219800 not present in the dump file. Type ".hh dbgerr004" for details
    Page 219800 not present in the dump file. Type ".hh dbgerr004" for details
    Page 219800 not present in the dump file. Type ".hh dbgerr004" for details
    Page 219800 not present in the dump file. Type ".hh dbgerr004" for details
    Page 219800 not present in the dump file. Type ".hh dbgerr004" for details
    Page 219800 not present in the dump file. Type ".hh dbgerr004" for details
    Page 219800 not present in the dump file. Type ".hh dbgerr004" for details
    Page 219800 not present in the dump file. Type ".hh dbgerr004" for details
    Page 219800 not present in the dump file. Type ".hh dbgerr004" for details
    Page 219800 not present in the dump file. Type ".hh dbgerr004" for details
    Page 219800 not present in the dump file. Type ".hh dbgerr004" for details
    Page 219800 not present in the dump file. Type ".hh dbgerr004" for details
    Page 219800 not present in the dump file. Type ".hh dbgerr004" for details
    Page 219800 not present in the dump file. Type ".hh dbgerr004" for details
    Page 219800 not present in the dump file. Type ".hh dbgerr004" for details
    Page 219800 not present in the dump file. Type ".hh dbgerr004" for details
    Page 219800 not present in the dump file. Type ".hh dbgerr004" for details
    Page 219800 not present in the dump file. Type ".hh dbgerr004" for details
    Page 219800 not present in the dump file. Type ".hh dbgerr004" for details
    Page 219800 not present in the dump file. Type ".hh dbgerr004" for details
    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: ffffd000201d8180, The PRCB address of the hung processor.
    Arg4: 0000000000000001, 0.
    
    Debugging Details:
    ------------------
    
    Page 219006 not present in the dump file. Type ".hh dbgerr004" for details
    Page 21935e not present in the dump file. Type ".hh dbgerr004" for details
    Page 219800 not present in the dump file. Type ".hh dbgerr004" for details
    Page 219800 not present in the dump file. Type ".hh dbgerr004" for details
    Page 219800 not present in the dump file. Type ".hh dbgerr004" for details
    Page 219800 not present in the dump file. Type ".hh dbgerr004" for details
    Page 219800 not present in the dump file. Type ".hh dbgerr004" for details
    Page 219800 not present in the dump file. Type ".hh dbgerr004" for details
    Page 219800 not present in the dump file. Type ".hh dbgerr004" for details
    Page 219800 not present in the dump file. Type ".hh dbgerr004" for details
    Page 219800 not present in the dump file. Type ".hh dbgerr004" for details
    Page 219800 not present in the dump file. Type ".hh dbgerr004" for details
    Page 219800 not present in the dump file. Type ".hh dbgerr004" for details
    Page 219800 not present in the dump file. Type ".hh dbgerr004" for details
    Page 219800 not present in the dump file. Type ".hh dbgerr004" for details
    Page 219800 not present in the dump file. Type ".hh dbgerr004" for details
    Page 219800 not present in the dump file. Type ".hh dbgerr004" for details
    Page 219800 not present in the dump file. Type ".hh dbgerr004" for details
    Page 219800 not present in the dump file. Type ".hh dbgerr004" for details
    Page 219800 not present in the dump file. Type ".hh dbgerr004" for details
    Page 219800 not present in the dump file. Type ".hh dbgerr004" for details
    Page 219800 not present in the dump file. Type ".hh dbgerr004" for 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:  
    fffff803`f37a5c58 fffff803`f1f89f13 : 00000000`00000101 00000000`00000018 00000000`00000000 ffffd000`201d8180 : nt!KeBugCheckEx
    fffff803`f37a5c60 fffff803`f1e6c81b : 00000000`00000001 fffff803`f2106180 00000000`00081691 fffff803`f2106180 : nt! ?? ::FNODOBFM::`string'+0x13d83
    fffff803`f37a5cf0 fffff803`f1e6c48c : 00000000`00000014 fffff803`f37a5d70 fffff803`f37a5e30 fffff803`f20b2920 : nt!KiUpdateRunTime+0x57
    fffff803`f37a5d30 fffff803`f1feb30c : fffff803`f20e43f0 fffff803`f1e72813 fffff803`f2106180 00000000`0000000c : nt!KiUpdateTime+0x63c
    fffff803`f37a5f10 fffff803`f259fe5f : ffffd000`00400a02 00000000`00000001 fffff800`00a48ba0 00000000`00008101 : nt!KeClockInterruptNotify+0x5c
    fffff803`f37a5f40 fffff803`f1eae343 : fffff803`f25ec900 00000000`00000008 fffff803`f37a5f50 00000000`00000010 : hal!HalpTimerClockInterrupt+0x4f
    fffff803`f37a5f70 fffff803`f1f6712a : fffff803`f25ec900 fffff803`f2106180 00000000`00000002 fffff803`f379e938 : nt!KiCallInterruptServiceRoutine+0xa3
    fffff803`f37a5fb0 fffff803`f1f67a9b : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xea
    fffff803`f379e5d0 fffff803`f1e5edbe : ffffe000`01360240 fffff800`00cb5253 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0xfb
    fffff803`f379e760 fffff803`f1e67730 : 00000000`00000000 00000000`00000000 00000000`00000000 ffffd000`29ca6000 : nt!KeFlushMultipleRangeTb+0x2be
    fffff803`f379e8b0 fffff803`f1eecbda : fffff6e8`0014e530 00000000`00000001 00000000`00000000 00000000`00000001 : nt!MiFlushTbList+0x2c
    fffff803`f379e8e0 fffff803`f1eeca96 : 00000000`00000000 fffff803`f20b7100 fffff803`f2106180 00000001`38975863 : nt!MiRemoveIoSpaceMap+0xea
    fffff803`f379ea30 fffff800`01bbb597 : 00000000`00100007 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MmUnmapIoSpace+0x6e
    fffff803`f379ea60 fffff800`01bbb603 : 00000000`00000000 00000000`00000000 ffffe000`0259e600 00000000`00000000 : Rt630x64+0x7e597
    fffff803`f379ea90 fffff800`01bbb989 : 00000000`00000000 ffffe000`0206cc40 fffff803`f2106180 00000000`00000000 : Rt630x64+0x7e603
    fffff803`f379ead0 fffff800`01bbd07b : ffffe000`0259e000 fffff803`f379ec00 ffffe000`025a1bd8 00000000`00020000 : Rt630x64+0x7e989
    fffff803`f379eb10 fffff800`01b5b612 : ffffe000`0259e000 5b942592`b4de076f ffffe000`0206cc40 00000000`00000002 : Rt630x64+0x8007b
    fffff803`f379eb40 fffff800`00a4b802 : ffffe000`024ac198 fffff800`00a48700 fffff803`f379ec01 ffffe000`024df1a0 : Rt630x64+0x1e612
    fffff803`f379ebb0 fffff803`f1ec5f64 : fffff803`f379ee70 fffff803`f379ec89 ffffe000`029635f0 00000000`00000000 : ndis!ndisMTimerObjectDpc+0xc6
    fffff803`f379ec10 fffff803`f1ec6478 : ffffd000`20f58830 fffff803`f1e18000 fffff803`f20bdcc0 fffff803`f2109640 : nt!KiProcessExpiredTimerList+0x1d8
    fffff803`f379ecf0 fffff803`f1f22478 : fffff803`f2106180 00000000`00da7a64 fffff803`0008150e fffff803`00081526 : nt!KiExpireTimerTable+0x218
    fffff803`f379ed90 fffff803`f1e72abc : ffffe000`0144b080 fffff803`f2106180 00000000`00000008 0000001f`9263e4bd : nt!KiTimerExpiration+0x148
    fffff803`f379ee40 fffff803`f1f68dd5 : 00000000`00000000 fffff803`f2106180 ffffd000`20b519d0 00000000`00000000 : nt!KiRetireDpcList+0x19c
    fffff803`f379efb0 fffff803`f1f68bd9 : ffffe000`018d0030 fffff800`01b576ca ffffe000`024df1a0 fffff803`f1f6693d : nt!KxRetireDpcList+0x5
    ffffd000`20b51920 fffff803`f1f6acfa : 00000000`00000000 ffffd000`20b51a28 00000000`00000002 00000000`00000001 : nt!KiDispatchInterruptContinue
    ffffd000`20b51950 fffff803`f1e8cc1f : fffff800`00a57625 ffffe000`0206a3a0 ffffe000`0206a380 ffffe000`0206b800 : nt!KiDpcInterrupt+0xca
    ffffd000`20b51ae8 fffff800`00a57625 : ffffe000`0206a3a0 ffffe000`0206a380 ffffe000`0206b800 ffffe000`02962538 : nt!KzLowerIrql+0x7
    ffffd000`20b51af0 fffff803`f1ea52e4 : fffff803`f215ea80 ffffe000`0206b880 00000000`00000080 ffffe000`0206b880 : ndis!ndisReceiveWorkerThread+0x169
    ffffd000`20b51b80 fffff803`f1f6c2c6 : fffff803`f2106180 ffffe000`0206b880 fffff803`f215ea80 00020000`00000002 : nt!PspSystemThreadStartup+0x58
    ffffd000`20b51be0 00000000`00000000 : ffffd000`20b52000 ffffd000`20b4b000 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> lmvm Unknown_Module
    start             end                 module name
    0: kd> !prcb 0
    PRCB for Processor 0 at fffff803f2106180:
    Current IRQL -- 13
    Threads--  Current ffffe0000206b880 Next ffffe000002a9880 Idle fffff803f215ea80
    Processor Index 0 Number (0, 0) GroupSetMember 1
    Interrupt Count -- 04c77511
    Times -- Dpc    00004a09 Interrupt 00004297 
             Kernel 000bdb29 User      0001b6ad 
    0: kd> !prcb 1
    PRCB for Processor 1 at ffffd000201d8180:
    Current IRQL -- 0
    Threads--  Current ffffe000048c4080 Next ffffe00004668480 Idle ffffd000201e4340
    Processor Index 1 Number (0, 1) GroupSetMember 2
    Interrupt Count -- 0117914f
    Times -- Dpc    00002128 Interrupt 00000239 
             Kernel 000c5abe User      00013478 
    0: kd> kv
    Child-SP          RetAddr           : Args to Child                                                           : Call Site
    fffff803`f37a5c58 fffff803`f1f89f13 : 00000000`00000101 00000000`00000018 00000000`00000000 ffffd000`201d8180 : nt!KeBugCheckEx
    fffff803`f37a5c60 fffff803`f1e6c81b : 00000000`00000001 fffff803`f2106180 00000000`00081691 fffff803`f2106180 : nt! ?? ::FNODOBFM::`string'+0x13d83
    fffff803`f37a5cf0 fffff803`f1e6c48c : 00000000`00000014 fffff803`f37a5d70 fffff803`f37a5e30 fffff803`f20b2920 : nt!KiUpdateRunTime+0x57
    fffff803`f37a5d30 fffff803`f1feb30c : fffff803`f20e43f0 fffff803`f1e72813 fffff803`f2106180 00000000`0000000c : nt!KiUpdateTime+0x63c
    fffff803`f37a5f10 fffff803`f259fe5f : ffffd000`00400a02 00000000`00000001 fffff800`00a48ba0 00000000`00008101 : nt!KeClockInterruptNotify+0x5c
    fffff803`f37a5f40 fffff803`f1eae343 : fffff803`f25ec900 00000000`00000008 fffff803`f37a5f50 00000000`00000010 : hal!HalpTimerClockInterrupt+0x4f
    fffff803`f37a5f70 fffff803`f1f6712a : fffff803`f25ec900 fffff803`f2106180 00000000`00000002 fffff803`f379e938 : nt!KiCallInterruptServiceRoutine+0xa3
    fffff803`f37a5fb0 fffff803`f1f67a9b : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xea (TrapFrame @ fffff803`f37a5e70)
    fffff803`f379e5d0 fffff803`f1e5edbe : ffffe000`01360240 fffff800`00cb5253 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0xfb (TrapFrame @ fffff803`f379e5d0)
    fffff803`f379e760 fffff803`f1e67730 : 00000000`00000000 00000000`00000000 00000000`00000000 ffffd000`29ca6000 : nt!KeFlushMultipleRangeTb+0x2be
    fffff803`f379e8b0 fffff803`f1eecbda : fffff6e8`0014e530 00000000`00000001 00000000`00000000 00000000`00000001 : nt!MiFlushTbList+0x2c
    fffff803`f379e8e0 fffff803`f1eeca96 : 00000000`00000000 fffff803`f20b7100 fffff803`f2106180 00000001`38975863 : nt!MiRemoveIoSpaceMap+0xea
    fffff803`f379ea30 fffff800`01bbb597 : 00000000`00100007 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MmUnmapIoSpace+0x6e
    fffff803`f379ea60 fffff800`01bbb603 : 00000000`00000000 00000000`00000000 ffffe000`0259e600 00000000`00000000 : Rt630x64+0x7e597
    fffff803`f379ea90 fffff800`01bbb989 : 00000000`00000000 ffffe000`0206cc40 fffff803`f2106180 00000000`00000000 : Rt630x64+0x7e603
    fffff803`f379ead0 fffff800`01bbd07b : ffffe000`0259e000 fffff803`f379ec00 ffffe000`025a1bd8 00000000`00020000 : Rt630x64+0x7e989
    fffff803`f379eb10 fffff800`01b5b612 : ffffe000`0259e000 5b942592`b4de076f ffffe000`0206cc40 00000000`00000002 : Rt630x64+0x8007b
    fffff803`f379eb40 fffff800`00a4b802 : ffffe000`024ac198 fffff800`00a48700 fffff803`f379ec01 ffffe000`024df1a0 : Rt630x64+0x1e612
    fffff803`f379ebb0 fffff803`f1ec5f64 : fffff803`f379ee70 fffff803`f379ec89 ffffe000`029635f0 00000000`00000000 : ndis!ndisMTimerObjectDpc+0xc6
    fffff803`f379ec10 fffff803`f1ec6478 : ffffd000`20f58830 fffff803`f1e18000 fffff803`f20bdcc0 fffff803`f2109640 : nt!KiProcessExpiredTimerList+0x1d8
    fffff803`f379ecf0 fffff803`f1f22478 : fffff803`f2106180 00000000`00da7a64 fffff803`0008150e fffff803`00081526 : nt!KiExpireTimerTable+0x218
    fffff803`f379ed90 fffff803`f1e72abc : ffffe000`0144b080 fffff803`f2106180 00000000`00000008 0000001f`9263e4bd : nt!KiTimerExpiration+0x148
    fffff803`f379ee40 fffff803`f1f68dd5 : 00000000`00000000 fffff803`f2106180 ffffd000`20b519d0 00000000`00000000 : nt!KiRetireDpcList+0x19c
    fffff803`f379efb0 fffff803`f1f68bd9 : ffffe000`018d0030 fffff800`01b576ca ffffe000`024df1a0 fffff803`f1f6693d : nt!KxRetireDpcList+0x5 (TrapFrame @ fffff803`f379ee70)
    ffffd000`20b51920 fffff803`f1f6acfa : 00000000`00000000 ffffd000`20b51a28 00000000`00000002 00000000`00000001 : nt!KiDispatchInterruptContinue
    ffffd000`20b51950 fffff803`f1e8cc1f : fffff800`00a57625 ffffe000`0206a3a0 ffffe000`0206a380 ffffe000`0206b800 : nt!KiDpcInterrupt+0xca (TrapFrame @ ffffd000`20b51950)
    ffffd000`20b51ae8 fffff800`00a57625 : ffffe000`0206a3a0 ffffe000`0206a380 ffffe000`0206b800 ffffe000`02962538 : nt!KzLowerIrql+0x7
    ffffd000`20b51af0 fffff803`f1ea52e4 : fffff803`f215ea80 ffffe000`0206b880 00000000`00000080 ffffe000`0206b880 : ndis!ndisReceiveWorkerThread+0x169
    ffffd000`20b51b80 fffff803`f1f6c2c6 : fffff803`f2106180 ffffe000`0206b880 fffff803`f215ea80 00020000`00000002 : nt!PspSystemThreadStartup+0x58
    ffffd000`20b51be0 00000000`00000000 : ffffd000`20b52000 ffffd000`20b4b000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
    0: kd> ~1
    1: kd> kv
    Child-SP          RetAddr           : Args to Child                                                           : Call Site
    00000000`00000000 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0
    1: kd> r if
    if=0
    1: kd> .trap fffff803`f37a5e70
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
    rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff803f1f67a9b rsp=fffff803f379e5d0 rbp=fffff803f379e938
     r8=0000000000000000  r9=0000000000000000 r10=0000002800000002
    r11=ffff8ec6c03f2cd8 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up di pl nz na pe nc
    nt!KiInterruptDispatchNoLockNoEtw+0xfb:
    fffff803`f1f67a9b 488b642410      mov     rsp,qword ptr [rsp+10h] ss:fffff803`f379e5e0=0000000000000000
    1: kd> knL
      *** Stack trace for last set context - .thread/.cxr resets it
     # Child-SP          RetAddr           Call Site
    00 fffff803`f379e5d0 00000000`00000004 nt!KiInterruptDispatchNoLockNoEtw+0xfb
    01 fffff803`f20b7100 00000000`000000fc 0x4
    02 fffff803`f20b7108 00000000`00000011 0xfc
    03 fffff803`f20b7110 00000000`00000000 0x11
    1: kd> .trap fffff803`f379e5d0
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000001 rbx=0000000000000000 rcx=ffffd00029ca6000
    rdx=fffff803f379e940 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff803f1e5edbe rsp=fffff803f379e760 rbp=0000000000000000
     r8=0000000000000000  r9=0000000000001000 r10=fffff803f379e940
    r11=fffff803f379e450 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl nz na pe nc
    nt!KeFlushMultipleRangeTb+0x2be:
    fffff803`f1e5edbe f390            pause
    1: kd> knL
      *** Stack trace for last set context - .thread/.cxr resets it
     # Child-SP          RetAddr           Call Site
    00 fffff803`f379e760 fffff803`f1e67730 nt!KeFlushMultipleRangeTb+0x2be
    01 fffff803`f379e8b0 fffff803`f1eecbda nt!MiFlushTbList+0x2c
    02 fffff803`f379e8e0 fffff803`f1eeca96 nt!MiRemoveIoSpaceMap+0xea
    03 fffff803`f379ea30 fffff800`01bbb597 nt!MmUnmapIoSpace+0x6e
    04 fffff803`f379ea60 fffff800`01bbb603 Rt630x64+0x7e597
    05 fffff803`f379ea90 fffff800`01bbb989 Rt630x64+0x7e603
    06 fffff803`f379ead0 fffff800`01bbd07b Rt630x64+0x7e989
    07 fffff803`f379eb10 fffff800`01b5b612 Rt630x64+0x8007b
    08 fffff803`f379eb40 fffff800`00a4b802 Rt630x64+0x1e612
    09 fffff803`f379ebb0 fffff803`f1ec5f64 ndis!ndisMTimerObjectDpc+0xc6
    0a fffff803`f379ec10 fffff803`f1ec6478 nt!KiProcessExpiredTimerList+0x1d8
    0b fffff803`f379ecf0 fffff803`f1f22478 nt!KiExpireTimerTable+0x218
    0c fffff803`f379ed90 fffff803`f1e72abc nt!KiTimerExpiration+0x148
    0d fffff803`f379ee40 fffff803`f1f68dd5 nt!KiRetireDpcList+0x19c
    0e fffff803`f379efb0 fffff803`f1f68bd9 nt!KxRetireDpcList+0x5
    0f ffffd000`20b51920 fffff803`f1f6acfa nt!KiDispatchInterruptContinue
    10 ffffd000`20b51950 fffff803`f1e8cc1f nt!KiDpcInterrupt+0xca
    11 ffffd000`20b51ae8 fffff800`00a57625 nt!KzLowerIrql+0x7
    12 ffffd000`20b51af0 fffff803`f1ea52e4 ndis!ndisReceiveWorkerThread+0x169
    13 ffffd000`20b51b80 fffff803`f1f6c2c6 nt!PspSystemThreadStartup+0x58
    14 ffffd000`20b51be0 00000000`00000000 nt!KiStartSystemThread+0x16
    1: kd> .trap fffff803`f379ee70
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=fffff80001a07690 rbx=0000000000000000 rcx=000d8e1e000d8e1e
    rdx=fffff80001a07690 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff803f1f68bd9 rsp=ffffd00020b51920 rbp=0000000000000000
     r8=000d8b1d000d8b1d  r9=fffff80000a48550 r10=000d81f7000d81f7
    r11=fffff80001a07690 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up di pl nz na pe nc
    nt!KiDispatchInterruptContinue:
    fffff803`f1f68bd9 fb              sti
    1: kd> knL
      *** Stack trace for last set context - .thread/.cxr resets it
     # Child-SP          RetAddr           Call Site
    00 ffffd000`20b51920 fffff803`f1f6acfa nt!KiDispatchInterruptContinue
    01 ffffd000`20b51950 00000000`00000000 nt!KiDpcInterrupt+0xca
    1: kd> .trap ffffd000`20b51950
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000000 rbx=0000000000000000 rcx=320b33d0f9800000
    rdx=0000000000000002 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff803f1e8cc1f rsp=ffffd00020b51ae8 rbp=0000000000000000
     r8=ffffe000024ae960  r9=ffffe0000259e004 r10=ffffe0000249a530
    r11=ffffd00020b51ac0 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei ng nz ac pe cy
    nt!KzLowerIrql+0x7:
    fffff803`f1e8cc1f c3              ret
    1: kd> knL
      *** Stack trace for last set context - .thread/.cxr resets it
     # Child-SP          RetAddr           Call Site
    00 ffffd000`20b51ae8 fffff800`00a57625 nt!KzLowerIrql+0x7
    01 ffffd000`20b51af0 fffff803`f1ea52e4 ndis!ndisReceiveWorkerThread+0x169
    02 ffffd000`20b51b80 fffff803`f1f6c2c6 nt!PspSystemThreadStartup+0x58
    03 ffffd000`20b51be0 00000000`00000000 nt!KiStartSystemThread+0x16
    1: kd> ~1
    1: kd> r
    Last set context:
    rax=0000000000000000 rbx=0000000000000000 rcx=320b33d0f9800000
    rdx=0000000000000002 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff803f1e8cc1f rsp=ffffd00020b51ae8 rbp=0000000000000000
     r8=ffffe000024ae960  r9=ffffe0000259e004 r10=ffffe0000249a530
    r11=ffffd00020b51ac0 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei ng nz ac pe cy
    cs=0010  ss=0018  ds=0000  es=0000  fs=0000  gs=0000             efl=00000293
    nt!KzLowerIrql+0x7:
    fffff803`f1e8cc1f c3              ret
    1: kd> knL
      *** Stack trace for last set context - .thread/.cxr resets it
     # Child-SP          RetAddr           Call Site
    00 ffffd000`20b51ae8 fffff800`00a57625 nt!KzLowerIrql+0x7
    01 ffffd000`20b51af0 fffff803`f1ea52e4 ndis!ndisReceiveWorkerThread+0x169
    02 ffffd000`20b51b80 fffff803`f1f6c2c6 nt!PspSystemThreadStartup+0x58
    03 ffffd000`20b51be0 00000000`00000000 nt!KiStartSystemThread+0x16
    1: kd> !thread
    THREAD ffffe000048c4080  Cid 0f00.11e8  Teb: 000000007fe11000 Win32Thread: 0000000000000000 RUNNING on processor 1
    Not impersonating
    DeviceMap                 ffffc00000df2260
    Owning Process            ffffe00003a54900       Image:         uTorrent.exe
    Attached Process          N/A            Image:         N/A
    Wait Start TickCount      888613         Ticks: 690 (0:00:00:10.781)
    Context Switch Count      84694          IdealProcessor: 1             
    UserTime                  00:00:07.421
    KernelTime                00:00:02.828
    Win32 Start Address 0x0000000000499998
    Stack Init ffffd00028387c10 Current ffffd00028386f60
    Base ffffd00028388000 Limit ffffd00028381000 Call 0
    Priority 9 BasePriority 8 UnusualBoost 0 ForegroundBoost 0 IoPriority 2 PagePriority 5
    Child-SP          RetAddr           : Args to Child                                                           : Call Site
    00000000`00000000 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0
    
    1: kd> !pcr
    KPCR for Processor 1 at ffffd000201d8000:
        Major 1 Minor 1
        NtTib.ExceptionList: ffffd000201e5280
            NtTib.StackBase: ffffd000201de2c0
           NtTib.StackLimit: 000000000c90e7e8
         NtTib.SubSystemTib: ffffd000201d8000
              NtTib.Version: 00000000201d8180
          NtTib.UserPointer: ffffd000201d87f0
              NtTib.SelfTib: 000000007fe11000
    
                    SelfPcr: 0000000000000000
                       Prcb: ffffd000201d8180
                       Irql: 0000000000000000
                        IRR: 0000000000000000
                        IDR: 0000000000000000
              InterruptMode: 0000000000000000
                        IDT: 0000000000000000
                        GDT: 0000000000000000
                        TSS: 0000000000000000
    
              CurrentThread: ffffe000048c4080
                 NextThread: ffffe00004668480
                 IdleThread: ffffd000201e4340
    
                  DpcQueue: Unable to read nt!_KDPC_DATA.DpcListHead.Flink @ ffffd000201daf00
    1: kd> lm vm Rt630x64
    start             end                 module name
    fffff800`01b3d000 fffff800`01be6000   Rt630x64   (no symbols)           
        Loaded symbol image file: Rt630x64.sys
        Image path: \SystemRoot\system32\DRIVERS\Rt630x64.sys
        Image name: Rt630x64.sys
        Timestamp:        Tue Jun 12 09:37:53 2012 (4FD74631)
        CheckSum:         000AEEBB
        ImageSize:        000A9000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Last edited by usasma; 27 Nov 2013 at 06:52.
      My System SpecsSystem Spec

  6. #26


    -Okay I'm erased my ssd then did a clean install of windows 8.1, but after that still got BSOD's
    -I've also installed every windows update, installed Windows 8.1 realtek driver, istalled every new driver with windows 8.1 compability and still getting BSOD's
    -Also my latest BSOD wasnt a clock_watchdog_timeout, It was UNEXPECTED_KERNEL_MODE_TRAP 00000000`00000008 ntoskrnl.exe

    I grow really tired of the uselessnes of my windows 8.1. I think erase everything and install a windows 7.
      My System SpecsSystem Spec

  7. #27


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


    At this point I would try Win7 to see if that fixes the BSOD's.
    If it does, then try Win8 (not 8.1) and see if that works. That's the way to rule out the incompatibility.

    Please rerun the data collection application so we can have a look at the new setup.
    Please see the "Usual causes" section at this link: BSOD Index
    It shows lot's of different causes for this error - and in this way is similar to the problems that we faced with the Clock Watchdog error.

    FWIW - I still have problems trying to install 8.1 on my new Samsung laptop
      My System SpecsSystem Spec

Page 3 of 3 FirstFirst 123
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