Software- or Configuration-related Crashes

Apparently it is your network driver that is failing here.

Code:

BugCheck D1, {18, 2, 0, fffff88001596a88}

Probably caused by : NETIO.SYS ( NETIO!WeightCompare+8 )

Followup: MachineOwner
---------------------------------------------------------------------------------------------------------
BugCheck D1, {0, 2, 0, fffff88001405a9d}

Probably caused by : NETIO.SYS ( NETIO!WeightCompare+1d )

Followup: MachineOwner
----------------------------------------------------------------------------------------------------------
BugCheck 3B, {c0000005, fffff8800165ea88, fffff8800ae9a020, 0}

Probably caused by : NETIO.SYS ( NETIO!WeightCompare+8 )

Followup: MachineOwner
---------

It may fail due to a lot of reasons like an outdated adapter driver, a virus, or an ambitious antivirus. For more detailed analysis, upload your MSINFO32.nfo file.

1. Click on the start button
2. Type "msinfo32" (without quotes) in the search bar of the start menu, click the resulting link. It will open the System Information window.
3. File>Save. In the "File Name" filed, put "MSINFO32" (without Quote), give the save location to desktop, and click the "save" button.
4. Give the time for processing, it will save a .nfo file on your desktop.
5. Zip it, and upload it following the instruction.

Lol ... not very happy to see you again, at the same place :)

Last time we updated the network drivers .... not seeing anything very interesting in your crash dumps or msinfo32. So let us go for some tests?

Scan the system for possible virus infection with the following programs.

• Anti-rootkit utility TDSSKiller
• Windows Defender Offline

And then enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any. Post it following the Blue Screen of Death (BSOD) Posting Instructions.

The verifier enabled BSOD is caused by network driver ....

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {0, 2, 0, fffff880016718c9}

Probably caused by : NETIO.SYS ( NETIO!IndexListClassify+50 )

Followup: MachineOwner
---------

But it is not specifying which one was in use at that time, so I am checking the both.

Realtek PCIe GBE Family Controller

Code:

fffff880`04800000 fffff880`04884000   Rt64win7   (deferred)             
    Image path: \SystemRoot\system32\DRIVERS\Rt64win7.sys
    Image name: Rt64win7.sys
    Timestamp:        Mon May 16 20:23:31 2011 (4DD13A6B)
    CheckSum:         000859EC
    ImageSize:        00084000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

So it is very old. Update it from Realtek, take the Win7 and WinServer 2008 R2 Auto Installation Program (SID:1581786), dated 2013/5/22.

D-Link DWA-125 Wireless N 150 USB Adapter(rev.A2) driver .....

Code:

fffff880`02a58000 fffff880`02beb000   Dnetr28ux   (deferred)             
    Image path: \SystemRoot\system32\DRIVERS\Dnetr28ux.sys
    Image name: Dnetr28ux.sys
    Timestamp:        Thu Apr 28 11:48:18 2011 (4DB906AA)
    CheckSum:         00193FD2
    ImageSize:        00193000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

This is also old. In this link D-Link | DWA-125 Wireless N150 USB Adapter, take the driver and try. If it does not work, search for your hardware version.

Free up the startup. Windows does not need any other program to auto start with it, but the auto start programs often conflicts and causes various problems including BSODs.

1. Click on the Start button
2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
3. Select the “Startup” tab.
4. Deselect all items other than the antivirus.
5. Apply > OK
6. Accept then restart.

Let us know the results.

Its ok mate :)
Waiting for the belated report, but wish you all the best :)

Another network relate issue, continuing.

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff8800167caaa, fffff8800bd14540, 0}

Probably caused by : NETIO.SYS ( NETIO!IsFilterBypassAvailable+2a )

Followup: MachineOwner
------------------------------------------------------------------------------------------------------
fffff880`0bd143f8  fffff880`01672000 NETIO!PtpSwapWithSuccessor <PERF> (NETIO+0x0)
fffff880`0bd14400  fffff880`016c1e7c NETIO!WPP_MAIN_CB <PERF> (NETIO+0x4fe7c)
fffff880`0bd14408  fffff880`01672000 NETIO!PtpSwapWithSuccessor <PERF> (NETIO+0x0)
fffff880`0bd14410  fffff880`016c1ef4 NETIO!WPP_MAIN_CB <PERF> (NETIO+0x4fef4)
fffff880`0bd14418  fffff880`01672000 NETIO!PtpSwapWithSuccessor <PERF> (NETIO+0x0)
fffff880`0bd14420  fffff880`016c1fa8 NETIO!WPP_MAIN_CB <PERF> (NETIO+0x4ffa8)
fffff880`0bd14428  fffff880`01800000 tcpip!OlmQuerySystemConnectionOffloadSupportCommon <PERF> (tcpip+0x0)
fffff880`0bd14430  fffff880`019a7d04 tcpip!LowMemoryEvent <PERF> (tcpip+0x1a7d04)
fffff880`0bd14438  fffff880`01800000 tcpip!OlmQuerySystemConnectionOffloadSupportCommon <PERF> (tcpip+0x0)
fffff880`0bd14440  fffff880`019a7d4c tcpip!LowMemoryEvent <PERF> (tcpip+0x1a7d4c)
fffff880`0bd14448  fffff880`01800000 tcpip!OlmQuerySystemConnectionOffloadSupportCommon <PERF> (tcpip+0x0)
fffff880`0bd14450  fffff880`019a7d1c tcpip!LowMemoryEvent <PERF> (tcpip+0x1a7d1c)
fffff880`0bd14458  fffff880`01800000 tcpip!OlmQuerySystemConnectionOffloadSupportCommon <PERF> (tcpip+0x0)
fffff880`0bd14460  fffff880`019a7ec0 tcpip!LowMemoryEvent <PERF> (tcpip+0x1a7ec0)
fffff880`0bd14468  fffff880`01800000 tcpip!OlmQuerySystemConnectionOffloadSupportCommon <PERF> (tcpip+0x0)
fffff880`0bd14470  fffff880`019a7e78 tcpip!LowMemoryEvent <PERF> (tcpip+0x1a7e78)
fffff880`0bd14478  fffff880`01800000 tcpip!OlmQuerySystemConnectionOffloadSupportCommon <PERF> (tcpip+0x0)

Nothing showing more as problem. Only thing I can find that the D-Link DWA-125 Wireless N 150 USB Adapter driver is not updated yet.

Code:

fffff880`0c23a000 fffff880`0c3cd000   Dnetr28ux   (deferred)             
    Image path: \SystemRoot\system32\DRIVERS\Dnetr28ux.sys
    Image name: Dnetr28ux.sys
    Timestamp:        Thu Apr 28 11:48:18 2011 (4DB906AA)
    CheckSum:         00193FD2
    ImageSize:        00193000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

A dongle with a backdated driver is always problematic. Is not there any update available?