Gigabyte MB owners - please post your spontaneous OC reset experiences

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).

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.

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.

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.

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.

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.

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

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

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

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! :)

Quote:

---

Originally Posted by GAM

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. :confused:

So...

MB/BIOS:
CPU:
RAM:

FSB:
Timings:
vCore:
vDimm:

etc. as applicable?

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

Quote:

---

Originally Posted by Eldonko

...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?

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.

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...

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.

Quote:

---

Originally Posted by 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.

---

Are either 2.1v?

Quote:

---

Originally Posted by Rectal Prolapse

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 ;)

Quote:

---

Originally Posted by 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.

---

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...

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.

Quote:

---

Originally Posted by GAM

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 :stick:

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.

Quote:

---

Originally Posted by 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.

---

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 :) )

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

Quote:

---

Originally Posted by 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.

---

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)

:(

i dont have reboots on my dq6.overclocked 36%.But...i have Presler and Kingston hyperX pc 7200 memory..maybe its because of memory or something...so far so good...

Flashing to BIOS F4D seems to have fixed the clock control reseting and reboot loops. I can also boot no problem with >400 FSB. I cant say those problems will not return, but it seems better atm.

GAM, sorry I meant to say that vDimm was also set to normal.

I didn't know that 1.9V was preferred with the EM2s. Even at 800MHz? Anyways, I didn't have any issues with the XP2s. My problem with the EM2 could be because I overvolted them, or the BIOS did if vDIMM set to Normal.

There are so many variables!

Running at 8x375 FSB has been rock solid for me - dual Prime stable for 62 hours even when the heatsink wasn't making proper contact with the center of the CPU! On Tuesday I ran dual Prime for 16 hours just for the heck of it while running World Community Grid at the same time with no problems. RAM timings at 4-4-4-12 with these XP2s.

DS3 F5 (Final) + Presler @ 300FSB/3.6GHz (that's not much of an oc, considering the stock freq is 3.46GHz @ 266FSB)...

I'm getting random OC reset as well. It happens once in a blue moon, but when it does happen, the "Host Clock Control" will reset to Disabled and it'll go back to the default clock speed. It'll only happen when I've shut it down for a day or so and started it again. It's never happened no matter how many times I restarted the system, even if I turn it off, press the power button again to start it.

I've tested with both MemTest, Orthos and 3dmark05 over night and there seems to be no problem whatsoever. Been using this for 3 weeks, even completing Need for Speed most wanted without any problems. The only 2 problems I've seen so far are:

1) OC random resets
2) SATA drive random boot disk failure

These problems only occur once in a while. Does Gigabyte know these problems yet?

Quote:

---

Originally Posted by DARK SIDE

i dont have reboots on my dq6.overclocked 36%.But...i have Presler and Kingston hyperX pc 7200 memory..maybe its because of memory or something...so far so good...

---

According to this, http://www.valueram.com/datasheets/KHX7200D2_1G.pdf, the SPD of your RAM is 1.8v. Now I don't really know what I am talking about here, but this is an indication to me that the RAM is 1.8v.

It would be nice if someone who 'knows' these things could shed some light on the subject.

(I wish I had my board back so could be testing all this.:( )

Quote:

---

Originally Posted by Rectal Prolapse

GAM, sorry I meant to say that vDimm was also set to normal.

I didn't know that 1.9V was preferred with the EM2s. Even at 800MHz? Anyways, I didn't have any issues with the XP2s. My problem with the EM2 could be because I overvolted them, or the BIOS did if vDIMM set to Normal.

There are so many variables!

Running at 8x375 FSB has been rock solid for me - dual Prime stable for 62 hours even when the heatsink wasn't making proper contact with the center of the CPU! On Tuesday I ran dual Prime for 16 hours just for the heck of it while running World Community Grid at the same time with no problems. RAM timings at 4-4-4-12 with these XP2s.

---

Re EM2 1.9v. Refer to http://www.mushkin.com/doc/products/...ail.asp?id=373. Whereas, XP2 indicates a range of 1.9-2.1v. Refer to http://www.mushkin.com/doc/products/...ail.asp?id=350
I was expecting your experiences to be the other way around i.e., EM2 no resets, XP2 resets.

Quote:

---

Originally Posted by Eldonko

Flashing to BIOS F4D seems to have fixed the clock control reseting and reboot loops. I can also boot no problem with >400 FSB. I cant say those problems will not return, but it seems better atm.

---

Good news. Let us know if this changes.

Have you tried F4 final yet? er... and any of the later betas?

Quote:

---

Originally Posted by CrazyJohn

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)

