BSOD insleep mode

[Greg123c]

Past 6 weeks everytime I simply close the lid on laptop, after few minutes I get BSOD.

Dump file reads :
DRIVER_POWER_STATE_FAILURE
Bug Check Code 0x0000009f
Parameter 1: 00000000`00000003
Parameter 2: fffffa80`0701fa10
Parameter 3: fffff800`00b9c518
Parameter 4: fffff980`31608d30
Caused by driver: ntoskrnl.exe
Caused by Address: ntoskrnl.exe+75c40
File Description: NT Kernel & System
Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.18044 (win7sp1_gdr.130104-1431) x64 ntoskrnl.exe+75c40

I have updated all drivers, runchkdsk, removed java, removed adobe, removed all unecessary programs, removed and reinstalled Kaspersky 2013 antivirus.
Have no more ideas.
Dell model N5010, windows 7 home premium, service pack1 , i3 CPU, 6 GB ram, 64 bit

I have no idea what caused this.
It may have been around the time when Kaspersky antivirus was updated from 2012 to 2013. Was an email from Kaspersky that since I had a 2 year subscription, click on link and get auto update to 2013. I also since removed and reinstalled in case that caused it. Could have been windows updates. Simply do not know.


Thank you in advance

 

[koolkat77]

Welcome to SevenForums.

Multiple antiviruses can cause problems such as BSOD-s.

Start Menu\Programs\McAfee	Public:Start Menu\Programs\McAfee	Public

McAfee is a frequent cause of BSOD-s, consider uninstalling it with the McAfee Removal Tool.

• How to uninstall McAfee products using the consumer Removal Tool (MCPR)

Perform a System File Check to check the integrity of all protected Windows 7 :

1. Click on the start rb:
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

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

• How to run Disk Check on Windows 7

Number down items at start-up. Keep only your anti-virus, this also improves the time for logging into windows.

• http://www.sevenforums.com/tutorials/1401-startup-programs-change.html
• http://www.sevenforums.com/tutorial...ation-conflicts-performing-clean-startup.html

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

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa800701fa10, fffff80000b9c518, fffff98031608d30}

*** WARNING: Unable to verify timestamp for bcmwl664.sys
*** ERROR: Module load completed but symbols could not be loaded for bcmwl664.sys
Probably caused by : bcmwl664.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: fffffa800701fa10, Physical Device Object of the stack
Arg3: fffff80000b9c518, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack
Arg4: fffff98031608d30, The blocked IRP

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


DRVPOWERSTATE_SUBCODE:  3

DEVICE_OBJECT: fffffa8009df5050

DRIVER_OBJECT: fffffa8009df7e70

IMAGE_NAME:  bcmwl664.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4b591bf2

MODULE_NAME: bcmwl664

FAULTING_MODULE: fffff88006252000 bcmwl664

IRP_ADDRESS:  fffff98031608d30

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`00b9c4c8 fffff800`034f2992 : 00000000`0000009f 00000000`00000003 fffffa80`0701fa10 fffff800`00b9c518 : nt!KeBugCheckEx
fffff800`00b9c4d0 fffff800`0348d94c : fffff800`00b9c618 fffff800`00b9c618 00000000`00000000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x33af0
fffff800`00b9c570 fffff800`0348d7e6 : fffffa80`09f9a0a0 fffffa80`09f9a0a0 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
fffff800`00b9c5e0 fffff800`0348d6ce : 00000009`6c113ce7 fffff800`00b9cc58 00000000`0003f54f fffff800`03601c68 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9cc30 fffff800`0348d4b7 : 00000002`356822c5 00000002`0003f54f 00000002`35682201 00000000`0000004f : nt!KiTimerExpiration+0x1be
fffff800`00b9ccd0 fffff800`0347a94a : fffff800`035fee80 fffff800`0360ccc0 00000000`00000002 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`00b9cd80 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0x9F_3_POWER_DOWN_IMAGE_bcmwl664.sys

BUCKET_ID:  X64_0x9F_3_POWER_DOWN_IMAGE_bcmwl664.sys

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

0: kd> !irp fffff98031608d30
Irp is active with 7 stacks 4 is current (= 0xfffff98031608ed8)
 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
 [  0, 0]   0 10 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
>[ 16, 2]   0 e0 fffffa8009df5050 00000000 fffff80003913da0-fffff98031608f20 Success Error Cancel 
	       \Driver\BCM43XX	nt!IovpInternalCompletionTrap
			Args: 00014400 00000000 00000004 00000002
 [ 16, 2]   0 e0 fffffa8009df8500 00000000 fffff80003913da0-fffff98031608f68 Success Error Cancel 
	       \DRIVER\VERIFIER_FILTER	nt!IovpInternalCompletionTrap
			Args: 00014400 00000000 00000004 00000002
 [ 16, 2]   0 e1 fffffa8009df45e0 00000000 fffff800036d0200-fffffa800c9d0af0 Success Error Cancel pending
	       \Driver\vwifibus	nt!PopSystemIrpCompletion
			Args: 00014400 00000000 00000004 00000002
 [  0, 0]   0  0 00000000 00000000 00000000-fffffa800c9d0af0    

			Args: 00000000 00000000 00000000 00000000
