- Joined
- Dec 24, 2001
- Location
- Shasta Lake, California
It may well be that the ram is simply actually failing at that address. Either that part of it is bad or not as overclockable.
Welcome to Overclockers Forums! Join us to reply in threads, receive reduced ads, and to customize your site experience!
yea man thanks, is there anything you can tell me about the fact that it returns the error at the same "spot" in the ram? should i ask these memtest peeps that? i guess i should get the newest version then. and as for vdimm, im using mobo max of 2.85 and the ram is at about 208 which should be alright, i think the max it can reach at 2.85 v before you need to really go more is like 215-220mhz so i dont think thats it. what i will do however, is let it run the new memtet all day when i leave for work shortly, and like i said i wonder if its something to do with my ram ITSELF that makes the test return the same spot for errors
felinusz said:Because 3DMark will almost always lock within the first ten test run loops, if it’s going to lock at all, 4 hours of looped testing is a more than sufficient test for your machine. After four hours of looped testing, 3DMark has done all it really can, and isn’t going to catch any instability.
Mr. Cornell
So, obviously small FFTs and large FFTs are tests that both need to be run, if you are like me and hate Blend. Blend can eat me, I've already memtested the rig for 24+ hours and I'm trying to test the CPU, so could you please stop paging the entire OS to disk already Prime?
GUIDELINE EDIT
For CPU specific testing, a Large FFT Prime95 test is an alternative to the more "system-stress" oriented Blend test that runs by default. The choice is ultimately up to the end user - the Blend test is reccomended in these guidelines because of it's qualities as both a processor and system stress test.
Super Nade
You make an excellent point by bringing up the "catch all" situation. However, it would be nice if we could figure out a clear cut way to seperate hardware and software issues. Following your and gnufsh's lead on this matter, I'd like to propose a few simple tests.
* Majority of software errors are random in nature and require a particular trigger for them to occur. By downclocking the system, one could first verify if it is indeed a software error and upon further analysis, isolate the trigger. Once the trigger is isolated, we can continue testing minus one variable. A case to point would be data corruption if memory settings are too tight. The software failure persists even after hardware issue has been resolved and one could spend endless hours tinkering with the HW settings, without realizing its an OS problem.
* As gnufsh said, we could test our harware settings on another OS. Since I have 2 HDD's, I am going to use one HDD as my OC test drive. I would have both Linux and XP on the test drive. XP to ensure that my main HDD (with its own copy of XP) works, if the test HDD works and Linux, to zero in on inherent OS problems with XP.
felinusz
One thing this guide is completely devoid of is solutions to instability. This is intentional, as lots of material exists that will aid anyone running an unstable machine in getting it up to par.
felinusz said:CONCLUSION
I really, really hope that this little guide has been helpful.
If you’ve read through the entire thing, and found it educational, then it has succeeded. If you read only the beginning, and learned a little bit about the dangers of instability, then it has succeeded.
The big goal here is for everyone to be aware of the potential for stability problems, and know how to test for them properly. This is an unrealistic goal, but every person who learns something about stability, and proper, thorough, stress testing, is one less potential victim of stability-related disaster.
I’m thinking about adding a little bit of information on the philosophies of stability, the different schools of thought on the issue, and different courses of action people take. I’m also thinking of making a little list of some of the ‘lesser’ stress testing programs, and where to get them – Some of them are very worthwhile, if inferior substitutes to the ‘Big Three’. I’ve left out really specific stress testing, such as that designed to stress test your hard-drive. The ‘Big Three’ do quite a thorough job of testing an entire system if used properly, and together, and I don’t find it pertinent to clutter an extremely long, but basically simple guide like this with arguably unnecessary information.
One thing this guide is completely devoid of is solutions to instability. This is intentional, as lots of material exists that will aid anyone running an unstable machine in getting it up to par.
If I have missed anything important, worded something really poorly, or not gone as in-depth as I should have on some issue, please PM me.
If anyone has any questions or comments please do take the time to post, or drop me a PM.