Official GIGABYTE Forum
Questions about GIGABYTE products => Motherboards with Intel processors => Topic started by: Jamesd on January 24, 2012, 05:27:49 pm
-
I have the mainboard GA-N680SLI-DQ6 http://www.gigabyte.com/products/product-page.aspx?pid=2460#fq (http://www.gigabyte.com/products/product-page.aspx?pid=2460#fq) which says it doesn't support the intel E8300 duo CPU. However I fitted the E8300 duo before realising it wasn't compatable with the mainboard and it worked with no problems. The only problem was the CPU was running at 2.6 instead of the 2.8 its supposed to as stock. I raised the FSB so the CPU ran at 2.8 and the PC seems to work fine with no problems. I did notice that in the bios it says Vcore fail.
What does Vcore fail mean? I assume its because the CPU isn't supported. Is there anyway to clear the Vcore fail error? If I continue to use the E8300 chip in this mainboard will I risk damaging the mainboard or the CPU. Why does the CPU appear to work correctly even though the mainboard says its not supported? Is it ok to use the E8300 chip since it seems to work even though its not supported?
Any information would be great
Thanks
-
You're putting a 45nm CPU in a board that only supports 65nm CPUs; the risk is putting too much voltage on it. Be sure you don't go over 1.3625v per your link.
There may be other issues, but that's the biggie.
-
Thank you for the reply. I thought this was maybe the reason the CPU was not supported but I noticed on the support list the board supports an E6300 CPU. According to intel the E6300 CPU is 45nm http://ark.intel.com/products/41493/Intel-Pentium-Processor-E6300-(2M-Cache-2_80-GHz-1066-MHz-FSB) (http://ark.intel.com/products/41493/Intel-Pentium-Processor-E6300-(2M-Cache-2_80-GHz-1066-MHz-FSB)) I did also notice that the FSB speed on the E6300 is 1066 where as my E8300 is 1333 but with that said some 1333 CPU's are in the support list for my board although I think they are 65nm. Could the reason my E8300 isn't supported is because its 45nm and 1333 and the board only supports 45nm with a fsb speed of 1066? Or shouldnt that make a difference?
Is the risk putting too much voltage on the CPU or on the board? What voltage should not go over 1.3625? The CPU voltage?
Sorry for all the questions, and thanks for your reply.
-
Your CPU max voltage (Vcore) is 1.3625v (but you shouldn't have to run that high unless you are overclocking quite a bit).
I was imprecise: a smaller die process uses less voltage; if your board were to incorrectly interpret VID from the CPU (hence the Vcore fail message), it could damage the CPU if it were to put too much voltage onto it, regardless if your board supports other 45nm CPUs. (I don't think it does since BIOS updates only list Kentsfield.)
Additionally, there are two E6300s (what genius :/): http://ark.intel.com/products/27248/Intel-Core2-Duo-Processor-E6300-%282M-Cache-1_86-GHz-1066-MHz-FSB%29
I would use CPUID's Hardware Monitor, CPU-Z, and IntelBurnTest to ensure everything stays within tolerances.
-
Ok thanks for the reply, if I set the voltage manually in the bios to under 1.3625v will this solve the problem? Or is it still to risky to run the E8300 CPU?
Two E6300's thats handy! I'm guessing the E6300 that my board supports is the 65nm one and not the 45nm.
Should I remove the E8300 CPU and get a new one that is on the board support list?
-
If it works, I see no reason to not use it.
What does it report Vcore is now? If it is <1.3v, you can set that manually as a starting point.
I've set my Vcore manually to overclock the C2D anyway. See how fast you can go.
-
I used a gigabyte board that didnt support my processor the one i used was 125watt and it only supported 95 watt that was 2 years ago now that board is in a friends computer with that 125 watt processor and still running strong. Just make sure your setting are right and hope you have the same luck my friend is still having with his.
-
If it works, I see no reason to not use it.
What does it report Vcore is now? If it is <1.3v, you can set that manually as a starting point.
I've set my Vcore manually to overclock the C2D anyway. See how fast you can go.
The bios reports that the Vcore is 0.83 and still says fail, but when I am in windows and using a hardware monitor (cpuid) program it reports the Vcore as 1.14. I tried setting the vcore in the bios to 1.2 and the PC would not post so I put it back onto auto and it works on auto. Im not sure why the bios says 0.83 and the monitor program says 1.14? I am not up to speed on the setting of voltages and I may have done it wrong. Could you talk me through the procedure to make sure I am doing it correctly? I would very much appreciate it if you would.
Thanks for your replys they have been very helpful.
I used a gigabyte board that didnt support my processor the one i used was 125watt and it only supported 95 watt that was 2 years ago now that board is in a friends computer with that 125 watt processor and still running strong. Just make sure your setting are right and hope you have the same luck my friend is still having with his.
That sounds promising I know that the board im using supports a higher watt than my CPU use's so hopefully I'll be ok. Its good to know your running an un supported CPU and have been for 2 years. It kinda puts my mind at ease a little.
-
Your Vcore will fluctuate as your CPU responds to varying loads, especially when power management features are enabled (SpeedStep, Halt, etc.).
For example, at idle, running one core at 1.6GHz, 0.83v (0.85v is the minimum but allow for tolerances) is fine. When your OS fires up, your CPU will use more cores and run at its max "turbo" speed (~2.83GHz) and will require more voltage. If it needed, say, 1.28v at load, your manual override of 1.2v won't be enough.
This is why I would leave it to [Auto] but monitor it under varying loads--especially max load with IntelBurnTest--to ensure the motherboard keeps Vcore within the E8300's specs.
-
Ok thanks I didn't know the vcore changes so 0.83 in the bios and 1.2 in windows is normal.
If I set the Vcore voltage to manual in the bios at either 1.2 or 1.3 then the PC wont start it reboots to the bios splash screen and freezes. After that I have to use the clear cmos jumper to rest the bios and get the computer to start. In the bios it says if the voltages are set to auto it may increase the voltage to overclock but if I set the voltages to manual but leave them at normal it doesn't display this warning. Would I be better to leave the voltage settings on manual and normal? Is the Vcore range the VID voltage range listed on the intel website? http://ark.intel.com/products/35070/Intel-Core2-Duo-Processor-E8300-(6M-Cache-2_83-GHz-1333-MHz-FSB) (http://ark.intel.com/products/35070/Intel-Core2-Duo-Processor-E8300-(6M-Cache-2_83-GHz-1333-MHz-FSB))
If I run the intelburn program and the board does increase the vcore to more than the CPU can handle will this damage either the board or CPU? The name is rather off putting hahaha it makes me think of my CPU catching fire because its not supported in my main board.
Sorry for all the questions and thank you for your replies they have been great.
-
I would leave it on auto it is doing just fine. One your chip isnt supported so when in bios it is probably just reported wrong. When you are in windows using cpuz it is reporting what it is really at so your all good there.
I have my old one overclocked to 3.4 from 3.0 and set on auto only thing i changed besides that is to manually set timings. Think of it this way if it is running fine leave it alone. When you decide to upgrade motherboard then get one that supports it and all will be well.
Dont overthink it or you will give yourself a headache and if it does worry you just get a new motherboard. Thats why i gave mine to a friend so i didnt have to worry about it and now 2 years later hes still happy as can be with it before that he was running a pent 4 at 2.8 now he is running a quad core amd at 3.4
-
Just leave it on [Auto].
IntelBurnTest is a must with a new CPU, clocks, cooler, anything. The purpose is to stress test the CPU to ensure it doesn't fault; it is better to find out now than later when you're in the middle of something and it freezes. If Vcore goes above spec, just hit the stop button on IBT. I think you're OK and agree with autotech in that the BIOS probably doesn't know the proper Vcore tolerances for that CPU but it seems to be reading VID OK.
-
I have never used IntelBurnTest so i cant say ant good or bad about it as i dont know zip but what i have read in the last 30 minutes. As rolo says you can hit stop at anytime id just and this is me personally keep a close eye on it when running it. Not sure about running stress test on an unsupported cpu but my other hasnt crashed during some heavy gaming by him and i mean 5 hours a night usually so never bothered to try a burn in test on it. Besides if it aint broke dont fix it and btw if it does have bad effects be prepared for the results. One being a new motherboard . two being replacing the processor if it gets drastic. Just my two cents take it for what its worth id enjoy it and not push it if you dont have to.
-
IBT has found faults that prime95 hadn't while I was building/tuning systems.
Monitor your voltage and nothing bad will happen. If IBT passes after an hour, you can be confident that you won't have any problems from the CPU running anything else.
I just wish I could find something as good as IBT for video cards; Kombustor doesn't cut it.
-
Thanks for the replies. Ok I have set the bios to auto voltages and have run the Intel burn program. I ran Intel burn at the standard settings and it did 10 repeats I think it took 10 minutes or so. The Vcore voltage did not go over 1.2 in the cpu-z program or the cpuidhardware monitor program. I also ran the coretemps program and under full load at stock speeds my CPU hit 72 degrees C. Is this a bit high? I was thinking about this and I don’t actually have the stock cooler for the E8300 I am using the stock cooler for my previous CPU a 995 Pentium extreme chip 3.4 dual core which I am thinking may not be adequate for the E8300. I have been looking at getting a Scythe Mugen cooler would this be up to the job? Would I also be able to overclock the CPU a bit with this cooler?
Since the voltage does not go over 1.2 while under full load with intel burn does that mean I should be able to continue using this E8300 chip in my board without risking damaging things? To be honest its more the board I am worried about as it is my Dads board and he wouldn’t be too impressed if I fried it as it cost him quite alot at the time.
-
As long as you follow the good advice given by Rolo42 and autotech I would say you should be fairly safe. They know what they are talking about. ;)
-
This won't fry the board; its designed for higher voltages than your CPU is and the new CPU is probably drawing less current.
1.2v is great. 72c is also great--no point in spending money on a cooler that will have zero performance impact.
The E8300's cooler is likely worse than the 955's since they're for 65W TDP and 130W, respectively.
Now, I would increase my clocks and run IBT to find how much you can overclock on those settings.
-
Excellent! Thats what I wanted to hear. I nearly bought a Q6600 because I was worried about the in compatability.
Really I thought 72c was high. What temperature is considered too high for this chip? Ah yeah I didn't think about that, the extreme 955's cooler is prob better. Thanks very much for all the information its put my mind right at ease. Now I am off to find an overclocking guide and play with the clocks to see what overclock I can get.
Thank you for all your help its very much appreciated.
-
~72c is the max case (or package) temp; max core temp is probably 100c; I wish TJmax were listed in the datasheets. If PROCHOT goes high, you've hit TJmax and your CPU will lower its frequency and input voltage to let the package and cooler catch up.
Be concerned if you go over 90c.
Ambient temp inside the PC enclosure should remain less than 38c in order for the stock cooler to dissipate heat properly.
-
Ok thanks. I clocked the chip to 3.2 last night and the temp hit 80c while running intelburn. I think the ambeint temperature in the case is a bit high, the heat pipes on my board seem to give off alot of heat and make the case temperature high. I already have all the fan spaces full though. I have a 12cm fan on the front beside the HDD rack which draws air in. I have a 12cm on the rear below the power supply blowing air out at the back and one 8cm fan on the side pannel of the case blowing air in and there aren't anymore fan spaces on the case.
Thanks for the reply
-
Sounds good!
I would think you could go higher; I have a Wolfdale that runs 3.66GHz with minimal increase in Vcore with a Zalman 9700 cooler.
-
I did have it a 3.6, Windows reported that the CPU was at 3.83 but CPUZ said it was at 3.6, but when I ran intelburn the temperature hit 88c and then the PC blue screened. So I set it to 3.2 instead and it seems fine at that. If I set the Vcore manually then the PC wont start up it freezes on the bios splash screen and I have to clear the bios using the jumper to get the PC to boot. So I dont think I will be able to raise the voltage any higher and get more from the chip.
-
What was Vcore when it wast at 3.6 at full load?
(At this point its more of an exercise unless you really need 3.6)
-
It was at vcore 1.36 according to cpu-z if I could increase this using the bios then perhaps it would make it stable at 3.8? The only trouble is the PC wont boot as soon as I adjust the voltage. Just to check when it says 1.3 in this bios this means set the vcore to 1.3 and not increase it by 1.3 doesn't it?
Thanks for the help
-
If you set Vcore to 1.36v, it should boot.
You may need to disable the power-saving features (C1E, EIST).
"1.3" is absolute, not relative (Asus boards, at least a few I had, were relative); you can tell the difference since the beginning values will be tiny.
-
I actually meant it was at vcore 1.16 at full load with intel burn not 1.36 sorry. I sent the last message from my phone and its akward to use on the phone. Sorry.
Ok thats good to know I had a fear that maybe me setting the bios to 1.3 was actually feeding it 1.3 more than what it had and not just 1.3 and thats why it didnt boot. I shall play about with the settings and see if I can get it to boot with the voltage manually set. Hmmm this overclocking is addictive, its the first time i have done it. I will have a look at the power saving settings too
Thanks again for the help
-
I would try 1.15v or 1.2v again but with power-saving features disabled.
If that works, I would try 1.3-1.36v with them enabled.
I've always has successful (no issues for the life of the component) overclocks since my first 386, so its always paid off.
-
It’s not interested at any voltage even with the power saving disabled. If I set the voltage to manual it just freezes at the bios screen and if I switch the PC off and back on then nothing happens and the screen stays off. After that the only way to get the PC to boot is by using the bios reset jumper. Weird I shall have a play with the settings and see if I can get it to boot. I have connected a spare reset switch from an old case on the bios reset pins which will make it easier to play with the settings. I had to remove one of my video cards to get to the reset pins before, which was a pain.
Wow! 386 that’s going back a few years, a 386 was one of the first PC’s I had ever seen lol. I’ll bet overclocking was harder on those? Were the frequencies settings not setup by physical switches or jumpers on the board?
-
I'm not getting any ideas on why setting it manually doesn't work at all--unless it has something to do with the Yorkshire's VID not being completely compatible with your BIOS.
Overclocking the old stuff was easier since there weren't many options. You had a few jumpers or DIP switches and that was pretty much it. I occasionally had to modify pins or motherboard connections for a few Pentiums, IIs, IIIs. The most challenging overclock I had was a Toshiba Libretto 50 palmtop. I wish I had this guide at the time! http://www.fixup.net/tips/l50.htm (http://www.fixup.net/tips/l50.htm)
-
I’m not sure why it won’t boot with a manual setting either. I can set the voltage to manual and leave it on normal and that works fine but as soon as I set a voltage it just won’t boot. You’re probably right and it’s something to do with the incompatibility between the board and my chip. Im not complaining though! It means I can use the E8300 which is a vast improvement over the 955 extreme chip and I can run a slight overclock on the E8300. Hopefully this will keep me going until I can afford a newer board and chip.
I always thought overclocking was a risky operation and that if done incorrectly it would break the PC so I have never attempted to overclock until now.
-
I always thought overclocking was a risky operation and that if done incorrectly it would break the PC
That's true but only if you don't bother to do a little research and put some thought into it.
-
Yeah as long as you dont go too far its ok. I think now I shall try and overclock every PC I have.
I think 3.4 is going to be the max I am going to get from the E8300 since I can't adjust the voltages manually and 3.6 makes it bluescreen while running intel burn. I wonder if using the last full realese of the bios might help? The version I have is a beta and might be the reason I cant adjust the Vcore. Just now the Vcore seems to stay constant at 1.14 I think if I could increase that then I might be able to push the chip higher.