FYI I got the *exact* same rounding error. :oQuote:
Originally Posted by andyOCZ
3500+ Winnie
Prommy Mach 1
OCZ Plat rev 2 2-2-2-5
250fsb
HTT x4
My winnie is being replaced by a newcastle due to cold shutdown error. :(
Printable View
FYI I got the *exact* same rounding error. :oQuote:
Originally Posted by andyOCZ
3500+ Winnie
Prommy Mach 1
OCZ Plat rev 2 2-2-2-5
250fsb
HTT x4
My winnie is being replaced by a newcastle due to cold shutdown error. :(
Hardly "exact" when it only mentions the rounding error returned 0.5 instead of something closer to 0.4 :stick:Quote:
Originally Posted by r00tcause
If you both get something exactly like rounding error 1.25455784558 then it's either coincidence (highly unlikely considering the precision levels), or there is something wrong with Prime95's coding, which is also highly unlikely since the programmers themselves on the Prime95 forum have clearly checked this and explained the problem, ie not in the coding.
or there is something wrong with Prime95's coding, which is also highly unlikely since the programmers themselves on the Prime95 forum have clearly checked this and explained the problem, ie not in the coding.
This thread has gotten very long and its hard to find any of the informative bits heh. You mention Prime95 forums (which I cant seem to find).
Do the Prime95 coders actually acknowledge a problem with the A64 and P95?
Although it's certainly possible for the A64 archeteture to be a little different and maybe not perform some of the same ops exactly the same (especially if its dropping from 64b to 32b precision), i can imagine how this would affect Prime95 only when CPUs are running at certain speeds.
Pi and Prime95 routinely fail while im trying new overclocks. Pi generally fails when the CPU is too high, and Prime95 is more sensetive to memory issues (and more advanced OP codes maybe). However, I can correct these faults by increasing voltages. That makes me think its not a logic error but a standard overclocking error. Prime95 will just pick up on different things that dont make other apps crash. Its handy to have several different apps to test stability. I've written my own burning app which checks math against preformed data (its extremely similar to Pi tho so I just use that).
I'm not really forming an opinion either way, but to me it seems that its not a Prime95 flaw on my system (av8, 3500+). Prime95 is stable even at very high FSBs on my system as long as the system itself is stable. I havent gotten any repeatable errors.
Prime95 warms up the CPU a lot higher than Pi tho, ive noticed that.
That still doesn't explain why PRIME95 fails at stock speeds. And why in single channel mode it works perfectly and fails in dual-channel mode (at least my chip does this).
It's never failed at stock for me in dual-channel. If it was a coding problem, the problem should be fairly consistant and reproducable at the same spot?
My week 37 also stinks pretty bad.Quote:
Originally Posted by andyOCZ
The max OC i get is ok.. (2.6 GHz at 1.7V)... but its not phenomenal... especially b/c I have it watercooled... it still fails prime95 at stock sometimes... not always, though.
I'm thinking of RMAing it. The mem controller on it really weak and has problems pushing my EB RAM.
Hopefully this will be fixed with the newer CPU week... like 50
I just got a new system and it will freeze while running prime 95 (week 44 winnie and neo2 plat.). It's got 1 stick 512 of ddr400 in it. What gives? Should I rma my chip or my mobo or both?
my ADA3500DIK4BI CBBFD 0436XPBW on a MSI Neo2 Plat. is prime stable at stock (2.2Ghz @ 1.4v) and overclocked to 2.3. It's been my experience that Sumout or Rounding errors are due to undervoltage on the cpu. usually a slight bump will solve that.
http://www.xtremesystems.org/forums/...id=22747&stc=1 :cool:
Quote:
Originally Posted by cardnut99668
you should do neither. Its nothing to worry about aslong as your comp doesnt give you anymore problems
1st of all, Wrong Thread. could be a weak power supply.Quote:
Originally Posted by cardnut99668
I've got a 480w thermaltake. Is that too weak? I wasn't sure where to put this. So should I try disconnecting stuff and see if it passes?
Not slamming Thermaltake, but most of thier PSU's are rated too high IMHO. Try running just the basics. A hard drive, CPU fan and nothing else.Quote:
Originally Posted by cardnut99668
I'll give it a shot.
I disconnected everything except the raptor w/ the os, 1 optical drive, my 6800gt gs, and the mobo and it's priming fine. Does this definately mean it's a psu issue? Should I go with the OCZ powerstream 520?
The 520w Powerstream should fix you up fine. 600w is more future proof, but more money. Bummer about your PSU. As you found, with A64 the PSU is critical!
Guys if you have a winni that fails prime could you list the full part and model number for your CPU...Especially the 3rd line of test on the cpu package.
Im helping narrow down if there was an issue with specific weeks cosed etc.
Since I am testing 'full' load (ZoneAlarm security + AV, acoustic edge sound pannel, etc). Other than that normal blend has been running for ...(looks at timer on main PC) 14 hrs @ his settings in sig. :banana: Gonna let it run until the morn (crosses fingers) when I have to 'cleaning lady' safe the PC for the day.
That sounds like a purely-processor-core related problem.Quote:
Originally Posted by saaya
I would check the processor temperature. It's likely overheating.Quote:
Originally Posted by cardnut99668
I tried to read most of the thread and absorb the most important info, I'm pretty sure I got the gist of it but probably missed some details so feel free to correct me. Having said that, I guess my results might kinda throw a monkey wrench in the whole Winchester/week 37 theory, sure glad I got lucky if some are really bad though. This chip was bought in November, take a look:
http://img120.exs.cx/img120/9890/maxstableoc7oy.th.jpg
http://img31.exs.cx/img31/144/maxsta...lftt2qf.th.jpg
I'd crop but I figure some might wanna take a look at the temps or whatnot and I'm too lazy to edit 'em and re-arrange it all. :p: In any case, first one was of my first test with a clean install after settling on 2.3GHz for now (more on that later). As you can see, Prime95 (blend) + looped MP3 + rhtdribl. See sig for system info, timings, vcore, etc.
Second one was a small FTT run as suggested here, it did put the CPU at 100% util which Blend alone didn't. However it didn't hiccup once, had HL2 DL'ing in the back even. The code on my A64's IHS reads as follows:
ADA3000DIK4BI
CBBFD 0437WPHW
1093569I40169
assembled in Malaysia
I mentioned I settled on 2.3GHz for now... Not very high, I know, 'specially by the standards you guys 'round here set. Alas, at 2.4GHz not only was it not Prime95 stable but it just wasn't stable while idling in Windows... It'd just lock up without any errors, rather quickly too. It's odd and I haven't been able to find out why. I've tried just about every setting/timing configuration.
The only things I haven't checked out at 2.4GHz are A) running at 1.4-1.45v vcore (I tried up to 1.65v and it lasted hours as opposed to minutes but was heating up too much) B) 4x HT multi as opposed to my 3x (most tell ya to stay under 1,000 but some have reported more stability actually going over 1k so worth a try).
My temps aren't the best (tropical island, concrete walls, no A/C, oi) but they're not terrible and they weren't any higher at 2.4GH than 2.3GHz so I doubt that's the prob in getting to 2.4GHz. My 12v line is usually pretty low (11.5-ish) and there's not much draw on it. I dunno if my PSU's just weak or the 2-pin Panaflo 92 L1A is drawing too much, I've gotta try having it on a molex just to make sure. Gotta check under the mobo NB HS too...
Anyway, I mention all this just in case it has any relevance, may help some, or in case anyone has any ideas that might get me 2.4GHz... But as you can see there's some week 37s out there that have absolutely zero issues with Prime. I used the latest version straight from the project site.
Thanks to ImageShack for Free Image Hosting
It was never proposed that ALL week 37's were bad. Other weeks up to 41 seem to have similar issues, but fewer in number. The reality is that the cores get made, then assembled and dated, so the cores surely get distrubuted over a more than one week.
If you have a good one, we are all happy for you. :) Thanks for the input.
We have a similar thread going over on the ocforums:
http://www.ocforums.com/showthread.php?t=348124
This problem is most bizarre, and needs clearing up - the Prime95 problems could well be indicative of bad processors that need to be returned. We have established that this is likely a hardware issue, and for what it's worth, I have sent an email to AMD about this.
Having corresponded with AMD several times before, I did my best to word things in order to best guarantee a helpful response. In particular, I want to know if owners of these "bad" chips should be RMAing.
I did not mention the main date stepping (0437) in my email, as this has proven to be inflammatory in my past correspondences: for whatever reason, AMD does not give answers to people who write like overclockers, or imply overclocking, and general stepping curiosity.
I will be sure to post any response to this email, both on the ocforums, and here.Quote:
My Email to AMD
Recently, a large number of Athlon64 processors have proven to have stability issues right out of the box, at 'stock' clock speeds.
Users are finding that their Athlon64 processors (particularly "Winchester" core Athlon64s) are consistantly unable to pass Prime95 CPU stability testing at stock speeds and voltages, even with AMD approved processor heatsinks, and as a group, are wondering why this stability issue exists.
Should these processor owners be returning ("RMA") their apparantly faulty processors? Does AMD know about the source of this problem?
Is there a specific telephone hotline that these users can call for assistance?
Thank you for your time,
You folks are doing some great work over here - good stuff! :)
I will point AMD to this thread, I will get them to look at OCforums also
Quote:
I will point AMD to this thread, please also post a link to the thread over at ocforums so they can go look there.
Here it is again :):
http://www.ocforums.com/showthread.php?t=348124
I have received the first automated response to my email. Basically, it details the processor owner's warranty rights, and gives a telephone number that all of you can call for help :rolleyes:. Typical, I guess my email wording was a little bit too rinky-dink.
I resent it as "unresolved", hopefully we'll get a run-down on the actual source of the problem soon.
I'm wondering, you Neo2 users... does turning "DRAM Drive Strength" to weak do anything to your Prime95 stability?