VISTA 32 BSOD--Help!

molon_labe · 06-23-2009, 05:28 PM

I am running Vista Ultimate, 32 Bit, Service Pack 2. I have been getting the BSOD 1-2 times a day. This just started last week. I have had 6 BSOD so far. I used WinDbg and discovered it was due to 2 different issues. I do not know how to interpret the issues, nor how to fix them. Can Someone please help?

Here is the first Dump:
Loading Kernel Symbols
...............................................................
................................................................
...................................................
Loading User Symbols
Loading unloaded module list
......................................
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: 89203030, Physical Device Object of the stack
Arg3: 89203030, Functional Device Object of the stack
Arg4: 85cee008, The blocked IRP

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

DRVPOWERSTATE_SUBCODE: 3

IRP_ADDRESS: 85cee008

DEVICE_OBJECT: 89203030

DRIVER_OBJECT: 882a4ac8

IMAGE_NAME: usbhub.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 49e01fe2

MODULE_NAME: usbhub

FAULTING_MODULE: 91721000 usbhub

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x9F

PROCESS_NAME: System

CURRENT_IRQL: 2

LAST_CONTROL_TRANSFER: from 8286a3ab to 82906b0d

STACK_TEXT:
8292eacc 8286a3ab 0000009f 00000003 89203030 nt!KeBugCheckEx+0x1e
8292eb28 82869fc8 8292eb94 8292ec50 82947401 nt!PopCheckIrpWatchdog+0x1ad
8292eb68 828e32eb 829474e0 00000000 0eb61950 nt!PopCheckForIdleness+0x343
8292ec88 828e2f21 8292ecd0 8292ed02 8292ecd8 nt!KiTimerListExpire+0x367
8292ece8 828e3615 00000000 00000000 00eaab33 nt!KiTimerExpiration+0x2a0
8292ed50 828e187d 00000000 0000000e 00000000 nt!KiRetireDpcList+0xba
8292ed54 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x49

STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

FAILURE_BUCKET_ID: 0x9F_IMAGE_usbhub.sys

BUCKET_ID: 0x9F_IMAGE_usbhub.sys

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

0: kd> lmvm usbhub
start end module name
91721000 91756000 usbhub (pdb symbols) c:\symbols\usbhub.pdb\9C123E3E318C46E591F4DEA40A1076452\usbhub.pdb
Loaded symbol image file: usbhub.sys
Mapped memory image file: c:\symbols\usbhub.sys\49E01FE235000\usbhub.sys
Image path: \SystemRoot\system32\DRIVERS\usbhub.sys
Image name: usbhub.sys
Timestamp: Fri Apr 10 21:43:14 2009 (49E01FE2)
CheckSum: 000327B5
ImageSize: 00035000
File version: 6.0.6002.18005
Product version: 6.0.6002.18005
File flags: 0 (Mask 3F)
File OS: 40004 NT Win32
File type: 2.0 Dll
File date: 00000000.00000000
Translations: 0409.04b0
CompanyName: Microsoft Corporation
ProductName: Microsoft® Windows® Operating System
InternalName: usbhub.sys
OriginalFilename: usbhub.sys
ProductVersion: 6.0.6002.18005
FileVersion: 6.0.6002.18005 (lh_sp2rtm.090410-1830)
FileDescription: Default Hub Driver for USB
LegalCopyright: © Microsoft Corporation. All rights reserved.

And here is the second dump:

Loading User Symbols
Loading unloaded module list
...............
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: 88312028, Physical Device Object of the stack
Arg3: 884de030, Functional Device Object of the stack
Arg4: 85dc0008, The blocked IRP

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

DRVPOWERSTATE_SUBCODE: 3

IRP_ADDRESS: 85dc0008

DEVICE_OBJECT: 88312028

DRIVER_OBJECT: 86d30c78

IMAGE_NAME: sbp2port.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 49e01ef4

MODULE_NAME: sbp2port

FAULTING_MODULE: 8bb52000 sbp2port

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x9F

PROCESS_NAME: firefox.exe

CURRENT_IRQL: 2

LAST_CONTROL_TRANSFER: from 828643ab to 82900b0d

