![]() |
|
|
#12 |
|
Aug 2002
Wroclaw, Poland
28 Posts |
There were so many errors during LL tests that there is a very small chance this results are correct (look at statistics published in this forum).
Dlugie pioro |
|
|
|
|
|
#13 |
|
"GIMFS"
Sep 2002
Oeiras, Portugal
2×7×113 Posts |
My machine is a Athlon XP 1800+ (Palomino core).
According to ASUS Probe, the CPU temp readings were, with a cooler from Spire, about 51ºC when P95 wasn´t running, and up to 57/58 when crunching. This was in (relatively) cold weather. In summer, with room temperatures around 28/29ºC, the mobo temp would reach 31ºC and the CPU well over 60ºC. In order not to stop P95 (the last thing in the world to do...), and before getting a new cooler, I had to underclock the CPU by roughly 25%. Then I got a Dragon Orb 7K rpm and even in hot weather I can run at normal (1533 MHz) speed, or even slightly overclock the CPU. The CPU temp never goes over 58ºC, and only in hot days.BTW, reckon it´s not an issue, for the max junction temp, for the CPU, as stated in AMD specs, is 90ºC! Obviously we should keep far from this value, but we shouldn´t get worried about temps in the high 50s. So far I haven´t had any errors whatsoever, even when the temperature reached 64ºC. I am running P95 since Jan/2002, 24/7 except for a couple of weeks break. |
|
|
|
|
|
#14 |
|
"GIMFS"
Sep 2002
Oeiras, Portugal
2×7×113 Posts |
johnymccarthy, why do you say You "can´t run P95 for more than 2 minutes"? A crash, or a frightening temp raise? 49ºC s a very reasonable value for an idle XP...
|
|
|
|
|
|
#15 |
|
Sep 2002
2×7 Posts |
Lycorn
I started a thread on the software forum entitled 'Upgrade and XP now crashes'. This explains were I was upto a couple of days ago. I looked into upgrading the BIOS, following a number of warnings I concluded that should the system freeze up on me during the process I could end up with no BIOS, and have to fork out for a new motherboard. I had a look at the ECS website (makers of my recent M/B purchase) and found a forum for my K7S5A, there was much talk about problems with memory, the board can use SDRAM or DDRAM (not both at the same time). When first set up I used one 256 SDRAM and all was OK, I then tried adding a 128 SDRAM and the the board became unstable, and ran very erratically. During this time the new Athlon 1900+ CPU began to fail. To cut a long story short, Exchanged the fault CPU. Removed the 128 SDRAM Re-installed XP Transfered files from my old HD (now slave) Installed Prime95 v22.9 All my old programs were fine, until I set Prime95 running and the longest it would go for was around 10 minutes! Today I went out and purchased 512 MB of DDRAM, installed it and Pime95 runs like a dream. My problem now is - why has everything else slowed to a crawl. System monitor shows CPU usage at 100% with prime running, XP takes about 10 minutes to shut down. I'm at work now, have left Prime running and have downloaded Taskinfo to floppy. Lets see what tomorrow brings. John |
|
|
|
|
|
#16 |
|
Sep 2002
11710 Posts |
This might be a long shot, but were you factoring at the time? If you set your computer to use 90% of your RAM, during the initial P1 factoring, you would experience a HUGE hit in performance.
|
|
|
|
|
|
#17 |
|
Aug 2002
2×5 Posts |
Try setting Options->Preferences->Iterations between screen outputs: to something more reasonable, like 100. On my systems it defaults to some absurd number like 1000 and on a 2.5G P4 it was 10000.
![]() When I set this lower, Prime95 responds quicker to the system shutdown command. Dan 8) |
|
|
|
|
|
#18 |
|
Aug 2002
23 Posts |
Well, glad to see you got it up and running...although it sounds like it was not an inexpensive fix.
I set most of my clients to report every 100,000 iterations. I figured the less time it spent writing to the screen, the more time it could spend crunching - although it probably wouldn't amount to much anyway. Even with it set that high though I've never had it slow down my system. AH! Wait. Was it trying to connect to the broken Primenet server? That always borks my boxes..... |
|
|
|
|
|
#19 |
|
Aug 2002
2×3×53 Posts |
It's probably because Winblows XP doesn't know how to delegate work load.
If you are only running XP because it is the newest wincrap OS, don't. I can run any Winblows OS or Linux and i choose 2K. Why, it does everything nice. No compatibility issues, knows how to delegate priorities and doesn't crap out like the rest. I have 6 systems running the ECS K7S5A mobo with DDR ram, all are running Win98SE. Of course these are dedicated crunchers so no other programs interfer. It is not the board, it is the OS. |
|
|
|
|
|
#20 |
|
Aug 2002
23 Posts |
FYI: I'm running Win2KSP2(and SP2 only) on my boxes. Of all the Windows versions I've run this one actually doesn't make me want to rip BillG's nipples off with a rusty pliers. :)
I had thought though that 2K and XP were close enough code-wise(besides the extra eyecandy and M$ sponsored trojans) that apps woud run about the same on both OS's....... |
|
|
|
|
|
#21 |
|
Aug 2002
207228 Posts |
If I didn't need to play games, or use USB, I'd be using NT4... I love that OS... It is nice and fast, easy on memory and stable... Plus, everything is in the "right place"...
|
|
|
|
|
|
#22 |
|
Aug 2002
2·3·29 Posts |
By the way, I think a program called memtest86 is even a better program to stress test memory than the prime95 torture test. For me it catches errors that Prime torture didnt catch.
http://hcidesign.com/memtest/ |
|
|
|
![]() |
| Thread Tools | |
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Interesting GPU heat issue... | nucleon | GPU Computing | 20 | 2012-01-29 19:25 |
| Four heat seeking missiles | mfgoode | Puzzles | 51 | 2007-01-10 10:02 |
| Heat problems | michaf | Sierpinski/Riesel Base 5 | 3 | 2006-07-04 21:11 |
| Opertons x52, x54 (3000 CPUs) heat = floating point errors | dsouza123 | Hardware | 5 | 2006-05-01 17:05 |
| Keeping the Heat down at Home | outlnder | Hardware | 61 | 2003-02-15 03:12 |