• Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.
  • The forums have been upgraded with support for dark mode. By default it will follow the setting on your system/browser. You may override it by scrolling to the end of the page and clicking the gears icon.

Passed Prime95 but not OCCT???!

Hvale2k5

New Member
Joined
Feb 19, 2008
Messages
99 (0.02/day)
Location
VA
System Name Fist gaming system
Processor AMD Phenom II x2 BE 555(unlocked x3 OC at 3.5 stable)
Motherboard Asrock 880 GXH/3.0USB
Cooling Zalman 9500a
Memory 4GB G.skill DRR3 (PC1600) 9-9-9-25
Video Card(s) ATI Radeon HD5770
Storage WDC (500)
Display(s) Viewsonic LCD 22inch
Case Rosewill Challenger ATX Mid Tower
Power Supply Cosair 650w
Software Window 7 Ultimate
I know its only 4hrs of *Blend*prime95 but the pc was fine, didn't shut down or anything.

After prime95, i want to test it again /w occt 3.1 and it would restart after 10mins in....:banghead::banghead:

6promu.png
 
Well, it's very simple. You never passed prime.


If you didn't run it until each FFT size has been run, and it starts back over again, the testing really isn't done yet. Takes about 9.5 hours @ 3.6ghz, on AMD quads.
 
Cadaveca makes an excellent point about P95 and it's something I never realized either until he turned me on to it in one of my own "problem" threads.

This may not be relevant depending upon your temps, but OCCT linpack is much more intense than P95 and will generate higher max temps. However the most intense utility I've found thus far is IBT (Intel Burn Test, and another hat tip to Cada).

IBT not only gives you the highest temps, but it does not cycle to the same degree as OCCT - which goes from about 17% for long intervals before returning to 100%. IBT will give you range of temps but it is a much narrower range with the low end being about the same as the max you get from OCCT.
 
What is the standard OCCT test made of? I just know in an hour with large data sets it consistently finds issues IBT doesn't.
 
IBT is not as accurate as people lead it to be. i have ran IBT/Lin-x for 20 passes then just 5-10 min after siccess crashing during web browsing, movies, or games. honestly i only use stress tests now to find my maximum temps because i have noticed more and more you can pass stress tests and then crash during normal use.
 
IBT is not as accurate as people lead it to be. i have ran IBT/Lin-x for 20 passes then just 5-10 min after siccess crashing during web browsing, movies, or games. honestly i only use stress tests now to find my maximum temps because i have noticed more and more you can pass stress tests and then crash during normal use.

Then you too, are not testing fully. For me, IBT must use all available ram. ALL. 20 passes at proper settings will take about 2.25 hours...I run IBT for a minimum of 12 hours.

That means, no, you cannot just start it with max settings...you'll probably only get 93% ram usage. You need to start a max test...let it load teh ram up, maybe finish an iteration, and then stop it...wait for ram to free itself back up...and then start the test again. Maybe you gotta do this once...maybe you gotta restart 5 times...maybe the 3rd time you get lower mem available, and can only get more by a reboot...


The way I look at/approach stability testing has evolved over the years, as cpus have evolved too, and one of the biggest changes as of late with cpus, is IMC's, and much larger caches.


But these tools...P95, OCCT, IBT...have been around for years(I think IBT is newest). How could they be designed to test today's platforms, when they weren't available back then?


So, anyway, these tools were really designed by a single person, kinda, who developed the program on a specific platform. So, for me, I think that way...this tool is only designed for THAT specific platform.


So, if I do not have the same platform, I have to use custom settings to make it a match for my platform.


And I don't use ONE tool. I use 'em all. If anything fails, I do not consider my system stable, even if I know that I'll never see a crash during my "normal" usage.


Probably 95% of people I've explained this too say:

"WHAT! That takes too long...I don't have time for that".


Real stability testing isn't benchmarketing. It takes time...and lots of it. It's not short, it's not fun, and it's a big waste of electrical power.

But for me...that's what it takes.
 
Last edited:
Sorry, but linpack testing goes back to the 70's, I think IT is the older of the group;)
 
agreed, but it does utilize Linpack correct?
 
agreed, but it does utilize Linpack correct?

I don't know.:laugh:


Actually, yeah, pretty sure it does. But I do think it is a relatively new Linpack version...I'm using the May 2010 IBT, but there's no version info on the linpack packages.
 
yeah i do a shitload of passes maximum ram usasge, and i do the "xtreme burning mode" its far more stressfull then regular ibt. but it there are times when it just hardlocks or bsod after successfull tests. idk why. i usually add vcore/vtt or lower clocks and go agin.
 
Back
Top