W2K BSOD

  • Thread starter Thread starter tlswift
  • Start date Start date
T

tlswift

I have a computer that has the following hex dump, but could find nothing in
the Knowledge Base on it.

Stop: 0x000000D1 (0x00000015, 0x00000002, 0x00000000, 0xF06BAB46)
DRIVER_IRQ_NOT_LESS_OR_EQUAL UHCD.SYS

The system boots fine. You log in and everything looks good for 30 seconds
to about 2 minutes; then you get the BSOD. Changing the current uhcd.sys
file to uhcd.old and copying another uhcd.sys file into system32/drivers
directory does nothing.

Anybody got any clues?

--
Terry

"Treat people as if they were what they ought to be and you help them to
become what they are capable of doing"

--Johann Wolfgang von Goethe
 
--------------------
From: "tlswift" <[email protected]>
Subject: W2K BSOD
Date: Mon, 7 Jun 2004 22:41:51 -0700

I have a computer that has the following hex dump, but could find nothing in
the Knowledge Base on it.

Stop: 0x000000D1 (0x00000015, 0x00000002, 0x00000000, 0xF06BAB46)
DRIVER_IRQ_NOT_LESS_OR_EQUAL UHCD.SYS

The system boots fine. You log in and everything looks good for 30 seconds
to about 2 minutes; then you get the BSOD. Changing the current uhcd.sys
file to uhcd.old and copying another uhcd.sys file into system32/drivers
directory does nothing.

Anybody got any clues?

--
Terry

"Treat people as if they were what they ought to be and you help them to
become what they are capable of doing"
Click to expand...
--Johann Wolfgang von Goethe
Click to expand...
--------------------

Do you have any USB devices installed? Have you tried booting up without
them connected?


--
~~ JASON HALL ~~
~ Performance Support Specialist,
~ Microsoft Enterprise Platforms Support
~ This posting is provided "AS IS" with no warranties, and confers no
rights.
~ Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
~ Note: For the benefit of the community-at-large, all responses to this
message are best directed to the newsgroup/thread from which they
originated.
 
Jason,

As for USB devices, I'm not sure. This is a machine I'm working on for a
friend and it's not in front of me right now. What should be the
troubleshooting guide for either way?
--
Terry

"Treat people as if they were what they ought to be and you help them to
become what they are capable of doing"

--Johann Wolfgang von Goethe
 
--------------------
From: "tlswift" <[email protected]>
References: <[email protected]>
Click to expand...
Subject: Re: W2K BSOD
Date: Tue, 8 Jun 2004 11:55:47 -0700

Jason,

As for USB devices, I'm not sure. This is a machine I'm working on for a
friend and it's not in front of me right now. What should be the
troubleshooting guide for either way?
--
Terry

"Treat people as if they were what they ought to be and you help them to
become what they are capable of doing"
Click to expand...
--Johann Wolfgang von Goethe
Click to expand...
---------------------

- I would try what I mentioned before, to see if something with the
device(s) is causing the issue
- Also, try installing the latest version of uhcd.sys in hotfix Q838989


--
~~ JASON HALL ~~
~ Performance Support Specialist,
~ Microsoft Enterprise Platforms Support
~ This posting is provided "AS IS" with no warranties, and confers no
rights.
~ Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
~ Note: For the benefit of the community-at-large, all responses to this
message are best directed to the newsgroup/thread from which they
originated.
 
Jason,

Tried finding that hotfix article you mentioned in the Support Group /
Knowledge Base, but came up empty.

--
Terry

"Treat people as if they were what they ought to be and you help them to
become what they are capable of doing"

--Johann Wolfgang von Goethe
 
Here's what troubleshooting I did that finally corrected the issue.

1. Did the repair from the W2K CD - no success
2. Replaced the UHCD.SYS file with a new one - partial success - allowed
computer to run
about 2 minutes before BSOD instead of 15-30 seconds
3. After finding that the UHCD.SYS file involved the USB System,
disconnected all USB
peripherals except the wireless keyboard.
4. System functions normal - no BSOD
5. USB device that was unplugged was a HP Officejet printer that had been
attached for a long
time with no problems
6. Plugged the USB cable into another USB port and got a BSOD - thought of
bad cable
7. Unplugged cable from printer and rebooted computer and left cable
plugged into the port -
no BSOD
8. Plugged USB cable into printer and rebooted system - NO BSOD

Gremlins in the system somewhere. All the while I was updating the guys
system with critical updates and stuff as he was like a year behind.

--
Terry

"Treat people as if they were what they ought to be and you help them to
become what they are capable of doing"

--Johann Wolfgang von Goethe
 
Thanks for the great feedback. I wish more posters would close off
their calls the way you did - detailed, systematic, comprehensive.
 
Back
Top