Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD on hibernate - different error messages

06 Oct 2015   #1
jacks computer

Windows 7 Home Premium 64 bit
 
 
BSOD on hibernate - different error messages

Since a month or so my computer crash while it is in hibernate. Not each time, but very often. First I thought it is a driver issue, but Bugcheck Analysis with WinDbg shows different error. It seems that each crash produce a different error message.

I am not a computer geek, but I can often solve computer issues searching the web for answers. But here I stuck. So I hope that someone here can help me to find out what caused the BSOD.

Here are some output of crashes:
Quote:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {0, 2, 1, fffff80002af5233}

Probably caused by : memory_corruption ( nt!MiReferenceControlArea+1ff )

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

3: 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: 0000000000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, 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: fffff80002af5233, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002d09100
0000000000000000

CURRENT_IRQL: 2

FAULTING_IP:
nt!MiReferenceControlArea+1ff
fffff800`02af5233 488908 mov qword ptr [rax],rcx

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: WerFault.exe

TRAP_FRAME: fffff8800602c5f0 -- (.trap 0xfffff8800602c5f0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000010000000000
rdx=0000000080000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002af5233 rsp=fffff8800602c780 rbp=fffff88002fd7180
r8=0000000000000000 r9=fffff88002fd7180 r10=0000000000000000
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nt!MiReferenceControlArea+0x1ff:
fffff800`02af5233 488908 mov qword ptr [rax],rcx ds:00000000`00000000=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80002acab69 to fffff80002acb5c0

STACK_TEXT:
fffff880`0602c4a8 fffff800`02acab69 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`0602c4b0 fffff800`02ac97e0 : fffffa80`0943ebe0 fffff880`01177b70 00000000`00000000 fffffa80`067da5b0 : nt!KiBugCheckDispatch+0x69
fffff880`0602c5f0 fffff800`02af5233 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x260
fffff880`0602c780 fffff800`02dc85c5 : 00000000`00000000 00000000`00000002 00000000`00000080 00000000`01000000 : nt!MiReferenceControlArea+0x1ff
fffff880`0602c7f0 fffff800`02da608e : fffff880`0602ca40 fffff880`0602cb60 00000000`00000000 fffff880`0602ca38 : nt!MmCreateSection+0x265
fffff880`0602c9f0 fffff800`02aca853 : fffffa80`092cf510 00000000`0018d768 fffff880`0602ca88 00000000`0018d9f8 : nt!NtCreateSection+0x171
fffff880`0602ca70 00000000`778cde5a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0018d748 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x778cde5a


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!MiReferenceControlArea+1ff
fffff800`02af5233 488908 mov qword ptr [rax],rcx

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: nt!MiReferenceControlArea+1ff

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 55afca65

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: X64_0xA_nt!MiReferenceControlArea+1ff

BUCKET_ID: X64_0xA_nt!MiReferenceControlArea+1ff

Followup: MachineOwner
---------
Quote:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 19, {3, fffffa80072f60f0, ff7ffa80072f60f0, fffffa80072f60f0}

Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+c96 )

Followup: Pool_corruption
---------

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

BAD_POOL_HEADER (19)
The pool is already corrupt at the time of the current request.
This may or may not be due to the caller.
The internal pool links must be walked to figure out a possible cause of
the problem, and then special pool applied to the suspect tags or the driver
verifier to a suspect driver.
Arguments:
Arg1: 0000000000000003, the pool freelist is corrupt.
Arg2: fffffa80072f60f0, the pool entry being checked.
Arg3: ff7ffa80072f60f0, the read back flink freelist value (should be the same as 2).
Arg4: fffffa80072f60f0, the read back blink freelist value (should be the same as 2).

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


BUGCHECK_STR: 0x19_3

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: dllhost.exe

CURRENT_IRQL: 2

LAST_CONTROL_TRANSFER: from fffff80002bc66ea to fffff80002a8f5c0

