DS3 Cold Boot SOLVED, But how did I do it? !

Markdek

[H]ard|Gawd
Joined
Jan 5, 2007
Messages
1,471
I just got through a few days of struggling w/ a cold boot problem on a DS3 Rev. 1.0 board, that started when I tried to use some new Crucial Ballistix ram. Keep in mind I'm just trying to keep a modest 400x8=3.2 / 4-4-4-12 overlock (and using F11 bios)!

Up until yesterday, there was NO combination of bios settings that solved the cold boot (I define the cold boot problem as a reset to stock settings after the computer was off > than 6-8 hours).

What were the last few things I tried before almost giving up, and chucking this board in the garbage (And I was really going to chuck it!!)?

- I moved the PCI-E voltage to 102, from 100.
- I pulled the CMOS battery for a while, then put it back in (I didn't use the reset jumper)
- I turned off "Hibernate", after turning it on about the same time I put the Crucial in (bad idea!)
- I may have made a few bios setting changes, but nothing I could put a finger on that would have helped.

Guys, I think it was turning off "Hibernate" that fixed the Cold Boot. It's got to be. The second best choice is move PCI-E up to 102, but it worked fine at 100 for 3 months. Does anyone know if Hibernate could have caused the cold boot?

I think the motherboard and ram are fed some juice, even when the power switch is off, but the PSU is plugged in. When you power on, the motherboard does something w/ the ram on boot, and that's what craps out; and it has something to do w/ hybernate. Hybernate perhaps sets up the ram to accept the ram dump to the hard drive, and that something did not like these overclocking settings being in place, hence the cold boot.

Anyway, the boards working now, hibernate is off, and I really don't want to do any more testing, for now, that could upset the current stability.

Actually, none of this really matters because a P5K Deluxe is going in the TJ09 as soon as the new board comes in.

Anybody want to buy, what now appears to be, an OK DS3 Rev. 1.0 board?

Mark
 
Crazy nonsense, isn't it? Never a solution that works for everyone, 100%; just makes you wonder.
 
Guys, I think it was turning off "Hibernate" that fixed the Cold Boot. It's got to be. The second best choice is move PCI-E up to 102, but it worked fine at 100 for 3 months.


upping the PCI frequency is an old "fix" for the cold boot issue. Unfortunately it doesnt work for everyone.

this is the first time I have seen Hibernate mentioned as a fix, most OCers dont use Hibernate but that means nothing, anything that works, works :)


This might be of interest.

http://www.hardforum.com/showthread.php?t=1193054
 
I knew about and have used the ISO backup thing; But, I've never had a problem eventually booting the machine (Reset!!), but the bios would come up as stock, not the overclocked settings.

The Hibernate is interesting, and obviously it's all to do w/ the power management features. With power management off, or by not using it, I have returned to stability. I doubt the pci-e frequency did it, but it's still at 102 anyways.

Tomorrow I should have the new Asus P5K Deluxe, and I look forward to installing it Thursday, Friday or the weekend. It was time to move up to a higher end board anyway, with more features, etc. I never installed an Asus so we'll see how it compares to Gigabyte.

The DS3 Rev. 3.3 continues to do fine in my Lian Li build of a month ago.

Thanks Bill.

P.S. The bios corruption is a possibility, but that's no reason why it doesn't boot on the "1st" bios successfully, which is the bios w/ the overclocked settings.

Are all the bios backup versions now fixed do you think? After several reboots, does the bios fix itself; i'm talking about all these copes (either 2 or 4)?
 
The confusing thing about it is that Gigabyte (as far as I can tell) sorta mixed up the bios procedure they posted having both boards like mine with 2 bios chips and the others with one and I am not sure what part of the "bios flow chart" is exclusive to each kind of board. I mean I think I can figure it out, it should be obvious, but I would have liked it better if they gave two procedures, each one for a specific kind of board. Honestly I should go back and study it some more but was so exicited when I found it and and the (apparent) lack of knowledge the utility even existed, I posted before I completely understood the whole deal figuring anything would be a help if it prevented a dead board.

Trouble is I have a DQ6 and yes, if anything goes wrong with the primary, it will boot from the backup and optionally fix the primary. It works great. OC settings and all. While I have been able to cause the machine to go into a "continous" reboot mode, just killing the power and rebooting has always brought me back (unlike some DS3 owners who get dead boards).

Honesly I dont know, its susposed to work but I dont have a DS3 so I cant play. I was mainly trying to make as many "safety nets" as possible known to DS3 owners.

Not too sure about that, thats what I am worring about, if you OC too hard and the machine starts its "rebooting cycle" its trying to determine proper bios settings and I assume rewriting the bios. Suspose you happen to get tired of it and hit the power right when its rewriting the bios, possible corruption and maybe a dead board. Its only a wild ass guess as to why some people are ending up with non-bootable boards but with the bios image on the HD at least there was some chance of getting the machine back.

So I readly admit the DS3 cold boot issue is still a mystery to me. Some things work for some people and some people are so fed up they get another board. Its a damn shame cause when it works right, its a great board. It really pisses me off Gigabyte has no forum or has (afaik) not communicated to customers what is going on. EVGA next time.
 
How could any setting in the OS have an effect on the PC before boot?
 
I have spotty info on this, but the motherboard is powered up, even when you turn it off. Second, the motherboard has to know if you're going to use Hibernate, which is one of the power management functions, if it is to write the contents of Ram to the hard drive, and, when you wake from Hibernate. Power management is also turned on in the bios. Third, Hibernate may actually set a side Ram address for this dump to the hard drive. Fourth, I think it's the ram and other self checks, that preceed the boot, with the Power Management on, that trips up the DS3. If you google it long enough, there is a little info you can find on it. Finally, I have no real idea.
 
Back
Top