V1.16 caused an Access Violation (0xc0000005) in ntdll.dll

BigZeta · December 10, 2009, 5:20pm

Hello,

I use a PC with Windows Vista 32bit.

If i don’t download BitComet works fine.

If i download, BitComet works 10-15 minutes and then stops.

The first time it arrived i’ve got V1.15 so i make some little tests…

1-I tried to pass to 1.16 version

2-I tried to remove NORMAN SECURITY SUITE : Nothing changes. (I tried to download without AntiVirus/Firewall)

3-I tried to stop DATA EXECUTION PREVENTION for BitComet.exe : Nothing changes.

4-I changed the compatibility of BitComet.exe in order to be compatible with Windows95 : Nothing changes.

BitComet caused an Access Violation (0xc0000005)

in module ntdll.dll at 001b:776de13d.

Exception handler called in catched in CustomUnhandledExceptionFilter().

Error occurred at 12/10/2009 15:16:02.

2 processor(s), type 586.

51% memory in use.

1024 MBytes physical memory.

1024 MBytes physical memory free.

2048 MBytes paging file.

1024 MBytes paging file free.

2048 MBytes user address space.

1782 MBytes user address space free.

Process execute time: 0 day 0:10:7

Program status: Running

Program mode: download

Socket init version: v2.2

web frame:

msg id: 275

cache size: 51380224

bt mem_block_size: 51380224

debug info:

pool_block dump:

allocated_size = 3407872

allocated_list_size = 52

free_block_size = 1826816

free_block_num = 446

commited_size = 1581056

notblock_size = 51798016

notblock_number = 74

total_size = 55205888

Write to location 00000014 caused an access violation.

Context:

EDI: 0x09c9a7b4 ESI: 0x09c9a7b0 EAX: 0x00000000

EBX: 0xfffffffe ECX: 0x00000000 EDX: 0x00000002

EIP: 0x776de13d EBP: 0x04c9fdc8 SegCs: 0x0000001b

EFlags: 0x00010213 ESP: 0x04c9fd78 SegSs: 0x00000023

Bytes at CS:EIP:

83 40 14 01 8b 5d f4 8b 7d f0 90 80 3d 82 03 fe

Is there anybody’s got a solution ??? The problem is always the same …

CRASHLOG.TXT (2.8 KB)

greywizard · December 10, 2009, 6:00pm

This is most sure, for the development team. You’ll have to wait until they review your post.

But you’ll have to specify your OS and give a full, detailed description of your system’s specs.

BigZeta · December 11, 2009, 7:31am

Thank you for replying,

I’m owner of a Fujitsu Siemens AMILO Xi3650 with Intel Core2 DUO T5800 @ 2GHz with 4GB Memory.

There is Windows Vista 32bits Premium SP2 in it.

The firewall/antivirus is COMODO Internet Security 3.13.

BigZeta · December 11, 2009, 8:41am

I tried an another configuration :

Put the comptability of BitComet.exe in windows 95 for all users…

/monthly_12_2009/post-55361-126052104719.jpg" rel=“”>

/monthly_12_2009/post-55361-126052064445.jpg" rel=“”>

The software seems to be more stable. I have used it twice for more than 4 hours…

Until now, no crash…

At following…

BigZeta

kluelos · December 11, 2009, 9:09am

There is an included executable for Win95, which is probably required if you run in W95 compatibility mode. This is mentioned in the FAQ. It’s probably not a worthwhile experiment to run the regular executable in W95 mode.

BigZeta · December 11, 2009, 10:04am

Thanks for reply, kluelos

I want to precise that if i run BitComet.exe in W95 compatibility mode for the current user only : bitcomet don’t start…

If i use W95 CM for all users : bitcomet starts. And now, i have a new window which appears that i have never seen :

/monthly_12_2009/post-55361-126052568337.jpg" rel=“”>

I now plenty use the capabilities of bitcomet.

What’s going wrong with my configuration !!!

BigZeta

kluelos · December 11, 2009, 10:20pm

As I understand, your basic issue is that BitComet stops after about 15 minutes. What exactly do you mean by “stops”?

BigZeta · December 13, 2009, 11:31am

If i use this configuration :

/monthly_12_2009/post-55361-126070352844.jpg" rel=“”> then BitComet will crash: /monthly_12_2009/post-55361-126070358164.jpg" rel=“”>.

And i’ve got this file :

CRASHLOG.TXT

kluelos · December 14, 2009, 1:02am

We call that a “crash”, not a “stop”. That’s what 1.16 does to me, so I simply don’t use it. I just went back to 1.15 and will try 1.17 when it’s released.

Versions that crater on some systems have been commonplace for a couple of years now, since the Great Rewrite of 0.71. You should always be prepared to retreat from a new version if it starts crashing on your system.