STACK_TEXT:
8059dd6c 828643ab 0000009f 00000003 88312028 nt!KeBugCheckEx+0x1e
8059ddc8 82863fc8 8059de34 8059def0 8a050001 nt!PopCheckIrpWatchdog+0x1ad
8059de08 828dd2eb 829414e0 00000000 974bae50 nt!PopCheckForIdleness+0x343
8059df28 828dceab 8059df70 8292b902 8059df78 nt!KiTimerListExpire+0x367
8059df88 828dd615 00000000 00000000 00131b24 nt!KiTimerExpiration+0x22a
8059dff4 828db2d5 c426dd10 00000000 00000000 nt!KiRetireDpcList+0xba
8059dff8 c426dd10 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x45
WARNING: Frame IP not in any known module. Following frames may be wrong.
828db2d5 00000000 0000001b 00c7850f bb830000 0xc426dd10

STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

FAILURE_BUCKET_ID: 0x9F_disk.sys_CNVIRP_IMAGE_sbp2port.sys

BUCKET_ID: 0x9F_disk.sys_CNVIRP_IMAGE_sbp2port.sys

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

0: kd> lmvm sbp2port
start end module name
8bb52000 8bb68000 sbp2port (pdb symbols) c:\symbols\sbp2port.pdb\B56E331B472744D8A10FBC0F7EA2CC811\sbp2port.pdb
Loaded symbol image file: sbp2port.sys
Mapped memory image file: c:\symbols\sbp2port.sys\49E01EF416000\sbp2port.sys
Image path: \SystemRoot\system32\DRIVERS\sbp2port.sys
Image name: sbp2port.sys
Timestamp: Fri Apr 10 21:39:16 2009 (49E01EF4)
CheckSum: 00018311
ImageSize: 00016000
File version: 6.0.6002.18005
Product version: 6.0.6002.18005
File flags: 0 (Mask 3F)
File OS: 40004 NT Win32
File type: 3.7 Driver
File date: 00000000.00000000
Translations: 0000.04b0
CompanyName: Microsoft Corporation
ProductName: Microsoft® Windows® Operating System
InternalName: sbp2port.sys
OriginalFilename: sbp2port.sys
ProductVersion: 6.0.6002.18005
FileVersion: 6.0.6002.18005 (lh_sp2rtm.090410-1830)
FileDescription: SBP-2 Protocol Driver
LegalCopyright: © Microsoft Corporation. All rights reserved.

usasma · 06-24-2009, 03:52 PM

You haven't included the entire dump file (you cut off the tops).
Also, the lmvm command is helpful at times, but there's more to it than just that.

Please describe what you're doing when the crashes happen, what you think may be causing it, and anything that you've done to your system recently. This is the most important part of any diagnosis.

An analysis of the dump file is a snapshot at a point in time of the system. Here's a scenario where the dump file won't contain the info on what caused the crash:

If program A writes to memory that's owned by program B, it won't cause a crash until program B tries to use it. So program A can exit before program B accesses that memory space. When program B finally accesses that memory space it crashes because the contents of that memory space aren't what it expected to find.

I would strongly suggest that you follow the directions in this post to provide us with information about your system and the crashes: http://www.techsupportforum.com/1871981-post2.html

You can find more info about conducting the analysis' here: http://usasma.vox.com/library/post/d...d-02oct08.html
At the bottom is a link to a post where I describe (briefly) how I go about reading the analysis'

molon_labe · 06-24-2009, 06:31 PM

I did the System Info & BSOD Mini Kernel Dump File Collection you reccommended.

I was able to upload the perfmon.zip html file. I tried to upload the TSF_Vista_Support.zip file, but it is 2.4 MB. I zipped it using maximum compression. I was able to compress it into a rar file that is 1.31 MB, so I attached that. If you need zip, is there another way I can send you the zip file? I really appreciate your help. Let me know if there is any other information or files you need.

Thank you,
Larry

usasma · 06-25-2009, 05:52 AM

Nope, the RAR will work just fine (there must be a limitation on the size of files that you can upload here).

The perfmon report looks OK at first glance.
There's 7 memory dump files in the RAR file, I didn't analyze the one from Dec 08. The others are from Jun 09 and I'm running an analysis on them right now.

The majority of the bugchecks are blamed on usbhub.sys - which is the default driver that Windows uses to drive USB devices.

Dot4.sys is the IEEE-1284.4-1999 Driver and is a part of Windows

The sbp2port.sys is the SBP-2 Protocol Driver - also a part of the Windows Operating System.

So we're most likely to be looking at a device that is connected to your computer through USB or other ports. Are you using any devices like this?

Since you're updated to SP2, there could be an issue with an older driver on your system that isn't working well with SP2. So, combine this with the USB stuff and the most likely suspect is the usbdpfp.sys driver - which is related to a Fingerprint scanner. Do you have such a device on your system? If so, update the drivers for it.

