BSOD when running uTorrent, error code d1

[Tolg]

Hello,

I've been getting a series of BSODs on my laptop recently. It appears they only occur while uTorrent is running - which is rather puzzling seeing how I've used it for months without issues and I have made no changes to it recently (it also takes some time after the start of the program for Windows to crash, so I'm not entirely sure uTorrent is really the culprit.)

Incidentally I am running Windows 7 Home Premium 64-bit on my 1.5 years old laptop. Windows came preinstalled and has been reinstalled by the Sony support less than 5 months ago (together with a new HD and motherboard).

Thanks in advance,

Torugu


------------------------------------------------------


Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 2057

Additional information about the problem:
BCCode: d1
BCP1: 0000000000000028
BCP2: 0000000000000002
BCP3: 0000000000000000
BCP4: FFFFF88001811B2D
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\122711-26223-01.dmp
C:\Users\Torugu\AppData\Local\Temp\WER-187201-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

 

[Tolg]

I don't want to appear impatient or ungrateful, but it's been a day since I first posted and my thread has since slipped all the way down to page 5, so I was wondering if you had any advice that you could give me.

Also I discovered an "error" entry in the event viewer that seems to coincide with the BSODs:


Event ID: 16398

A new BITS job could not be created. The current job count for the user Kudryavka\Torugu (60) is equal to or greater than the job limit (60) specified through group policy. To correct the problem, complete or cancel the BITS jobs that haven't made progress by looking at the error, and restart the BITS service. If this error recurs, contact your system administrator and increate the per-user and per-computer Group Policy job limits.

 

[writhziden]

For your event error, see Event ID 16398

 

[writhziden]

You need to update sfep.sys for your laptop. To do so:
1. http://www.sevenforums.com/tutorials/697-system-restore-point-create.html
2. Download and install Sony eSupport - VPCEG290X - Software & Drivers
3. If the driver causes stability issues, http://www.sevenforums.com/tutorials/700-system-restore.html

 

[Tolg]

I'm sorry, but I'm afraid that doesn't help me all that much. I'm not running Windows Server 2008 and none of the solutions apply to my system. (I can't even get past the first step because my system doesn't seem to have the system tools necessary.)

Edit: Sorry, I posted before your second reply. I'll try that now.

 

[writhziden]

I'm sorry, but I'm afraid that doesn't help me all that much. I'm not running Windows Server 2008 and none of the solutions apply to my system. (I can't even get past the first step because my system doesn't seem to have the system tools necessary.)

Edit: Sorry, I posted before your second reply. I'll try that now.

Yeah, I realized you probably couldn't fix it. I'm not sure what is causing that error; it is very strange. It may be due to your antivirus software...

 

[boohbah]

as a test you could try installing bittorrent, it is practically the same ,and maybe uninstall utorrent

if you still have problems that would rule out utorrent.

 

[Tolg]

So, I have done a few experiments:

First of all I have uninstalled my virus software (avira antivirus) to prevent any issues that may cause. Then I uninstalled uTorrent 3.0.0 and tried uTorrent 2.2.1 and BitTorrent (separately). Both caused BSODs shortly after they started downloading.

From my amateur point of view it looks like it's not the software that's causing the BSOD but rather the act of downloading (using a torrent protocol).

I have attached the report from the most recent BSOD (the BitTorrent install) in the hope that that may shed some light on the issue.

 

[writhziden]

So, I have done a few experiments:

First of all I have uninstalled my virus software (avira antivirus) to prevent any issues that may cause. Then I uninstalled uTorrent 3.0.0 and tried uTorrent 2.2.1 and BitTorrent (separately). Both caused BSODs shortly after they started downloading.

From my amateur point of view it looks like it's not the software that's causing the BSOD but rather the act of downloading (using a torrent protocol).

I have attached the report from the most recent BSOD (the BitTorrent install) in the hope that that may shed some light on the issue.

Does the BITS service error time correspond with the blue screen errors? Your errors are all due to NETIO.SYS for the most recent blue screens.

I think they may be related. I am trying to look into the BITS error for you.

 

[writhziden]

Nevermind. The BITS seems to be unrelated. It appears to occur on login after rather than during a blue screen error. I will still try to resolve the error for you, but we should try to track down the cause of your blue screen issues.

Typically, NETIO.SYS means that you probably have a problem with the driver for your internet connection. If you are connected via wireless, update your Atheros driver. If you are connected via ethernet, update your ethernet connector driver.

 

[Tolg]

Edit: Never mind. I'll do that.

 

[Tolg]

Ok, I updated my Atheros driver to 9.2.0.105 - the newest version I could find - and I was about to say that it did the job, but I'm afraid I was wrong.

This time around there was a much longer gap between the launch of my torrent program and the BSOD (slightly less than an hour rather than a few minutes), but ultimately it ended up crashing anyway...

 

[writhziden]

Ok, I updated my Atheros driver to 9.2.0.105 - the newest version I could find - and I was about to say that it did the job, but I'm afraid I was wrong.

This time around there was a much longer gap between the launch of my torrent program and the BSOD (slightly less than an hour rather than a few minutes), but ultimately it ended up crashing anyway...

It is still the same as before. I am afraid I cannot find the issue. You may consider running Driver verifier with the following steps:
1. Backup your system and user files
2. Create a system restore point
3. If you do not have a Windows 7 DVD, Create a system repair disc
4. Run Driver Verifier
If Windows cannot start in normal mode with driver verifier running, start in safe mode. If it cannot start in safe mode or normal mode, restore the system restore point using http://www.sevenforums.com/tutorials/700-system-restore.html OPTION TWO.
Thanks to zigzag3143 for contributing to the above steps.

This will allow bad drivers to be singled out if you post the blue screen dmp files after any blue screens occur while Verifier is running.

 

[writhziden]

So, I have done a few experiments:

First of all I have uninstalled my virus software (avira antivirus) to prevent any issues that may cause. Then I uninstalled uTorrent 3.0.0 and tried uTorrent 2.2.1 and BitTorrent (separately). Both caused BSODs shortly after they started downloading.

From my amateur point of view it looks like it's not the software that's causing the BSOD but rather the act of downloading (using a torrent protocol).

I have attached the report from the most recent BSOD (the BitTorrent install) in the hope that that may shed some light on the issue.

How did you uninstall Avira? Did you use Avira RegistryCleaner - Download to clean up any remnants? It's possible Avira is still causing blue screen with utorrent if you did not clean up the Avira registry entries using the linked tool.

 

[Tolg]

So I have run the registry cleaner, it removed 3 files but did nothing to solve the problem.

I have also tried using the verifier but that results in a BSOD during the boot process (I assume running verifier in safe mode is meaningless since safe mode doesn't load non-essential drivers?).

I have attached the current crash dump, but I'm not even sure if it was generated successfully - the BSOD stops after the second step ("Initialising crash dump to hard drive" or something like that. I can write down the exact wording if you're not sure what I mean.) and does not restart automatically.

 

[writhziden]

You may need to run Verifier one non-Microsoft driver at a time to determine which causes the blue screen when Windows starts.

And you were right, there were no Verifier related blue screens included in your dmp files. Only NETIO.SYS again.

 

[Tolg]

I haven't been able to pinpoint the driver yet, but I was just running verifier on roughly a third of my drivers and this time around it seems to have created a crash dump and so I thought I'd just post it her. I'll be trying to narrow it down further.

Also I want to say thank you very much for everything you have done so far.

Edit: And this time with attachment.

 

[writhziden]

Glad I could help.

Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\Torugu\Windows_NT6_BSOD_jcgriff2\122911-18220-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02e5a000 PsLoadedModuleList = 0xfffff800`0309f670
Debug session time: Thu Dec 29 13:15:13.415 2011 (GMT-7)
System Uptime: 0 days 0:00:15.038
Loading Kernel Symbols
...............................................................
.....................................................
Loading User Symbols
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C9, {23e, fffff8800450a308, fffff980053aaea0, 0}

Unable to load image \SystemRoot\System32\Drivers\PxHlpa64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for PxHlpa64.sys
*** ERROR: Module load completed but symbols could not be loaded for PxHlpa64.sys
Unable to load image \SystemRoot\system32\DRIVERS\dtsoftbus01.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for dtsoftbus01.sys
*** ERROR: Module load completed but symbols could not be loaded for dtsoftbus01.sys
Probably caused by : dtsoftbus01.sys ( dtsoftbus01+1308 )

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

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
The IO manager has caught a misbehaving driver.
Arguments:
Arg1: 000000000000023e, A driver has marked an IRP pending but didn't return STATUS_PENDING.
Arg2: fffff8800450a308, The address in the driver's code where the error was detected.
Arg3: fffff980053aaea0, IRP address.
Arg4: 0000000000000000, Status code.

Debugging Details:
------------------


BUGCHECK_STR:  0xc9_23e

DRIVER_VERIFIER_IO_VIOLATION_TYPE:  23e

FAULTING_IP: 
dtsoftbus01+1308
fffff880`0450a308 4053            push    rbx

FOLLOWUP_IP: 
dtsoftbus01+1308
fffff880`0450a308 4053            push    rbx

IRP_ADDRESS:  fffff980053aaea0

DEVICE_OBJECT: fffffa80064fda30

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff800033603dc to fffff80002ed6c40

STACK_TEXT:  
fffff880`033718c8 fffff800`033603dc : 00000000`000000c9 00000000`0000023e fffff880`0450a308 fffff980`053aaea0 : nt!KeBugCheckEx
fffff880`033718d0 fffff800`0336a47a : fffff800`0335e9f0 fffff880`0450a308 fffff980`053aaea0 00000000`00000000 : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`03371910 fffff800`0336b34e : 00000000`0000023e 00000000`00000000 fffff980`053aaea0 00000000`ffffffff : nt!ViErrorFinishReport+0xda
fffff880`03371960 fffff800`0337671f : fffffa80`06c6f6c0 fffffa80`03ff8f40 fffffa80`03ff8ff8 fffff880`0450e080 : nt!VfErrorReport6+0x6e
fffff880`03371a30 fffff800`03376b63 : fffffa80`03ff8f40 00000000`00000002 fffffa80`064fda30 fffff880`0450a3d8 : nt!IovpCallDriver2+0x13f
fffff880`03371a90 fffff800`0337cc2e : fffff980`053aaea0 fffff980`053aaea0 00000000`00000002 fffffa80`064fda30 : nt!VfAfterCallDriver+0x353
fffff880`03371ae0 fffff880`0135e4d5 : fffff980`053aaf70 fffffa80`069e8180 fffff980`053aaea0 fffffa80`03ff8f40 : nt!IovCallDriver+0x57e
fffff880`03371b40 fffff980`053aaf70 : fffffa80`069e8180 fffff980`053aaea0 fffffa80`03ff8f40 fffff980`00000020 : PxHlpa64+0x34d5
fffff880`03371b48 fffffa80`069e8180 : fffff980`053aaea0 fffffa80`03ff8f40 fffff980`00000020 fffffa80`00000001 : 0xfffff980`053aaf70
fffff880`03371b50 fffff980`053aaea0 : fffffa80`03ff8f40 fffff980`00000020 fffffa80`00000001 fffffa80`00000001 : 0xfffffa80`069e8180
fffff880`03371b58 fffffa80`03ff8f40 : fffff980`00000020 fffffa80`00000001 fffffa80`00000001 00000000`00000000 : 0xfffff980`053aaea0
fffff880`03371b60 fffff980`00000020 : fffffa80`00000001 fffffa80`00000001 00000000`00000000 00000000`00000000 : 0xfffffa80`03ff8f40
fffff880`03371b68 fffffa80`00000001 : fffffa80`00000001 00000000`00000000 00000000`00000000 fffff880`03371d20 : 0xfffff980`00000020
fffff880`03371b70 fffffa80`00000001 : 00000000`00000000 00000000`00000000 fffff880`03371d20 00000000`00000000 : 0xfffffa80`00000001
fffff880`03371b78 00000000`00000000 : 00000000`00000000 fffff880`03371d20 00000000`00000000 fffffa80`06533c00 : 0xfffffa80`00000001


STACK_COMMAND:  .bugcheck ; kb

SYMBOL_NAME:  dtsoftbus01+1308

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dtsoftbus01

IMAGE_NAME:  dtsoftbus01.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4dfb047d

FAILURE_BUCKET_ID:  X64_0xc9_23e_VRF_dtsoftbus01+1308

BUCKET_ID:  X64_0xc9_23e_VRF_dtsoftbus01+1308

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

Please remove Daemon Tools, as it uses a driver called dtsoftbus01.sys that is known to cause BSODs.

I prefer TotalMounter as my CD/DVD virtualization software as it allows me to burn images to a virtual CD/DVD if I just want an ISO file instead of a disc, and it is free.

Many use MagicISO - Convert BIN to ISO, Create, Edit, Burn, Extract ISO file, ISO/BIN converter/extractor/editor as well, which is also free.

 

[Tolg]

Okay, I'll do that and check if it solves the issue. Meanwhile perhaps you could have a look at this third batch of drivers (the final one) which likewise causes a BSOD at start-up. This time my VPN client is among them - and that certainly sounds like a likely suspect for an Internet connection related blue screen.

 

[writhziden]

Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\Torugu\Windows_NT6_BSOD_jcgriff2\122911-16879-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02e06000 PsLoadedModuleList = 0xfffff800`0304b670
Debug session time: Thu Dec 29 13:39:52.697 2011 (GMT-7)
System Uptime: 0 days 0:00:14.320
Loading Kernel Symbols
...............................................................
.....................................................
Loading User Symbols
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C9, {23e, fffff880042e9308, fffff9800460ce10, 0}

Unable to load image \SystemRoot\System32\Drivers\PxHlpa64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for PxHlpa64.sys
*** ERROR: Module load completed but symbols could not be loaded for PxHlpa64.sys
Unable to load image \SystemRoot\system32\DRIVERS\dtsoftbus01.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for dtsoftbus01.sys
*** ERROR: Module load completed but symbols could not be loaded for dtsoftbus01.sys
Probably caused by : dtsoftbus01.sys ( dtsoftbus01+1308 )

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

3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
The IO manager has caught a misbehaving driver.
Arguments:
Arg1: 000000000000023e, A driver has marked an IRP pending but didn't return STATUS_PENDING.
Arg2: fffff880042e9308, The address in the driver's code where the error was detected.
Arg3: fffff9800460ce10, IRP address.
Arg4: 0000000000000000, Status code.

Debugging Details:
------------------


BUGCHECK_STR:  0xc9_23e

DRIVER_VERIFIER_IO_VIOLATION_TYPE:  23e

FAULTING_IP: 
dtsoftbus01+1308
fffff880`042e9308 4053            push    rbx

FOLLOWUP_IP: 
dtsoftbus01+1308
fffff880`042e9308 4053            push    rbx

IRP_ADDRESS:  fffff9800460ce10

DEVICE_OBJECT: fffffa80064dc4a0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff8000330c3dc to fffff80002e82c40

STACK_TEXT:  
fffff880`03386828 fffff800`0330c3dc : 00000000`000000c9 00000000`0000023e fffff880`042e9308 fffff980`0460ce10 : nt!KeBugCheckEx
fffff880`03386830 fffff800`0331647a : fffff800`0330a9f0 fffff880`042e9308 fffff980`0460ce10 00000000`00000000 : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`03386870 fffff800`0331734e : 00000000`0000023e 00000000`00000000 fffff980`0460ce10 00000000`ffffffff : nt!ViErrorFinishReport+0xda
fffff880`033868c0 fffff800`0332271f : fffffa80`06afef60 fffffa80`03fa4a90 fffffa80`03fa4b48 fffff880`042ed080 : nt!VfErrorReport6+0x6e
fffff880`03386990 fffff800`03322b63 : fffffa80`03fa4a90 00000000`00000002 fffffa80`064dc4a0 fffff880`042e93d8 : nt!IovpCallDriver2+0x13f
fffff880`033869f0 fffff800`03328c2e : fffff980`0460ce10 fffff980`0460ce10 00000000`00000002 fffffa80`064dc4a0 : nt!VfAfterCallDriver+0x353
fffff880`03386a40 fffff800`03327c42 : fffff980`0460cee0 00000000`00000002 fffffa80`06abe680 fffffa80`03fa4a90 : nt!IovCallDriver+0x57e
fffff880`03386aa0 fffff800`03328c16 : fffff980`0460ce10 00000000`00000002 fffffa80`06abe530 fffff800`033243f5 : nt!ViFilterDispatchGeneric+0x62
fffff880`03386ad0 fffff880`0138b4d5 : fffff980`0460cf28 fffffa80`06a9c180 fffff980`0460ce10 fffffa80`03ff3cd0 : nt!IovCallDriver+0x566
fffff880`03386b30 fffff980`0460cf28 : fffffa80`06a9c180 fffff980`0460ce10 fffffa80`03ff3cd0 fffffa80`00000020 : PxHlpa64+0x34d5
fffff880`03386b38 fffffa80`06a9c180 : fffff980`0460ce10 fffffa80`03ff3cd0 fffffa80`00000020 fffffa80`00000001 : 0xfffff980`0460cf28
fffff880`03386b40 fffff980`0460ce10 : fffffa80`03ff3cd0 fffffa80`00000020 fffffa80`00000001 fffffa80`00000000 : 0xfffffa80`06a9c180
fffff880`03386b48 fffffa80`03ff3cd0 : fffffa80`00000020 fffffa80`00000001 fffffa80`00000000 00000000`00000000 : 0xfffff980`0460ce10
fffff880`03386b50 fffffa80`00000020 : fffffa80`00000001 fffffa80`00000000 00000000`00000000 00000000`00000000 : 0xfffffa80`03ff3cd0
fffff880`03386b58 fffffa80`00000001 : fffffa80`00000000 00000000`00000000 00000000`00000000 fffff880`03386da0 : 0xfffffa80`00000020
fffff880`03386b60 fffffa80`00000000 : 00000000`00000000 00000000`00000000 fffff880`03386da0 00000000`00000000 : 0xfffffa80`00000001
fffff880`03386b68 00000000`00000000 : 00000000`00000000 fffff880`03386da0 00000000`00000000 fffffa80`068d9b90 : 0xfffffa80`00000000


STACK_COMMAND:  .bugcheck ; kb

SYMBOL_NAME:  dtsoftbus01+1308

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dtsoftbus01

IMAGE_NAME:  dtsoftbus01.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4dfb047d

FAILURE_BUCKET_ID:  X64_0xc9_23e_VRF_dtsoftbus01+1308

BUCKET_ID:  X64_0xc9_23e_VRF_dtsoftbus01+1308

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

Still caused by Daemon Tools's dtsoftbus01.sys

You'll have to uninstall that before you can see if there are others.