BSOD ethernet lan adapter k57nd60a.sys - Windows 10 x64

PBou · Aug 12, 2015

Hi

My Broadcom Ethernet adapter driver crashes when I'm downloading from internet, no issue when downloading from a computer on my lan, no issue either from wifi adapter. I experience BSOD every time after windows diagnose the issue.

OS - Windows 8.1, 8, 7, Vista ? Windows 10 Pro upgraded from windows 7 pro OEM
· x86 (32-bit) or x64 ? x64
· What was original installed OS on system? windows 7 pro OEM
· Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from retailer)? OEM
· Age of system (hardware) 2010
· Age of OS installation - have you re-installed the OS? Yes 2013 after upgrading HDD for SSD
· CPU Intel(R) Core(TM) i7 CPU M 620 @ 2.67GHz, 2667 Mhz, 2 Core(s), 4 Logical Processor(s)
· Video Card ATI Mobility Radeon HD 4670
· MotherBoard - (if NOT a laptop)
· Power Supply - brand & wattage (if laptop, skip this one)
· System Manufacturer DELL
· Exact model number (if laptop, check label on bottom) studio XPS 1647 model PP35L
· Laptop or Desktop? Laptop
· Ethernet adapter ? Broadcom NetLink (TM) Gigabit Ethernet Broadcom BCM5784M LAN
· Ethernet adapter Driver? k57nd60a.sys Broadcom version 15.6.1.2

OneDrive reports and dump files: Microsoft services

I which we could fix the issue because downgrade to win 7 pro isn't working probably due to some system restores.

Pierre

x BlueRobot · Aug 12, 2015

Code:

