Originally Posted by Weedvender
Report me if you want but I believe that is excessive for stress testing, unless the user needs mission critical applications to run flawlessly on an overclocked system. He should be fine with a general, 10 hour run of Prime and a small FFT run if he feels so inclined.
In my own personal experience combined with what I have read here on Overclock.net, I have come to learn that this is not excessive.
There was a time when I had only tested my overclock to be "9 hours stable" with the Small FFTs test. I had also only done about 5 passes in Memtest as well as about 2 hours of the Blend test. I hadn't done any linpack testing at this point in time that I am referring to. Back then, it was fairly stable, but I was still frustrated by problems. But I thought that I needed to reformat.
But one day I suddenly got the desire to go further and make my overclock pass at least a 12-hour Small FFTs test at minimum, then up to about 10 passes in Memtest, and then at least 6 hours of the Blend test. After that, those problems were eliminated.
But ove time I learned that they weren't eliminated; they were just significantly reduced so much that they became much less frequent. A few weeks after that, I got the desire to try linpack testing. So, I got LinX and eventually got it to pass 37 runs using all available memory (it locked up during the 38th run, but this was after many attemps to get it to exceed around 10 runs. After I did this, those problems were truly eliminated. It has been at least 3 months, and I haven't had one single problem due to instability. Not one
In addition to that, I see so many people saying things like, "but it's stable enough to pass 6 hours of the Small FFTs test, so why am I still seeing problems?" The solution to that problem is ALWAYS this "excessive" stress testing. Yes, always
Originally Posted by Pooping^fish
If only that made sense.
It stops certain types of overflow attacks by setting permissions on memory areas. A type of DEP, like nonexecutable stack.
Id say its pretty important, so keep it on if possible.
Data Execution Prevention, or "DEP" uses Excecute Disable Bit. If it's disabled, then DEP cannot function.
For more information on DEP, visit the following pages: