recurring blue screens, again

[simeon]

I already reported painful BSODs here : http://www.sevenforums.com/crashes-debugging/110310-recurring-blue-screens.html#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:
[FONT=Segoe UI, Arial]Bugcheck code: 0x124 (0x0, 0xFFFFFA8007D1A028, 0xB6002000, 0xE2000175)[/FONT]

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

Last Output of "whocrashed" as follows :
---------------------------------------
[FONT=Segoe UI, Arial]Welcome to WhoCrashed Home Edition 2.10 [/FONT]
[FONT=Segoe UI, Arial]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.
[/FONT]

[FONT=Segoe UI, Arial]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 ...


[/FONT][FONT=Segoe UI, Arial] Home Edition notice [/FONT]
[FONT=Segoe UI, Arial]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. [/FONT]

[FONT=Segoe UI, Arial] Analysis [/FONT]
[FONT=Segoe UI, Arial]Crash dump directory: C:\Windows\Minidump[/FONT]

[FONT=Segoe UI, Arial][FONT=Segoe UI, Arial]Crash dumps are enabled on your computer.
[/FONT][/FONT]

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

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

[FONT=Segoe UI, Arial]On Fri 10/09/2010 04:38:05 your computer crashed
This was likely caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT]
Bugcheck code: 0x7F (0x8, 0x80050031, 0x6F8, 0xFFFFF80002C45D28)
Error: [FONT=Segoe UI, Arial]UNEXPECTED_KERNEL_MODE_TRAP[/FONT]
Dump file: C:\Windows\Minidump\091010-16224-01.dmp
[/FONT][FONT=Segoe UI, Arial]file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
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.
[/FONT][FONT=Segoe UI, Arial]
[/FONT]

[FONT=Segoe UI, Arial]On Thu 09/09/2010 19:34:28 your computer crashed
This was likely caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT]
Bugcheck code: 0x7F (0x8, 0x80050031, 0x6F8, 0xFFFFF80002C38D28)
Error: [FONT=Segoe UI, Arial]UNEXPECTED_KERNEL_MODE_TRAP[/FONT]
Dump file: C:\Windows\Minidump\090910-18969-01.dmp
[/FONT][FONT=Segoe UI, Arial]file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
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.
[/FONT][FONT=Segoe UI, Arial]
[/FONT]

[FONT=Segoe UI, Arial]On Thu 09/09/2010 05:04:39 your computer crashed
This was likely caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT]
Bugcheck code: 0x7F (0x8, 0x80050031, 0x6F8, 0xFFFFF80002C55D28)
Error: [FONT=Segoe UI, Arial]UNEXPECTED_KERNEL_MODE_TRAP[/FONT]
Dump file: C:\Windows\Minidump\090910-15085-01.dmp
[/FONT][FONT=Segoe UI, Arial]file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
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.
[/FONT][FONT=Segoe UI, Arial]
[/FONT]

[FONT=Segoe UI, Arial]On Thu 09/09/2010 05:00:14 your computer crashed
This was likely caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT]
Bugcheck code: 0x7F (0x8, 0x80050031, 0x6F8, 0xFFFFF80002CA0EC8)
Error: [FONT=Segoe UI, Arial]UNEXPECTED_KERNEL_MODE_TRAP[/FONT]
Dump file: C:\Windows\Minidump\090910-17331-01.dmp
[/FONT][FONT=Segoe UI, Arial]file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
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.
[/FONT][FONT=Segoe UI, Arial]
[/FONT]

[FONT=Segoe UI, Arial]On Tue 07/09/2010 15:16:34 your computer crashed
This was likely caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT]
Bugcheck code: 0x7F (0x8, 0x80050031, 0x6F8, 0xFFFFF80002C8CD28)
Error: [FONT=Segoe UI, Arial]UNEXPECTED_KERNEL_MODE_TRAP[/FONT]
Dump file: C:\Windows\Minidump\090710-15319-01.dmp
[/FONT][FONT=Segoe UI, Arial]file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
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.
[/FONT][FONT=Segoe UI, Arial]
[/FONT]

[FONT=Segoe UI, Arial]On Tue 07/09/2010 12:08:00 your computer crashed
This was likely caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT]
Bugcheck code: 0x7F (0x8, 0x80050031, 0x6F8, 0xFFFFF80002C44EC8)
Error: [FONT=Segoe UI, Arial]UNEXPECTED_KERNEL_MODE_TRAP[/FONT]
Dump file: C:\Windows\Minidump\090710-23992-01.dmp
[/FONT][FONT=Segoe UI, Arial]file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
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.
[/FONT][FONT=Segoe UI, Arial]
[/FONT]

