Clean instalation of HP Probook 6560b - BSOD 1000009f

Update the drivers to:

• Realtek RTL8187 Wireless 802.11b/g 54Mbps USB 2.0 Network Adapter: Driver Reference Table - rtl8187.sys
• Wi-Fi Broadcom 4313GN 802.11b/g/n 1x1: Downloads | Broadcom

Also:

Code:

fffff880`031b5a48  fffffa80`058bd600Unable to load image C:\Program Files\ESET\ESET NOD32 Antivirus\em018_64.dat, Win32 error 0n2
*** WARNING: Unable to verify timestamp for em018_64.dat
*** ERROR: Module load completed but symbols could not be loaded for em018_64.dat
 em018_64+0x63600

Uninstall Nod32, at least as a test. Use Microsoft Security Essentials as your antivirus with windows inbuilt firewall, and free MBAM as the on demand scanner.

Let us know the results.

I searched, but not found anything better than that is installed. So did not suggested anything specific.

At a point you may need to change your network adapter.

tomashewk said:

Unfortunatelly, it is laptop so changing WiFi adapter is not that easy. You have noticed any particular problem with the WiFi drivers in the minidump report?

Changing a USB adapter is never "not that easy".

Code:

Realtek RTL8187 Wireless 802.11b/g 54Mbps USB 2.0 Network Adapter

And, there is no other reason that I am saying it to you.

That I quoted there.

There are disclosed issue with WiFi in the minidumps, but not driver specific. So I checked the dates to the wireless adapters. Both seemed sort of old, and no update to neither was available.

A stop 0x9F (or any variant thereto) is basically a driver issue. Specifically, a PnP driver fails to react within the specified time when you wake up the computer/hardware component from hibernate/sleep.

Like any other antivirus, Nod32 affects the network adversely (as per their architecture). And, it is the case here. So removing it will be a necessary step.

But the base issue is a PnP device driver for a WiFi device (USB or PCI). And we have old drivers there. Even if they are not failing on themselves right now (we cannot say it with 100% certainty, as we have visible nod32 failure), very soon they will start to act up. That is why I said it in #4.

Arc said:

At a point you may need to change your network adapter.

As you asked for assistance, I think my duty is to explain the situation to you. That is what I have done. I know that people does not like to listen anything adverse to their system/settings etc. Analysis and interpretation is always the leg job.

Anyway, you gave me hard time, and I had to spend a time to make you understand it.