The rest of the outdated drivers are listed below:

Code:

82fcb000 82fde000   DefragFS DefragFS.sys Tue Mar 13 10:55:17 2007 (45F6BB55)
83467000 83474000   nvstor   nvstor.sys   Sat Dec 23 11:07:25 2006 (458D543D)
834b5000 834d2000   nvstor32 nvstor32.sys Thu Aug 09 14:11:36 2007 (46BB58D8)
83565000 8357afe0   DRVMCDB  DRVMCDB.SYS  Fri Jul 21 14:20:31 2006 (44C11AEF)
8b912000 8b928340   DLAUDF_M DLAUDF_M.SYS Thu Oct 26 19:18:49 2006 (45414259)
8b9d7000 8b9e8000   bcm4sbxp bcm4sbxp.sys Wed Jun 14 17:02:02 2006 (4490794A)
911d2000 911d3740   DLACDBHM DLACDBHM.SYS Thu Feb 08 23:05:12 2007 (45CBF2F8)
91294000 912de000   altghle3 altghle3.SYS Sun Nov 12 05:40:09 2006 (4556FA09)
91395000 913a0900   pcouffin pcouffin.sys Fri Jun 30 09:40:17 2006 (44A529C1)
91767000 917ba000   stwrt    stwrt.sys    Sat May 05 20:40:01 2007 (463D23E1)
921c3000 921c82e0   DLARTL_M DLARTL_M.SYS Thu Feb 08 23:04:41 2007 (45CBF2D9)
95692000 9569e000   nm3      nm3.sys      Tue Jun 19 12:51:25 2007 (4678098D)
957b8000 957c3900   usbdpfp  usbdpfp.sys  Sat Sep 16 20:23:05 2006 (450C9569)
957c4000 957ccb00   dpK0Bx01 dpK0Bx01.sys Sat Sep 16 20:25:37 2006 (450C9601)
957ea000 957ff6c0   DLAUDFAM DLAUDFAM.SYS Thu Oct 26 19:19:10 2006 (4541426E)
95db8000 95dc2600   DRVNDDM  DRVNDDM.SYS  Fri Feb 09 15:33:42 2007 (45CCDAA6)
95dc3000 95dc39c0   DLADResM DLADResM.SYS Thu Oct 26 19:20:51 2006 (454142D3)
95dc4000 95ddbd60   DLAIFS_M DLAIFS_M.SYS Thu Oct 26 19:18:31 2006 (45414247)
95ddc000 95de0bc0   DLAOPIOM DLAOPIOM.SYS Thu Oct 26 19:20:03 2006 (454142A3)
95de1000 95de2dc0   DLAPoolM DLAPoolM.SYS Thu Oct 26 19:18:34 2006 (4541424A)
95de3000 95de9e20   DLABMFSM DLABMFSM.SYS Thu Oct 26 19:19:29 2006 (45414281)
95dea000 95df03e0   DLABOIOM DLABOIOM.SYS Thu Oct 26 19:19:24 2006 (4541427C)
a6600000 a6604400   wdfwhid  wdfwhid.sys  Wed Mar 22 15:37:49 2006 (4421A78D)
a66c9000 a66cad00   dsunidrv dsunidrv.sys Thu May 25 13:04:54 2006 (4475E3B6)
91294000 912de000   altghle3 altghle3.SYS Sun Nov 12 05:40:09 2006 (4556FA09)
8b9d7000 8b9e8000   bcm4sbxp bcm4sbxp.sys Wed Jun 14 17:02:02 2006 (4490794A)
82fcb000 82fde000   DefragFS DefragFS.sys Tue Mar 13 10:55:17 2007 (45F6BB55)
95de3000 95de9e20   DLABMFSM DLABMFSM.SYS Thu Oct 26 19:19:29 2006 (45414281)
95dea000 95df03e0   DLABOIOM DLABOIOM.SYS Thu Oct 26 19:19:24 2006 (4541427C)
911d2000 911d3740   DLACDBHM DLACDBHM.SYS Thu Feb 08 23:05:12 2007 (45CBF2F8)
95dc3000 95dc39c0   DLADResM DLADResM.SYS Thu Oct 26 19:20:51 2006 (454142D3)
95dc4000 95ddbd60   DLAIFS_M DLAIFS_M.SYS Thu Oct 26 19:18:31 2006 (45414247)
95ddc000 95de0bc0   DLAOPIOM DLAOPIOM.SYS Thu Oct 26 19:20:03 2006 (454142A3)
95de1000 95de2dc0   DLAPoolM DLAPoolM.SYS Thu Oct 26 19:18:34 2006 (4541424A)
921c3000 921c82e0   DLARTL_M DLARTL_M.SYS Thu Feb 08 23:04:41 2007 (45CBF2D9)
8b912000 8b928340   DLAUDF_M DLAUDF_M.SYS Thu Oct 26 19:18:49 2006 (45414259)
957ea000 957ff6c0   DLAUDFAM DLAUDFAM.SYS Thu Oct 26 19:19:10 2006 (4541426E)
957c4000 957ccb00   dpK0Bx01 dpK0Bx01.sys Sat Sep 16 20:25:37 2006 (450C9601)
83565000 8357afe0   DRVMCDB  DRVMCDB.SYS  Fri Jul 21 14:20:31 2006 (44C11AEF)
95db8000 95dc2600   DRVNDDM  DRVNDDM.SYS  Fri Feb 09 15:33:42 2007 (45CCDAA6)
a66c9000 a66cad00   dsunidrv dsunidrv.sys Thu May 25 13:04:54 2006 (4475E3B6)
95692000 9569e000   nm3      nm3.sys      Tue Jun 19 12:51:25 2007 (4678098D)
83467000 83474000   nvstor   nvstor.sys   Sat Dec 23 11:07:25 2006 (458D543D)
834b5000 834d2000   nvstor32 nvstor32.sys Thu Aug 09 14:11:36 2007 (46BB58D8)
91395000 913a0900   pcouffin pcouffin.sys Fri Jun 30 09:40:17 2006 (44A529C1)
91767000 917ba000   stwrt    stwrt.sys    Sat May 05 20:40:01 2007 (463D23E1)
957b8000 957c3900   usbdpfp  usbdpfp.sys  Sat Sep 16 20:23:05 2006 (450C9569)
a6600000 a6604400   wdfwhid  wdfwhid.sys  Wed Mar 22 15:37:49 2006 (4421A78D)

