Have you tried putting the RAM in the 2nd (black) dimm slots? This board is decent if you only plan to run 2GB ever, if you want to run 4GB its more or less a crapshoot. Can also try increasing the voltage slightly to 2.2V, which would compensate for any undervolting to the dimm slots or fluctuations in Vdimm. If all else fails, I'd return it within your retailer's return period. Asus RMA is a pain to deal with and won't cross-ship under any circumstances.
Update.
My test with all of the subtimings manualy set to 1 more then the auto set them at appears to have ended my constant freezing problems with this ram (Almost 4 days now since I did this and no freeze). I had this freezing problem with BIOS versions 505 and 608. Not sure what to do now since it appears there is a compatibility problem between this ram and the BIOS that is causing the subtimings to be set to low. If I keep this RAM and future BIOS updates do not fix the problem it is going to be a real pain to have to manualy change the subtimings every time I change the FSB. I will also need to test them one at a time with the auto setting to see which one/one's are causing the problem.
Any thoughts?
I have just had the similar experience.
It seems that the subtimings play a more important role that anyone might think.
I did the same thing - relaxed the subtimings even more aggressively.
tRC from 18 to 24 (as per my EPP)
tRRD from 3 to 6 (actually, by accident...)
tWR from 5 to 6 (as per my EPP)
The programs seem to open a bit faster, even though the Memory bandwidth (SANDRA) dropped to ~6300 from ~6500.
All my startup problems suggest the memory as a culprit. When I hit "Reset" on a "frozen" POST (just after the CPU info is displayed, immediately before the memory check would be performed), the computer reboots with the same OC of 2.92GHz.
So the problem is not the overclock, since it would go back to 2.4GHz, but (I believe) the memory, which, due to some kind of error, doesn't allow the POST to proceed.
Well, we'll see how it goes, but I wish that the whole process wasn't just a trial and error game, and the manufacturers of both the RAM and MB's would give us more information.
It seems that the subtimings play a more important role that anyone might think.
I did the same thing - relaxed the subtimings even more aggressively.
tRC from 18 to 24 (as per my EPP)
tRRD from 3 to 6 (actually, by accident...)
tWR from 5 to 6 (as per my EPP)
The programs seem to open a bit faster, even though the Memory bandwidth (SANDRA) dropped to ~6300 from ~6500.
All my startup problems suggest the memory as a culprit. When I hit "Reset" on a "frozen" POST (just after the CPU info is displayed, immediately before the memory check would be performed), the computer reboots with the same OC of 2.92GHz.
So the problem is not the overclock, since it would go back to 2.4GHz, but (I believe) the memory, which, due to some kind of error, doesn't allow the POST to proceed.
Well, we'll see how it goes, but I wish that the whole process wasn't just a trial and error game, and the manufacturers of both the RAM and MB's would give us more information.
so what nb voltage yall use? ppl on XS forums told me 450 ish was fine with stock voltage but i need 1.39v just for 400 fsb. any one dime in on their setting? im at 415 right now and the HS is hella hot.
I have mine set to Auto, but I am only @325MHz FSB.
It has been recommended to set it to 1.56V with 4 sticks of RAM, but in this case I would strongly suggest some kind of active cooling - I have a small (I believe 40mm) fan installed with a drywall screw inserted between the NB heatsink fins. It is enough to get just a bit of a "bite".
I had it at 1.56V for awhile, but it didn't do anything to my issues - I hope the relaxed subtimings help.
Good luck!
It has been recommended to set it to 1.56V with 4 sticks of RAM, but in this case I would strongly suggest some kind of active cooling - I have a small (I believe 40mm) fan installed with a drywall screw inserted between the NB heatsink fins. It is enough to get just a bit of a "bite".
I had it at 1.56V for awhile, but it didn't do anything to my issues - I hope the relaxed subtimings help.
Good luck!
By subtimings, you mean the bank of settings below the 4-4-4-12-t2 bit?
Mine are all set to auto, how can I tell what they're actually running at? I can tell that Trc is at 22 from CPU-Z but not any of the others.
On auto, mine per Everest are:
tRC = 21
tRFC = 38
tRRD = 3
tWR = 5
tRTW = 5
tWTR = 8
this per Everest, at 711 with auto in the BIOS
There is no doubt in my mind that AUTO will give settings that are unsuitable for some RAM. Not all RAM is the same. on AUTO, the BIOS surely can't know what is right for your particular RAM. It just chooses a set of values somehow, which might be OK for some and not OK for others
hmm so with 4 gigs upping the nb voltage helps it be more stable? i didnt know nb had anything to do with ram. guess u learn something new everyday
Just recently I've begun to experience some random freezing and it's starting to annoy the piss out of me. I've run ORTHOS stable (cpu test) for 8+ hours at this OC. I ran memtest while at work today (8+ hours), no issues reported, and outside of a freeze (1 out of the 12 times I've run the mixed test) after 8 mins 32 seconds with Orthos, I can't reproduce the cause. I'm considering dumping the board and trying a P35. I really have no other complaints with this board (especially since I'm a 2gig ram guy ;P) but even after adding a new HD, a new OS, reformatting back to XP, and still experiencing random freezing, I can't figure it out. It's not even when I play games, so I don't think the video card is doing it. Since orthos runs 8+ hours every time but the one, I don't see it being an OC issue (and I've run Orthos for 12 hours at stock w/ no issues).
Outside of letting memtest run for eternity, can anyone else suggest a possible culprit? It's not a device manager issue as I've reformatted and ensured everything is installed, updated, firmware'd, etc.
Outside of letting memtest run for eternity, can anyone else suggest a possible culprit? It's not a device manager issue as I've reformatted and ensured everything is installed, updated, firmware'd, etc.
Try to relax the subtimings like I did above:
tRC from 18 to 24
tRRD from 3 to 6
tWR from 5 to 6
Memory Voltage 2.07V, VCore 1.3125V.
NB Voltage on Auto - if that doesn't work, increase to 1.56V
Hope this helps.
tRC from 18 to 24
tRRD from 3 to 6
tWR from 5 to 6
Memory Voltage 2.07V, VCore 1.3125V.
NB Voltage on Auto - if that doesn't work, increase to 1.56V
Hope this helps.
This might be a stupid question, but according to the manual, the DIMM slots are not color coordinated. It lists Slots A_1 and A_2 as being Channel "A", which are the first Yellow and black DIMM slots.
[yellow] A_1
[black] A_2
[yellow] B_1
[black] B_2
From discussions here, it seems to me that they are color coordinated, which is correct? I've been running so far with identical sticks in the first 2 slots (Yellow and Black). When I match them up - yellow and yellow, the PC is unstable and freezes constantly.
[yellow] A_1
[black] A_2
[yellow] B_1
[black] B_2
From discussions here, it seems to me that they are color coordinated, which is correct? I've been running so far with identical sticks in the first 2 slots (Yellow and Black). When I match them up - yellow and yellow, the PC is unstable and freezes constantly.
Apparently it is no longer critical to "color match" the slots to run memory in Dual Channel.
But I do - mine are yellow-yellow and black-black.
Are you sure you are running in Dual Channel...?
But I do - mine are yellow-yellow and black-black.
Are you sure you are running in Dual Channel...?
Man, what a quirky board...I simply can't get it to be stable with 4X1GB if I don't keep a 1:1 memory / FBS ratio.
I was running it unlinked with the memory @845MHz (Due to the 'hole' if one has 4GB; otherwise it won't POST @800MHz) and a mild overclock on my C2D E6400 @2.66GHz.
Though it'd POST with no problems, I'd get a BSOD in Vista 64 as soon as it loaded explorer, unless I raised voltage on the NB to 1.56v and the memory voltage to 2.1v; that's a little too high for my tastes. But Orthos fails after the first test, and so does Memtest. And I'd get BSoDs while doing stuff like using a web browser or using WMP.
Keeping a 1:1 linked ration fixes all the problems, but then I can't keep the memory speed as high as I want, and I have to set the timings really loose. 5-5-5-15 just BSODs as soon as Vista loads up. 5-7-7-17 is stable though.
I was running it unlinked with the memory @845MHz (Due to the 'hole' if one has 4GB; otherwise it won't POST @800MHz) and a mild overclock on my C2D E6400 @2.66GHz.
Though it'd POST with no problems, I'd get a BSOD in Vista 64 as soon as it loaded explorer, unless I raised voltage on the NB to 1.56v and the memory voltage to 2.1v; that's a little too high for my tastes. But Orthos fails after the first test, and so does Memtest. And I'd get BSoDs while doing stuff like using a web browser or using WMP.
Keeping a 1:1 linked ration fixes all the problems, but then I can't keep the memory speed as high as I want, and I have to set the timings really loose. 5-5-5-15 just BSODs as soon as Vista loads up. 5-7-7-17 is stable though.
Odd, I run dividers with 4 x 1GB no problem at all. I run 711 at the moment with a 266 FSB. I think that's 3:2 or something in the BIOS.
I run 2.0875 for the memory which is what the sticker on it says (2.1v actually). It's not that high really.
I run 2.0875 for the memory which is what the sticker on it says (2.1v actually). It's not that high really.
0202 was great....then i upgraded to a Q6600 and with it 0608 and wow......who the heck approved this POS for release. Anyway after reading here and elsewhere i set my timings to 4/4/4/12 2t 2.1V and two other other subtimings. Also upped my VCore to 1.3 as it was defaulting to 1.24. Rock solid stable. Played BF2142 for an hour last night with everything on max.
Problem: When i unlink the FSB and up it even for a very modest overclock like 1200 the thing hangs at the post screen. What is weird is that if i take on stick of ram out it doesn't hang. Anyway here are the specs
Q6600 G0 - stock fan
TWIN2x1024-6400C4
8800 GTX KO
XFi-Xtreme
Samsung 183L
7200.8 400 gb HD
XP SP2
ALL mobo settings except the above mentioned memory timings/VCore/VMem are 0608 default/auto. Question is how do i get a 3 GHz overclock (which i got with my E6600 + 0202 easily). What settings etc.
Problem: When i unlink the FSB and up it even for a very modest overclock like 1200 the thing hangs at the post screen. What is weird is that if i take on stick of ram out it doesn't hang. Anyway here are the specs
Q6600 G0 - stock fan
TWIN2x1024-6400C4
8800 GTX KO
XFi-Xtreme
Samsung 183L
7200.8 400 gb HD
XP SP2
ALL mobo settings except the above mentioned memory timings/VCore/VMem are 0608 default/auto. Question is how do i get a 3 GHz overclock (which i got with my E6600 + 0202 easily). What settings etc.
Does anyone know when the next bios is expected. I'm ready for the 700 series from Nvidia...hopefully they will get it right this time. 
Does anyone running the P5N-E SLI have trouble with coming out of S3 standby? I have posted about this problem in the motherboard forum, but just saw this dedicated P5N-E thread. Here is my original post (no responses yet) :
http://forums.anandtech.com/me...=2085422&enterthread=y
The short of it is, instead of coming out of sleep, when I hit the space bar, the system boots. Did I enable too much? I am trying to get S3 standby to work on XP via the space bar on my PS/2 kb. Prior to upgrading to the P5N-E, I had an Athlon board and S3 Standby worked fine, so I know my PS is supplying the required power. So now I am thinking that maybe the pin on the mobo should be turned off, maybe that is telling the BIOS to reboot instead of come awake?
- I have changed the 3-pin KBPWR jumper on the board to the 2-3 position
- I have enabled Power Up by PS/2 Keyboard in the BIOS (set to space bar)
- I have set my ACPI suspend type to S3 (also tried "S1&S3")
- I have ensured the keyboard in Device Manager correctly states "Allow this device to bring the computer out of standby"
Not sure what else to try. I am running the 0608 BIOS (upgraded from 0202). I have installed the latest NForce drivers, latest vid, sound, mouse, and kb drivers, and fully patched XP SP2. Any other ideas?
Thanks,
BM
http://forums.anandtech.com/me...=2085422&enterthread=y
The short of it is, instead of coming out of sleep, when I hit the space bar, the system boots. Did I enable too much? I am trying to get S3 standby to work on XP via the space bar on my PS/2 kb. Prior to upgrading to the P5N-E, I had an Athlon board and S3 Standby worked fine, so I know my PS is supplying the required power. So now I am thinking that maybe the pin on the mobo should be turned off, maybe that is telling the BIOS to reboot instead of come awake?
- I have changed the 3-pin KBPWR jumper on the board to the 2-3 position
- I have enabled Power Up by PS/2 Keyboard in the BIOS (set to space bar)
- I have set my ACPI suspend type to S3 (also tried "S1&S3")
- I have ensured the keyboard in Device Manager correctly states "Allow this device to bring the computer out of standby"
Not sure what else to try. I am running the 0608 BIOS (upgraded from 0202). I have installed the latest NForce drivers, latest vid, sound, mouse, and kb drivers, and fully patched XP SP2. Any other ideas?
Thanks,
BM
Originally posted by: helix2
Does anyone know when the next bios is expected. I'm ready for the 700 series from Nvidia...hopefully they will get it right this time.
Yup, 0703 is out, right now. With a readme, which leads me to believe it's no beta.
Here.
Use at your own risk, though. At least one person in the ASUS forum has voiced his praise, claiming 0703 finally allows him to boot Vista 64 with 4 sticks of RAM running at 800MHz.
YMMV...
I'll wait until the BIOS appears on the download site before taking the chance, as I've killed one P5N-E SLI already, attempting a flash.
Regarding the 7xx series from nV, I wouldn't hold my breath. I fact, considering the random crashes I've had and the problems my mate continues to have with his ASUS 680i mobo, I reckon this is the first and last time I buy an nVidia board. I don't actually need SLI. I'll go Intel, next time.
Probably...
Oh yes... though it's kind of random. Sometimes perfect, other times no good. Definitely something to do with the video card.
I've noticed when the computer refuses to resume, the GPU fan does not spin up. Other times I've seen that all seems well, as in the computer resumes, but the GPU temp is sitting at 100°C! Idling! Keee-rist! Reboot, all good - fan going crazy for a few minutes cooling the GPU down.
I now refuse to use standby. My computer boots in next to no time. Still, I like S3 and would definitely use it were it 100% stable.
Ain't gonna be me.....like i said i AM stable even though i can't seem to overclock and BF2142 runs at MAX everything nice and smooth. I know that there has to be someone on here that wants to be the guinea pig
Just don't understand why they don't test it with every type of stick out there...not like there are alot or that it would take that long. Either it is plug and play or still messed up.
Just don't understand why they don't test it with every type of stick out there...not like there are alot or that it would take that long. Either it is plug and play or still messed up.
Originally posted by: meesterlars
Originally posted by: helix2
Does anyone know when the next bios is expected. I'm ready for the 700 series from Nvidia...hopefully they will get it right this time.
Yup, 0703 is out, right now. With a readme, which leads me to believe it's no beta.
Here.
Use at your own risk, though. At least one person in the ASUS forum has voiced his praise, claiming 0703 finally allows him to boot Vista 64 with 4 sticks of RAM running at 800MHz.
YMMV...
I'll wait until the BIOS appears on the download site before taking the chance, as I've killed one P5N-E SLI already, attempting a flash.
Regarding the 7xx series from nV, I wouldn't hold my breath. I fact, considering the random crashes I've had and the problems my mate continues to have with his ASUS 680i mobo, I reckon this is the first and last time I buy an nVidia board. I don't actually need SLI. I'll go Intel, next time.
Probably...
We have discussed the S3 issues somewhere around page 180-ish or 185-ish, so please read the posts from around June.
There was a few threads on the ASUS forum, too:
http://vip.asus.com/forum/topi...-E+SLI&SLanguage=en-us
And the ASUS FAQ section:
http://support.asus.com/faq/fa...D1345B&SLanguage=en-us
BTW, after struggling with the startup problems for over 1 month, I re-flashed the 0608 BIOS with 0401, and all the problems disappeared.
So... if you are stable under any BIOS version, DO NOT UPDATE TO NEWER BIOS VERSIONS UNLESS YOU ABSOLUTELY HAVE TO FOR A NEW CPU OR NEW HARDWARE
There was a few threads on the ASUS forum, too:
http://vip.asus.com/forum/topi...-E+SLI&SLanguage=en-us
And the ASUS FAQ section:
http://support.asus.com/faq/fa...D1345B&SLanguage=en-us
BTW, after struggling with the startup problems for over 1 month, I re-flashed the 0608 BIOS with 0401, and all the problems disappeared.
So... if you are stable under any BIOS version, DO NOT UPDATE TO NEWER BIOS VERSIONS UNLESS YOU ABSOLUTELY HAVE TO FOR A NEW CPU OR NEW HARDWARE
Hey guys,
Please excuse the stench of my newbie ugliness in anything that follows. I am in desperate need of help with a REALLY odd problem. Thanks in advance for any advice.
I just built the following system (a mix of new and old hardware):
Core Duo E6550 2.33 GHz (Stock cooling)
P5N-E SLI NVidia 650i BIOS 0608
2X 1GB Kingston KVR667D2N5 (Black Slots)
eVGA 7900 GT
160GB Maxtor
CoolerMaster eXtreme Power 650W
32-bit XP
I'm experiencing some really odd RAM issues and I can only assume one of two things at this point. Either this RAM Is totally incompatible or the RAM slots themselves are fried.
THE PROBLEM: I can only get 1 stick of ram to work in DIMM_B2 (4th slot). Even though my second stick can be plugged in any of the remaining slots, the motherboard doesn't recognize it as being installed. So long story short, although the system boots up fine it does not see the full 2GB. Both the BIOS and Windows only see 1024.
ATTEMPTED FIXES: I updated my BIOS to 0608 hoping that this would help me...it didn't. I swapped out the ram in various combinations, got a 1-long, 2-short beep when nothing was inserted in the fourth slot. No combination worked other than the single stick in DIMM_B2. I did ensure that both sticks of ram were working however by swapping the two sticks in DIMM_B2. I have read a number of articles on odd RAM compatibility problems with this board but none really address Kingston or my specific issue with "ghost ram". I tweaked a number of settings but I'm kinda stumbling around in the dark on this one. I've built systems before but this problem is out of my league.
QUESTION: Any suggestions on how I might move forward? Should I buy new RAM with better compatibility or does it sound like my ram slots are fried?
THANK YOU for any help in this my darkest hour
Denny
Please excuse the stench of my newbie ugliness in anything that follows. I am in desperate need of help with a REALLY odd problem. Thanks in advance for any advice.
I just built the following system (a mix of new and old hardware):
Core Duo E6550 2.33 GHz (Stock cooling)
P5N-E SLI NVidia 650i BIOS 0608
2X 1GB Kingston KVR667D2N5 (Black Slots)
eVGA 7900 GT
160GB Maxtor
CoolerMaster eXtreme Power 650W
32-bit XP
I'm experiencing some really odd RAM issues and I can only assume one of two things at this point. Either this RAM Is totally incompatible or the RAM slots themselves are fried.
THE PROBLEM: I can only get 1 stick of ram to work in DIMM_B2 (4th slot). Even though my second stick can be plugged in any of the remaining slots, the motherboard doesn't recognize it as being installed. So long story short, although the system boots up fine it does not see the full 2GB. Both the BIOS and Windows only see 1024.
ATTEMPTED FIXES: I updated my BIOS to 0608 hoping that this would help me...it didn't. I swapped out the ram in various combinations, got a 1-long, 2-short beep when nothing was inserted in the fourth slot. No combination worked other than the single stick in DIMM_B2. I did ensure that both sticks of ram were working however by swapping the two sticks in DIMM_B2. I have read a number of articles on odd RAM compatibility problems with this board but none really address Kingston or my specific issue with "ghost ram". I tweaked a number of settings but I'm kinda stumbling around in the dark on this one. I've built systems before but this problem is out of my league.
QUESTION: Any suggestions on how I might move forward? Should I buy new RAM with better compatibility or does it sound like my ram slots are fried?
THANK YOU for any help in this my darkest hour
Denny
TRENDING THREADS
-
Discussion Zen 5 Speculation (EPYC Turin and Strix Point/Granite Ridge - Ryzen 9000)- Started by DisEnchantment
- Replies: 24K
-
Discussion Intel Meteor, Arrow, Lunar & Panther Lakes Discussion Threads
- Started by Tigerick
- Replies: 20K
-
-
-
Facebook
Twitter