Share via

Windows Blue Screen error 1000009f-How do I fix it?

Anonymous
2014-05-20T23:54:25+00:00

Thanks in advance for any help you can provide me. I have been dealing with this error and can't seem to correct it. Here's my information:

Problem signature:

  Problem Event Name: BlueScreen

  OS Version: 6.1.7601.2.1.0.768.3

  Locale ID: 1033

Additional information about the problem:

  BCCode: 1000009f

  BCP1: 0000000000000004

  BCP2: 0000000000000258

  BCP3: FFFFFA80039DC660

  BCP4: FFFFF80000B9C510

  OS Version: 6_1_7601

  Service Pack: 1_0

  Product: 768_1

Here's a link to the .dmp file in question:

https://onedrive.live.com/redir?resid=4F08C16C7A7DD6CB%21107

Windows for home | Previous Windows versions | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments
Answer accepted by question author
  1. Anonymous
    2014-05-21T02:02:01+00:00

    Thanks very much!

    The attached DMP file is of the DRIVER_POWER_STATE_FAILURE (9f) bug check.

    This bug check indicates that the driver is in an inconsistent or invalid power state.

    0: kd> !locks

    **** DUMP OF ALL RESOURCE OBJECTS ****

    KD: Scanning for held locks.....................

    Resource @ 0xfffffa8005f68930    Shared 1 owning threads

        Contention Count = 1

         Threads: fffffa80082ecb53-01<*> *** Actual Thread fffffa80082ecb50

    0: kd> !thread fffffa80082ecb50

    THREAD fffffa80082ecb50  Cid 0224.1060  Teb: 000007fffffaa000 Win32Thread: 0000000000000000 WAIT: (WrPageIn) KernelMode Non-Alertable

        fffffa8007dc38a0  NotificationEvent

    IRP List:

        fffffa800dab8990: (0006,03e8) Flags: 00020403  Mdl: fffffa8007dc3940

    Impersonation token:  fffff8a016cba730 (Level Impersonation)

    Owning Process            fffffa8005829650       Image:         svchost.exe

    Attached Process          N/A            Image:         N/A

    Wait Start TickCount      83839          Ticks: 1 (0:00:00:00.015)

    Context Switch Count      5137           IdealProcessor: 2             

    UserTime                  00:00:00.046

    KernelTime                00:00:00.608

    Win32 Start Address 0x000007fef83fd710

    Stack Init fffff8800b8c5db0 Current fffff8800b8c52f0

    Base fffff8800b8c6000 Limit fffff8800b8c0000 Call 0

    Priority 8 BasePriority 7 UnusualBoost 0 ForegroundBoost 0 IoPriority 0 PagePriority 1

    Child-SP          RetAddr           : Args to Child                                                           : Call Site

    fffff8800b8c5330 fffff800034815f2 : 0000000000000000 fffffa80082ecb50 0000000000000000 0000000000000000 : nt!KiSwapContext+0x7a

    fffff8800b8c5470 fffff8000349299f : fffffa800a76e620 fffff800034baee0 0000000000000000 fffffa8007dc3800 : nt!KiCommitThreadWait+0x1d2

    fffff8800b8c5500 fffff800034ba232 : 0000000000000000 fffffa8000000009 fffffa800dab8900 fffff800034b2e00 : nt!KeWaitForSingleObject+0x19f

    fffff8800b8c55a0 fffff8000342c068 : fffffa8007dc3880 0000000000000000 0000000000000000 0000000000000000 : nt!MiWaitForInPageComplete+0xc2

    fffff8800b8c5680 fffff800036e84f2 : 0000000000000000 fffffa8006d24160 0000000000000001 fffffa8006d24160 : nt!MiPfCompletePrefetchIos+0x54

    fffff8800b8c56b0 fffff800038ec4dd : 0000000000000001 0000000000000001 fffffa8006d24160 fffff8800b8c5778 : nt!MmPrefetchPages+0x13a

    fffff8800b8c5710 fffff800038f44fe : fffff8a000000000 fffff8a000000000 fffff8a000000038 fffff8a000000000 : nt!PfpPrefetchFilesTrickle+0x21d

    fffff8800b8c5810 fffff800038f4dd7 : 0000000000000000 fffff8800b8c5ca0 fffff8800b8c5a08 fffff8a0016df060 : nt!PfpPrefetchRequestPerform+0x30e

    fffff8800b8c5960 fffff8000390168e : fffff8800b8c5a08 fffff8800b8c5c01 fffffa80085d15f0 0000000000000000 : nt!PfpPrefetchRequest+0x176

    fffff8800b8c59d0 fffff80003905eba : 0000000000000000 000000000000004f 0000000000000000 ffffffffffffff01 : nt!PfSetSuperfetchInformation+0x1ad

    fffff8800b8c5ab0 fffff8000348ae53 : fffffa80082ecb50 0000000000000000 0000000000000001 000000000000dd68 : nt!NtSetSystemInformation+0xc8d

    fffff8800b8c5c20 00000000770529aa : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiSystemServiceCopyEnd+0x13 (TrapFrame @ fffff880`0b8c5c20)

    0000000000a0f858 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x770529aa

    >[  3,34]  10 e1 fffffa800457b060 00000000 fffff880017711b0-00000000 Success Error Cancel pending

               \Driver\Disk    partmgr!PmReadWriteCompletion

                Args: 00001000 00000000 1b8f0400 00000000

     [  3, 0]  10 e0 fffffa800457bb90 00000000 fffff88001781010-fffffa80045811b0 Success Error Cancel

               \Driver\partmgr    volmgr!VmpReadWriteCompletionRoutine

                Args: e57e1b20 00000000 1b8f0400 00000000

     [  3, 0]   0 e0 fffffa8004581060 00000000 fffff880019b90a8-fffffa8004580bd0 Success Error Cancel

               \Driver\volmgr    fvevol!FvePassThroughCompletion

                Args: 00001000 00000000 e57e1b1f 00000000

     [  3, 0]   0 e0 fffffa8004580a80 00000000 fffff88001879f40-fffffa80081fad00 Success Error Cancel

               \Driver\fvevol    volsnap!VspReadCompletionRoutine

                Args: 00001000 00000000 153f0400 00000000

     [  3, 0]   0 e1 fffffa8004583040 00000000 fffff88001a5cf00-fffffa800bd60ae0 Success Error Cancel pending

               \Driver\volsnap    Ntfs!NtfsMasterIrpAsyncCompletionRoutine

                Args: 00001000 00000000 153f0400 00000000

     [  3, 0]   0  1 fffffa80046ae030 fffffa8005f7c910 00000000-00000000    pending

               \FileSystem\Ntfs

                Args: 00001000 00000000 00034400 00000000

    We have various different file system related drivers (all system non 3rd party).

    ----------------------

    1. AppleCharger.sys is listed and loaded which is the GIGABYTE On/Off Charge driver. See here for details -http://www.gigabyte.us/MicroSite/185/on-off-charge.htm

    Very troublesome software, so please uninstall ASAP!

    2. Remove and replace Kaspersky with Microsoft Security Essentials for temporary troubleshooting purposes as it's likely causing file system conflicts:

    Kaspersky removal -http://support.kaspersky.com/common/service.aspx?el=1464

    MSE -  http://windows.microsoft.com/en-us/windows/security-essentials-download

    Regards,

    Patrick

    0 comments

5 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2014-05-26T01:22:56+00:00

    My pleasure, glad to hear it.

    If and when you are comfortable and feel your issue has been solved, I'd recommend marking any posts of mine that answered your question as answered so this thread no longer shows up as requiring an answer.

    Regards,

    Patrick

    0 comments
  2. Anonymous
    2014-05-26T00:50:40+00:00

    Thanks for your help Patrick. PC is much much better.

    0 comments
  3. Anonymous
    2014-05-21T01:19:43+00:00

    Thanks again for your help. Here's the memory.dmp

    https://onedrive.live.com/redir?resid=4F08C16C7A7DD6CB%21108

    0 comments
  4. Anonymous
    2014-05-21T00:12:16+00:00

    Hi,

    1st parameter = 0x4, which implies that a power IRP has failed to synchronize with the PnP Manager. With this said, we'll need a kernel-dump to properly debug this type of bug check as not information lies within the minidump.

    Kernel-dumps are located at C:\Windows and named MEMORY.DMP. If there is nothing there, you may need to enable generation of them - http://msdn.microsoft.com/en-us/library/windows/hardware/ff540128%28v=vs.85%29.aspx

    Regards,

    Patrick

    0 comments