[COLOR=#ff0000]BugCheck 9F[/COLOR], {[COLOR=#0000cd]4[/COLOR], 12c, [COLOR=#008000]ffffe00094681040[/COLOR], fffff8017dc10af0}

Implicit thread is now ffffe000`94681040
Probably caused by : pci.sys

The stack of the thread does support the type of bugcheck your experiencing, and the driver which is responsible is easy to find. As you have mentioned, yes the error is a consequence of your Network Adapter driver.

Code:

0: kd> [COLOR=#008000]!thread ffffe00094681040[/COLOR]
GetPointerFromAddress: unable to read from fffff8017bc391c0
THREAD ffffe00094681040  Cid 0004.00c8  Teb: 0000000000000000 Win32Thread: 0000000000000000 WAIT: (Executive) KernelMode [COLOR=#ff0000]Non-Alertable[/COLOR]
    [COLOR=#ff0000]ffffd00197162d58[/COLOR]  SynchronizationEvent
IRP List:
    [COLOR=#0000cd]ffffe000ff9d3d30[/COLOR]: (0006,02c8) Flags: 00000000  Mdl: 00000000
Not impersonating
GetUlongFromAddress: unable to read from fffff8017bb87fe8
Owning Process            ffffe00093021680       Image:         System
Attached Process          N/A            Image:         N/A
fffff78000000000: Unable to get shared data
Wait Start TickCount      169573       
Context Switch Count      722412         IdealProcessor: 0  NoStackSwap
ReadMemory error: Cannot get nt!KeMaximumIncrement value.
UserTime                  00:00:00.000
KernelTime                00:00:00.000
Win32 Start Address nt!ExpWorkerThread (0xfffff8017b8ec5c0)
Stack Init ffffd00197163dd0 Current ffffd001971629b0
Base ffffd00197164000 Limit ffffd0019715e000 Call 0
Priority 15 BasePriority 12 UnusualBoost 0 ForegroundBoost 0 IoPriority 2 PagePriority 5
Child-SP          RetAddr           : Args to Child                                                           : Call Site
ffffd001`971629f0 fffff801`7b8b90d0 : ffffe000`00000000 00000000`00000001 fffff801`7bc4d340 ffffe000`94681140 : nt!KiSwapContext+0x76
ffffd001`97162b30 fffff801`7b8b8ae8 : ffffe000`94681040 ffffe000`94681180 00000000`00000000 00000000`00000000 : nt!KiSwapThread+0x160
ffffd001`97162be0 fffff801`7b8bad35 : fffff801`7baedee8 00000000`00000000 ffffe000`95fff920 fffff800`97677d77 : nt!KiCommitThreadWait+0x148
ffffd001`97162c70 fffff801`7b945ab8 : ffffd001`97162d58 ffffc000`00000000 00000000`00000000 fffff801`7bd22f00 : nt!KeWaitForSingleObject+0x385
ffffd001`97162d20 fffff800`97675bb7 : ffffe000`977d8a50 ffffffff`00000003 00000000`00000000 fffff801`7bd201cc : nt!ExWaitForRundownProtectionReleaseCacheAware+0xb8
ffffd001`97162d90 fffff800`976753a8 : 00000000`00000001 00000000`00000001 fffff801`7bd22f00 ffffd001`9716305c : tcpip!FlpUninitializePacketProviderInterface+0x57
ffffd001`97162dd0 fffff800`96cf1a1c : ffffe000`97780c10 ffffd001`97162fb0 ffffe000`949e3620 ffffe000`977d8a50 : tcpip!FlPnpEvent+0x138
ffffd001`97162e70 fffff800`96d399c6 : 00000000`c00000bb ffffd001`97162fb0 ffffe000`949e3620 ffffe000`97780c10 : ndis!ndisDeliverNetPnPEventSynchronously+0x70
ffffd001`97162eb0 fffff800`96d00659 : ffffd001`97163100 ffffd001`97163179 ffffd001`97163100 ffffe000`96dd11a0 : ndis!ndisPnPNotifyBinding+0xe2
ffffd001`97163090 fffff800`96d00600 : ffffe000`97780c10 00000000`00000000 00000000`00000005 00000000`00000000 : ndis!ndisPnPNotifyBindingUnlocked+0x35
ffffd001`971630e0 fffff800`96d0054f : 00000000`00000001 00000000`00000000 ffffc000`b5439630 00000000`00000000 : ndis!ndisPauseProtocolInner+0x68
ffffd001`971631e0 fffff800`96cf269a : ffffe000`96dd11a0 ffffd001`97163320 ffffe000`96dd25f8 00000000`00000001 : ndis!ndisPauseProtocol+0x63
ffffd001`97163220 fffff800`96cf2234 : 00000000`00000000 00000000`00000000 00000000`00000000 ffffe000`96dd25f8 : ndis!Ndis::BindEngine::Iterate+0x3fe
ffffd001`97163450 fffff800`96cf2036 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff800`96cf218a : ndis!Ndis::BindEngine::UpdateBindings+0x34
ffffd001`97163480 fffff800`96d3657b : ffffe000`96dd11a0 ffffe000`96964930 ffffe000`96964930 00000000`00000000 : ndis!Ndis::BindEngine::ApplyBindChanges+0x92
ffffd001`971634d0 fffff800`96ceaac2 : ffffe000`96dd11a0 ffffe000`96dd1050 ffffe000`96dd11a0 fffff800`96c6ba35 : ndis!ndisPnPRemoveDevice+0x18b
ffffd001`97163720 fffff800`96d3c1e2 : ffffe000`96dd11a0 ffffe000`96dd1050 00000000`00000000 ffffe000`ff9d3d00 : ndis!ndisPnPRemoveDeviceEx+0x82
ffffd001`97163770 fffff800`96cefd2a : ffffe000`ff9d3d30 ffffd001`97163810 00000000`00000000 ffffe000`96dd11a0 : [COLOR=#ff0000]ndis!ndisPnPIrpRemoveDevice+0x6d5a[/COLOR]
ffffd001`971637d0 fffff801`7bccdd90 : ffffe000`96dd1001 ffffe000`96dd1050 ffffd001`97163801 ffffc000`c41d9060 : ndis!ndisPnPDispatch+0x21a
ffffd001`97163840 fffff801`7bcebcbf : 00000000`00000002 ffffe000`947985b0 ffffe000`94798010 ffffe000`947985b0 : nt!IopSynchronousCall+0xe0
ffffd001`971638b0 fffff801`7b8ff613 : ffffc000`c2fc25c0 ffffe000`94798010 00000000`00000001 00000000`0000000a : [COLOR=#ff0000]nt!IopRemoveDevice+0xdf[/COLOR]
ffffd001`97163960 fffff801`7bceb943 : ffffe000`94798010 ffffe000`00000016 00000000`00000000 00000000`00000016 : [COLOR=#ff0000]nt!PnpRemoveLockedDeviceNode+0xf3[/COLOR]
ffffd001`971639b0 fffff801`7bceb6a1 : 00000000`00000000 ffffd001`97163a30 ffffc000`c2ccb080 ffff4d86`4bffb192 : nt!PnpDeleteLockedDeviceNode+0x4b
ffffd001`971639f0 fffff801`7bceb2f9 : ffffe000`947985b0 ffffd001`00000002 ffffe000`947985b0 ffffe000`94798010 : nt!PnpDeleteLockedDeviceNodes+0xb1
ffffd001`97163a60 fffff801`7bd675b5 : ffffc000`c2fc2500 ffffc000`c40ac300 ffffd001`00000001 ffffc000`00000000 : nt!PnpProcessQueryRemoveAndEject+0x5fd
ffffd001`97163bd0 fffff801`7bd66d20 : ffffc000`c2fc25c0 00000000`00000000 ffffd001`97163c80 00000000`00000001 : nt!PnpProcessTargetDeviceEvent+0xd9
ffffd001`97163c10 fffff801`7b8ec6a9 : fffff801`7bc4d340 ffffe000`94681040 ffffe000`9a68c6d0 fffff801`7bc4d340 : nt!PnpDeviceEventWorker+0x33c
ffffd001`97163cb0 fffff801`7b95a948 : ffffe000`93021680 00000000`00000080 fffff801`7bc4d340 ffffe000`94681040 : nt!ExpWorkerThread+0xe9
ffffd001`97163d40 fffff801`7b9c6de6 : ffffd001`9d396180 ffffe000`94681040 ffffe000`93144040 00000000`00000000 : nt!PspSystemThreadStartup+0x58
ffffd001`97163da0 00000000`00000000 : ffffd001`97164000 ffffd001`9715e000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16

I'll assume (without looking at the power states), that the device was being powered down and thus the reason why it would unmounted and then removed from the device tree. If we examine the IRP which was associated with the thread, then we can see the nature of the IRP request.

Code:

0: kd> [COLOR=#008000]!irp ffffe000ff9d3d30[/COLOR]
Irp is active with 3 stacks 3 is current (= 0xffffe000ff9d3e90)
 No Mdl: No System Buffer: Thread ffffe00094681040:  Irp stack trace.  
     cmd  flg cl Device   File     Completion-Context
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    

            Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    

            Args: 00000000 00000000 00000000 00000000
>[IRP_MJ_PNP(1b), IRP_MN_REMOVE_DEVICE - (2)]
            0  0 ffffe00096dd1050 00000000 00000000-00000000    
          \Driver\[COLOR=#ff0000]k57nd60a[/COLOR]
            Args: 00000000 00000000 00000000 00000000

The IRP indicates to use that the device object representing your network adapter has failed to sychronize correctly with the PnP Manager. Why this is the case? There is could lots of different reasons, but the driver responsible for the device could be possibly outdated, and therefore I would recommend that update that driver.

Code:

0: kd> [COLOR=#008000]lmvm k57nd60a[/COLOR]

start             end                 module name
fffff800`9b4f0000 fffff800`9b55b000   k57nd60a T (no symbols)           
    Loaded symbol image file: k57nd60a.sys
    Image path: \SystemRoot\System32\drivers\k57nd60a.sys
    Image name: k57nd60a.sys
    Timestamp:        [COLOR=#ff0000]Wed Jan 30 00:48:55 2013[/COLOR] (51086DF7)
    CheckSum:         000709BB
    ImageSize:        0006B000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

You can find the support page for the driver here - Downloads | Broadcom

The thread won't be able to complete the necessary I/O processing until it has switched to an Alterable state, and this will not happen until the driver has correctly handled the IRP. For more information on the bugcheck, please read this guide - https://www.sysnative.com/forums/bs...11910-complete-guide-debugging-stop-0x9f.html

x BlueRobot · Aug 12, 2015

I forgot to mention, have you checked the driver is even compatible with Windows 10?

PBou · Aug 12, 2015

x BlueRobot said:
I forgot to mention, have you checked the driver is even compatible with Windows 10?

No, I can't find anything from google where could I can check compatibility with Win 10?

Latest k57nd60a.sys from Broadcom is version 15.6.0.10 dated 2013-01-29. Windows came with version 15.6.1.2.

Looks like Windows 10 wont work well on my 5 years old Dell XPS laptop. I'll check on Dell forum.

x BlueRobot · Aug 18, 2015

That's quite old, there should be a Windows Compatibility checker - http://www.microsoft.com/en-us/windows/compatibility/CompatCenter/Home

BSOD ethernet lan adapter k57nd60a.sys - Windows 10 x64

PBou

New member

x BlueRobot

Administrator

x BlueRobot

Administrator

PBou

New member

x BlueRobot

Administrator