Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
- Did you reset the CMOS yet?
As I understand it, you currently have the PC set up out of the case. This is good. First, reset the BIOS. Then, turn it on and see if the PSU will function normally. Don't go into the BIOS, don't touch anything, just see if it boots up without crashing or rebooting.Anyone available to assist step by step. I think it would be the quickest path.
Thank you...
I'll stop this and do whatever. When you say RESET the CMOS do you mean clear it with the jumpers?
Wait, so are the BIOs hangs and resets gone now that the mobo is on a cardboard box AND the USB devices are unplugged?
Also, what USB devices did you have connected to the system when the problems were occuring? Which ones did you remove when the system finally booted?
Yes.
I have:
- LCD - USB hub
- Timex DataLink Watch
- Sansa Fuze
- HP Printer
- Logitech Webcam
- External HDD 400G IDE
- TrippLite UPS
I unplugged everything at one time not one at a time to test each.
Here's what I did. Reconnected all 5 USB devices. Hangs. Reboot. Hang.
Who makes the external enclosure: Ximeta. I think the HDD inside is Seagate. Been in the case almost 2 years by now....roughly.
+1. If it works without the USB devices but not with them, then one or more of them must be the culprit.OK since the system is working fine without those 5 USB devices, guess what? You get to play detective and see which USB device is hanging your system.
It may not be one device. What if it matters when I simply unplug about half the USB devices?
It may not be one device. What if it matters when I simply unplug about half the USB devices?
But why did all this shit work previously and then crap out later? Same issue but new mb and RAM?
What? R U shitting me?
Different computer, different story. Keep troubleshooting.Somethings whacky here. This shit all worked on this PC and the other mb/RAM. What gives?
Set the settings back to default. If that message still occurs, ignore it for now and concentrate on the USB devices.
If I plug the Sansa dock into the mb direct instead of the LCD hub I have the issue. If I go into the BIOS I get that error message above. What's the correlation?
If the Sansa Fuze is plugged in this causes a problem. It seems. The Fuze want's to draw power right away and I wonder if this is a problem for the mb. So, it won't work in Windows then apparently? That's fucked up as I got the Fuze for Christmas. PCs at their best.
Do you see that error message with the Sansa dock?
Try using the Fuze in Windows and see if any errors occur? And yes there might be a compatibility problem between your mobo and the Sansa dock.
It's not the dock itself but the Sansa Fuze. I tested it just using the USB data/charging cable that comes with the Fuze. Tell me that's not a larger problem of some size for Gigabyte.
Yes, I did get the red error in the BIOS. Not sure how many times I the reboot has to hang to generate the error when going into the BIOS.
Default BIOS: presents a problem. What can I adjust? Otherwise I've wasted money on all of this. The CPU mult is off by default, etc.
But have you tried plugging in the Sansa when Windows is fully loaded?
I have Legacy USB Storage Detect enabled so if I want to boot from a USB device. The Fuze comes on as soon as the PC does (gets power). The PC is trying to boot from the Fuze. I think disabling this will clear up this problem.
Also, the red error alert (as I referred to it) will happen as a warning. Why? The voltage range in this mb is quite large. 1.8v is the highest for normal and anything after that is considered overclocking. So, even though the RAM is 2.2v the board will throw this error as a warning since 1.8v is the top standard (I guess you'd call it) anything higher is OCing. The warning, of course, is to let people know if they are pushing the voltage too high on RAM that is not rated for voltage that high...that it may get damaged.
I concur. It's worth a try.
Never ran into this probelm with other Gigabyte motherboards. But if that's the word from Gigabyte, then yeah, news to me.
Danny: you've been very helpful and I've run into an error testing with OCCT. When OC'd to 4.05Ghz I get an error after 10 minutes when running the Auto 1Hour CPU test. It reports an "Error reported on core #1". I have a handful of PNG images that OCCT produced. I set the OCing back to standard settings to not OC for now.
Have you run into this error? I've done some research but not finding what this may be.
That just means that the test failed for some reason or another, which is usually caused by either your CPU or RAM being unstable at the settings you were running them at.Danny: you've been very helpful and I've run into an error testing with OCCT. When OC'd to 4.05Ghz I get an error after 10 minutes when running the Auto 1Hour CPU test. It reports an "Error reported on core #1". I have a handful of PNG images that OCCT produced. I set the OCing back to standard settings to not OC for now.
Have you run into this error? I've done some research but not finding what this may be.