Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD while hybernating/leaving computer unattended for a while

17 Mar 2013   #1
vicbitter

Windows 7 Home Premium x64
 
 
BSOD while hybernating/leaving computer unattended for a while

Hello,

I have been having BSOD problems since the last couple of months atleast. I can't figure out what is wrong so hoping to get some information here.

Please find the SF Diagnostic tool results attached with this.

In addition, I downloaded Windbg tool a few days ago and ran diagnostics and this is what I found (just in case this helps!)

DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa800737ee30, Physical Device Object of the stack
Arg3: fffff80000b9c3d8, Functional Device Object of the stack
Arg4: fffffa8014e59e50, The blocked IRP

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


DRVPOWERSTATE_SUBCODE: 3

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MODULE_NAME: ntkrnlmp

FAULTING_MODULE: fffff880048e4000 vmnetadapter

IRP_ADDRESS: fffffa8014e59e50

DEVICE_OBJECT: fffffa8010123050

DRIVER_OBJECT: fffffa8010153850

IMAGE_NAME: ntkrnlmp

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x9F

PROCESS_NAME: System

CURRENT_IRQL: 2

STACK_TEXT:


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

FAILURE_BUCKET_ID: X64_0x9F_3_IMAGE_ntkrnlmp

BUCKET_ID: X64_0x9F_3_IMAGE_ntkrnlmp

Followup: MachineOwner


My System SpecsSystem Spec
.
17 Mar 2013   #2
koolkat77

Microsoft Community Contributor Award Recipient

Windows 10 Home 64Bit
 
 

Welcome to Seven Forums.

Your BSOD's were caused by vmnetadapter.sys - Driver Description: VMware virtual network adapter driver

Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa8007374bb0, fffff80000b9c3d8, fffffa80158a5010}

Unable to load image \SystemRoot\system32\DRIVERS\vmnetadapter.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for vmnetadapter.sys
*** ERROR: Module load completed but symbols could not be loaded for vmnetadapter.sys
Probably caused by : ntkrnlmp

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

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


DRVPOWERSTATE_SUBCODE:  3

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: ntkrnlmp

FAULTING_MODULE: fffff880051f7000 vmnetadapter

DEVICE_OBJECT: fffffa8010408050

DRIVER_OBJECT: fffffa800f97d9f0

IMAGE_NAME:  ntkrnlmp