Here's a summary of the bugchecks:

Code:

Built by: 6002.18005.x86fre.lh_sp2rtm.090410-1830
Debug session time: Tue Jun  9 20:34:58.857 2009 (GMT-4)
System Uptime: 3 days 0:11:46.901
BugCheck 1000008E, {c0000005, 9257e173, b5be0b24, 0}
Probably caused by : Dot4.sys ( Dot4!GetChannelFromHandle+fd )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  hpqtra08.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 6002.18005.x86fre.lh_sp2rtm.090410-1830
Debug session time: Tue Jun 16 16:29:26.512 2009 (GMT-4)
System Uptime: 1 days 10:16:28.489
BugCheck 9F, {3, 8906f030, 8906f030, 87027428}
Probably caused by : usbhub.sys
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 6002.18005.x86fre.lh_sp2rtm.090410-1830
Debug session time: Thu Jun 18 22:48:06.501 2009 (GMT-4)
System Uptime: 1 days 10:08:55.388
BugCheck 9F, {3, 882be030, 882be030, 874fa5a0}
Probably caused by : usbhub.sys
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 6002.18005.x86fre.lh_sp2rtm.090410-1830
Debug session time: Sat Jun 20 13:25:35.500 2009 (GMT-4)
System Uptime: 0 days 17:19:41.387
BugCheck 9F, {3, 89423030, 89423030, 870729a0}
Probably caused by : usbhub.sys
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  LCDCountdown.ex
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 6002.18005.x86fre.lh_sp2rtm.090410-1830
Debug session time: Tue Jun 23 11:27:02.501 2009 (GMT-4)
System Uptime: 2 days 18:38:37.864
BugCheck 9F, {3, 89203030, 89203030, 85cee008}
Probably caused by : usbhub.sys
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 6002.18005.x86fre.lh_sp2rtm.090410-1830
Debug session time: Tue Jun 23 17:00:08.501 2009 (GMT-4)
System Uptime: 0 days 5:25:33.392
BugCheck 9F, {3, 88312028, 884de030, 85dc0008}
Probably caused by : sbp2port.sys
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  firefox.exe

molon_labe · 06-26-2009, 05:02 PM

John,
Thank you very much for your help. I have installed the latest software & driver for my Microsoft Fingerprint Reader driver (Digital Persona). So far no blue screens. I will let it go a week and if I have further problems I will just have to uninstall it.