[FONT=Segoe UI, Arial]On Mon 06/09/2010 05:17:10 your computer crashed
This was likely caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT]
Bugcheck code: 0x7F (0x8, 0x80050031, 0x6F8, 0xFFFFF80002C39D28)
Error: [FONT=Segoe UI, Arial]UNEXPECTED_KERNEL_MODE_TRAP[/FONT]
Dump file: C:\Windows\Minidump\090610-16114-01.dmp
[/FONT][FONT=Segoe UI, Arial]file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
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.
[/FONT][FONT=Segoe UI, Arial]
[/FONT]

[FONT=Segoe UI, Arial]On Mon 06/09/2010 05:13:14 your computer crashed
This was likely caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT]
Bugcheck code: 0x7F (0x8, 0x80050031, 0x6F8, 0xFFFFF80002C38D28)
Error: [FONT=Segoe UI, Arial]UNEXPECTED_KERNEL_MODE_TRAP[/FONT]
Dump file: C:\Windows\Minidump\090610-18564-01.dmp
[/FONT][FONT=Segoe UI, Arial]file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
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.
[/FONT][FONT=Segoe UI, Arial]
[/FONT]

[FONT=Segoe UI, Arial]On Mon 06/09/2010 04:23:53 your computer crashed
This was likely caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT]
Bugcheck code: 0x7F (0x8, 0x80050031, 0x6F8, 0xFFFFF80002C86D28)
Error: [FONT=Segoe UI, Arial]UNEXPECTED_KERNEL_MODE_TRAP[/FONT]
Dump file: C:\Windows\Minidump\090610-19078-01.dmp
[/FONT][FONT=Segoe UI, Arial]file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
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.
[/FONT][FONT=Segoe UI, Arial]
[/FONT]

[FONT=Segoe UI, Arial]On Sun 05/09/2010 08:29:22 your computer crashed
This was likely caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT]
Bugcheck code: 0x7F (0x8, 0x80050031, 0x6F8, 0xFFFFF80002C89D28)
Error: [FONT=Segoe UI, Arial]UNEXPECTED_KERNEL_MODE_TRAP[/FONT]
Dump file: C:\Windows\Minidump\090510-16754-01.dmp
[/FONT][FONT=Segoe UI, Arial]file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
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.
[/FONT][FONT=Segoe UI, Arial]
[/FONT]

[FONT=Segoe UI, Arial]On Sun 05/09/2010 05:33:25 your computer crashed
This was likely caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT]
Bugcheck code: 0x7F (0x8, 0x80050031, 0x6F8, 0xFFFFF80002C92D28)
Error: [FONT=Segoe UI, Arial]UNEXPECTED_KERNEL_MODE_TRAP[/FONT]
Dump file: C:\Windows\Minidump\090510-19375-01.dmp
[/FONT][FONT=Segoe UI, Arial]file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
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.
[/FONT][FONT=Segoe UI, Arial]
[/FONT]

[FONT=Segoe UI, Arial]On Mon 16/08/2010 19:28:15 your computer crashed
This was likely caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT]
Bugcheck code: 0x19 (0x22, 0xFFFFF8A00109A000, 0x1, 0x0)
Error: [FONT=Segoe UI, Arial]BAD_POOL_HEADER[/FONT]
Dump file: C:\Windows\Minidump\081610-25615-01.dmp
[/FONT][FONT=Segoe UI, Arial]file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
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.
[/FONT][FONT=Segoe UI, Arial]
[/FONT]

[FONT=Segoe UI, Arial] Conclusion [/FONT]
[FONT=Segoe UI, Arial]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. [/FONT]

[FONT=Segoe UI, Arial]
[/FONT]

[FONT=Segoe UI, Arial]
[/FONT]

 

[usasma]

The STOP 0x124 error is an error that your CPU reports to Windows. As such it doesn't have a whole bunch of information that's useful to those who don't write code (me included). But it's a simple error - reflecting a hardware issue.

This is most likely broken hardware, but can also be a compatibility issue, or even a driver issue. We're lucky that you have a dual-boot system, as that will tend to rule out hardware (because it works in Linux). But that also makes it much harder to figure out what the problem is.

Here's a link that'll get you started on troubleshooting the error: http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html

Here's some additional, free stress testing utilities:

FurMark download site: FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net
FurMark Setup:
- If you have more than one GPU, select Multi-GPU during setup
- In the Run mode box, select "Stability Test" and "Log GPU Temperature"
Click "Go" to start the test
- Run the test until the GPU temperature maxes out - or until you start having problems (whichever comes first).
- Click "Quit" to exit

Prime95 download site: Free Software - GIMPS
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 you may want to 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.

Two other video stress tests (may be more stressful than FurMark):
Video Memory stress Test - МИРNVIDIA / Утилиты / VMT
Artifact Locator - МИРNVIDIA / Утилиты / Artifact Locator
Sorry, but I don't read the language that this website is made in.

Because of previous errors, I'd start by guessing that it's your video card or network card (it's just a guess, don't buy anything because of this). If you have a spare card to try, you may want to swap them out to see if it makes any difference.

