- Joined
- Apr 20, 2004
- Location
- JAX, Mississauna
Okay we have been given a mission for this thread. The reason for starting this thread is still true and outlined below. But we have been asked to try for a consensus as outlined just below. Thank you.
Can we in this thread develop a basic set of guidelines as follows:
1. What is the recommended quick test method to check an overclock for stability (less than an hour of testing)
2. What is the recommended good test method to check an overclock for stability
3. What is the extreme recommendation to ensure you almost definitely won't see a crash under almost any condition
I feel some of the three points above will overlap, but we should do our best to fulfil the three criteria as outlined above. The problem with trying to develop such guidelines is personal bias. I have it. We all have it. In those instances I have to think out of my box and over at someone else's computer desk. RGone...ster.
Dear Moderators:
You may feel free to position this thread in a more appropiate area if you so deem. Thank you.
Right now viewers per forum:
Cooling 75 viewers
Cpus 175 viewers
Motherboards 127 viewers
Video Cards 111 viewers
Storage 65
Memory 40
Display and Sound Technology 65 viewers
The rest of subforums under "Hardware" are on average showing less than 30 viewers.
The topic of how to do Stability Testing and probably a hot topic has been brought to my attention. Do we as posters have any responsibility for what we post? Looking at the numbers of viewers as shown above, I think we do have at least a modicum of responsibility to ensure that if we are posting an opinion that is inline with the general community; that we make our statements with a clear disclaimer that I am posting 'my personal opinion". We have far more viewers than posters. Far more viewers than 'helpers'. So I try to ensure my personal opinion is not going to be too great an influence on those that are in the viewer community, where they may have no idea about where I am standing when I voice an opinion.
Also open to discussion is the idea that my latest opinion, may be the new wave of technology and procedures. There is no sense in remaining in the past if there are newer and better procedures that we all might have consensus about.
LINK >>
What prompted me to start this thread was this thread and posts in it.
So I see that the idea that Prime95 is over-rated is set forth as an opinion as it likely should be.
I can go back to my first experience with Prime 95. A forum I was a member of was doing some overclocking on a particular motherboard series. Our overclock submissions had to include captures of validations including 8 hours of Prime95. WTH? Prime who? Prime Rate? Prime my pump?
When I threw Prime at my glorious overclock...well my stuff was a failure. Deeyam P95. I was now sitting on the floor in the footspace of my computer desk. Shaken and feeling beaten.
The rise from the ashes of my first experience with Prime95 was one of the experiences of my lifetime. I learned more about overclocking in general with my quest to conquer my Prime95 failure, than I likely ever could in any other process. I learned what was needed to push my rigs in an over-speeded context and remain what was deemed stable by Prime95 and my peers at the time. I learned what relationships of hardware and software mattered. I mean if I was really going to do calculations that might unearth a real prime number, then I did not need a computer that could not pass Prime95 testing parameters.
So have we gone beyond the days of Prime95 and perhaps many of our tests or procedures for stability testing? Is it time to come to a new consensus for stability testing?
I don't know. I know I went kicking and screaming toward testing with programs like Prime95. After much perceived hardship, I came to have a fond if tempered affection for Prime95. But is it time to change? Do we have a new and better way? Again I do not know. That is what this thread is all about. Have we accrued enough valid information to perhaps develop a new consensus? I still don't know and is the reason for this thread. I suggest that opinions are like noses in that we all have one. Make your postulations with some valid background data.
You are now returned to your regularly scheduled programming. RGone...ster.
Can we in this thread develop a basic set of guidelines as follows:
1. What is the recommended quick test method to check an overclock for stability (less than an hour of testing)
2. What is the recommended good test method to check an overclock for stability
3. What is the extreme recommendation to ensure you almost definitely won't see a crash under almost any condition
I feel some of the three points above will overlap, but we should do our best to fulfil the three criteria as outlined above. The problem with trying to develop such guidelines is personal bias. I have it. We all have it. In those instances I have to think out of my box and over at someone else's computer desk. RGone...ster.
Dear Moderators:
You may feel free to position this thread in a more appropiate area if you so deem. Thank you.
Right now viewers per forum:
Cooling 75 viewers
Cpus 175 viewers
Motherboards 127 viewers
Video Cards 111 viewers
Storage 65
Memory 40
Display and Sound Technology 65 viewers
The rest of subforums under "Hardware" are on average showing less than 30 viewers.
The topic of how to do Stability Testing and probably a hot topic has been brought to my attention. Do we as posters have any responsibility for what we post? Looking at the numbers of viewers as shown above, I think we do have at least a modicum of responsibility to ensure that if we are posting an opinion that is inline with the general community; that we make our statements with a clear disclaimer that I am posting 'my personal opinion". We have far more viewers than posters. Far more viewers than 'helpers'. So I try to ensure my personal opinion is not going to be too great an influence on those that are in the viewer community, where they may have no idea about where I am standing when I voice an opinion.
Also open to discussion is the idea that my latest opinion, may be the new wave of technology and procedures. There is no sense in remaining in the past if there are newer and better procedures that we all might have consensus about.
LINK >>
What prompted me to start this thread was this thread and posts in it.
RGone said:1. You have a C2 stepping processor. Not as good as a C3 stepping in general. After all you said you had it a pretty long time.
3. If Prime95 passes and we can see the Screen capture of HWMonitor we will know where the board stands and knowing you have an upward unlocked processor you can bump the muliplier to 18 from 17 and Prime95 again for at least 2 hours. If Prime95 fails immediately...then up Vcore 0.05 and retest.
Need to see Screen capture of the HWMonitor as it was running during the 2 hour Prime95 @ 18 multiplier.
4. When Prime95 is fully stable at the 18 multiplier for 2 hours...you can test the 19 Multiplier. Need to see Screen capture of the HWMonitor as it was running during the 2 hour Prime95 @ 19 multiplier.
storm-chaster said:I think prime is overrated. Use the integrated system stability test within everest or aida64, just as effective. Like breaking in a new engine, you wouldnt stress it to the limit or 8000rpm redline for 17 hours, nor would you see 100% load on your cpu for a sustained 17 hours. Sure it can prove that your system is bulletproof, but if it fails after 3 or 4 hours it doesnt mean your system in its overclocked state is unstable. To each his own. I've seen many overclocks over the years that pass prime for a while, but eventually fail. In real life you never see BSODs or have any reliability problems. but again, just my experience.
So I see that the idea that Prime95 is over-rated is set forth as an opinion as it likely should be.
I can go back to my first experience with Prime 95. A forum I was a member of was doing some overclocking on a particular motherboard series. Our overclock submissions had to include captures of validations including 8 hours of Prime95. WTH? Prime who? Prime Rate? Prime my pump?
When I threw Prime at my glorious overclock...well my stuff was a failure. Deeyam P95. I was now sitting on the floor in the footspace of my computer desk. Shaken and feeling beaten.
The rise from the ashes of my first experience with Prime95 was one of the experiences of my lifetime. I learned more about overclocking in general with my quest to conquer my Prime95 failure, than I likely ever could in any other process. I learned what was needed to push my rigs in an over-speeded context and remain what was deemed stable by Prime95 and my peers at the time. I learned what relationships of hardware and software mattered. I mean if I was really going to do calculations that might unearth a real prime number, then I did not need a computer that could not pass Prime95 testing parameters.
So have we gone beyond the days of Prime95 and perhaps many of our tests or procedures for stability testing? Is it time to come to a new consensus for stability testing?
I don't know. I know I went kicking and screaming toward testing with programs like Prime95. After much perceived hardship, I came to have a fond if tempered affection for Prime95. But is it time to change? Do we have a new and better way? Again I do not know. That is what this thread is all about. Have we accrued enough valid information to perhaps develop a new consensus? I still don't know and is the reason for this thread. I suggest that opinions are like noses in that we all have one. Make your postulations with some valid background data.
You are now returned to your regularly scheduled programming. RGone...ster.
Last edited: