BSOD After Replacing Battery on Laptop, Power Driver Failure

Hello and welcome to Seven Forums.

Please upload your msinfo32.nfo file. To get this: Start Menu -> Type msinfo32 into the Search programs and files box -> When it opens, go to File, Save -> Save as msinfo32.nfo and save in a place you will remember -> Let it finish the process of gathering and saving the system info -> Right click the .nfo file, click send to compressed (zipped) folder -> Upload the .zip file here.

Please upload your msinfo32.txt file. To get this: Start Menu -> Type msinfo32 into the Search programs and files box -> When it opens, go to File, Export -> Save as msinfo32.txt and save in a place you will remember -> Let it finish the process of gathering and saving the system info -> Right click the .txt file, click send to compressed (zipped) folder -> Upload the .zip file here.

Have you reported this issue to the place you got the battery replaced from?

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa80080b0060, fffff80004fb53d8, fffffa800fa97950}

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: fffffa80080b0060, Physical Device Object of the stack
Arg3: fffff80004fb53d8, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack
Arg4: fffffa800fa97950, The blocked IRP

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


DRVPOWERSTATE_SUBCODE:  3

IMAGE_NAME:  pci.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7928f

MODULE_NAME: pci

FAULTING_MODULE: fffff88000e00000 pci

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

TAG_NOT_DEFINED_c000000f:  FFFFF80004FBBFB0

STACK_TEXT:  
fffff800`04fb5388 fffff800`02eff8c2 : 00000000`0000009f 00000000`00000003 fffffa80`080b0060 fffff800`04fb53d8 : nt!KeBugCheckEx
fffff800`04fb5390 fffff800`02e9a84c : fffff800`04fb54d8 fffff800`04fb54d8 00000000`00000000 00000000`00000002 : nt! ?? ::FNODOBFM::`string'+0x33af0
fffff800`04fb5430 fffff800`02e9a6e6 : fffffa80`0c2e6ab8 fffffa80`0c2e6ab8 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
fffff800`04fb54a0 fffff800`02e9a5ce : 0000019a`b2042536 fffff800`04fb5b18 00000000`00ac8877 fffff800`0300e168 : nt!KiProcessExpiredTimerList+0xc6
fffff800`04fb5af0 fffff800`02e9a3b7 : 0000005c`03767bc6 0000005c`00ac8877 0000005c`03767b26 00000000`00000077 : nt!KiTimerExpiration+0x1be
fffff800`04fb5b90 fffff800`02e8790a : fffff800`0300ae80 fffff800`03018cc0 00000000`00000002 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`04fb5c40 00000000`00000000 : fffff800`04fb6000 fffff800`04fb0000 fffff800`04fb5c00 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0x9F_3_NETwNs64_IMAGE_pci.sys

BUCKET_ID:  X64_0x9F_3_NETwNs64_IMAGE_pci.sys

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

0: kd> !irp fffffa800fa97950
Irp is active with 5 stacks 3 is current (= 0xfffffa800fa97ab0)
 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
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
>[ 16, 2]   0  0 fffffa800b275050 00000000 00000000-00000000    
	      Unable to load image \SystemRoot\system32\DRIVERS\NETwNs64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for NETwNs64.sys
*** ERROR: Module load completed but symbols could not be loaded for NETwNs64.sys
 \Driver\NETwNs64
			Args: 00014400 00000000 00000004 00000002
 [ 16, 2]   0 e1 fffffa80084454f0 00000000 fffff800030dc200-fffffa800d1c7f90 Success Error Cancel pending
	       \Driver\vwifibus	nt!PopSystemIrpCompletion
			Args: 00014400 00000000 00000004 00000002
 [  0, 0]   0  0 00000000 00000000 00000000-fffffa800d1c7f90

Update the Driver below:

Code:

    Image name: NETwNs64.sys
    Timestamp:        Thu Aug 04 06:28:26 2011 (4E39E7AA)

Intel(R) Wireless WiFi Link 5000 Series Adapter Driver for Windows 7 Driver Reference Table - NETwNs64.sys

Basic checks: Please run these tests and report back the results

1. SFC /scannow to check windows for corruption - SFC /SCANNOW Command - System File Checker
2. Disk check for errors on the hard drive - How to Run Disk Check in Windows 7
3. Troubleshoot applications by a clean boot - Troubleshoot Application Conflicts by Performing a Clean Startup
4. Memtest86+ paying close attention to part 3 - RAM - Test with Memtest86+
5. Hard drive test from HDD mfg website - Hard Drive Diagnostic Procedure

Will wait for the results, good luck.

Wait and observe for a week before marking as solved :)

Hmm upload new reports.

I will take a look at them ASAP.

Please bump the thread if I haven't replied in 24 hours.