BSOD when hibernating or shutting down, error: STOP 0X0000000A

katqueenie said:

I've been getting the BSOD many times the past couple days, usually when my computer enters hibernation mode or it's happened when I've selected shut down.

Hi katqueenie.

If you can identify the BSODs start after the installation of the new version of the display driver (as it is appearing from the dumps), roll it back to the previous version that worked good.
Device Manager - Roll Back Driver

Also uninstall Glare Utilities .... it is one of the snake oil programs. Not helpful actually but problematic itself.

Let us know if the BSODs continue even after rolling back the display driver.
___________________________________

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {fffff8a00036af58, 2, 0, fffff8000368425b}

Probably caused by : ntkrnlmp.exe ( nt!ExpScanGeneralLookasideList+a0 )

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

5: 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: fffff8a00036af58, 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: fffff8000368425b, address which referenced memory

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


OVERLAPPED_MODULE: Address regions for 'hiber_iaStor' and 'spsys.sys' overlap

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800038c7100
GetUlongFromAddress: unable to read from fffff800038c71c0
 fffff8a00036af58 Paged pool

CURRENT_IRQL:  2

FAULTING_IP: 
nt!ExpScanGeneralLookasideList+a0
fffff800`0368425b 418b40d8        mov     eax,dword ptr [r8-28h]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

TRAP_FRAME:  fffff880033e7870 -- (.trap 0xfffff880033e7870)
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=fffff8000368425b rsp=fffff880033e7a00 rbp=0000000000000001
 r8=fffff8a00036af80  r9=0000000000000004 r10=0000000000000000
r11=0000000000000100 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
nt!ExpScanGeneralLookasideList+0xa0:
fffff800`0368425b 418b40d8        mov     eax,dword ptr [r8-28h] ds:fffff8a0`0036af58=00000068
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff8000368f169 to fffff8000368fbc0

STACK_TEXT:  
fffff880`033e7728 fffff800`0368f169 : 00000000`0000000a fffff8a0`0036af58 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`033e7730 fffff800`0368dde0 : 00000000`00000000 00000000`00000008 fffff6fb`80008438 fffff800`03835420 : nt!KiBugCheckDispatch+0x69
fffff880`033e7870 fffff800`0368425b : fffff800`03846f48 00000000`00000001 00000000`00000000 fffff800`038c7c40 : nt!KiPageFault+0x260
fffff880`033e7a00 fffff800`03679a60 : 00000000`00000001 00000000`00000008 00000000`00000001 fffff800`038c7c40 : nt!ExpScanGeneralLookasideList+0xa0
fffff880`033e7a60 fffff800`03679fae : 00000000`00000008 fffff880`033e7ad0 00000000`00000001 fffffa80`00000000 : nt!ExAdjustLookasideDepth+0x40
fffff880`033e7a90 fffff800`0392b73a : fffffa80`0cdd87d0 00000000`00000080 fffffa80`0cd415f0 00000000`00000001 : nt!KeBalanceSetManager+0x1be
fffff880`033e7c00 fffff800`036808e6 : fffff880`009b3180 fffffa80`0cdd87d0 fffff880`009be0c0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`033e7c40 00000000`00000000 : fffff880`033e8000 fffff880`033e2000 fffff880`033e75c0 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!ExpScanGeneralLookasideList+a0
fffff800`0368425b 418b40d8        mov     eax,dword ptr [r8-28h]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!ExpScanGeneralLookasideList+a0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  531590fb

IMAGE_VERSION:  6.1.7601.18409

FAILURE_BUCKET_ID:  X64_0xA_nt!ExpScanGeneralLookasideList+a0

BUCKET_ID:  X64_0xA_nt!ExpScanGeneralLookasideList+a0

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0xa_nt!expscangenerallookasidelist+a0

FAILURE_ID_HASH:  {2d4aa3ce-d2f6-a1c2-6e10-dc77b60dfba4}

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

katqueenie said:

Hi Arc,

I uninstalled Glary and downloaded the driver updater, it said I had 14 out of date drivers, I went on the manufacturers websites and all their update tools said I was running the latest version. I installed the 14 updates and am now going to put my computer into hibernate mode and see if I get a BSOD. Thanks for your help so far!

Which driver updater? :)
Asking because I am not aware of any program of this line which provides the actual information. I am somehow afraid that you might have picked a wrong one.

Have you rolled back the display driver?

Yes, that is an ad! We have ads but not for registered members. If you have logged on there you would not have seen that ad. :)

And dont think any bad about yourself. You are now here. You need your time to get accustomed.

Let us know if the BSODs continue.