Share via

Blue Screen During Sleep Mode

Anonymous
2010-09-15T02:17:55+00:00

Lately I've been having a problem where my laptop gets the blue screen while it is in sleep or hibernation mode. It has never happened while I have actually been using the computer.

I ran BugCheck Analysis on the Crash Dumps and came up with the following results:

the crash that occurred on 8/30/10 was probably caused by iastor.sys

the crash that occurred on 9/6/10 was probably caused by pci.sys

the crash that occurred on 9/14/10 was probably caused by pci.sys

I can post the actual debugging results as well as the critical error messages if needed. What needs to be done with these files in order to fix my blue screen problem? I should point out that I'm not extremely computer savvy and that I consider getting this far an accomplishment in and of itself, so don't hesitate to talk down to me.

Windows for home | Previous Windows versions | Windows update

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 No comments

Answer accepted by question author

Anonymous
2010-09-15T18:53:15+00:00

Hi,

Good idea would be to update all major drivers, BIOS, and low level chipset drives. Doing that

would likely correct the issues the system has now and help prevent others in the future. Check

with your system maker (motherboard maker for custom systems) and the chipset maker. You

can also determine the chipset maker and model by using Start - type in the Search box ->

System Information         find at top and double click on it.

Are you using any Roxio or Nero programs? These have been known to cause this problem even

if they were working well for a long period of time. If so check with their support.

==============================================================

Check this thread for information on using BlueScreenView, MyEventViewer, and other methods to

troubleshoot BlueScreens - top 3 replies (+1 other). There is also information on updating drivers.

http://social.answers.microsoft.com/Forums/en-US/w7repair/thread/c675b7b8-795f-474d-a1c4-6b77b3fcd990


More troubleshooting help though the key is updating as mentioned above.

**References to Vista also apply to Windows 7.**This "could" be a power supply problem though it is not the most common cause.

9f is likely a driver issue. Antivirus/antispware/security programs can also cause these issues.

Have you added devices lately or updated drivers - be sure to check in Windows Updates to see

if a driver was updated prior to this occurring. This could also be caused by a loose card or cable

and even a weak power supply.

That error means a driver is not handling the power state properly. Check in Control Panel - Device

Manager to be sure major drivers are not shut off during sleep - double click Display Adapter - NIC

and WIFI - Sound and others - Power Management tab - uncheck Allow computer to turn off power.

Maybe only one has an issue.

Start - type in Search box - MSCONFIG  find at top - Right Click - RUN AS ADMINGeneral Tab - check Diagnostic Start  - APPLY / OK  -  REBOOTTry it now. If it still blue screens think Video Driver. If not think NIC, Wifi, Sound, or......(and it still could be video interacting with something else). See next message for mygeneric driver update methods.

BCCode: 9F  0x0000009F  <-- read thishttp://www.faultwire.com/solutions-fatal\_error/DRIVER-POWER-STATE-FAILURE-0x0000009F-\*1167.html?order=date

See the troubleshooter links posted above for methods to update drivers.

Hope this helps.


Rob Brown - MS MVP - Windows Desktop Experience : Bicycle - Mark Twain said it right.

Was this answer helpful?

1 person found this answer helpful.
0 comments No comments

Answer accepted by question author

Anonymous
2010-09-16T00:11:30+00:00

Thanks for your help everyone. I've updated the BIOS and drivers. Hopefully there won't be any more problems. If there are, I'll post back here.

Was this answer helpful?

0 comments No comments

11 additional answers

