BSOD possibly after going idle?

[danaagogo]

Hello. I have been getting the BSOD for the last 2 days. I followed the posting instructions but I am unsure what activating event triggers the BSOD. Hopefully I did the log correctly and the issue can be identified. Thank you for your help in advance!

 

[Arc]

Hi danaagogo.

You did the log correctly. But the crash dump itself is not very informative about the cause of the BSOD. And there is a single crash dump only.

The thread title gives a hint that somehow the BSOD have a time relation with sleep-wakeup. In that case, you free up the startup. Windows does not need any other program to auto start with it, but the auto start programs often conflicts and causes various problems including BSODs.

1. Click on the Start button
2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
3. Select the “Startup” tab.
4. Deselect all items other than the antivirus and teh touchpad driver, SynTPEnh. You may keep Dell Dock there, too.
5. Apply > OK
6. Accept then restart.

Report us for any further BSOD after doing it.
______________________________________________

BugCheck A, {fffff80083515c40, 2, 0, fffff800032dc89d}

Probably caused by : ntkrnlmp.exe ( nt!KiCommitThreadWait+26d )

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: fffff80083515c40, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff800032dc89d, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003515100
GetUlongFromAddress: unable to read from fffff800035151c0
 fffff80083515c40 Nonpaged pool

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KiCommitThreadWait+26d
fffff800`032dc89d 4d8bb4c040fc2a00 mov     r14,qword ptr [r8+rax*8+2AFC40h]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre

TRAP_FRAME:  fffff88007bbe9d0 -- (.trap 0xfffff88007bbe9d0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000010000000 rbx=0000000000000000 rcx=0000000000000084
rdx=0000000000187000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800032dc89d rsp=fffff88007bbeb60 rbp=0000000000000000
 r8=fffff80003266000  r9=0000000000000000 r10=fffffffffffffffe
r11=fffff88009383c20 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
nt!KiCommitThreadWait+0x26d:
fffff800`032dc89d 4d8bb4c040fc2a00 mov     r14,qword ptr [r8+rax*8+2AFC40h] ds:fffff800`83515c40=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800032d7fe9 to fffff800032d8a40

STACK_TEXT:  
fffff880`07bbe888 fffff800`032d7fe9 : 00000000`0000000a fffff800`83515c40 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`07bbe890 fffff800`032d6c60 : fffffa80`057ea6b0 fffff800`032db673 fffffa80`00000000 fffffa80`0aa925e0 : nt!KiBugCheckDispatch+0x69
fffff880`07bbe9d0 fffff800`032dc89d : fffffa80`0aa925e0 fffffa80`0aa925e0 fffff8a0`040d09c8 fffffa80`00000004 : nt!KiPageFault+0x260
fffff880`07bbeb60 fffff800`032e0d63 : fffff8a0`040d0630 fffffa80`06520180 fffff880`00000084 fffff880`00000002 : nt!KiCommitThreadWait+0x26d
fffff880`07bbebf0 fffff800`032e267d : 00000000`00000000 fffff800`035ce701 fffff800`034e4a00 00000000`00000002 : nt!KeRemoveQueueEx+0x323
fffff880`07bbecb0 fffff800`03572aba : 00000000`055820bd fffffa80`0aa925e0 00000000`00000080 fffffa80`054455f0 : nt!ExpWorkerThread+0xe9
fffff880`07bbed40 fffff800`032ca426 : fffff880`009e9180 fffffa80`0aa925e0 fffffa80`05457040 fffffa80`06384e70 : nt!PspSystemThreadStartup+0x5a
fffff880`07bbed80 00000000`00000000 : fffff880`07bbf000 fffff880`07bb9000 fffff880`07bbe9e0 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiCommitThreadWait+26d
fffff800`032dc89d 4d8bb4c040fc2a00 mov     r14,qword ptr [r8+rax*8+2AFC40h]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!KiCommitThreadWait+26d

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  5507a73c

IMAGE_VERSION:  6.1.7601.18798

FAILURE_BUCKET_ID:  X64_0xA_nt!KiCommitThreadWait+26d

BUCKET_ID:  X64_0xA_nt!KiCommitThreadWait+26d

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0xa_nt!kicommitthreadwait+26d

FAILURE_ID_HASH:  {9436cc2b-0a72-e98a-a74c-044b06706483}

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