Constant BSOD (WIndows 7 32-bit)

If all of the Prime95 tests were run on "Blend" - then it won't tell us much.
Here's the Prime95 results file:

Code:

[Feb 21 23:08] Worker starting
[Feb 21 23:08] Setting affinity to run worker on logical CPU #1
[Feb 21 23:08] Beginning a continuous self-test to check your computer.
[Feb 21 23:08] Please read stress.txt.  Choose Test/Stop to end this test.
[Feb 21 23:08] Test 1, 4000 Lucas-Lehmer iterations of M19922945 using FFT length 1024K.
[Feb 21 23:09] FATAL ERROR: Rounding was 0.5, expected less than 0.4
[Feb 21 23:09] Hardware failure detected, consult stress.txt file.
[Feb 21 23:09] Torture Test completed 0 tests in 1 minutes - 1 errors, 0 warnings.
[Feb 21 23:09] Worker stopped.


[Feb 21 23:08] Worker starting
[Feb 21 23:08] Setting affinity to run worker on logical CPU #2
[Feb 21 23:08] Beginning a continuous self-test to check your computer.
[Feb 21 23:08] Please read stress.txt.  Choose Test/Stop to end this test.
[Feb 21 23:08] Test 1, 4000 Lucas-Lehmer iterations of M19922945 using FFT length 1024K.
[Feb 21 23:10] FATAL ERROR: Rounding was 0.5, expected less than 0.4
[Feb 21 23:10] Hardware failure detected, consult stress.txt file.
[Feb 21 23:10] Torture Test completed 0 tests in 2 minutes - 1 errors, 0 warnings.
[Feb 21 23:10] Worker stopped.


[Feb 21 23:08] Worker starting
[Feb 21 23:08] Setting affinity to run worker on logical CPU #3
[Feb 21 23:08] Beginning a continuous self-test to check your computer.
[Feb 21 23:08] Please read stress.txt.  Choose Test/Stop to end this test.
[Feb 21 23:08] Test 1, 4000 Lucas-Lehmer iterations of M19922945 using FFT length 1024K.
[Feb 21 23:10] Test 2, 4000 Lucas-Lehmer iterations of M19922943 using FFT length 1024K.
[Feb 21 23:11] Test 3, 4000 Lucas-Lehmer iterations of M19374367 using FFT length 1024K.
[Feb 21 23:13] Test 4, 4000 Lucas-Lehmer iterations of M19174369 using FFT length 1024K.
[Feb 21 23:14] Test 5, 4000 Lucas-Lehmer iterations of M18874369 using FFT length 1024K.
[Feb 21 23:14] FATAL ERROR: Rounding was 0.4951171875, expected less than 0.4
[Feb 21 23:14] Hardware failure detected, consult stress.txt file.
[Feb 21 23:14] Torture Test completed 4 tests in 6 minutes - 1 errors, 0 warnings.
[Feb 21 23:14] Worker stopped.

So we have to try the other Prime95 tests (Small FFT's and Large FFT's) - which one's give errors and which one's don't give errors will point us in the next direction to look.

If your drivers are old(er) and there aren't any newer one's available - you don't have much choice.
If we suspect them, then you can uninstall the programs (thereby removing the drivers).

In the case of the Windows Driver Kit (which is free), this is probably the best idea.
I'd do the same with the FoxAwdWINFLASH.SYS simply because it is so old.

But, I don't think that that's going to make any difference.
The Prime95 Blend test causes problems with your system
The Prime95 Small FFT test doesn't cause problems (which tests mostly CPU cache and little RAM)
We still have to see what happens with the Large FFT test.

So this seems to be a memory problem - but which memory is the question here.
Is it the mobo, the RAM, or even the memory in the video card, the memory controller in the i-Series CPU, or some other component?

If we get errors with the Large FFT's, then the CPU is still in the running.
If we don't get errors with the Large FFT's, then the CPU is probably not a problem.

Finally, here's a quote from the stress.txt file:

WHAT TO DO IF A PROBLEM IS FOUND?
---------------------------------

The exact cause of a hardware problem can be very hard to find.

If you are not overclocking, the most likely cause is an overheating CPU
or memory DIMMs that are not quite up to spec. Another possibility is
you might need a better power supply. Try running MotherBoard monitor
and browse the forums above to see if your CPU is running too hot.
If so, make sure the heat sink is properly attached, fans are operational,
and air flow inside the case is good. For isolating memory problems, try
swapping memory DIMMs with a co-worker's or friend's machine. If the errors
go away, then you can be fairly confidant that memory was the cause of
the trouble. A power supply problem can often be identified by a significant
drop in the voltages when prime95 starts running. Once again the overclocker
forums are a good resource for what voltages are acceptable.

If you are overclocking then try increasing the core voltage, reduce the
CPU speed, reduce the front side bus speed, or change the memory timings
(CAS latency). Also try asking for help in one of the forums above - they
may have other ideas to try.

Still have to update motherboard/chipset drivers (if you've done this from the Foxconn website, then it's OK)
Still have to update the network drivers for your Realtek network card. (if you did this from the Foxconn website, let us know and we'll dig up the driver from the Realtek website).

Since this is most likely a memory issue, can you get other RAM to test in the system (or test your RAM in another system)? How about another video card (I can't recall if this has been tried or not).

We'll see what else I can figure out while I'm at work and I'll post back later on.

No need for further minidumps. This is a memory issue - so now you have to start testing the assorted memory components on the system.

Start by either trying other RAM in your system - or trying your RAM in another system. Run Prime95 Blend and Large FFT's to see if that causes crashes.

The last test shows errors with your video card. Try another one.

As for the RAM, it never hurts to test it in different slots - but let's see if another video card fixes things!