:(

---

As you know, 'Normal' vCore auto sets itself where ever it thinks is best. Probably better to set it yourself even at stock voltage if that works for you. 'Normal' mightn't be giving your CPU enough. I've had spontaneous reboots from Windows with insufficient vCore. (Don't mean to beat a dead horse ;) )
Sorry, I can't offer any other suggestions in this case.

Quote:

---

Originally Posted by ZachSaw

DS3 F5 (Final) + Presler @ 300FSB/3.6GHz (that's not much of an oc, considering the stock freq is 3.46GHz @ 266FSB)...

I'm getting random OC reset as well. It happens once in a blue moon, but when it does happen, the "Host Clock Control" will reset to Disabled and it'll go back to the default clock speed. It'll only happen when I've shut it down for a day or so and started it again. It's never happened no matter how many times I restarted the system, even if I turn it off, press the power button again to start it.

I've tested with both MemTest, Orthos and 3dmark05 over night and there seems to be no problem whatsoever. Been using this for 3 weeks, even completing Need for Speed most wanted without any problems. The only 2 problems I've seen so far are:

1) OC random resets
2) SATA drive random boot disk failure

These problems only occur once in a while. Does Gigabyte know these problems yet?

---

'..."Host Clock Control" will reset to Disabled and it'll go back to the default clock speed. It'll only happen when I've shut it down for a day or so and started it again. ...'
I've seen this circumstance a few times too. Maybe these boards are a bit like car engines, they don't like 'cold starts'. :D

ZachSaw, what RAM?

Quote:

---

Originally Posted by GAM

I've seen this circumstance a few times too. Maybe these boards are a bit like car engines, they don't like 'cold starts'. :D

ZachSaw, what RAM?

---

Corsair ValueSelect 667 @ 800 :D

Not the ram though, since I've had memtest running on it for over 8 hours...

Someone should inform Gigabyte...

Quote:

---

Originally Posted by DARK SIDE

i dont have reboots on my dq6.overclocked 36%.But...i have Presler and Kingston hyperX pc 7200 memory..maybe its because of memory or something...so far so good...

---

try with lower multi on CPU and rise FSB to 420 + and see the reboots :D


you dont have problems cause you dont use high FSBs ;)


there is so many threads of gigabyte mobos that we all already know that all models of gigabyte have reboot problems , sometimes boot with XX settings and next minute dont bot with same settings , ........ and other issues .

GUYS its NORMAL on all gigabyte mobos reboots, and other strange things , didnt you guys realised that yet???


regards

Quote:

---

Originally Posted by GAM

Good news. Let us know if this changes.

Have you tried F4 final yet? er... and any of the later betas?

---

Everything is working fine with F4D so I'm sticking with it. :)

Quote:

---

Originally Posted by Eldonko

Everything is working fine with F4D so I'm sticking with it. :)

---

Furry muff ;)

100th post! :woot:

