recurring blue screens, again

I already reported painful BSODs here : https://www.sevenforums.com/crashes-d...tml#post950019

and, having removed Zone Alarm, I thought that all my problems were resolved.

Apparently not. Although less frequent, I still enjoy BSODs (2 for today).

The output of "whocrashed" shows me a different error code than then ones with ZA. It points to a "hardware" issue, but does not give me any hint on which one. Worth to note, this is a dual boot machine and -so far - I did not experience any crash under Ubuntu 10.04.1, so I am a bit skeptic on the diagnosis. I am mainly using Linux for web activities, browsing, posting, utube etc...so the chances that I got a virus on windows are dim (I did not install flashplayer under windows for fear of worms).
Also worth to note on hw side : I did not set any overclocking on, the whole ASUS config is running with default options.

The 2 most recent crashes (i.e. after ZA removal) give exactly the same error code:
Bugcheck code: 0x124 (0x0, 0xFFFFFA8007D1A028, 0xB6002000, 0xE2000175)

I attach the 2 zipped files as recommended.
Help or hints will be appreciated.
Many thanks in advance.

Last Output of "whocrashed" as follows :
---------------------------------------
Welcome to WhoCrashed Home Edition 2.10
This program checks for drivers which have been crashing your computer.

Whenever a computer suddenly reboots without displaying any notice or blue screen of death, the first thing that is often though about is a hardware failure. In reality, on Windows most crashes are caused by malfunctioning device drivers and kernel modules. In case of a kernel error, most computers do not show a blue screen unless they are configured to do so. Instead these systems suddenly reboot without any notice.

This program does post-mortem crash dump analysis with the single click of a button.


To obtain technical support visit www.resplendence.com/support

To check if a newer version of this program is available, click here.

Just click the Analyze button for a comprehensible report ...


Home Edition notice
This version of WhoCrashed is free for use at home only. If you would like to use this software at work or in a commercial environment you should get the professional edition. The professional edition of WhoCrashed also allows analysis of crashdumps on remote drives and computers on the network and offers more detailed analysis.

Analysis
Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Sun 12/09/2010 15:19:22 your computer crashed
This was likely caused by the following module: hardware
Bugcheck code: 0x124 (0x0, 0xFFFFFA8007D1A028, 0xB6002000, 0xE2000175)
Error: WHEA_UNCORRECTABLE_ERROR
Dump file: C:\Windows\Minidump\091210-30451-01.dmp



On Sun 12/09/2010 08:40:35 your computer crashed
This was likely caused by the following module: hardware
Bugcheck code: 0x124 (0x0, 0xFFFFFA8007CF9028, 0xB6004000, 0x75000175)
Error: WHEA_UNCORRECTABLE_ERROR
Dump file: C:\Windows\Minidump\091210-29858-01.dmp



