BSOD when laptop goes to idle auto lock screen


  1. Posts : 1
    Win7 64bit
       #1

    BSOD when laptop goes to idle auto lock screen


    All, I keep getting a BSOD on Windows 7 64bit, it happens when the workstation is doing the idle timeout lockscreen.


    Microsoft (R) Windows Debugger Version 10.0.10586.567 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\Windows\MEMORY.DMP]
    Kernel Summary Dump File: Kernel address space is available, User address space may not be available.

    Symbol search path is: srv*
    Executable search path is:
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7601.23418.amd64fre.win7sp1_ldr.160408-2045
    Machine Name:
    Kernel base = 0xfffff800`0380e000 PsLoadedModuleList = 0xfffff800`03a50730
    Debug session time: Mon Jun 27 19:14:39.230 2016 (UTC - 4:00)
    System Uptime: 0 days 0:52:21.992
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ................................................................
    .....
    Loading User Symbols
    PEB is paged out (Peb.Ldr = 000007ff`fffdb018). Type ".hh dbgerr001" for details
    Loading unloaded module list
    .................
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 1, {7734bbaa, 0, ffff, fffff8800f3d6b60}

    Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExit+245 )

    Followup: MachineOwner
    ---------

    0: kd> !analyze -v
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    APC_INDEX_MISMATCH (1)
    This is a kernel internal error. The most common reason to see this
    bugcheck is when a filesystem or a driver has a mismatched number of
    calls to disable and re-enable APCs. The key data item is the
    Thread->CombinedApcDisable field. This consists of two separate 16-bit
    fields, the SpecialApcDisable and the KernelApcDisable. A negative value
    of either indicates that a driver has disabled special or normal APCs
    (respectively) without re-enabling them; a positive value indicates that
    a driver has enabled special or normal APCs (respectively) too many times.
    Arguments:
    Arg1: 000000007734bbaa, Address of system call function or worker routine
    Arg2: 0000000000000000, Thread->ApcStateIndex
    Arg3: 000000000000ffff, (Thread->SpecialApcDisable << 16) | Thread->KernelApcDisable
    Arg4: fffff8800f3d6b60, Call type (0 - system call, 1 - worker routine)

    Debugging Details:
    ------------------


    DUMP_CLASS: 1

    DUMP_QUALIFIER: 401

    BUILD_VERSION_STRING: 7601.23418.amd64fre.win7sp1_ldr.160408-2045

    SYSTEM_MANUFACTURER: Dell Inc.

    SYSTEM_PRODUCT_NAME: Precision 7510

    SYSTEM_SKU: 06D9

    BIOS_VENDOR: Dell Inc.

    BIOS_VERSION: 1.3.10

    BIOS_DATE: 01/24/2016

    BASEBOARD_MANUFACTURER: Dell Inc.

    BASEBOARD_PRODUCT: 0RJHDG

    BASEBOARD_VERSION: A00

    DUMP_TYPE: 1

    BUGCHECK_P1: 7734bbaa

    BUGCHECK_P2: 0

    BUGCHECK_P3: ffff

    BUGCHECK_P4: fffff8800f3d6b60

    FAULTING_IP:
    +0
    00000000`7734bbaa ?? ???

    CPU_COUNT: 8

    CPU_MHZ: a98

    CPU_VENDOR: GenuineIntel

    CPU_FAMILY: 6

    CPU_MODEL: 5e

    CPU_STEPPING: 3

    CPU_MICROCODE: 6,5e,3,0 (F,M,S,R) SIG: 74'00000000 (cache) 74'00000000 (init)

    DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

    BUGCHECK_STR: 0x1

    PROCESS_NAME: audiodg.exe

    CURRENT_IRQL: 0

    ANALYSIS_SESSION_HOST:

    ANALYSIS_SESSION_TIME: 06-29-2016 10:56:09.0825

    ANALYSIS_VERSION: 10.0.10586.567 amd64fre

    LAST_CONTROL_TRANSFER: from fffff8000387c9a9 to fffff8000387d400

    STACK_TEXT:
    fffff880`0f3d6928 fffff800`0387c9a9 : 00000000`00000001 00000000`7734bbaa 00000000`00000000 00000000`0000ffff : nt!KeBugCheckEx
    fffff880`0f3d6930 fffff800`0387c8e0 : fffffa80`1129f060 00000000`0083df88 fffff880`0f3d6a88 00000000`00000001 : nt!KiBugCheckDispatch+0x69
    fffff880`0f3d6a70 00000000`7734bbaa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x245
    00000000`0083df58 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7734bbaa


    STACK_COMMAND: kb

    THREAD_SHA1_HASH_MOD_FUNC: 713a38487ff3d82058f51d9870e0b3de39cbf964

    THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 561f1421a866d36916a994b3bd23a42b1aea0bb5

    THREAD_SHA1_HASH_MOD: 2a7ca9d3ab5386d53fea7498e1d81b9c4a4c036b

    FOLLOWUP_IP:
    nt!KiSystemServiceExit+245
    fffff800`0387c8e0 4883ec50 sub rsp,50h

    FAULT_INSTR_CODE: 50ec8348

    SYMBOL_STACK_INDEX: 2

    SYMBOL_NAME: nt!KiSystemServiceExit+245

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: nt

    IMAGE_NAME: ntkrnlmp.exe

    DEBUG_FLR_IMAGE_TIMESTAMP: 5708972e

    IMAGE_VERSION: 6.1.7601.23418

    FAILURE_BUCKET_ID: X64_0x1_SysCallNum_4_nt!KiSystemServiceExit+245

    BUCKET_ID: X64_0x1_SysCallNum_4_nt!KiSystemServiceExit+245

    PRIMARY_PROBLEM_CLASS: X64_0x1_SysCallNum_4_nt!KiSystemServiceExit+245

    TARGET_TIME: 2016-06-27T23:14:39.000Z

    OSBUILD: 7601

    OSSERVICEPACK: 1000

    SERVICEPACK_NUMBER: 0

    OS_REVISION: 0

    SUITE_MASK: 272

    PRODUCT_TYPE: 1

    OSPLATFORM_TYPE: x64

    OSNAME: Windows 7

    OSEDITION: Windows 7 WinNt (Service Pack 1) TerminalServer SingleUserTS

    OS_LOCALE:

    USER_LCID: 0

    OSBUILD_TIMESTAMP: 2016-04-09 01:46:22

    BUILDDATESTAMP_STR: 160408-2045

    BUILDLAB_STR: win7sp1_ldr

    BUILDOSVER_STR: 6.1.7601.23418.amd64fre.win7sp1_ldr.160408-2045

    ANALYSIS_SESSION_ELAPSED_TIME: bf6

    ANALYSIS_SOURCE: KM

    FAILURE_ID_HASH_STRING: km:x64_0x1_syscallnum_4_nt!kisystemserviceexit+245

    FAILURE_ID_HASH: {e506ede0-d282-2e4c-5056-6cb373197a73}

    Followup: MachineOwner
    ---------
      My Computer


  2. Posts : 7,050
    Windows 10 Pro
       #2
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 19:52.
Find Us