It looks like there's enough room to use either slot, whether you have SLI or not.
It looks like there's enough room to use either slot, whether you have SLI or not.
Still have the BSOD with the NV_DISP.DLL occurring on a regular basis, cannot run any 3D apps at all. Running everything at stock.
In an effort to identify the cause, memory keeps coming up as the culprit. I have everything set to AUTO in the bios, Everest reads the SB at 1.6v and the NB at 1.15v.
Which one has the memory controller? One sounds to high, one to low. Memory passes memtest for 12hrs.+
I still think it something to do with the 8800GTS or the drivers! As I've googled this error message, it sounds like it's very common on NVidia boards, 680i or 680a or 650!
increase NB to 1.4 at the least.
SB to 1.55 should be fine.
you can do 1.55volts on the NB no problem, but I see no reason to up the SB voltage beyond the 1.50volts it's been fine with every overclock I've done and I've gotten to 1600/1000.Quote:
Originally Posted by shimmishim
Naughty, finally got a dual 32MB SPi to post @ 3600/960; I'm so happy...Ran ORTHOS for 3 hours but had to stop temp >60 load w/ Infinity P/p :(Quote:
Originally Posted by Naughtyboy
http://img262.imageshack.us/img262/9...3442bb1.th.png
How come the second SPi is faster than the first?
4Mb shared L2 Cache does not necessarily mean 50% per core all the time ;)Quote:
Originally Posted by H0RM0NE
Quick questions
When your saying your CPU temp > 60 are you talking about the temp of teh cores (read by CoreTemp or such program) or the reading the BIOS/ASUS programs give you?
Also I'm suffering random crashing when doing more than 70% total load on a Q6600. It happens at 3030Mhz, 3150Mhz, 3300Mhz. Basically any speed i set it to. i can boot & run windows Orthos whatever. but if i stress all 4 cores after awhile the system just reboots. same thing happens at NB voltage of 1.4, 1.45 or 1.5. exactly the same so i dun think thats the problem. I dun like going past 1.475 Vcore cos my Core temps get to hot. & its happening even at 3Ghz when it will run 3Ghz Orthos on 2 cores stable @ 1.38125 V. so i dun see why i would need a full extra volt & then run into over heating problems. Also tried ram at all range of speeds. Currently @ 965Mhz 4-3-3-8 timings @ 2.5V. But i am getting the crashing issue even at 800Mhz 5-5-5-15 @ 2.2 volts. so i really doubt ram is the problem.
Bios is 602
could vDroop be an issue?
if not any other ideas?
my guess its ram sub-timings.Quote:
Originally Posted by BenArcher
it took me a long while to determine that it was the subtimings that prevented me from running orthos for more than 15 minutes.
once i found the right set of subtimings, i was able to orthos for 11+ hours.
anyone else having issues with their NB temps?
i've replaced the stock one with a swiftech mcx(?)-159cu and it is hot to the touch at the base. i can't keep more than a few seconds on it.
now that i've been able to run orthos for 11 hours, i'd expect to be able to do regular things with no problems but i had my windows media player crash on me 3 times last night. i wasn't stressing the system, yet it still crashed.
man, the chipset sure does generate a lot of heat!
SO true, I'm thinking of HR-05 for NB... it will deal with the heat mercilessly ;)
I like the ability to remove one heatpipe set only (NB & vertical mosfets) and not having to remove the whole solution (see Striker Extreme)
agreed! i got some PLL sinks for the vertical mosfets. :)Quote:
Originally Posted by xoqolatl
I used latest ver. SpeedFan setup to read tcase and tjunc temps that indicated >60C to make my decision to stop. AFAIK CoreTemp and SF read the same; tjunc thermal points. I guess I need to look at re-lapping for a flatter contact between the HSF and CPU. My Infinity does not seem to get very warm at all.Quote:
Originally Posted by BenArcher
Thanks for the idea.
Ive reduced each sub timing by 1 to see if that makes any difference. As well as after playing with a multimeter i found my VDroop to vary between 0.06 & 0.07 Volts so that seemed pretty major. So I have done the Vdroop pencil mod so now it only drops 0.01V.
Seems more stable now. Prime is running now so i guess ill see how stable soon :P.
Also does this seems strange to anyone?
If i set BIOS to default or Clear CMOS. I can;t boot at all. Can;t even get into BIOS unless I take out a stick of ram & even then its flaky. Until I can manage to raise my RAM voltage & NB voltage its totally screwed. once they are up though everything runs happy until i stress all 4 cores. But hopefully thats fixed ;)
Ive come down to two boards for my next upgrade P5N32-E SLI PLUS or the P5N32-E SLI which of these two is better?
i have that problem too with my 8000HZ's.Quote:
Originally Posted by BenArcher
it has to do with the board and the way it reads the SPD timings on the sticks.
my sticks are programed to boot at ddr2-1000 4-4-4-5 with default voltage which is aorund 1.8 i believe... hence my sticks can't do that sort of timings at 1.8 so it won't boot.
i'm sure yours are probably doing the same thing.
I have both boards and I would say you can't go wrong with either. I found MY NON plus better for max FSB but boards are like CPU's some will work better than others at lower voltages.Quote:
Originally Posted by malik22
The pencil mod is recommended to sort out Vdroop on both boards.
can anyone tell me if the quad-core does ok on this board?...like 400 MHz FSB
What bios are you running? to clear the cmos I pop the battery. When an overclock fails I just press the reset button and the system boots at stock.Quote:
Originally Posted by BenArcher
320 if you're lucky :/Quote:
Originally Posted by Ace-a-Rue
mine are 8000 sticks too. but the SPD is programed to 5-5-5-15 @ 800Mhz 1.8V
so yeah i dunno whats up with that. but at 2.2V that are running happy at 965Mhz 4-3-3-8 timings & giving a nice 7500MB bandwidth :)
The sub timings wern;t my problem it seems it was the VDroop.
Im on 602 bios & sometimes it does reset but sometimes it just jams & is very unhappy at everything. I worked out how to get around it though. if i do a quick pencil VCore mod it boots. Then I just set it back down & then rub off my pencil :P
What's the fastest people are running their memory on these boards at 1T? 450? 500? 550?
i've settled for 24/7 settings of 426.7MHz 4-4-4-8 1T with 2.1V at the moment, no idea if that's any good :shrug: (though i doubt it :p:)
took me a while to get stable sub timings
might try going higher sometime, but for daily use i don't really fancy going over say 2.2-2.3V
Done some benching:
400MHz 4-3-3-3 1T is equally fast as 550MHz 5-3-3-3 2T
Currently working on max. 1T speeds, I'll keep you posted
Thought you guys may find this interesting. Just for :banana::banana::banana::banana:s and giggles, Im currently running my P4 930 in this mobo until I can purchase a C2D to replace it. I was actually very surprised to see it go this high. 24hr Orthos Stable. (CPUZ reports the CPU volts incorrectly for some reason)
I did purchase two 40MM fans when I bought this mobo from Newegg as I had read about the heat concerns, and thats no lie. Even with these two 40mm's on the heatpipes, OC'd they can still get very hot. I also have a Delta 60MM on a rheostat that is positioned right above the NB.
Even at this speed I barely out pace a C2D @ 2Ghz.. haha (according to Sandra anyways). 8800GTS is CPU limited until I purchase that C2D. :)
http://home.comcast.net/~clamarr/4050CPUZ.JPG
http://home.comcast.net/~clamarr/24hrORTHOS.JPG
(Temps in pic were taken right after Orthos was stopped. Temps on the 930 go almost immediately back to idle for some reason.. Underload it was @ 113-115F or so.)
This was done with a Tuniq Tower 120 cooler. So far I'm very pleased with this board. Although its not without its flaws. This board takes a little bit of fiddling. Certain FSB settings would not work, and others would (currently running 0602 Bios release updated almost immediately after switching the board on). I stopped at about 3850 because I fealt like I had hit a wall, and my friend who owns a EVGA 680i advised he has what he calls "FSB holes" where he'll reach a certain FSB and a number of FSB settings wont work (either lockup or not boot), but he'll pass those and continue to try above those and he'll find a few that work. Definately takes some time to figure out what works and what does not.
Also unlinked seems to not work for me. I can hit speeds with the MEM "linked" that wont even post "unlinked". Not sure why or if its due to the 930. Once I get a C2D I'll definately be trying unlinked again. Im currently running a 1GB Kingston DDR2 800 Stick. Soon to be 2GB with C2D.
I'm getting bored waiting for my Xeon 3070 so here's a pic of my p2n32-e sli plus.
edit: pic is now in the watercooling section