Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [F:\BSODDmpFiles\makan\020512-9890-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffffa80`0ca565d0?
Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Machine Name:
Kernel base = 0xfffff800`02e4e000 PsLoadedModuleList = 0xfffff800`0308be70
Debug session time: Sat Feb 4 10:19:09.539 2012 (GMT-7)
System Uptime: 1 days 1:24:15.866
Loading Kernel Symbols
...............................................................
................................................................
...........................................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000009F, {4, 258, fffffa800731a040, fffff800042b94d0}
Unable to load image \SystemRoot\system32\drivers\iaStor.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for iaStor.sys
*** ERROR: Module load completed but symbols could not be loaded for iaStor.sys
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
Followup: memory_corruption
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 0000000000000004, The power transition timed out waiting to synchronize with the Pnp
subsystem.
Arg2: 0000000000000258, Timeout in seconds.
Arg3: fffffa800731a040, The thread currently holding on to the Pnp lock.
Arg4: fffff800042b94d0
Debugging Details:
------------------
DRVPOWERSTATE_SUBCODE: 4
FAULTING_THREAD: fffffa800731a040
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: CODE_CORRUPTION
BUGCHECK_STR: 0x9F
PROCESS_NAME: System
CURRENT_IRQL: 2
LAST_CONTROL_TRANSFER: from fffff80002ec56e2 to fffff80002ec447a
STACK_TEXT:
fffff880`02faf450 fffff800`02ec56e2 : fffffa80`0731a040 fffffa80`0731a040 00000000`00000000 00000000`00000000 : nt!KiSwapContext+0x7a
fffff880`02faf590 fffff800`02ec7b9f : fffffa80`07b6cab0 fffff800`02ff32dd fffffa80`00000000 fffffa80`07ccb010 : nt!KiCommitThreadWait+0x1d2
fffff880`02faf620 fffff800`02fce5b5 : 00000000`00000000 00000000`00000000 fffffa80`07b6ca00 fffff880`00f6f400 : nt!KeWaitForSingleObject+0x19f
fffff880`02faf6c0 fffff880`0108dbf1 : fffffa80`089d31a0 fffffa80`07892c02 00000000`00000000 fffffa80`089d31a0 : nt!IoReleaseRemoveLockAndWaitEx+0x45
fffff880`02faf700 fffffa80`089d31a0 : fffffa80`07892c02 00000000`00000000 fffffa80`089d31a0 00000000`00000000 : iaStor+0x32bf1
fffff880`02faf708 fffffa80`07892c02 : 00000000`00000000 fffffa80`089d31a0 00000000`00000000 fffff880`010b1237 : 0xfffffa80`089d31a0
fffff880`02faf710 00000000`00000000 : fffffa80`089d31a0 00000000`00000000 fffff880`010b1237 fffffa80`07892c10 : 0xfffffa80`07892c02
STACK_COMMAND: .thread 0xfffffa800731a040 ; kb
CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
fffff80002ec47a5 - nt!SwapContext_PatchXSave+2
[ 01:21 ]
fffff80002ec4888 - nt!SwapContext_PatchXRstor+2 (+0xe3)
[ 09:29 ]
fffff80002ec4a45 - nt!EnlightenedSwapContext_PatchXSave+2 (+0x1bd)
[ 01:21 ]
fffff80002ec4b2a - nt!EnlightenedSwapContext_PatchXRstor+2 (+0xe5)
[ 09:29 ]
4 errors : !nt (fffff80002ec47a5-fffff80002ec4b2a)
MODULE_NAME: memory_corruption
IMAGE_NAME: memory_corruption
FOLLOWUP_NAME: memory_corruption
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MEMORY_CORRUPTOR: ONE_BIT_LARGE
FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_ONE_BIT_LARGE
BUCKET_ID: X64_MEMORY_CORRUPTION_ONE_BIT_LARGE
Followup: memory_corruption
---------
Possible causes are Memory problems... Drivers...
If you are overclocking any hardware, please stop.
Run the boot version of
Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of
the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).
Update to Service Pack 1 (SP1)
Links to Service Pack 1 (SP1) and preparation for SP1 courtesy of JMH
An underlying driver may be incompatible\conflicting with your system. Run Driver Verifier to find any issues. To run Driver Verifier, do the following:
a.
Backup your system and user files
b.
Create a system restore point
c. If you do not have a Windows 7 DVD,
Create a system repair disc
d. Run
Driver Verifier
If Windows cannot start in normal mode with driver verifier running, start in safe mode. If it cannot start in safe mode or normal mode, restore the system restore point using
System Restore OPTION TWO.
Thanks to zigzag3143 for contributing to the Verifier steps.
If you are unable to start Windows with all drivers being verified or if the blue screen crashes fail to create .dmp files, run them in groups of 5 or 10 until you find a group that causes blue screen crashes and stores the blue screen .dmp files.
You may also find Avoid Static Damage to Your PC | PCWorld interesting further reading as to why RAM problems can occur. It basically says that ~400 Volts of electrostatic discharge (ESD) can ruin RAM, but you will not feel the discharge until it reaches ~1400-3500 Volts (that link says 3500-4000 Volts, but it varies based on the climate and how dry it is). When RAM receives a shock that we cannot feel, it can work for a while, and then slowly fail over time until symptoms become noticeable. That is one of the many reasons why so many users end up on these forums wondering why their systems are suddenly not working.
Make sure you practice good electrostatic discharge (ESD) habbits and keep yourself grounded when touching PC components.
For ESD Safety, follow these steps:
- Shut down and turn off your computer.
- Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
- Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
- Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working.
Once these steps have been followed, it is safe to remove and replace components within your computer.
Please follow the https://www.sevenforums.com/crashes-d...tructions.html to provide us with the crash reports. While the .dmp files can be analyzed, more information will allow us to help you better.