Thanks - I will give that a go :)Quote:
Originally Posted by ahmad
Printable View
Thanks - I will give that a go :)Quote:
Originally Posted by ahmad
That's what I was thinking - however, I know people that have no issues with Vista 64 and SuperPi - I can run SuperPi 1M no problem :rolleyes:Quote:
Originally Posted by RejZoR
I`ve already tested 600% coverage, no errors :up:Quote:
Originally Posted by squito
I am getting same thing here now I looked.. It doesn't start with Windows though in msconfig?? or services that I can see??Quote:
Originally Posted by KoHaN69
Did you try running Memtest86+ overnight? It might be because of memory instability.
No I can run your test fine. I thought about it and this is just saying the program took awhile to open that's all it isn't actually talking about it starting with windows.. I just wasn't thinking before posting sorry bout that. I love your program it is awsome.
same here :)Quote:
Originally Posted by WaterFlex
I give that a go tonite :cool:Quote:
Originally Posted by AgentGOD
Lol, I used it on my Eee PC and it only got up to 66C. Not bad. :)
There might be a bug then with spi in 64bit OS, doesn't make sense that you pass this, prime, and HCI and spi fails.Quote:
Originally Posted by squito
squito, have you tried hyper pi with the compatibiltity options checked? http://www.xtremesystems.org/Forums/...d.php?t=176904
vista's audio service and themes have been found to cause problems with super pi
Option 1: maximum memory, is obviously the best test for RAM, but how about when I want to test vcore, NB, VTT (GTL)?
And Is 10 passes good enough, for a indication for daily stability for gaming and some encoding? Or how many passes do u guys recommend?
Looking good overnite :up:
Well, it could be anything if you think about it - this is a computer we're talking about :)Quote:
Originally Posted by ahmad
It could be that even though I took great pains not to fubar my Vista installation, that's exactly what happened :confused:
That's the plan for tonite :)Quote:
Originally Posted by Pyr0
I read about disabling vista's audio service and themes - didn't work for yours truly - and I've personally seen it not be a problem on a bunch of other systems :rolleyes:
HyperPi actually when ran runs times slower then superPI .. now what youc an do is open HyperPi and check off the three items that Vista needs to be checked off for Super Pi to work and then leave it OPEN and then open Super PI and run it ... :)
Works every time.... and once done . uncheck those three things and close Hyper Pi and then do your screen shot of Super Pi ... :)
After playing some more, I found the following problem. IntelBurnTest will not run in maximum stress test with the page file disabled. So if you are getting this error, turn your page file back on for testing. It frees up more memory that is reserved by the OS. Turn it back off after testing.
IMO 50 passes is a good test, probably 40 is acceptable too, but I have failed between 20 and 30 tests before so I would recommend going over that to be perfectly stable. 10 is a good start when when messing with settings, but before you finalize 50 is a better test.
hmmm I passed 20 passes @ linpack but prime small failed within 2 min.... could it be because of XP32bits? I just got 2GB RAM tho....and it should utulize all RAM?
I also am BurnTest stable times 20 iterations but fail out in Prime95 in less than a minute. Very modest overclock from default 3.2 GHz to 3.4 GHz. I am running 64-bit Vista. Not sure what's up here. Voltages are the same running both BurnTest and Prime95.Quote:
Originally Posted by CERO
Updated to v1.6
- Added updated 32-bit and 64-bit Intel(R) Linpack binaries from Intel(R) [August, Official]
#EDIT:
Updated native 64-bit WinPE version as well.
does it pass memtest86+?Quote:
Originally Posted by CERO
Thank you very much - this program rox :)Quote:
Originally Posted by AgentGOD
I love this program, but is there a chance it pushes a CPU to an unrealistic point which is unlikely to ever be reached in regular use?
Just a thought. Don't bite me!
Silent data corruption is always a hazard... this is one step closer to error-freeness.
If the numbers in <norm> dont match, what does it mean? Unstable memory and CPU?