BUGCODE_usb_driver

I frequently get a BSOD error BUGCODE_usb_driver
(I attached a screen shot )

i have external hared drive,my phone for tethering and 2 usb sticks plugged in always
&
i have below error
once all of my usb devices are not working(usb sticks viwed in my computer but they didn't view any data)
plz help!

samitha said:

I frequently get a BSOD error BUGCODE_usb_driver
(I attached a screen shot )

i have external hared drive,my phone for tethering and 2 usb sticks plugged in always
&
i have below error
once all of my usb devices are not working(usb sticks viwed in my computer but they didn't view any data)
plz help!

We do need the DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.

If you are overclocking STOP

You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.

To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

The procedure:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.
*If the files are too large please upload them to a file sharing service like "Rapidshare" and put a link to them in your reply.

To ensure minidumps are enabled:

* Go to Start, in the Search Box type: sysdm.cpl, press Enter.
* Under the Advanced tab, click on the Startup and Recovery Settings... button.
* Ensure that Automatically restart is unchecked.
* Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
* Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
* OK your way out.
* Reboot if changes have been made.

i have only 128kb varies of minidump file

samitha said:

i have only 128kb varies of minidump file

It is obvious that this machine was updated (not clean installed). There are drivers from as far back as 2003. They dont know how to work in win 7.

The crash was related to one of them

USBBUGCODE_INVALID_PHYSICAL_ADDRESS The host controller is
using a physical memory address that was not allocated by
the USBport driver.

I would suggest you update the following drivers (there are a lot of them)

Code:

sisgrp.sys    10/29/2003 1:54:56 PM    0x91323000    0x9138b700        0x00068700    0x3fa00d00                        
SiSGRV.dll    10/29/2003 2:01:55 PM    0x899c0000    0x89ad1200        0x00111200    0x3fa00ea3                        
srvkp.sys    10/29/2003 2:36:35 PM    0x87ff9000    0x87ffbc00        0x00002c00    0x3fa016c3                        
cmuda.sys    5/12/2005 1:21:06 AM    0x90d5e000    0x90ea3540        0x00145540    0x4282f5d2                        
s0017mdfl.sys    9/30/2008 4:03:36 PM    0x9cebe000    0x9cec0080        0x00002080    0x48e29428                        
s0017mdm.sys    9/30/2008 4:03:40 PM    0x9cea1000    0x9cebb580        0x0001a580    0x48e2942c                        
s0017cr.sys    9/30/2008 4:06:09 PM    0x9cf0c000    0x9cf0d000        0x00001000    0x48e294c1                        
s0017unic.sys    9/30/2008 4:06:13 PM    0x9cef2000    0x9cf0b280        0x00019280    0x48e294c5                        
s0017nd5.sys    9/30/2008 4:06:23 PM    0x9cf16000    0x9cf1ab80        0x00004b80    0x48e294cf                        
s0017wh.sys    9/30/2008 4:08:39 PM    0x9ce9f000    0x9cea0580        0x00001580    0x48e29557                        
s0017bus.sys    9/30/2008 4:08:43 PM    0x9ce8b000    0x9ce9e900        0x00013900    0x48e2955b                        
s0017mgmt.sys    9/30/2008 4:10:25 PM    0x9ced9000    0x9cef1d00        0x00018d00    0x48e295c1                        
s0017cm.sys    9/30/2008 4:12:07 PM    0x9cebc000    0x9cebd580        0x00001580    0x48e29627                        
s0017obex.sys    9/30/2008 4:12:11 PM    0x9cec1000    0x9ced8e80        0x00017e80    0x48e2962b                        
VSTCNXT3.SYS    10/15/2008 7:29:13 PM    0x9111c000    0x911d1000        0x000b5000    0x48f68ad9                        
VSTBS23.SYS    10/15/2008 7:30:15 PM    0x90f84000    0x90fd0000        0x0004c000    0x48f68b17                        
VSTDPV3.SYS    10/15/2008 7:32:04 PM    0x9101a000    0x9111c000        0x00102000    0x48f68b84

How To Find Drivers:

- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

- - The most common drivers are listed on this page: Driver Reference Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads

This is a old machine i bought in 2003 so i cant update driver (i cant find them in manufactures site) .this computer works fine before I took my external hard rive.I think this has to something to do wit it.so is there anything I can do?

samitha said:

This is a old machine i bought in 2003 so i cant update driver (i cant find them in manufactures site) .this computer works fine before I took my external hard rive.I think this has to something to do wit it.so is there anything I can do?

Understood, but some change has made you start crashing. I dont know if the HD is involved (in fact I dont even know what kind of system you have--No system specs given)

I do note this driver Related to sisgrp.sys SiS Compatible Super VGA Driver. It is part of your video driver and needs to be updated.

Without the updates you may keep crashing.