BSOD power driver failure error 9f
YES YOU ARE RIGHT
Epfwndis.sys is a ESET firewall filter driver. You can seek assistanceform the software vendor or try updating the newer version. As Microsoft operating system should not be blamed for the third party product. Hope you understand Syed
http://www.arabitpro.com
September 1st, 2012 7:28am
Since you are using Windbg you should take the blocked IRP (from Argument 4)
Arg4: 896952e8, The blocked IRPThen Go to K> and type !IRP 896952e8It will return some null fields then a field with the Real cause of the BSOD. It may be the ESET timed out because another driver did not repsond in time.I would also make sure that ESET is at least Version 5.x (6.x is just out of beta)MS-MVP 2010, 2011, 2012 Sysnative.com Team ZigZag
Free Windows Admin Tool Kit Click here and download it now
September 1st, 2012 7:30pm
I am getting BSOD everytime I put my laptop into sleep mode. I have mini dump file also but don't know how to analyses it or where to upload this file for support
September 2nd, 2012 3:14am
you can upload it here online
http://www.osronline.com/page.cfm?name=analyzehttp://www.arabitpro.com
Free Windows Admin Tool Kit Click here and download it now
September 2nd, 2012 6:07am
Thanks Syed. I did analysis of the dump file and did some research which says there is some problem with Eset installed. What do you suggest or any one else. Here is debug output.
Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com)
Online Crash Dump Analysis Service
See http://www.osronline.com for more information
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17803.x86fre.win7sp1_gdr.120330-1504
Machine Name:
Kernel base = 0x84a47000 PsLoadedModuleList = 0x84b904d0
Debug session time: Fri Aug 31 12:18:07.493 2012 (UTC - 4:00)
System Uptime: 0 days 7:41:20.163
*******************************************************************************
* *
* 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: 00000003, A device object has been blocking an Irp for too long a time
Arg2: 86a54530, Physical Device Object of the stack
Arg3: 84b6eae0, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack
Arg4: 896952e8, The blocked IRP
Debugging Details:
------------------
TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2
DRVPOWERSTATE_SUBCODE: 3
DEVICE_OBJECT: 8a106028
DRIVER_OBJECT: 89ce5ab0
IMAGE_NAME: Epfwndis.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a0c18a3
MODULE_NAME: Epfwndis
FAULTING_MODULE: 927f3000 Epfwndis
IRP_ADDRESS: 896952e8
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
BUGCHECK_STR: 0x9F
PROCESS_NAME: System
CURRENT_IRQL: 2
STACK_TEXT:
84b6ea94 84b0decf 0000009f 00000003 86a54530 nt!KeBugCheckEx+0x1e
84b6eb00 84b0df48 84b6eba0 00000000 84b7b380 nt!PopCheckIrpWatchdog+0x1f5
84b6eb38 84ac1019 84b896e0 00000000 34d5926e nt!PopCheckForIdleness+0x73
84b6eb7c 84ac0fbd 84b71d20 84b6eca8 00000001 nt!KiProcessTimerDpcTable+0x50
84b6ec68 84ac0e7a 84b71d20 84b6eca8 00000000 nt!KiProcessExpiredTimerList+0x101
84b6ecdc 84abf00e 001b1316 86a416f0 84b7b380 nt!KiTimerExpiration+0x25c
84b6ed20 84abee38 00000000 0000000e 00000000 nt!KiRetireDpcList+0xcb
84b6ed24 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x38
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
FAILURE_BUCKET_ID: 0x9F_3_IMAGE_Epfwndis.sys
BUCKET_ID: 0x9F_3_IMAGE_Epfwndis.sys
Followup: MachineOwner
September 2nd, 2012 6:49am
YES YOU ARE RIGHT
Epfwndis.sys is a ESET firewall filter driver. You can seek assistanceform the software vendor or try updating the newer version. As Microsoft operating system should not be blamed for the third party product. Hope you understand Syed
http://www.arabitpro.com
Free Windows Admin Tool Kit Click here and download it now
September 2nd, 2012 7:17am
Since you are using Windbg you should take the blocked IRP (from Argument 4)
Arg4: 896952e8, The blocked IRPThen Go to K> and type !IRP 896952e8It will return some null fields then a field with the Real cause of the BSOD. It may be the ESET timed out because another driver did not repsond in time.I would also make sure that ESET is at least Version 5.x (6.x is just out of beta)MS-MVP 2010, 2011, 2012 Sysnative.com Team ZigZag
September 2nd, 2012 7:19pm