First, please excuse my questions as I've just come to this topic - and I have some serious eye problems so I've only been able to glance over all 105 posts.
You have instructed Driver Verifier to check all non-Microsoft drivers
Yet Microsoft drivers are showing up as the cause in the Driver Verifier enabled memory dumps.
This, to me, means that the 3rd party drivers aren't at fault.
If that's the case, the only things left are: Windows, compatibility issues, or hardware
Now, a discussion about Driver Verifier (DV).
DV is used to stress drivers and (hopefully) cause them to crash and spit out a BSOD error message that names the faulty driver. But driver developers don't have to follow Microsoft's rules for drivers development - so we can't assume that all drivers will react equally to DV.
In short, what if you have a driver that's not quite up to Microsoft's standards - but it works OK under normal circumstances? In that case, the driver can crash under Driver Verifier, but won't necessarily crash under normal usage.
So, use Driver Verifier if you're having crashes. Once you've finished with the crash diagnostics - turn Driver Verifier off.
I don't think that Windows is the issue.
But there are issues with Win7 that aren't present with the other OS's (in particular, I've seen RAM issues in the Asus P5 series of boards that can only be explained by that).
So, we're looking at how your system handles RAM
We're looking at your video card and it's drivers
We're looking at your power supply - and how well it provides power to the video card
and we're looking at the mobo/CPU in case of issues there.
FIRST
To test RAM, please run these two free tests according to the instructions:
Memory Diagnostics (read the instructions at the link)
Please run the test for a minimum of 7 passes.
and
Prime95 Setup:
- extract the contents of the zip file to a location of your choice
- double click on the executable file
- select "Just stress testing"
- select the "Blend" test. If you've already run MemTest overnight please run the "Small FFTs" test instead. (run all 3 if you find a problem and note how long it takes to error out with each)
- "Number of torture test threads to run" should equal the number of CPU's times 2 (if you're using hyperthreading).
The easiest way to figure this out is to go to Task Manager...Performance tab - and see the number of boxes under CPU Usage History
Then run the test for 6 to 24 hours - or until you get errors
(whichever comes first).
This won't necessarily crash the system - but check the output in the test window for errors.
The Test selection box and the stress.txt file describes what components that the program stresses.
More details on the use of this test:
Torture test your CPU with Prime95