Quote Originally Posted by CrazyNutz View Post
I don't buy what you are saying "software/OS is effecting the stress test"

This is a quote from the author of OCCT:

bbz_Ghost : Stability testing, CPU-wise, can be done under any OS. Let me explain : in stability program, we address the CPU directly, through assembly code. We control almost everything. I'm developing under windows just to get the benefits of a few Windows procedures, be able to produce a nice GUI, etc. The only thing that can break my program is a problem with Windows's Task sheduler (and that's really unlikely). Even if it runs under Windows, if OCCT reports an error, it *does* mean the assembly code itself detected an error. So even under Windows, you get pretty good results
I find the "you want your computer to be stable under windows" remark really true too
And it's much more convenient as well


This is a little out of context so you should read the whole thing here:
http://www.hardforum.com/showthread.php?t=1145172

I too am a programmer, and I know that unless you are making windows API
calls and such windows is very unlikely to have an impact on the stability of your application (and unless some driver, or windows bug brings the whole system crashing down). Stress testing apps should have they own discreet
stress testing routines to run, and not rely on the os API's.
I said I need to research it and see if that's the case. That a damaged OS may be the problem with that drive, but that I doubt that there's much different from drive to drive.

I too am a programmer and I know exactly why you would have your doubts.

Let's try something constructive and time permitting I'll test and report back. Knowing my setup, and assuming I can duplicate what happened earlier with passing on one drive and not the other, what test method could prove to you there's no difference from drive to drive? I can test out the warm up theory as well if you'd like.

Lets work on it.