Windows 10: error 0x9f, ACPI - will BIOS update fix?

Hi @essenbe
Have attached the collector per your request. Hoping there's nothing here and the BIOS update will fix it?
Thanks. *Smile

:)

 

ACPI bios error

Hello,

The issue that you’ve encountered regarding the behavior of your Windows 10
computer may be caused by some configuration or programs that prevent Windows from working properly. To sort out your concern, we suggest that you follow the steps provided in this article on
how
to use Windows Recovery Environment (WinRE) to troubleshoot common startup issues. Once you’re on the page, you may proceed with the steps from the
Summary section, and then complete the process. After completing the steps, you may check if you’re able to use your device properly.

Keep us updated about your concern for additional assistance.

 

ACPI BIOS ERROR

I took my computer to Staples. When they turned it on it came up performing diagnostic then a option to repair. Tech picked October 16th as a restore date. Once finished computer started correctly. He said others had come in after doing updates for 10 with
similar issues. For some reason when I did this at home it would not perform diagnostic. Any way thanks to the community.

 

@simrick, It is hard to tell. You had 3 dump files, all 9F - Driver Power State Failure
2 were
Code: Use !analyze -v to get detailed debugging information. BugCheck 9F, {3, ffffe00192bc5840, fffff80183b71ce0, ffffe0019aff0490} Implicit thread is now ffffe001`9f4da840 *** WARNING: Unable to verify timestamp for nvlddmkm.sys *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys Probably caused by : dxgkrnl.sys ( dxgkrnl!DpiFdoHandleDevicePower+1e4 ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* DRIVER_POWER_STATE_FAILURE (9f) A driver has failed to complete a power IRP within a specific time. Arguments: Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time Arg2: ffffe00192bc5840, Physical Device Object of the stack Arg3: fffff80183b71ce0, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack Arg4: ffffe0019aff0490, The blocked IRP[/quote] The other one was the same but with a different cause listed

Code: Use !analyze -v to get detailed debugging information. BugCheck 9F, {3, ffffe000e0b82060, fffff8039556a990, ffffe000e08a8b40} *** WARNING: Unable to verify timestamp for iaStorA.sys *** ERROR: Module load completed but symbols could not be loaded for iaStorA.sys Probably caused by : iaStorA.sys Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* DRIVER_POWER_STATE_FAILURE (9f) A driver has failed to complete a power IRP within a specific time. Arguments: Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time Arg2: ffffe000e0b82060, Physical Device Object of the stack Arg3: fffff8039556a990, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack Arg4: ffffe000e08a8b40, The blocked IRP Debugging Details:[/quote] I am also seeing errors from Firefox, usually the Flash Player Plugin caused by SS2OSD.dll. I saw several errors naming that .dll. From what I could find, it is used in several games, such as LCPD and Hitman PRO but is sometimes associated with AI Suite. In trying to run down the dumps, it should tell me what the device is but it could not read it. I usually don't post this much code, but...


Code: !devnode ffffe00192ba5d30 DevNode 0xffffe00192ba5d30 for PDO 0xffffe00192bb2060 Parent 0xffffe00192bcdb10 Sibling 0xffffe00192ba5a50 Child 0xffffe00192bc3c70 InterfaceType 0 Bus Number 0 InstancePath is "PCI\VEN_8086&DEV_1901&SUBSYS_86941043&REV_07\3&11583659&0&08" ServiceName is "pci" State = Unknown State (0x0) Previous State = Unknown State (0x0) Flags (0000000000) 0: kd> !devnode ffffe00192ba5a50 DevNode 0xffffe00192ba5a50 for PDO 0xffffe00192bb1060 Parent 0xffffe00192bcdb10 Sibling 0xffffe00192ba4d30 Child 0xffffe00196af1890 InterfaceType 0 Bus Number 0 InstancePath is "PCI\VEN_8086&DEV_A12F&SUBSYS_86941043&REV_31\3&11583659&0&A0" ServiceName is "USBXHCI" State = Unknown State (0x0) Previous State = Unknown State (0x0) Flags (0000000000) 0: kd> !devnode ffffe00196af1890 DevNode 0xffffe00196af1890 for PDO 0xffffe001982313e0 Parent 0xffffe00192ba5a50 Sibling 0000000000 Child 0xffffe00196cb7810 InterfaceType 0 Bus Number 0 InstancePath is "USB\ROOT_HUB30\4&1148bc98&0&0" ServiceName is "USBHUB3" State = Unknown State (0x0) Previous State = Unknown State (0x0) Flags (0000000000)[/quote] Look in Device Manager and see if there are warnings on your USB 3.0 Hubs. Also, do you have anything connected to the USB 3.0 ports such as an external hard drive or something else?

It first named your Graphics card but after digging down a little farther, it named USB 3.0 hubs. The only thing the 2 have in common that I know of is they are both PCIe devices.

Look in BIOS and give me the values of your +12V, +5V and +3.3V. Look at your sata controller and tell me the mode it is set to (IDE, AHCI or Raid) it should be AHCI by default. Look at the boot configuration and note the boot device and configuration. Make sure you write it down, or better, put a USB flash drive in a USB 2.0 port. On any page you can press F12 and it will put a picture of that page on the USB drive. After your BIOS update, go into bios and set Optimized defaults. make sure your sata configuration is what it is set to right now., Make sure your boot configuration and boot devices are set as they are right now. Download and install CPUz (CPU-Z | Softwares | CPUID) Post screenshots of the CPU, Mainboard, Memory and SPD tabs. On the SPD tab, you can select each Dimm Slot from a dropdown list in the upper left of the screen. Just post the Dimm slots populated with ram. The others will be blank.

 

dxgkrnl.sys = graphics. Checking for an update now. Yeah, update from v359.00 to v361.43 from 12-21-2015.

iaStorA.sys = that's definately BIOS related. That's on the top of my TO-DO list.

SS2OSD.dll = No bangs on anything in Device Manager, except the Virtual Adapter, which I disabled myself.

Yes, I have a Seagate ext HDD attached to a USB3 port on the front of the machine.

Re: Values - Do I have to boot into BIOS to get this, or do ASUS provide software to work within Windows?

 

Boot into BIOS and the values are on the main tab or monitor tab. It will show temps and voltages and other stuff. IaStor is Intel's IRST driver. It is their Raid driver but is also the only way to get the Intel AHCI driver, which gives a little better performance than the default Microsoft driver. A lot of people use it, but it causes some people problems, for some reason.

Did you set your Bus speed to 100.5? It shouldn't cause a problem. Was the Seagate external hard drive running when the BSOD occurred? If it was you may want to run Seaools on the external drive. A USB 3.0 error and a sata driver error may have come from the same place. The AI Suite causes some people a lot of problems and it is close to impossible to completely get rid of. Some of the functions are useful, but some can cause problems.

 

will do.

no. I haven't done any changes at all to anything.

yes, it was connected, don't know if it was running.

ok.

 

Left my computer on last night to download W10-1511, and set it to sleep in 1 hour. This morning I looked and computer was off. WhoCrashed shows same error:

Crash dumps are enabled on your computer.

On Wed 12/30/2015 7:31:54 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\123015-20968-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x9F (0x3, 0xFFFFE000944C6060, 0xFFFFF80049F71CE0, 0xFFFFE0009EECA010)
Error: DRIVER_POWER_STATE_FAILURE
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


On Wed 12/30/2015 7:31:54 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x9F (0x3, 0xFFFFE000944C6060, 0xFFFFF80049F71CE0, 0xFFFFE0009EECA010)
Error: DRIVER_POWER_STATE_FAILURE
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


Uploading another collector for you, if you have time. Thanks. Will have to find a good Seatools download now for my external drive.Attachment 56125


EDIT: Every time this happens, I am not around, not doing anything on the computer. Could it be something to do with windows maintenance?

 

it could have something to do with sleep or hibernation. A lot of chipsets since Sandy Bridge have had a problem with sleep.

 

Should I try turning all that off then?

 

Found a good SeaTools for DOS link:
SeaTools | Seagate

 

That seems to be your Graphics card waking up from sleep.
Code: kd> !devnode ffffe000944c7cd0 DevNode 0xffffe000944c7cd0 for PDO 0xffffe000944c6060 Parent 0xffffe0009448bd30 Sibling 0xffffe000944c6d30 Child 0xffffe00099eaa010 InstancePath is "PCI\VEN_10DE&DEV_1401&SUBSYS_39673842&REV_A1\4&2d78ab8f&0&0008" ServiceName is "nvlddmkm" State = DeviceNodeStarted (0x308) Previous State = DeviceNodeEnumerateCompletion (0x30d) StateHistory[12] = DeviceNodeEnumerateCompletion (0x30d) StateHistory[11] = DeviceNodeEnumeratePending (0x30c) StateHistory[10] = DeviceNodeStarted (0x308) StateHistory[09] = DeviceNodeEnumerateCompletion (0x30d) StateHistory[08] = DeviceNodeEnumeratePending (0x30c) StateHistory[07] = DeviceNodeStarted (0x308) StateHistory[06] = DeviceNodeStartPostWork (0x307) StateHistory[05] = DeviceNodeStartCompletion (0x306) StateHistory[04] = DeviceNodeStartPending (0x305) StateHistory[03] = DeviceNodeResourcesAssigned (0x304) StateHistory[02] = DeviceNodeDriversAdded (0x303) StateHistory[01] = DeviceNodeInitialized (0x302) StateHistory[00] = DeviceNodeUninitialized (0x301) StateHistory[19] = Unknown State (0x0) StateHistory[18] = Unknown State (0x0) StateHistory[17] = Unknown State (0x0) StateHistory[16] = Unknown State (0x0) StateHistory[15] = Unknown State (0x0) StateHistory[14] = Unknown State (0x0) StateHistory[13] = Unknown State (0x0) Flags (0x6c0000f0) DNF_ENUMERATED, DNF_IDS_QUERIED, DNF_HAS_BOOT_CONFIG, DNF_BOOT_CONFIG_RESERVED, DNF_NO_LOWER_DEVICE_FILTERS, DNF_NO_LOWER_CLASS_FILTERS, DNF_NO_UPPER_DEVICE_FILTERS, DNF_NO_UPPER_CLASS_FILTERS CapabilityFlags (0x00002000) WakeFromD3[/quote] PCI\VEN_10DE&DEV_1401&SUBSYS_39673842&REV_A1\4&2d78ab8f&0&0008 is the address of your graphics card, when it wakes up from sleep, it appears the drivers do not "wake up with it". Notice the bottom says "Wake from D3" and says no Upper Class or Lower class filters (I intrepret that as drivers). This is not uncommon and I am not sure if it is an OS problem or a BIOS problem. Try to set the monitors to shut off when you want them to but the hard drives never to sleep in the advanced power options. Try that and see if the BSODs stop.

 

Okay sleep and hibernation are now off. Geesh! LOL

 

Running the long generic test on the ext hdd now.

 

OK, good. Anymore BSODs?. If you get another, upload the zip file. Did you delete the hyberfile when turning Hibernation off? To delete it, open an elevated command prompt and run powercfg -h off . That should turn it off as well as delete the hyberfile from your hard drive and give you 16 GB more free space on your hard drive.