Login    Forum    Search    FAQ

Board index » Upgrading and Repairing Forum » Windows OS




Post new topic Reply to topic  [ 8 posts ] 
Author Message
 Post subject: Shutdown involving Windows Vista Home Premium
 Post Posted: Sat Feb 05, 2011 10:17 pm 
Offline

Joined: Sat May 08, 2010 4:13 pm
Posts: 1060
Scott, my PC with Windows Vista Home Premium on it experienced a shutdown after I got it out of "sleep" mode. I know that a dump was created, and that the blue-screen message contained "BUGCODE_USB_DRIVER." Here are the problem details:

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.0.6002.2.2.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: fe
BCP1: 00000008
BCP2: 00000004
BCP3: 00000000
BCP4: 00000000
OS Version: 6_0_6002
Service Pack: 2_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\Mini020511-01.dmp
C:\Users\Chris\AppData\Local\Temp\WER-179900-0.sysdata.xml
C:\Users\Chris\AppData\Local\Temp\WERA968.tmp.version.txt


Top 
 Profile  
Reply with quote  
 Post subject: Re: Shutdown involving Windows Vista Home Premium
 Post Posted: Sat Feb 05, 2011 10:30 pm 
Offline
Site Admin

Joined: Sun Feb 04, 2007 11:44 am
Posts: 6120
The Stop 0xFE BUGCODE_USB_DRIVER bug check indicates that an error has occurred in a USB driver. There was a similar problem (for which a hotfix was available) in Vista RTM, but that hotfix was included in SP1 and later, and that problem apparently occurred when putting the system *into* sleep/hibernation.

If it was a one-time occurrence then I'd say it was just a "glitch", which can probably be ignored. But if it does reoccur or you want to track it down further, see my post on Troubleshooting Windows crashes (BSOD/Stop errors). Problems like this are often caused by a buggy or defective driver, malware or other software related issues, but it could also be a defective USB port, cable or device. Let me know what you find, Scott.


Top 
 Profile  
Reply with quote  
 Post subject: Re: Shutdown involving Windows Vista Home Premium
 Post Posted: Sat Feb 12, 2011 11:26 pm 
Offline

Joined: Sat May 08, 2010 4:13 pm
Posts: 1060
Scott, check the following stuff out:

Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\Mini020511-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*DownstreamStore*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 = 0x82840000 PsLoadedModuleList = 0x82957c70
Debug session time: Sat Feb 5 20:05:20.291 2011 (UTC - 8:00)
System Uptime: 0 days 23:21:40.866
Loading Kernel Symbols
...............................................................
................................................................
...........................................
Loading User Symbols
Loading unloaded module list
...........................................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck FE, {8, 4, 0, 0}

Probably caused by : bthport.sys ( bthport!BthDefaultPnpHandler+20 )

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

1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

BUGCODE_USB_DRIVER (fe)
USB Driver bugcheck, first parameter is USB bugcheck code.
Arguments:
Arg1: 00000008, USBBUGCODE_RESERVED_USBHUB
Arg2: 00000004, USBHUB_PDO_TRAP_FATAL
Arg3: 00000000, Context if next arg null, else PDO
Arg4: 00000000, Context if not null

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


CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xFE

PROCESS_NAME: System

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from 8fc1d984 to 8290db8d

