Prime errors with gskill le at only 260!
I am getting rounding errors running my gskill le in prime 95 at 260 htt with a 3xht multi at 2.75 vdimm doing 2.5-3-3-7 1t
This can't be happening WTF I thought this ram was rated at ddr 550 at these timings and it cant' do below stock. This is bs man.
sorry people won't happen again.
Sorry but I did not know about the three letter word problem. I do know now and it won't happen again.
I bought the ram on advice and scores from everyone here and I know the ram is good and that is why I was surprised to get errors running it at 260 at the stock ddr 550 timings. I didn't mean to tick anyone off or badmouth gskill.
I think my proc is topped out at 2.6ghz. I used a divider on the ram and I could boot at 10x 270 but I would get an immediate restart and a bsod. I dropped back down to 260 x10 and went back with a 1:1 ratio on the memory.
My vcore is at 1.65 and my proc is stable but I get rounding errors after 5 minutes of p95 torture test. I upped the vdimm to 2.75 and still the same problem.
What could be wrong? This ram should do the stock timings on 260 like nothing or else I am totally stupid and rounding errors in p95 have nothing to do with memeory.
system specs:
3500+ newcastle
6800ultra not oced
2x512 gskill le
msi neo2 plat 1.4 bios
watercooled by dd tdx
vcore 1.65
vdimm 2.75
htt 260
ht 3x
2.5-3-3-7 1t command rate
Maybe I am just missing something.
FATAL ERROR: Rounding was 0.5, expected less than 0.4
Hardware failure detected, consult stress.txt file.
[Wed Jan 26 21:53:54 2005]
FATAL ERROR: Rounding was 0.5, expected less than 0.4
Hardware failure detected, consult stress.txt file.
ahhh yes I love when I corrupt my windows install!! So FUN!
Well I did it again!
A nicely corrupted system32 cofig and all 120 gigs of data I had are GONE!
Wowo I just love ocing on a raid array!! Well now that I have a fresh install I might as well go and play with this ram and corrupt it again :banana4: This timne all the important data is not there to lose.
I really get discouraged when this happens. 290 at stock ddr550 timngs and gskill nicely corrupted my windows install so I gather that it ain't doing those timings at that speed.
Well I guess it is back to gathering all the nice progs I had installed and all the movies I had. Probably will take me a few weeks but oh well. I am never using a raid array EVER again as a boot drive. I now have my two wd 160's on seperate drive letters and one of them is only for data. I am not going to corrupt another boot drive filled with all my goodies on a stupid oc mission.
I should have used memtest but that is for another time.
what do you mean recovery console?
Quote:
Originally Posted by Torin
^^ What he said. Make sure you are using the right SATA ports, 2 are not locked and that will happen everytime.
Like I said in the other thread, you should be testing DDR clock maxes at 8x or 9x multi, to eliminate your CPU limit and discover your mem limit.
And as the Jupiler said, don't use the recovery console, hit enter to install windows, then you will be given the option for automatic repair.
Don't get discouraged! Your memory has a long way to go, but you have to work out the other system issues to get it to max out.
I corrupted the system config file. I inserted the xp disk and booted from the cd and went through all the mtions of installing windows from the cd. When it asked to "repair" an install by pressing "r" that is what I did and immediately I was booted to the dos prompt c:> I tried this at least 10 times and everytime it would not repair anything. What could be the problem?
enter meaning install xp ?
Quote:
Originally Posted by Jupiler
This is normal if you press "r" the first time. It boots you to the dos prompt.
Don't press "r" the first time it asks you if you wanna repair XP. Just press enter and continue.
It's only the second time you have the option to choose "repair", that you have to press "r". (it will check for previous installations) This will repair you installation, and should normally not boot you back to the dos prompt.
Or does this happen the second time too? Because your post is a bit confusing.
If you press enter it installs xp. I do not recall it ever asking if you want to repair a "second" time after you hit enter to install the os.
So what you are saying is that you boot from the xp cd and wehn it asks to install or repair or exit you press enter to install xp. After that it will ask you to repair your install a second time and not go through with the actual installation from pressing enter.
If this is what you mean I only hit hit repair the FIRST time it askes after the initial boot up from the cd. I did NOT press enter like I was just installing the os for the first time. Dam I might have just wasted all my data for nothing if this is the case
:eek:
what is the board made for then?
Quote:
Originally Posted by skate2snow
I cant affirm that this is 100% true, but it is very possible. MSI K8N Neo2 may have a problem with NewCastle cores.
I have the same problem as you. My BH5 can do 255MHz memtest and on other rigs, but in windows I cant do over 220MHz 2-2-2-7 on this board. And, my WindowsXP Currupts so easily!
I am almost sure that the Neo2 as a compatibility problem with NewCastle. And I'm pretty sure that if MSI knows this problem, a BIOS could repair it.
If the board is made for socket 939 and the 3500+ is a socket 939 then why should there be a problem with the 3500+ which is meant to go in a desktop mobo like the neo2. My newcastle cpu works fine I just wanted a better oc outta it than I am getting. I could always just buy an fx-55 but since the fx-57 is gonna be out in the summer I will wait and then have the best amd offers.