Sort by: Most helpful
  1. Anonymous
    2010-09-15T02:46:59+00:00

    Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64

    Copyright (c) Microsoft Corporation. All rights reserved.

    Loading Dump File [C:\Users\Matt\Desktop\090610-40513-01.dmp]

    Mini Kernel Dump File: Only registers and stack trace are available

    DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff800`04508500?

    Symbol search path is: srv*

    Executable search path is:

    Windows 7 Kernel Version 7600 MP (2 procs) Free x64

    Product: WinNt, suite: TerminalServer SingleUserTS Personal

    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621

    Machine Name:

    Kernel base = 0xfffff80003009000 PsLoadedModuleList = 0xfffff80003246e50

    Debug session time: Mon Sep  6 10:30:59.463 2010 (UTC - 5:00)

    System Uptime: 0 days 22:45:51.378

    Loading Kernel Symbols

    ...............................................................

    ................................................................

    .................................................

    Loading User Symbols

    Loading unloaded module list

    ..............................

    *******************************************************************************

    *                                                                             *

    *                        Bugcheck Analysis                                    *

    *                                                                             *

    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 9F, {3, fffffa800468ba20, fffff80004508518, fffffa80080a5650}

    Probably caused by : pci.sys

    Followup: MachineOwner


    0: kd> !analyze -v

    *******************************************************************************

    *                                                                             *

    *                        Bugcheck Analysis                                    *

    *                                                                             *

    *******************************************************************************

    DRIVER_POWER_STATE_FAILURE (9f)

    A driver is causing an inconsistent power state.

    Arguments:

    Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time

    Arg2: fffffa800468ba20, Physical Device Object of the stack

    Arg3: fffff80004508518, Functional Device Object of the stack

    Arg4: fffffa80080a5650, The blocked IRP

    Debugging Details:


    DRVPOWERSTATE_SUBCODE:  3

    IMAGE_NAME:  pci.sys

    DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc117

    MODULE_NAME: pci

    FAULTING_MODULE: fffff88000fa2000 pci

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

    BUGCHECK_STR:  0x9F

    PROCESS_NAME:  System

    CURRENT_IRQL:  2

    STACK_TEXT:  

    fffff800045084c8 fffff800030e8273 : 000000000000009f 0000000000000003 fffffa800468ba20 fffff80004508518 : nt!KeBugCheckEx

    fffff800045084d0 fffff8000308529e : fffff80004508630 fffff80004508630 0000000000000001 0000000000000000 : nt! ?? ::FNODOBFM::`string'+0x292b0

    fffff80004508570 fffff80003084dd6 : fffffa8005b27a48 fffffa8005b27a48 0000000000000000 0000000000000000 : nt!KiProcessTimerDpcTable+0x66

    fffff800045085e0 fffff800030854be : 000000beced3f4a1 fffff80004508c58 000000000050288b fffff800031f73e8 : nt!KiProcessExpiredTimerList+0xc6

    fffff80004508c30 fffff80003084cb7 : 000000282d7edac4 000000280050288b 000000282d7eda87 000000000000008b : nt!KiTimerExpiration+0x1be

    fffff80004508cd0 fffff80003081eea : fffff800031f3e80 fffff80003201c40 0000000000000002 fffff88000000000 : nt!KiRetireDpcList+0x277

    fffff80004508d80 0000000000000000 : fffff80004509000 fffff80004503000 fffff80004508d40 0000000000000000 : nt!KiIdleLoop+0x5a

    STACK_COMMAND:  kb

    FOLLOWUP_NAME:  MachineOwner

    FAILURE_BUCKET_ID:  X64_0x9F_3_NETw5s64_IMAGE_pci.sys

    BUCKET_ID:  X64_0x9F_3_NETw5s64_IMAGE_pci.sys

    Followup: MachineOwner


    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2010-09-15T02:45:55+00:00

    Is this what you're looking for?

    Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64

    Copyright (c) Microsoft Corporation. All rights reserved.

    Loading Dump File [C:\Users\Matt\Desktop\083010-69872-01.dmp]

    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: srv*

    Executable search path is:

    Windows 7 Kernel Version 7600 MP (2 procs) Free x64

    Product: WinNt, suite: TerminalServer SingleUserTS Personal

    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621

    Machine Name:

    Kernel base = 0xfffff80003055000 PsLoadedModuleList = 0xfffff80003292e50

    Debug session time: Mon Aug 30 19:37:48.531 2010 (UTC - 5:00)

    System Uptime: 1 days 7:30:10.279

    Loading Kernel Symbols

    ...............................................................

    ................................................................

    ...............................................

    Loading User Symbols

    Loading unloaded module list

    ..............

    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

    *******************************************************************************

    *                                                                             *

    *                        Bugcheck Analysis                                    *

    *                                                                             *

    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 9088, {fffff880085528c0, fffff880085528c4, fffff880085528d0, fffff880085528d4}

    Probably caused by : iaStor.sys ( iaStor+4b41e )

    Followup: MachineOwner


    0: kd> !analyze -v

    *******************************************************************************

    *                                                                             *

    *                        Bugcheck Analysis                                    *

    *                                                                             *

    *******************************************************************************

    Unknown bugcheck code (9088)

    Unknown bugcheck description

    Arguments:

    Arg1: fffff880085528c0

    Arg2: fffff880085528c4

    Arg3: fffff880085528d0

    Arg4: fffff880085528d4

    Debugging Details:


    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

    BUGCHECK_STR:  0x9088

    PROCESS_NAME:  IAANTmon.exe

    CURRENT_IRQL:  0

    LAST_CONTROL_TRANSFER:  from fffff8800112141e to fffff800030c5740

    STACK_TEXT: 

    fffff88008552858 fffff8800112141e : 0000000000009088 fffff880085528c0 fffff880085528c4 fffff880085528d0 : nt!KeBugCheckEx

    fffff88008552860 0000000000009088 : fffff880085528c0 fffff880085528c4 fffff880085528d0 fffff880085528d4 : iaStor+0x4b41e

    fffff88008552868 fffff880085528c0 : fffff880085528c4 fffff880085528d0 fffff880085528d4 0000000000000000 : 0x9088

    fffff88008552870 fffff880085528c4 : fffff880085528d0 fffff880085528d4 0000000000000000 fffffa8004aac000 : 0xfffff880`085528c0

    fffff88008552878 fffff880085528d0 : fffff880085528d4 0000000000000000 fffffa8004aac000 0000000000000000 : 0xfffff880`085528c4

    fffff88008552880 fffff880085528d4 : 0000000000000000 fffffa8004aac000 0000000000000000 fffffa800a051850 : 0xfffff880`085528d0

    fffff88008552888 0000000000000000 : fffffa8004aac000 0000000000000000 fffffa800a051850 fffffa8007ad3660 : 0xfffff880`085528d4

    STACK_COMMAND:  kb

    FOLLOWUP_IP:

    iaStor+4b41e

    fffff880`0112141e ??              ???

    SYMBOL_STACK_INDEX:  1

    SYMBOL_NAME:  iaStor+4b41e

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: iaStor

    IMAGE_NAME:  iaStor.sys

    DEBUG_FLR_IMAGE_TIMESTAMP:  4a287aa4

    FAILURE_BUCKET_ID:  X64_0x9088_iaStor+4b41e

    BUCKET_ID:  X64_0x9088_iaStor+4b41e

    Followup: MachineOwner


    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2010-09-15T02:31:32+00:00

    Hi,

    We really need the Bug_Check codes.

    Check this thread for information on using BlueScreenView, MyEventViewer, and other methods to

    troubleshoot BlueScreens - top 3 replies (+1 other).

    http://social.answers.microsoft.com/Forums/en-US/w7repair/thread/c675b7b8-795f-474d-a1c4-6b77b3fcd990

    You can use BlueScreenView to paste the BSOD info into a message here.

    VIEW - HTML Report ALL ITEMS    or  Right Click on a BSOD line and select same. Then copy and

    paste the lines in to a message here. Be sure and check the filename section. Also check the time

    in MyEventViewer for other possible information.

    Hope this helps.


    Rob Brown - MS MVP - Windows Desktop Experience : Bicycle - Mark Twain said it right.

    Was this answer helpful?

    0 comments No comments