BSOD while using Utorrent error 0x000000D1

[Karl Ash]

Been having frequent BSOD recently and as far as i can tell it's only happening when im running Utorrent. I get the following in the BSOD, DRIVER_IRQL_NOT_LESS_OR_EQUAL followed by the stop code in the title and NETIO.SYS. I used the SF Diagnostics Tool and will link the Zip file now, hopefully i have done this correctly, all and any help will be appreciated, thanks alot for your time.

View attachment 253548

 

[Arc]

Hello Karl.

fffff880`035a8788  fffff880`010c84ee [COLOR=Red]ataport[/COLOR]!IdePortDispatch+0x16
fffff880`035a8718  fffff880`010d17cb [COLOR=Red]ataport[/COLOR]!RefPdoWithTag+0x33
fffff880`035a8648  fffff880`010cf204 [COLOR=Red]ataport[/COLOR]!IdeLunQueueInsert+0x110
fffff880`035a8448  fffff880`010c2c74 [COLOR=Red]ataport[/COLOR]!IdeLogCrbActive+0xe0
fffff880`035a8370  fffff880`010d71a0 [COLOR=Red]ataport[/COLOR]!WPP_MAIN_CB

Scan the system for possible virus infection.

• Anti-rootkit utility TDSSKiller
• Windows Defender Offline

update the network driver.
First, download the network card driver from manufactuer's website, Realtek
Then reinstall the driver as follows:

1. Click the Start Button, type "devmgmt.msc" (without quotation marks) in the Start Menu Search box and press Enter.
2. Double click to expand "Network adaptors".
3. Right click your network card and click Uninstall.
4. Check "Delete driver software for this device" check box, click OK.
5. Restart the computer
6. If windows does not auto configure the appropriate drivers at startup, install the downloaded one manually.

Let us know the results.

 

[Karl Ash]

Hi Arc thanks for replying to me so fast, so i scanned with the Anti-rootkit utility TDSSKiller (wasn't sure if i was ment to use both links) and found no threats or problems.

As far as the Network Driver goes i followed the instructions and it was configured at start up, if this was the fix to the BSOD i will get back to you either when i get another BSOD or in a day or 2 because the infrequency at which they happen is very odd, i've gone days without one and then i would get 2-3 in a few hours.

Thanks again for the speedy post, i will keep an eye on this thread in case there's anything else you want me to do.

 

[Karl Ash]

Hey again, sorry to bring my problem back to you guys but i just got another BSOD. I'm really stumped on how to fix this issue, i have read more forums then i care to admit and tried alot all to no avail, i'll attach my latest DMP File in case their is anything you can suggest, thanks in advance for your help.

View attachment 253573

 

[Arc]

Lamost the same situation, but a bit elaborate. I am summarizing the dump's report here:

[COLOR=Red]BugCheck D1[/COLOR], {28, 2, 0, fffff880019356fd}

*** WARNING: Unable to verify timestamp for ndis.sys
*** ERROR: Module load completed but symbols could not be loaded for ndis.sys
[COLOR=Red]Probably caused by : NETIO.SYS [/COLOR]( NETIO!RtlCopyBufferToMdl+1d )

Followup: MachineOwner
----------------------------------------------------------------------------------------------------------
fffff880`035a1718  fffff880`00e2a7cb [COLOR=Red]ataport[/COLOR]!RefPdoWithTag+0x33
----------------------------------------------------------------------------------------------------------
fffff880`035a0d38  fffff880`06d779b0Unable to load image Rt64win7.sys, Win32 error 0n2
[COLOR=Red]*** WARNING: Unable to verify timestamp for Rt64win7.sys
*** ERROR: Module load completed but symbols could not be loaded for Rt64win7.sys
 Rt64win7+0x1b9b0[/COLOR]
-----------------------------------------------------------------------------------------------------------
fffff880`06d5c000 fffff880`06dfc000   Rt64win7 T (no symbols)           
    Loaded symbol image file: Rt64win7.sys
    Image path: Rt64win7.sys
[COLOR=Red]    Image name: Rt64win7.sys
    Timestamp:        Tue Sep 27 20:20:33 2011[/COLOR] (4E81E2B9)
    CheckSum:         0009FB77
    ImageSize:        000A0000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

The first part shows the bugcheck. D1 means Driver IRQL less or not equal, so some device driver is not working properly. Probably caused by NATIO.sys means most probably some network driver is failing.

The second part, is a hint of a malware infection. Dumps dont provide it precisely, but this is a notable hint. Port errors are caused my a special type of malware called rootkit.

The third part clearly indicates that the realtek network driver is failing. So it is also to be fixed. But how?

Here comes the fourth part, says that the network driver is very old, it is of sept 2001. So it is to be updated.

What I can say now, that all the issues are just as the earlier. You now download the realtek driver from Realtek (the 5th one in the list) and install it. Also scan with Windows Defender Offline.

Will be eager to know the results.

 

[Karl Ash]

Hey again, so i ran the Windows Defender Offline like you suggested and came up with no threats or problems, i updated my driver (sorry about that i should have done that after the reinstall). I just got another BSOD. Going to attach the DMP File in case anything may have changed with the driver updates.

View attachment 253595

 

[koolkat77]

Let see if this can be solved without having to reinstall windows on your system.

Enable driver verifier as instructed here:

Use verifier for 36 hours. Then send us the BSOD reports

Driver Verifier

I'd suggest that you first backup your data and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Windows 7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

Using Driver Verifier to identify issues with Windows drivers for advanced users
Driver Verifier - BSOD related
Using Driver Verifier (Windows Drivers)

Run the torrent stuff again, and upload all the crash dumps you get with verifier enabled.