Official GIGABYTE Forum
Questions about GIGABYTE products => Motherboards with Intel processors => Topic started by: Spagnum_dk on March 21, 2010, 12:14:23 pm
-
Hi
Motherboard: X58A-UD3R
Processor: i7 930 @ 2.8 Ghz, no OC
OS: Win 7 64bit home Danish.
Memory: 6 GB DDR3 Kingston.
Bios: F5
I have a problem with shutdown and sleep.
The computer always restart after 3-5 sec. The only way to shut the computer down, is to cut the power.
This was not a issue when I revive my new computer, this is after i upgraded the Bios or change some setting in the Bios
Any ideas ?
-
Edit:
The Computer runs normal, but when I want to shut down the computer, it automatic restart after 3-4 sec.
If I cut the power to the power immediately after the PC shut down, I can turn the power back on, the computer don't restart and then I can start the computer the normal way.
-
Same problem on X58A-UD7 :(
http://forum.giga-byte.co.uk/index.php/topic,1316.0.html
I asked this question in GigaByte Taiwan website and they reply to me saying it is because ITE chipset is faulty and ask me to return for a replacement.
-
I have the same problem on UD3R too.
Or kinda have... I cleared CMOS, updated bios to F5, disconnected one harddrive (WD 1TB Caviar Black 7200rpm SATA III w/ 64MB Cache) and reinstalled win7 64 (had to do it for other reasons). Now it shuts down properly...
I tested shutdown pretty much after every option change in bios and after every driver install in OS.
Now all SATA controllers are in AHCI mode.
OS is installed in IDE mode and then AHCI mode turned on.
I didn't turn on quick boot option yet.
This time chipset drivers were first thing I installed.
I didn't try reconnecting that SATA3 hdd back yet.
I didn't install energy saving utility yet.
I don't quite remember at what point system started to shutdown normally (probably after cmos clearing and bios flash). I had it fixing itself before too, when I flashed to F4, noticing the problem and flashing back to F1 (I thought it was a bug in F4). Except it then came back in F1 too...
I didn't try sleeping or hibernating in windows yet. I wonder if bios gets confused about it's shutdown state and treats S5 as one of sleeping states or something...
-
Hi
Problem solved! :)
UnFleshedOne gave me the solution, thx
Under “Integrated Peripherals”
I change all SATA setting from IDE to ACHI.
I change …
ICH SATA Control Mode
eSATA Ctrl Mode
GSATA 6_7IDE Ctrl Mode
GSATE 8_9IDE Ctrl Mode
…. from IDE to ACHI
The restart issue was properly after BIOS upgrade, then all BIOS setting is set to default.
I have also reinstalled Windows 7 but that did not solve my problem, I wish I had this solution yesterday ???
-
It just started doing it again for me...
What I think happened is:
I have Cosmos S cooler master case, with sensor power button. Just now when machine was off I hit it about 3 times in short interval (I thought I missed first 2). It started up and then immediately shutdown, then started up again. I suspect that at this point dual bios detected failed post or something and restored bios. It then restarted machine again and I got into cleared bios (even date and time were reset).
I set correct time, loaded all settings from memory (my saved profile and last good boot weren't deleted), booted into win 7 and logged in. Then I immediately shut it down. It restarted instead.
I think I tried another couple of times and then I cut power and cleared cmos (pressing down the button in the back for 10 seconds).
Interestingly, clearing cmos didn't clear date and time.
Then I loaded profile from a flash drive instead (pretty similar to what I had in memory).
Booted into OS and shut it down and it was staying down properly...
So I guess it isn't any bios settings, like ahci versus ide. It is a glitch with dual bios autorestoring. Or something...
-
It also happened for me again……
I can get it up and running, if I press the reset BIOS button and make a new configuration.
But it only last one day, next day, the PC f***ed up again.
UnFleshedOne suspect Dual Bios, I agreed
So now my motherboard is replaced with a new one.
Hope this will work
-
Spagnum_dk, did you get X58A-UD3R again?
I see this problem pretty much every cold boot too. Just shutting down, letting it cool down for a minute and powering back resets bios, system clock and all (but not saved profiles)...
I'm going to see if retailer will replace the board before RMAing it to gigabyte.
-
Yep, the PC was only 10 days old, so there was an warranty on the board.
-
Update:
Got a new motherboard install yesterday, this morning the machine did the same, there was a bios failure, I configured the BIOS again, but still Windows restarts on shutdown. >:(
Now I will try to return the whole PC
-
I'd expect much more people with same problem then...
Can you post all your components if you didn't return it yet? In case it is some weird incompatibility with PSU or something.
Mine are:
Case: Cooler Master Cosmos S, full tower
PSU: Corsair CMPSU-850TX
CPU: i7 930, batch 3001A135
CPU cooling: Cooler Master V8
RAM: GSkill F3-12800CL9T-6GBNQ, triple channel, 3x2Gb
DVDRW: Samsung S243D/BEBE 24x SATA
HDD: 150 Gb velociraptor (SATA2), 1Tb WD black (SATA3, 64Mb cache), 1Tb WD black (SATA2, 32Mb cache)
OS: Win 7 Ultimate, 64 bit
-
Can you also post batch number of you MB? (apparently first 4 digits in serial number). And for old one if you still have it somewhere.
Mine is 1006
-
Hi.
Another update. I downgraded my BIOS from F5 to F4, and my PC has been stable for 3 days now.
This is what I know about my components:
Case: Vision Silent miditower
PSU: Energon 750W
CPU: i7 930
CPU Cooling : Scythe Shuriken Retail
RAM: DDR3-1333 Kingston 3 x 2GB
DVDRW: Sony AD-5240S-0B SATA DVD-RW Black
HDD: 1TB Seagate SATAII 7200 RPM.
OS: Win 7 Home Premium, 64 bit.
I still have the box from my old motherboard, and the serial starts with 1004
Can't find the serial on the new motherboard.
-
first thanks UnFleshedOne
http://forum.giga-byte.co.uk/index.php/topic,1316.0.html
can you guys check you enable the turbo boost etc power management related setup in CPU setup ? Try to disable all power related setup including those in CPU section?
-
I can't check now, since my new MB doesn't seem to have the problem. But I'm fairly sure I did try disabling everything possible power related, including CPU options, which I disabled for overclocking anyway. It is still possible that every time it got the problem (cold boot, bios resets, windows starts rebooting instead of shutdown from now on), some of those options were enabled -- I didn't specifically control for them.
I suspect all the solutions just make it go away for a while...
It is also possible that "cold boot reset" and "reboot instead of shutdown" are two completely unrelated problems that just happen to manifest together on the board I had. Since nobody specifically reported first one... (or did I miss it?)
If you are right and i7 power options are what is causing it, you should be able to reproduce the bug at will: turn off all CPU options -- problem goes away, turn them on -- problem is back, and it goes away again when they are off.
-
Hi.
Update.
The supplier has changed my mother board ones more.
So this is motherboard number tree.
So far the PC is working with no problems :)
-
I have the same issue, no matter how I shut down the pc, after a few seconds it boots up again, unless I cut the power. I wrote gigabyte support and they gave me nothing, except to return the board to the retailer. Now that I don't want to do since dismantling the computer would take half a day, and after that I'd stuck for two weeks without a computer while the retailer sits on the returned board. (they confirm that its faulty 2-3 days, then they return it to the distributor, who also check if its really faulty that's another week, and when they give the go ahead the retailer orders a replacement, which if I'm lucky I can get in two days)
As I see nobody was able to confirm what causes this problem, even the replacement didn't solve it permanently. But everyone just suddenly disappeared, so I ask: Did you gave up all hope, or you found the solution and just didn't bother posting it?
-
I have the same issue, no matter how I shut down the pc, after a few seconds it boots up again, unless I cut the power. I wrote gigabyte support and they gave me nothing, except to return the board to the retailer. Now that I don't want to do since dismantling the computer would take half a day, and after that I'd stuck for two weeks without a computer while the retailer sits on the returned board. (they confirm that its faulty 2-3 days, then they return it to the distributor, who also check if its really faulty that's another week, and when they give the go ahead the retailer orders a replacement, which if I'm lucky I can get in two days)
As I see nobody was able to confirm what causes this problem, even the replacement didn't solve it permanently. But everyone just suddenly disappeared, so I ask: Did you gave up all hope, or you found the solution and just didn't bother posting it?
Can you give a few more concise details of your setup please and maybe we can discover the answer to your problem.
-
My second MB didn't have this problem. I'm running 64 bit Win7 for several month now without any problems.
-
I had this problem and it was driving me nuts. For months I have been without power off and S3 functionality. I was THIS close to RMAing the board when I finally found a solution.
The problem is some strange BIOS or hardware bug and has not been fixed even as of the f6 beta. It is possible the bug is a hardware bug only on the V1 board.
I know for a fact that it is a BIOS or hardware design flaw and not a driver problem because you don't to boot Windows to demonstrate the problem.
If you cold boot the computer and press END on the bios start screen you enter a bios utility which purpose is to back up or restore the bios from a drive. In that utility there are menu items that let you either immediately reboot or turn off the computer. If you select the "turn off computer" item, the system turns off and then immediately reboots (if you have the problem.) This happens even if you have just performed cold boot from a power-cord removed state.
I tried repeatedly loading the default/failsafe settings, but that never worked. I even tried flashing to F5 from F3, then F6beta from F5, to F1 from F5, and then back to F5.
Finally out of desperation I used the blue CLR CMOS button on the rear of the computer (with the power off!) and this caused everything to start working properly again. (I also cleared the DMI pool, but I now believe this had nothing to do with the fix since I ended up fixing the problem twice and didn't clear the DMI pool the second time.)
Interestingly enough, the problem reappeared after about 30 minutes when I tried to let the computer auto-enter the sleep state. I had already manually shut down the computer successfully several times as well as manually entering the sleep state and restoring several times. Remember I had been unable to do this for months prior.
As an experiment, I saved the BIOS profile and used the clr-cmos button again, and again the problem went away. I then restored the saved profile and the problem was still gone. Whatever causes the problem it is not touched by saving or loading the cmos settings via bios software, but IS fixed by hitting that blue button.
I then upgraded my INF to the latest version and turned off USB selective suspend and disabled wake timers in the power options dialog trying to find a magic bullet fix that would prevent the problem from appearing and have not since (in two days) had any problems. Whether I stumbled across a fix that is keeping the cmos from getting messed up or whether the cause is random and I just haven't hit it again yet I don't know.
Does hitting the clr-cmos button clear more of the cmos than can be done from the bios utility, or is there some other part of the same chip that latches up and needs resetting that simply cannot be reset any other way because of the constant application of battery power? I don't know that either.
I do know that twice in a row I was able to fix the problem by saving my cmos profile, hitting the blue clr-cmos button with the power off, and then restoring the profile.
If using the "shut down" option from bios utility you get to by pressing the END key on boot doesn't cause a reboot for you then this probably won't help, but it has sure been a lifesaver for me. I am very confident this will fix the problem for some people since I had to do it twice and since the second time it was the only action I performed to fix the problem.
-
I think that you are getting mixed up between the BIOS and the CMOS. The CMOS is a memory of all your hardware that you have installed. The BIOS is a list of settings of how that hardware is to be configured on startup. Changing the BIOS options has no bearing on the CMOS. That is what is cleared by the Blue Button and cannot be done from inside the BIOS.
-
I think that you are getting mixed up between the BIOS and the CMOS.
No, I am not getting mixed up. Sorry, but your statement is in error. The BIOS is the firmware which is flashed to the FLASH non-volatile bios chip. It is the software which runs when you first power on your computer. It is the software which MANIPULATES the settings. No settings are stored in on the flash chip itself as it must be erased prior to being written. (When you flash your BIOS, this is the "erasing flash" stage.)
CMOS is the batter-powered static ram which stores the settings manipulated by the BIOS as well as the DMI pool. Everything you change using the BIOS is saved in the CMOS.
"Changing the CMOS" and "Changing the BIOS settings" are synonymous for the most part (with the exception of the DMI pool.)
The list of resources you mention is the DMI pool and is also generated by BIOS -- it is just not user generated. It is also stored in CMOS, but as I already said, I don't think the DMI pool is the problem. (Of course, clearing the cmos also clears the DMI pool as they are stored on the same physical chip at different addresses.) Why don't I think it's a DMI problem? Because clearing the DMI is a simple process of erasing a range of addresses which triggers the BIOS to completely rebuild the table. I find it hard to come up with a problem that would not disappear after performing a complete table rebuild. It's not impossible, just unlikely. (Besides, does it matter really? Hitting the blue button fixes the problem. Maybe it's a DMI problem. Maybe it's a bios settings problem. Regardless, it's a bit in the cmos problem probably.)
Until proven wrong, I stand by the solution posted above.
-
I didn't say your solution was wrong only that I thought you were getting mixed up. The BIOS chip is 8Mb and when you flash the BIOS you only flash 1Mb so the rest of the information stored is still there.
-
I didn't say your solution was wrong only that I thought you were getting mixed up. The BIOS chip is 8Mb and when you flash the BIOS you only flash 1Mb so the rest of the information stored is still there.
When you press the blue button the rest of the information is still there, too. The BIOS chip requires power to be erased as it is FLASH and not battery powered. If that wasn't the case, pressing the blue button would erase your BIOS and you would no longer be able to boot at all!
-
Well I am glad to see that you do understand it all and that you have fixed your initial problem. ;)
-
Yep, clearing CMOS was fixing it for me to. But it would always return eventually.
-
Yep, clearing CMOS was fixing it for me to. But it would always return eventually.
I will cross my fingers that updating the .inf will fix the problem more permanently for me. Before I updated it, the problem reappeared within thirty minutes, but after updating it the problem has gone away for several days and the computer has been through at least 50 s3 sleep/restore cycles. Here's to hoping...
-
Hi All,
Joined to share my frustration with this restarting business. Its exctly the problem as original poster but my board is P965-DS4, firmware F11
Mine started after about 8 months of use. After googling, I found a forum where they were talking about replacing the BIOS battery, so I did. I have been replacing batteries everytime it starts rebooting....battery lasts about 6 months.
But recently it developed a new fault, along with the reboot issue. When I restart the PC I get the single beep, then detecting HDD..then rapid beeps and PC restarts again, this keeps looping. So I unplug the power, wait few minutes and reconnect. It boots up fine but the original restart after shutdown returned. I replaced the battery only a month ago, so cant be that.
I am begining to get cheesed of with Gigabyte, the last 2 boards lasted last 2 years, failed just after warranty period, sodds law.
If anyone know what this rappid beeping is, please let me know.
----------------------------------------------------
Model Name : GA-965P-DS4(rev. 1.0)
M/B Rev : 1.0
BIOS Ver : F11
VGA Brand : GIGABYTE Model : GT9600 silent
CPU Brand : Intel Model : E6400 Speed : 2.4Ghz
Operation System : Win 7 64-bit
Memory Brand : Kingston DDRII
Memory Size : 8Gb, 667Mhz
Power Supply : 550 W
-
Well it would seem from your description that you have two different problems. TYhe first would sound like a short on the board that keeps draining your CMOS battery down and secondly maybe a memory or power fault. Can you list your hardware for us please?
-
Hi Dark mantis,
Thanks for the quick reply, here are some more details, pls let me know if I have missed anything.
Core2Duo E6400 2.4Ghz - No overcloking
Antec Neo 550watts PSU
Antec Solo case
1xDVD
1xDVD-RW
2x Hitachi 160Gb, raid 0
1x Hitachi 250gb
4x 2Gb Kingston DDR2 667
GA-8600GT silent
1xantec 120mm fan near
2x80mm intake fans
-
The first thing that stand out especially if it is a bit older is the PSU being underpowered. The thing is power supplies deteriorate with age and use, the capacitors suffer from droop and the output drops. I would see if you can replace(test it) it with a new higher power model preferably something like the Gigabyte Odin or Corsair 650w at least to give you a bit of headroom for the future.
-
Many multiple fast beeps is often memory setting tRD (Static tRead Value) Set too low.
Please press Control + F1 on the MAIN page of your BIOS, the screen will flash, then enter the MIT Section and tell me if you see the above mentioned setting anywhere in your memory settings. Sorry, I can't remember if 965P has this or not.
If you do not have the setting I would try to borrow a different set of memory from someone for testing if you can to see if that is the issue or not.
*Edit*
Actually, just checked your BIOS and you do not have this option. Please try setting Performance Enhance to standard if you do not have it set that way already, then if the same occurs please try High Speed Dram setting option 1 and 2 and see if either of those help.
I agree with Dark Mantis as well, if you can please test with another newer or larger PSU to see if that alleviates either issue.
-
Thanks guys for your quick replies, I will check the settings.
Also, now that you mention it could be memory, I will put the old memory back in to test. Only reason I changed the memory recently was that I got them for next to nothing and that my previous 7Gb was mixed size and brands.
-
If using 4GB or more you will need to increase your NB voltage, keep that in mind.
-
If using 4GB or more you will need to increase your NB voltage, keep that in mind.
Yes a very common problem that is easy to fix.
-
Sorry, never messed around with these voltages, always went with the default, how do I change the NB voltage.
I will also try this when I get home tonight.
Thanks
-
It will tell you in your manual but it will be in the BIOS under the MIT section and labeled MCH control or similar. You only need to raise it by a little and see if it helps with the stability.
-
OK, I got myself into a irght mess last night, after resitting the rams, hoovering the any dust out, got frustrated rest the bios and the dmi data.
Now I've lot one of the raid 0 disk, it says 'non-member' for one of the disk, the other one still says member. overall the raid array 'failed'.
Any way I can get the data out?
If I remove the other disk amd make it non-member, will it delete the data or the raid info?
I thought then I can create the raid at it was before and get the data back?
-
You will have to rebuild the RAID to get the data back. Why it has dropped of is another matter. Have you moved the data cable to another port or anything like that?
-
No, I did not touch the sata cables, I did how ever unplug the power from all hdd and mb.
Only good thing that came out of this is that after I thought I had nothing else to lose, I did a restore of bios from backup to main. Now the pc stay shutdown. Real proof will be once I've installed W7 again.
-
It's just one of those days for you isn't it? I wouldn't even touch the computer any more! ;)
-
Anytime you reset the BIOS, flash it, or load Optimized or Fail Safe (Never suggested), always be sure to reboot RIGHT BACK to the BIOS to then set your RAID options again - otherwise if you try to load windows and forget to set RAID again you will corrupt your array.
Hope the reinstall goes smoothly for you!
-
Thanks for the tips,
It appears that I cannot boot from a USB stick and USD HDD works but extremely slow. Both these methods work ok and install Win7 quite fast on my old laptop.
I had to resort to DVD, even that was sloow, its been a while so I forgot to diable the floppy, and what a difference that made to the installation time.
Anyway, back to the original issue of rebooting and rapid beeps.
After the rebuild, its still doing it and it appears that when I put the PC to sleep, it goes in Hybrid-Sleep, turns everything off, because of the reboot issue it never stays of and thats when the rapid beeps sound.
-
Cant belive my luck, it looks like its the motherboard, I tried two other PSU's One Antec and one unbraded, PC keeps restarting.
Now it restarts as soon as the rocker switch at back was turn on.
What buffles me is that every article I read about the PS_ON# says 5v= OFF and 0v= ON. When I measured the voltage on pin#16 on the power connector, it was complete opposite. when the pc was on it was 5.02v and when I shutdown, for the 2-3 seconds that it stays off it reads 0.86v.
Is there a way to fix this? maybe the logic driver has gone wakky, is that replaceable?
P.S. Gigabyte we're not interested, after a week their answer was 'its out of warranty'.
-
You haven't got a sticky switch on the case have you?
-
I wish it was the switch, would have saved my £83 for the Asus PSQ5 Deluxe......yes back to Asus
-
What motherboard did you have. I took it that it wasn't that old. There is a 3 year warranty on the motherboards, some more. ???