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 every day the same failure 1000009F


08 Dec 2011   #1

Windows 7 Ultimate x64
 
 
BSOD every day the same failure 1000009F

Hey guys, every day BSOD coming I totaly reinstall my computer, run verifier, memory test and so on... unfortunately failure have the same name and I donīt know why. Computer was perfect about 1 year now is something wrong. When computer go to sleep (mostly only second sleep mode), screen go to off but computer didnīt and crash.
What do you mean about it?
Thanx
Comba

*******************************************************************************
* *
* 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: fffffa8009760040, The thread currently holding on to the Pnp lock.
Arg4: fffff80000b9c510
Debugging Details:
------------------

DRVPOWERSTATE_SUBCODE: 4
FAULTING_THREAD: fffffa8009760040
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x9F
PROCESS_NAME: System
CURRENT_IRQL: 2
LOCK_ADDRESS: fffff800030d1b80 -- (!locks fffff800030d1b80)
Resource @ nt!PiEngineLock (0xfffff800030d1b80) Available
WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.

WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.
1 total locks
PNP_TRIAGE:
Lock address : 0xfffff800030d1b80
Thread Count : 0
Thread address: 0x0000000000000000
Thread wait : 0x0
LAST_CONTROL_TRANSFER: from fffff80002ed7f32 to fffff80002ed54da
STACK_TEXT:
fffff880`03b85660 fffff800`02ed7f32 : fffffa80`09760040 fffffa80`09760040 00000000`00000000 00000000`00000000 : nt!KiSwapContext+0x7a
fffff880`03b857a0 fffff800`02eda74f : fffff880`03b85c10 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiCommitThreadWait+0x1d2
fffff880`03b85830 fffff800`02f8d8a5 : 00000000`00000000 00000000`00000000 fffffa80`097f0d00 fffff800`0313c700 : nt!KeWaitForSingleObject+0x19f
fffff880`03b858d0 fffff800`03271b2e : fffff800`030d1940 fffff880`03b859a4 00000000`00000000 00000000`00000001 : nt!PnpDeviceCompletionQueueGetCompletedRequest+0x35
fffff880`03b85920 fffff800`032beb68 : fffffa80`097f0d90 fffffa80`097f0d90 00000000`00000002 00000000`00000000 : nt!PnpDeviceCompletionProcessCompletedRequests+0x5e
fffff880`03b85950 fffff800`032bf018 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000001 : nt!PipProcessDevNodeTree+0x378
fffff880`03b85bc0 fffff800`02fcf8e7 : 00000001`00000003 00000000`00000000 00000000`00000001 00000000`00000084 : nt!PiProcessReenumeration+0x98
fffff880`03b85c10 fffff800`02edd001 : fffff800`02fcf5c0 fffff800`031c9901 fffffa80`09760000 00000000`00000000 : nt!PnpDeviceActionWorker+0x327
fffff880`03b85cb0 fffff800`0316dfee : 00000000`00000000 fffffa80`09760040 00000000`00000080 fffffa80`09746040 : nt!ExpWorkerThread+0x111
fffff880`03b85d40 fffff800`02ec45e6 : fffff880`0396a180 fffffa80`09760040 fffff880`039750c0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03b85d80 00000000`00000000 : fffff880`03b86000 fffff880`03b80000 fffff880`03b85310 00000000`00000000 : nt!KxStartSystemThread+0x16

STACK_COMMAND: .thread 0xfffffa8009760040 ; kb
FOLLOWUP_IP:
nt!KiSwapContext+7a
fffff800`02ed54da 488d8c2400010000 lea rcx,[rsp+100h]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!KiSwapContext+7a
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4e02aaa3
FAILURE_BUCKET_ID: X64_0x9F_4_nt!KiSwapContext+7a
BUCKET_ID: X64_0x9F_4_nt!KiSwapContext+7a
Followup: MachineOwner
---------

been having BSOD's for a while now and i have no idea whats causing them i've updated everything i can think off, ive ran driver verifier, and upload the dump files, im hoping someone can point me to whats up.

Also ive ran memtest, at 8 passes i had an error, but i went on to test both sticks in each slot individually and there where no errors : /

My System SpecsSystem Spec
.

08 Dec 2011   #2

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by combicek View Post
Hey guys, every day BSOD coming I totaly reinstall my computer, run verifier, memory test and so on... unfortunately failure have the same name and I donīt know why. Computer was perfect about 1 year now is something wrong. When computer go to sleep (mostly only second sleep mode), screen go to off but computer didnīt and crash.
What do you mean about it?
Thanx
Comba

