I think it's a very good idea about testing this on a K8T800 PRO board with a winch. I have a AV8, but haven't bought the CPU yet because I have exams and am studying for them. I would be happy to test on Dec 20 :toast:
Anybody have one? ;)
Printable View
I think it's a very good idea about testing this on a K8T800 PRO board with a winch. I have a AV8, but haven't bought the CPU yet because I have exams and am studying for them. I would be happy to test on Dec 20 :toast:
Anybody have one? ;)
well, I will do some extensive testing over the next couple of weeks...
I have both the old version (with the single test) and V23.8 (with the 3 tests) and see what happens.
I have 3 3500+'s to use 1 winnie and 2 newcastles.. also have 2 Mobo's (1 Asus a8V and MSI Neo2)..
I was looking over at the GIMPS forums and versions 23.x Are optimized for The P4.. there is no code for the athon64 in Prime95. They are also having a problem with False prime numbers being reported on non-overclocked systems of all types (P4, AthlionXP and AMD64), so they could have some bugs in the code.
ALSO.... Remember that Memtest does not perform any Math calculations. it is Just reading and writing test patterns to memory and back. I have trashed my OS disk many a times finding Memtest never erroring, but Cpu was overclocked too high and trashed the OS...
Also, Make sure you get Prime95 ONLY from their website.. I have already found some copies that the files were corrupted, and would not run correctly at all..
Quote:
Originally Posted by Byron
Byron -
First of all overclocking results are going to vary - this is for issues with Prime at STOCK settings. If you are overclocking and failing prime95, then that problem is your own, the CPU isn't defective. My stability at 280 x 9 increased greatly once I cleaned / applied AS5 to my chipset as well. Just wanted to clarify that for people overclocking and not having prime stability is NOT the issue that we were getting at its the stock clocked prime failures.
hag6br
>>ALSO.... Remember that Memtest does not perform any Math calculations. it is Just reading and writing test patterns to memory and back.
And what do you think calculating something looks like at a lower level? Just like that.
>>there is no code for the athon64 in Prime95
A64 supports SSE2 so what's the problem? It might not run optimally, but it WILL run.
Please test the winch on the A8V and the K8N Neo2 @ stock. What week is it, btw?
ALL
Good news - local store (NCIX) has 3000/3200's 0441's in stock. I will be joining you in exactly 7 days.
What I am saying is that memtest only does memory reads and writes using a set pattern and compares them... Prime95 does floating point calculations and also uses Virtual memory (which memtest does not)..Quote:
Originally Posted by IvanAndreevich
ANd yes it has SSE2 code which he is still optimizing. Also, I was looking at his version info, and FFTS over 2048 have a time limit on them. If they do not complete in that time, they will fail.. (but do not know if this is implemented in the torture test).
My Winnie is a 0441. But I have a friend with a 0437 that I might borrow..
my Newcastles are 0427 and the other is an Original (bought it less than 2 weeks after they were released.
I am wondering on Prime95 though.. when they switched over to the New version systems that were Prime95 stable for 24hrs+ with the old version, Failed Prime95 within 15 minutes under the new version.
also, the version Presently in Beta is going to be a Huge memory Hog.. It is going to require 1GB+ of ram (both Physical and Virtual) to complete a run..
I havent tried priming at stock: A64 3000+ Winchester CBBFD 0442SPMW as you can see some of my results here
I have tried priming at 2520Mhz 280HTT 1:1 "Blend" and it fails after 3hrs or so...everytime i prime, always after 3hrs.
As you can see from my tests the pc is completely stable and has not crashed onces during testing and/or during everyday use/games.
I also had a 3200+ week 41 cpu that was in the same situation.
I will try and prime at stock speeds and report back.
Hey r2 :D
read up a lil futher, some one posted that by cleaning off the white goop underneath the MCP HSF and applying AS5, they could prime stable at a setting that would not have passed before...
Quote:
Originally Posted by jlccarv
That was me. Would crash priming at 278 x 9 sometimes 2 hr, sometimes 3 hr, now I'm at 280 x 9 now and primed 2 times over 12 hours - JOY JOY!
When i was using 3200+ week 41 i did apply as5 on the NB chip which made no difference to me.Quote:
Originally Posted by dnottis
This time i was experimenting as i applied the paste that came with xp-90 hsf (white goo) and i applied it to the NB and cpu (just wanted to compare to as5)
Ill tell you right now nothing compares to as5. However im going to remount the HSF and apply as5 and at the same time will fix up the NB with as5 is well.
Just currious, by why isnt AMD shipping 90nm CPUs in december?
over here the stock got empty in the first days of december, and dates on the different webshops now shows no stock b4 january...
Tip: try to LOWER the CPU frequency to 1200 MHz, 200*6, to see whether it fails, if it doesn't, then your CPU is defective, if it fails, it is something with the program or something is wrong with your system, and not the CPU (of course there could be problem with something another in the CPU, but not the operating frequency of CPU itself, maybe onboard memory controller).
:toast: :toast: :toast: :toast: :toast:
EVERYONE WITH PRIME95 FAILING AT STOCK !!! TRY THIS PLS ;)
OK, here's some more data into the equation:
Abit AV8 + 3200+ Winne Week 41 (0441MPMW)
260X10, vCore 1.55v = P95 stable depending on mem settings and timings (with divider definitely stable, no divider depends)
270X10, vCore 1.6v = SuperPI 31s, Benchs good, P95 blows immediately.
Sweet spot should be somwhere in between.
sorry for "late" responce...it was OCed...i will be doing stock testing on a new MSI mobo today...Quote:
Originally Posted by andyOCZ
o BTW Suma over on OC found P95 version: 2.46 which "seems" to be the latest versoin...? (DL from linked post)
just what we needed...more variables :p:
Fair enough andy, but if you can find more than one Winchester that can run Prime stably (and that's already been shown), then you have already shown it's not a problem with the software code, since all Winchesters are created using the same blueprints. Sure it's possible there are problems in AMD's manufacturing process with X week CPU and that could be causing some memory returns. I just want to make it clear that, unless there is some randomness in the stress test, the fault is not in the software.
Exactly, so no code specifically for A64's to go wrongQuote:
Originally Posted by hag6br
That's because of this: http://forums.extremeoverclocking.co...d.php?t=143717 :toast:Quote:
Originally Posted by v142
Ref
You're assuming that a CPU that is faulty @ 2.4 Ghz will not be faulty @ 1.2 Ghz, which is not necessarily true.
Quote:
Originally Posted by IvanAndreevich
Exactly - I see what he's getting at - but it's more important to Prime at STOCK to determine if a CPU is "defective" than to cripple it and run Prime95. It may prime fine at 1.2 Ghz and not be able to Prime at it's "stock speed".
I have a Winnie 0437RPCW and had no problems with Prime95 at 2313 (9.0x257) @ 1.575V. Now I keep it at 2250 (9.0x250) @ 1.475V with mem. @ 204. Made a 11 hour Prime at this speed and had no problems.
Quote:
Originally Posted by scorp
Interesting - heres a wrench in the week 37 theory -
what if it's only week 37 (and earlier) and MSI Neo2 Platinum boards?
Well...as I have mentioned before in this thread, my week 37 works fine too :), with 512MB RAM that is (2x256 DC in my case). 2x512 fails instantly. Scorp seems to run only one 512MB stick in single channel mode.
That's true :). I'll have to wait a little bit till I can get my hands on a pair of TCCDs :(.
I should try mine with 1x512 too :)
My system has been stable at 2.5ghz in dual channel. After turning off nv/ati speedup and removing the bad memory moduel (need to rma to consair) I got the sytsem stable up to 2.789ghz. that is prime stable for 7 hours along with 2 hours of 3d01 and super pi 32m. I dont seem to be having the prime bug... The only bug i have is that my chip doenst want to hit 2.8ghz!
BTW, im runnning on a week 41 3200 winnie.
scorp
Can you run the CPU and mem 1:1? Maybe it's a 1:1 glitch!
lsevald
..which strongly points to a $hitty memory controller.
MaxxxRacer
Seems like many newer CPUs don't have this problem.
Remember I started off with ny 3500+ week 37 and a GB K8NS Ultra-939 board. So the MSI only can't be true. I have nor read the whole thread but did anyone try a VIA board?Quote:
Originally Posted by dnottis
Ah, true - I forgot about that....Quote:
Originally Posted by andyOCZ