Question
3161 views

Many BSOD's caused by: ntoskrnl.exe (nt+0x14DCA0)

Von Gold asked on
I have faced a BSOD for days when waking the laptop up from sleep, and then it takes 15 minutes to start up. Refreshing and resetting do not solve the problem. Here's my computer info:

windows version: Windows 8 , 6.2, build: 9200
windows dir: C:\Windows
Hardware: S500CA, ASUSTeK COMPUTER INC.
CPU: GenuineIntel Intel(R) Core(TM) i5-3317U CPU @ 1.70GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 12765052928 total
VM: 2147352576, free: 1924603904

The ntoskernl.exe below is by far the most frequently reported cause of BSOD:

On Tue 1/21/2014 3:10:37 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012114-271484-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DCA0)
Bugcheck code: 0x9F (0x3, 0xFFFFE000007CF880, 0xFFFFD0002052A840, 0xFFFFE0000A67F250)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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.

Occasionally it's caused by:


crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x9F (0x3, 0xFFFFE00000FAF060, 0xFFFFD00020723840, 0xFFFFCF81790D0D30)
Error: DRIVER_POWER_STATE_FAILURE

And only once:
On Mon 1/20/2014 8:25:59 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012014-273609-01.dmp
This was probably caused by the following module: iastora.sys (iaStorA+0x2B8E58)
Bugcheck code: 0x9F (0x3, 0xFFFFE000010C0060, 0xFFFFD0002052A840, 0xFFFFE000033C2550)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\Windows\system32\drivers\iastora.sys
product: Intel Rapid Storage Technology driver
company: Intel Corporation
description: Intel Rapid Storage Technology driver - x64
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.


I've done all kinds of command prompts like scannow and chkdsk /F , etc. but this doesn't solve the problem. I'd really appreciate any help!

Thank you,

Von
8 people had this question

Abuse history


The answered status icon Answer
Patrick Barker replied on

Not a problem, thanks!

All of the attached DMP files are of the DRIVER_POWER_STATE_FAILURE (9f) bug check.

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

If we run an !irp on the 4th parameter of the bug check (blocked IRP address), we get the following:

>[ 16, 2]   0 e1 ffffe000010ee050 00000000 fffff802c7115d80-ffffe00000f26540 Success Error Cancel pending
          Unable to load image \SystemRoot\System32\drivers\iaStorA.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for iaStorA.sys
*** ERROR: Module load completed but symbols could not be loaded for iaStorA.sys
 \Driver\iaStorA    nt!PopRequestCompletion


^^ Intel RST (Rapid Storage Technology) driver.

If we run an lmvm on yours:

1: kd> lmvm iaStorA
start             end                 module name
fffff800`0082c000 fffff800`00af7000   iaStorA  T (no symbols)          
    Loaded symbol image file: iaStorA.sys
    Image path: \SystemRoot\System32\drivers\iaStorA.sys
    Image name: iaStorA.sys
    Timestamp:        Sat Sep 01 21:01:24 2012


^^ Dated ~2012, when the latest from Asus' website is - 2013.01.30.

Update ASAP - http://www.asus.com/us/Notebooks_Ultrabooks/ASUS_VivoBook_S500CA/#support

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

If you're still crashing after the above...

1. AiCharger.sys is listed and loaded which is the Asus Charger driver, it's very known to cause BSOD's. Please remove any Asus software you have installed such as the Asus AI Suite, etc.

2.
Remove and replace Norton with Windows 8's built-in Windows Defender for temporary troubleshooting purposes:

Norton removal - https://support.norton.com/sp/en/us/home/current/solutions/kb20080710133834EN_EndUserProfile_en_us;jsessionid=841A6D40BA6872C47697C6C6B19C8E11.4?entsrc=redirect_pubweb&pvid=f-home

Windows Defender (how to turn on after removal) - http://www.eightforums.com/tutorials/21962-windows-defender-turn-off-windows-8-a.html

Regards,

Patrick
Debugger/Reverse Engineer.
1 person found this helpful

Abuse history


progress