Forums Bug Reports mIRC.exe Error

Sometimes I get this error
I got mIRC 6.12, does anyone know what could be causing this problem?

MIRC caused an invalid page fault in
module MIRC.EXE at 0197:0042cbe4.
Registers:
EAX=00000000 CS=0197 EIP=0042cbe4 EFLGS=00010246
EBX=00000000 SS=019f ESP=0081eeec EBP=00000004
ECX=00f70dec DS=019f ESI=00f70dec FS=3ad7
EDX=00000000 ES=019f EDI=00000005 GS=0000
Bytes at CS:EIP:
8b 8e 80 08 00 00 41 8b c1 83 f8 14 89 8e 80 08
Stack dump:
0081fb80 0081fb78 0000801d 0081fbcc 74697865 3564000a 6957215d 40544e6e 6c6f6f70 2d38362d 2d313631 312d3039 6e2e3331 35323379 7361652e 65762e74

DbzDP, do you by chance run the SysReset script? I, too, get a crash very similar to yours, and never had a problem with mIRC until I started using SysReset v2.53, which automatically installs mIRC 6.12. I can't tell which one brought the problem.

I use Windows 98SE with 1GB DDRAM and here is the crash output:

MIRC caused an invalid page fault in
module MIRC.EXE at 0167:0042b567.
Registers:
EAX=00000000 CS=0167 EIP=0042b567 EFLGS=00010246
EBX=00000000 SS=016f ESP=0081eaf0 EBP=00f61bcc
ECX=f2d09ca0 DS=016f ESI=00000003 FS=3247
EDX=0001d604 ES=016f EDI=00000000 GS=0000
Bytes at CS:EIP:
39 9d 28 05 00 00 0f 85 be 00 00 00 8b 15 94 40
Stack dump:
00f61bcc 0081fb78 bff55591 7325206f 6d697420 6f206465 00007475 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000

I too have sysreset 2.53 and never had that problem but I installed sysreset into my own folder and then placed a clean copy of mirc 6.12 into it. No problems no crashing. If there was a version of mirc with the script (zip file?), there shouldn't be and I would delete that portion of the script and re-install and do what I did. Good luck

I too have been having frequent crashes in Mirc.exe. I do not seem to be running the script you've spoken of.
Has anyone found a reason/cure for this problem. It crashes 7 or 8 times a day on me...

As I mentioned install sysreset (excluding mirc.exe) - into it's own folder and then place a clean copy of mirc 6.12 into it... if it still crashes then it's a problem with capability with sysreset. I use mirc 6.12 on it's own with my own custom scripts and never had a crash. I also use sysreset (in it's own folder different than my basic mirc) and also never had a crash.

Try that... good luck

Someone said to me, connect to the server and don't join any channels see how long it goes without a crash, after 4-5 hours no crash at all. Normally it would crash at abotu 1-3hours. So then I knew someone was using the mIRC 6.12 bug on me, which can crash peoples mIRC. It is like the mIRC 6.03 - 6.11 bug.

try running your normal day with a clean install...

if that goes okay it;s a problem in your scripts and not in mIRC

Thanks for the advice. I did... and it didn't work any better.

Whatever this same script did work very well with 6.03 and doesn't work any longer. Seems to be definitely mIRC 6.12. Even if this is a fuzzy bug with random occurences (and apparently triggered externally when a chat window is closed in our case).

Also there are other threads here about various problems around the /close -c $nick command. And even without the use of a script (of course, fserve scripts do a lot of these close chats by themselves... making the bug to appear).

I don't think that denying the problems that other people have is a good policy. And I don't think that Khaled needs any "defender". Neither do Rz_Ten1.

As a programmer, I know that fixing such a bug is very difficult when it can't be reproduced at will. And we all hope that a solution will be found soon. But we have to characterize the problem, not to deny it.

"Whatever this same script did work very well with 6.03 and doesn't work any longer"

In a general manner, Mirc can hardly be held accountable if a script written for another version no longer works as it did due to changes within a new version. It isnt a matter of anyone denying a problem exists. Obviously there are two different issues to be considered:
-if a scripted command doesnt work as its supposed to
-or is the script not compatible with changes in a new version

When someone reports a bug that could be script related, the obvious place to start is with a clean copy of mIRC to see if the problem exists without scripts. Thats logic, not a case of defending anyone or denying something exists. The more information ppl have, the better able they are to track down a problem in any situation.

Agreed. And I didn't mean to say anything else. But the fact it did work is at least a positive hint .


I (we) did and, of course, reinstalled the script just after. Same crashes.
But you should agree also that a script can do legitimate actions or sequences of actions which are not being done in interactive standard use... Especially when using the remote event control... obviously made for this kind of use.
Either this is just a 'closed' software and yes, obviously, a mere 'blank' test is sufficient, or this includes scripting capabilities and thus we can also test scripts with it. Just common sense.


100% agreed... and it is almost the conclusion of my previous post

mIRC is a great product becoming more and more complex and I know this kind of bug can't be avoided. And scripting just makes it worse. Because any undocumented or non-standard command use can work in one version and become impossible in the next one. No doubt about this, I have many examples in other languages/kits. That's the reason why the "incompatible change" chapter is soooo important in every sdkit.

But, once again, there are other threads here focusing on some close -c $nick inconsistencies. And this seems to be related also to this random crash since the logs I get always point to a chat close as the bug trigger. I'm really trying to trace the problem and if I manage to have more details I will give them to whoever can use them...

I've tried installing sysreset - only to experience the same nagging crash. Do I have to search my system and remove all Mirc... before installing?