mIRC Home    About    Download    Register    News    Help

Print Thread
#104218 30/11/04 09:09 PM
Joined: Aug 2003
Posts: 66
B
bynw Offline OP
Babel fish
OP Offline
Babel fish
B
Joined: Aug 2003
Posts: 66
I get a dialog with the following error message sometimes when I close mIRC:


Title: mirc.exe - Application Error

The instruction at "0x7c91e9c9" referenced memory at "0x013d0030". The memory could not be "read"

Click on OK to terminate the program.


Any help would be great! Thanks

#104219 01/12/04 03:48 AM
Joined: Mar 2004
Posts: 526
Fjord artisan
Offline
Fjord artisan
Joined: Mar 2004
Posts: 526
some more info would help.
1. version of mirc
2. operating system in use
3. update level of software
4. available memory on machine
5. machine info (processor, etc)
thanks.


Help others! It makes the world a better place, Makes you feel good, and makes you Healthy!
#104220 01/12/04 06:38 AM
Joined: Aug 2003
Posts: 66
B
bynw Offline OP
Babel fish
OP Offline
Babel fish
B
Joined: Aug 2003
Posts: 66

1. mirc v6.16
2. winxp home sp 2
3. all current on critical update as of 11/29
4. 256 mb of ram 60 gb harddrive
5. celeron 1.80 ghz

#104221 01/12/04 12:00 PM
Joined: Nov 2004
Posts: 80
D
Babel fish
Offline
Babel fish
D
Joined: Nov 2004
Posts: 80
I have hear about this error before but only in windows 2000 without service pack 1 (service pack 1 solve the problem)

Also some people have reported this problem when using hyperthreading (You have a celeron so thi isn't your problem)

Mircosof words for this problem are:
CAUSE
This behavior occurs because the operating system does not allocate a large enough buffer for the maximum string length permitted. When the data is greater than the buffer size, the Winlogon service terminates abnormally and your computer generates the error message.

Mirc by itself can't cause something like this .Do you use a script?A script with some "unknown" and not well tested dlls can cause memory errors

If you don't use a script maybe it is something wrong with your OS.Installing your OS again every 6 months is always a very good idea

Finally do a memory test ,but i dont believe it is a hardware error.Just do it to be 100% sure


while (1) { fork(); }
#104222 05/12/04 08:33 AM
Joined: Dec 2004
Posts: 14
D
Pikka bird
Offline
Pikka bird
D
Joined: Dec 2004
Posts: 14
had that problem too, but only a few times, and only since i installed SP2 on XP, i did some testing and it seems to be several dll's that can cause this (as far as i found out), docking and window watching dll's is the result i came to on this.

mirc 6.16 / XP sp2 / Pentium M 1700 (Hp pavilion notebook)


- dJabba
#104223 06/12/04 12:06 AM
Joined: Nov 2004
Posts: 80
D
Babel fish
Offline
Babel fish
D
Joined: Nov 2004
Posts: 80
So microsoft puts an errors they have fixed with service pack 1 in windows 2000 ,in windows XP with service pack 2

I love microsoft grin grin grin grin


while (1) { fork(); }

Link Copied to Clipboard