Simple one, conflict with zone alarm and the system, use this hot fix or you could uninstall zone alarm.
http://support.microsoft.com/kb/981180
0x0000007F: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
A system thread generated an exception which the error handler did not catch. There are numerous individual causes for this problem, including hardware incompatibility, a faulty device driver or system service, or some software issues. Check Event Viewer (EventVwr.msc) for additional information.
Code:
icrosoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\richc46\AppData\Local\Temp\Temp18_Minidump[1].zip\082410-18703-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`03064000 PsLoadedModuleList = 0xfffff800`032a1e50
Debug session time: Tue Aug 24 09:52:52.107 2010 (GMT-4)
System Uptime: 0 days 0:12:13.232
Loading Kernel Symbols
...............................................................
................................................................
.............................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 7F, {8, 80050033, 6f8, fffff800030debd0}
Probably caused by : NETIO.SYS ( NETIO!CompareSecurityContexts+6a )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
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: 0000000080050033
Arg3: 00000000000006f8
Arg4: fffff800030debd0
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 fffff800030d3ca9 to fffff800030d4740
STACK_TEXT:
fffff800`00ba4d28 fffff800`030d3ca9 : 00000000`0000007f 00000000`00000008 00000000`80050033 00000000`000006f8 : nt!KeBugCheckEx
fffff800`00ba4d30 fffff800`030d2172 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff800`00ba4e70 fffff800`030debd0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2
fffff880`0be86fe0 fffff800`030d9da7 : fffff880`0be871a0 fffff880`0be871c0 00000000`00000001 06f91691`005f8b60 : nt!SepMandatoryIntegrityCheck+0xf0
fffff880`0be87060 fffff800`0309cf6a : fffffa80`0759b080 00000000`00000001 00000000`00000000 fffffa80`065557c8 : nt!SeAccessCheckWithHint+0x317
fffff880`0be87140 fffff880`01599c5a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!SeAccessCheckFromState+0x102
fffff880`0be87830 fffff880`0159794f : 00000000`c0000022 00000000`00000000 00000000`00000000 00000000`00000000 : NETIO!CompareSecurityContexts+0x6a
fffff880`0be878a0 fffff880`015999b5 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : NETIO!MatchValues+0xef
fffff880`0be878f0 fffff880`01599845 : fffffa80`08bfb460 fffffa80`075226e0 fffff880`0be87b18 fffff880`0be88250 : NETIO!FilterMatch+0x95
fffff880`0be87940 fffff880`0159accb : 00000000`00000000 00000000`00000000 fffff880`0be88250 fffff880`0be87b00 : NETIO!IndexListClassify+0x69
fffff880`0be879c0 fffff880`01640417 : fffff880`0be87e98 fffff880`0be87e98 fffff880`0be88bd0 fffffa80`05ac0540 : NETIO!KfdClassify+0xa4e
fffff880`0be87d30 fffff880`0163983e : fffff880`01748690 00000000`00000000 fffffa80`0884c580 00000000`00000000 : tcpip!WfpAleClassify+0x57
fffff880`0be87d70 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : tcpip!WfpAlepAuthorizeSend+0x94e
STACK_COMMAND: kb
FOLLOWUP_IP:
NETIO!CompareSecurityContexts+6a
fffff880`01599c5a 448b442470 mov r8d,dword ptr [rsp+70h]
SYMBOL_STACK_INDEX: 6
SYMBOL_NAME: NETIO!CompareSecurityContexts+6a
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: NETIO
IMAGE_NAME: NETIO.SYS
DEBUG_FLR_IMAGE_TIMESTAMP: 4bbe946f
FAILURE_BUCKET_ID: X64_0x7f_8_NETIO!CompareSecurityContexts+6a
BUCKET_ID: X64_0x7f_8_NETIO!CompareSecurityContexts+6a
Followup: MachineOwner
---------
Hot fix and zone alarm uninstall tool, which should be used if you choose to uninstall
Zone Alarm Uninstall Tool http://forums.zonealarm.com/showthread.php?t=70034 and hotfix
http://support.microsoft.com/kb/981180
Quote