View Full Version : XFX 680i Random Reboot Insanity
Okay, this is driving me crazy. I think I've been hexed. My XFX 680i randomly reboots whenever it feels like it. Sometimes it's minutes before a reboot, sometimes it's hours.
A little history is in order. I built this rig in mid-October. Then, just before Thanksgiving, my RAM went bad - OCZ SLI-Ready 2GB (2 x 1GB) DDR2 SDRAM DDR2 1066 (PC2 8500) - OCZ2N1066SR2GK. Got an RMA, then waited, machine down, no joy.
Got RAM back, rig worked for a couple of weeks, then mobo malfunctioned on Dec. 13th. Probably a bad voltage regulator. Got an RMA from XFX. Sent bad mobo in on Dec. 26th. Waited again, machine down. No joy.
Got RMA'd mobo back three weeks later. New mobo, not refurb, much joy. New mobo didn't like DDR2 1066 RAM settings so I set RAM manually to DDR2 800 and lowered the voltage. Smooth sailing at an overclock of 3.6GHz. A couple of weeks later, random reboots started to occassionally happen with this new mobo.
When I received the new mobo, I did not install a fresh OS install at first. I used a ghosted image from 10 days prior to the first mobo going bad. Thinking that I needed a fresh OS install, I did just that on Feb. 10th. It was an all day affair.
Things looked good. Actually, everything was going great. I brought my system back up to spec as far as applications and data was concerned. Then, random reboots right in front of my eyes. I couldn't believe it.
I had ghosted the image four times during the install process:
1. New XP Pro SP2 install - basic drivers - no Windows Updates.
2. Added Windows Updates
3. Installed Applications (Acrobat, Office, AVG Anti-Virus, etc.)
4. Added personal data & installed Company of Heroes
I used these images to re-ghost and go back to a previous point in time. Same thing, random reboots. It was very late so I gave up for the night and crashed. When I awoke the next morning, my rig was throwing a hissy fit. Within an hour, determined that my RAM had gone bad again. One stick would not boot at all. The only thing it would do for me was to give me one long beep.
OCZ gave me an RMA by the end of the day and I ordered temporary replacement RAM form Newegg - G.SKILL 2GB (2 x 1GB) 240-Pin DDR2 SDRAM DDR2 800 (PC2 6400) - F2-6400CL5D-2GBNQ.
While waiting for the repalcement RAM to arrive, I used one stick (1GB) of the OCZ RAM and went back to a stock clock of 2.66GHz on my CPU. It worked, but life ain't pretty with only 1 gig. No random reboots and I thought that maybe bad RAM had been my issue. So, I was eager to get some new RAM and be at peace with the world.
My replacement RAM arrived and I thought that all my problems had been solved. I ran my rig at stock clock for a day and was happy enough. Then, I tried to overclock the beastie and the random reboots re-appeared. It seems as though I'm not alone with this issue:
http://news.softpedia.com/news/Nvidia-Still-Has-Some-Problems-with-680i-42944.shtml
Am I doomed? Is there no hope for me? This shouldn't be happening.
At this point in time, I have no faith in my XFX 680i mobo other than the fact that I know it will randomly reboot itself.
And yes, I do have the P32 BIOS installed and all drivers are current.
scaven92
02-21-2008, 06:35 AM
Wish I could offer some advice but you sure have bad luck with hardware. If there is anything I've learned as being an electrical engineer its that seldom does so many parts continue to fail without something else being the route cause.
Hope the problem is fixed soon by someone more experienced.
srpeters18
02-21-2008, 06:42 AM
If you can rule out a failing PSU (yours definitely has enough power, but maybe its bad?) it sounds like a voltage issue for your overclock. If you think voltage is good enough, try a lower overclock to see if maybe you're running into FSB "holes". I was getting the same reboots on my 780i at 3.6GHz but it's solid at 3.5.
If you can rule out a failing PSU (yours definitely has enough power, but maybe its bad?) it sounds like a voltage issue for your overclock. If you think voltage is good enough, try a lower overclock to see if maybe you're running into FSB "holes". I was getting the same reboots on my 780i at 3.6GHz but it's solid at 3.5.
I'm pretty sure that the PSU is fine though I have yet to put the multimeter on it. I'd be pretty darned amazed if it was the culprit. And I've looked into that whole FSB "hole" thing. Apparently, I'm in the "safe" zone, just below the FSB hole for my CPU and mobo combo. I tried lowering the FSB for a day already to 1280 for an overclock of 3.2GHz but that produced the same results, random reboots.
I've also tried all different manner of voltages on the FSB, SPP, MCP, etc. Right now I'm running the MCP "hot" at 1.6v. We'll see what happens. I'm expecting a random reboot any time now. And that's the frustrating part. Knowing it can happen at any time; no matter what I'm doing.
The first board, the one that died and got RMA'd, never did the random reboot thing. Before it and the RAM died, I was doing a 3.66GHz overclock and the OCZ RAM was zinging along at 1066MHz. This new mobo never did like having the RAM set that high and I ran my DDR2 1066 at 800MHz and at a much lower voltage but it died too.
Two bad sets of RAM, a bad motherboard, maybe two, and random reboots. What next? I get hit by a bus?
srpeters18
02-21-2008, 07:32 AM
Try dropping your multiplier on the CPU, then you can see if your FSB is stable or not. If it still reboots randomly I'd suspect the mobo, or at least the FSB speed at that point.
:keepfolding:Try dropping your multiplier on the CPU, then you can see if your FSB is stable or not. If it still reboots randomly I'd suspect the mobo, or at least the FSB speed at that point.
Dropping the multiplier is on the list but I'm more inclined to think it's an MCP issue so I'm following that trail right now using the upped voltage. I think that it is, without doubt, a motherboard issue. I don't think that software is involved at all because I've tried four different images of installations at various points at both 3.2GHz & 3.6GHz. I've also tried tried running this thing bare-boned at those various stages with no applications running; anti-virus off, no folding, etc.
As it stands right now though, I have been running stable for 10+ hours with the upped MCP voltage @ 3.6GHz; folding @ home, playing games, watching HD on ABC & FOX.
I'd like to get this all ironed out as I'm tired of this crap. I'm getting in a 400GB Seagate drive tomorrow to use as a D: drive and I'd like to add a third 320GB to two 320's that I already have and change the raid array around a bit. But I really would like to have a stable platform before I do that.
srpeters18
02-21-2008, 08:11 AM
Wow, I'm surprised the MCP is taking that much voltage. What are you using to cool it? Hopefully it'll keep running stable for you.
Miker
02-21-2008, 08:15 AM
If it runs at stock ok, yet restarts with OC it means it can't handle the OC. It is that simple.
Wow, I'm surprised the MCP is taking that much voltage. What are you using to cool it? Hopefully it'll keep running stable for you.
Not doing anything special yet though I'm thinking about removing that damned heatpipe on the northbridge/southbridge and replacing the TIM. I just got a big ol' tube of Arctic Silver 5 last week.
If it runs at stock ok, yet restarts with OC it means it can't handle the OC. It is that simple.
Miker,
You hit the nail on the head. It runs stock okay but the OC is unstable. And that's just not the way it's supposed to be. This particular mobo has issues. With watercooling, I should have no problems at all running this thing at 3.6GHz. Hell, the whole world is running this CPU/mobo combo at that on air!
Miker
02-21-2008, 08:32 AM
Everything OCs different, just because 10 other people got over 3.6 doesn't mean you will.
Everything OCs different, just because 10 other people got over 3.6 doesn't mean you will.
Ten people do not the world make. But I understand your point. However, I'm a brat and I want my overclock!
After 28 hours this thing finally rebooted itself using it's own random reboot generating algorithm with the following settings:
CPU Core Speed: 3600.0 MHz
Multiplier: 10X
Bus Speed: 360.0 MHz
FSB: 1440.00 (QDR) MHz
SPP: PCI-E 2500 MHz
MCP: PCI-E 2500MHz
GPU Core: (3D) 576 MHz
GPU Memory: 900 MHz
Memory Frequency: 400 MHz
FSB : DRAM Ratio: 9:10
CAS # Latency (tLC): 5.0 clocks
RAS# to CAS# Delay (tRCD): 5 clocks
RAS# Precharge (tRP): 5 clocks
Cycle Time (tRAS): 15 clocks
Bank Cycle Time (tRC): 20 clocks
Command Rate (CR): 2 T
CPU: 1.5000v
Memory: 1.8500v
FSB: 1.5000v
HT (SPP-MCP):1.5000v
PCI-E: 1.5000v
nForce: 1.6000v
AUX: 1.6000vAfter it rebooted itself I went into the BIOS and reduced the FSB to 1200MHz, giving me an overclock of 3.0GHz. While 3.0GHz is not a satisfactory overclock at all, it will suffice for testing purposes. I fully expect this thing to reboot itself given enough time. If I go much lower, I will be at stock speed and I did not buy this particular motherboard to accomplish that task.
Okay,
So I took a little side trip for a couple of days and went off the 3.0GHz plan. I cleared my CMOS and then I broke my mirrored raid array and set it up as a striped array and added a Seagate 400GB as a D: drive for a total of four drives. The fourth is a Western Digital 250GB eSata formatted with FAT32 to house my ghosted images.
I used a ghost image for the new array made just prior. I made the image and did the re-imaging at stock clock of 2.66GHz. Then, I overclocked. Same random reboots at both 3.6GHz & 3.2GHz. I tried all manner of voltages and FSB/Multiplier combinations.
Temps look good all across the board. I put the power supply to the tester and all the rails look good.
Yet, this machine still randomly reboots itself. The funny this that it has never rebooted itself while playng a game. Hell, I even stress test with Orthos, play .mp3's, run HD TV on FOX, and transfer large files while gaming and not so much as even a hiccup.
Perplexed though I may be, I am continuing to test this thing. It's set at 3.0GHz now using a FSB of 1200MHz and a 10X Multiplier. I'm not a happy puppy. :frown:
I have been experiencing the same problem 2 months, except I have never Overclocked any of the components. I think the mobo doesn't like my DDR2 RAM (CAS 3 @ 2.3V). Whenever I run 2 sticks it would lock-up every few hours, yet yesterday it refused to boot, so I got my old stick of RAM (which I thought was causing the problem a month before) put it in, ran memory test passed 0 errors. I've been running 1stick of RAM for about 35 hours now, not a single lockup. I've tested all sticks separately, and they seem fine, passing memory tests.
You've mentioned you've RMA'd your RAM, did they test it and confirmed as bad RAM? I ask because I suspect the 680i doesn't like fast or higher voltage RAM. Try your overclock with 1 stick of RAM see if you can run it 120 Hours or so without lockups/restarts.
SensNation
02-24-2008, 01:02 PM
I was reading a post on another site, by someone who had the same problem as you with the same board but with running a Q6600. He said after he changed the voltage setting for his Ram to 2.1 and the random reboot problems went away.
I have been experiencing the same problem 2 months, except I have never Overclocked any of the components. I think the mobo doesn't like my DDR2 RAM (CAS 3 @ 2.3V). Whenever I run 2 sticks it would lock-up every few hours, yet yesterday it refused to boot, so I got my old stick of RAM (which I thought was causing the problem a month before) put it in, ran memory test passed 0 errors. I've been running 1stick of RAM for about 35 hours now, not a single lockup. I've tested all sticks separately, and they seem fine, passing memory tests.
You've mentioned you've RMA'd your RAM, did they test it and confirmed as bad RAM? I ask because I suspect the 680i doesn't like fast or higher voltage RAM. Try your overclock with 1 stick of RAM see if you can run it 120 Hours or so without lockups/restarts.
I'm pretty sure that either my mobo doesn't like OCZ DDR2 1066 SLI-Ready RAM or that the RAM doesn't like me after having two kits go belly up on me. It will be interesting to see what happens when I get my third kit back from RMA.
I didn't try it on an overclock but I did run one stick of RAM for four days while waiting for my temporary RAM to come in. At a stock clock with only 1GB of RAM it never rebooted on me.
I was reading a post on another site, by someone who had the same problem as you with the same board but with running a Q6600. He said after he changed the voltage setting for his Ram to 2.1 and the random reboot problems went away.
I've also read that random reboots exist on that Quad core. The second set of OCZ DDR2 1066 never liked to run at 1066MHz on this motherboard (2nd mobo after first one croaked) so I ran it at 800Mhz with a voltage of 2.1v. I got random reboots until that kit died. The voltage on the G.Skil DDR2 800 kit that I have now is rated between 1.8v and 2.0v. I'm running it at 1.9v right now.
Miker
02-24-2008, 10:38 PM
There is really no point in complaining a PC won't OC. You are pushing the hardware past its limit. Some push farther then others. There is nothing wrong at all even if you can only OC is just 1%.
There is really no point in complaining a PC won't OC.
That's your opinion. I am not quite so docile.
You are pushing the hardware past its limit.
Yes, technically speaking, I am pushing the hardware past it's limit or rather it's rated specifications. I was under the impression that that is what overclocking is all about.
Some push farther then others.
True that is.
There is nothing wrong at all even if you can only OC is just 1%.
Once again, that's your opinion. But IMHO it's pretty extreme. A 1% overclock is acceptable to you? Really? Why not just say 0.5%? Is that acceptable? It's not acceptable to me. Nuh uh. And neither is a 1% overclock.
Miker
02-25-2008, 01:45 AM
0% OC is acceptable. There is nothing wrong if you can't OC your components.
There is nothing you can do, your PC will not run at 3.6GHz. There is no way to change that with out getting a new CPU, or MoBo. Doesn't even have to be a different type, but the same type and hope you get lucky and it OCs better.
Scott
02-25-2008, 01:54 AM
And all of this sounds like a bad power supply to me.
Miker
02-25-2008, 01:55 AM
And all of this sounds like a bad power supply to me.
That is a good one, it does seem that every problem he had was power related.
0% OC is acceptable.
You are most forgiving. However, I am not.
There is nothing wrong if you can't OC your components.
Should I add this as Rule #1 in The Overclocker's Handbook? :wink:
There is nothing you can do, your PC will not run at 3.6GHz.
Say it isn't so! Don't say there's nothing I can do. Surely there must be something that I can do. While your omniscience is impressive, I am not so enlightened and therefore not want to do nothing. And though you've determined that my PC will not run at 3.6GHz, I am not so convinced, thus the testing. I'll run it at 3.0GHz until the RMA'd RAM returns or the beastie reboots itself.
There is no way to change that with out getting a new CPU, or MoBo. Doesn't even have to be a different type, but the same type and hope you get lucky and it OCs better.
I think that you're coming around to my point of view in a round about sort of way. My hypothosis is this,
"There's Something Very Wrong Going On Around Here!"
I did get a new motherboard for this CPU when the first one went south. It was a brand spanking new XFX 680i replacement for an RMA. I didn't get lucky (thanks for the sentiment though) and this one doesn't seem to overclock as well. It likes to randomly reboot itself when overclocked to 3.2GHz or 3.6GHz. I'd like to know why.
Since I didn't "get lucky", could it be something as simple as a faulty reset switch on the motherboard?
Or could it be something else intirely?
And all of this sounds like a bad power supply to me.
That is a good one, it does seem that every problem he had was power related.
I put the power supply on the PSU tester and then checked it with the multimeter under load.
I've checked and rechecked all plugs, cables, and wiring, looking for a shorts and making sure that connectons are secure.
My case has no reset switch.
cvasquez
02-25-2008, 10:05 PM
When I set up my computer first rule of thumb don't overclock right away.
2nd rule of thumb image your computer when it's all nice and fresh with most of necessary programs already loaded.
When I set up my computer first rule of thumb don't overclock right away.
2nd rule of thumb image your computer when it's all nice and fresh with most of necessary programs already loaded.
Excellent advice. That's pretty much my modis operandi.
When my temp G.Skil DDR2 800 RAM came in to take the place of my RMA'd OCZ DDR2 1066, I ran this beastie at stock clock for 24hrs.+ with nary a twitter.
And I always image my computer during the install at various stages. That's how I'm able to go back to an earlier point in time and rule out software/application incompatibilities. Still, it reboots.
My Basic Windows XP Pro install (always performed at stock clock) includes SP2 and drivers:
nVidia 9.53_nforce_680i_winxp_english_whql.exe Drivers for mobo installed
Realtek High Definition Audio Driver WDM_R184 for onboard audio installed
nVidia 169.21_forceware_winxp_32bit_english_whql.exe Drivers for video card installed
Cleartype installed
I have tried this Basic install at both 3.6GHZ & 3.2GHz and have gotten the random reboots. Also, during various testing phases, I have installed various flavors of the drivers above, even going so far as to strip out the Realtek and Cleartype drivers leaving just the mobo & video card drivers intact.
With a stripped down install like the one mentioned above providing me with my random reboot entertainment when overclocked, I'm fairly convinced that it's not a software issue. Could it be a driver issue? Possibly, but not very likely. Could it be a hardware issue? Maybe, probably more than just a bit likely. Could it be an issue related to the motherboard itself? Ah, now there's an idea. Is it motherboard related? Sadly, I'm begining to believe that's the case.
But still, I'll continue to monitor the situation at 3.0GHz until the OCZ DDR2 1066 RAM comes in and who knows, maybe I'll get lucky and this new RAM will magically make all my woes disappear. I mean, afterall, third times a charm, right? Though I'm hopeful for success with my third kit from OCZ, if this board (nVidia reference design) eats this set of OCZ SLI-Ready RAM, I may put it up for sale after I get it RMA'd from OCZ.
Okay,
So the FedEx guy delivered my RMA'd RAM today. I'll see if I have better luck with this set. It's my third kit of:
OCZ SLI-Ready 2GB (2 x 1GB) SDRAM DDR2 1066 (PC2 8500) - OCZ2N1066SR2GK
If this kit goes bad then either this particular RAM model is bad or I'm terribly unlucky or this motherboard (nVidia reference design ) truly does like to eat RAM (or maybe it just likes to eat this particular model of RAM).
The testing at 3.0GHz produced no random reboots.
C:\>systeminfo | find "Up Time"
System Up Time: 6 Days, 5 Hours, 27 Minutes, 38 Seconds
The following settings were used for the 3.0GHz testing:
CPU: Inel Core 2 Duo E6700
CPU Core Speed: 3000.0 MHz
Multiplier: 10X
Bus Speed: 300.0 MHz
FSB: 1200.00 (QDR) MHz
SPP: PCI-E 2750 MHz
MCP: PCI-E 2750MHz
GPU Core: (3D) 576 MHz
GPU Memory: 900 MHz
Memory: G.SKILL 2GB (2 x 1GB) DDR2 800 (PC2 6400)
Memory Model: F2-6400CL5-1GBNQ
Frequency: 400 MHz
FSB : DRAM Ratio: 3:4
CAS # Latency (tLC): 5.0 clocks
RAS# to CAS# Delay (tRCD): 5 clocks
RAS# Precharge (tRP): 5 clocks
Cycle Time (tRAS): 15 clocks
Bank Cycle Time (tRC): 20 clocks
Command Rate (CR): 2 T
CPU: 1.4000v
Memory: 1.9000v
FSB: 1.4000v
HT (SPP-MCP):1.2000v
PCI-E: 1.4000v
nForce: 1.5000v
AUX: 1.5000v
CPU-Z Ver. 1.44.1 Core Voltage: 1.352VI'll start testing with the above settings using the OCZ RAM, gradually increasing the overclock, and see what happens. Hopefully, the random reboots that have plagued me will be a thing of the past.
Miker
03-01-2008, 03:11 AM
You are pushing your system way over what it is designed too, things can fail.
You are pushing your system way over what it is designed too, things can fail.
Miker,
Your prophecies of doom are unheard by this infidel.
Perhaps you missed this somewhere along the way but this particular motherboard is designed for overclocking.
nVidia nForce 680i SLI Overclocking Guide (http://www.nvidia.com/docs/CP/45121/nforce_680i_sli_overclocking.pdf)
Though there are no gauranteed results when overclocking, there are minimal results using certain mobo/CPU combinations that are acknowledged by the overclocking community. It is not unexpected to achieve 3.2GHz or even 3.6GHz using this setup. Color me an optimist. Though things can fail, I would hate to think that my second XFX 680i mobo is faulty.
So, with that said, I will continue on my overclocking quest to achieve the highest overclock possible with the maximum amount of stability. For me, stability is key and is valued more than speed, but I do prefer to have both.
werty316
03-01-2008, 04:45 AM
If you get any system instabilities try setting the memory voltage to 2.0V or 2.1V.
Miker
03-01-2008, 04:46 AM
There is nothing wrong with your MoBo if it works ok at stock speeds. Only reason I am arguing with you is because you seem to think something is wrong with your Mobo, while, at stock speeds it is perfect.
If you get any system instabilities try setting the memory voltage to 2.0V or 2.1V.
Thanks Werty.
I've got the RAM throttled back for now; only running it at 400MHz; same as the 2nd set that was RMA'd.
Memory: OCZ SLI-Ready 2GB (2 x 1GB) SDRAM DDR2 1066 (PC2 8500)
Memory Model: OCZ2N1066SR2GK
Memory Voltage: 2.1000v
Frequency: 400 MHz
CAS # Latency (tLC): 5.0 clocks
RAS# to CAS# Delay (tRCD): 5 clocks
RAS# Precharge (tRP): 5 clocks
Cycle Time (tRAS): 15 clocks
Bank Cycle Time (tRC): 22 clocks
Command Rate (CR): 2 T
There is nothing wrong with your MoBo if it works ok at stock speeds. Only reason I am arguing with you is because you seem to think something is wrong with your Mobo, while, at stock speeds it is perfect.
Once again I'd like to point out that this motherboard was designed for overclocking. If this particular mother board doesn't overclock paticularly well, then there very well may be something faulty with this particular motherboard. It's either that or that I may very well be cursed. Perish the thought. Keep in mind though that I have had before a faulty motherboard of this model motherboard as verified by XFX and their RMA process.
And Miker, I don't think you need any reason at all to argue with anybody. :wink:
Miker
03-01-2008, 05:54 AM
And Miker, I don't think you need any reason at all to argue with anybody. :wink:
Aw, that was sweet. Thanks.
But as you said before, there is no guarantee the board will OC. Well I wish you luck with your OC, even if it takes 12 RMAed Mobos.
C:\>systeminfo | find "Up Time"
System Up Time: 2 Days, 0 Hours, 33 Minutes, 29 Seconds
Well I wish you luck with your OC...
Thanks for the sentiment, Miker. Look! Two days up with no glitches or random reboots. You may be my lucky charm. Orthos has been running 13+ hrs. now while folding both CPUs. I hope that this beastie remains stable.
The following settings are being used for the 3.6GHz testing:
CPU: Inel Core 2 Duo E6700
CPU Core Speed: 3600.0 MHz
Multiplier: 10X
Bus Speed: 360.0 MHz
FSB: 1440.00 (QDR) MHz
SPP: PCI-E 2750 MHz
MCP: PCI-E 2750MHz
GPU Core: (3D) 576 MHz
GPU Memory: 900 MHz
Memory: OCZ SLI-Ready 2GB (2 x 1GB) SDRAM DDR2 1066 (PC2 8500)
Memory Model: OCZ2N1066SR2GK
Frequency: 400 MHz
FSB : DRAM Ratio: 9:10
CAS # Latency (tLC): 5.0 clocks
RAS# to CAS# Delay (tRCD): 5 clocks
RAS# Precharge (tRP): 5 clocks
Cycle Time (tRAS): 15 clocks
Bank Cycle Time (tRC): 22 clocks
Command Rate (CR): 2 T
CPU: 1.4500v
Memory: 2.1000v
FSB: 1.5000v
HT (SPP-MCP):1.2000v
PCI-E: 1.5000v
nForce: 1.5000v
AUX: 1.5000v
CPU-Z Ver. 1.44.1 Core Voltage: 1.392V
One week has past since I put the new RAM in and started my overclock testing at 3.6GHz. I've had no random reboots in that rime. I've rebooted the thing myself a couple of times to get into the BIOS and make adjustments; tweaking the CPU voltage a bit.
As it is, I am a lot happier now than I was before. Hopefully, good fortune will continue to smile upon me. :smile:
I'm going to continue testing for another week before I start tweaking the memory. I want to make sure that I have a rock solid platform first as stability is key. Though I am not about to draw any conclusions just yet, I am leaning a certain direction as to the cause of the random reboots. What is that, you say? Stay tuned.
Miker
03-08-2008, 07:12 AM
Tough I am not about to draw any conclusions just yet, I am leaning a certain direction as to the cause of the random reboots. What is that, you say? Stay tuned.
It being OCed? :lol:
I like to think I am a lucky person. :grin: I am thinking you can get to 1T on the RAM, and some descent timings. How many volts over normal is the CPU?
It being OCed? :lol:
Funny guy, Miker. Funny guy. However, giving props to you, you are correct, in a manner of speaking. If this beastie wasn't overclocked, the random reboot issue would probably be a non-issue.
I like to think I am a lucky person. :grin: I am thinking you can get to 1T on the RAM, and some descent timings. How many volts over normal is the CPU?
You may be right. That second set of OCZ SLI-Ready DDR2 1066 RAM ran just fine for weeks at 800MHz with 2.1v - 4-4-4-12-16-1T until it crapped out. It didn't particularly like being run at 10066MHz so I went the other direction. We'll see what happens with this third kit.
As for the CPU voltage - I'm running that at 1.46250V and CPU-Z shows it at 1.400V. Unfortunately, I goofed on the Orthos test last week and only noticed that I was running just a RAM stress test and not a stress test of the RAM & CPU after I had posted. Still, it did stress the RAM for over thirteen hours. But I have yet to complete a lengthy testing of the CPU mainly because I am forgetful in nature. I will get it done and hopefully I will find the sweet spot for this CPU. Orthos stability guaranteed or not, I haven't experienced any issues so far.
So far, everything has been stable for a while now. No random reboots.
Orthos has been running a blend stress test of the CPU and RAM for 61+ hrs. I'm fairly confident that it could continue longer, but it's eating up 1.17GB RAM and I'm ready to stop it to free up those resources.
I had to up the voltage a bit on the CPU to get it to this point. CPU voltage is now at 1.4750V and in CPU-z it shows up as 1.416V.
If this beatie remains stable, I will start tweaking the RAM this weekend.
Methious
03-12-2008, 05:47 PM
That the 24/7 OC your planning on running? You must like RMAing components.
Miker
03-12-2008, 07:50 PM
That the 24/7 OC your planning on running? You must like RMAing components.
He really does like RMAing stuff, I think he would be happier if he could get it even higher too. He will learn once he fries his whole PC.
That the 24/7 OC your planning on running? You must like RMAing components.
:keepfolding:
Yes, it is. 3.6GHz OC 24/7. CPU temps are cool enough.
And no, I don't. RMA's are expensive and time consuming. Plus, I don't like being w/o the parts. Until this most recent spate of problems, the most I've ever RMA'd in 15+ yrs. was a couple of hard drives and a mouse.
He really does like RMAing stuff, I think he would be happier if he could get it even higher too. He will learn once he fries his whole PC.
Sometimes you're spot on and sometimes you're off by a mile, Miker. I would be happier with a higher overclock, but I'm not going to push it for a while.
I've been overclocking since the Celeron 300MHz days and have never fried anything though I did have a NIC catch on fire one time right before my eyes. That was about a week after a lightning strike took out five components in my roommate's PC. I guess that the spike weakened something on that card and it didn't show up right away. Fortunately, I was home at the time it caught fire.
What's funny about the whole affair is that I was playing one of the Jane's Combat Sims and just got hit by a missle. I smelt electronics burning and just for a split second I was thinking, "Man, this is too real!"
Check six.
Miker
03-12-2008, 10:49 PM
I've been overclocking since the Celeron 300MHz days and have never fried anything though I did have a NIC catch on fire one time right before my eyes. That was about a week after a lightning strike took out five components in my roommate's PC. I guess that the spike weakened something on that card and it didn't show up right away. Fortunately, I was home at the time it caught fire.[/I]"
I had a PSU go up in sparks, it had blue glass on the side so it looked really cool.
I had a PSU go up in sparks, it had blue glass on the side so it looked really cool.
I think I almost bought that PSU, but I went for something much cheesier. :grin:
Anyways, it's been a full two weeks now since installing this 3rd kit of OCZ SLI-Ready DDR2 1066 RAM and there has not been one single random reboot the entire time.
As to what conclusion I can draw, as far as I'm concerned, the random reboots were probably due to faulty, or less-than-stellar, RAM. I believe that the faulty 2nd kit of OCZ that was RMA'd played a part in the random reboots as did the less-than-stellar G.Skill RAM. Of course, this is all conjecture but it makes the most sense to me. It's just odd though that a bad RAM kit and a supposedly good RAM kit would produce the same results. But stranger things have happened.
In all probability though, the motherboard itself had very little to do with it unless it's just finicky as to what RAM it has in it at any particular time. At the moment, it appears to like this RAM very much or at the very least it likes the current settings. I'm going to start tweaking those RAM setting a bit and see what I can come up with. If I'm lucky, all hell won't break loose.
This CPU/mobo combination seems very happy running at 3.6GHz, as I hoped it would be. Now that I have a stable overclocked baseline to work with, I'll see if I can squeeze anything more out of it. I reckon a little more won't hurt but I'll probably have to get an E8400 if I want to see 4.0GHz or above.
CPU: Inel Core 2 Duo E6700
CPU Core Speed: 3600.0 MHz
Multiplier: 10X
Bus Speed: 360.0 MHz
FSB: 1440.00 (QDR) MHz
SPP: PCI-E 2750 MHz
MCP: PCI-E 2750MHz
GPU Core: (3D) 576 MHz
GPU Memory: 900 MHz
Memory: OCZ SLI-Ready 2GB (2 x 1GB) SDRAM DDR2 1066 (PC2 8500)
Memory Model: OCZ2N1066SR2GK
Frequency: 400 MHz
FSB : DRAM Ratio: 9:10
CAS # Latency (tLC): 5.0 clocks
RAS# to CAS# Delay (tRCD): 5 clocks
RAS# Precharge (tRP): 5 clocks
Cycle Time (tRAS): 15 clocks
Bank Cycle Time (tRC): 22 clocks
Command Rate (CR): 2 T
CPU: 1.4750v
Memory: 2.1000v
FSB: 1.5000v
HT (SPP-MCP):1.2000v
PCI-E: 1.5000v
nForce: 1.5000v
AUX: 1.5000v
CPU-Z Ver. 1.44.1 Core Voltage: 1.416V
compunerd22
10-28-2008, 02:51 AM
To anyone who might have reboot issues on a 680i SLI board, I resolved this issue by running nvidia graphics drivers 3 versions old. As of the time of this post, current drivers are 178.24. I can only play games on 175.19. Any other driver version and I reboot randomly. On the latest drivers, its pretty much insta-reboot. On the previous version I can go 5 - 45 minutes until reboot. On 175.19 I'm stable for the long haul.
I found this out after RMA on the boardx2, RMA memoryx1 and complete replacement of memory with a new brand, and finally, a new power supply. I also tried every voltage combo that I thought wouldn't fry my parts. For all I know, everything was good the entire time - who knows.
Hope this helps.
vBulletin® v3.7.0 Release Candidate 3, Copyright ©2000-2009, Jelsoft Enterprises Ltd.