New
#1
BSOD can upload zip files now
Ran chck disk memtest with no errors get random BSOD have uploaded filesAttachment 102461
Attachment 102462
Ran chck disk memtest with no errors get random BSOD have uploaded filesAttachment 102461
Attachment 102462
This one was probably caused by NETIO.sys usually Zone alarm is the real culprit. I would remove and replace with Microsoft Security Essentials.
Make sure you remove all traces of ZAP.
Let us know if you need further assistance
Ken J
Code:Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\100510-20872-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/;srv*e:\symbols *http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7600 MP (6 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Machine Name: Kernel base = 0xfffff800`02a00000 PsLoadedModuleList = 0xfffff800`02c3de50 Debug session time: Tue Oct 5 20:12:02.747 2010 (GMT-4) System Uptime: 0 days 0:15:41.714 Loading Kernel Symbols ............................................................... ................................................................ .................. Loading User Symbols Loading unloaded module list .... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 7F, {8, 80050031, 6f8, fffff80002a38d28} *** ERROR: Module load completed but symbols could not be loaded for tcpip.sys Probably caused by : NETIO.SYS ( NETIO!CompareSecurityContexts+6a ) Followup: MachineOwner --------- 3: 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: 0000000080050031 Arg3: 00000000000006f8 Arg4: fffff80002a38d28 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 fffff80002a6fca9 to fffff80002a70740 STACK_TEXT: fffff880`02fd9d68 fffff800`02a6fca9 : 00000000`0000007f 00000000`00000008 00000000`80050031 00000000`000006f8 : nt!KeBugCheckEx fffff880`02fd9d70 fffff800`02a6e172 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69 fffff880`02fd9eb0 fffff800`02a38d28 : 000004d8`00000000 000004d8`00000000 000004d8`00000000 000004d8`00000000 : nt!KiDoubleFaultAbort+0xb2 fffff880`02ff6000 fffff800`02a38f07 : fffffa80`04a0f7c8 00000000`00000001 000004d8`00000000 000004d8`00000000 : nt!SepTokenFromAccessInformation+0x20 fffff880`02ff6030 fffff880`01510c5a : 000004d8`00000000 000004d8`00000000 000004d8`00000000 000004d8`00000000 : nt!SeAccessCheckFromState+0x9f fffff880`02ff6720 fffff880`0150e94f : 000004d8`00000000 000004d8`00000000 000004d8`00000000 000004d8`00000000 : NETIO!CompareSecurityContexts+0x6a fffff880`02ff6790 fffff880`015109b5 : 000004d8`00000000 000004d8`00000000 000004d8`00000000 000004d8`00000000 : NETIO!MatchValues+0xef fffff880`02ff67e0 fffff880`01510845 : fffffa80`0661a710 fffffa80`064b7d00 fffff880`02ff6a08 fffff880`02ff7140 : NETIO!FilterMatch+0x95 fffff880`02ff6830 fffff880`01511ccb : 00000000`00000000 00000000`00000000 fffff880`02ff7140 fffff880`02ff69f0 : NETIO!IndexListClassify+0x69 fffff880`02ff68b0 fffff880`0163e417 : fffff880`02ff6d88 fffff880`02ff6d88 fffff880`02ff7ac0 fffffa80`06353570 : NETIO!KfdClassify+0xa4e fffff880`02ff6c20 fffff880`0163783e : fffff880`01746690 00000000`00000000 fffffa80`06488a70 00000000`00000000 : tcpip+0x3d417 fffff880`02ff6c60 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : tcpip+0x3683e STACK_COMMAND: kb FOLLOWUP_IP: NETIO!CompareSecurityContexts+6a fffff880`01510c5a 448b442470 mov r8d,dword ptr [rsp+70h] SYMBOL_STACK_INDEX: 5 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 ---------
Thanks! Did what you advised and no crashes yet
Thanks Again,
Scott
please help