Constant BSOD (WIndows 7 32-bit)

[usasma]

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

[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] [COLOR=Red]Hardware failure detected[/COLOR], 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] [COLOR=Red]Hardware failure detected[/COLOR], 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] [COLOR=Red]Hardware failure detected[/COLOR], 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.

 

[nikos21]

Intel Processor Diagnostic passed
Memtest86 test passed (all-night through), about 169 passes. I have one 2MB stick .
Prime95 Small FFt test passed (9 hours, no problems). I will try Large FFT tonight.
CPU stability test 6.0 run about 6 hours, did not show any problems, but then I had a crash.

I still don't know what to do with drivers. Most of the links go to Windows Resource Kit, which I have
already installed.
The same thing for FoxandWinFlash.sys. Any ideas?

 

[usasma]

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.

 

[nikos21]

Large FFt test crashed tonight.

 

[usasma]

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.

 

[nikos21]

I installed Win7 and WinServer 2008 R2 Auto Installation Program (SID:1442300) for Realtek 10/100/1000 Gigabit Ethernet PCI Express from this link
Realtek

Prime 95 Large FFT failed. Workers 2 and 4 stopped after an hour, and after 3 hours I had a crash (my blue screen
showed file wdf01000.sys.

I attach minidump

 

[usasma]

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.

 

[nikos21]

• Video Memory Stress test results

WARNING: Your card can be not compatible with this test! If multiple errors will found, try test with onscreen buffer usage or wthout of ignoring colors bit mask.
Changing video mode to 640x480x16...OK
[23/2/2011 8:16:06 ìì] Test started for "Âáóéêü ðñüãñáììá ïäÞãçóçò ïèüíçò (ATI Radeon HD 5450)"...
Trying 16bpp RGB:565 mode...OK
Trying 16bpp RGB:555 mode...OK
Trying 16bpp BGR:565 mode...NOT SUPPORTED (Code: 80004001)
Trying 32bpp RGB:888 mode...OK
Error at [085AB460]: must be FF00FF00, but found FF00FD00 (bits: 00000000000000000000001000000000)
Error at [085AB5C0]: must be FF00FF00, but found FF00FD00 (bits: 00000000000000000000001000000000)
Error at [085AB650]: must be FF00FF00, but found FF00FD00 (bits: 00000000000000000000001000000000)
Error at [085AB870]: must be FF00FF00, but found FF00FD00 (bits: 00000000000000000000001000000000)
Error at [085ABEB8]: must be FF00FF00, but found FF00FD00 (bits: 00000000000000000000001000000000)
Error at [085ABED0]: must be FF00FF00, but found FF00FD00 (bits: 00000000000000000000001000000000)
Error at [085ABF98]: must be FF00FF00, but found FF00FD00 (bits: 00000000000000000000001000000000)
Error at [14647428]: must be FFFF7FFF, but found FFFF7DFF (bits: 00000000000000000000001000000000)
Error at [0DB10D58]: must be FBFFFFFF, but found FBFFFDFF (bits: 00000000000000000000001000000000)
Trying 32bpp BGR:888 mode...NOT SUPPORTED (Code: 80004001)
[23/2/2011 9:37:47 ìì] Pass completed (9 errors found).

• Another question: in general should I have Windows Update working or not?
• It's rather difficult test my RAM in another PC, does it worth changing RAM's place to the other port?

 

[usasma]

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!

 

[nikos21]

I changed Ram slots, but Prime95 large FFT test stopped working (worker #2 stopped at first).
Ozone 3d Funmark test (Stability test) run allnight and showed no problems, but when I exit from
the program there was a crash

 

[usasma]

OK, so the Large FFT failures are independent of whatever slot the RAM is in.
You still have to try another video card. If you can't borrow one, then purchase one that you can return (and get your money back) - then test with that.

 

[nikos21]

I think borrowing a card it's not easy at all.
Is there a video card test for us to have, so that I can prove to the shop that I bought my PC that my video card is
faulty?
I am still in guarantee, my computer is only six months old...
Finally, are we sure that my video card drivers are OK? A month ago, I brought my PC to the providers, and they insisted that hardware was tested and found OK, so there was a software (Win 7) problem.

 

[usasma]

There are no video card tests that are 100% sure. If the provider insisted that there were no hardware problems, then they must have tests that no one else has. Even the few tests that we use here (HDD and memory) aren't 100% accurate.

You have updated your video drivers, so we presume that they installed correctly and are functioning correctly.

Furthermore you have used a video stress test and it found errors with your video card (in post #28). You're also experiencing errors in Prime95. Show those results to the shop and see what they have to say. They should have a spare video card to test your system with.

 

[nikos21]

One last (?) question.

Do you think that Mozilla Firefox crashes are related to my video card problem ? I have uninstall and re-installed it a few times, but crashes still appear.

Thanks a lot for your help. I will let you know when I have results.

 

[usasma]

Uninstall/reinstall of Firefox makes it pretty certain that Firefox isn't at fault.

It's possible that they're related, but that'd take an analysis of those crashes - and I'm no good at analyzing user-level crashes.

 

[nikos21]

Problem solved!

Usasma,

finally the problem was solved. My Ram was defective, the PC provider gave me a brand new and now everything is working properly.

Thank you indeed for your time and help.