February 10th, 2006, 06:03 PM #1
USB Initializing... Hang on bootup!
I don't know exactly what I changed, but yesterday when I rebooted -- and now every single time -- it gets stuck on the bootup screen for about a minute stating: "USB Initializing..." and above that, it says "Checking NVRam..."
On the screen, it also displays:
"1 AMD North Bridge, Rev C6"
"VIA K8T800 AGP Controller, Rev A2"
"VIA VT8237 South Controller, Rev A2"
I tried resetting my bios, unplugging USB devices, and unplugged PCI slots, but to no avail. Can anyone please help with this mess?
February 10th, 2006, 11:33 PM #2
- Join Date
- Dec 2005
Have you tested the battery? When a board's battery gets weak you will start seeing error
messages and hangs at post due to problems then experienced with the NVRam. That is the
programming for the bios itself being effected. This will cause the failure to properly detect
hardwares installed when the bios chipset's programming is not able to run completely. You
mention resetting the bios by? just moving the jumper back and forth or by removal of the
battery as well? If you left the jumper in the clear bios and not default position that can be
an obvious problem as well as a weak battery. These are the first things to look into before
assuming any type of hardware failure is involved.
February 11th, 2006, 03:35 AM #3
Wow, you really seem like you know what I'm talking about. I tried removing the jumper back and forth. I think I always had the jumper at the clear bios because, when I set it to the default position, my power would not turn on. Strangely, it would turn on if I have it in the reset position (I'm guessing it's the reset position, at least according to my board manual, unless they had it written incorrectly reversed?). I guess it really could be a battery problem?
By the way, after a minute or so of "searching for USB devices/USB initiliazing" (or whatever it's doing), it would start Windows like it would normally do. And once I log on, my USB are still working fine. So is this because there's still some juice left in the battery?
Last edited by Namie; February 11th, 2006 at 04:37 AM.
February 11th, 2006, 05:18 AM #4
- Join Date
- Dec 2005
One way to see if the error messages are being seen due to a weak battery is to assign a
wav file to the "critical battery alarm" through the control panel's "sound and audio devices"
that has a very distinctive sound. If you start hearing the sound you choose that currently is
not assigned to any other that would clearly point to the battery. This would be done if you
do not have a basic multimeter onhand to test the battery's voltage. Even the "low battery"
having a sound assigned is generally a good idea.
In the event the battery is found strong or even a replacement sees the same problem, the
next step would be to monitor system temps. Those should be monitored regularly anytime
that you plan to have a system running for an extended period of time. Most newer boards
have a temperature monitor of some type in the bios itself. With the NVRam error suddenly
coming up which is dealing directly with the bios itself a good look at the temps may point to
the cause if a hardware failure is on the way soon. Sometimes the bios chipset can get hot
without seeing it in cpu and board temp readings. Pointing a regular small fan at the side of the case with a side panel off is one way often advised to see if something is heat related.
A temperature rise with a system itself usually can be solved by additional or better method
of cooling. A fan clogged with dust and dirt too common can easily be cleaned by the use of
an air cleaner found at most stores with pc accessories onhand. The third idea to pass your
way would be a failing board component like a "bad cap"(capacitor) that is suddenly decided
on giving you a headache before it quits. This would be the last thing. Battery-Temps and??
February 11th, 2006, 07:28 AM #5
A tempreture problem? Bios chipset getting too hot? "crap" capacitor? Battery?
He does seem to know what he is talking about
Mobo battery's usually last at least 5 years or so...PCTECH250..Sorry to rain on your parade...
correct me if i am wrong PCTECH...As i am lean't new things every day!
Last edited by Coolzer; February 11th, 2006 at 07:32 AM.
February 11th, 2006, 03:39 PM #6
Originally Posted by Coolzer
- Join Date
- Dec 2005
so "mystical" as to not be looked into as well as a possible overheating issue. The
NVRam error clearly points out that something is effecting the bios programming. A
overheating cpu recently cooked two different mother boards when the cpu given
away from a failed system ruined a working one before the warning not to use any
hardware from the failed system could be given. That was originally pointing at the
board as the source. Why do you think bios chipsets have heatsinks too?
Namie adding some additional system information could also be useful here so as
not to have to listen to a smear campaign. Until the cause is known don't rule out
a few different possible causes. A $2- battery is far less expensive to rule out then
your expensive hardwares. Someone with some "practical working advice" is more
then welcome to join the thread here since they will stay on subject.
February 11th, 2006, 03:49 PM #7
First of all, just to be safe change the battery and clear the CMOS and see what happens.
Make sure you have no USB devices hooked up.
Check your manual and make sure the jumper is where it is supposed to be.
If none of this works, look on your start up disk for your motherboard and see if you have a copy of your bios and a flash utility. You may have somehow gotten a corrupt bios.Obama: The rich have the Federal Reserve and the poor have Harry Reid... LOL. Life really is unfair!
February 11th, 2006, 03:49 PM #8
Why do you hit the return like you're using a typewriter?
February 11th, 2006, 04:08 PM #9
Because it's easier to read. It's not like I'm wasting paper...Obama: The rich have the Federal Reserve and the poor have Harry Reid... LOL. Life really is unfair!
February 11th, 2006, 04:23 PM #10
- Join Date
- Oct 2001
- Kingsford, MI
- Blog Entries
It's never booted without being in reset? Sounds like a short in the motherboard somewhere. Perhaps a standoff in the wrong place on the tray. If the board has never booted normally, there's a problem there. Try to figure that one out, and it all might go away, right?
February 11th, 2006, 04:33 PM #11Originally Posted by PC TECH250
PS: why do you push the enter button at the end of each line?
Originally Posted by Whir
I'd take the motherboard out of the case and check the stand-offs like wir is saying
Last edited by Coolzer; February 11th, 2006 at 04:37 PM.
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)
By tcobb64 in forum Technical SupportReplies: 14Last Post: August 19th, 2005, 07:09 PM
By abolith in forum Technical SupportReplies: 3Last Post: April 16th, 2005, 05:28 PM
By CyberGhost in forum General Tech DiscussionReplies: 0Last Post: April 15th, 2005, 10:19 AM
By Tekk in forum Distributed ComputingReplies: 1Last Post: December 27th, 2002, 10:21 PM