I'd recommend the F4d BIOS for the DQ6 too. I've never experienced any random resets (except when over 460 FSB, which isn't surprising), or boot loops.

My HZ works fine at 1.8v, in fact more vdimm seems to hinder overclocking.

Quote:

---

Originally Posted by GAM

According to this, http://www.valueram.com/datasheets/KHX7200D2_1G.pdf, the SPD of your RAM is 1.8v. Now I don't really know what I am talking about here, but this is an indication to me that the RAM is 1.8v.

It would be nice if someone who 'knows' these things could shed some light on the subject.

(I wish I had my board back so could be testing all this.:( )

---

No dude....it is 2.0V to 2.2V.That's kingston hyperX ddr2 pc 7200 memory(900mhz factory optimal speed)...i advise you to avoid this RAM because of "elpida" chips inside, who are not good for overclock(sadly i have 2 giga of this ram)...Kingston pc 8500 hyperX(on 1066mhz) have "micron" chips that overclock very good....

Quote:

---

Originally Posted by mascaras

try with lower multi on CPU and rise FSB to 420 + and see the reboots :D


you dont have problems cause you dont use high FSBs ;)


there is so many threads of gigabyte mobos that we all already know that all models of gigabyte have reboot problems , sometimes boot with XX settings and next minute dont bot with same settings , ........ and other issues .

GUYS its NORMAL on all gigabyte mobos reboots, and other strange things , didnt you guys realised that yet???


regards

---

LOwer multi on Presler 920?:eek:
Btw.for me its normal for DQ6 to work fine with no reboots..:D...but i dont like strong overclock..maybe she will go crazy with high vcore,fsb or other overclocking stuff..

Spec as per sig, F6a BIOS
random reboots over 400mhz on the 9x multi (was unstable but bootable with F5)

Quote:

---

Originally Posted by DARK SIDE

No dude....it is 2.0V to 2.2V.That's kingston hyperX ddr2 pc 7200 memory(900mhz factory optimal speed)...i advise you to avoid this RAM because of "elpida" chips inside, who are not good for overclock(sadly i have 2 giga of this ram)...Kingston pc 8500 hyperX(on 1066mhz) have "micron" chips that overclock very good....

---

Exactly what RAM are you using (model nos.)?

Kingston HyperX Dual Channel DDR2 (PC2-7200): http://www.valueram.com/datasheets/KHX7200D2K2_1G.pdf ?

1.8V for the HZ is cool for POSTing and making voltage changes...but has anyone tried to boot in Windows with 1.8V and 800Mhz?

Cause G.SKILL say it needs 2.0-2.1V for 800MHz, i run 2.2V to run at 933Mhz...pretty sure it good upto 1000MHz at 2.2V.

Quote:

---

Originally Posted by GAM

Exactly what RAM are you using (model nos.)?

Kingston HyperX Dual Channel DDR2 (PC2-7200): http://www.valueram.com/datasheets/KHX7200D2K2_1G.pdf ?

---

this one(2 giga i have):







PS.folks from kingston email me and told me that i can run this memory on 2.2V with no fear.

Quote:

---

Originally Posted by DARK SIDE

this one(2 giga i have):
PS.folks from kingston email me and told me that i can run this memory on 2.2V with no fear.

---

This pdf applies to your RAM: Kingston HyperX Dual Channel DDR2 (PC2-7200): http://www.valueram.com/datasheets/KHX7200D2K2_1G.pdf

It suggests to me that the 'default' voltage is still 1.8v (not referring to optimum, ideal, required, etc, just 'default').

Quote:

---

Originally Posted by GAM

This pdf applies to your RAM: Kingston HyperX Dual Channel DDR2 (PC2-7200): http://www.valueram.com/datasheets/KHX7200D2K2_1G.pdf

It suggests to me that the 'default' voltage is still 1.8v (not referring to optimum, ideal, required, etc, just 'default').

---

Sticker on my ram says 2.0V..not 1.8V;)
I have dq6 mobo with c1 rev. of chipset...couple of days and e6400 will arrive...looks like c1 rev sucks for overclock...i think c2 is not in the market...
ps. cpu-z ver.1.36 have data for rev of this chip...

Quote:

---

Originally Posted by DARK SIDE

Sticker on my ram says 2.0V..not 1.8V;)
I have dq6 mobo with c1 rev. of chipset...couple of days and e6400 will arrive...looks like c1 rev sucks for overclock...you have which one?fsb?
ps. cpu-z ver.1.36 have data for rev of this chip...

---

I am not doubting you, just trying to understand the difference between the various references to RAM voltages. Consider the subject dropped ;)

