multiple bsod and crashes

Hello jbdred & Welcome to SevenForums.

First of all, have you read https://www.sevenforums.com/crashes-d...tructions.html, anyway I'll debug the things we have so far.

BSOD Summary

Code:

BugCheck 19, {20, fffffa80116edbf0, fffffa80116ee0e0, c4f0001}

Probably caused by : afd.sys ( afd!AfdPoll32+856 )

Followup: MachineOwner
----
STACK_COMMAND:  kb

FOLLOWUP_IP: 
SYMNETS+5f27c
fffff880`0331827c 6646392449      cmp     word ptr [rcx+r9*2],r12w

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  SYMNETS+5f27c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: SYMNETS

IMAGE_NAME:  SYMNETS.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  4dae0dbb

FAILURE_BUCKET_ID:  X64_0x50_SYMNETS+5f27c
----
STACK_COMMAND:  kb

FOLLOWUP_IP: 
SYMEVENT64x86!SYMEvent_GetSystemRootPathPtr+7ad
fffff880`04bd4f2d ff1535610000    call    qword ptr [SYMEVENT64x86!SYMEvent_GetSystemRootPathPtr+0x68e8 (fffff880`04bdb068)]

SYMBOL_STACK_INDEX:  5

SYMBOL_NAME:  SYMEVENT64x86!SYMEvent_GetSystemRootPathPtr+7ad

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: SYMEVENT64x86

IMAGE_NAME:  SYMEVENT64x86.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  4d8bcd8c

FAILURE_BUCKET_ID:  X64_0xA_SYMEVENT64x86!SYMEvent_GetSystemRootPathPtr+7ad

BUCKET_ID:  X64_0xA_SYMEVENT64x86!SYMEvent_GetSystemRootPathPtr+7ad

Followup: MachineOwner

My first advice is to uninstall Norton, and you antivirus like MSE

Report the full .dmp and we'll be happy to go further :)

Best Regards,
FredeGail

jbdred said:

My appologize for not following the forums recommended reporting structure. I will get the required information the correct way and update later.
Thanks,
Jon

No problem! You can easily follow the instructions given so far.

Best Regards,
FredeGail

Hello again!

BSOD Summary

Code:

Unable to load image \??\C:\Windows\system32\Drivers\SYMEVENT64x86.SYS, Win32 error 0n2
*** WARNING: Unable to verify timestamp for SYMEVENT64x86.SYS
*** ERROR: Module load completed but symbols could not be loaded for SYMEVENT64x86.SYS
Unable to load image \??\C:\ProgramData\Norton\{0C55C096-0F1D-4F28-AAA2-85EF591126E7}\NIS_18.1.0.37\Definitions\BASHDefs\20110723.001\BHDrvx64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for BHDrvx64.sys
*** ERROR: Module load completed but symbols could not be loaded for BHDrvx64.sys
Probably caused by : SYMEVENT64x86.SYS ( SYMEVENT64x86+19f2d )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 1E, {ffffffffc0000005, fffff800033bfdd3, 0, ffffffffffffffff}

Probably caused by : wanarp.sys ( wanarp! ?? ::NNGAKEGL::`string'+44e )

Followup: MachineOwner
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Unable to load image \SystemRoot\System32\Drivers\NISx64\1206000.01D\SYMNETS.SYS, Win32 error 0n2
*** WARNING: Unable to verify timestamp for SYMNETS.SYS
*** ERROR: Module load completed but symbols could not be loaded for SYMNETS.SYS

Could not read faulting driver name
Probably caused by : SYMNETS.SYS ( SYMNETS+5f27c )

Followup: MachineOwner

Many of your BSOD is still causing Norton. Use the Norton Removal Tool to make sure we'll not have leftover files still causing BSOD. You can use MSE instead of Norton.

Code:

0: kd> lmvm SYMEVENT64x86
start             end                 module name
fffff880`04bbb000 fffff880`04bf1000   SYMEVENT64x86 T (no symbols)           
    Loaded symbol image file: SYMEVENT64x86.SYS
    Image path: \??\C:\Windows\system32\Drivers\SYMEVENT64x86.SYS
    Image name: SYMEVENT64x86.SYS
    Timestamp:        Fri Mar 25 00:02:36 2011 (4D8BCD8C)
    CheckSum:         00031D48
    ImageSize:        00036000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Another BSOD was caused by wanarp.sys, but let's leave that until we fixed your Norton problem!

Best Regards,
FredeGail

jbdred said:

NIS2011 has been removed, cleanup tool has been run, and MSE has been installed.

I find it strange that NIS is acting up...I have used NIS for years and have had litterally no issues since the re-write in 2009.

Time will tell...I keep you posted...

Thanks for the assist.
Jon

Glad to hear it.
Well, actually, software can easily act up over the years. It's normal.

Best Regards,
FredeGail