Windows 7: BSOD using uTorrent/Vuze

Stevieb2685 · 20 Jul 2013

I received a BSOD Error using uTorrent. It happened ever since I downloaded uTorrent. It also happened when I downloaded Vuze (another Torrent client). Why does this happen?

Steve

centaur78 · 20 Jul 2013

Please use this tool to update your profile specs

And then use this tool to post all the files here not just the dumps

koolkat77 · 20 Jul 2013

McAfee is a frequent cause of BSOD's. Especially during torrent downloads, Replace with Microsoft Security Essentials & the Free version of Malwarebytes, update and make full scans separately:

Uninstallers (removal tools) for common antivirus software - ESET Knowledgebase

Microsoft Security Essentials - Microsoft Windows

Malwarebytes Free

Do not start the trial version of MalwareBytes

You may also take a look at:

Good & Free System Security Combination

Use the System File Checker tool and Run Disk Check:

Repair Windows 7 System Files with System File Checker

Run Disk Check in Windows 7 for Bad Sectors & Errors

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck E1, {fffff800043c4d50, 2, fffffa800e0f6ca0, fffffa800e0f6ca0}

Probably caused by : ntkrnlmp.exe ( nt!IopProcessWorkItem+0 )

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

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

WORKER_THREAD_RETURNED_AT_BAD_IRQL (e1)
Arguments:
Arg1: fffff800043c4d50, address of worker routine (do ln on this to find guilty driver)
Arg2: 0000000000000002, IRQL returned at (should have been 0, but isn't).
Arg3: fffffa800e0f6ca0, workitem parameter
Arg4: fffffa800e0f6ca0, workitem address

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


FAULTING_IP: 
nt!IopProcessWorkItem+0
fffff800`043c4d50 fff3            push    rbx

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0xE1

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80004154ef8 to fffff800040ccc00

STACK_TEXT:  
fffff880`033cbb68 fffff800`04154ef8 : 00000000`000000e1 fffff800`043c4d50 00000000`00000002 fffffa80`0e0f6ca0 : nt!KeBugCheckEx
fffff880`033cbb70 fffff800`0436aede : 00000000`00000000 fffffa80`06cf5040 00000000`00000080 fffffa80`06c619e0 : nt! ?? ::FNODOBFM::`string'+0x58286
fffff880`033cbc00 fffff800`040bd906 : fffff880`031d7180 fffffa80`06cf5040 fffff880`031e1fc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`033cbc40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nt!IopProcessWorkItem+0
fffff800`043c4d50 fff3            push    rbx

SYMBOL_NAME:  nt!IopProcessWorkItem+0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  5147d9c6

FAILURE_BUCKET_ID:  X64_0xE1_nt!IopProcessWorkItem+0

BUCKET_ID:  X64_0xE1_nt!IopProcessWorkItem+0

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

Code:

Unloaded modules:
fffff880`0b0a8000 fffff880`0b0f2000   mfeavfk01.sy
fffff880`099d4000 fffff880`099de000   vwifimp.sys
fffff880`08f4d000 fffff880`08f57000   vwifimp.sys
fffff880`04448000 fffff880`0447e000   WUDFRd.sys
fffff880`01693000 fffff880`016a1000   crashdmp.sys
fffff880`0402e000 fffff880`04182000   dump_iaStor.
fffff880`04182000 fffff880`04195000   dump_dumpfve

Stevieb2685 · 20 Jul 2013

SF Diagnostic tool, when I click Grab All, is telling me that access to C:\Windows\Minidump is denied. What do I do if that happens?

centaur78 · 21 Jul 2013

right click on Sfdiag and click on "Run as Administrator"

Stevieb2685 · 21 Jul 2013

I think I may have resolved the problem. I had McAfee SecurityCenter installed and it my subscription ran out. I removed it and so far *knock wood*, I haven't gotten BSOD. Let's hope that was the problem.

Steve

Stevieb2685 · 21 Jul 2013

Reuploading the zip file again.

centaur78 · 21 Jul 2013

Steve

Holy crap !! You seriously are being paranoid....

Looking at what you installed on your system ... you had

Mcafee - Antivirus ... ( which is removed .... but had some orphan files remaining)

Emisoft Anti- Malware - ( which was one causes for the BSOD along with Mcafee)
Spybot Search & Destroy
Superantispyware
WinPatrol
MalwareByte's AntiMalware

that's 5 software doing the same work !!!!!! You are just calling in more trouble ....
I would suggest you keep MalwareByte's and remove the rest asap