Printable View
I would make sure your RAM is working.Quote:
Originally Posted by skinnee
Then, make sure you dont give them more than 1.84vdimm in BIOS (1.90 real), this kills RAM for sure.
Thats some nice results, if you could have those timings at 8-8-8-21, it would be just amazing.Quote:
Originally Posted by tekjunkie
Make it 24/7 stable and you got yourself some golden hardware.
The RAM is rated for 1.9V, I did look and with overvoltage its 1.94...I'll drop it a bit. Will run memtest prior to booting to Windows this time.
Lol, thanks slim. I put my Gskills on and tried doing it, but I cant get my Gskills to hit DDR3-2000 without insane voltage to even pass memtest. So this is what I did after I put my Gskills onQuote:
Originally Posted by slim142
http://img75.imageshack.us/img75/332...0fsbkd6.th.jpg
I am currently priming it.
I am still getting 12K reads and I dopped the voltages too for a safe 24/7 settings on air. This is probably gonna be my 24/7 settings on my E8600-S2E combo and am probably going for the 790i FTW with 280 GTX tri sli for my other rig with my QX9650 on it all WC.
BTW, Slim how is WC comming along.
I would make sure to fix that asap. I just hate how more than 1.90 can kill D9s so easily.Quote:
Originally Posted by skinnee
Look at you tek, thats a impressive overclock if you ask me.Quote:
Originally Posted by tekjunkie
What voltage do you have for the RAM on BIOS? And for NB?
Well, about the WC, Im still trying to get more parts, Its been kinda busy this days hehe, but Im pretty sure they will come soon :D
Okay, so here is where I'm at. I am amazed that RAM won't go higher, it is 2x2GB, but still, 1780 is it or LCD Poster does not get past DET DRAM.
Reached 1780 Linked and Synced. SuperPi, PiFast and wPrime ran without a hitch, Vantage on the other hand did not, Display Driver kept crashing. CPU-Z Valid. Vantage run had to be done at 1700 Linked and Synced, only P14128, but good for me thus far.
I keep a spreadsheet of everything which is attached, that has every setting in BIOS listed. Currently running and benching at 1800 FSB, 1600 DDR, just have to run Vantage then on to another setting. :up:
I would also like to be able to run at least 1800 Linked/Sync, thats the perfect spot. FSB2000/RAM1800 is also a nice spot, but a quad to get to 500 would need to be a rare sample. FSB1800/RAM2000 would also be nice as long as you dont need more than 1.90
I hate I cant overclock... Is making me go crazy
Hey everybody
Just one question regarding the "new" Intel Burn Test, is it reliable? I have run it 10 times and (for my surprise) it passed all 10, but Im surprised because I started it, went to eat, come back and is done?
Is it true that with this program you can test stability within 15 mins? (I ran the test 10 times with Maximum stress)
RAM @ 1.92 and NB @ 1.44. Bothe BIOS settings.Quote:
Originally Posted by slim142
I would still run prime after it passed the linpack(Intel burn test depends on the linpack from Intel). To give you a for instance, after putting on my Gskills and after passing linpack, prime failed within the first hour on one of the cores of my E8600.I am pretty sure it's the RAM as I can do 500 FSB linked and synced with more than 2 hours of priming with my OCZ DDR3-2000 4 GB kit. My S2E for some reason hates the microns(on my gskill and OCZ 1600EB kits) and it loves the samsungs on my OCZ DDR3-2000 4 GB kit. Very wierd.Quote:
Originally Posted by slim142
Slim, you still have those G.Skill DDR3-1600 2x2GB (F3-12800CL7D-4GBHZ)?
If so, switch to CAS8 for anything 1800+. At CAS7 I kept getting POST lockup with DET DRAM on the LCD Poster. Switched to CAS8...MemTest complete with no errors. Now I have to tweak sub timings.
edit
Correction, CAS7 @ 1800 (7-13-13-33 2T) is POSTing now, we'll see how MemTest goes.
Hmm, make sure you are not overvolting those sticks. Im guessing your real vdimm right now is 1.98 idle and 1.96 load.Quote:
Originally Posted by tekjunkie
That linpack doesnt convince me at all, I will keep prime as my super-stress tool.
Yes, but mines is 2x1GbQuote:
Originally Posted by skinnee
Do you think this memory can run at 1800Mhz 8-8-8-18 @ 1.90 real (1.84 BIOS)? or even 8-7-7-18?
I dont want to OC RAM because if for some random reason I corrupt my system, I seriously have no time to sit and reinstall everything..
What do you mean when you say 7-13-13-33?, Why do you go that high? On the worse case 7-8-8-33 maybe?
I got mem test passed @ 7-7-7-20 2T, trying 1808 @ 7-7-7-22 2T right now, nope MemTest just locked up.Quote:
Originally Posted by slim142
I'm going to keep trying but I have a feeling 1800 is my RAM wall.
Trying 1808.2 @ CAS 8.
I think I might have to jump on the E8600 bandwagon. Maybe I'll pick one up this week. You able to get your clocks any higher? I'd like to see 4.5-5ghz on water.
I am on air, so I can't answerthat. But somewhere between 4.5 to 5 is very doable with a good batch of E8600 on water. I have seen 'em in the E8600 thread here @ the Intel section.
im thinking of getting a S2E next week, do you guys think its a good idea ?
Hit 1860 Linked and Synced at CAS8 (8-8-8-18 2T), with 1 Run of MemTest passed. CPU-Z Validated
Odd thing when I went back to a 1700 Linked and Synced at CAS7 (24/7 settings), NICs won't grab a DHCP address and won't communicate when I manually set an IP on my network. I tried uninstalling the devices, but that didn't seem to work either...checked for corruption, none found.
Anyone else had any problems with the NICs (nForce 9.64 drivers) not working?
YES..I have had the strangest issues with the nic's when overclocking. Currently I'm using 9.64 for everything except the nic's, 15.17 for just the nic's themselves. This setup has been working well for me, one thing I do now when I'm trying higher overclocks is to disable the nic's in the bios first. If OC passes memtest re-enable before going into Vista.Quote:
Originally Posted by skinnee
Other thoughts...
You may have a corrupt nic driver, the install and uninstall does not always work correctly, if you run the nvidia control panel and the networking tree is not there your driver is corrupt. Uninstall reinstall.
Also try going into your router and releasing the address, power off router and then back on, this helped me a few times. The whole teaming virtual driver thing is finicky for sure. I use VNC to remote access my computer so I have to keep an eye on the IP the virtual driver is using, it can't change or VNC has to be reconfigured, you'd be surprised how many times it's gone and switched from using a combined single IP to 2 seperate ips. No idea why.
I sometimes have more wierd problem with my NICs. They won't even light upQuote:
Originally Posted by skinnee
when the PC is off and the light does not go on in my router too. Then I switch the connection to the other connection and everything is fine. Obviously this is not a driver problem as there is no connectivity outside the OS.
You passed 7-7-7-20 at 1800? That should be good enough. If your NB voltage is lower than 1.38, then that might be the problem.Quote:
Originally Posted by skinnee
Quote:
Originally Posted by skinnee
Thats a good ideaQuote:
Originally Posted by Trigger5521
Disable NICS while overclocking, they seem to give out problems (a lot)
[Remember when I had to buy a D-Link PCI card?]
Yeah, first boot with 1860 Linked and Synced the NICs Link and Activity lights work, but won't grab a DHCP address or use a static. I can ping loopback so I know the TCP/IP stack is fine. I'll try 15.17 for the NICs alone and stick with 9.64 for everything else.Quote:
Originally Posted by Trigger5521
You mean the chipset/NIC driver or the OS? I have Imaging for getting my OS back quickly versus reinstalling the OS. Crazy thing is, the NICs aren't working in Acronis Boot Manager either.Quote:
Originally Posted by Trigger5521
I use a seperate DHCP server, but yeah I know what you're getting at and those are the first few things I tried including setting a static IP on the NIC in use. You don't use RDP? Why VNC over RDP...linux use?Quote:
Originally Posted by Trigger5521
On the NIC teaming, I haven't used it due to local bandwidth, I have a full GigE network (all Cisco) up to my cable modem and just don't see the need for NIC teaming...another thing to go wrong. :D
Thanks for the tips...I'll let you know how it comes out.
No, I gave up on CAS7 at 1800 last night. Night was drawing to a close and I wanted to see if I could get preliminary settings in the 1800-1860 range, so I bumped to CAS8. Got 1800, 1820, 1840 and 1860 at CAS8...booted into Vista using 1860 and thats when the NIC driver issue happened. Ran some quick tests and went back to 1700. NIC problem was still there, needless to say I did not get to bed when I should have. :shakes:Quote:
Originally Posted by slim142
I do, thats why I dug out my trusty Intel PCI NIC a few minutes ago as a band-aid until I get the onboard NICs working again.Quote:
Originally Posted by slim142
Odd...
Fired the machine up, first booted into Safe Mode, checked the driver file for the NICs. Rebooted since I couldn't open NVIDIA Control Panel. Both NICs are working just fine. :shrug: :shrug: :shrug:
Hi,I have this same motherboard striker 2 extreme,along with Q9550,4GB of Corsair Dominator ddr3 ram,sli gtx280,I just wanted to check to see if I am running safe voltages for 24/7 running,I have the Q9550 overclocked with these settings.
FSB memory and FSB QDR are linked and sinked at 1800mhz which gives me 3825mhz on the Q9550.
Ram settings are
P1 enabled
P2 enabled
8-8-8-24-2T
Voltages are
CPU Vcore 1.43125
Mem volt 1.80
All other settings are at auto except I turned of that speedstep.
The system is really stable,but I mainly wanted to know is the cpu vcore voltages safe to run for 24/7 on air.
Nothings is getting to hot I don't think,the cpu is around 32 degrees at idle and gets up around 60 to 65 degrees on full load,the north bridge sits at around 51 to 53 on idle and will go anywhere from 55 to 60 on full load.
Another strange thing I have notist,is that the readings in windows from the programs Everest and CPUZ seem to give different readings on the vcore,Everest tells me the vcore is at 1.44v to 1.46v at idle,but CPUZ says the vcore is only running at 1.376v not sure which one is right,hopfully CPUZ is,still both are giving me different readings from what I set in the bios.
Here is the CPUZ vcore reading
http://img158.imageshack.us/img158/1049/cpuztg1.th.jpg
And Everest vcore readings
http://img158.imageshack.us/img158/8...est1rb0.th.jpg
I'm 4.5 @1.26v 24/7 on 1/2" water.Quote:
Originally Posted by Fusion2002
Ran some benches 4.7ghz @1.31v first sub 10sec pi 1m....
It's really an awesome chip, E0 stepping rocks.
My QX9650 is on the shelf indefinately.
poor QX9650...I'd like one if you're willing to sell. PM me a price if you're interested.
Anyone have a success story with the new bios. I have not heard anyone reporting any real benefit to the new bios. I am reluctant to even try it.
As I said strangest issues, it's very weird huh. I have had so many strange things go on with the nics I'm not sure what's what.Quote:
Originally Posted by skinnee
Just now the computer woke itself up for no reason, check the event log and the date and time for the wake event by the nic is not the same as system time. A quick power cycle of the router and bango everything is fine again sleeps without waking up. Router date and time are accurate. Not sure what's up with that.