BSOD after install of windows 7 ultimate

swiftbite said:

Hey guys,

I really need some help

Attached is my BSOD DMP files.

Please help

Took a quick look at the dumps. both were similar. Both reflected a power plan problem when entering or leaving hibernation.

I would
update bios
Run a system file check to verify your system files
to run type cmd in search>right click and run as admin>SFC /SCANNOW

let us know the results
check the power plan settings to see if your computer supports the mode in use by typing powercfg -h in the cmd window.

Could also be caused by memory
download and run memtestx86 to test the memory

Let us know the results

Ken J


Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\110309-17128-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*d:\symbols*Symbol information
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0x82816000 PsLoadedModuleList = 0x8295e810
Debug session time: Tue Nov 3 05:51:38.582 2009 (GMT-5)
System Uptime: 0 days 2:11:06.909
Loading Kernel Symbols
...............................................................
................................................................
....................
Loading User Symbols
Loading unloaded module list
.....
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

INTERNAL_POWER_ERROR (a0)
The power policy manager experienced a fatal error.
Arguments:
Arg1: 0000000b, The hibernation file is too small.
Arg2: 77eba000, Size of the hibernation file.
Arg3: 00000003, HIBERFILE_PROGRESS_MEMORY_RANGES
Arg4: 1d66a000, 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 82b3e033 to 828f2d10

STACK_TEXT:
8d293714 82b3e033 000000a0 0000000b 77eba000 nt!KeBugCheckEx+0x1e
8d293844 82b3dc09 87d12388 e2b0f000 00000010 nt!PopWriteHiberPages+0x98
8d293894 82b3d9e6 000102a0 8d2939b8 00000010 nt!PopAddPagesToCompressedPageSet+0x192
8d2938cc 82b3d6f3 87d12388 8d2939b8 00000001 nt!PopBufferCompressedPageSet+0xaf
8d2939c8 82b3d391 e2ae3000 e2a8a000 00000000 nt!PopWriteHiberImage+0x310
8d293aac 82c464ab 87d12388 00000092 8d293b98 nt!PopSaveHiberContext+0x1be
8d293ae4 82b367d7 00003705 82b3d1d2 87d12388 hal!HaliAcpiSleep+0xbb
8d293b18 82b3669f 00000000 00000000 000f4240 nt!PopHandleNextState+0x107
8d293b2c 82b36429 00000004 00000006 87d12388 nt!PopIssueNextState+0x24
8d293c40 82b3e547 00000006 87d12388 00000000 nt!PopInvokeSystemStateHandler+0x2e7
8d293ca4 82b3be91 00000001 00000006 8bb93ba0 nt!PopEndMirroring+0x64
8d293d1c 82b35a7a 8d293d3c 00000000 85195020 nt!MmDuplicateMemory+0x8ac
8d293d50 82a2466d 8bb93ba0 abb13f10 00000000 nt!PopTransitionToSleep+0xce
8d293d90 828d60d9 82b359ac 8bb93ba0 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!PopWriteHiberPages+98
82b3e033 cc int 3

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!PopWriteHiberPages+98

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrpamp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc007

FAILURE_BUCKET_ID: 0xA0_nt!PopWriteHiberPages+98

BUCKET_ID: 0xA0_nt!PopWriteHiberPages+98

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

System specs please (BIOS version also).

Please go to Start and type in "msinfo32.exe" (without the quotes) and press Enter
Save the report as an .nfo file, then zip up the .nfo file and upload/attach the .zip file with your next post.

Stack text mentioned the HAL and something to do with ACPI - which causes me to wonder about the BIOS and compatibility issues.