BSOD DRIVER_POWER_STATE_FAILURE Acer5920

[mark1961]

Hi this is my first post here, but I'm getting desperate....

My son runs a Vista Ultimate 32bit on an Acer 5920G since Feb 2008 (so "brand new"). This has worked OK for a while but we recently experienced frequent BSOD with "Driver_Power_Status_Failed". We have done SP1 (as I thought it might be because of that), and following updates via Windows Update manager), and I have installed a new/updated Video driver for the NVidia Geforce 7800 card (as indicated on Acer website – other drivers also available, but not yet done), but still the same.

Also, when he tries to start Windows Live messenger (you know kids like msn…) it does not start…. Sometimes Windows IE7 starts slow as well (takes a while to start).

The message we get when the system restarts is a BCCode of 9F.:

Probleemhandtekening:

Gebeurtenisnaam van probleem: BlueScreen

Versie van besturingssysteem: 6.0.6001.2.1.0.256.1

Landinstelling-id: 2067

Aanvullende informatie over dit probleem:

BCCode: 9f

BCP1: 00000003

BCP2: 8DDFF030

BCP3: 90018028

BCP4: A593DE28

OS Version: 6_0_6001

Service Pack: 1_0

Product: 256_1

Bestanden die helpen bij het beschrijven van het probleem:

C:\Windows\Minidump\Mini060808-02.dmp

C:\Users\Olivier\AppData\Local\Temp\WER-66799-0.sysdata.xml

C:\Users\Olivier\AppData\Local\Temp\WER99ED.tmp.version.txt

Can anybody advise on this? I cannot attach the minidump, asI'm on the work and the PC is at home. When I try to read the dump (or one that is attached in some posts, I'm not able to read them; is there a tool to use for?).

Thanks a lot.

Mark;

[cluberti]

You can open the dump with windbg, from the debugging tools for windows package. If you can place the .dmp files (zipped or rar'ed) on a file download or FTP site, that would be good too.

[mark1961]

Hi Clberti,

thanks for your quixck reply. I attach the mini-dump files from yetserday and today.

I downloaded the debuggertool fro windws ion my XP machine (Windbg6.9.0003.113x86) but I'm not sure this is the right version fror my XP machine (when I try to open a dmp file with ope crash dump, I get errormessags in the file like this:

Loading Dump File [C:\D-drive\MRK_temp\olivier\ACER 5920\dump\Mini060808-02.dmp]

Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: *** Invalid ***

****************************************************************************

* Symbol loading may be unreliable without a symbol search path. *

* Use .symfix to have the debugger choose a symbol path. *

* After setting your symbol path, use .reload to refresh symbol locations. *

****************************************************************************

Executable search path is:

*********************************************************************

* Symbols can not be loaded because symbol path is not initialized. *

* *

* The Symbol Path can be set by: *

* using the _NT_SYMBOL_PATH environment variable. *

* using the -y <symbol_path> argument when starting the debugger. *

* using .sympath and .sympath+ *

*********************************************************************

Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2

so I cannot myself start investigating things.

Looking forward to some suggestions (solution?) from your side.

Thanks in advance.

Mark

dump.zip

[CoffeeFiend]

Your crashes are being caused by snp2uvc.sys (usb2 webcam driver).

[cluberti]

according to the minidumps, it certainly looks like you're having issues with this webcam driver suite (at least it looks like it's a webcam driver suite).

Is it Vista certified? Doesn't look like it from the driver signature, but maybe the vendor has a version that is?

// Looks like a 9f bugcheck, like you stated:
0: kd> .bugcheck
Bugcheck code 0000009F
Arguments 00000003 8d7596f0 8e1a5028 ab19ca30

// according to the help on a 9f, these mean:
00000003 == A device object has been blocking an Irp for too long a time
8d7596f0 == Physical Device Object of the stack
8e1a5028 == Functional Device Object of the stack
ab19ca30 == The blocked IRP