[edit: wrong board. sorry - 8i945pro]
Had... Rev. A1 (according to this old screenshot from Everest):
http://www.xtremesystems.org/forums/...0&d=1156791997
Board is getting 'repaired'-broken CPU socket pin, apparently. Getting very impatient for its return. 2weeks+. :( Apologies for not being able to contribute testing/info at the moment.
Best 'dual-prime stable' OC, before failure, as per sig. 'Decommissioned'.

Quote:

---

Originally Posted by GAM

I am not doubting you, just trying to understand the difference between the various references to RAM voltages. Consider the subject dropped ;)

Had... Rev. A1 (according to this old screenshot from Everest):
http://www.xtremesystems.org/forums/...0&d=1156791997
Board is getting 'repaired'-broken CPU socket pin, apparently. Getting very impatient for its return. 2weeks+. :( Apologies for not being able to contribute testing/info at the moment.
Best 'dual-prime stable' OC, before failure, as per sig. 'Decommissioned'.

---

It's ok;) .You are right...kingston forgot to put the range of voltage in data sheat from 1.8 to 2.2V:) .Thats the only thing here...
good luck with the board...;)

Quote:

---

Originally Posted by GAM

...
Had... Rev. A1 (according to this old screenshot from Everest):
[IMG removed]
...
Best 'dual-prime stable' OC, before failure, as per sig. 'Decommissioned'.

---

Oops. Sorry, screen shot and revision detail is for a different board (GA8i945Pro). Decommission sig details still apply though.

Quote:

---

Originally Posted by DARK SIDE

It's ok;) .You are right...kingston forgot to put the range of voltage in data sheat from 1.8 to 2.2V:) .Thats the only thing here...
good luck with the board...;)

---

Cheers. (just followed up on MB, still not ready. :mad:)

Okay, as I suggested ages ago, I finally tried my A-Data DDR2 533 (1.8v) RAM in the GB 945pro board with a D805.

Results related to subject of this thread: SAME

Set OC in BIOS at FSB-175, ratio 4:8, vDimm Normal (also +0.1 to 0.3), CPU @ 3.5Ghz
Save and reboot
POST
Boot to Windows
Dual-Prime 30mins (okay but CPU throttled due to temp)
Reboot
No POST
Auto Reset 'Host Clock Control' to Disabled
Power Off
Cold Boot
POST with original OC settings!!!

Same behaviour 9 times out of 10 with various settings except the most minimal OC.

Note, running now with G.Skill HZ, FSB 175, vDimm +0.2, CPU 3.5Ghz. No doubt, when I reboot Clock Control will be disabled.
[EDIT - Sure enough, disabled on reboot from Windows]

Quote:

---

Originally Posted by GAM

Okay, as I suggested ages ago, I finally tried my A-Data DDR2 533 (1.8v) RAM in the GB 945pro board with a D805.

Results related to subject of this thread: SAME

---

So the conclusion is that there's a bug in GB's bios across multiple boards? I'm still getting resets on my mild oc. it's a PITA to have to go into bios and set the PCIe and "host clock control" every time this happens...

Quote:

---

Originally Posted by ZachSaw

So the conclusion is that there's a bug in GB's bios across multiple boards? I'm still getting resets on my mild oc. it's a PITA to have to go into bios and set the PCIe and "host clock control" every time this happens...

---

I agree on all points, especially PITA!

Also worth noting, default 1.8v RAM seemed to make no difference. So not distinctly a RAM voltage issue either.

Well my DS3 just wont boot now, going to RMA it (it would loop trying to boot at stock and when I could get it to boot it wont post, everythign seems to work except graphics)

really does do my head in and its stressful lol

Quote:

---

Originally Posted by finlay666

Well my DS3 just wont boot now, going to RMA it (it would loop trying to boot at stock and when I could get it to boot it wont post, everythign seems to work except graphics)

really does do my head in and its stressful lol

---

I'm assuming you've reset CMOS (by Jumper or CMOS Battery removal), disconnected everything, changed RAM if possible, etc etc? If not, search the forum as there are several options that have rectified this situation in many cases. Didn't work for me though, but then, Gigabyte say I had a broken CPU socket pin which doesn't make much sense but is quite possible.

The challenge is fun for awhile, but then it all becomes a big PITA in the end if you don't get results and worse if you end up with a dysfunctional machine!