0: kd> lmvm bcmwl664
start             end                 module name
fffff880`06252000 fffff880`06541000   bcmwl664 T (no symbols)           
    Loaded symbol image file: bcmwl664.sys
    Image path: bcmwl664.sys
    Image name: bcmwl664.sys
    Timestamp:        Fri Jan 22 09:30:58 2010 (4B591BF2)
    CheckSum:         002F8634
    ImageSize:        002EF000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Your BSOD-s were caused by Broadcom 802.11g Network Adapter - Dell Wireless 1390 WLAN Mini-Card so reinstall the drivers to their latest following this method:

Sometimes drivers remain, not completely uninstalled. Follow this tutorial for complete removal of drivers of the particular program:

• How to Clean Left Over Driver Files with Driver Sweeper

Driver Reference Table - bcmwl664.sys
Driver Reference Table - BCMWL664.SYS​

Let us know the results.

 

[Greg123c]

Thank you for response. I followed all steps you recommended except the last step which was to remove the dell wireless card driver and run the Driver sweeper.
Still has BSOD after the other steps.

I do not see the driver listed for the Broadcom 802.11g Network Adapter - Dell Wireless 1390 WLAN Mini-Card in any way to delete and choose in Driver sweeper.

Could you please advise as to where to locate, since following the steps on the link in the forum, I do not see it listed.

If it matters, the BSOD ocurred before I updated the driver. I used slimdriver to update the driver.

Today I rolled back to an earlier save point and reupdated the driver and had same BSOD at earlier save point and again after reupdated.

Thank you

 

[koolkat77]

Can you upload the new reports.

 

[Greg123c]

Attached are the new downloads

If it is the dell wireless driver, please advise on the steps I should take.

Thank you very much

 

[koolkat77]

Is this of any help? Dell Wireless 1390 802.11g Mini Card - Dell - Search - All Dell.com

Let's run driver verifier and see if it catches any misbehaving drivers:

• Driver Verifier Enable/Disable

 

[Greg123c]

Ran driver verifier

It caused the restart to have a problem.
PC then went to restart and "fix" to allow restart.

Dump files attached.

Hopefully this helps to find problem driver.

Thank you in advance.

 

[koolkat77]

Actually I screwed my PC up, need to reinstall windows.. I hope I will be able to get back to you in 24 hours.
Please bump the thread if you do not get a reply in a day.

 

[Greg123c]

Found the problem

I am not sure which worked, but I completely removed Kaspersky antivirus, skype - and slimdrivers that I downloaded well after this problem started.
Also, had a dell utility check my laptop which took an hour and deleted and added as it went.

So far - works like it should.

Thank you for your advice - and hope you reloaded windows without much effort.

Greg

 

[koolkat77]

Thanks for the update on the good job! I have reinstalled windows without a problem

Now installing the tools I check your reports with and once done, I will check your files and let you know if you need to do anything else.

Good luck!

 

[koolkat77]

Hum. This might be a false positive from driver verifier, not very sure though.

The BSOD was caused by Sonic CD/DVD driver (used by many different CD/DVD programs) but I would disregard this dump. Disable verifier and let us know if you get BSODs again.

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

Use !analyze -v to get detailed debugging information.

BugCheck C9, {228, fffff88001c62f74, fffff98004dd6d80, 0}

*** WARNING: Unable to verify timestamp for PxHlpa64.sys
*** ERROR: Module load completed but symbols could not be loaded for PxHlpa64.sys
Probably caused by : PxHlpa64.sys ( PxHlpa64+2f74 )

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
The IO manager has caught a misbehaving driver.
Arguments:
Arg1: 0000000000000228, A driver's completion routine has not marked the IRP pending if the
	PendingReturned field was set in the IRP passed to it. This may cause the OS
	to hang, especially if an error is returned by the stack.
Arg2: fffff88001c62f74, The address in the driver's code where the error was detected.
Arg3: fffff98004dd6d80, IRP address.
Arg4: 0000000000000000

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


BUGCHECK_STR:  0xc9_228

DRIVER_VERIFIER_IO_VIOLATION_TYPE:  228

FAULTING_IP: 
PxHlpa64+2f74
fffff880`01c62f74 49894818        mov     qword ptr [r8+18h],rcx

FOLLOWUP_IP: 
PxHlpa64+2f74
fffff880`01c62f74 49894818        mov     qword ptr [r8+18h],rcx

IRP_ADDRESS:  fffff98004dd6d80

DEVICE_OBJECT: fffffa8009699030

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  [U]WIN7_DRIVER_FAULT[/U] Yikes?? :S

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff800039593dc to fffff800034cac40

