Daily Random BSODs Win7 Ent x64

Jrob78 · 17 Jan 2011

Hi Carl,

I followed you advice and was not able to isolate a bad module. As the Memtest only had 1 error in over 25+ passes I tried testing that stick solo going 10+ passes later no errors. I tried my other 3 stick solo same thing. Passes varied from 10-100, depends on how long i forgot about them running over the weekend.

I have also tried 1 stick in every slot and no errors.

Currenly I'm running 2 of 4 stick and its been close to 24 hours error free.

Any advice on what to try next if I crash again?

As always, Thanks for all your help.

CarlTR6 · 17 Jan 2011

RAM errors can be caused by any of the following: bad RAM stick; RAM incompatibility - different brands, different models of the same brand, different types, etc; RAM incompatible with the motherboard; bad RAM slots; bad memory controller; failing power supply short in wiring or on the motherboard; RAM voltages and timing; faulty CPU. Is all of your RAM the type, brand and model?

I am glad you are running smoothly and I hope this continues. If you crash again, run Prime95 to test your CPU and your RAM. Carefully follow the instructions in this tutorial: https://www.sevenforums.com/tutorials...t-prime95.html. Run 3 separate tests, one on each of the settings (Blend, Small FFTs, Large FFTs). Post back with your results.

Jrob78 · 18 Jan 2011

Hi Carl,

The Ram is all the same brand and model. I try Prime95 and post back with my results.

CarlTR6 · 18 Jan 2011

It could be an issue with the voltages and timings when you have all of your RAM installed. We will see what Prime 95 shows. At least you are running smoothly with the two sticks installed.

Jrob78 · 20 Jan 2011

Hi Carl,
Well I was running smoothly. I ran all 3 tests with Prime95 (over 40 hours) and had no issues. I stopped prime95 decided all was well and then kicked off MS Sec Essentials scan and opened up IE8 had a couple tabs open and left for work this morning. I checked on it about 1.5 hours later and it had BSODed (attached).

Thanks,

Jordie

CarlTR6 · 21 Jan 2011

Your latest dump is bugcheck A0, INTERNAL_POWER_ERROR. The power policy manager experienced a fatal error.

Here is some reading from Microsoft on this error. I suggest you read these and see if something applies to your system.

KB 974772 Error when entering Hibernation on a Windows 7-based computer: “STOP 0x000000A0 INTERNAL_POWER_ERROR (0x0000000B, 0x????????, 0x????????, 0x????????)”
KB 979148 "0x0000009F" or "0x000000A0" Stop errors on a computer that is running Windows Vista or Windows Server 2008 when a USB webcam is set as the default audio device

More BSOD articles at this link: stop: 0x000000a0 - Microsoft Search.

Go through your hibernation settings and see what devices you have set to wake up your computer from hibernation. In particular check USB devices.

Code:

Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02a58000 PsLoadedModuleList = 0xfffff800`02c95e50
Debug session time: Tue Jan 11 22:38:09.546 2011 (GMT-5)
System Uptime: 0 days 4:55:06.201
Loading Kernel Symbols
...............................................................
................................................................
...................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A0, {b, 5fede000, 3, f888000}

Probably caused by : ntkrnlmp.exe ( nt!PopWriteHiberPages+a3 )

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

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

INTERNAL_POWER_ERROR (a0)
The power policy manager experienced a fatal error.
Arguments:
Arg1: 000000000000000b, The hibernation file is too small.
Arg2: 000000005fede000, Size of the hibernation file.
Arg3: 0000000000000003, HIBERFILE_PROGRESS_MEMORY_RANGES
Arg4: 000000000f888000, Size of the remaining memory ranges.

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


BUGCHECK_STR:  0xA0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002d08513 to fffff80002ac8740

STACK_TEXT:  
fffff880`0249f1b8 fffff800`02d08513 : 00000000`000000a0 00000000`0000000b 00000000`5fede000 00000000`00000003 : nt!KeBugCheckEx
fffff880`0249f1c0 fffff800`02d08bbb : fffffa80`01d78240 00000000`0000e000 fffffa80`01d78240 00000000`0000fcd0 : nt!PopWriteHiberPages+0xa3
fffff880`0249f3c0 fffff800`02d08d25 : 00002a9d`5178e8d7 fffff880`0249f6c8 fffff880`0000e000 00000000`00000010 : nt!PopAddPagesToCompressedPageSet+0x1eb
fffff880`0249f450 fffff800`02d0a132 : fffff880`04712000 fffff880`0249f6c8 00000000`00000020 00000000`00000050 : nt!PopBufferCompressedPageSet+0xd5
fffff880`0249f4c0 fffff800`02d0a919 : fffffa80`00006ac5 fffff880`069e3000 00000000`0005fed9 00000000`0000fcd0 : nt!PopWriteHiberImage+0x3d2
fffff880`0249f6b0 fffff800`02a1509e : ffffffff`ffd0d000 00000000`00000000 fffff800`02d0a730 00000000`00000000 : nt!PopSaveHiberContext+0x1ea
fffff880`0249f860 fffff800`02d0fbe9 : 00000000`00003705 00000000`00000000 00000000`00000000 fffff800`02ab2f6b : hal!HaliAcpiSleep+0x18f
fffff880`0249f8d0 fffff800`02d0fc8f : 00000000`00000000 fffffa80`01d78240 fffff800`02c78420 00000000`02d0bee0 : nt!PopHandleNextState+0x12a
fffff880`0249f920 fffff800`02d15140 : 00000000`00000005 00000000`00000001 00000000`00000000 fffff880`0249faa0 : nt!PopIssueNextState+0x1f
fffff880`0249f950 fffff800`02d155a4 : 00000000`00000000 00000000`0007feab 00000000`00000000 00000000`00000001 : nt!PopInvokeSystemStateHandler+0x3c0
fffff880`0249fb10 fffff800`02d11464 : ffffffff`ffffffff ffffffff`ffffffff 00000000`0007feab 00000000`00000000 : nt!PopEndMirroring+0x84
fffff880`0249fbe0 fffff800`02d15925 : fffff880`0249fd00 fffff880`00000008 00000000`00000000 fffffa80`00000008 : nt!MmDuplicateMemory+0xb64
fffff880`0249fcd0 fffff800`02d6cc06 : fffffa80`019c7b60 fffffa80`00000000 00000000`00000000 fffff800`02ac05c7 : nt!PopTransitionToSleep+0xd5
fffff880`0249fd40 fffff800`02aa6c26 : fffff880`009e8180 fffffa80`019c7b60 fffffa80`023c6b60 fffff880`0121b534 : nt!PspSystemThreadStartup+0x5a
fffff880`0249fd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!PopWriteHiberPages+a3
fffff800`02d08513 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!PopWriteHiberPages+a3

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

FAILURE_BUCKET_ID:  X64_0xA0_nt!PopWriteHiberPages+a3

BUCKET_ID:  X64_0xA0_nt!PopWriteHiberPages+a3

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

Jrob78 · 31 Jan 2011

Hi Carl,

I wanted to say thanks for all your help with investigating my BSOD issues. It appears that 1 of my Ram sticks was the culprit as I am down to 2 GB and been running fine since except for the last BSOD you reviewed.

I did find it weird that MemTest only showed 1 error after multiple passes in numerous configurations. Now to try and get my RAM replaced from OCZ.

Again Thanks for all your help.

Jordie