Jump to content

BSOD 0x000000D1 when using uTorrent


aserg45

Recommended Posts

Several times over the last month I have encountered a Blue Screen Of Death while using uTorrent. The stop code is 0x000000D1. I tracked down uTorrent as the source of the problem via the minidumps, and am posting the basic analysis here, taken from the Microsoft WinDbg tool. My system is Windows XP Professional SP 3, Intel Core2 Duo CPU, 4GB RAM. This problem has occurred with the current version of uTorrent, build 18488, as well as with a few previous versions.

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini032710-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*c:\pubsymbs*http://msdl.microsoft.com/download/symbols
Executable search path is: c:\windows
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp3_gdr.090804-1435
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Sat Mar 27 12:51:53.156 2010 (GMT-5)
System Uptime: 30 days 20:06:46.943
Loading Kernel Symbols
...............................................................
................................................................
................
Loading User Symbols
Loading unloaded module list
..................................................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 100000D1, {0, 2, 1, 83652a0a}

*** ERROR: Symbol file could not be found. Defaulted to export symbols for epfwtdi.sys -
Probably caused by : epfwtdi.sys ( epfwtdi+35c7 )

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

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 00000000, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: 83652a0a, address which referenced memory

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


WRITE_ADDRESS: 00000000

CURRENT_IRQL: 2

FAULTING_IP:
+35c7
83652a0a f3a5 rep movs dword ptr es:[edi],dword ptr [esi]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xD1

PROCESS_NAME: uTorrent.exe

LAST_CONTROL_TRANSFER: from 8362df59 to 83652a0a

STACK_TEXT:
WARNING: Frame IP not in any known module. Following frames may be wrong.
8bd5f4dc 8362df59 00000000 fe5cd004 007bde70 0x83652a0a
8bd5f5b8 9df5e42f 80554000 9df5f8bc 8737e3f8 0x8362df59
8bd5f5d4 9df5e4e5 f7eec0e0 8a7a40d8 00000000 tcpip!FreeIPPacket+0x191
8bd5f60c 9df5e865 89ec16f0 0037e3f8 00000000 tcpip!IPSendComplete+0x126
8bd5f630 b9d65c2c 89f7c410 870dc06c 00000000 tcpip!ARPSendComplete+0xf6
8bd5f654 8bd5f8c0 8bd5f71c 8a7d28c0 00000000 NDIS!ndisMSendCompleteX+0x8d
8bd5f92c 9deed5c7 9def7d00 f83192c8 000042b4 0x8bd5f8c0
00000000 00000000 00000000 00000000 00000000 epfwtdi+0x35c7


STACK_COMMAND: kb

FOLLOWUP_IP:
epfwtdi+35c7
9deed5c7 837d0c01 cmp dword ptr [ebp+0Ch],1

SYMBOL_STACK_INDEX: 7

SYMBOL_NAME: epfwtdi+35c7

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: epfwtdi

IMAGE_NAME: epfwtdi.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4aa9daef

FAILURE_BUCKET_ID: 0xD1_epfwtdi+35c7

BUCKET_ID: 0xD1_epfwtdi+35c7

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

Link to comment
Share on other sites

  • 2 weeks later...

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...