*******************************************************************************
* *
* 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: fffffa8009760040, The thread currently holding on to the Pnp lock.
Arg4: fffff80000b9c510
Debugging Details:
------------------

DRVPOWERSTATE_SUBCODE: 4
FAULTING_THREAD: fffffa8009760040
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x9F
PROCESS_NAME: System
CURRENT_IRQL: 2
LOCK_ADDRESS: fffff800030d1b80 -- (!locks fffff800030d1b80)
Resource @ nt!PiEngineLock (0xfffff800030d1b80) Available
WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.

WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.
1 total locks
PNP_TRIAGE:
Lock address : 0xfffff800030d1b80
Thread Count : 0
Thread address: 0x0000000000000000
Thread wait : 0x0
LAST_CONTROL_TRANSFER: from fffff80002ed7f32 to fffff80002ed54da
STACK_TEXT:
fffff880`03b85660 fffff800`02ed7f32 : fffffa80`09760040 fffffa80`09760040 00000000`00000000 00000000`00000000 : nt!KiSwapContext+0x7a
fffff880`03b857a0 fffff800`02eda74f : fffff880`03b85c10 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiCommitThreadWait+0x1d2
fffff880`03b85830 fffff800`02f8d8a5 : 00000000`00000000 00000000`00000000 fffffa80`097f0d00 fffff800`0313c700 : nt!KeWaitForSingleObject+0x19f
fffff880`03b858d0 fffff800`03271b2e : fffff800`030d1940 fffff880`03b859a4 00000000`00000000 00000000`00000001 : nt!PnpDeviceCompletionQueueGetCompletedRequest+0x35
fffff880`03b85920 fffff800`032beb68 : fffffa80`097f0d90 fffffa80`097f0d90 00000000`00000002 00000000`00000000 : nt!PnpDeviceCompletionProcessCompletedRequests+0x5e
fffff880`03b85950 fffff800`032bf018 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000001 : nt!PipProcessDevNodeTree+0x378
fffff880`03b85bc0 fffff800`02fcf8e7 : 00000001`00000003 00000000`00000000 00000000`00000001 00000000`00000084 : nt!PiProcessReenumeration+0x98
fffff880`03b85c10 fffff800`02edd001 : fffff800`02fcf5c0 fffff800`031c9901 fffffa80`09760000 00000000`00000000 : nt!PnpDeviceActionWorker+0x327
fffff880`03b85cb0 fffff800`0316dfee : 00000000`00000000 fffffa80`09760040 00000000`00000080 fffffa80`09746040 : nt!ExpWorkerThread+0x111
fffff880`03b85d40 fffff800`02ec45e6 : fffff880`0396a180 fffffa80`09760040 fffff880`039750c0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03b85d80 00000000`00000000 : fffff880`03b86000 fffff880`03b80000 fffff880`03b85310 00000000`00000000 : nt!KxStartSystemThread+0x16

STACK_COMMAND: .thread 0xfffffa8009760040 ; kb
FOLLOWUP_IP:
nt!KiSwapContext+7a
fffff800`02ed54da 488d8c2400010000 lea rcx,[rsp+100h]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!KiSwapContext+7a
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4e02aaa3
FAILURE_BUCKET_ID: X64_0x9F_4_nt!KiSwapContext+7a
BUCKET_ID: X64_0x9F_4_nt!KiSwapContext+7a
Followup: MachineOwner
---------

been having BSOD's for a while now and i have no idea whats causing them i've updated everything i can think off, ive ran driver verifier, and upload the dump files, im hoping someone can point me to whats up.

Also ive ran memtest, at 8 passes i had an error, but i went on to test both sticks in each slot individually and there where no errors : /
Verifier should tell us which driver but none of these had verifier enabled.
My System SpecsSystem Spec
12 Dec 2011   #3

Windows 7 Ultimate x64
 
 