STACK_TEXT:
8b3639fc 8fc1d984 000000fe 00000008 00000004 nt!KeBugCheckEx+0x1e
8b363a18 8fc0b584 00000000 00000000 00000000 usbhub!UsbhTrapFatal_Dbg+0x27
8b363a34 8fc256df 00000000 00000100 8a2e10e8 usbhub!FdoExt+0x18
8b363a4c 8fc30ab0 00000000 8a2e1030 8a2e146c usbhub!Usbh_PdoSurpriseRemove_PdoEvent+0x11
8b363a6c 8fc0d654 8a2e1030 86e82d18 86cb9628 usbhub!UsbhPdoPnp_SurpriseRemoveDevice+0x64
8b363a88 8fc0be81 8a2e1030 86e82d18 8a2e1030 usbhub!UsbhPdoPnp+0x78
8b363a9c 828849c6 8a2e1030 86e82d18 86e82d18 usbhub!UsbhGenDispatch+0x4a
8b363ab4 c6369dbc c637dbd0 c6363928 86cb9628 nt!IofCallDriver+0x63
8b363ac8 c636a3a3 86cb9628 86e82d18 c637dbd0 bthport!BthDefaultPnpHandler+0x20
8b363ae4 c636a8ee 86cb9628 86e82d18 c637dbd0 bthport!BthHandleSurpriseRemoval+0xc9
8b363b0c c636aab7 86cb9628 86e82d18 86e82e60 bthport!BthHandlePnp+0x19e
8b363b28 828849c6 86cb9570 86e82d18 8b363bcc bthport!BthDispatchPnp+0x7b
8b363b40 829eea1f 8a2e1030 8a2e1030 864b8448 nt!IofCallDriver+0x63
8b363b74 82ab8bf3 8a2e1030 8b363ba8 00000000 nt!IopSynchronousCall+0xce
8b363bd0 82ab226f 8a2e1030 00000017 a4683088 nt!IopRemoveDevice+0xd1
8b363bfc 82ab212c 00000308 00000000 8a2e1900 nt!PnpSurpriseRemoveLockedDeviceNode+0xc4
8b363c10 82ab23e7 00000003 00000000 00000000 nt!PnpDeleteLockedDeviceNode+0x20
8b363c44 82ab5e8b 86b506f0 a4683088 00000003 nt!PnpDeleteLockedDeviceNodes+0x4c
8b363d04 829a6993 8b363d34 00000000 bccd3a80 nt!PnpProcessQueryRemoveAndEject+0x594
8b363d1c 829d2491 00000000 8294213c 84d0f2d8 nt!PnpProcessTargetDeviceEvent+0x38
8b363d44 828e5e22 899c1208 00000000 84d0f2d8 nt!PnpDeviceEventWorker+0x201
8b363d7c 82a15c42 899c1208 eb5f50cf 00000000 nt!ExpWorkerThread+0xfd
8b363dc0 8287ef4e 828e5d25 00000001 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
bthport!BthDefaultPnpHandler+20
c6369dbc 56 push esi

SYMBOL_STACK_INDEX: 8

SYMBOL_NAME: bthport!BthDefaultPnpHandler+20

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: bthport

IMAGE_NAME: bthport.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 49e01fdd

FAILURE_BUCKET_ID: 0xFE_bthport!BthDefaultPnpHandler+20

BUCKET_ID: 0xFE_bthport!BthDefaultPnpHandler+20

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


Top 
 Profile  
Reply with quote  
 Post subject: Re: Shutdown involving Windows Vista Home Premium
 Post Posted: Sun Feb 13, 2011 6:34 am 
Offline
Site Admin

Joined: Sun Feb 04, 2007 11:44 am
Posts: 6120
The specific driver indicated is bthport.sys, which is a Microsoft Bluetooth bus driver (Bluetooth interfaces via USB).

I previously stated "If it was a one-time occurrence then I'd say it was just a "glitch", which can probably be ignored." Has the problem reoccurred?

If so, to check for defective hardware does the problem reoccur after disconnecting or removing all USB and Bluetooth devices (including the internal front panel chassis connections)? If so then the problem could be software or a motherboard hardware problem. To check for software corruption or malware, does it happen after booting from a clean reload of Windows Vista w/SP2? If it continues to occur after a fresh reload with no USB/Bluetooth devices attached (including internal connections), then I'd suspect the motherboard is defective. Check the motherboard based USB ports for any bent or shorted contacts, repair any you find. If all are good but the problem remains, then replace the motherboard. Let me know how the story ends... Scott.


Top 
 Profile  
Reply with quote  
 Post subject: Re: Shutdown involving Windows Vista Home Premium
 Post Posted: Tue Mar 08, 2011 1:26 am 
Offline

Joined: Sat May 08, 2010 4:13 pm
Posts: 1060
Scott, I removed the SetPoint software from Logitech that I had installed on the computer, and the problem seemed to go away.


Top 
 Profile  
Reply with quote  
 Post subject: Re: Shutdown involving Windows Vista Home Premium
 Post Posted: Tue Mar 08, 2011 1:37 am 
Offline
Site Admin

Joined: Sun Feb 04, 2007 11:44 am
Posts: 6120
That software seems to have caused you a lot of problems. Good riddance I say! <g> Scott.


Top 
 Profile  
Reply with quote  
 Post subject: Re: Shutdown involving Windows Vista Home Premium
 Post Posted: Sat Mar 17, 2012 10:53 pm 
Offline

Joined: Sat May 08, 2010 4:13 pm
Posts: 1060
Update: I'm currently using SetPoint on a PC with a Windows XP installation, and it works OK on it.


Top 
 Profile  
Reply with quote  
 Post subject: Re: Shutdown involving Windows Vista Home Premium
 Post Posted: Sat Mar 17, 2012 11:02 pm 
Offline
Site Admin

Joined: Sun Feb 04, 2007 11:44 am
Posts: 6120
Why use it at all? Scott.


Top 
 Profile  
Reply with quote  
Display posts from previous:  Sort by  
 
Post new topic Reply to topic  [ 8 posts ] 

Board index » Upgrading and Repairing Forum » Windows OS


Who is online

Users browsing this forum: No registered users and 5 guests

 
 

 
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
cron