Jump to content

Crach Report for utorrent 1.7.7 build 8179


djblade

Recommended Posts

Not sure what happened here but here's the report.

Loading Dump File [C:\Program Files (x86)\uTorrent\8179-utorrent.18e1.dmp]

User Mini Dump File: Only registers, stack and portions of memory are available

Symbol search path is: *** Invalid ***

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

* Symbol loading may be unreliable without a symbol search path. *

* Use .symfix to have the debugger choose a symbol path. *

* After setting your symbol path, use .reload to refresh symbol locations. *

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

Executable search path is:

Windows Server 2003 Version 3790 (Service Pack 2) MP (2 procs) Free x86 compatible

Product: WinNt, suite: SingleUserTS

Debug session time: Fri Mar 14 04:37:48.000 2008 (GMT+0)

System Uptime: not available

Process Uptime: 0 days 0:40:48.000

................

This dump file has an exception of interest stored in it.

The stored exception information can be accessed via .ecxr.

(2c0.840): Access violation - code c0000005 (first/second chance not available)

eax=00000000 ebx=002bc8a0 ecx=03c32818 edx=00002000 esi=002bc878 edi=002bc8d0

eip=7d61d6c6 esp=0259ef80 ebp=0259ef8c iopl=0 nv up ei pl nz na po nc

cs=0023 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00010202

*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntdll.dll -

ntdll!ZwGetContextThread+0x12:

7d61d6c6 c20800 ret 8

dump file for download

http://www.mediafire.com/?yu3ymmufgyy

Link to comment
Share on other sites

Hmmmm. K, it sounds like that crash is fixed in 1.8. Is that the first time it crashed for you? If it's a regular occurance you should try running 1.8 to verify it doesn't happen. If not, you can run 1.7 as you wish OR test the new 1.8 beta found in the Announcement forum. To save configuration mixups you can easily download the EXE and run it self-contained :)

Link to comment
Share on other sites

Well if it only happened once then it sounds like you're OK. If however it starts happening regularly --even if you are dedicated to staying on 1.7 -- you should at least try 1.8 once for long enough to rule out it HASN'T been fixed... you've got no idea how much tighter 1.8 is resource-wise... or maybe you do ;)

Link to comment
Share on other sites

Archived

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

×
×
  • Create New...