BSOD - BAD_POOL_CALLER ; Windows shut down unexpectedly

BSOD......DRIVER_POWER_STATE_FAILURE ....dammit!!!

The following describes an issue with my Laptop tonight;



I'm also a problem as I've lost the guide that shows me how to create and upload a zipped mini-dump file to the forum, for analysis by the experts. Pointers anyone?







....it's the medication!!

Re: BSOD......DRIVER_POWER_STATE_FAILURE ....dammit!!!

Here is the information that you need.
http://www.vistax64.com/crashes-debugging/282419-blue-screen-death-bsod-posting-instructions.html

Re: BSOD......DRIVER_POWER_STATE_FAILURE ....dammit!!!

The mini dumps in C:\Windows\Minidump Just make a big zipfile, then attach them to the thread via the advanced posting button, using the Manage Attachments.

Edit..

Guess theres an easier way...

Re: BSOD......DRIVER_POWER_STATE_FAILURE ....dammit!!!

If that 9F code is correct, it is a driver. Easy to replace, just like the last time.


This is the list of old drivers that I suggested to be replaced. Assuming that you did not, these BSOD's will happen more and more frequently. The computer is getting old, technology is changing, we must keep up.

Re: BSOD......DRIVER_POWER_STATE_FAILURE ....dammit!!!

How to set up the files to be sent.
Dump files - Upload to Seven Forums - Windows 7 Forums

Re: BSOD......DRIVER_POWER_STATE_FAILURE ....dammit!!!

Thank-you Richard for your patience.....

I hope that I managed to get this bit right and have attached something of value for analysis.

View attachment Perfmon HTML.zip

View attachment 21043

There's hope for old fogeys sometimes......but not often!!:huh:

.....and obviously this is one of those times as I've had a 'senior moment' and forgot to include System details etc, here:



The system is full OEM of July 2007, however RAM was increased from 1GB [1 x 1GB stick] to 4GB [2 x 2GB sticks] about 2 years ago, and about 12 months ago, the Hard drive was increased from 120GB to 320Gb, as can be seen in the above.

The OS hasn't been touched since new - no reformatting etc. because of no reboot CD.

Other details in the Systems Info below.

Re: BSOD......DRIVER_POWER_STATE_FAILURE ....dammit!!!

richc46 said:

If that 9F code is correct, it is a driver. Easy to replace, just like the last time.

Code:

