Tech Support banner
Status
Not open for further replies.
1 - 8 of 8 Posts

·
Registered
Joined
·
4 Posts
Discussion Starter · #1 ·
I have a brand new T410 (less than a week old) and I have been having problems with it. When I first got it, right out of the box I would get a "windows does not recognize one of your usb devices" message, and when I went to device manager "unknown device" was the issue. So I uninstalled it, and I thought that was that. A couple days later, I started getting BSoDs with the error code "BUGCODE_USB_DRIVER". I have gotten a bunch since then (I would guess around 10) and they seem to happen fairly randomly; I haven't been able to pick up a pattern. Here's some basic system information:

OS- Windows 7 Pro, 64-bit. Came pre-installed. I have not reinstalled it.
Like I said, my computer is less than a week old. Well, it shipped out of Lenovo's warehouse on june 21st, but it arrived around july 6th or 7th.
I have an intel graphics media accelerator HD (not sure if that's the name of the video card or not?)

Anyways, any help anyone can give would be greatly appreciated.
 

·
TSF Team Emeritus, Microsoft MVP
Joined
·
7,483 Posts
16 memory dumps from 08 to 14 Jul 2010 (1 week)
All are STOP 0xFE and all blame usbhub.sys (a Windows component)
The dump files are running very slowly due to symbol problems - did you get this system direct from Lenovo or from another retailer?

Here's what to do about the symbol issues:
Unfortunately, the Windows Debugging Tools aren't able to access symbols for your operating system files (in particular USBPORT.SYS and USBHUB.SYS) from the Microsoft Symbol Server - so that makes debugging them difficult if not impossible.

Please do the following (this will not affect the analysis of the current files - but it may help later files that are acquired):
- activate/validate the Windows installation at http://www.microsoft.com/genuine
- run sfc.exe /scannow to replace any problem files
- open a support incident with Microsoft to see if they can fix the missing symbols issue ( http://support.microsoft.com/ph/14019 )
- If that doesn't fix it, then wipe the hard drive and reinstall Windows
I do see traces of Norton/Symantec in the stack text, so I'd suggest doing this first:
Anti-Virus Removal:
Please do the following:
- download a free antivirus for testing purposes: http://www.carrona.org/freeav.html
- uninstall the Norton from your system (you can reinstall it, if so desired, when we're done troubleshooting)
- remove any remnants of Norton using this free tool: http://service1.symantec.com/Support/tsgeninfo.nsf/docid/2005033108162039
- IMMEDIATELY install and update the free antivirus
- check to see if this fixes the BSOD's
So, the first question is what do you have connected to the USB ports?
Also, please check the "unknown device" by right clicking on it and selecting "Properties"
Then select the "Details" tab, then select "Hardware ID" in the dropdown box - and let us know what the Hardware ID is. We'll need the first 4 characters after the VID_ and the first 4 characters after the PID_ (It could also be VEN_ and DEV_)

Frankly, you're at the point where you may have to rely on the warranty - so the first thing to do is to contact either the place that you bought it from or Lenovo and start a support incident (get a case number). This will show that you had problems within a week of receiving it. FWIW - Lenovo was great with me when I had issues with my tablet. The point here is that the earlier you contact them, the more likely they are to offer you a new system (rather than trying to repair the current one).

Next, backup your stuff and then use the recovery disks to reinstall Windows.
If that stops the BSOD's, then you're good. If not, then start talking with the support people about an exchange for a unit that works properly.
 

·
TSF Team Emeritus, Microsoft MVP
Joined
·
7,483 Posts
Continued....

BSOD BUGCHECK SUMMARY
Code:
[font=lucida console]
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue Jul 13 21:03:02.044 2010 (UTC - 4:00)
System Uptime: 0 days 0:34:39.886
*** WARNING: Unable to verify timestamp for usbhub.sys
*** ERROR: Module load completed but symbols could not be loaded for usbhub.sys
BugCheck FE, {8, 6, 5, fffffa8007f7d7a0}
Probably caused by : usbhub.sys ( usbhub+12a60 )
BUGCHECK_STR:  0xFE
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue Jul 13 20:27:47.083 2010 (UTC - 4:00)
System Uptime: 0 days 4:23:05.581
*** WARNING: Unable to verify timestamp for usbhub.sys
*** ERROR: Module load completed but symbols could not be loaded for usbhub.sys
BugCheck FE, {8, 6, 5, fffffa8007e987a0}
*** WARNING: Unable to verify timestamp for iaStor.sys
*** ERROR: Module load completed but symbols could not be loaded for iaStor.sys
Probably caused by : iaStor.sys ( iaStor+2de7b )
BUGCHECK_STR:  0xFE
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue Jul 13 16:04:05.508 2010 (UTC - 4:00)
System Uptime: 0 days 1:21:58.006
*** WARNING: Unable to verify timestamp for usbhub.sys
*** ERROR: Module load completed but symbols could not be loaded for usbhub.sys
BugCheck FE, {8, 6, 5, fffffa8007b017a0}
Probably caused by : usbhub.sys ( usbhub+12a60 )
BUGCHECK_STR:  0xFE
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue Jul 13 14:41:32.858 2010 (UTC - 4:00)
System Uptime: 0 days 14:02:16.982
*** WARNING: Unable to verify timestamp for usbhub.sys
*** ERROR: Module load completed but symbols could not be loaded for usbhub.sys
BugCheck FE, {8, 6, 5, fffffa80079437a0}
*** WARNING: Unable to verify timestamp for iaStor.sys
*** ERROR: Module load completed but symbols could not be loaded for iaStor.sys
Probably caused by : iaStor.sys ( iaStor+2de7b )
BUGCHECK_STR:  0xFE
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue Jul 13 00:38:43.288 2010 (UTC - 4:00)
System Uptime: 0 days 0:23:46.787
*** WARNING: Unable to verify timestamp for usbhub.sys
*** ERROR: Module load completed but symbols could not be loaded for usbhub.sys
BugCheck FE, {8, 6, 5, fffffa8007c547a0}
Probably caused by : usbhub.sys ( usbhub+12a60 )
BUGCHECK_STR:  0xFE
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue Jul 13 00:14:22.296 2010 (UTC - 4:00)
System Uptime: 0 days 6:42:05.138
*** WARNING: Unable to verify timestamp for usbhub.sys
*** ERROR: Module load completed but symbols could not be loaded for usbhub.sys
BugCheck FE, {8, 6, 5, fffffa80081b97a0}
Probably caused by : usbhub.sys ( usbhub+12a60 )
BUGCHECK_STR:  0xFE
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon Jul 12 17:31:43.898 2010 (UTC - 4:00)
System Uptime: 0 days 7:18:43.739
*** WARNING: Unable to verify timestamp for usbhub.sys
*** ERROR: Module load completed but symbols could not be loaded for usbhub.sys
BugCheck FE, {8, 6, 5, fffffa80081c27a0}
Probably caused by : usbhub.sys ( usbhub+12a60 )
BUGCHECK_STR:  0xFE
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon Jul 12 10:12:04.851 2010 (UTC - 4:00)
System Uptime: 0 days 14:59:15.303
*** WARNING: Unable to verify timestamp for usbhub.sys
*** ERROR: Module load completed but symbols could not be loaded for usbhub.sys
BugCheck FE, {8, 6, 5, fffffa8007fb17a0}
Probably caused by : usbhub.sys ( usbhub+12a60 )
BUGCHECK_STR:  0xFE
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sun Jul 11 19:11:44.299 2010 (UTC - 4:00)
System Uptime: 0 days 5:24:39.797
*** WARNING: Unable to verify timestamp for usbhub.sys
*** ERROR: Module load completed but symbols could not be loaded for usbhub.sys
BugCheck FE, {8, 6, 5, fffffa8007e2a7a0}
Probably caused by : usbhub.sys ( usbhub+12a60 )
BUGCHECK_STR:  0xFE
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sun Jul 11 13:46:32.563 2010 (UTC - 4:00)
System Uptime: 0 days 0:18:43.687
*** WARNING: Unable to verify timestamp for usbhub.sys
*** ERROR: Module load completed but symbols could not be loaded for usbhub.sys
BugCheck FE, {8, 6, 5, fffffa8007ee07a0}
Probably caused by : usbhub.sys ( usbhub+12a60 )
BUGCHECK_STR:  0xFE
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sun Jul 11 13:27:09.684 2010 (UTC - 4:00)
System Uptime: 0 days 3:03:40.525
*** WARNING: Unable to verify timestamp for usbhub.sys
*** ERROR: Module load completed but symbols could not be loaded for usbhub.sys
BugCheck FE, {8, 6, 5, fffffa8007fb27a0}
*** WARNING: Unable to verify timestamp for SYMEVENT64x86.SYS
*** ERROR: Module load completed but symbols could not be loaded for SYMEVENT64x86.SYS
Probably caused by : SYMEVENT64x86.SYS ( SYMEVENT64x86+19d5e )
BUGCHECK_STR:  0xFE
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sun Jul 11 10:22:53.221 2010 (UTC - 4:00)
System Uptime: 1 days 8:20:07.580
*** WARNING: Unable to verify timestamp for usbhub.sys
*** ERROR: Module load completed but symbols could not be loaded for usbhub.sys
BugCheck FE, {8, 6, 5, fffffa80078cd7a0}
*** WARNING: Unable to verify timestamp for SYMEVENT64x86.SYS
*** ERROR: Module load completed but symbols could not be loaded for SYMEVENT64x86.SYS
Probably caused by : SYMEVENT64x86.SYS ( SYMEVENT64x86+19d5e )
BUGCHECK_STR:  0xFE
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sat Jul 10 02:00:24.279 2010 (UTC - 4:00)
System Uptime: 0 days 10:35:43.778
*** WARNING: Unable to verify timestamp for usbhub.sys
*** ERROR: Module load completed but symbols could not be loaded for usbhub.sys
BugCheck FE, {8, 6, 5, fffffa8007ec27a0}
Probably caused by : usbhub.sys ( usbhub+12a60 )
BUGCHECK_STR:  0xFE
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri Jul  9 00:35:55.922 2010 (UTC - 4:00)
System Uptime: 0 days 6:04:50.046
*** WARNING: Unable to verify timestamp for usbhub.sys
*** ERROR: Module load completed but symbols could not be loaded for usbhub.sys
BugCheck FE, {8, 6, 5, fffffa8007a847a0}
Probably caused by : usbhub.sys ( usbhub+12a60 )
BUGCHECK_STR:  0xFE
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Thu Jul  8 18:30:01.278 2010 (UTC - 4:00)
System Uptime: 0 days 1:03:49.104
*** WARNING: Unable to verify timestamp for usbhub.sys
*** ERROR: Module load completed but symbols could not be loaded for usbhub.sys
BugCheck FE, {8, 6, 5, fffffa8007cfe7a0}
Probably caused by : usbhub.sys ( usbhub+12a60 )
BUGCHECK_STR:  0xFE
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Thu Jul  8 13:29:12.926 2010 (UTC - 4:00)
System Uptime: 0 days 1:59:29.050
*** WARNING: Unable to verify timestamp for usbhub.sys
*** ERROR: Module load completed but symbols could not be loaded for usbhub.sys
BugCheck FE, {8, 6, 5, fffffa8007eb07a0}
Probably caused by : usbhub.sys ( usbhub+12a60 )
BUGCHECK_STR:  0xFE
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
  
  
 
[/font]
 

·
Registered
Joined
·
4 Posts
Discussion Starter · #5 ·
Yes, I got this machine direct from the lenovo website. It is a customized machine, but I ordered it customized from lenovo, so I wouldn't think that would make a difference.

As for what USB devices I have plugged in, I don't. That's the confusing part for me. I don't have any USB devices plugged in.

And as for properties of the unknown device, when it was giving me problems I uninstalled it and it is no longer listed under my devices. If you know of a way for me to get it back, I would be happy to give you that information.

It is currently in the hands of an IT guy that I am friends with, and he's running some scans on it, so hopefully he'll come up with a fix for it. If not, though, I'll definitely try some of this stuff.
 

·
TSF Team Emeritus, Microsoft MVP
Joined
·
7,483 Posts
My system was customized by Lenovo also.

If there's no USB devices installed and you're getting USB errors - that implies a hardware problem with the USB controller. The definitive troubleshooting test for that would be to reinstall Windows - and if the problem remains it's safe to assume that it's a hardware issue.

Call Lenovo and start the process now (you can always call and cancel later on). The sooner that you start, the easier it'll be to get a new system (rather than waiting for this one to be repaired).
 

·
Registered
Joined
·
4 Posts
Discussion Starter · #7 ·
Ok, the unknown device is back, and when I try to check the hardware id it says USB\UNKNOWN. Although I upgraded my BIOS earlier today, and my IT friend said that I had a bad block in my hard drive and he said he thinks it's fixed, and I haven't had any issues since then (although sometimes my computer would last a long time before blue screening me), so maybe it's fixed? Hopefully?
 
1 - 8 of 8 Posts
Status
Not open for further replies.
Top