e6300 no longer overclocks

darrellc

n00b
Joined
Feb 26, 2008
Messages
4
Since this is my first post I'll give a little history of my comp before telling you my problem.

I built my computer around the first month of 2007 with a e6300 on a gigabyte ds3 and a g-skill 6400. I had my system overclocked to above 3.2ghz and then about april pushed it up to 4ghz
M2 Information - Version 2.11
M Squared Technologies (C) 2001 - 2003
------------------------------------------------------
Date and Time : Sun Apr 01 14:12:35 2007
Architecture : Genuine Intel
Number of CPUs : 2
CPU Type : x86 Family 6 Model 15 Stepping 2
MMX Feature : Present
CPU Speed : 4081.62 (8163.24) Mhz
Operating System: Microsoft Windows XP
Version : 5.1 Service Pack 2
All of this was running on a HSF, so I decided to lower the high idle temps with a water cooling unit. It took a while to find and receive the cooling unit I wanted so I just gave my computer a 2 month hiatus. After that I rebooted it with the new water cooling unit and even upgraded the video card from a X1650 to a Radeon HD 3870(single core).

This is where my problem begins...

I had 3.2ghz running stable when I installed COD4 over the weekend to test out the new rig. On Monday I restarted my computer. After which my bios settings were resetted. I set them back give me 3.2ghz. The comp would then restart to bios, and in the middle of showing the post screen would restart again to default settings. Since then, I've been playing with it, even changing the fsb to 270 only to have it revert back. Not even the smallest change to the fsb will stick. I even reinstalled Easy Tune 5 and made fine tuned adjustments. With Easy Tune I a little more luck changing the fsb to 290 but anything above that crashes my comp.

Would anyone know what's going on?
(ps - sorry for the long post)
 
Which DS3 are you speaking of? The P35 or 965? Do you have another processor to test it with?
 
I'm using the 965. And unfortuneately I don't have any other processors on me to test with.
 
I've pushed it a little over 1.4v just playing around with it. But the highest I've run the cpu for more than a couple of minutes was 1.37
 
i had this board for almost a year, cheap piece of cr*p, but stable as hell

maybe a BIOS problem?
 
I've been able to overclock it before with the original bios with no problem, but just in case that was the problem I flashed the bios tuesday and i still get the same problem.
 
I've pushed it a little over 1.4v just playing around with it. But the highest I've run the CPU for more than a couple of minutes was 1.37

That blows my theory, tons of those chips run at that voltage or higher without any issues. Mine has been at 1.375 for 17 months and I have played with it up to 1.45 on occasion for an hour or so.

My only suggestion is to look very hard at what was changed between "it was fine" and "now it wont". It would, logically, have to be something you changed. According to your post you changed.

1) Air cooling to water cooling,
2) upgraded the video card from a X1650 to a Radeon HD 3870(single core)
3) Installed COD4

IMO.
3) COD4 has nothing to do with boot so save that for absolute last resort, I can think of no way that should affect your boot/post/bios but God works in strange ways so cannot completely eliminate it, but its the very last thing to look at.

2) this is easy, put the old video card back in and see if the issue is still there. I give this a fair chance of being the issue. This is a PCI-e 2.0 board and while that is supposed to be backward compatible with the PCI-e 1.0, there are a very few reports of boards not liking the new cards. I cannot recall the Gigabytes having the issue but then, what the hell do I know. :D

1) This is hard, you do not want to reinstall the air cooler, but triple double damn check every little thing with the water block mounting, is the block seated properly, did any other heatsinks get knocked/bumped when installing the block, you eliminated the airflow around the CPU voltage regulation circuity with the removal of any HS/Fan air cooling, did you compensate with an auxiliary fan blow air on the components around the CPU socket ?. Did a drop of water escape and maybe be sitting on the board, it would evaporate but could have left a conductive trail of deposits between two contacts (a rare possibility but we are just speculating and if the issue was easy to find you would have already found it). Could the WC pump be pulling just enough power to cause your power supply to be marginal ? etc. etc. etc. Go over it all with a microscope, slowly, looking for anything out of the ordinary. With that block full of water sitting on the cpu it would not kill/hurt it to boot the machine without the pump running for a couple of minutes. (do NOT do this with anything but a C2D.)

The alternative is that you have done something to make Baby Jesus cry and are doomed to computer hell forever.
 
Back
Top