STACK_TEXT:  
fffff880`03db5228 fffff800`039593dc : 00000000`000000c9 00000000`00000228 fffff880`01c62f74 fffff980`04dd6d80 : nt!KeBugCheckEx
fffff880`03db5230 fffff800`0396347a : fffff800`039579f0 fffff880`01c62f74 fffff980`04dd6d80 00000000`00000000 : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`03db5270 fffff800`03964483 : 00000000`00000228 fffff880`01c62f74 fffff980`04dd6d80 00000000`ffffffff : nt!ViErrorFinishReport+0xda
fffff880`03db52c0 fffff800`03964654 : fffff880`01c62f74 fffffa80`09dcb810 fffff880`01c62f74 fffff980`04dd6d80 : nt!VfErrorReport1+0x63
fffff880`03db5360 fffff800`039775f9 : fffff980`04dd6ee0 00000000`00000000 fffff880`03db5530 fffff980`04dd6d80 : nt!IovpCompleteRequest4+0x64
fffff880`03db5390 fffff800`034ce6d1 : fffff980`04dd6ee3 00000000`00000000 00000000`00000000 fffff800`0358e7ab : nt!IovpLocalCompletionRoutine+0x189
fffff880`03db53f0 fffff800`0396f19f : fffff980`04dd6d80 fffff880`01faa100 fffffa80`070ec900 00000000`00000000 : nt!IopfCompleteRequest+0x341
fffff880`03db54e0 fffff880`01f994c9 : fffff980`04dd6e98 fffff800`0395914e 00000000`00000000 fffffa80`070ec901 : nt!IovCompleteRequest+0x19f
fffff880`03db55b0 fffff880`01f9ecba : fffffa80`00000000 fffff880`01faa110 00000000`00000000 fffffa80`070ec901 : storport!RaidCompleteRequestEx+0x19
fffff880`03db55e0 fffff880`01f90833 : fffffa80`070ecb10 fffff980`04dd6d80 fffffa80`09635150 fffff800`03974c42 : storport!RaUnitClaimDeviceSrb+0x7a
fffff880`03db5630 fffff880`01f8c71d : fffff880`03db57a8 fffff880`01faa110 fffffa80`098765c8 fffffa80`09699030 : storport! ?? ::FNODOBFM::`string'+0x1fd5
fffff880`03db56f0 fffff800`03975c16 : fffff980`04dd6d80 00000000`00000002 fffffa80`070ec9c0 fffff800`0397137e : storport!RaDriverScsiIrp+0x5d
fffff880`03db5730 fffff800`03974c42 : fffff980`04dd6e98 00000000`00000002 fffffa80`09876190 fffffa80`072d1f40 : nt!IovCallDriver+0x566
fffff880`03db5790 fffff800`03975c16 : fffff980`04dd6d80 00000000`00000002 fffffa80`09876040 fffffa80`09635240 : nt!ViFilterDispatchGeneric+0x62
fffff880`03db57c0 fffff880`01c634d5 : fffff980`04dd6ee0 fffffa80`09699180 fffff980`04dd6d80 fffffa80`07361ae0 : nt!IovCallDriver+0x566
fffff880`03db5820 fffff980`04dd6ee0 : fffffa80`09699180 fffff980`04dd6d80 fffffa80`07361ae0 fffffa80`00000000 : PxHlpa64+0x34d5
fffff880`03db5828 fffffa80`09699180 : fffff980`04dd6d80 fffffa80`07361ae0 fffffa80`00000000 fffffa80`00000001 : 0xfffff980`04dd6ee0
fffff880`03db5830 fffff980`04dd6d80 : fffffa80`07361ae0 fffffa80`00000000 fffffa80`00000001 fffffa80`00000000 : 0xfffffa80`09699180
fffff880`03db5838 fffffa80`07361ae0 : fffffa80`00000000 fffffa80`00000001 fffffa80`00000000 00000000`00000000 : 0xfffff980`04dd6d80
fffff880`03db5840 fffffa80`00000000 : fffffa80`00000001 fffffa80`00000000 00000000`00000000 fffffa80`098765c8 : 0xfffffa80`07361ae0
fffff880`03db5848 fffffa80`00000001 : fffffa80`00000000 00000000`00000000 fffffa80`098765c8 00000000`00000000 : 0xfffffa80`00000000
fffff880`03db5850 fffffa80`00000000 : 00000000`00000000 fffffa80`098765c8 00000000`00000000 00000000`00000000 : 0xfffffa80`00000001
fffff880`03db5858 00000000`00000000 : fffffa80`098765c8 00000000`00000000 00000000`00000000 fffffa80`0733e840 : 0xfffffa80`00000000


STACK_COMMAND:  .bugcheck ; kb

SYMBOL_NAME:  PxHlpa64+2f74

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: PxHlpa64

IMAGE_NAME:  PxHlpa64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a416253

FAILURE_BUCKET_ID:  X64_0xc9_228_PxHlpa64+2f74

BUCKET_ID:  X64_0xc9_228_PxHlpa64+2f74

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

0: kd> lmvm PxHlpa64
start             end                 module name
fffff880`01c60000 fffff880`01c6be00   PxHlpa64 T (no symbols)           
    Loaded symbol image file: PxHlpa64.sys
    Image path: PxHlpa64.sys
    Image name: PxHlpa64.sys
    Timestamp:        Wed Jun 24 05:16:35 2009 (4A416253)
    CheckSum:         000111B7
    ImageSize:        0000BE00
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4