Hi xrefa, welcome to 7F :)
The first minidmp blames NETwNs64.sys - Intel® Wireless WiFi Link 5000 Series Adapter Driver for Windows 7.
The second vmnetadapter.sys is a WINDOWS system32 driver, VMware Virtual Network Adapter Driver
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 9F, {3, fffffa80043a6a10, fffff80000b9c518, fffffa800880fd30}
*** WARNING: Unable to verify timestamp for NETwNs64.sys
*** ERROR: Module load completed but symbols could not be loaded for NETwNs64.sys
Probably caused by : NETwNs64.sys
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
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: fffffa80043a6a10, Physical Device Object of the stack
Arg3: fffff80000b9c518, Functional Device Object of the stack
Arg4: fffffa800880fd30, The blocked IRP
Debugging Details:
------------------
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
FAILURE_BUCKET_ID: X64_0x9F_IMAGE_NETwNs64.sys
BUCKET_ID: X64_0x9F_IMAGE_NETwNs64.sys
Followup: MachineOwner
---------
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 9F, {3, fffffa8003668bb0, fffff80000b9c518, fffffa8007320870}
*** WARNING: Unable to verify timestamp for vmnetadapter.sys
*** ERROR: Module load completed but symbols could not be loaded for vmnetadapter.sys
Probably caused by : vmnetadapter.sys
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
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: fffffa8003668bb0, Physical Device Object of the stack
Arg3: fffff80000b9c518, Functional Device Object of the stack
Arg4: fffffa8007320870, The blocked IRP
Debugging Details:
------------------
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
FAILURE_BUCKET_ID: X64_0x9F_IMAGE_vmnetadapter.sys
BUCKET_ID: X64_0x9F_IMAGE_vmnetadapter.sys
Followup: MachineOwner
---------
You would have to:
- Go to Intel's Download Center ( http://downloadcenter.intel.com ) and download the latest version of the drivers for that device.
- Uninstall the current drivers on your system for that device
- Install the freshly downloaded drivers
- Monitor for further BSOD's.
The second indicates a system file has not been updated, and you would have to run the same procedure as above for the Intel driver.
Unless your Company allows you to do this, okay, forge ahead. But, I would take it back to your IT dept., and tell them it is not working right.
Until you can fix it or have it replaced, does it work okay if you just shut it down then restart?
Are you forcing it to hibernate/sleep or are you allowing the settings in Power Options to let it hibernate/sleep?
Quote