Driver Power State Failure, ntoskrnl.exe?

Welcome to SevenForums.

Here's an output of your recent BSOD dump file:

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa800e3c6a10, fffff80000b9c3d8, fffffa800ed0fe10}

Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : pci.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 (usually 10 minutes).
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa800e3c6a10, Physical Device Object of the stack
Arg3: fffff80000b9c3d8, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack
Arg4: fffffa800ed0fe10, The blocked IRP

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


DRVPOWERSTATE_SUBCODE:  3

IMAGE_NAME:  pci.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7928f

MODULE_NAME: pci

FAULTING_MODULE: fffff88000fad000 pci

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

TAG_NOT_DEFINED_c000000f:  FFFFF80000BA2FB0

STACK_TEXT:  
fffff800`00b9c388 fffff800`031016d2 : 00000000`0000009f 00000000`00000003 fffffa80`0e3c6a10 fffff800`00b9c3d8 : nt!KeBugCheckEx
fffff800`00b9c390 fffff800`030a1c3c : fffff800`00b9c4c0 fffff800`00b9c4c0 00000000`00000000 00000000`00000002 : nt! ?? ::FNODOBFM::`string'+0x33ac0
fffff800`00b9c430 fffff800`030a1ad6 : fffffa80`10cf9168 fffffa80`10cf9168 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
fffff800`00b9c4a0 fffff800`030a19be : 00000014`236bd848 fffff800`00b9cb18 00000000`000875ca fffff800`0320dbc8 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9caf0 fffff800`030a17a7 : 00000003`ebc4c1c3 00000003`000875ca 00000003`ebc4c114 00000000`000000ca : nt!KiTimerExpiration+0x1be
fffff800`00b9cb90 fffff800`0308ecca : fffff800`03209e80 fffff800`03217cc0 00000000`00000002 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`00b9cc40 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cc00 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0x9F_3_ACPI_IMAGE_pci.sys

BUCKET_ID:  X64_0x9F_3_ACPI_IMAGE_pci.sys

Followup: MachineOwner
---------

0: kd> !irp fffffa800ed0fe10
Irp is active with 4 stacks 2 is current (= 0xfffffa800ed0ff28)
 No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  
     cmd  flg cl Device   File     Completion-Context
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
>[ 16, 2]   0 e1 fffffa800e3bb9d0 00000000 fffff8800f29b778-fffffa8010bb4850 Success Error Cancel pending
	       \Driver\ACPI	nvlddmkm
			Args: 00000000 00000001 00000001 00000000
 [ 16, 2]   0 e1 fffffa800f651480 00000000 00000000-00000000    pending
	       \Driver\nvlddmkm
			Args: 00000000 00000001 00000001 00000000
 [  0, 0]   0  0 00000000 00000000 00000000-fffffa80118963c0    

			Args: 00000000 00000000 00000000 00000000
0: kd> lmvm nvlddmkm
start             end                 module name
fffff880`0f205000 fffff880`0fe75780   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Thu Mar 10 04:41:51 2011 (4D78022F)
    CheckSum:         00C7FA55
    ImageSize:        00C70780
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

It looks as if old Nvidia drivers are causing the BSOD, but from your msinfo file I see this:

Code:

Driver	c:\windows\system32\drivers\nvlddmkm.sys (8.17.12.6764, 12.45 MB (13,050,344 bytes), 1/9/2013 4:44 PM)

Driver version from 2013, which means latest drivers might have been installed?

Click on the Start ► Control Panel ► Programs ► Uninstall a program ► Uninstall everything related to "NVIDIA" and reboot the system. Delete remnants of its drivers/older drivers using Driver Sweeper.

Tutorial here:

Drivers - Clean Left over Files after Uninstalling

Now install the drivers linked on this Nvidia link:

• NVIDIA DRIVERS 306.23WHQL

Video Card - Stress Test with Furmark

• Video Card - Stress Test with Furmark

Monitor your temps with Speccy during this test

• Speccy - System Information - Free Download

   Warning

Video Card Stress Test with Furmark can damage GPU if temperatures are not taken care of.

Video memory test (for 20 passes)

• |MG| Video Memory Stress Test 1.7.116 Download

Clean up some factory bloatware:

• Clean Up Factory Bloatware

Also..what security app do you use? KIS? Norton? McAfee?

Microsoft Security Essentials.

Recommended from a strict BSOD perspective, compatibility & stability compared to other antiviruses/internet security software. It is free and lightweight:-

• Microsoft Security Essentials - Free Antivirus for Windows
  
  • Malwarebytes : Malwarebytes Anti-Malware removes malware including viruses, spyware, worms and trojans, plus it protects your computer
    
    • Good and Free system security combination.
    • How to Scan Your Computer With Multiple Antivirus Programs - How-To Geek
    
    
  
  

   Warning

Do not start the free trial of Malware Bytes; remember to deselect that option when prompted.

Run a full scan with both (separately) once downloaded, installed and updated.

Perform a System File Check:

1. Click on the start
2. Type CMD on Search
3. Left click and Run as Administrator
4. Type SFC /scannow

Full tutorial here:

• SFC /SCANNOW Command - System File Checker

Reduce items at start-up. Nothing except anti-virus is required plus improves the time for logging in windows.

• Startup Programs - Change
• Troubleshoot Application Conflicts by Performing a Clean Startup

Disk Check on your hard drive for file system errors and bad sectors on it:

• Disk Check

Let us know the results.

Okay.
Let us know when you get a bsod.

Execute the SF diag tool for one more time please.

Go to your laptop maker's support page and get the graphics driver from there. Many, most times, laptops have special brand/model specific drivers. If they have a driver detection feature, use that.

@Palladion: Please provide information in the system specs of your forum profile - use the easy system specs link in my signature below so you don't have to look for th informtion and type it in. Manually update the system mfgr with model information - click on the My System Specs link in any post to get an idea.

Please also provide either a System information report or PUBLISH a Speccy report (pasting the url in a new post on this thread).

Trying to solve a technical issue witout hard information is like talking to a mechanic and saying "I have this car.... it won't start". Lots of guesses can be made - dead battery, no fuel, no battery...

Thanks

Bill
.