BSOD when laptop lid is closed, ntkrnlpa.exe error

[davidsmith82]

Beginning on March 26, 2015 almost every time I close my laptop lid, my machine doesn't enter sleep mode properly, and as a result, it shuts down with a BSOD error that I find when I start the machine again.

I have tried putting the machine into Sleep from the Start > Shutdown menu, and it still fails to enter sleep mode properly.

I downloaded and installed BlueScreenView, and I found that I am encountering the same errors pretty consistently. I have one error on 4/1/2015 that was related to the Wireless card, and some errors prior to 3/26 related to software that I have since removed. All remaining dumps since 3/26 have a bug check string of DRIVER_POWER_STATE_FAILURE caused by driver ntkrnlpa.exe

I have attached the DM Log Collector zip file from my system.

 

[Arc]

Do two things.

First, download and install Intel® PROSet/Wireless Software and Drivers for Windows 7.

Second, Free up the startup. Windows does not need any other program to auto start with it, but the auto start programs often conflicts and causes various problems including BSODs.

1. Click on the Start button
2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
3. Select the “Startup” tab.
4. Deselect all items other than the antivirus and the touchpad driver, SynTPEnh.
5. Apply > OK
6. Accept then restart.

Report us for any further BSOD.

_____________________________________________

>[ 16, 2]   0  0 86730028 00000000 00000000-00000000    
          Unable to load image \SystemRoot\system32\DRIVERS\NETwsn01.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for NETwsn01.sys
*** ERROR: Module load completed but symbols could not be loaded for NETwsn01.sys
 \Driver\NETwNs32
            Args: 00014400 00000001 00000004 00000002
 [ 16, 2]   0 e1 8665e828 00000000 00000000-00000000    pending
           \Driver\vwifibus
            Args: 00014400 00000001 00000004 00000002

 

[davidsmith82]

Arc,

Thanks for the reply. So far, so good. I will hold on for another day or two before I mark this as solved.

Cheers,
David

 

[davidsmith82]

So, my machine got another BSOD after nearly 2 weeks of normal operation. I waited much longer than I intended to for marking this thread as solved, because despite the lack of BSOD, my machine was operating very slowly.

Attached is the latest DM Log Collector File.

 

[Arc]

You cannot blame the computer for it. It is you only who is forcing the computer to run 22 items always in the background.

Free up the startup. Windows does not need any other program to auto start with it, but the auto start programs often conflicts and causes various problems including BSODs.

1. Click on the Start button
2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
3. Select the “Startup” tab.
4. Deselect all items other than the antivirus and the touchpad driver, SynTPEnh.
5. Apply > OK
6. Accept then restart.

Report us for any further issue.