Avast WEBforum

Other => General Topics => Topic started by: YLAP on May 11, 2007, 10:19:24 PM

Title: Help needed: BSOD and USB v2
Post by: YLAP on May 11, 2007, 10:19:24 PM
Hello,

I have one interesting problem. After fresh install my system started to show BSOD as soon as I connect my Kingston Data Traveler (or any other USB Storage device)  :'(. I have to disable USB 2.0 Support on BIOS to fix the problem. I have never had this strange problem with my pc... Any ideas what can I do and how to solve it? (Minidump is pasted below)

-----------------------------------------------------------------------------

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


Loading Dump File [C:\Documents and Settings\Pauliux\Desktop\Mini051107-03.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 ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a820
Debug session time: Fri May 11 20:16:37.343 2007 (GMT+3)
System Uptime: 0 days 0:01:36.919
*********************************************************************
* 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 ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {c0000005, f89888ea, f89887f0, f89884ec}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*** WARNING: Unable to verify timestamp for USBPORT.SYS
*** ERROR: Module load completed but symbols could not be loaded for USBPORT.SYS
*** WARNING: Unable to verify timestamp for usbhub.sys
*** ERROR: Module load completed but symbols could not be loaded for usbhub.sys
*** WARNING: Unable to verify timestamp for hal.dll
*** ERROR: Module load completed but symbols could not be loaded for hal.dll
Probably caused by : USBPORT.SYS ( USBPORT+185a9 )
Title: Re: Help needed: BSOD and USB v2
Post by: Lisandro on May 11, 2007, 11:22:43 PM
The only strange thing I've noticed is that one of my USB devices (the old one) is not recognized automatically.
The others are.
But fortunately, no BSODs for me.
Title: Re: Help needed: BSOD and USB v2
Post by: YLAP on May 11, 2007, 11:33:30 PM
Tried everything... Only disabling usb 2.0 controller in bios helps... As I don't want to reinstall all system again at the same day, seems I'll have to live with USB 1.1 here  :-\ All my connected hardware worked perfectly with usb 2.0, but usb mass storage device crashed my system as soon as connected... stupid windows...  >:(
Title: Re: Help needed: BSOD and USB v2
Post by: Lisandro on May 11, 2007, 11:35:15 PM
But usb mass storage device crashed my system as soon as connected... stupid windows...  >:(
Do you have some info on Windows Events related to the crash?
Can you post it here?
Title: Re: Help needed: BSOD and USB v2
Post by: YLAP on May 11, 2007, 11:44:24 PM
No, nothing unusual in event viewer...  :-\
Title: Re: Help needed: BSOD and USB v2
Post by: YLAP on May 11, 2007, 11:46:58 PM
Actually, I've even tried to turn on PC with USB stick pluged in... At the moment when logon screen should appear - BSOD again... Now I understand why someone calls it Plug and Pray...  >:(

If it helps - SiS 7001 PCI to USB Open Host controller here...
Title: Re: Help needed: BSOD and USB v2
Post by: DavidR on May 12, 2007, 12:18:55 AM
What was the BSOD information, Stop Error code, any other meaningful error text, etc. ?

If the same as that reported in the BugCheck bit 1000007E, then a google search returns many hits, http://www.google.com/search?q=stop+1000007E (http://www.google.com/search?q=stop+1000007E). Also a google search for BSOD and USB 2, http://www.google.com/search?q=BSOD+and+USB+2 (http://www.google.com/search?q=BSOD+and+USB+2). There are a lot of hits on this one but a lot of them seem irrelevant so you might try refining the search.

Title: Re: Help needed: BSOD and USB v2
Post by: YLAP on May 12, 2007, 09:40:42 AM
PAGE FAULT IN NON PAGED AREA ... STOP 0x00000050 (0XB5A9F8B0, ...) and so on. In BSOD there is no info about file what caused it. Debugging tools from minidump shows

*** WARNING: Unable to verify timestamp for USBPORT.SYS
*** ERROR: Module load completed but symbols could not be loaded for USBPORT.SYS
*** WARNING: Unable to verify timestamp for usbhub.sys
*** ERROR: Module load completed but symbols could not be loaded for usbhub.sys
*** WARNING: Unable to verify timestamp for hal.dll
*** ERROR: Module load completed but symbols could not be loaded for hal.dll
Probably caused by : USBPORT.SYS ( USBPORT+185a9 )


But... I can't understand the problem. Maybe I need to try to replace USBPORT.SYS and hal.dll files with recovery console...
Title: Re: Help needed: BSOD and USB v2
Post by: Lisandro on May 12, 2007, 02:06:26 PM
Strange that this problem should be solved a long time ago...
http://support.microsoft.com/?scid=kb%3Ben-us%3B291284&x=11&y=14
http://support.microsoft.com/?scid=kb%3Ben-us%3B817197&x=19&y=12
Title: Re: Help needed: BSOD and USB v2
Post by: DavidR on May 12, 2007, 02:38:51 PM
What is your motherboard ?
How old is it ?

There may be a mix of USB 1.1 and 2.0 ports and if you plug in a USB 2 device into a USB 1.1 port it might not work, though I don't know if it would throw p this kind or error or BSOD, it just won't work as fast as usb flash drive I don't believe need any power from the usb 2 port.

I don't know enough about Vista to suggest you extract a copy of usbport.sys from your Vista DVD assuming you got one.

I don't know if it might help but there are a lot of hits for http://www.google.com/search?q=Vista+%22Unable+to+verify+timestamp%22+usbport.sys (http://www.google.com/search?q=Vista+%22Unable+to+verify+timestamp%22+usbport.sys).
Title: Re: Help needed: BSOD and USB v2
Post by: Hard_ROCKER on May 12, 2007, 07:46:50 PM
He's running XP SP2. Apparently everything was working fine this morning but after he finished installing all his software(it was a fresh windows reinstall) this started happening so i guess it must be related to a program or a driver he installed. I suggested he go back to one of his working restore points and take it one step at a time to find the culprit program/driver .
His motherboard is something from Asrock but i don't remember which model other than it's socket A based(about 3yrs old running a duron cpu). BIOS is setup correctly also there seem to be no hardware conflicts. Reinstall of the usb drivers didn't help either.
Title: Re: Help needed: BSOD and USB v2
Post by: YLAP on May 12, 2007, 08:09:50 PM
I'm back here  ;D PC is still under construction ATM, but.. everything was software related... Now I know the problem was my BENQ digital camera's software, which USB drivers hides so deep inside, what even system restore was not able to undo them... But now I know where is the problem, and now it is solved. My digital camera does not need any driver to get pictures from it, to buy a separate webcam is not a problem  ;D Going back to install all soft here. Heh, Windows, Plug and Pray  ;D Two complete reinstalls in two days - better it would be the last time  ;D Even in nightmares  ;D

PS. Asrock K7S41GX here, never had problems with it, so I knew it should be software, espiacialy when I'm using latest BIOS v. 2.80 (about 6 months old if I'm not wrong)
Title: Re: Help needed: BSOD and USB v2
Post by: YLAP on May 12, 2007, 08:12:01 PM
THANKS FOR HELP EVERYBODY, especially for you, Mikey  ;)
Title: Re: Help needed: BSOD and USB v2
Post by: Hard_ROCKER on May 12, 2007, 08:16:43 PM
Yeah no problem buddy !  :)