afraid to go to sleep - "no BSOD" STOP 0x0000009f

[Steffi]

When going into standby sooner or later my laptop will crash. Sometimes it runs for a few days, then again it crashes several times a day. Only when going into standby. The only way I know it is going to crash is when it doesn't shut off within 20s. The screens go blank and the laptop stays on and eventually shuts down with a crash. I never saw the BSOD and I don't know how long it actually takes, but more then 5min anyways.

I have already tried a lot, updated whatever could be involved. The error of a STOP 9f when going into standby is found often on the net but no solution has worked for me.

The laptop is a few months old, Win7U 64bit was cleanly installed by me. I have done memory testing and ran the system with 8GB RAM instead of 16 for a while until I got the same crashes.

attached are the last 4 minidumps.

here's the Windbg output:

[COLOR=navy][SIZE=3]*******************************************************************************
*                                                                             *
*                        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: fffffa800dbc2c20, Physical Device Object of the stack
Arg3: fffff80000b8c518, Functional Device Object of the stack
Arg4: fffffa80115ba540, The blocked IRP

Debugging Details:
------------------


DRVPOWERSTATE_SUBCODE:  3

IRP_ADDRESS:  fffffa80115ba540

DEVICE_OBJECT: fffffa800dbc2c20

DRIVER_OBJECT: fffffa800cd36060

IMAGE_NAME:  ACPI.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4e66db16

MODULE_NAME: ACPI

FAULTING_MODULE: fffff88000e00000 ACPI

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002d35cd2 to fffff80002cc7c40

STACK_TEXT:  
fffff800`00b8c4c8 fffff800`02d35cd2 : 00000000`0000009f 00000000`00000003 fffffa80`0dbc2c20 fffff800`00b8c518 : nt!KeBugCheckEx
fffff800`00b8c4d0 fffff800`02cd35fc : fffff800`00b8c600 fffff800`00b8c600 00000000`00000000 00000000`00000002 : nt! ?? ::FNODOBFM::`string'+0x34a90
fffff800`00b8c570 fffff800`02cd3496 : fffffa80`0ebc4c10 00000000`000aa9b0 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
fffff800`00b8c5e0 fffff800`02cd337e : 00000019`61b7496a fffff800`00b8cc58 00000000`000aa9b0 fffff800`02e41888 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b8cc30 fffff800`02cd3167 : 00000004`4932dac2 00000004`000aa9b0 00000004`4932da8d 00000000`000000b0 : nt!KiTimerExpiration+0x1be
fffff800`00b8ccd0 fffff800`02cbf96a : fffff800`02e3de80 fffff800`02e4bcc0 00000000`00000001 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`00b8cd80 00000000`00000000 : fffff800`00b8d000 fffff800`00b87000 fffff800`00b8cd40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0x9F_IMAGE_ACPI.sys

BUCKET_ID:  X64_0x9F_IMAGE_ACPI.sys

Followup: MachineOwner
[/SIZE][/COLOR]

it blames ACPI.SYS and I found and installed a hotfix for ACPI.sys (for a different problem though) and it didn't help.

 

[writhziden]

The first thing to check is whether the hard disk is physically connected to the motherboard properly. To do so:

• Shut down and turn off the computer
• Remove the AC Adapter
• Remove the battery
• Hold down the power button for 15-30 seconds to close the circuit and drain any residual power
• Remove the panel on the underside of the laptop where the hard disk is housed
• Remove and re-insert the hard disk by sliding it away from the connector and then gently but firmly pressing it back into the connector (no screws should need to be removed to do this step)
• Replace the panel on the underside of the laptop to cover the hard disk
• Replace the battery
• Replace the AC Adapter
• Turn on the computer and see how it responds

Post back once these steps have been implemented whether the system is stable. Sometimes these crashes can occur due to a loose connection.


If the above does not resolve the problem, check for conflicts with services or startup programs: http://www.sevenforums.com/tutorial...ation-conflicts-performing-clean-startup.html


If you still have problems, check drivers by letting Windows stress them and let us analyze crashes during the drivers stress test.

