USB-related BSODs?

C

ConfusedBSOD

Posts: 16   +0
Hello

Over the past few weeks I have been getting BSODs. A lot of them point to usb_bugcode_driver or usbohci.sys, but not all of them. Some of them don't highlight a specific driver. I have attached three minidumps, so to speak :)

According to the MS Windows update site I have the latest USB drivers, even though they are dated January 2001 .....

Thx :)
 

Attachments

  • minidumps.zip
    65.9 KB · Views: 4
Two of these minidumps are pointing at the USB subsystem; involving usbport.sys & usbohci.sys. Can you please give me info do you remember what you are doing when this BSOD shows up? e.g. attaching USB flash drive or hdd?
 
Thank you for taking the time to read my files! I was surfing the 'net via a USB Router (Sagem F@ST). I also have a USB wireless mouse and keyboard, but the BSODs also happened with my old USB wired mouse and PS2 keyboard ....
 
I'm back a little earlier than I expected. The updated drivers installer was very user unfriendly ... the worst I have ever seen for a driver installer. I don't think the modem driver is to blame .. the BSODs sometimes appear before the modem is even connected ....
 
With your next post please give me your system's specifications and also I want you to run memtest on your system; it seems to me that the issue may be with your system's RAM or some device driver.

Here is the link to download memtest and you need to let it run for at least 8 passes; once you have done that please let me know if it finds any errors.

Secondly, if its a device driver (e.g. USB related in your case as it is in couple of your minidumps) you can confirm it by:

Steps:
1) Windows Key + R
2) Type in 'verifier' and hit enter
3) Make sure 'Create Standard Setting' is selected and hit next
4) Click on 'Select all drivers installed on this computer' and hit Finish
5) Reboot

There is a strong possibility that your computer will crash on reboot. If this occurs hit F8 when rebooting just before the windows logo screen and select the safe mode boot option. Follow the same steps above but on step 4 choose 'Select driver names from a list'; hit next; check the box next to any driver where the provider is not Microsoft; hit Finish; reboot.

This will slow the performance of you computer a little while enabled but will hopefully catch the driver causing corruption. Next time you crash the blue screen will hopefully say something like "DRIVER_VERIFIER_DETECTED_VIOLATION". When this occurs please repost your minidump.
 
Thank you, and sorry for taking so long to get back to you. My PC crashed five times in the past 15 minutes, and I'm beginning to think it's hardware related e.g. The PC wouldn't reboot properly .. it just hung, without anything on the display! It also made a funny beeping sound ... :(

I will try your suggestions later :)
 
My latest crash reports are attached ... I will do the memtest and the other suggestions later! :)

P.S. The crashing mainly occurs when the PC is cold, and the crashes normally go away after a while .... it is so weird! The crashes have gone away for the rest of the day!
 

Attachments

  • Archive.zip
    57 KB · Views: 1
1. rdbss.sys (Redirected Drive Buffering SubSystem Driver) caused the first BSOD.The Stop 0xD1 messages indicates that the system attempted to access pageable memory using a kernel process IRQL that was too high. Drivers that have used improper addresses typically cause this error.

2. tcpip.sys (Transmission Control Protocol subsystem), same as above at #1.

3. USBPORT.SYS, same explanation as above at #1.

As these dumps points to different device drivers randomly; it is essential that you run memtest from the link in the post # 7; asap.

What sort of beep? was it the first time ever you heard it?

Also, do backup your data from that HDD, just as precaution. At this moment I don't suspect this has anything to do with your HDD though.

Edit:
If you haven't cleaned out your system in a while, do so with air canister, to clear out dust etc.
 
Hello

I ran memtest for over an hour (200% completed), and I got three memory errors. All of the following were errors related to copying between addresses:

1) 1789c07 and 1789b33

2) 2fb6eb6 and 2fb6ea3

3) 435b17b and 435b103

Everything on my HD has been backed up. I'll try and eliminate the faulty memory card over the next 24 hours or so. I have two 512Mb RAM cards.

>What sort of beep? was it the first time ever you heard it?

The beep was a continuous 1 second beep. I have never heard that beep before.

Once in a while I get a BSOD that completely screws the system up, and rebooting causes the PC to freeze. The "symptoms" include no display, and no activity.

Thank you for your continued guidance :)

P.S. I will clean the inside of the case.
 
You are welcome; however, I'll advise you to run memtest thoroughly; more ideally on both RAM modules one by one, so you can figure out whether its just one module which is causing this issue; or both of them are bad. Regards
 
Archean said:
You are welcome; however, I'll advise you to run memtest thoroughly; more ideally on both RAM modules one by one, so you can figure out whether its just one module which is causing this issue; or both of them are bad. Regards
Click to expand...

I'll run memtest overnight, one module at a time.
 
I have tested both memory modules in slot #1, and both have errors :(. What are the chances of both modules developing errors? They are of differing age (1 year difference), and different manufacturers (Samsung vs Crucial).

Could it be a PSU problem? 99% of the BSODs occur a few minutes after starting the PC from cold ....
 
It can happen, as it did in your case. However, I'll advise you to check your PSU as well. Please provide me with your system's complete specs, including PSU make/model etc. Also, it is better to have just one type of RAM in a system, as it reduces the chance of any incompatibilities between two different types of RAM modules/mismatching etc.
 