int15.sys    Wed Oct 01 01:29:49 2003 (3F7A664D)
NTIDrvr.sys  Tue Dec 21 15:33:14 2004 (41C8888A)
Afc.sys      Wed Feb 23 01:58:55 2005 (421C29AF)
DPortIO.sys  Fri Dec 23 03:13:04 2005 (43ABB190)
bcm4sbxp.sys Wed Jun 14 17:02:02 2006 (4490794A)
mdmxsdk.sys  Mon Jun 19 17:26:59 2006 (449716A3)
xaudio.sys   Fri Aug 04 20:39:09 2006 (44D3E8AD)
BrUsbSer.sys Sat Sep 02 20:53:37 2006 (44FA2791)
secdrv.SYS   Wed Sep 13 09:18:32 2006 (45080528)
DKbFltr.sys  Thu Oct 19 04:24:28 2006 (4537363C)
peauth.sys   Mon Oct 23 04:55:32 2006 (453C8384)
SynTP.sys    Mon Oct 23 13:52:26 2006 (453D015A)
EMS7SK.sys   Wed Oct 25 02:36:34 2006 (453F05F2)
ESM7SK.sys   Wed Oct 25 02:36:42 2006 (453F05FA)
ESD7SK.sys   Wed Oct 25 02:36:47 2006 (453F05FF)
NETw3v32.sys Mon Oct 30 13:42:26 2006 (45463982)
crcdisk.sys  Thu Nov 02 04:52:27 2006 (4549B1CB)
HSX_CNXT.sys Wed Nov 08 18:53:45 2006 (45526E09)
HSXHWAZL.sys Wed Nov 08 18:53:56 2006 (45526E14)
HSX_DPV.sys  Wed Nov 08 18:55:07 2006 (45526E5B)
PSDNServ.sys Sun Dec 24 23:20:44 2006 (458F519C)
psdvdisk.sys Sun Dec 24 23:20:48 2006 (458F51A0)
spldr.sys    Thu Jun 21 20:29:17 2007 (467B17DD)
timntr.sys   Wed Aug 29 08:13:12 2007 (46D562D8)
tifsfilt.sys Wed Aug 29 08:37:17 2007 (46D5687D)
PxHelp20.sys Wed Oct 17 14:24:26 2007 (4716535A)
intelppm.sys Sat Jan 19 00:27:20 2008 (47918A38)
Fs_Rec.SYS   Sat Jan 19 00:27:57 2008 (47918A5D)
cdfs.sys     Sat Jan 19 00:28:02 2008 (47918A62)
Msfs.SYS     Sat Jan 19 00:28:08 2008 (47918A68)
bowser.sys   Sat Jan 19 00:28:26 2008 (47918A7A)
luafv.sys    Sat Jan 19 00:30:35 2008 (47918AFB)
BATTC.SYS    Sat Jan 19 00:32:45 2008 (47918B7D)
compbatt.sys Sat Jan 19 00:32:47 2008 (47918B7F)
CmBatt.sys   Sat Jan 19 00:32:47 2008 (47918B7F)
wmiacpi.sys  Sat Jan 19 00:32:47 2008 (47918B7F)
msisadrv.sys Sat Jan 19 00:32:51 2008 (47918B83)
mssmbios.sys Sat Jan 19 00:32:55 2008 (47918B87)
fileinfo.sys Sat Jan 19 00:34:27 2008 (47918BE3)
Dxapi.sys    Sat Jan 19 00:36:12 2008 (47918C4C)
Beep.SYS     Sat Jan 19 00:49:10 2008 (47918F56)
Null.SYS     Sat Jan 19 00:49:12 2008 (47918F58)
mountmgr.sys Sat Jan 19 00:49:13 2008 (47918F59)
kbdclass.sys Sat Jan 19 00:49:14 2008 (47918F5A)
mouclass.sys Sat Jan 19 00:49:14 2008 (47918F5A)
mouhid.sys   Sat Jan 19 00:49:16 2008 (47918F5C)
i8042prt.sys Sat Jan 19 00:49:17 2008 (47918F5D)
swenum.sys   Sat Jan 19 00:49:20 2008 (47918F60)
intelide.sys Sat Jan 19 00:49:42 2008 (47918F76)
volmgr.sys   Sat Jan 19 00:49:51 2008 (47918F7F)
vga.sys      Sat Jan 19 00:52:06 2008 (47919006)
VIDEOPRT.SYS Sat Jan 19 00:52:10 2008 (4791900A)
WDFLDR.SYS   Sat Jan 19 00:52:19 2008 (47919013)
monitor.sys  Sat Jan 19 00:52:19 2008 (47919013)
Wdf01000.sys Sat Jan 19 00:52:21 2008 (47919015)
WUDFPf.sys   Sat Jan 19 00:52:49 2008 (47919031)
WUDFRd.sys   Sat Jan 19 00:53:04 2008 (47919040)
WMILIB.SYS   Sat Jan 19 00:53:08 2008 (47919044)
HIDPARSE.SYS Sat Jan 19 00:53:16 2008 (4791904C)
USBD.SYS     Sat Jan 19 00:53:17 2008 (4791904D)
usbuhci.sys  Sat Jan 19 00:53:20 2008 (47919050)
usbccgp.sys  Sat Jan 19 00:53:29 2008 (47919059)
umbus.sys    Sat Jan 19 00:53:40 2008 (47919064)
mpsdrv.sys   Sat Jan 19 00:54:45 2008 (479190A5)
lltdio.sys   Sat Jan 19 00:55:03 2008 (479190B7)
rspndr.sys   Sat Jan 19 00:55:03 2008 (479190B7)
irda.sys     Sat Jan 19 00:55:25 2008 (479190CD)
tunmp.sys    Sat Jan 19 00:55:40 2008 (479190DC)
ndisuio.sys  Sat Jan 19 00:55:40 2008 (479190DC)
netbios.sys  Sat Jan 19 00:55:45 2008 (479190E1)
nsiproxy.sys Sat Jan 19 00:55:50 2008 (479190E6)
ipfltdrv.sys Sat Jan 19 00:56:23 2008 (47919107)
ndistapi.sys Sat Jan 19 00:56:24 2008 (47919108)
NDProxy.SYS  Sat Jan 19 00:56:28 2008 (4791910C)
rasacd.sys   Sat Jan 19 00:56:31 2008 (4791910F)
wanarp.sys   Sat Jan 19 00:56:31 2008 (4791910F)
rasl2tp.sys  Sat Jan 19 00:56:33 2008 (47919111)
raspptp.sys  Sat Jan 19 00:56:34 2008 (47919112)
TDI.SYS      Sat Jan 19 00:57:10 2008 (47919136)
modem.sys    Sat Jan 19 00:57:16 2008 (4791913C)
RDPCDD.sys   Sat Jan 19 01:01:08 2008 (47919224)
tdtcp.sys    Sat Jan 19 01:01:08 2008 (47919224)
rdpencdd.sys Sat Jan 19 01:01:09 2008 (47919225)
TSDDD.dll    Sat Jan 19 01:01:09 2008 (47919225)
tssecsrv.sys Sat Jan 19 01:01:15 2008 (4791922B)
usbscan.sys  Sat Jan 19 01:14:09 2008 (47919531)
usbprint.sys Sat Jan 19 01:14:40 2008 (47919550)
drmk.sys     Sat Jan 19 01:53:02 2008 (47919E4E)
BOOTVID.dll  Sat Jan 19 02:27:15 2008 (4791A653)
LVUSBSta.sys Sat Jul 26 10:59:36 2008 (488B3BD8)
snman380.sys Wed Nov 19 19:23:37 2008 (4924AE09)
BrSerIf.sys  Thu Jan 22 23:59:04 2009 (49794E98)
nvlddmkm.sys Fri Jan 30 13:05:03 2009 (4983414F)
spsys.sys    Tue Mar 10 13:10:28 2009 (49B69F04

This is the list of old drivers that I suggested to be replaced. Assuming that you did not, these BSOD's will happen more and more frequently. The computer is getting old, technology is changing, we must keep up.

Click to expand...

Your patience is outstanding Richard.

However, this list is somewhat overwhelming, and I guess that I will be dragging your patience to the limit with the following:

Q1..........Is there a Tutorial here that will give me some simple guidance on how to update all of these drivers - presumably, one by one??

Q2..........Is it just a matter of 'Googling' each individual listed driver, taking the first in the list, say - int15.sys , finding a download host website, and just downloading from there?

Q3..........Assuming that Q2 is correct, is there a need to, and should I reboot after each update? I'm assuming that the need to create Restore points along the way, is also a prudent matter?

Sorry about putting you through all of this........it's the medication, you know

Re: BSOD......DRIVER_POWER_STATE_FAILURE ....dammit!!!

Hi Tony, while you are waiting for Rich to get back to you you might like to have a look at this guide it was written for Seven but applicable to Vista.
Disregard what is said about the BIOS as BIOS flashing can be risky and should only be done if necessary (Rich will advise you on this if it is necessary)
Yours being a laptop you need a modified Graphics driver usually best sourced from your laptop manufacturer.

Installing and updating drivers in 7 - Windows 7 Forums

Acer Europe - Service & Support, Drivers & Utilities, Downloads, Notebook, Aspire 5630

Hope you get things sorted links will give you a bit of a start while waiting for Rich to get back

Re: BSOD......DRIVER_POWER_STATE_FAILURE ....dammit!!!

G'day Mitch,
...and thanks for this. Are you in the South Island Ngai Tahu?

However, I'm absolutely lost in this realm. The Acer link throws up this list....but where to start? Because I have a Logitech webcam for Notebooks, I've actually disabled the Acer Orbicam [Logitech] shown here, but I suppose it wouldn't harm to keep it updated:



I guess though, that something needs to be done before I turf it out the window, and now is as good a time as any.

Cheers.

PS. Great Comm. Games Rugby and Netball results....eh bro'.!

Re: BSOD......DRIVER_POWER_STATE_FAILURE ....dammit!!!

Hi Again Tony
Sorry that we have to meet under these circumstances, but I am glad that you are back. I enjoyed our time together during the last problem.
I just got back from 3 weeks in Europe; Paris, Prague, Munich, Vienna and some small towns, my sleep schedule is all screwed up. I just want to give you a quick idea of the problem, then off to bed. We will try to work together to get this resolved for good; for now it appears to be a simple problem. You have to replace a driver
Productname: GEARAspi
Description: Filter Driver for 2k and XP
Company: GEAR Software
Tomorrow morning, I will give you a good analysis, answer all questions and get you going again.
You will notice that the driver is so old, it is classified for XP use.
Dont worry about the questions; I enjoy helping. Trust me it is very enjoyable working with you, it is like working with a friend.


I was a bit surprised to find the cause of your BSOD was the same as the last time you had a problem. It is the ITunes driver. If you updated the driver during our last meeting and the problem still persists, you must find a replacement for ITunes.

GEARAspiWDM.sys Mon May 18 08:16:53 2009
From your old BSOD, the driver has the same date and has not been updated.

Re: BSOD......DRIVER_POWER_STATE_FAILURE ....dammit!!!

sassofalco said:

G'day Mitch,
...and thanks for this. Are you in the South Island Ngai Tahu?

Click to expand...

Migrated to the warmer climate of the North Island Tony Also my wife is from up here she is Ngati Porou (East Cape)

Take care mate

Re: BSOD......DRIVER_POWER_STATE_FAILURE ....dammit!!!

richc46 said:

Hi Again Tony
Sorry that we have to meet under these circumstances, but I am glad that you are back. I enjoyed our time together during the last problem.
I just got back from 3 weeks in Europe; Paris, Prague, Munich, Vienna and some small towns, my sleep schedule is all screwed up. I just want to give you a quick idea of the problem, then off to bed. We will try to work together to get this resolved for good; for now it appears to be a simple problem. You have to replace a driver
Productname: GEARAspi
Description: Filter Driver for 2k and XP
Company: GEAR Software
Tomorrow morning, I will give you a good analysis, answer all questions and get you going again.
You will notice that the driver is so old, it is classified for XP use.
Dont worry about the questions; I enjoy helping. Trust me it is very enjoyable working with you, it is like working with a friend.

Code:

Microsoft (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\Windows_NT6_BSOD_jcgriff2\Mini102510-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6002.18267.x86fre.vistasp2_gdr.100608-0458
Machine Name:
Kernel base = 0x84633000 PsLoadedModuleList = 0x8474ac70
Debug session time: Mon Oct 25 07:26:58.783 2010 (GMT-4)
System Uptime: 0 days 4:13:48.523
Loading Kernel Symbols
...............................................................
................................................................
.........................................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 9F, {3, 87d47390, 88462370, 87479bb8}
*** WARNING: Unable to verify timestamp for GEARAspiWDM.sys
*** ERROR: Module load completed but symbols could not be loaded for GEARAspiWDM.sys
Probably caused by : GEARAspiWDM.sys
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 00000003, A device object has been blocking an Irp for too long a time
Arg2: 87d47390, Physical Device Object of the stack
Arg3: 88462370, Functional Device Object of the stack
Arg4: 87479bb8, The blocked IRP
Debugging Details:
------------------
 
DRVPOWERSTATE_SUBCODE:  3
IRP_ADDRESS:  87479bb8
DEVICE_OBJECT: 88462370
DRIVER_OBJECT: 88454c40
IMAGE_NAME:  GEARAspiWDM.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  4a1151b5
MODULE_NAME: GEARAspiWDM
FAULTING_MODULE: 92988000 GEARAspiWDM
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
CURRENT_IRQL:  2
LAST_CONTROL_TRANSFER:  from 846643fb to 84700b8d
STACK_TEXT:  
84728acc 846643fb 0000009f 00000003 87d47390 nt!KeBugCheckEx+0x1e
84728b28 84664018 84728b94 84728c50 00000001 nt!PopCheckIrpWatchdog+0x1ad
84728b68 846dd30b 847414e0 00000000 896d0630 nt!PopCheckForIdleness+0x343
84728c88 846dcecb 84728cd0 8cbb4b02 84728cd8 nt!KiTimerListExpire+0x367
84728ce8 846dd635 00000000 00000000 000ee534 nt!KiTimerExpiration+0x22a
84728d50 846db89d 00000000 0000000e 00000000 nt!KiRetireDpcList+0xba
84728d54 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x49
 
STACK_COMMAND:  kb
FOLLOWUP_NAME:  MachineOwner
FAILURE_BUCKET_ID:  0x9F_IMAGE_GEARAspiWDM.sys
BUCKET_ID:  0x9F_IMAGE_GEARAspiWDM.sys
Followup: MachineOwner
---------
0: kd> lmtsmn
start    end        module name
8c692000 8c6d8000   acpi     acpi.sys     Sat Apr 11 00:19:03 2009 (49E01A37)
92966000 9296e000   Afc      Afc.sys      Wed Feb 23 01:58:55 2005 (421C29AF)
935ae000 935f6000   afd      afd.sys      Sat Apr 11 00:47:01 2009 (49E020C5)
94b6c000 94b6eb00   aswFsBlk aswFsBlk.SYS Tue Sep 07 10:47:05 2010 (4C865069)
94b35000 94b6c000   aswMonFlt aswMonFlt.sys Tue Sep 07 10:47:28 2010 (4C865080)
93600000 93604100   aswRdr   aswRdr.SYS   Tue Sep 07 10:47:44 2010 (4C865090)
93c63000 93c89c80   aswSP    aswSP.SYS    Tue Sep 07 10:52:01 2010 (4C865191)
93590000 93599c00   aswTdi   aswTdi.SYS   Tue Sep 07 10:52:23 2010 (4C8651A7)
8c7d7000 8c7df000   atapi    atapi.sys    Sat Apr 11 00:39:09 2009 (49E01EED)
8c7df000 8c7fd000   ataport  ataport.SYS  Sat Apr 11 00:39:10 2009 (49E01EEE)
8c722000 8c72c000   BATTC    BATTC.SYS    Sat Jan 19 00:32:45 2008 (47918B7D)
92bdf000 92bf0000   bcm4sbxp bcm4sbxp.sys Wed Jun 14 17:02:02 2006 (4490794A)
937da000 937e1000   Beep     Beep.SYS     Sat Jan 19 00:49:10 2008 (47918F56)
80689000 80691000   BOOTVID  BOOTVID.dll  Sat Jan 19 02:27:15 2008 (4791A653)
a3899000 a38b2000   bowser   bowser.sys   Sat Jan 19 00:28:26 2008 (47918A7A)
93cbb000 93cc7c00   BrSerIf  BrSerIf.sys  Thu Jan 22 23:59:04 2009 (49794E98)
93cb8000 93cbae80   BrUsbSer BrUsbSer.sys Sat Sep 02 20:53:37 2006 (44FA2791)
9b060000 9b06e000   cdd      cdd.dll      unavailable (00000000)
a39ce000 a39e4000   cdfs     cdfs.sys     Sat Jan 19 00:28:02 2008 (47918A62)
9296e000 92986000   cdrom    cdrom.sys    Sat Apr 11 00:39:17 2009 (49E01EF5)
806d2000 807b2000   CI       CI.dll       Sat Apr 11 02:25:22 2009 (49E037D2)
8cddd000 8cdfe000   CLASSPNP CLASSPNP.SYS Sat Apr 11 00:39:05 2009 (49E01EE9)
80691000 806d2000   CLFS     CLFS.SYS     Sat Apr 11 00:13:51 2009 (49E018FF)
92a00000 92a03780   CmBatt   CmBatt.sys   Sat Jan 19 00:32:47 2008 (47918B7F)
8c71f000 8c721900   compbatt compbatt.sys Sat Jan 19 00:32:47 2008 (47918B7F)
94ae1000 94aee000   crashdmp crashdmp.sys Sat Apr 11 00:39:12 2009 (49E01EF0)
8cb75000 8cb7e000   crcdisk  crcdisk.sys  Thu Nov 02 04:52:27 2006 (4549B1CB)
93c4c000 93c63000   dfsc     dfsc.sys     Sat Apr 11 00:14:12 2009 (49E01914)
8cdcc000 8cddd000   disk     disk.sys     Sat Apr 11 00:39:14 2009 (49E01EF2)
92919000 92923000   DKbFltr  DKbFltr.sys  Thu Oct 19 04:24:28 2006 (4537363C)
93c3e000 93c41380   DPortIO  DPortIO.sys  Fri Dec 23 03:13:04 2005 (43ABB190)
934d5000 934fa000   drmk     drmk.sys     Sat Jan 19 01:53:02 2008 (47919E4E)
94af9000 94b01000   dump_atapi dump_atapi.sys Sat Apr 11 00:39:09 2009 (49E01EED)
94aee000 94af9000   dump_dumpata dump_dumpata.sys Sat Apr 11 00:39:09 2009 (49E01EED)
94b01000 94b0b000   Dxapi    Dxapi.sys    Sat Jan 19 00:36:12 2008 (47918C4C)
9253b000 925dc000   dxgkrnl  dxgkrnl.sys  Thu Sep 24 21:27:14 2009 (4ABC1C72)
8cda5000 8cdcc000   ecache   ecache.sys   Sat Apr 11 00:40:12 2009 (49E01F2C)
92bf0000 92bff300   EMS7SK   EMS7SK.sys   Wed Oct 25 02:36:34 2006 (453F05F2)
928fb000 92905500   ESD7SK   ESD7SK.sys   Wed Oct 25 02:36:47 2006 (453F05FF)
928e8000 928fac80   ESM7SK   ESM7SK.sys   Wed Oct 25 02:36:42 2006 (453F05FA)
807e4000 807f4000   fileinfo fileinfo.sys Sat Jan 19 00:34:27 2008 (47918BE3)
807b2000 807e4000   fltmgr   fltmgr.sys   Sat Apr 11 00:13:59 2009 (49E01907)
937ca000 937d3000   Fs_Rec   Fs_Rec.SYS   Sat Jan 19 00:27:57 2008 (47918A5D)
8caef000 8cb0a000   fwpkclnt fwpkclnt.sys Sat Apr 11 00:45:42 2009 (49E02076)
[B]92988000 9298d280   GEARAspiWDM GEARAspiWDM.sys Mon May 18 08:16:53 2009[/B] (4A1151B5)
84600000 84633000   hal      halmacpi.dll Sat Apr 11 00:13:13 2009 (49E018D9)
92803000 92890000   HDAudBus HDAudBus.sys Sat Apr 11 00:42:41 2009 (49E01FC1)
92991000 929a1000   HIDCLASS HIDCLASS.SYS Sat Apr 11 00:42:47 2009 (49E01FC7)
929a1000 929a7380   HIDPARSE HIDPARSE.SYS Sat Jan 19 00:53:16 2008 (4791904C)
93cdd000 93ce6000   hidusb   hidusb.sys   Sat Apr 11 00:42:48 2009 (49E01FC8)
93709000 937bd000   HSX_CNXT HSX_CNXT.sys Wed Nov 08 18:53:45 2006 (45526E09)
93606000 93709000   HSX_DPV  HSX_DPV.sys  Wed Nov 08 18:55:07 2006 (45526E5B)
934fa000 93537000   HSXHWAZL HSXHWAZL.sys Wed Nov 08 18:53:56 2006 (45526E14)
a380f000 a387c000   HTTP     HTTP.sys     Sat Feb 20 15:53:31 2010 (4B804BCB)
92906000 92919000   i8042prt i8042prt.sys Sat Jan 19 00:49:17 2008 (47918F5D)
a39e4000 a39f5000   int15    int15.sys    Wed Oct 01 01:29:49 2003 (3F7A664D)
8c785000 8c78c000   intelide intelide.sys Sat Jan 19 00:49:42 2008 (47918F76)
8cbb2000 8cbc1000   intelppm intelppm.sys Sat Jan 19 00:27:20 2008 (47918A38)
93d96000 93da8000   ipfltdrv ipfltdrv.sys Sat Jan 19 00:56:23 2008 (47919107)
94b81000 94b9f000   irda     irda.sys     Sat Jan 19 00:55:25 2008 (479190CD)
92923000 9292e000   kbdclass kbdclass.sys Sat Jan 19 00:49:14 2008 (47918F5A)
93162000 9316b000   kbdhid   kbdhid.sys   Sat Apr 11 00:38:40 2009 (49E01ED0)
80601000 80608000   kdcom    kdcom.dll    Sat Apr 11 02:25:29 2009 (49E037D9)
930dc000 93106000   ks       ks.sys       Sat Apr 11 00:38:47 2009 (49E01ED7)
8c803000 8c874000   ksecdd   ksecdd.sys   Mon Jun 15 08:48:53 2009 (4A364335)
94b9f000 94baf000   lltdio   lltdio.sys   Sat Jan 19 00:55:03 2008 (479190B7)
94b1a000 94b35000   luafv    luafv.sys    Sat Jan 19 00:30:35 2008 (47918AFB)
a6327000 a632ba80   LVPr2Mon LVPr2Mon.sys Fri May 07 21:36:25 2010 (4BE4C019)
94a9d000 94ae0480   lvrs     lvrs.sys     Tue Jul 27 03:59:44 2010 (4C4E91F0)
94406000 94a8ae00   lvuvc    lvuvc.sys    Tue Jul 27 04:00:04 2010 (4C4E9204)
80608000 80678000   mcupdate_GenuineIntel mcupdate_GenuineIntel.dll Sat Apr 11 02:23:19 2009 (49E03757)
a39f5000 a39f8180   mdmxsdk  mdmxsdk.sys  Mon Jun 19 17:26:59 2006 (449716A3)
937bd000 937ca000   modem    modem.sys    Sat Jan 19 00:57:16 2008 (4791913C)
94b0b000 94b1a000   monitor  monitor.sys  Sat Jan 19 00:52:19 2008 (47919013)
9295b000 92966000   mouclass mouclass.sys Sat Jan 19 00:49:14 2008 (47918F5A)
93152000 9315a000   mouhid   mouhid.sys   Sat Jan 19 00:49:16 2008 (47918F5C)
8c7c7000 8c7d7000   mountmgr mountmgr.sys Sat Jan 19 00:49:13 2008 (47918F59)
a38b2000 a38c7000   mpsdrv   mpsdrv.sys   Sat Jan 19 00:54:45 2008 (479190A5)
a38c7000 a38e8000   mrxdav   mrxdav.sys   Sat Apr 11 00:14:39 2009 (49E0192F)
a38e8000 a3907000   mrxsmb   mrxsmb.sys   Tue Feb 23 06:10:12 2010 (4B83B794)
a3907000 a3940000   mrxsmb10 mrxsmb10.sys Tue Feb 23 06:10:17 2010 (4B83B799)
a3940000 a3958000   mrxsmb20 mrxsmb20.sys Tue Feb 23 06:10:12 2010 (4B83B794)
93558000 93563000   Msfs     Msfs.SYS     Sat Jan 19 00:28:08 2008 (47918A68)
8c6e1000 8c6e9000   msisadrv msisadrv.sys Sat Jan 19 00:32:51 2008 (47918B83)
929aa000 929d9000   msiscsi  msiscsi.sys  Sat Apr 11 00:40:07 2009 (49E01F27)
8c97f000 8c9aa000   msrpc    msrpc.sys    Sat Apr 11 00:37:32 2009 (49E01E8C)
93106000 93110000   mssmbios mssmbios.sys Sat Jan 19 00:32:55 2008 (47918B87)
8cd96000 8cda5000   mup      mup.sys      Sat Apr 11 00:14:12 2009 (49E01914)
8c874000 8c97f000   ndis     ndis.sys     Sat Apr 11 00:45:52 2009 (49E02080)
93064000 9306f000   ndistapi ndistapi.sys Sat Jan 19 00:56:24 2008 (47919108)
94bd9000 94be3000   ndisuio  ndisuio.sys  Sat Jan 19 00:55:40 2008 (479190DC)
9306f000 93092000   ndiswan  ndiswan.sys  Sat Apr 11 00:46:31 2009 (49E020A7)
9316b000 9317c000   NDProxy  NDProxy.SYS  Sat Jan 19 00:56:28 2008 (4791910C)
931d0000 931de000   netbios  netbios.sys  Sat Jan 19 00:55:45 2008 (479190E1)
9317c000 931ae000   netbt    netbt.sys    Sat Apr 11 00:45:35 2009 (49E0206F)
8c9aa000 8c9e5000   NETIO    NETIO.SYS    Sat Apr 11 00:46:21 2009 (49E0209D)
92a04000 92bc5000   NETw3v32 NETw3v32.sys Mon Oct 30 13:42:26 2006 (45463982)
93563000 93571000   Npfs     Npfs.SYS     Sat Apr 11 00:14:01 2009 (49E01909)
93c42000 93c4c000   nsiproxy nsiproxy.sys Sat Jan 19 00:55:50 2008 (479190E6)
84633000 849ec000   nt       ntkrpamp.exe Tue Jun 08 10:36:44 2010 (4C0E557C)
8cc03000 8cd13000   Ntfs     Ntfs.sys     Sat Apr 11 00:14:34 2009 (49E0192A)
92986000 92987800   NTIDrvr  NTIDrvr.sys  Tue Dec 21 15:33:14 2004 (41C8888A)
937d3000 937da000   Null     Null.SYS     Sat Jan 19 00:49:12 2008 (47918F58)
91e09000 9253b000   nvlddmkm nvlddmkm.sys Fri Jan 30 13:05:03 2009 (4983414F)
94baf000 94bd9000   nwifi    nwifi.sys    Sat Apr 11 00:43:27 2009 (49E01FEF)
931ae000 931c4000   pacer    pacer.sys    Sat Apr 11 00:45:51 2009 (49E0207F)
8c710000 8c71f000   partmgr  partmgr.sys  Sat Apr 11 00:39:19 2009 (49E01EF7)
8c6e9000 8c710000   pci      pci.sys      Sat Apr 11 00:19:16 2009 (49E01A44)
8c78c000 8c79a000   PCIIDEX  PCIIDEX.SYS  Sat Apr 11 00:39:09 2009 (49E01EED)
8c79a000 8c7c7000   pcmcia   pcmcia.sys   Sat Apr 11 00:19:14 2009 (49E01A42)
a6204000 a62e2000   peauth   peauth.sys   Mon Oct 23 04:55:32 2006 (453C8384)
934a8000 934d5000   portcls  portcls.sys  Sat Apr 11 00:42:48 2009 (49E01FC8)
8c600000 8c609000   psdfilter psdfilter.sys Sun Dec 24 23:20:44 2006 (458F519C)
8cd8d000 8cd96000   PSDNServ PSDNServ.sys Sun Dec 24 23:20:44 2006 (458F519C)
8cd7b000 8cd8d000   psdvdisk psdvdisk.sys Sun Dec 24 23:20:48 2006 (458F51A0)
80678000 80689000   PSHED    PSHED.dll    Sat Apr 11 02:25:32 2009 (49E037DC)
931c4000 931d0000   pssdk42  pssdk42.sys  Tue Jun 23 08:14:40 2009 (4A40C730)
8cd74000 8cd7b000   pssnap   pssnap.sys   Tue Sep 28 09:03:20 2010 (4CA1E798)
807f4000 807fcdc0   PxHelp20 PxHelp20.sys Wed Oct 17 14:24:26 2007 (4716535A)
93571000 9357a000   rasacd   rasacd.sys   Sat Jan 19 00:56:31 2008 (4791910F)
9304d000 93064000   rasl2tp  rasl2tp.sys  Sat Jan 19 00:56:33 2008 (47919111)
93092000 930a1000   raspppoe raspppoe.sys Sat Apr 11 00:46:30 2009 (49E020A6)
930a1000 930b5000   raspptp  raspptp.sys  Sat Jan 19 00:56:34 2008 (47919112)
930b5000 930ca000   rassstp  rassstp.sys  Sat Apr 11 00:46:40 2009 (49E020B0)
93c02000 93c3e000   rdbss    rdbss.sys    Sat Apr 11 00:14:26 2009 (49E01922)
937ed000 937f5000   RDPCDD   RDPCDD.sys   Sat Jan 19 01:01:08 2008 (47919224)
937f5000 937fd000   rdpencdd rdpencdd.sys Sat Jan 19 01:01:09 2008 (47919225)
a6343000 a6376000   RDPWD    RDPWD.SYS    Sat Apr 11 00:51:22 2009 (49E021CA)
94be3000 94bf6000   rspndr   rspndr.sys   Sat Jan 19 00:55:03 2008 (479190B7)
93201000 934a7700   RTKVHDA  RTKVHDA.sys  Tue Oct 27 23:36:33 2009 (4AE7BC41)
935f6000 935fc000   SASDIFSV SASDIFSV.SYS Wed Feb 17 13:19:19 2010 (4B7C3327)
929d9000 929fb000   SASKUTIL SASKUTIL.SYS Mon May 10 13:15:22 2010 (4BE83F2A)
928ce000 928e8000   sdbus    sdbus.sys    Sat Apr 11 00:19:14 2009 (49E01A42)
a62e2000 a62ec000   secdrv   secdrv.SYS   Wed Sep 13 09:18:32 2006 (45080528)
9359a000 935ae000   smb      smb.sys      Sat Apr 11 00:45:22 2009 (49E02062)
8cd54000 8cd73280   snman380 snman380.sys Wed Nov 19 19:23:37 2008 (4924AE09)
8cd4c000 8cd54000   spldr    spldr.sys    Thu Jun 21 20:29:17 2007 (467B17DD)
93ce6000 93d96000   spsys    spsys.sys    Tue Mar 10 13:10:28 2009 (49B69F04)
a3980000 a39ce000   srv      srv.sys      Mon Sep 06 09:45:36 2010 (4C84F080)
a3958000 a3980000   srv2     srv2.sys     Mon Sep 06 09:45:21 2010 (4C84F071)
a387c000 a3899000   srvnet   srvnet.sys   Mon Sep 06 09:45:18 2010 (4C84F06E)
93001000 93042000   storport storport.sys Sat Apr 11 00:39:19 2009 (49E01EF7)
930da000 930db380   swenum   swenum.sys   Sat Jan 19 00:49:20 2008 (47918F60)
9292e000 92958380   SynTP    SynTP.sys    Mon Oct 23 13:52:26 2006 (453D015A)
8ca05000 8caef000   tcpip    tcpip.sys    Wed Jun 16 09:45:41 2010 (4C18D585)
a62ec000 a62f8000   tcpipreg tcpipreg.sys Tue Dec 08 12:26:18 2009 (4B1E8C3A)
93042000 9304d000   TDI      TDI.SYS      Sat Jan 19 00:57:10 2008 (47919136)
a632c000 a6337000   tdtcp    tdtcp.sys    Sat Jan 19 01:01:08 2008 (47919224)
9357a000 93590000   tdx      tdx.sys      Sat Apr 11 00:45:56 2009 (49E02084)
930ca000 930da000   termdd   termdd.sys   Sat Apr 11 00:51:14 2009 (49E021C2)
94b6f000 94b78340   tifsfilt tifsfilt.sys Wed Aug 29 08:37:17 2007 (46D5687D)
8cb0a000 8cb74380   timntr   timntr.sys   Wed Aug 29 08:13:12 2007 (46D562D8)
9b040000 9b049000   TSDDD    TSDDD.dll    unavailable (00000000)
a6337000 a6343000   tssecsrv tssecsrv.sys Sat Jan 19 01:01:15 2008 (4791922B)
8cba9000 8cbb2000   tunmp    tunmp.sys    Sat Jan 19 00:55:40 2008 (479190DC)
8cb9e000 8cba9000   tunnel   tunnel.sys   Thu Feb 18 06:28:13 2010 (4B7D244D)
93110000 9311d000   umbus    umbus.sys    Sat Jan 19 00:53:40 2008 (47919064)
94a8b000 94a9ce00   usbaudio usbaudio.sys Sat Apr 11 00:42:54 2009 (49E01FCE)
93c8a000 93ca1000   usbccgp  usbccgp.sys  Sat Jan 19 00:53:29 2008 (47919059)
92959000 9295a700   USBD     USBD.SYS     Sat Jan 19 00:53:17 2008 (4791904D)
92bd0000 92bdf000   usbehci  usbehci.sys  Sat Apr 11 00:42:52 2009 (49E01FCC)
9311d000 93152000   usbhub   usbhub.sys   Sat Apr 11 00:43:14 2009 (49E01FE2)
92890000 928ce000   USBPORT  USBPORT.SYS  Sat Apr 11 00:42:55 2009 (49E01FCF)
93ca1000 93cab000   usbprint usbprint.sys Sat Jan 19 01:14:40 2008 (47919550)
93cab000 93cb8000   usbscan  usbscan.sys  Sat Jan 19 01:14:09 2008 (47919531)
93cc8000 93cdd000   USBSTOR  USBSTOR.SYS  Sat Apr 11 00:42:55 2009 (49E01FCF)
92bc5000 92bd0000   usbuhci  usbuhci.sys  Sat Jan 19 00:53:20 2008 (47919050)
937e1000 937ed000   vga      vga.sys      Sat Jan 19 00:52:06 2008 (47919006)
93537000 93558000   VIDEOPRT VIDEOPRT.SYS Sat Jan 19 00:52:10 2008 (4791900A)
8c72c000 8c73b000   volmgr   volmgr.sys   Sat Jan 19 00:49:51 2008 (47918F7F)
8c73b000 8c785000   volmgrx  volmgrx.sys  Sat Apr 11 00:39:25 2009 (49E01EFD)
8cd13000 8cd4c000   volsnap  volsnap.sys  Sat Apr 11 00:39:37 2009 (49E01F09)
9315a000 93162000   wacommousefilter wacommousefilter.sys Fri Feb 16 13:12:29 2007 (45D5F40D)
9298e000 92990080   wacomvhid wacomvhid.sys Wed May 20 15:54:02 2009 (4A145FDA)
929a8000 929a9680   WacomVKHid WacomVKHid.sys Thu Feb 15 18:11:07 2007 (45D4E88B)
931de000 931f1000   wanarp   wanarp.sys   Sat Jan 19 00:56:31 2008 (4791910F)
925dc000 925e8000   watchdog watchdog.sys Sat Apr 11 00:22:43 2009 (49E01B13)
8c609000 8c685000   Wdf01000 Wdf01000.sys Sat Jan 19 00:52:21 2008 (47919015)
8c685000 8c692000   WDFLDR   WDFLDR.SYS   Sat Jan 19 00:52:19 2008 (47919013)
9ae20000 9b023000   win32k   win32k.sys   unavailable (00000000)
8cbc1000 8cbca000   wmiacpi  wmiacpi.sys  Sat Jan 19 00:32:47 2008 (47918B7F)
8c6d8000 8c6e1000   WMILIB   WMILIB.SYS   Sat Jan 19 00:53:08 2008 (47919044)
a630d000 a631f000   WUDFPf   WUDFPf.sys   Sat Jan 19 00:52:49 2008 (47919031)
a62f8000 a630c580   WUDFRd   WUDFRd.sys   Sat Jan 19 00:53:04 2008 (47919040)
a631f000 a6327000   xaudio   xaudio.sys   Fri Aug 04 20:39:09 2006 (44D3E8AD)
Unloaded modules:
94b79000 94b81000   drmkaud.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
8cb7e000 8cb8b000   crashdmp.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
8cb8b000 8cb96000   dump_ataport
    Timestamp: unavailable (00000000)
    Checksum:  00000000
8cb96000 8cb9e000   dump_atapi.s
    Timestamp: unavailable (00000000)
    Checksum:  00000000

I was a bit surprised to find the cause of your BSOD was the same as the last time you had a problem. It is the ITunes driver. If you updated the driver during our last meeting and the problem still persists, you must find a replacement for ITunes.

GEARAspiWDM.sys Mon May 18 08:16:53 2009
From your old BSOD, the driver has the same date and has not been updated.

Click to expand...

To answer one of your questions, here is a tutorial on how to replace drivers
Driver Install - Device Manager - Windows 7 Forums
This is the fastest way, but not the best. You may want to update all the drivers using the easy method and then at you convenience, maybe two a day, begin with the best method.

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/

Re: BSOD......DRIVER_POWER_STATE_FAILURE ....dammit!!!

G'day Rich,

Yeah I'd be buggered too if I was made to do all that travelling in such a short time, with the body clock playing merry hell with sleep and meal times, and I hope that your's was a better experience than Griswald Family in National Lampoon's "European Vacation".

Right, this is what I've managed to find so far;

Websites;

Search results for gearaspi and,

GEARAspiWDM.sys Windows process - What is it?





With regard to the highlighted GEARAspiWDM.sys ....is this the driver that I need to replace. I'm not very confident about this sort of messing around , but if so, how do I go about that? Or is it the GEARAspi.dll that I'm supposed to replace?

You've heard of Confucius? Well hello from Confuseceous.

Re: BSOD......DRIVER_POWER_STATE_FAILURE ....dammit!!!

I will go with you step by step then you can help yourself with other drivers
Take the company name, which I gave you
Gear Software
Put that in Google.
First entry in Google shows the company and driver updates. Click on updates.
You should come up with this page
Driver updates - GEAR Software

We are looking for.sys not .dll

Re: BSOD......DRIVER_POWER_STATE_FAILURE ....dammit!!!

Rich, me old China,

This news could save one helluva lot of stomach acid for both of us...BUT...I uninstalled iTunes about 2 months ago, or more!! So as I see it, this little swine has been sitting here on it's lone backside and creating merry hell in the meantime - Yes?

Since I no longer have iTunes, it therefore follows that I no longer need this particular driver, correct? And if so, how do I go about making sure that it's deleted? Or is it best left where it is and to go ahead and update it anyway?

Now, to try and work through that list that you so generously presented me with....over 90 of the little devils....I'll be a very old man by the time I get through that lot!!

We'll soon see what happens.

Cheers Mate.

Re: BSOD......DRIVER_POWER_STATE_FAILURE ....dammit!!!

If ITunes is gone, there is no need to update. Sometimes, when a program is removed the driver remains. Go to the driver, change the .sys to .bup. That should be the end of your troubles. If you still get BSOD's, which you should not, post in this thread. We want your computer to work as well as it can.

Always start with a system restore point, just in case.

Re: BSOD......DRIVER_POWER_STATE_FAILURE ....dammit!!!

Thanks for the advice yet again Rich, and may I just say that it's not the Computer that is deficient here, but questionably, the bloke that's sitting in front of it.....one renamed driver coming up......after a new restore point is done

OK Rich, that's all done and dusted.....and now typing with crossed fingers, but I did at least have a great 'Eureka' moment that will help immensely.

While I was in C:\Windows\System32\drivers to change the file extension to .bup, I accidentally discovered that in mousing over most of the driver file icons, details of the type of driver, Manufacturer or Company and the current version appeared. This will help me in my search to update that list you brought to my attention. Thanks.

Cheers Mate

Re: BSOD......DRIVER_POWER_STATE_FAILURE ....dammit!!!

Tony,
Do not be afraid to post as soon as you have a problem. I enjoy working with you. I get satisfaction on helping you get your computer up to par.

Re: BSOD......DRIVER_POWER_STATE_FAILURE ....dammit!!!

Hey Rich,

Mate, thanks for everything so far, but I've got to ask....the file extension '.bup', you gave me to disable the iTunes driver that was surplus to requirements, does that apply to any given situation where the disabling of a driver is called for?

Tell you why. Two drivers found so far in the 'List of Dishonour' , timntr.sys and tifsfilt.sys are a part of Acronis software I once had, but in disgust threw out in favour of Macrium Reflect. The Acronis website advises uninstall or buy [?] new, so the solution for these two is quite clear, 'cos I'm not buying anything that I'm not ever going to use.

So is it reasonable to assume that I can go to the System 32 Folder, locate the offenders and change their extensions, so disabling them? And can that apply in all other similar cases?

Besides, is there a set procedure to follow to actually uninstall specific [such as these] drivers??

Cheers Mate.

Re: BSOD......DRIVER_POWER_STATE_FAILURE ....dammit!!!

Drivers should be uninstalled
http://www.vistax64.com/tutorials/171469-uninstall-device-device-driver.html
In situations such as this, ITunes is gone, you can uninstall manually, or use the .bup extension. In this case I prefer the .bup. Until your computer is up to your expectations, I do not know what we will have to do to repair. For safety, I prefer to keep the driver for now, with the bup. If needed we can always put the .sys back.
For the two drivers in question, you can get rid of them, after you make a system restore point. I would just use the .bup for now. If you use the machine and there are no problems you can just uninstall. This is a safety factor just to be sure that the drivers are not needed.
I have included a tut to show you how to uninstall.

Good luck Tony.