Again, thank you,
Larry

06-23-2009, 05:28 PM	#1 (permalink)
molon_labe Registered User Join Date: Jun 2009 Posts: 3 OS: Vista 32Bit	VISTA 32 BSOD--Help! I am running Vista Ultimate, 32 Bit, Service Pack 2. I have been getting the BSOD 1-2 times a day. This just started last week. I have had 6 BSOD so far. I used WinDbg and discovered it was due to 2 different issues. I do not know how to interpret the issues, nor how to fix them. Can Someone please help? Here is the first Dump: Loading Kernel Symbols ............................................................... ................................................................ ................................................... Loading User Symbols Loading unloaded module list ...................................... 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: 89203030, Physical Device Object of the stack Arg3: 89203030, Functional Device Object of the stack Arg4: 85cee008, The blocked IRP Debugging Details: ------------------ DRVPOWERSTATE_SUBCODE: 3 IRP_ADDRESS: 85cee008 DEVICE_OBJECT: 89203030 DRIVER_OBJECT: 882a4ac8 IMAGE_NAME: usbhub.sys DEBUG_FLR_IMAGE_TIMESTAMP: 49e01fe2 MODULE_NAME: usbhub FAULTING_MODULE: 91721000 usbhub CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x9F PROCESS_NAME: System CURRENT_IRQL: 2 LAST_CONTROL_TRANSFER: from 8286a3ab to 82906b0d STACK_TEXT: 8292eacc 8286a3ab 0000009f 00000003 89203030 nt!KeBugCheckEx+0x1e 8292eb28 82869fc8 8292eb94 8292ec50 82947401 nt!PopCheckIrpWatchdog+0x1ad 8292eb68 828e32eb 829474e0 00000000 0eb61950 nt!PopCheckForIdleness+0x343 8292ec88 828e2f21 8292ecd0 8292ed02 8292ecd8 nt!KiTimerListExpire+0x367 8292ece8 828e3615 00000000 00000000 00eaab33 nt!KiTimerExpiration+0x2a0 8292ed50 828e187d 00000000 0000000e 00000000 nt!KiRetireDpcList+0xba 8292ed54 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x49 STACK_COMMAND: kb FOLLOWUP_NAME: MachineOwner FAILURE_BUCKET_ID: 0x9F_IMAGE_usbhub.sys BUCKET_ID: 0x9F_IMAGE_usbhub.sys Followup: MachineOwner --------- 0: kd> lmvm usbhub start end module name 91721000 91756000 usbhub (pdb symbols) c:\symbols\usbhub.pdb\9C123E3E318C46E591F4DEA40A1076452\usbhub.pdb Loaded symbol image file: usbhub.sys Mapped memory image file: c:\symbols\usbhub.sys\49E01FE235000\usbhub.sys Image path: \SystemRoot\system32\DRIVERS\usbhub.sys Image name: usbhub.sys Timestamp: Fri Apr 10 21:43:14 2009 (49E01FE2) CheckSum: 000327B5 ImageSize: 00035000 File version: 6.0.6002.18005 Product version: 6.0.6002.18005 File flags: 0 (Mask 3F) File OS: 40004 NT Win32 File type: 2.0 Dll File date: 00000000.00000000 Translations: 0409.04b0 CompanyName: Microsoft Corporation ProductName: Microsoft® Windows® Operating System InternalName: usbhub.sys OriginalFilename: usbhub.sys ProductVersion: 6.0.6002.18005 FileVersion: 6.0.6002.18005 (lh_sp2rtm.090410-1830) FileDescription: Default Hub Driver for USB LegalCopyright: © Microsoft Corporation. All rights reserved. And here is the second dump: Loading User Symbols Loading unloaded module list ............... 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: 88312028, Physical Device Object of the stack Arg3: 884de030, Functional Device Object of the stack Arg4: 85dc0008, The blocked IRP Debugging Details: ------------------ DRVPOWERSTATE_SUBCODE: 3 IRP_ADDRESS: 85dc0008 DEVICE_OBJECT: 88312028 DRIVER_OBJECT: 86d30c78 IMAGE_NAME: sbp2port.sys DEBUG_FLR_IMAGE_TIMESTAMP: 49e01ef4 MODULE_NAME: sbp2port FAULTING_MODULE: 8bb52000 sbp2port CUSTOMER_CRASH_COUNT: 2 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x9F PROCESS_NAME: firefox.exe CURRENT_IRQL: 2 LAST_CONTROL_TRANSFER: from 828643ab to 82900b0d STACK_TEXT: 8059dd6c 828643ab 0000009f 00000003 88312028 nt!KeBugCheckEx+0x1e 8059ddc8 82863fc8 8059de34 8059def0 8a050001 nt!PopCheckIrpWatchdog+0x1ad 8059de08 828dd2eb 829414e0 00000000 974bae50 nt!PopCheckForIdleness+0x343 8059df28 828dceab 8059df70 8292b902 8059df78 nt!KiTimerListExpire+0x367 8059df88 828dd615 00000000 00000000 00131b24 nt!KiTimerExpiration+0x22a 8059dff4 828db2d5 c426dd10 00000000 00000000 nt!KiRetireDpcList+0xba 8059dff8 c426dd10 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x45 WARNING: Frame IP not in any known module. Following frames may be wrong. 828db2d5 00000000 0000001b 00c7850f bb830000 0xc426dd10 STACK_COMMAND: kb FOLLOWUP_NAME: MachineOwner FAILURE_BUCKET_ID: 0x9F_disk.sys_CNVIRP_IMAGE_sbp2port.sys BUCKET_ID: 0x9F_disk.sys_CNVIRP_IMAGE_sbp2port.sys Followup: MachineOwner --------- 0: kd> lmvm sbp2port start end module name 8bb52000 8bb68000 sbp2port (pdb symbols) c:\symbols\sbp2port.pdb\B56E331B472744D8A10FBC0F7EA2CC811\sbp2port.pdb Loaded symbol image file: sbp2port.sys Mapped memory image file: c:\symbols\sbp2port.sys\49E01EF416000\sbp2port.sys Image path: \SystemRoot\system32\DRIVERS\sbp2port.sys Image name: sbp2port.sys Timestamp: Fri Apr 10 21:39:16 2009 (49E01EF4) CheckSum: 00018311 ImageSize: 00016000 File version: 6.0.6002.18005 Product version: 6.0.6002.18005 File flags: 0 (Mask 3F) File OS: 40004 NT Win32 File type: 3.7 Driver File date: 00000000.00000000 Translations: 0000.04b0 CompanyName: Microsoft Corporation ProductName: Microsoft® Windows® Operating System InternalName: sbp2port.sys OriginalFilename: sbp2port.sys ProductVersion: 6.0.6002.18005 FileVersion: 6.0.6002.18005 (lh_sp2rtm.090410-1830) FileDescription: SBP-2 Protocol Driver LegalCopyright: © Microsoft Corporation. All rights reserved.