Operating system: Microsoft Windows XP Home Edition
Service pack: 3.0
Manufacturer: TriGem Computer NETHERLANDS
Model: Advent Series
BIOS type: Phoenix - AwardBIOS v6.00PG
BIOS ID: 04/16/2004-SiS-661-6A7I4E1AC-00
BIOS sign on: None
BIOS date: 2004.04.16 (The latest version, according to eSupport)
Chipset: SiS 661 rev 17
SuperIO chipset: ITE 8705/SiS 950 rev 2 at port 002E
GPU: ATI Radeon 9600
Sound: SoundBlaster
HD: 2 x Hitachi Deskstar, 120Gb
CPU: P4 Prescott 3.0GHz
RAM: 1024 Mb
Extra Cooling Fan: PCI Slot Fan (Acasa)
Network: Ethernet LAN
PSU: Seasonic SS-300GS (Active PFC T3); 300Watts
Three USB Ports in regular use
Front Bay Card Reader
Floppy Drive
1 x CDRW Drive
1 x CD Rom Drive
Click to expand...

The BSODs seem to have stopped .... maybe it's because I swapped the RAM modules over?

I used a PSU calculator (http://extreme.outervision.com/PSUEngine), and my recommended minimum wattage was 389W, compared to the 300W that I currently have.
 
Thats a very strong probability as faulty ram is out of that system :)

Just ensure that your RAM is set at the prescribed timings/voltage of its manufacturer.

Edit:
Also please do remember PSU's do degrade overtime; therefore, it is advisable if you further investigate into this issue; and perhaps replace it.
 
Archean said:
Thats a very strong probability as faulty ram is out of that system :)

Just ensure that your RAM is set at the prescribed timings/voltage of its manufacturer.

Edit:
Also please do remember PSU's do degrade overtime; therefore, it is advisable if you further investigate into this issue; and perhaps replace it.
Click to expand...

Thank you for your help over th past week or so! :) Just to clarify, I swapped the RAM modules over i.e. original RAM module is now in slot #2, and the newer RAM module now in slot #1. The crashes have gone away completely .... I'll do another memory test, just in case.

Thanks again!
 
You are welcome; I'm glad the issue seems to have been taken care off. Goodluck and take care.
 
It's me again

I'm back ... :haha:. After six months of BSOD-free operation .... they are back with a vengeance! The BSODs have returned for no apparent reason. I have noticed something very distinctive about the BSODs, that may point to a hardware/BIOS problem:

The BSODs only occur when the PC is booted up from cold. After 10-20 minutes of BSODs .... the problem disappears. If I leave the PC running overnight .... there are no problems. I can leave the PC running for days on end, and not one BSOD! However, if I shut the PC down for an hour, and restart ... BSOD hell resumes for 10-20 minutes!

I have the "latest" BIOS available for my system (as confirmed by biosagentplus.com aka eSupport) ... but the BIOS is about six years old. Some of the BSODs have referred to my BIOS not being "ACPI compliant". I'm contacting eSupport again, in the hope that they can find me a newer BIOS.

Any ideas? :)
 
Considering that you are having BSOD's from cold booting, there is significant chance that it is due to hardware issues, probably degradation, or another dimension can be degradation of your PSU, hence it is unable to supply required level of power when it is required.

I remember calling Prescott cores as Preshots in one of my posts ;) ......... they are very power hungry cpus anyway.

Did you replaced your PC's PSU in the light our previous discussions?
 
Archean said:
Considering that you are having BSOD's from cold booting, there is significant chance that it is due to hardware issues, probably degradation, or another dimension can be degradation of your PSU, hence it is unable to supply required level of power when it is required.

I remember calling Prescott cores as Preshots in one of my posts ;) ......... they are very power hungry cpus anyway.

Did you replaced your PC's PSU in the light our previous discussions?
Click to expand...

Hi again :)

Thanks for getting back to me. I have just ordered a 450W ATX PSU, as I think you are right about the PSU ageing issue. The stock PSU is 300W. According to your link earlier in the thread, my current requirements are 400W ....:blush:

I'll report back to you as soon as I've installed the PSU :)
 
Hmmm

Hello again.

I received the new PSU, which was advertised as having four Molex connectors ... it only had three, and the cables are too short :(. Before I attempted to fit the new PSU, I used compressed air to remove a lot of dust. I also blasted the memory modules and sockets with compressed air. The BSODs have vanished again.

My computer must be getting very sensitive to dust in its old age.
 
which brand of PSU you purchased? And if the cables are 'too short' in length to be easily reach connecting points, I think you should have gotten it replaced straightaway. Glad to hear that BSODs are gone, lets keep fingers crossed and hope that we actually solved the bigger issue. Regards
 

Similar threads

Daniel Sims
Windows users report widespread device issues following January 2025 updates
Replies
23
Views
502
ZedRM
ZedRM
LinzReid
TrojanDownloader.JS/swabfex.P
Replies
1
Views
635
LinzReid
LinzReid
Iddo12
USB 28 error on windows 10
Replies
8
Views
1K
Nelson28
N

Latest posts

Back