[SOLVED] Multiple BSOD all relating to NIC drivers

C

chardar

New member
Joined
Dec 13, 2013
Posts
3
I have an ongoing issue with a Dell Vostro 420 on our network. Its keeps BSOD always noting the NIC driver in the results.. AT first i though it was the Realtek driver causing the issue, tried updating it but no change, tried a different NIC (took me a few attempts to find one NOT based on the Realtek drivers!!) but still have the same issues.

I have followed the forum posting instructions here:

https://www.sysnative.com/forums/bs...ctions-windows-8-1-8-7-and-windows-vista.html

and posted my results here.

Very grateful for any help with this frustrating issue...

Things i have tried:

Updating all the main drivers (gfx, audio etc)
Changing the NIC (multiple times!)
Memtest

Ran Verifier and it throws up a 0x0000007E BSOD before windows can fully boot every time.

Thanks,

Chardar
 
Code: 
[COLOR=#ff0000]BugCheck D1[/COLOR], {4, 2, 0, 8c8f2963}

Probably caused by : [COLOR=#ff0000]E1G60I32.sys[/COLOR] ( E1G60I32+963 )

Code: 
0: kd> [COLOR=#008000]lmvm E1G60I32[/COLOR]
start    end        module name
8c8f2000 8c90f000   E1G60I32 T (no symbols)           
    Loaded symbol image file: E1G60I32.sys
    Image path: \SystemRoot\system32\DRIVERS\E1G60I32.sys
    Image name: E1G60I32.sys
    Timestamp:        [COLOR=#ff0000]Wed Sep 24 00:09:00 2008[/COLOR] (48D9770C)
    CheckSum:         00029D64
    ImageSize:        0001D000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Code: 
0: kd> [COLOR=#008000]lmvm NNSNAHSL[/COLOR]
start    end        module name
8e32e000 8e33a000   NNSNAHSL T (no symbols)           
    Loaded symbol image file: NNSNAHSL.sys
    Image path: \SystemRoot\system32\DRIVERS\NNSNAHSL.sys
    Image name: NNSNAHSL.sys
    Timestamp:        [COLOR=#ff0000]Mon Jul 01 09:39:52 2013[/COLOR] (51D14058)
    CheckSum:         000183A4
    ImageSize:        0000C000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Your Panda Security Network Activity Hook Server LWF driver seems to be conflicting with your Intel PRO/100 NDIS driver, please remove the Panda Security Network program for at least troubleshooting purposes, with the Panda Removal Procedure and then installed Microsoft Security Essentials.

Code: 
0: kd> [COLOR=#008000]knL[/COLOR]
 # ChildEBP RetAddr  
00 8039d82c 8c8f2963 nt!KiTrap0E+0x1c5
WARNING: Stack unwind information not available. Following frames may be wrong.
01 8039d89c 8039d8b4 [COLOR=#ff0000]E1G60I32+0x963[/COLOR]
02 8039d8a0 832a2cf0 0x8039d8b4
03 8039d8b4 8e3312f6 ndis!NdisFReturnNetBufferLists+0x1a
04 8039d8dc 83336b69 [COLOR=#ff0000]NNSNAHSL+0x32f6[/COLOR]
05 8039d8f4 83344137 ndis!ndisReturnNetBufferListsInternal+0x48
06 8039d908 886707c3 ndis!NdisReturnNetBufferLists+0x16
07 8039d930 833ada88 tcpip!FlpReturnNetBufferListChain+0x9a
08 8039d960 88670645 NETIO!NetioDereferenceNetBufferListChain+0xcf
09 8039d96c 88670609 tcpip!TcpFlushNetBufferLists+0x32
0a 8039d9a0 8865d0c8 tcpip!TcpFlushDelay+0x4cb
0b 8039d9cc 8865d11f tcpip!TcpPreValidatedReceive+0x23c
0c 8039d9e8 8865bac0 tcpip!TcpReceive+0x2d
0d 8039d9f8 88673c2b tcpip!TcpNlClientReceiveDatagrams+0x12
0e 8039da24 88673658 tcpip!IppDeliverListToProtocol+0x49
0f 8039da44 88673aa8 tcpip!IppProcessDeliverList+0x2a
10 8039da9c 886752c0 tcpip!IppReceiveHeaderBatch+0x1eb
11 8039db2c 886717c8 tcpip!IpFlcReceivePackets+0xbe1
12 8039dba8 886710d9 tcpip!FlpReceiveNonPreValidatedNetBufferListChain+0x6e3
13 8039dbd0 833440b0 tcpip!FlReceiveNetBufferListChain+0x104
14 8039dc04 83336d25 ndis!ndisMIndicateNetBufferListsToOpen+0xab
15 8039dc2c 83336c9c ndis!ndisIndicateSortedNetBufferLists+0x4a
16 8039dda8 8327e4a2 ndis!ndisMDispatchReceiveNetBufferLists+0x129
17 8039dde4 8327e5b3 ndis!ndisDoPeriodicReceivesIndication+0x170
18 8039de08 82cf21eb ndis!ndisPeriodicReceivesTimer+0x48
19 8039df28 82cf1dab nt!KiTimerListExpire+0x367
1a 8039df88 82cf2515 nt!KiTimerExpiration+0x22a
1b 8039dff4 82cf01d5 nt!KiRetireDpcList+0xba
1c 8039dff8 9a11fa70 nt!KiDispatchInterrupt+0x45
1d 82cf01d5 00000000 0x9a11fa70

[TD="class: small"][/TD]
 
Thanks for your reply. I have gone back to Panda support with this, and hopefully there is a fix. Our Panda security is a corporate solution and we would rather find a way forward with it if possible.
 
Hi,

Thanks for the response, we truly do appreciate it. It's good to know Panda also treats their customers with care!

I've gone ahead and marked your thread as SOLVED. Please let us know however if your have further issues.

Regards,

Patrick
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top