All the best!

Check this thread out from tomshardware.com:

http://forumz.tomshardware.com/hardw...ict199396.html

This guy has 4 DQ6 motherboards and has had constant rebooting on all of them when he tried to boot with Mushkin EM2-4200 DIMM sticks.

Solution was to use different RAM.

Quote:

---

Originally Posted by Rectal Prolapse

Check this thread out from tomshardware.com:

http://forumz.tomshardware.com/hardw...ict199396.html

This guy has 4 DQ6 motherboards and has had constant rebooting on all of them when he tried to boot with Mushkin EM2-4200 DIMM sticks.

Solution was to use different RAM.

---

Rather unfavourable solution! :rolleyes:

I've come to the conclusion that I only get reboot cycle by applying more than 2.37v (dq6 - bios F4D). 2.37 is iffy, boots sometimes, sometimes not, below that is ok. Havent saw freq clock go to auto again since flashing.

Quote:

---

Rather unfavourable solution!

---

Fortunately for him, the EM2s are low quality - so upgrading to better RAM saved him a lot of headache. :)

I upgraded to F5d, and something strange is happening - I don't get power cycle when I change timings and reboot! Anyone see this?

Disappeared for me when I flashed F4D. :woot:

anyone knows default vcore for e6600?dq6 bios read default voltage for e6600 1.32V....this is default or bug?
On this vcore stabile 400mhz fsb and 3200mhz cpu on x8 multi....

This is pissing me off, mine is going back to default on cold boots. I never really noticed it the first few days because I never completely cut power, pretty much running 24/7. If I shut down the manual fsb control (whatever its called) is disabled, I just need to enable it again and I am back where I left off. At least the FSB, voltage, timing, etc stay set where they were so it's just one setting but its damn annoying having to go into bios every time I start up.

I get random shutdowns. spend half of my life to find the cause. memtest passes ok. 20+ hours ORTHOS stable ok, oc doesn't seem to affect it. Completely RANDOM shut downs and reboots. Prolly isn't my PSU either. I'm gonna change this Gigabyte DS4 (F8 BIOS, tried all others), even if it's not the real cause I'm sure not gonna miss it!!
this is funny. runs ORTHOS 20 hours stable and when i hit STOP at Orthos afer 2 sec computer shuts down!!!
my computer was working ok and this happens suddenly for absolutely not reason :mad:

Sometimes on my DS3 it shuts down for no reason, then won't stay stable in windows for over five seconds. This is with an overclock that passed nine hours of high priority orthos in windows.

So I'll lower the FSB from 464 to 400, and the problem continues.

I clear CMOS, I try again at the high speed, and it works.

The shutdown only appears to occur in games. I am trying it at stock now to see where the issue lies.

I just bought a DS3P rev3.3 to go with my E6600 and Crucial Ballistix D9's. I cannot get anything past stock cpu speeds. The CPU host clock control keeps disabling itself and I have NFI why. I have done all the usual disables in the bios EIST etc but nothing has helped. Memtested the ram, switched slots and nothing.
Upon hitting f10 to save sometime the pc will reboot twice then go into Windows and its still at stock speed or the pc will shut down, everything powers down, then after about two seconds it will power up again.
I'm hoping there will be a new bios release soon as I have no option but to stay with F4 atm.

Opti, this thread is pretty dead. Check this thread out for more details and recent activity on the DS3/4/DQ6.

I have a DQ6, overclocked nicely and essentially stable, which passes stress tests etc. but still suffers those issues every so often. It is a PITA but I live with it-runs 24/7 anyway, so I rarely have to deal with it. Reducing your overclock settings usually avoids it. Definately get a more recent bios as they improved considerably. F7 or F8 (DQ6) is best for most (I'm using F9 because I can't be bothered going back ;)). Equivalent DS3 is F8/F9 iirc.

My OC settings don't reset anymore (reduced FSB to 434 iirc), but I do get 'Wide Area Protection' kicking in occassionaly. I ignore it and everything is fine until next boot.

...anyway, check out and post in the other thread for relavent info and active overclockers with this board.

Good luck.