BSOD BUGCHECK SUMMARY

[font=lucida console]
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sun Sep 12 11:12:05.918 2010 (UTC - 4:00)
System Uptime: 0 days 1:04:47.853
BugCheck 124, {0, fffffa8007d1a028, b6002000, e2000175}
Probably caused by : hardware
BUGCHECK_STR:  0x124_AuthenticAMD
PROCESS_NAME:  Bridge.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sun Sep 12 04:38:53.459 2010 (UTC - 4:00)
System Uptime: 0 days 4:19:16.755
BugCheck 124, {0, fffffa8007cf9028, b6004000, 75000175}
Probably caused by : hardware
BUGCHECK_STR:  0x124_AuthenticAMD
PROCESS_NAME:  Bridge.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Thu Sep  9 15:56:19.792 2010 (UTC - 4:00)
System Uptime: 0 days 0:22:12.727
BugCheck 7F, {8, 80050031, 6f8, fffff80002c45d28}
Probably caused by : NETIO.SYS ( NETIO!CompareSecurityContexts+6a )
BUGCHECK_STR:  0x7f_8
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Thu Sep  9 14:38:19.549 2010 (UTC - 4:00)
System Uptime: 0 days 0:59:44.845
BugCheck 7F, {8, 80050031, 6f8, fffff80002c38d28}
Probably caused by : NETIO.SYS ( NETIO!CompareSecurityContexts+6a )
BUGCHECK_STR:  0x7f_8
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Thu Sep  9 01:03:31.541 2010 (UTC - 4:00)
System Uptime: 0 days 0:03:35.836
BugCheck 7F, {8, 80050031, 6f8, fffff80002c55d28}
Probably caused by : NETIO.SYS ( NETIO!CompareSecurityContexts+6a )
BUGCHECK_STR:  0x7f_8
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Sep  8 15:27:29.548 2010 (UTC - 4:00)
System Uptime: 0 days 1:04:34.844
BugCheck 7F, {8, 80050031, 6f8, fffff80002ca0ec8}
Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
BUGCHECK_STR:  0x7f_8
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Sep  7 11:15:28.734 2010 (UTC - 4:00)
System Uptime: 0 days 0:14:23.045
BugCheck 7F, {8, 80050031, 6f8, fffff80002c8cd28}
Probably caused by : NETIO.SYS ( NETIO!CompareSecurityContexts+6a )
BUGCHECK_STR:  0x7f_8
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Sep  6 16:22:00.734 2010 (UTC - 4:00)
System Uptime: 0 days 1:38:56.669
BugCheck 7F, {8, 80050031, 6f8, fffff80002c44ec8}
Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
BUGCHECK_STR:  0x7f_8
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Sep  6 01:16:00.448 2010 (UTC - 4:00)
System Uptime: 0 days 0:03:06.743
BugCheck 7F, {8, 80050031, 6f8, fffff80002c39d28}
Probably caused by : NETIO.SYS ( NETIO!CompareSecurityContexts+6a )
BUGCHECK_STR:  0x7f_8
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Sep  6 00:52:00.782 2010 (UTC - 4:00)
System Uptime: 0 days 0:22:27.078
BugCheck 7F, {8, 80050031, 6f8, fffff80002c38d28}
Probably caused by : NETIO.SYS ( NETIO!CompareSecurityContexts+6a )
BUGCHECK_STR:  0x7f_8
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sun Sep  5 16:40:00.265 2010 (UTC - 4:00)
System Uptime: 0 days 0:14:32.201
BugCheck 7F, {8, 80050031, 6f8, fffff80002c86d28}
Probably caused by : NETIO.SYS ( NETIO!CompareSecurityContexts+6a )
BUGCHECK_STR:  0x7f_8
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sun Sep  5 03:40:00.170 2010 (UTC - 4:00)
System Uptime: 0 days 0:29:20.105
BugCheck 7F, {8, 80050031, 6f8, fffff80002c89d28}
Probably caused by : NETIO.SYS ( NETIO!CompareSecurityContexts+6a )
BUGCHECK_STR:  0x7f_8
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Sep  4 03:15:20.687 2010 (UTC - 4:00)
System Uptime: 0 days 0:22:41.982
BugCheck 7F, {8, 80050031, 6f8, fffff80002c92d28}
Probably caused by : NETIO.SYS ( NETIO!CompareSecurityContexts+6a )
BUGCHECK_STR:  0x7f_8
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Aug 16 15:27:03.053 2010 (UTC - 4:00)
System Uptime: 0 days 1:47:02.348
BugCheck 19, {22, fffff8a00109a000, 1, 0}
*** WARNING: Unable to verify timestamp for atipmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atipmdag.sys
Probably caused by : atipmdag.sys ( atipmdag+277a8 )
BUGCHECK_STR:  0x19_22
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  
 
 [/font]

 

[simeon]

some feedback, may be resolved

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)