Gigabyte MB owners - please post your spontaneous OC reset experiences

[GAM]

I thought the issue of 'spontaneous' OC settings being disabled after reboots, cold boots, resets, etc were limited to DQ6 owners, but I understand this occurrence is being experienced by other Gigabyte board owners.

To help isolate the problem/reason, could you please post details of your experiences with these issues.

If anyone knows the answers, please let us all know. Otherwise provide info...

Not sure exactly what info we should be collecting, but I'll make a start as follows. (Note, it is also prudent to note circumstances when this DOES NOT happen.)

MB: DQ6 / F3x onwards?
CPU: E6400
RAM: 2GB G.Skill - HZ

FSB: 350+ (can't remember exactly, but pretty sure this was only happening once I started overclocking around this level.)
Timings: 1:1@4 4 4 12 & @5 5 5 15
vCore: 1.325-1.4, (Normal?)
vDimm: +0.1-0.3

No other changes. At least nothing that helped anything.

Last recalled experience - Had dual-primed for around 20hrs+ @ 3.4Ghz 4 4 4 12 @ 1.3875v - 100% stable. Rebooted from Windows a few 'hours' later and..
beep, nothing, reset, beep and post at default settings!!! Enter BIOS, renable OC, change nothing else, reset, post, boot to Windows - WTF?

Numerous automatic resets after cold boots for no apparent reason too, despite boot and stability with same 'unchanged' settings. Typically I noticed it after 'restarting' from Windows (my machine is rarely powered off).

[Rectal Prolapse]

I have MCE2005 installed, and once my DQ6 went into a continuous reboot when I used the remote to wake the PC up from standby. I'm only running my E6400 @ 3.0 GHz (375MHz FSB, everything set to Normal except Vcore @ 1.35V).

Running official F3 BIOS.

It hasn't happened since, and it didn't reset my overclock settings.

The DQ6 is flaky. Every 5 or so reboots I lose DTS Connect audio. I discovered a workaround for the loss of DTS/DD5.1 encoded audio (and very scratchy 2 channel audio) - I downloaded the Microsoft Devcon.exe utility and force a restart of the Microsoft UAA HD audio 1.0a driver. It could be a Realtek driver problem - I'm using the WDM 1.44 Realtek audio driver.

[Eldonko]

The only issue I have with DQ6 is the occasional continuous reboots. When that happens I just clear cmos, fixes the problem. Using BIOS F3G, I like it so dont plan on switching.

[Rectal Prolapse]

One other thing - I have 2x Mushkin XP2-6400 1GB RAM - it supports 1.8V on bootup, so this might be the reason why I don't lose OC. But then again I'm not OC'ing that high.

I can run 8x400 FSB, but it isn't dual Prime95 stable - it bombs out after a couple of hours. I could probably up the voltage more but I didn't like the 10 degrees C increase.

[GAM]

There's certainly more than one problem here that may or may not be related, continuous reboots (experienced myself and reason I don't have a DQ6 at the moment-RMA'd) and the resetting of OC settings i.e., 'CPU Host Clock Control' is disabled.

I suspect they're related but obviously show different symptoms. I don't know enough about the electronics, engineering and architecture of motherboards. I am hoping that those that understand these things would be able to offer some intelligent insight.

Clearing CMOS after constant reboots worked for me for a while there too, but after flashing to F4a and upping FSB, there was no hope. Tried everything except this: http://www.xtremesystems.org/forums/...d.php?t=113462 (discovered later). Would still like to know whether this works for anyone in the same situation.

ElDonko, what RAM?

RP, next time you're at 400fsb, please try a couple of reboots from Windows (not BIOS) and also a couple of cold boots and let us know if clock control is ever disabled.

Have read of the Audio issues and seen solutions. Not sure if they were the same solution as yours. It may be worth a search.

[Eldonko]

Using XP2-8000 Redline atm, and im going to try an old set of fatbody soon.

I've never had an audio issue (yet), but then again I got fresh drivers online and didnt use the disk at all.

I saw clock control get disabled a few times, but I think it was because of unstable settings and it auto fixes itself. If you have that problem, try a bios clear.

[GAM]

Have you ever experienced disabled clock control with established 'bootable' settings? This is really the crux.

[Eldonko]

Not yet no, but Ive only been running the board since yesterday...

[GAM]

Post back if/when it does or doesn't with OC. You may have a combo that is not afflicted.

[Rectal Prolapse]

GAM, now that you mentioned it I did have the CPU Clock Control disabled and my OC settings reset a couple of times - that was when I was trying for 400 FSB and was using the older F2 BIOS. I was using Mushkin EM2-6400 2x1GB RAM at the time - they suck and since replaced them with Mushkin XP2-6400s.

As for audio stuff, I never used the Gigabyte supplied drivers. Um. I think. I can't remember. BTW, Realtek just released WDM 1.45 drivers now. They've been releasing quite frequently!

I'm not sure if I'll try 400 FSB again - it gets really hot and I hate it when my room's ambient temp goes above 24 degrees - and it is in the basement!

[Eldonko]

Have you ever experienced disabled clock control with established 'bootable' settings? This is really the crux.

Yep getting that now and I'm not sure of the cause.

PCIE Freq changes to auto and CPU Host Clock Control changes to disable. It keeps changing after going back into bios and fixing it unless I reset cmos and then it works properly again.

[GAM]

So...

MB/BIOS:
CPU:
RAM:

FSB:
Timings:
vCore:
vDimm:

etc. as applicable?

[Eldonko]

Here are the settings I have been booting @, not sure if it will help or not. Its most likely just a BIOS bug.

MB/BIOS: DQ6 F3G
CPU: E6400
RAM: Mush XP2-8000 Redline

FSB: 330 (2:3)
Timings: 3-4-3
vCore: 1.425
vDimm: 2.3v

[GAM]

...Its most likely just a BIOS bug.

You're probably right. Interestingly though, I notice the same thing now with my current active MB (ga-8i945Pro/D805@3150).

The only things in common are:
Gigabyte Motherboard, but not 965 S/Dx
G.Skill HZ RAM (2.1v-BIOS +0.3v, Everest showing 2.05v)

Your RAM is rated 2.1v, right? I wonder if this problem occurs for people with 1.8v RAM?

[Eldonko]

RAM is rated @ 2.2v, but boots fine at 1.8v.

I just flashed F4D to see if the issue is still there, will report back after testing.

[CrazyJohn]

MB: DS3 / F4,, F5c, F5e, F5
CPU: E6300
RAM: 1GB Good Ram Pro D9 2x512

FSB: 400
Timings: 1:1@4 4 4 12
vCore: 1.15 @ 1.325
vDimm: +0.1


one a while my system in windows just reboots :|
it is not bios ver, nor any virus... i think it's sth with my gfx, just trying older video drivers...

[GAM]

CrazyJohn, I wouldn't have thought your issue and reset Clock Control is related, but I realise your ram is also using D9 chips and is 2.1v. Hmm.

I know it has been said elsewhere that D9 is not welcomed by these Gigabyte boards.

Is/does anyone out there have 1.8v ram and NOT experience any related issues?

I'd try the A-Data Vitesta I have except I don't have the DQ6 at the moment. I should try with this 945pro I'm using. Will swap 'em over tonight if I get the chance.

[GAM]

GAM, now that you mentioned it I did have the CPU Clock Control disabled and my OC settings reset a couple of times - that was when I was trying for 400 FSB and was using the older F2 BIOS. I was using Mushkin EM2-6400 2x1GB RAM at the time - they suck and since replaced them with Mushkin XP2-6400s.

Are either 2.1v?

I'm not sure if I'll try 400 FSB again - it gets really hot and I hate it when my room's ambient temp goes above 24 degrees - and it is in the basement!

I know the feeling. ...but it's cold here at the moment, so the extra heat is welcome

[CrazyJohn]

CrazyJohn, I wouldn't have thought your issue and reset Clock Control is related, but I realise your ram is also using D9 chips and is 2.1v. Hmm.

I know it has been said elsewhere that D9 is not welcomed by these Gigabyte boards.

Is/does anyone out there have 1.8v ram and NOT experience any related issues?

I'd try the A-Data Vitesta I have except I don't have the DQ6 at the moment. I should try with this 945pro I'm using. Will swap 'em over tonight if I get the chance.

i know i know, but found this topic and thought maybe anyone had any bad experiences concering o/c and resets, since the topic is not crystal clear,

i wouldn't like to be mistaken, and like they say Don't count your chickens before they are hatched
but it looks as i have to set VCore manually to 1.325 undervoltage and/or stock auto setting doesn't work for me...

[GAM]

CrazyJohn, I didn't mean it like that. The D9's seem to invite problems with these boards and may be a significant reason for these issues, if not the only reason. ?!?
That's why I'm wondering whether 1.8v users or non D9 chip users are having the same problems. I don't think this is identified in this thread yet.

You're spontaneous reboot 'from Windows' might be contributable to your undervolted cpu @ 400fsb.

[jimwah]

You're probably right. Interestingly though, I notice the same thing now with my current active MB (ga-8i945Pro/D805@3150).

My box never reset properly, I always cold boot now but I think it goes into a loop if I do reset it - its also a ga-8i945/D805@3560 with cheap DDR2-533.

I also had similar issues with various P4 single cores in my 8i915 board, although that board has been getting worse recently & often reports an "Overclock failed" message at POST, even with BIOS defaults loaded; gonna throw it soon 'cos I'm sick of messing around with it tbh

[Rectal Prolapse]

GAM, both versions of Mushkin RAM (XP2-6400 1GB and EM2-6400 1GB sticks) support 1.8V. But I'm pretty sure 1.8V only at low frequencies (@533 MHz is my guess).

On my DQ6, FSB voltage is set to Normal, which means automatically controlled by the BIOS and Easytunes tells me 2.1V when I run 1:1 at 375MHz FSB.

[GAM]

GAM, both versions of Mushkin RAM (XP2-6400 1GB and EM2-6400 1GB sticks) support 1.8V. But I'm pretty sure 1.8V only at low frequencies (@533 MHz is my guess).

On my DQ6, FSB voltage is set to Normal, which means automatically controlled by the BIOS and Easytunes tells me 2.1V when I run 1:1 at 375MHz FSB.

You mean vDimm set to Normal?

Although both sticks 'support' 1.8v, it looks like the XP2's 'want' or 'prefer' 2.1v. The EM2's on the other hand 'prefer' (or are happier) with 1.9v. [Info gleaned from a couple of web reviews so accuracy is not verified.]

That said, you experienced issues with the EM2's or the XP2's? (I am hoping you're going to say the XP2's )

[burn what?]

i was booting/testing fine at my sig specs, then did updates. namely the intel .inf update from the cd and the jmicron update from windows update. after reboot, i couldn't get to windows at all. checked and reset all oc stuff to stock in bios, nothing. finally did a windows repair from os cd and came back up fine. i then did the .inf update from gigabyte site which was newer than cd and is fine. i'm not retrying the jmicron update, as i think that was it. i'm raid 0

[CrazyJohn]

CrazyJohn, I didn't mean it like that. The D9's seem to invite problems with these boards and may be a significant reason for these issues, if not the only reason. ?!?
That's why I'm wondering whether 1.8v users or non D9 chip users are having the same problems. I don't think this is identified in this thread yet.

You're spontaneous reboot 'from Windows' might be contributable to your undervolted cpu @ 400fsb.

Surprisingly when i set normal VCore it did reboot :| I'm so tired of this MB...
The last thing which i changed in bios was IDE from AHCI... And it's sooo strange, yesterday my pc worked whole day without reboots, today it rebooted 10 min after turning on... ;/
Anyway it's not undervoltage... nor these C1E, EIST features, i've disabled them...
I guess it worked like a week ago on the same settings ;/
What is even more funny Orthos, Spi, GoldMem all stable... :|

PS These reboots are i guess not windows concerning, i've installed a fresh copy of windows and disabled autoreboot in settings (in order to see all BSoD)