// So this is a blocking IRP timeout, the stack matches:
0: kd> kb
ChildEBP RetAddr  Args to Child			  
81f33acc 81e71b6c 0000009f 00000003 8d7596f0 nt!KeBugCheckEx+0x1e
81f33b28 81e716bc 81f33b94 81f33c50 81f4c401 nt!PopCheckIrpWatchdog+0x1ad
81f33b68 81ef4d00 81f4c4e0 00000000 b6981718 nt!PopCheckForIdleness+0x343
81f33c88 81ef4936 81f33cd0 a628d902 81f33cd8 nt!KiTimerListExpire+0x367
81f33ce8 81ef4483 00000000 00000000 0000b159 nt!KiTimerExpiration+0x2a0
81f33d50 81ef2f9d 00000000 0000000e 00000000 nt!KiRetireDpcList+0xba
81f33d54 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x49

// Tracked down the device object in the stack:
0: kd> !devobj ffffffff8e1a5028 f
Device object (8e1a5028) is for:
 \Driver\SNP2UVC DriverObject 8e171a40
Current Irp 00000000 RefCount 0 Type 0000002f Flags 00002050
DevExt 8e1a50e0 DevObjExt 8e1a71f8 
Device queue is not busy.

// The driver object involved, looks like it's also relying on ks.sys and STREAM.sys,
// so it's a kernel streaming driver of some sort:
0: kd> !drvobj ffffffff8e171a40 f
Driver object (8e171a40) is for:
 \Driver\SNP2UVC
Driver Extension List: (id , addr)

Device Object list:
8e1a5028  

DriverEntry:   909b5b85	snp2uvc
DriverStartIo: 00000000	
DriverUnload:  8d4d4599	ks
AddDevice:	 00000000	

Dispatch routines:
[00] IRP_MJ_CREATE					  8d4cd0f4	ks+0x140f4
[01] IRP_MJ_CREATE_NAMED_PIPE		   81e63fef	nt!IopInvalidDeviceRequest
[02] IRP_MJ_CLOSE					   8d4c7265	ks+0xe265
[03] IRP_MJ_READ						81e63fef	nt!IopInvalidDeviceRequest
[04] IRP_MJ_WRITE					   81e63fef	nt!IopInvalidDeviceRequest
[05] IRP_MJ_QUERY_INFORMATION		   81e63fef	nt!IopInvalidDeviceRequest
[06] IRP_MJ_SET_INFORMATION			 81e63fef	nt!IopInvalidDeviceRequest
[07] IRP_MJ_QUERY_EA					81e63fef	nt!IopInvalidDeviceRequest
[08] IRP_MJ_SET_EA					  81e63fef	nt!IopInvalidDeviceRequest
[09] IRP_MJ_FLUSH_BUFFERS			   909baf2a	STREAM+0x1f2a
[0a] IRP_MJ_QUERY_VOLUME_INFORMATION	81e63fef	nt!IopInvalidDeviceRequest
[0b] IRP_MJ_SET_VOLUME_INFORMATION	  81e63fef	nt!IopInvalidDeviceRequest
[0c] IRP_MJ_DIRECTORY_CONTROL		   81e63fef	nt!IopInvalidDeviceRequest
[0d] IRP_MJ_FILE_SYSTEM_CONTROL		 81e63fef	nt!IopInvalidDeviceRequest
[0e] IRP_MJ_DEVICE_CONTROL			  909baf2a	STREAM+0x1f2a
[0f] IRP_MJ_INTERNAL_DEVICE_CONTROL	 81e63fef	nt!IopInvalidDeviceRequest
[10] IRP_MJ_SHUTDOWN					81e63fef	nt!IopInvalidDeviceRequest
[11] IRP_MJ_LOCK_CONTROL				81e63fef	nt!IopInvalidDeviceRequest
[12] IRP_MJ_CLEANUP					 909bb1b2	STREAM+0x21b2
[13] IRP_MJ_CREATE_MAILSLOT			 81e63fef	nt!IopInvalidDeviceRequest
[14] IRP_MJ_QUERY_SECURITY			  81e63fef	nt!IopInvalidDeviceRequest
[15] IRP_MJ_SET_SECURITY				81e63fef	nt!IopInvalidDeviceRequest
[16] IRP_MJ_POWER					   909bbcee	STREAM+0x2cee
[17] IRP_MJ_SYSTEM_CONTROL			  909c02c0	STREAM+0x72c0
[18] IRP_MJ_DEVICE_CHANGE			   81e63fef	nt!IopInvalidDeviceRequest
[19] IRP_MJ_QUERY_QUOTA				 81e63fef	nt!IopInvalidDeviceRequest
[1a] IRP_MJ_SET_QUOTA				   81e63fef	nt!IopInvalidDeviceRequest
[1b] IRP_MJ_PNP						 909c0fd2	STREAM+0x7fd2

