Windows 7 BSOD's just started on 3 month old system

[SevenD]

Hello, I have a home built system, my second in a few years. I'm running windows 7 prof. 64bit. I will include CPU-Z info below to help identifiy my system specs. It first happened a few days ago while watching a video from e-mail attachment. It seem to happen while watching youtube videos and once while son was playing a small video game. This seems to be a problem as there are many psots online. I ran windows memory diagnostic with no problems noted. If anyone can help it would be great!!! Memory is G Skill, Asus M4A89GTD PRO/USB3 Motherboard. AMD Phenom 2 965.

Link RemovedLink RemovedLink RemovedLink RemovedLink RemovedThanks, SevenD

 

[Trouble]

Your most recent dump file identifies
Netio.sys and vsdatant.sys
Which indicates a problem with ZoneAlarm
Remove zone alarm from your system and see if the blue screens persist.

 

[Elmer]

Hi SevenD and Welcome to The Forum

Your last half dozen dump files all give a stop error of 0x7F. Its a stop error that ZoneAlarm firewall gives frequently. You have two (?) options:
ZoneAlarm Firewall is known to be a cause of BSOD's on many Windows 7 systems. Download the ZoneAlarm Remover - Link Removed due to 404 Error. Uninstall ZoneAlarm through Programs and Features. Boot to safe mode and run the ZoneAlarm Remover. Reboot. Make sure that Windows Firewall is enabled.
Alternatively
Try this Microsoft hotfix if you wish to try and keep ZoneAlarm: Stop Error 0x07F when you run apps. that transfer data by the UDP protocol in Win 7. I can neither verify or discount this fix. It may work, it may not.

I'll update this post when I've been through your latest dump file.


Damn that Fast Fingers Trouble!!

Drivers with Updates:

Rt64win7.sys Mon May 31 04:46:43 2010 Link Removed

RTKVHD64.sys Fri Jan 29 06:48:35 2010 Link Removed

You might want to visit your Mobo Mfr. site. There are newer drivers also available for USB 3.0
nusb3hub.sys Fri Apr 23 02:34:35 2010
nusb3xhc.sys Fri Apr 23 02:34:36 2010

And that's your lot.

Let us know how it goes.

HTH.

 

[Trouble]

Yep. And according to recent research, all newer versions of ZoneAlarm have embedded within the program the built-in removal tool. So depending on the version installed it may not be necessary anymore to download the vendor specific proprietary uninstaller/removal tool. Just use Start->Programs->ZoneAlarm->Uninstall Zone Alarm (suppose to be the same thing as the old tool.
But thanks for your confirmation of my best guess.
And by the way SevenD, welcome to the forums.
Regards Randy

 

[nmsuk]

Hi SevenD

I've also noticed your RAM Timings are misconfigured. The SPD info in cpu-z states the memory should have a Command Rate of 2T but it's set at 1T. The setting can be found in the bios probably under performance or advanced chipset. On an ASUS board it could be under AI Tweaker or OC Tweaker though.

 

[SevenD]

I was wondering about the "ntoskrnl.exe" error that seems to be the most of?

Thanks, SevenD

 

[Elmer]

All the dumps I looked at blame NETIO.SYS.

Stop 7F + NETIO.SYS = If ZA present, look no further.

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

Use !analyze -v to get detailed debugging information.

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

Probably caused by : [B][COLOR=#ff0000]NETIO.SYS [/COLOR][/B]( NETIO!CompareSecurityContexts+6a )

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

2: 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: fffff80002c94d91

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 fffff80002c8ec69 to fffff80002c8f700

STACK_TEXT:  
fffff880`02f69ce8 fffff800`02c8ec69 : 00000000`0000007f 00000000`00000008 00000000`80050031 00000000`000006f8 : nt!KeBugCheckEx
fffff880`02f69cf0 fffff800`02c8d132 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`02f69e30 fffff800`02c94d91 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2
fffff880`0aaa8fa0 fffff800`02c57f32 : fffffa80`068b78f0 00000000`00000001 00000000`00000000 fffffa80`049767c8 : nt!SeAccessCheckWithHint+0x301
fffff880`0aaa9080 fffff880`01576c5a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!SeAccessCheckFromState+0x102
fffff880`0aaa9770 fffff880`0157494f : 00000000`c0000022 00000000`00000000 00000000`00000000 00000000`00000000 : NETIO!CompareSecurityContexts+0x6a
fffff880`0aaa97e0 fffff880`015769b5 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : NETIO!MatchValues+0xef
fffff880`0aaa9830 fffff880`01576845 : fffffa80`04f67480 fffffa80`0670dbc0 fffff880`0aaa9a58 fffff880`0aaaa190 : NETIO!FilterMatch+0x95
fffff880`0aaa9880 fffff880`01577ccb : 00000000`00000000 00000000`00000000 fffff880`0aaaa190 fffff880`0aaa9a40 : NETIO!IndexListClassify+0x69
fffff880`0aaa9900 fffff880`0163d3a7 : fffff880`0aaa9dd8 fffff880`0aaa9dd8 fffff880`0aaaab10 fffffa80`03bf7950 : NETIO!KfdClassify+0xa4e
fffff880`0aaa9c70 fffff880`016367ee : fffff880`01745690 00000000`00000000 fffffa80`06277a70 00000000`00000000 : tcpip!WfpAleClassify+0x57
fffff880`0aaa9cb0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : tcpip!WfpAlepAuthorizeSend+0x94e


STACK_COMMAND:  kb

FOLLOWUP_IP: 
NETIO!CompareSecurityContexts+6a
fffff880`01576c5a 448b442470      mov     r8d,dword ptr [rsp+70h]

SYMBOL_STACK_INDEX:  5

SYMBOL_NAME:  NETIO!CompareSecurityContexts+6a

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: NETIO

IMAGE_NAME:  [COLOR=#ff0000][B]NETIO.SYS[/B][/COLOR]

DEBUG_FLR_IMAGE_TIMESTAMP:  4bbe946f

FAILURE_BUCKET_ID:  X64_0x7f_8_NETIO!CompareSecurityContexts+6a

BUCKET_ID:  X64_0x7f_8_NETIO!CompareSecurityContexts+6a

Followup: MachineOwner

 

[Trouble]

Just for informational purposes will anyone who might read this thread please not upload individual .dmp files one at a time or in groups. Put them into a folder on your desktop and zip up that folder and attach them that way. It makes it way more easy to get them locally for analysis.
Thank You
Randy

 

[SevenD]

Thank you all for the quick replies. I am going to try the zone alarm uninstall. Also my memory modules are sold as 7-7-7-21 but I notice they are running at 9-9-9-24. I don't know if this could be a problem...and is the 2T command a likely problem? I'll post the results after testing. It's funny that the crashes seem to happen while watching video or something with sound.

Thanks, SevenD

 

[nmsuk]

With your memory are you using the epp\xmp profile? I think that sets the memory to ddr3 1333 with 9-9-9-24-2T. Best you uninstall ZA before we go checking your memory settings.

 

[SevenD]

I have been testing the system all afternoon and evening and it appears that the BSOD problem was in fact zone alarm. I'm running MSE and Windows firewall for now. Many thanks to Elmer, Trouble and nmsuk for your help.

Thanks, SevenD

 

[Elmer]

Thanks for the feedback Seven.

 

[SevenD]

Just an afterthought... are there any other firewall anti-virus programs better than MSE Windows firewall or is it worth trying the Zone Alarm patch? Just wondering.

SevenD

 

[nmsuk]

I wouldn't use ZA as that was the problem. If your using a router, Microsoft's firewall is fine.