Norton Internet Security / Norton AntiVirus

[jh5646]

After installing NIS 2010, I starting receiving regular BSOD crashes with 0x0000007F and the parameters showing a "Double Fault".

At first I thought something was wrong with my installation so I reinstalled Windows 7 several times from scratch. I later found the thread in this forum titled "NETIO.SYS & SYMTDIV.SYS BSOD on Win7 RTM with NAV 2010 - ( 09-12-2009 )" which, for reasons I do not understand, is marked as "Solved".

This issue remains a problem.

It is important because the recommended solution is to disable NetBIOS over TCP/IP which, in effect, cripples my Windows 7 system as a member of a workgoup / homegroup. This is not a solution and really is not an effective work around.

Will this issue be fixed in an upcoming release? Will it be an NIS release? A Microsoft Windows Update? A Hotfix?

What became of the joint Microsoft / Symantec investigation referenced by "Simon" on 9-14-2009?

What happened with respect to "Microsoft is currently evaluating this problem for a possible fix in the future" referenced by Peter_Linhardt on 9-16-2008?

Here is the information from my 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: fffff80002acd591

[delphinium Norton Fighter]

jh5646:

Did you check the Win 7 compatibility utility before installing?  Intel has a Management Engine Interface problem that can cause this as well.  I also have an Intel machine.  Have you checked to make sure that you have all of the updated drivers, including an MEI patch?  It seems to have soothed my machine.

[jh5646]

Thanks delphinium.

I looked up the Intel “Management Engine Interface” and it appears to be specific to Intel motherboards. Mine is an ASUS P6X58D Premium motherboard. Although it has an Intel Chipset, I don’t think this applies since I don’t have an Intel motherboard. Do you agree?

When I turned off “NetBIOS over TCP/IP”, the crashes immediately stopped. My problem is that the work around (turn off “NetBIOS over TCP/IP”) cripples my Windows 7 system as a member of a workgoup / homegroup. This is not a solution and really is not an effective work around.

Here is my system configuration (all components are brand new):

Motherboard: ASUS P6X58D Premium

CPU: Intel Core i7-920 (2.66GHz x 4)

Memory: OCZ Gold 6GB (3 x 2GB) Model OCZ3G1600LV6GK

Graphics: ASUS ENGTS250 DK/DI/1G GeForce GTS 250 1GB PCI Express 2.0 x16

Hard Drives: 3 x WD5000AADS Caviar Green drives in a RAID 5 configuration

Optical Drive: ASUS SATA CD/DVD Burner Model DRW-24B1ST

All Windows / Microsoft updates are applied. All drivers are the latest version from the manufactures. I have the latest BIOS for the motherboard.

I would be happy to upload my crash / dump information. However, after studying the other thread referenced in my post, it appears that this is already diagnosed a stack issue. Unfortunately, the previous thread is marked as "Solved" and cannot be added to. I was hoping to shed some light on the implications of this work around and push for a solution to this issue. Having a powerhouse machine that is an island in my network is not really a workable solution.

[delphinium Norton Fighter]

Yes, it's too nice a setup to be left all alone.  Hopefully one of the Symantec reps can make some suggestions, or another user with a similar configuration. 

[reese_anschultz]

jh5646,

As indicated in the thread NETIO.SYS & SYMTDIV.SYS BSOD on Win7 RTM with NAV 2010, Microsoft is currently evaluating a fix for the future. Unfortunately I'm not privy to Microsoft's release plans. The bug is in Microsoft's NetBIOS over TCP code and the only known workaround at this time is to disable this Windows feature.

[Vineeth]

Hi jh5646,

Is it possible for you to get  me the small memory dump? Once you have the dump, I will help you in uploading the files.

Also when the crash occurs, are you able to boot in to safe mode?

Vineeth

[jh5646]

Reese,

Thanks for the clarification. It was not completely clear to me from the previous thread that it is, in fact, a Microsoft bug. Since Windows comes with NetBIOS over TCP/IP enabled, shouldn't this be a problem for more people? Or is this a rare occurrence? If its rare, any idea what other factors may contribute so that I may be able to eliminate them instead of NetBIOS and start sharing files and my printer again?

Secondly, I suspect that you (whether through your company or not) have much greater influence on Microsoft than me, a single windows user. Is there any way to find out their plans regarding this issue? Is there any way, as a community, to put a little pressure on them for a fix? It's been 4 or 5 months.

Thanks again for your input.

John

[reese_anschultz]

---

jh5646 wrote:

Reese,

Thanks for the clarification. It was not completely clear to me from the previous thread that it is, in fact, a Microsoft bug. Since Windows comes with NetBIOS over TCP/IP enabled, shouldn't this be a problem for more people? Or is this a rare occurrence? If its rare, any idea what other factors may contribute so that I may be able to eliminate them instead of NetBIOS and start sharing files and my printer again?

Secondly, I suspect that you (whether through your company or not) have much greater influence on Microsoft than me, a single windows user. Is there any way to find out their plans regarding this issue? Is there any way, as a community, to put a little pressure on them for a fix? It's been 4 or 5 months.

Thanks again for your input.

John

---

I'm not sure why one person would see this and another wouldn't. I'll ask one of our developers again about this but before posting my last message I did inquire whether there is any other way to remedy the problem.

As stated before, Microsoft is aware of the problem. We brought it to their network developers' attention and they found the problem but were unclear about when a fix would be made available. We also know that some of their other teams are concerned about the issue because they approached us about it last week, at which point we point them to their network team.