// The actual IRP blocking:
0: kd> !irp ab19ca30
Irp is active with 9 stacks 8 is current (= 0xab19cb9c)
 No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  Pending has been returned
	 cmd  flg cl Device   File	 Completion-Context
 [  0, 0]   0  0 00000000 00000000 00000000-00000000	

			Args: 00000000 00000000 00000000 00000000
 [  0, 0]   0  0 00000000 00000000 00000000-00000000	

			Args: 00000000 00000000 00000000 00000000
 [  0, 0]   0  0 00000000 00000000 00000000-00000000	

			Args: 00000000 00000000 00000000 00000000
 [  0, 0]   0  0 00000000 00000000 00000000-00000000	

			Args: 00000000 00000000 00000000 00000000
 [  0, 0]   0  0 00000000 00000000 00000000-00000000	

			Args: 00000000 00000000 00000000 00000000
 [  0, 0]   0  0 00000000 00000000 00000000-00000000	

			Args: 00000000 00000000 00000000 00000000
 [ 16, 0]   0  0 8d7596f0 00000000 909bb79a-00000000	
		   \Driver\usbhub	STREAM
			Args: 00000000 00000000 00000000 00000000
>[ 16, 2]   0 e1 8e1a5028 00000000 81e42db4-845b2120 Success Error Cancel pending
		   \Driver\SNP2UVC	nt!PopRequestCompletion
			Args: 00000000 00000001 00000001 00000000
 [  0, 0]   0  0 00000000 00000000 00000000-845b2120	

			Args: 00000000 00000000 00000000 00000000

// Webcam, maybe?:
0: kd> lmvm snp2uvc
start	end		module name
90812000 909b8280   snp2uvc  T (no symbols)		   
	Loaded symbol image file: snp2uvc.sys
	Image path: \SystemRoot\system32\DRIVERS\snp2uvc.sys
	Image name: snp2uvc.sys
	Timestamp:		Mon Jun 11 22:38:23 2007 (466E071F)
	CheckSum:		 001AEC22
	ImageSize:		001A6280
	Translations:	 0000.04b0 0000.04e0 0409.04b0 0409.04e0

This could be related to the issue documented in 950127 as well, so you might want to apply that hotfix too. However, the root is likely the snp2uvc.sys driver. A quick google search for that driver also shows that you aren't the only one seeing this, and it's definitely this driver. Hopefully you don't have an Asus box .

[mark1961]

Hi both,

thanks for the information. The webcam is actually a built-in webcam in teh ACER 5920G Laptop. I'll check the ACER website too.

How can one see the drivers are Vista certified? It used to work OK....

Thx.

Mark.

[mark1961]

Hi Cluberti and Crahak,

Thank you both for the info.

I did a search on Google for drivers, but was not immediately able to find an updated version of the driver, but as you said some pages with similar problems.

I guess I need to check at home on the laptop for the right manufacturer.

I kooked at the ACER webstie for updated drivers (http://support.acer-euro.com/drivers/notebook/as_5920.html ) but could not find any related to the webcam.

I had e-maile the Acer support site describing the problem, and they just mailed back 1 hour ago saying I need to reset the PC into manufacturer mode (i.e press ALT+F10 when restarting). This procedures erases the C-partition and resets everything into "1 time use". Of course that is always a "nice try" but not sure this would help (what if I re-install SP1?).

So I called the BeNeLux technical support line. I explained that on the msfn forum I received the message that the USB2 driver for the webcam might be the issue and they than said they will collect the Laptop fro repair….

So not sure what to do… follow the patches route or just sent in for repair (anyway under guarantee…).

Any clue? Also where to find updated drivers for the webcam?

Anyway, many thanks for the great support.

[cluberti]

As to the drivers, if the vendor doesn't have updated drivers, you're out of luck. However, if you aren't using the webcam, you could always simply remove it and uninstall any software for it.

If you need one, perhaps using a different webcam from another vendor is probably a better option than sending the laptop back for repair (what are they gonna repair!?!? the driver is bad!!!).