BSOD, BSOD, BSOD (minidump files zipped)

[devane68]

The title says it all. Brand new i7 x980. Asus x58 premium. 12GB Mushkin enhanced redline. USB 3.0. SATA 6Gbps. Intel x-25MG2 160GB.
Multiple blue screens. Just this morning (Tuesday morning) it was 4 or 5 of them within about a 40 minute time frame. PC Pitstop driver scan had me update my NIC drivers. No help.
I'm hoping you forensic computer detectives can help figure this one out.
Minidumps are zipped up as are three WER XML files.
Thanks,
Ethan

 

[Payzant]

What was the error message that arrived with the BlueScreen? Was it Driver_irql_not_less_or_equal?

 

[devane68]

Here is the BlueScreenView report. To my untrained eye it looks like all the same error?

 

[Jonathan_King]

Very straightforward, your network drivers are causing the crash. Look for an updated version, on the computer manufacturer's site.

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


Loading Dump File [C:\Users\Jonathan\AppData\Local\Temp\Temp1_BSOD.zip\BSOD\040610-11668-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 (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02c52000 PsLoadedModuleList = 0xfffff800`02e8fe50
Debug session time: Tue Apr  6 07:59:42.236 2010 (GMT-4)
System Uptime: 0 days 0:11:29.718
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, fffff80002cc9591}

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

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

5: 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: fffff80002cc9591

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 fffff80002cc3469 to fffff80002cc3f00

STACK_TEXT:  
fffff880`0308eee8 fffff800`02cc3469 : 00000000`0000007f 00000000`00000008 00000000`80050033 00000000`000006f8 : nt!KeBugCheckEx
fffff880`0308eef0 fffff800`02cc1932 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`0308f030 fffff800`02cc9591 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2
fffff880`030aafb0 fffff800`02c8c842 : fffffa80`0dac3080 00000000`00000001 00000000`00000000 fffffa80`0a5e77c8 : nt!SeAccessCheckWithHint+0x301
fffff880`030ab090 fffff880`01406c5a : 1d021d02`1d021d02 e112e112`e112e112 c2e4c2e4`c2e4c2e4 f79af79a`f79af79a : nt!SeAccessCheckFromState+0x102
fffff880`030ab780 fffff880`0140494f : 19c819c8`c0000022 927f927f`00000000 1d021d02`1d021d02 e112e112`e112e112 : NETIO!CompareSecurityContexts+0x6a
fffff880`030ab7f0 fffff880`014069b5 : 8edf8edf`8edf8edf 6c096c09`6c096c09 84c884c8`84c884c8 34a534a5`34a534a5 : NETIO!MatchValues+0xef
fffff880`030ab840 fffff880`01406845 : fffffa80`09ec31e0 fffffa80`0dac7820 fffff880`030aba68 fffff880`030ac1a0 : NETIO!FilterMatch+0x95
fffff880`030ab890 fffff880`01407ccb : 00000000`00000000 00000000`00000000 fffff880`030ac1a0 fffff880`030aba50 : NETIO!IndexListClassify+0x69
fffff880`030ab910 fffff880`0163f4d0 : fffff880`030ac1a0 fffff880`030abde8 fffff880`030acb20 fffffa80`0f8b2d50 : NETIO!KfdClassify+0xa4e
fffff880`030abc80 fffff880`0163877e : fffff880`01747690 00000000`00000000 fffffa80`0cf6db00 00000000`00000000 : tcpip!WfpAleClassify+0x50
fffff880`030abcc0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : tcpip!WfpAlepAuthorizeSend+0x94e


STACK_COMMAND:  kb

FOLLOWUP_IP: 
NETIO!CompareSecurityContexts+6a
fffff880`01406c5a 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:  4a5bc18a

FAILURE_BUCKET_ID:  X64_0x7f_8_NETIO!CompareSecurityContexts+6a

BUCKET_ID:  X64_0x7f_8_NETIO!CompareSecurityContexts+6a

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

 

[devane68]

Thanks, Jonathan. No BSOD's this morning. I updated my NIC drivers yesterday. I thought I had a BSOD after the update but I might not have restarted for them to take effect at that point. We'll wait and see.
Ethan

 

[devane68]

5 BSOD's in the last hour. In trying to find solutions I read a post where someone said, "Now I know why people buy Apple products". Now I love my Windows products. I like to think that "we" have a level of understanding that no Apple person can have of their OS. But 5 BSOD's in the last hour? 10 in the last 24 hours? I only get a couple hours a day on my machine. Brand new, top of the line chip and memory and I'm stuck trying to fix it? Getting a little ridiculous.
This is the 3rd time I've started to write this post because of Blue Screens. Last 2 times were when I tried to attach a jpeg to this post so I'm not going to try and do it this time.
Event 41, Kernel-Power.
Any ideas guys?:huh:

 

[Jonathan_King]

Apple products are very stable, because all hardware is 100% compatible and the drivers are written by Apple. However, you pay for that luxury, as a 17in MacBook Pro costs literally twice as much as a similar Dell.

Now could you please upload the latest dmps?

I suspect it will still be network drivers. I suggest looking for older versions of your driver. The latest ones aren't necessarily the best; the September drivers for my video card work better than the February ones.