Win 7 BSOD i think when network active

Hi

my computer is only 4 days old, it is a Win 7 Professional 64 bit OEM system with 4 gig ram 1TB HDD, i use it as the main PC on a network via a cable router, although never all on at once the network has a second desktop Win XP home SP3 (my wifes) which generally is in use in the late evening till midnight, there is also a laptop which is ocassionally used on the network Win XP prof SP3. at the moment my old PC is also connected at times to transfer a lot of the data on it to the new PC tha is also win XP prof SP3 (all the extra PCs are 32bit).

I have experienced 11 or 12 BSOD,s in the last 3 days and looking at threads all over the web it seems it may be related to Zonealarm and or the network but i cannot read the crash dumps to find out what is the cause, i cannot swear to it but i believe all BSODs occurred when one of the other PCs was also live and connected to the home network.

my antivirus is AVG free,

Zonealarm is the paid version which i have been using for years on all the PCs on the network.

ZoneAlarm version: 10.0.241.000
vsmon version: 10.0.241.000
Driver version: 10.0.217.000
ZoneAlarm Browser Security: 1.5.311.0
ZoneAlarm ForceField Spyware Scanner: 1.5.53.235
ZoneAlarm ForceField Anti-Phishing Database: 1.2.104.0
ZoneAlarm ForceField Spyware Sites Database: 04.155

i do hope you can shed some light on this

Many thanks

The cause is probably ZoneAlarm, it has known issues with Windows 7.
Remove it completely and reinstall it. AVG should be removed and replaced by MSE

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7F, {8, 80050031, 406f8, fffff80002c46e88}

Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )


UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault).  The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
        use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
        use .trap on that value
Else
        .trap on the appropriate frame will show where the trap was taken
        (on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: 0000000080050031
Arg3: 00000000000406f8
Arg4: fffff80002c46e88

Debugging Details:
------------------


BUGCHECK_STR:  0x7f_8

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002c7dc69 to fffff80002c7e700

STACK_TEXT:  
fffff880`031dbce8 fffff800`02c7dc69 : 00000000`0000007f 00000000`00000008 00000000`80050031 00000000`000406f8 : nt!KeBugCheckEx
fffff880`031dbcf0 fffff800`02c7c132 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`031dbe30 fffff800`02c46e88 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2
fffff880`03b4ce80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!SeAccessCheckFromState+0x58


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiDoubleFaultAbort+b2
fffff800`02c7c132 90              nop

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  nt!KiDoubleFaultAbort+b2

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4d9fdd34

FAILURE_BUCKET_ID:  X64_0x7f_8_nt!KiDoubleFaultAbort+b2

BUCKET_ID:  X64_0x7f_8_nt!KiDoubleFaultAbort+b2

Followup: MachineOwner
---------

Many thanks for the quick response, strangely enough i have been on the PC for about 2 hours tonight with my wife on her PC both on the home network and we have both been online as well and everything has been stable, i am beginning to think it may be down to the old PC (which is off tonight) it was getting cranky taking a good 15 mins to boot to a usable state, typical WIN XP fault, i may just remove the hard drive and put it in the new machine just to copy off all the data temporarily rather than connect it to the network as i have been doing with its second drive.

as a matter of interest i will be uninstalling and reinstalling zonealarm as suggested but why AVG, was that implicated in the info, its just that i went over to it as all the other antiviruses i have used over the years have all ended up having to be turned off just to install a file, AVG lets me do that when it is running and on the old PC cought lots of stuff hapening that all the others never found. i also have a distrust of any security software from microsoft considering how many holes are in their operating systems.

Thanks again, i will update this in a few days to let everyone know if it has cleared up permanently.

its been well over 24 hours now with no BSOD's so it looks as if the old PC was causing something when connected in the home network, as it is going to be wiped completely and OS reinstalled i would guess that it will not cause any probs when it is finally allowed back on in a few weeks time as my wifes new PC.

another 24 hours with no problems so i think i can officially call this one cured, many thanks again for the help