View Single Post
02 Jan 2011  

Win 8 Release candidate 8400

Quote   Quote: Originally Posted by vashnic View Post

This is my first attempts to do anything resembling building a computer, which just started running last night. Ran perfectly well into video game until ~15 min in, then screen froze, went blank save for a thin line through the middle (??), weird electronic noise, then BSoD and autorestart. Happens anywhere from 5/10 min into games now. Has also been happening sporadically (without the noise) when I try to install software. No problems elsewhere.

Updated BIOS and graphics drivers to most recent, best of my knowledge.

OS: Windows 7x64 Home OEM
GPU: HIS Radeon 6850
Mobo: Asus M4A87TD/USB3
CPU: AMD Phenom II X6 Black 1090T
PSU: OCZ 650w

Thank you very much for your time. ^^
All of these were virtually identical. They were blamed on NETIO.SYS, and usually that is caused by Zone Alarm. I looked on step further and ZAP process was running in all of them

I would remove it and replace with Microsoft Security Essentials and the win 7 firewall

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Users\K\Desktop\BSoD files\Windows_NT6_BSOD_jcgriff2\123110-19203-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*;srv*e:\symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02862000 PsLoadedModuleList = 0xfffff800`02a9fe50
Debug session time: Fri Dec 31 23:49:28.461 2010 (GMT-5)
System Uptime: 0 days 0:17:25.428
Loading Kernel Symbols

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

Loading User Symbols
Loading unloaded module list
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *

Use !analyze -v to get detailed debugging information.

BugCheck 7F, {8, 80050031, 6f8, fffff800028da609}

Probably caused by : NETIO.SYS ( NETIO!CompareSecurityContexts+6a )

Followup: MachineOwner

2: kd> !analyze -v
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *

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
        .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)
kb will then show the corrected stack.
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: 0000000080050031
Arg3: 00000000000006f8
Arg4: fffff800028da609

Debugging Details:




PROCESS_NAME:  install_flash_


LAST_CONTROL_TRANSFER:  from fffff800028d3469 to fffff800028d3f00

fffff880`02d69d68 fffff800`028d3469 : 00000000`0000007f 00000000`00000008 00000000`80050031 00000000`000006f8 : nt!KeBugCheckEx
fffff880`02d69d70 fffff800`028d1932 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`02d69eb0 fffff800`028da609 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2
fffff880`02d8cfc0 fffff800`028d99e4 : 00000486`00000000 fffff880`02d8d2e0 fffff880`02d8d2e0 00000486`00000000 : nt!SepNormalAccessCheck+0x29
fffff880`02d8d050 fffff800`028d9410 : fffff880`02d8d2c0 00000000`00000000 fffff880`02d8d2c0 fffff880`02d8d2e0 : nt!SepAccessCheck+0x1d4
fffff880`02d8d180 fffff800`0289c842 : fffffa80`0694e970 00000000`00000001 00000000`00000000 fffffa80`04b327c8 : nt!SeAccessCheckWithHint+0x180
fffff880`02d8d260 fffff880`015a4c5a : 00000486`00000000 00000486`00000000 00000486`00000000 00000486`00000000 : nt!SeAccessCheckFromState+0x102
fffff880`02d8d950 fffff880`015a294f : 00000486`00000000 00000486`00000000 00000486`00000000 00000486`00000000 : NETIO!CompareSecurityContexts+0x6a
fffff880`02d8d9c0 fffff880`015a49b5 : 00000486`00000000 00000486`00000000 00000486`00000000 00000486`00000000 : NETIO!MatchValues+0xef
fffff880`02d8da10 fffff880`015a4845 : fffffa80`05459170 fffffa80`0684a190 fffff880`02d8dc38 fffff880`02d8e370 : NETIO!FilterMatch+0x95
fffff880`02d8da60 fffff880`015a5ccb : 00000000`00000000 00000000`00000000 fffff880`02d8e370 fffff880`02d8dc20 : NETIO!IndexListClassify+0x69
fffff880`02d8dae0 fffff880`0163e4f7 : fffff880`02d8dfb8 fffff880`02d8dfb8 fffff880`02d8ecf0 fffffa80`0444b3d0 : NETIO!KfdClassify+0xa4e
fffff880`02d8de50 fffff880`0163779e : fffff880`01746690 00000000`00000000 fffffa80`063a4a70 00000000`00000000 : tcpip!WfpAleClassify+0x57
fffff880`02d8de90 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : tcpip!WfpAlepAuthorizeSend+0x94e


fffff880`015a4c5a 448b442470      mov     r8d,dword ptr [rsp+70h]


SYMBOL_NAME:  NETIO!CompareSecurityContexts+6a

FOLLOWUP_NAME:  MachineOwner




FAILURE_BUCKET_ID:  X64_0x7f_8_NETIO!CompareSecurityContexts+6a

BUCKET_ID:  X64_0x7f_8_NETIO!CompareSecurityContexts+6a

Followup: MachineOwner
Ken J
My System SpecsSystem Spec