On Fri 10/09/2010 04:38:05 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x7F (0x8, 0x80050031, 0x6F8, 0xFFFFF80002C45D28)
Error: UNEXPECTED_KERNEL_MODE_TRAP
Dump file: C:\Windows\Minidump\091010-16224-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Thu 09/09/2010 19:34:28 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x7F (0x8, 0x80050031, 0x6F8, 0xFFFFF80002C38D28)
Error: UNEXPECTED_KERNEL_MODE_TRAP
Dump file: C:\Windows\Minidump\090910-18969-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Thu 09/09/2010 05:04:39 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x7F (0x8, 0x80050031, 0x6F8, 0xFFFFF80002C55D28)
Error: UNEXPECTED_KERNEL_MODE_TRAP
Dump file: C:\Windows\Minidump\090910-15085-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Thu 09/09/2010 05:00:14 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x7F (0x8, 0x80050031, 0x6F8, 0xFFFFF80002CA0EC8)
Error: UNEXPECTED_KERNEL_MODE_TRAP
Dump file: C:\Windows\Minidump\090910-17331-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Tue 07/09/2010 15:16:34 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x7F (0x8, 0x80050031, 0x6F8, 0xFFFFF80002C8CD28)
Error: UNEXPECTED_KERNEL_MODE_TRAP
Dump file: C:\Windows\Minidump\090710-15319-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Tue 07/09/2010 12:08:00 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x7F (0x8, 0x80050031, 0x6F8, 0xFFFFF80002C44EC8)
Error: UNEXPECTED_KERNEL_MODE_TRAP
Dump file: C:\Windows\Minidump\090710-23992-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Mon 06/09/2010 05:17:10 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x7F (0x8, 0x80050031, 0x6F8, 0xFFFFF80002C39D28)
Error: UNEXPECTED_KERNEL_MODE_TRAP
Dump file: C:\Windows\Minidump\090610-16114-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Mon 06/09/2010 05:13:14 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x7F (0x8, 0x80050031, 0x6F8, 0xFFFFF80002C38D28)
Error: UNEXPECTED_KERNEL_MODE_TRAP
Dump file: C:\Windows\Minidump\090610-18564-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Mon 06/09/2010 04:23:53 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x7F (0x8, 0x80050031, 0x6F8, 0xFFFFF80002C86D28)
Error: UNEXPECTED_KERNEL_MODE_TRAP
Dump file: C:\Windows\Minidump\090610-19078-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Sun 05/09/2010 08:29:22 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x7F (0x8, 0x80050031, 0x6F8, 0xFFFFF80002C89D28)
Error: UNEXPECTED_KERNEL_MODE_TRAP
Dump file: C:\Windows\Minidump\090510-16754-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Sun 05/09/2010 05:33:25 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x7F (0x8, 0x80050031, 0x6F8, 0xFFFFF80002C92D28)
Error: UNEXPECTED_KERNEL_MODE_TRAP
Dump file: C:\Windows\Minidump\090510-19375-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Mon 16/08/2010 19:28:15 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x19 (0x22, 0xFFFFF8A00109A000, 0x1, 0x0)
Error: BAD_POOL_HEADER
Dump file: C:\Windows\Minidump\081610-25615-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



Conclusion
14 crash dumps have been found and analyzed. Note that it's not always possible to state with certainty whether a reported driver is really responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.

I think it is worth that I give some feedback.

I did not find enough time to "stress test" my hw config as hinted above (but I'll do so when I find it ;-). for the simple reason that it works well under Ubuntu. Furthermore, I was very careful choosing it : with an Antec Twelve Hundred using 6 fans and a huge ThermalTake fan on CPU, I do not think cooling is a problem (there is also enough power supply with the ATX Enermax Revolution85+ 950W). Also: all Asus config is set to default values, i.e. no overclocking at all.

I really think that the latest updates I obtained from MS did fix the problem. I did not check exactly what exactly went through the automated update, but for sure it helped. The following facts might give some hints :

1. in the summary diagnosis provided above, there is an explicit indication that the process which triggered latest BSODs (i.e. after removal of ZoneAlarm) was bridge.exe

2. once the OS updates were installed, I started bridge (= photoshop browser ) again and this time obtained an explicit error message explaining there was a memory problem and that the application needed to close. This time, no BSOD.

3. googling on the issue, I found out that I was not the only one experiencing memory issues under win7/64 with that application. Worth to note, photoshop is supposed to be a true 64 bits application, whereas bridge runs in a 32 bits address space. It would not surprise me that, despite my 8 Gb RAM, that windows 7/64 had a problem handling both at the same time. Even stranger, the task manager never showed I was approaching the 2^^32 boundary...

4. finally, I applied the trick given by one of the adobe forumers : start bridge holding the CTRL key, which resets config values to their default.

Since then I experienced no crash...

So, if s.o. has a better explanation, his feedback is welcome, particularly on the 32/64 boundaries (by the way: why aren't ALL applications recompiled on a 64 bits compiler ????).

If I may ask, I would suggest not to close directly this thread because no BSOD for a whole week-end is no certainty the issue is resolved. I would also like to share the results of the stress tests that I still intend to do, if I may...

And by the way, sincere thanks to those above who helped me (without the explicit reference to bridge.exe , I would never have looked in that direction)