Hi, so itīs take 2 days with slow computer (verifier "on") and now come crash for iaStor.sys . Is this problem with my Intel SSD hardrive and what can I do?
Comba

Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {fffff8a00c299700, 2, 1, fffff8800129c3a0}
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
Probably caused by : iaStor.sys ( iaStor+773a0 )
Followup: MachineOwner
---------
4: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: fffff8a00c299700, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff8800129c3a0, address which referenced memory
Debugging Details:
------------------

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800030bf100
fffff8a00c299700
CURRENT_IRQL: 2
FAULTING_IP:
iaStor+773a0
fffff880`0129c3a0 488911 mov qword ptr [rcx],rdx
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR: 0xD1
PROCESS_NAME: System
TRAP_FRAME: fffff88003b4e9f0 -- (.trap 0xfffff88003b4e9f0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff8a00c299700 rbx=0000000000000000 rcx=fffff8a00c299700
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800129c3a0 rsp=fffff88003b4eb88 rbp=0000000000000008
r8=0000000000000000 r9=0000000000000001 r10=0000007ffffffff8
r11=0000000000000338 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
iaStor+0x773a0:
fffff880`0129c3a0 488911 mov qword ptr [rcx],rdx ds:0246:fffff8a0`0c299700=0000000000000000
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002e8c1e9 to fffff80002e8cc40
STACK_TEXT:
fffff880`03b4e8a8 fffff800`02e8c1e9 : 00000000`0000000a fffff8a0`0c299700 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`03b4e8b0 fffff800`02e8ae60 : ffffffff`ffffffff 00000000`00000001 00000000`00000000 fffffa80`0b12e320 : nt!KiBugCheckDispatch+0x69
fffff880`03b4e9f0 fffff880`0129c3a0 : fffff880`01230055 fffffa80`0b12e300 fffff800`0332dbdf fffffa80`0b49eb38 : nt!KiPageFault+0x260
fffff880`03b4eb88 fffff880`01230055 : fffffa80`0b12e300 fffff800`0332dbdf fffffa80`0b49eb38 fffff980`0440af00 : iaStor+0x773a0
fffff880`03b4eb90 fffffa80`0b12e300 : fffff800`0332dbdf fffffa80`0b49eb38 fffff980`0440af00 fffffa80`0b488a10 : iaStor+0xb055
fffff880`03b4eb98 fffff800`0332dbdf : fffffa80`0b49eb38 fffff980`0440af00 fffffa80`0b488a10 fffffa80`00000000 : 0xfffffa80`0b12e300
fffff880`03b4eba0 fffff880`0124999d : fffffa80`0b488290 00000000`00000002 fffff880`01275430 00000000`00000000 : nt!VerifierKeAcquireSpinLockRaiseToDpc+0x11f
fffff880`03b4ec00 fffffa80`0b488290 : 00000000`00000002 fffff880`01275430 00000000`00000000 fffffa80`0b49ac50 : iaStor+0x2499d
fffff880`03b4ec08 00000000`00000002 : fffff880`01275430 00000000`00000000 fffffa80`0b49ac50 fffff880`012283fb : 0xfffffa80`0b488290
fffff880`03b4ec10 fffff880`01275430 : 00000000`00000000 fffffa80`0b49ac50 fffff880`012283fb fffffa80`0b12e320 : 0x2
fffff880`03b4ec18 00000000`00000000 : fffffa80`0b49ac50 fffff880`012283fb fffffa80`0b12e320 fffffa80`0b12e301 : iaStor+0x50430

STACK_COMMAND: kb
FOLLOWUP_IP:
iaStor+773a0
fffff880`0129c3a0 488911 mov qword ptr [rcx],rdx
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: iaStor+773a0
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: iaStor
IMAGE_NAME: iaStor.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4dd69c48
FAILURE_BUCKET_ID: X64_0xD1_VRF_iaStor+773a0
BUCKET_ID: X64_0xD1_VRF_iaStor+773a0
Followup: MachineOwner
---------
My System SpecsSystem Spec
.


21 Dec 2011   #4

Windows 7 Ultimate x64
 
 

Hi everyone, problem solved. For several days did not cause system BSOD. The change that I make was stopped the SATA connection of my primary HDD (that is SSD Intel) on my MB in position SATA3 and start using one of six Intel ICH10R SATA2 controllers. Itīs hard to believe but problem is in onboard Marvell's SE9128 chip for SATA3, at least on my PC.
Perhaps this information will someone help.
Comba
My System SpecsSystem Spec
Reply

 BSOD every day the same failure 1000009F




Thread Tools



Similar help and support threads for2: BSOD every day the same failure 1000009F
Thread Forum
Solved BSOD BCCode: 1000009f BSOD Help and Support
BSOD error 1000009f doing basic stuff BSOD Help and Support
BSOD 3rd time in 7 days error 1000009f BSOD Help and Support
BSOD - BC 1000009f BSOD Help and Support
BSOD 1000009f every 15 Minutes BSOD Help and Support
BSOD BCCode 1000009f Sony VAIO 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 01:23 PM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33