06-24-2009, 03:52 PM	#2 (permalink)
usasma Tech Hardware Team Join Date: Apr 2009 Location: Southeastern CT, USA Posts: 1,591 OS: Vista (x64); Win7 (x32 & x64)	Re: VISTA 32 BSOD--Help! You haven't included the entire dump file (you cut off the tops). Also, the lmvm command is helpful at times, but there's more to it than just that. Please describe what you're doing when the crashes happen, what you think may be causing it, and anything that you've done to your system recently. This is the most important part of any diagnosis. An analysis of the dump file is a snapshot at a point in time of the system. Here's a scenario where the dump file won't contain the info on what caused the crash: If program A writes to memory that's owned by program B, it won't cause a crash until program B tries to use it. So program A can exit before program B accesses that memory space. When program B finally accesses that memory space it crashes because the contents of that memory space aren't what it expected to find. I would strongly suggest that you follow the directions in this post to provide us with information about your system and the crashes: http://www.techsupportforum.com/1871981-post2.html You can find more info about conducting the analysis' here: http://usasma.vox.com/library/post/d...d-02oct08.html At the bottom is a link to a post where I describe (briefly) how I go about reading the analysis' __________________ aka John MVP Windows - Desktop Experience "There are very few problems in life that can't be fixed by the proper application of high explosives" If I haven't replied in 48 hours, please send me a PM. Last edited by usasma; 06-24-2009 at 03:53 PM.

06-26-2009, 05:02 PM	#5 (permalink)
molon_labe Registered User Join Date: Jun 2009 Posts: 3 OS: Vista 32Bit	Re: VISTA 32 BSOD--Help! John, Thank you very much for your help. I have installed the latest software & driver for my Microsoft Fingerprint Reader driver (Digital Persona). So far no blue screens. I will let it go a week and if I have further problems I will just have to uninstall it. Again, thank you, Larry