STACK_TEXT:
fffff880`094292e8 fffff800`02bc66ea : 00000000`00000019 00000000`00000003 fffffa80`072f60f0 ff7ffa80`072f60f0 : nt!KeBugCheckEx
fffff880`094292f0 fffff800`02bc81a1 : 00000000`000000a0 fffffa80`07ef6760 00000000`00000000 69634d43`09502720 : nt!ExDeferredFreePool+0xc96
fffff880`09429380 fffff800`02d56e77 : fffffa80`0a3a0650 fffff8a0`0c285090 fffff8a0`6c546553 00000000`00000003 : nt!ExFreePoolWithTag+0x411
fffff880`09429430 fffff800`02a99754 : 00000000`00000000 00000000`00000000 00000000`00000004 fffffa80`06656f30 : nt!SepTokenDeleteMethod+0x97
fffff880`09429460 fffff800`02d6337a : 00000000`00000004 fffff8a0`0cfb4730 fffff8a0`0cfb4710 fffffa80`06d61998 : nt!ObfDereferenceObject+0xd4
fffff880`094294c0 fffff800`02d9c9c8 : fffff8a0`0cfb4710 fffffa80`06d61998 fffff8a0`0cfb4730 fffffa80`000004b0 : nt!AlpcpSecurityDestroyProcedure+0x10e
fffff880`094294f0 fffff800`02d304df : 00000000`00000000 fffff8a0`0cfb4730 fffffa80`06d61988 fffffa80`0a3a0650 : nt!AlpcpDestroyBlob+0x28
fffff880`09429520 fffff800`02d30337 : 00000000`00000000 fffffa80`06d61840 fffffa80`06d61988 00000000`000007ff : nt!AlpcpFlushResourcesPort+0x10b
fffff880`09429550 fffff800`02d30d6c : fffffa80`06d61870 00000000`00000001 fffff8a0`0f1e53c0 00000000`00000000 : nt!AlpcpDoPortCleanup+0x97
fffff880`09429580 fffff800`02d8654e : 00000000`00000000 fffffa80`06d61840 00000000`00000000 fffff800`02a9975c : nt!AlpcpClosePort+0x44
fffff880`094295b0 fffff800`02d861bf : fffffa80`06d61840 fffffa80`00000001 fffff8a0`0f1e53c0 00000000`00000000 : nt!ObpDecrementHandleCount+0x8e
fffff880`09429630 fffff800`02d47380 : 00000000`00000220 fffff8a0`0f1e53c0 fffff8a0`15472880 00000000`00000220 : nt!ObpCloseHandleTableEntry+0xaf
fffff880`094296c0 fffff800`02d47278 : 00000000`00000004 00000000`00000000 fffffa80`0a3a0650 fffff800`02d32411 : nt!ObpCloseHandleProcedure+0x30
fffff880`09429700 fffff800`02d4790a : fffff8a0`0e0b1601 fffff880`09429ae0 fffffa80`0a3a0650 00000000`00000001 : nt!ExSweepHandleTable+0x74
fffff880`09429740 fffff800`02d64572 : fffff8a0`0e0b16b0 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ObKillProcess+0x62
fffff880`09429780 fffff800`02d490dd : 00000000`00000000 00000000`00000201 000007ff`fffdb000 fffffa80`0a72db50 : nt!PspExitThread+0x522
fffff880`09429880 fffff800`02a82d5a : 00000000`00000001 00000000`00000000 fffffa80`09312440 fffff880`02f65180 : nt!PsExitSpecialApc+0x1d
fffff880`094298b0 fffff800`02a830a0 : 00000000`00000000 fffff880`09429930 fffff800`02d49050 00000000`00000001 : nt!KiDeliverApc+0x2ca
fffff880`09429930 fffff800`02a8e8f7 : fffffa80`09312440 00000000`01e1fc08 fffff880`09429a88 fffff880`09429a00 : nt!KiInitiateUserApc+0x70
fffff880`09429a70 00000000`76e1df6a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x9c
00000000`01e1fbe8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76e1df6a


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!ExDeferredFreePool+c96
fffff800`02bc66ea cc int 3

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!ExDeferredFreePool+c96

FOLLOWUP_NAME: Pool_corruption

IMAGE_NAME: Pool_Corruption

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MODULE_NAME: Pool_Corruption

FAILURE_BUCKET_ID: X64_0x19_3_nt!ExDeferredFreePool+c96

BUCKET_ID: X64_0x19_3_nt!ExDeferredFreePool+c96

Followup: Pool_corruption
---------
Quote:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 19, {20, fffffa80067f7ba0, fffffa80067f8020, 4480004}

GetPointerFromAddress: unable to read from fffff80002d05100
Probably caused by : ntkrnlmp.exe ( nt!ObpCloseHandleTableEntry+c1 )

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

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

BAD_POOL_HEADER (19)
The pool is already corrupt at the time of the current request.
This may or may not be due to the caller.
The internal pool links must be walked to figure out a possible cause of
the problem, and then special pool applied to the suspect tags or the driver
verifier to a suspect driver.
Arguments:
Arg1: 0000000000000020, a pool block header size is corrupt.
Arg2: fffffa80067f7ba0, The pool entry we were looking for within the page.
Arg3: fffffa80067f8020, The next pool entry.
Arg4: 0000000004480004, (reserved)

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


BUGCHECK_STR: 0x19_20

POOL_ADDRESS: fffffa80067f7ba0

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: firefox.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff80002bfecae to fffff80002ac75c0

STACK_TEXT:
fffff880`08b8e8e8 fffff800`02bfecae : 00000000`00000019 00000000`00000020 fffffa80`067f7ba0 fffffa80`067f8020 : nt!KeBugCheckEx
fffff880`08b8e8f0 fffff800`02ad175c : 00000000`00000001 fffffa80`067f7bd0 fffffa80`6e657645 fffffa80`0909fa40 : nt!ExDeferredFreePool+0x12da
fffff880`08b8e9a0 fffff800`02dbe1d1 : fffffa80`067f7bd0 00000000`00000000 fffffa80`0a4a2060 00000000`00000000 : nt!ObfDereferenceObject+0xdc
fffff880`08b8ea00 fffff800`02dbe8e4 : 00000000`0000091c fffffa80`070ad060 fffff8a0`0beea5c0 00000000`0000091c : nt!ObpCloseHandleTableEntry+0xc1
fffff880`08b8ea90 fffff800`02ac6853 : fffffa80`0a4a2060 fffff880`08b8eb60 00000000`fff6b000 fffffa80`094629b0 : nt!ObpCloseHandle+0x94
fffff880`08b8eae0 00000000`77b0daaa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`08f4e728 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77b0daaa


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!ObpCloseHandleTableEntry+c1
fffff800`02dbe1d1 33c0 xor eax,eax

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: nt!ObpCloseHandleTableEntry+c1

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 55afca65

FAILURE_BUCKET_ID: X64_0x19_20_nt!ObpCloseHandleTableEntry+c1

BUCKET_ID: X64_0x19_20_nt!ObpCloseHandleTableEntry+c1

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



My System SpecsSystem Spec
.
06 Oct 2015   #2
axe0

Windows 10 Pro
 
 

Hi jacks computer,

Welcome to the 7forums.

Unfortunately, only the !analyze -v output is not always enough.
This because then you only find Windows drivers causing it, which is almost never true.
Windows drivers are the last active, but rarely the cause.

The first is likely a driver problem, because a driver tries to write to the wrong memory.
About the rest I cannot say.

Please read BSOD Posting Instructions & How to upload files
My System SpecsSystem Spec
Reply

 BSOD on hibernate - different error messages




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
Multiple BSOD error messages
Hello! I have all specs filled, so feel free to check dome info there :) My computer is like 1 and half year old, never had problem with him, just little one - PC accepted only 4Gigs of ram instead of 8. I couldn't play games like BF4, or have game and browser opened at same time, but I really...
BSOD Help and Support
Various BSOD error messages
Hi guys Been getting Blue screens with various error messages for a week or 2 now, page file, Reference by pointer IDriver.exe. Tried updating, re installing drivers, disabling and re enabling page files... I have no idea. The Windows key I use was through a training centre and now my account...
BSOD Help and Support
Crashes Sometimes/BSOD with different error messages.
Hello, I've been trying to figure out what is wrong with my diyed PC. I've started getting random BSOD's on my computer and I'm trying to work out what's triggering them. I've used memtest and no errors were found. They normally happen after a few hours. I'm using download software like...
BSOD Help and Support
BSOD after random, different error messages.
Some times I do not receive any error message. Sometimes I get "uncorrectable hardware error". This has been going on for a while but the crashes happen every two days or so. It is very annoying so I would be grateful for any help.
BSOD Help and Support
a series of BSOD error messages
Hi , i try to keep it short... My machine Asus N73SV 12 gb Ram 2 HD win7 64 ultim. I bought the win8 upgrade 15$ version... Installed 100% ...reboot..and now the trouble starts.. a series of error messages..see photos... after hours of talking with MS tech support.. I gave up.... I tested the...
BSOD Help and Support
Various BSOD error messages
I have been getting various seemingly unrelated BSOD messages recently and was hoping someone would hopefully be able to help me. I have ran memtest on my RAM and after 7 tests it showed up no errors I have re-installed windows but still having issues since. Hopefully someone can help, Cheers...
BSOD Help and Support


Our Sites

Site Links

About Us

Find 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 16:09.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App