IRP_ADDRESS:  fffffa80158a5010

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`02f33992 : 00000000`0000009f 00000000`00000003 fffffa80`07374bb0 fffff800`00b9c3d8 : nt!KeBugCheckEx
fffff800`00b9c390 fffff800`02ece94c : fffff800`00b9c4d8 fffff800`00b9c4d8 00000000`00000000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x33af0
fffff800`00b9c430 fffff800`02ece7e6 : fffffa80`0f9b5958 fffffa80`0f9b5958 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
fffff800`00b9c4a0 fffff800`02ece6ce : 0000008b`c0763c39 fffff800`00b9cb18 00000000`003ab5af fffff800`03043868 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9caf0 fffff800`02ece4b7 : 00000017`1a6fc7c5 00000017`003ab5af 00000017`1a6fc79f 00000000`000000af : nt!KiTimerExpiration+0x1be
fffff800`00b9cb90 fffff800`02ebb94a : fffff800`0303fe80 fffff800`0304dcc0 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_POWER_DOWN_IMAGE_ntkrnlmp

BUCKET_ID:  X64_0x9F_3_POWER_DOWN_IMAGE_ntkrnlmp

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

0: kd> !irp fffffa80158a5010
Irp is active with 3 stacks 2 is current (= 0xfffffa80158a5128)
 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 fffffa8010408050 00000000 00000000-00000000    pending
	       \Driver\VMnetAdapter
			Args: 00015500 00000001 00000004 00000003
 [  0, 0]   0  0 00000000 00000000 00000000-fffffa800738e0a0    

			Args: 00000000 00000000 00000000 00000000
0: kd> lmvm vmnetadapter
start             end                 module name
fffff880`051f7000 fffff880`051ff000   vmnetadapter T (no symbols)           
    Loaded symbol image file: vmnetadapter.sys
    Image path: \SystemRoot\system32\DRIVERS\vmnetadapter.sys
    Image name: vmnetadapter.sys
    Timestamp:        Sun Jul 08 13:58:35 2012 (4FF93DAB)
    CheckSum:         000077E3
    ImageSize:        00008000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
Update it to the latest version available, if that does not work. Remove it completely.

Sometimes drivers remain, not completely uninstalled. Follow this tutorial for complete removal of drivers of the particular program:
Bit Defender contributes in BSOD's. As a test please remove it using its removal tool from here: Uninstallers (removal tools) for common antivirus software - ESET Knowledgebase

We recommended Microsoft Security Essentials from a strict BSOD perspective. Is most compatible & provides most stability compared to other antivirus app/Internet Security Software.
warning   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 to check the integrity of all protected Windows 7:
  1. Click on the start
  2. Type CMD on Search
  3. Left click and Run as Administrator
  4. Type
    Code:
    SFC /scannow
Full tutorial here:Check your hard drive(s) for errors by running chkdsk:Number down items at start-up. Keep only your anti-virus, this also improves the time for logging into windows.Do you have a SSD? Is the firmware for your SSD up-to-date?

Check for one and see if the stability returns.

Let us know the results and further BSOD reports if you have them.

BSOD BUGCHECK SUMMARY
Code:
**************************Sun Mar 17 00:42:00.537 2013 (UTC + 6:00)**************************
Loading Dump File [C:\Users\Yusra\Downloads\SF_17-03-2013\SF_17-03-2013\031713-12058-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431
System Uptime: 0 days 16:40:22.942
Unable to load image \SystemRoot\system32\DRIVERS\vmnetadapter.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for vmnetadapter.sys
*** ERROR: Module load completed but symbols could not be loaded for vmnetadapter.sys
Probably caused by : ntkrnlmp
BugCheck 9F, {3, fffffa8007374bb0, fffff80000b9c3d8, fffffa80158a5010}
BugCheck Info: DRIVER_POWER_STATE_FAILURE (9f)
Usual causes:  Device driver
Arguments: 
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa8007374bb0, Physical Device Object of the stack
Arg3: fffff80000b9c3d8, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack
Arg4: fffffa80158a5010, The blocked IRP
BUGCHECK_STR: 0x9F
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: System
FAILURE_BUCKET_ID: X64_0x9F_3_POWER_DOWN_IMAGE_ntkrnlmp
CPUID:        "Intel(R) Core(TM) i5-3317U CPU @ 1.70GHz"
MaxSpeed:     1700
CurrentSpeed: 1692

Vendor Insyde Corp.
BIOS Version  1.60
BIOS Release Date 08/16/2012
Manufacturer TOSHIBA      
Product Name Satellite U840
Version PSU4WA-006004
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
**************************Fri Mar 15 20:00:55.067 2013 (UTC + 6:00)**************************
Loading Dump File [C:\Users\Yusra\Downloads\SF_17-03-2013\SF_17-03-2013\031613-13150-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431
System Uptime: 0 days 11:58:37.472
Unable to load image \SystemRoot\system32\DRIVERS\vmnetadapter.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for vmnetadapter.sys
*** ERROR: Module load completed but symbols could not be loaded for vmnetadapter.sys
Probably caused by : ntkrnlmp
BugCheck 9F, {3, fffffa800736cbb0, fffff800049d13d8, fffffa8014d99d10}
BugCheck Info: DRIVER_POWER_STATE_FAILURE (9f)
Usual causes:  Device driver
Arguments: 
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa800736cbb0, Physical Device Object of the stack
Arg3: fffff800049d13d8, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack
Arg4: fffffa8014d99d10, The blocked IRP
BUGCHECK_STR: 0x9F
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: System
FAILURE_BUCKET_ID: X64_0x9F_3_POWER_DOWN_IMAGE_ntkrnlmp
CPUID:        "Intel(R) Core(TM) i5-3317U CPU @ 1.70GHz"
MaxSpeed:     1700
CurrentSpeed: 1692

Vendor Insyde Corp.
BIOS Version  1.60
BIOS Release Date 08/16/2012
Manufacturer TOSHIBA      
Product Name Satellite U840
Version PSU4WA-006004
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
**************************Thu Mar 14 22:50:21.400 2013 (UTC + 6:00)**************************
Loading Dump File [C:\Users\Yusra\Downloads\SF_17-03-2013\SF_17-03-2013\031513-13431-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431
System Uptime: 0 days 11:58:37.472
Unable to load image \SystemRoot\system32\DRIVERS\vmnetadapter.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for vmnetadapter.sys
*** ERROR: Module load completed but symbols could not be loaded for vmnetadapter.sys
Probably caused by : ntkrnlmp
BugCheck 9F, {3, fffffa800735de30, fffff80000b9c3d8, fffffa8010f716c0}
BugCheck Info: DRIVER_POWER_STATE_FAILURE (9f)
Usual causes:  Device driver
Arguments: 
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa800736cbb0, Physical Device Object of the stack
Arg3: fffff800049d13d8, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack
Arg4: fffffa8014d99d10, The blocked IRP
BUGCHECK_STR: 0x9F
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: System
FAILURE_BUCKET_ID: X64_0x9F_3_POWER_DOWN_IMAGE_ntkrnlmp
CPUID:        "Intel(R) Core(TM) i5-3317U CPU @ 1.70GHz"
MaxSpeed:     1700
CurrentSpeed: 1692

Vendor Insyde Corp.
BIOS Version  1.60
BIOS Release Date 08/16/2012
Manufacturer TOSHIBA      
Product Name Satellite U840
Version PSU4WA-006004
My System SpecsSystem Spec
17 Mar 2013   #3
vicbitter

Windows 7 Home Premium x64
 
 

Hi Koolkat77,

Thank you so much for your suggestions, I can attest that this problem is now resolved.

I went to msconfig.exe, and disable the vmware software from the startup programs.

Now when I close the lid of the computer, the laptop goes to sleep and wakes up when I open the lid!

I would like to keep the vmware software because I use certain software on virtual drive, but I have disabled it from automatically starting on system start up.

Reg. you other suggestions, I have tried microsoft security essentials in the past and have always found it coming up short when it comes to catching viruses, although I can't recall using malwarebytes simulataneously with MSE.

At present, I have Bitdefender Internet Security 2013 and it's doing a great job for the past 4 months and recently I have added Advanced Systemcare Pro and both these jobs appear to be doing a good job..

Thanks again for your help, I really appreciate it!

Regards,

Vik
My System SpecsSystem Spec
.

17 Mar 2013   #4
koolkat77

Microsoft Community Contributor Award Recipient

Windows 10 Home 64Bit
 
 

Good to hear!

Be sure to post again if you have any problems
My System SpecsSystem Spec
Reply

 BSOD while hybernating/leaving computer unattended for a while




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
BSOD at random times while computer is hybernating BCCode: 9f
Hello there seven forum! I am having an issue with BSOD. The short of it is that the computer runs fine while I am on it, however *sometimes* when I let the computer go to sleep at some point (usually within 24hr) the system shuts down randomly and then when I come back to it I have to boot it...
BSOD Help and Support
BSOD while leaving computer unattended
Hello, I hope you guys can help me. I bought parts and build this computer, and I'm afraid my inexperience might be the cause of this BSOD. Here are the details that appear when I boot my computer after the BSOD. Problem signature: Problem Event Name: BlueScreen OS...
BSOD Help and Support
BSOD while computer was unattended
I am new to this forum - thanks in advance for your help. I left my computer running (with a few programs open: Word 2010, Excel, Opera, etc.). When I came back, a BSOD awaited me. I've attached a photo I took of the screen and a zip file containing: the output directory of the jcgriff...
BSOD Help and Support
BSOD after leaving the computer alone for some time
Hey Guys, Well I have been getting the BSOD for sometime now. It only happens to usually my account, which is the main one on this PC, when I am logged in and I leave for about 30 minutes. If I log off and leave the computer alone at just the login screen I usually do not get this error. I...
BSOD Help and Support
BSOD after leaving computer unattended. Sometimes win32.sys error
Hello everyone, I have read the instruction for posting to this forum and hopefully have done it correctly. I have a home built computer (built about Mid 2010) that is our HTPC. When I first set it up I would get the BSOD every once in a while (3-4 months), but since this computer was not...
BSOD Help and Support
BSOD when leaving computer on for a little while
I've been getting some BSOD errors relatively frequently recently. This is on a recent (week or two) fresh windows 7 install. x64 full retail version (MSDNAA). My hardware is about 4 years old or so; I've written the hardware details into my profile. I've upgraded the GPU, SSD, Audio card,...
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

й Designer Media Ltd

All times are GMT -5. The time now is 11:47.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App