BSOD on Vaio Laptop

STOP 0x0000009F: DRIVER_POWER_STATE_FAILURE Usual causes: Device driver

Productname: Intel® Wireless WiFi Link Adapter
Description: Intel® Wireless WiFi Link Driver
Company: Intel Corporation

Replace above driver.

Remove any CD virtualization programs such as Daemon Tools and Alcohol 120%. They use a driver, found in your dmp, sptd.sys, that is notorious for causing BSODs. Use this SPTD uninstaller when you're done:
www.duplexsecure.com/en/downloads

Code:

icrosoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
 
Loading Dump File [C:\Users\richc46\AppData\Local\Temp\Temp1_Windows_NT6_BSOD_jcgriff2[2].zip\031510-41028-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff800`00b9c500?
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`0340f000 PsLoadedModuleList = 0xfffff800`0364ce50
Debug session time: Mon Mar 15 04:12:36.069 2010 (GMT-4)
System Uptime: 0 days 10:09:13.162
Loading Kernel Symbols
...............................................................
................................................................
..............................
Loading User Symbols
Loading unloaded module list
...............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 9F, {3, fffffa800785e060, fffff80000b9c518, fffffa801558b010}
*** WARNING: Unable to verify timestamp for NETw5s64.sys
*** ERROR: Module load completed but symbols could not be loaded for NETw5s64.sys
Probably caused by : NETw5s64.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: fffffa800785e060, Physical Device Object of the stack
Arg3: fffff80000b9c518, Functional Device Object of the stack
Arg4: fffffa801558b010, The blocked IRP
Debugging Details:
------------------
 
DRVPOWERSTATE_SUBCODE:  3
IRP_ADDRESS:  fffffa801558b010
DEVICE_OBJECT: fffffa80093e8050
DRIVER_OBJECT: fffffa80093db610
IMAGE_NAME:  NETw5s64.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  4aafedb7
MODULE_NAME: NETw5s64
FAULTING_MODULE: fffff88005605000 NETw5s64
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
CURRENT_IRQL:  2
LAST_CONTROL_TRANSFER:  from fffff800034efe23 to fffff80003480f00
STACK_TEXT:  
fffff800`00b9c4c8 fffff800`034efe23 : 00000000`0000009f 00000000`00000003 fffffa80`0785e060 fffff800`00b9c518 : nt!KeBugCheckEx
fffff800`00b9c4d0 fffff800`0348cfa6 : fffff800`00b9c600 fffff800`00b9c600 00000000`00000001 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x29330
fffff800`00b9c570 fffff800`0348c326 : fffffa80`0aeda168 fffffa80`0aeda168 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
fffff800`00b9c5e0 fffff800`0348ce7e : 00000055`1b61fa26 fffff800`00b9cc58 00000000`0023c0e0 fffff800`035fde88 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9cc30 fffff800`0348c697 : 0000000d`43d18bc3 0000000d`0023c0e0 0000000d`43d18bdf 00000000`000000e0 : nt!KiTimerExpiration+0x1be
fffff800`00b9ccd0 fffff800`034896fa : fffff800`035f9e80 fffff800`03607c40 00000000`00000001 fffffa80`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_IMAGE_NETw5s64.sys
BUCKET_ID:  X64_0x9F_IMAGE_NETw5s64.sys
Followup: MachineOwner
---------

Refer the links below for more details on updating drivers:

Update a driver for hardware that isn't working properly
Update a driver for hardware that isn't working properly

Update drivers: recommended links
Update drivers: recommended links

Peter

The BSOD reports are like clues. You had many so there is a good chance that the driver mentioned is the cause. In addition, be sure to remove Daemon and its driver (may be Alchohol 120% rather than Daemon), but it must be removed. We can find alternative software if desired.

I think that if you replace the drivers, you will be OK. If not repost. I will help you find the driver if necessary.
NETw5s64.sys The Wireless Driver. It is dated August of last year. It may not be outdated, but may be corrupt. Try to replace and we will see what happens. I will help if you have problems.

If replacement does not help, lets try not to use wireless for a while, as a test.


How to Find Drivers
search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone - will help you search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- - if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.
- The most common drivers are listed on this page: http://www.carrona.org/dvrref.html
- - Driver manufacturer links are on this page: http://www.carrona.org/drvrdown.html
To remove any left over driver remnants, especially from graphics cards, use driver sweeper
www.guru3d.com/category/driversweeper/

Second row, second box; Intel will update all drivers that are necessary. If none are found, post and we will just replace.

http://downloadcenter.intel.com/

Peter
Go to search type cmd
In cmd type driverquery. The list of all your drivers will appear. If SPTD is still there, let me know and we will use the removal tool to unistall it.
You can use this in lieu of Daemon
Freeware MagicISO Virtual CD/DVD-ROM(MagicDisc) Overview

Always update from the websites. The automatic update leaves a lot to be desired.

Please remove any CD virtualization programs such as Daemon Tools and Alcohol 120%. They use a driver, found in your dmp, sptd.sys, that is notorious for causing BSODs. Use this SPTD uninstaller when you're done:
www.duplexsecure.com/en/downloads