Jump to content

How to report about BSOD because of uTorrent?


kiav

Recommended Posts

Windows 8 Pro

1: kd> !analyze -v

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

ATTEMPTED_WRITE_TO_READONLY_MEMORY (be)

An attempt was made to write to readonly memory. The guilty driver is on the

stack trace (and is typically the current instruction pointer).

When possible, the guilty driver's name (Unicode string) is printed on

the bugcheck screen and saved in KiBugCheckDriver.

Arguments:

Arg1: 76b659a8, Virtual address for the attempted write.

Arg2: 257bb005, PTE contents.

Arg3: d3e48404, (reserved)

Arg4: 0000000a, (reserved)

Debugging Details:

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

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0xBE

PROCESS_NAME: uTorrent.exe

CURRENT_IRQL: 2

TRAP_FRAME: d3e48404 -- (.trap 0xffffffffd3e48404)

ErrCode = 00000003

eax=76b659a8 ebx=85a13560 ecx=85b1da88 edx=d3e489fc esi=00000000 edi=85dc7a10

eip=82c96014 esp=d3e48478 ebp=d3e486d8 iopl=0 nv up ei pl nz na po nc

cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202

tcpip!UdpSendMessagesOnPathCreation+0x139:

82c96014 c60000 mov byte ptr [eax],0 ds:0023:76b659a8=??

Resetting default scope

LAST_CONTROL_TRANSFER: from 81f14b60 to 81f4476c

STACK_TEXT:

d3e4833c 81f14b60 000000be 76b659a8 257bb005 nt!KeBugCheckEx

d3e48370 81e77c40 00000001 00000000 76b659a8 nt!MiRaisedIrqlFault+0x160

d3e483ec 81fbc694 00000001 76b659a8 00000000 nt!MmAccessFault+0x8f7

d3e483ec 82c96014 00000001 76b659a8 00000000 nt!KiTrap0E+0xdc

d3e486d8 82c96851 00000000 00000000 85a4f4d0 tcpip!UdpSendMessagesOnPathCreation+0x139

d3e488d4 82c96d2d 855a6d40 00000000 d3e4895c tcpip!UdpSendMessages+0x1c0

d3e488e4 81ef285b d3e489a4 6f45d57b 00000000 tcpip!UdpTlProviderSendMessagesCalloutRoutine+0x14

d3e4895c 81ef24ba 82c96d19 d3e489a4 00002400 nt!KeExpandKernelStackAndCalloutInternal+0x38b

d3e4897c 82c95d55 82c96d19 d3e489a4 00002400 nt!KeExpandKernelStackAndCalloutEx+0x1f

d3e489c0 8fa61c8c 85a4f4d0 d3e489d8 8566aee8 tcpip!UdpTlProviderSendMessages+0x55

d3e48a14 8fa61952 8566aee8 0e429794 7fff0000 afd!AfdTLFastDgramSend+0xc6

d3e48ad0 8fa50573 d3e48b90 00000000 00000000 afd!AfdFastDatagramSend+0x1fd

d3e48c40 820e77e2 8566aee8 00000001 0336bb28 afd!AfdFastIoDeviceControl+0x56e

d3e48cf0 820e75f9 8638e2c8 00000414 00000000 nt!IopXxxControlFile+0x1cd

d3e48d24 81fb933c 00000374 00000414 00000000 nt!NtDeviceIoControlFile+0x2a

d3e48d24 77136954 00000374 00000414 00000000 nt!KiFastCallEntry+0x12c

WARNING: Frame IP not in any known module. Following frames may be wrong.

0336bbf0 00000000 00000000 00000000 00000000 0x77136954

STACK_COMMAND: kb

FOLLOWUP_IP:

tcpip!UdpSendMessagesOnPathCreation+139

82c96014 c60000 mov byte ptr [eax],0

SYMBOL_STACK_INDEX: 4

SYMBOL_NAME: tcpip!UdpSendMessagesOnPathCreation+139

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: tcpip

IMAGE_NAME: tcpip.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 505aa9a9

BUCKET_ID_FUNC_OFFSET: 139

FAILURE_BUCKET_ID: 0xBE_tcpip!UdpSendMessagesOnPathCreation

BUCKET_ID: 0xBE_tcpip!UdpSendMessagesOnPathCreation

Followup: MachineOwner

---------

Link to comment
Share on other sites

Archived

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

×
×
  • Create New...