• 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. In Windows 7:

  • Click the Start Menu
  • Type verifier in Search programs and files (do not hit enter)
  • Right click verifier and click Run as administrator
  • Put a tick in Create custom settings (for code developers) and click next
  • Put a tick in Select individual settings from a full list and click next
  • Set up the individual settings as in the image and click next
    View attachment 210491
  • Put a tick in Select driver names from a list
  • Put a tick next to all non-Microsoft drivers.
  • Click Finish.
  • Restart your computer.

  
  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 http://www.sevenforums.com/tutorials/700-system-restore.html 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.​
  The idea with Verifier is to cause the system to crash, so do the things you normally do that cause crashes. After you have a few crashes, upload the crash reports for us to take a look and try to find patterns.
  
  When you are ready to disable Verifier: Start Menu -> All Programs -> Accessories -> Right click Command Prompt -> Run as administrator -> Type the following command and then Enter:
  verifier /reset​
  -> Restart your computer.

 

[Steffi]

I'm nowhere near a solution. I took quite a while but my mainboard and graphics card was replaced with a new one.
I have also changed my power supply.
On top I ran driver verifier for 3 days allthewhile working with the machine. Other than some sound distortion no crashes.
I installed a second Windows and used it for a while, had a crash when going into standby - but no memory dump was written.

Can somebody please look at the dumps? The info must be there. I saved all my full dumps, too. I'll soon open another case with HP. But it is so annoying, so much time wasted. I never had such a crappy system.

 

[writhziden]

The crashes all indicate a driver issue. ACPI.sys is blamed; Advanced Configuration and Power Interface is part of Windows, and since it does not cause crashes when Windows is running properly, this indicates you likely have either a bad Windows installation or a hardware problem...

• Check Windows for corruption. Run http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html up to three times to fix all errors with a restart in between each. Post back if it continues to show errors after a fourth run or if the first run comes back with no integrity violations. Use OPTION THREE of http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html to provide us with the sfcdetails.txt file if errors occur.

With Verifier enabled, you do not get any crashes during shut down, sleep, or hibernate?


I have seen ACPI.sys blamed due to graphics card drivers. It could also be a PCI card that has faulty drivers or faulty hardware. I wonder about network adapters.

Have you re-installed Windows since the hardware was replaced?

 

[Steffi]

The "corrupted" files that SFC found need to be that way. The deviation is due to changed settings inside them. Obviously they are not a problem for those crashes.

I'm pretty sure it's the graphics driver. Nvidia has produced the biggest crap imaginable in the past years. On my search for solutions I found countless issues with those drivers that Nvidia is not willing or able to fix or needed years to do so. I have had many of those issues myself and updated drivers helped but introduced new bugs. I have 3 other extremly annoying issues and am seriously considering changing my graphics card to ATI. But I would loose CUDA power....

My main problem, however, doesn't seem to be a common one, plus it's only 20% repeatable. I hope to find a workaround or better proof to go at the companies involved.

And I totally forgot to go into standby/hibernate during the verifier run because I left the machine running continuously. I will catch up on that. But will the dump likely be different and more helpful?

 

[writhziden]

It may be different, which would be helpful. I have had no issues with either nVidia or ATI cards, and I have seen countless cases with problems due to each. It usually boils down to software being installed that conflicts or bad hardware and is rarely due to nVidia or ATI drivers.

That being said, that does not mean bad drivers do not happen. nVidia had a bad batch for a few weeks about six months ago, and ATI's current batch has caused issues on a number of systems. I experienced some of the ATI problems, but thankfully, they were resolved with a restart of my computer and I haven't had many problems recently other than the occasional hiccup that may or may not be related. I have not yet checked my error logs to see if the problem is other software or the ATI graphics driver since it happens once in a blue moon.

The changed settings you speak of that are found by the sfc /scannow do make me wonder if your modifications are causing issues. Are they necessary? Can you see if removing those modifications resolves your crashes? Those are some pretty important system files that are being changed and could be causing problems related to your drivers and power management features.

 

[Steffi]

Are you talking about the msc-files? They are just the control panels for services etc. I just saved them with a bigger window size and in standard view - MS chose the most unusable settings possible. None of them are open or running. In XP it was much easier to save the settings.

 

[writhziden]

Ah, sorry, I didn't look carefully at the extensions. I am not on my usual debugging system, and my interface to that system is down due to my home internet having issues.

You are right; these are all just visual based files and nothing to worry about.