BSOD due to ntoskrnl.exe

elisssx

Reputable
Jan 10, 2016
2
0
4,510
Hi all,
I keep having trouble with figuring out how to fix my continuously occuring BSODs. I've searched almost every forum and possible answer but still, the BSODs keep happening. I'm not really computer smart, so that may also be a problem. I have not overclocked my laptop.
The occurances are random, but the cause stated in the .dmp files are the same. I've tried using Driver Verifier but that hasn't made me any wiser. I have also tried using the command prompt with The command SFC /SCANNOW but that doesn't seem to find anything.
I'm starting to get really hopeless, so I'm happy with any kind of help I can get. Also sorry in advance, but as mentioned earlier I'm not really computer smart so you may have to have some patience.
My laptop qualifications:
windows version: Windows 8.1 , 6.3, build: 9600
windows dir: C:\Windows
Hardware: N751JX, ASUSTeK COMPUTER INC.
CPU: GenuineIntel Intel(R) Core(TM) i7-4720HQ CPU @ 2.60GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 8473542656 total

Link to my dump files, the driver view and the system information file.:
https://onedrive.live.com/redir?resid=5EA8014B77F04705%21945

On Sun 10-1-2016 18:05:04 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011016-32671-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E8A0)
Bugcheck code: 0x9F (0x3, 0xFFFFCF801A71A880, 0xFFFFD000F8A6A960, 0xFFFFCF801AA6ACA0)
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.


On Sun 10-1-2016 18:05:04 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt+0x14E8A0)
Bugcheck code: 0x9F (0x3, 0xFFFFCF801A71A880, 0xFFFFD000F8A6A960, 0xFFFFCF801AA6ACA0)
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 Tue 5-1-2016 16:14:44 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010516-27062-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E8A0)
Bugcheck code: 0x9F (0x3, 0xFFFFE0009E27B060, 0xFFFFF8016AFCB960, 0xFFFFE000A22A5B20)
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.



On Tue 5-1-2016 15:39:10 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010516-27484-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E8A0)
Bugcheck code: 0x9F (0x3, 0xFFFFE0007B054880, 0xFFFFD000AC786960, 0xFFFFE0007B0256A0)
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.



On Sat 2-1-2016 22:46:21 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010216-23734-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E8A0)
Bugcheck code: 0x9F (0x3, 0xFFFFE000599EB6A0, 0xFFFFD0011513E960, 0xFFFFE0005C3FC010)
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.
 
Solution
it is a usb utility installed by asus, you might just be able to search your drive for the file and rename it so it does not load. (depends on how it was installed, if it is in the hidden driverstore, the system will just put the file back on the next bootup)
you can also remove the driver package using this method:
https://technet.microsoft.com/en-us/library/cc730875.aspx

or maybe look for a update for your motherboard under the asus utility sections.
This driver does seem to be involved with a lot of USB problems though.

if the updates below do not help, then you have to change the memory dump type from minidump to a kernel dump. The debug info for power problems is stripped out of minidumps.
how to change the memory dump type: (select kernel memory dump)
https://www.sophos.com/en-us/support/knowledgebase/111474.aspx
note: kernel memory dumps are stored in a different file location and name. c:\windows\memory.dmp


------------
basically, your error indicates that a hardware device did not correctly respond to a power request in a reasonable time. This will be a bug in the BIOS, the driver for the device or the hardware in the device that did not respond. It looks like the bios is 5 versions old, you should pick up the updates and install all of the current versions of the drivers.

be sure to update the utilities also (i am thinking of this one)
ASUS USB Charger Plus
because it can mess up devices plugged into the USB ports.
And it looks like AiCharger.sys is having some problems.
it is a custom driver used to override the maximum current that a USB port can provide. It is used to charge apple devices on a PC.
you can uninstall it if you don't charge apple devices with your PC USB ports.






https://www.asus.com/Notebooks/N751JX/HelpDesk_Download/
update the BIOS to the current version.

your version:
BIOS Version N751JX.202
BIOS Starting Address Segment f000
BIOS Release Date 01/12/2015
Manufacturer ASUSTeK COMPUTER INC.
Product Name N751JX
Version 1.0
SKUNumber ASUS-NotebookSKU
Chassis Type Notebook
Processor Version Intel(R) Core(TM) i7-4720HQ CPU @ 2.60GHz
Processor Voltage 8ch - 1.2V
External Clock 100MHz
Max Speed 3800MHz
Current Speed 2600MHz


 
Okay, so I updated the BIOS and the other utilities, thank you! The only thing left is deleting the Aicharger.sys as you said, but I can't find it anywhere. I tried doing it the regular way by trying to uninstall it via the control panel but it isn't in the list. Also tried looking in programfiles/asus but it isn't there as well.

Have you got any idea where I can find it?
 
it is a usb utility installed by asus, you might just be able to search your drive for the file and rename it so it does not load. (depends on how it was installed, if it is in the hidden driverstore, the system will just put the file back on the next bootup)
you can also remove the driver package using this method:
https://technet.microsoft.com/en-us/library/cc730875.aspx

or maybe look for a update for your motherboard under the asus utility sections.
This driver does seem to be involved with a lot of USB problems though.



 
Solution