corsair hydrocool 200ex water with 1/4" tubing hehQuote:
Originally Posted by jc2mm2
Printable View
corsair hydrocool 200ex water with 1/4" tubing hehQuote:
Originally Posted by jc2mm2
Ran Burn x2 all night then ran prime (small FFt) x2 for 12hrs np htt265 Vcore 1.42 Cpux10 mem full Auto temp 54-52C
At htt270 (rest as above) failed prime both cores in about 1min or less lasted 2mins 42secs on one core tonight but got BSOD with burnx2 within 15 mins both nights but lasted longer tonight
If I have the mem set on anything but auto(all) it will boot but BSOD b4 getting into windows at 2650 or 2700
Just increased the Vcore1.5V to see if that helps
ahhhh :D So if you think I'll do air cooling, what would be my max oc?:D any ideas?:D thanks for the help :D
Yeah that seems to be the exact same as me but I'm 290x9 (165opty) but it aint prime stable. Any more than 295x9 and I get the bsod+reboot. Dosn't matter whether I set memory to cas2 or 3 or 1t or 2t. Tried increasing vcore to 1.5 to no avail.Quote:
Originally Posted by Zeus...
Runs 3dmark05 and pc mark fine tho.
Currently burning in with cpuburnK7 ;) at 2520 to see if that helps.
Set mem all to auto (except Volts) and try that
Nah, posts fine then as soon as windows starts loading ...BSOD/reboot. I'm sure it aint temps either. At high FSB (270+) the mobo auto lowers the memory to 154.3 mhz(according to cpu-z) does that sound right?
Running Corsair 3500LL 2-3-2-6
Burning ATM @270HTT 1.5V CPUx10 mem at auto and CPU-Z says the mem is at 180MHz 2 2 2 5 14 16
Opteron 175
CCBWE 0536XPMW
Well, I'm kinda disappointed in this chip... If it was a 170, it would be fine, but not a 175.
I can get 2.6Ghz Dual Prime Stable at 1.5V and 48*C
Can't get 2.65Ghz at 1.5V though.
This is on a TT BT lapped with AS5 and a 78CFM 120mm fan (thermaltake case fan).
As I type this I am running 1.55V through the CPU
2.64Ghz at 49*C running Prime Dual Small FFTs.
Seems stable.
I really wanted 2.7 out of this chip, but it ain't gonna happen unless I water cool and prolly have to take the IHS off.
The A8N32-SLI could be limiting me, but I doubt it. Some parts of this board are confusing that's for sure. Also, CPUZ doesn't show the (+0.02V) that I set in the bios to get the voltage I'm at. Kinda weird, but PCProbe shows the correct voltage.
I think I may try some more of the funky mobo settings, like overvolting the Hypertransport bus and North Bridge.
The chip average I guess, I may look at getting a 170 to test out.
If I try for the insane 1.6V, I'll let ye know... also, not done testing 1.55 yet.
Been running prime for 15 minutes now at 2.64.... Hmmm.
More to come I guess.
POS, core 0 failed after 26 minutes.
Oh, forgot to mention, I did do a 16hour CPUBurnk7 as well...
well, back to 2.6ghz I guess... or maybe I'll try 1.6v to be crazy....
Guys, I need help. I can't get my opty 170 to 2.4ghz without 1.64 volts! I am running at 7x300 right now and memtest comes up without any problems for 24hrs. I really want at least 2.4, but my second core keeps failing almost instantly. I've tried lowering my memory and I even tried 240x10, but it didn't work. I am definetly not a newb to overclocking, but the DFI has alot of new options. Any help is appreciated.
what really......can't be man........i mean all the 165's with that stepping are easily doing 2.6GHz........with low volts mind youQuote:
Originally Posted by cdelatte
what bios are you on.............623 bios and the new 11-14 or whatever they called it are THE BEST for dual core CPUs...............i'd give the new bios a try as eva2000 saw some decent OCing improvement with it..........http://www.i4memory.com/showthread.p...8994#post28994
So guys, when it comes to OC, i'm pretty much a noob to the ins and outs.. I finally got my parts in on friday and put my system together over the weekend. From a non-OC perspective, having a new setup is great (I moved up from a p3-1ghz !!).
I know this is absolutely not extreme, but I haven't really began to get crazy with it, I still have a ways to go in learning the ins and outs:
It's an Opteron 180 CCBWE 0543:
http://www.anodized.com/~clayne/tmp/o180.jpg
The temps are inaccurate there because I had taken the screen shot after I turned the fans down and let it cool off. It's more accurate to say it goes up to around 52-55C loaded wtith the fans @ 5800 rpm (Venus 12). I did raise VC up to 1.45, and had the chip @ 2.8, but the average non-loaded temps were a bit too high for my tastes (48-49C steady). Stability-wise it was fine. Currently I'm still running it at stock VC and 2.7 ghz. Heat looks to be the main issue to handle now (what else is new).
edit: Sorry about the image size, I'll fix that in any new posts.
Quote:
Originally Posted by dinos22
I'm running the 6-23. I was hesitant to run the beta because it didn't look like it fixed muched. I'll give it a whirl and post back with some results. It will probably be tomorrow when I post again. Thanks
man i don't think you need all those volts for 2.4GHz...............maybe clear the bios again and start all over againQuote:
Originally Posted by cdelatte
Probably a suicide run here, but now @ 2.64GHz (240x11) and :slapass: 1.55V bios/up to 1.60V in Windows. I sure hope that max tcase rating of 49 degrees C was a typo :p Seeing up to 55 degrees C when running 2x FAH WUs with a cold-ass room (maybe 25 degrees C ambient), Zalman 9500 w/AS 5, 4 80mm Sunon case fans, and no side panel :nono:
Me = crazy (or dumb, take your pick) :D
http://img.photobucket.com/albums/v2...n/2640opty.jpg
Man, another 175 stuck at 2.6 hmmm... It's like they pre test these things for 2.6 at 1.5V or something lol.
Hey, coming from a Winnie 3000 that maxed out @ 2.43GHz this thing is a dream :DQuote:
Originally Posted by phadeout
2x SPi 32M stable shot:
http://img.photobucket.com/albums/v2...2m2640copy.jpg
Opened the window in my room last night. I'm freezing my ass off in here but so's my comp :D CPU temp's down to 48 degrees C now. I can live with that.
Quote:
Originally Posted by dinos22
I feel the same way. I was thinking maybe a bad MB or maybe a bad seating of the processor. Anyway, I flashed the Bios and it made things worse. Now both cores fail instantly with Prime95. This is running at 1.55v and 240x10 or 300x8. I can run at 7x300 all night long @ 1.4v, but I feel ripped off. I know I shouldn't b/c I got what I paid for, but others are getting so much more than what they pay for! What's funny is it feels stable all the way to around 2.6 and I know theres a difference between feels and is stable. I was thinking of selling mine off, but the prices for another have skyrocketed! I'm going to clear my Bios again, reseat my processor for the heck of it and maybe even reflash. If that doesn't work then I'm think I might sell it for the profit and try a different processor. :rolleyes: Bad thing is, is I always wanted a dual processor system with 1mb cache.
Before blaming the CPU you should try it in a real enthusiast mobo like an Ultra D, or even better, an Expert
I have heard of a few ppl with OC problems using the Infinity series board
hmmm, the infinity....
are you sure that you should be flashing your BIOS with the BIOS's for the lanparty boards?
try this DFI BIOS flashing cd from tmod:Quote:
Originally Posted by cdelatte
http://www.dfi-street.com/forum/showthread.php?t=22031
it has menu's showing the BIOS's available for different DFI boards
Doh, I'm sorry, I have the Lanparty. I was updating my specs here at work and got confused.
i have a CCBWE 0543TPMW 170 coming in soon, as well as another unknown 170. Will report results by the weekend.
Seems that core 0 is weaker than core 1 as core 0 is only stable <2565 where as core 1 will only start failing P95 around 2650. Tried using cpuburnk7 for 10 hours today but has made little difference.
Any ideas on how I can improve the second core? More burn in?
Try to burn it in some more. If it works then thats great, and if it doesn't then you're no worse off.
I get my motherboard back this week (thursday?) from rma and I'll be testing my opteron. I had 2.80ghz before I upped the voltage and was pretty stable at 2.95ghz with a little bump (no errors after a few hours of prime but not really extensive testing). I was shooting for 3.0ghz when my mobo died so lets hope for the best. Also, this will be the first time that I will test burning in myself so I'll be sure to report on that.