Blue Screen of Death because of ethernet problems How to tackle

bIASed asked on
Windows solution checking application says "You received this message because hardware or software on your computer caused Windows to shut down unexpectedly and restart. This is a serious problem, commonly referred to as a stop error or blue screen.
Although the specific cause of this problem is not known, it appears to be related to Ethernet networking."

The more specific information about it as i found in Event Viewer is
"Fault bucket 0x9F_3_POWER_DOWN_IMAGE_b57nd60x.sys, type 0"

What to do?

1 person had this question

Abuse history

The answered status icon Answer
Patrick Barker replied on


All of the recent attached DMP files are of the DRIVER_POWER_STATE_FAILURE (9f) bug check.

This bug check indicates that the driver is in an inconsistent or invalid power state.

If we run an !irp on the 4th parameter of the bug check (blocked IRP address), we get the following:

>[ 16, 2]   0 e1 85b14380 00000000 8241f2d2-851be8e8 Success Error Cancel pending
           \Driver\b57nd60x    nt!PopRequestCompletion

*** WARNING: Unable to verify timestamp for b57nd60x.sys
*** ERROR: Module load completed but symbols could not be loaded for b57nd60x.sys
Probably caused by : b57nd60x.sys

is the Broadcom NetXtreme Gigabit Ethernet NDIS6.0 Driver.

Usually when we have network related crashes like this it's due to one of two things:

1. Network drivers themselves need to be updated -

2. 3rd party antivirus or firewall is causing NETBIOS conflicts. I see and avast! driver that's loaded, so let's go ahead and remove and replace avast! with Microsoft Security Essentials for temporary troubleshooting purposes:

avast! removal tool -



If you're still crashing after all of the above, let's enable Driver Verifier to look for further device driver corruption:

Driver Verifier:

What is Driver Verifier?

Driver Verifier is included in Windows 8, 7, Windows Server 2008 R2, Windows Vista, Windows Server 2008, Windows 2000, Windows XP, and Windows Server 2003 to promote stability and reliability; you can use this tool to troubleshoot driver issues. Windows kernel-mode components can cause system corruption or system failures as a result of an improperly written driver, such as an earlier version of a Windows Driver Model (WDM) driver.

Essentially, if there's a 3rd party driver believed to be at issue, enabling Driver Verifier will help flush out the rogue driver if it detects a violation.

Before enabling Driver Verifier, it is recommended to create a System Restore Point:

Vista - START | type rstrui - create a restore point
Windows 7 - START | type create | select "Create a Restore Point"
Windows 8 -

How to enable Driver Verifier:

Start > type "verifier" without the quotes > Select the following options -

1. Select - "Create custom settings (for code developers)"
2. Select - "Select individual settings from a full list"
3. Check the following boxes -
- Special Pool
- Pool Tracking
- Force IRQL Checking
- Deadlock Detection
- Security Checks (Windows 7 & 8)
- DDI compliance checking (Windows 8)
- Miscellaneous Checks
4. Select  - "Select driver names from a list"
5. Click on the "Provider" tab. This will sort all of the drivers by the provider.
6. Check EVERY box that is [B]NOT[/B] provided by Microsoft / Microsoft Corporation.
7. Click on Finish.
8. Restart.

Important information regarding Driver Verifier:

- If Driver Verifier finds a violation, the system will BSOD.

- After enabling Driver Verifier and restarting the system, depending on the culprit, if for example the driver is on start-up, you may not be able to get back into normal Windows because Driver Verifier will flag it, and as stated above, that will cause / force a BSOD.

If this happens, do not panic, do the following:

- Boot into Safe Mode by repeatedly tapping the F8 key during boot-up.

- Once in Safe Mode - Start > type "system restore" without the quotes.

- Choose the restore point you created earlier.
If you did not set up a restore point, do not worry, you can still disable Driver Verifier to get back into normal Windows:

- Start > Search > type "cmd" without the quotes.

- To turn off Driver Verifier, type in cmd "verifier /reset" without the quotes.
・    Restart and boot into normal Windows.

How long should I keep Driver Verifier enabled for?

It varies, many experts and analysts have different recommendations. Personally, I recommend keeping it enabled for at least 24 hours. If you don't BSOD by then, disable Driver Verifier.

My system BSOD'd, where can I find the crash dumps?

They will be located in %systemroot%\Minidump

Any other questions can most likely be answered by this article:


Debugger/Reverse Engineer.
1 person found this helpful

Abuse history