This happens everytime I connect to a random IRC server, with mIRC running a custom script. This only happened after I had to install the .NET framework because of VS.NET. I tried upgrading to .NET SP2 but no help.

I'm running Win XP with all the security patches. The mIRC error during crash is:
Code:
The instruction at "0x77f83aed" referenced memory at "0x00000000". The memory could not be "written".

A chunk of disassembly (break point indended):
Code:
77F83AC7  mov         al,byte ptr [edi+5]
77F83AC7  mov         al,byte ptr [edi+5]
77F83ACA  and         al,10h
77F83ACC  test        al,10h
77F83ACE  mov         byte ptr [esi+5],al
77F83AD1  je          77F83ADE
77F83AD3  movzx       eax,byte ptr [esi+4]
77F83AD7  mov         eax,dword ptr [ebx+eax*4+58h]
77F83ADB  mov         dword ptr [eax+38h],esi
77F83ADE  push        edi
77F83ADF  push        ebx
77F83AE0  call        77F82F79
77F83AE5  mov         eax,dword ptr [edi+8]
77F83AE8  mov         ecx,dword ptr [edi+0Ch]
77F83AEB  cmp         eax,ecx
  77F83AED  mov         dword ptr [ecx],eax
77F83AEF  mov         dword ptr [eax+4],ecx
77F83AF2  jne         77F83B15
77F83AF4  mov         ax,word ptr [edi]
77F83AF7  cmp         ax,80h
77F83AFB  jae         77F83B15
77F83AFD  movzx       ecx,ax
77F83B00  mov         eax,ecx
77F83B02  and         ecx,7
77F83B05  mov         dl,1
77F83B07  shr         eax,3
77F83B0A  shl         dl,cl
77F83B0C  lea         eax,[eax+ebx+158h]
77F83B13  xor         byte ptr [eax],dl
77F83B15  mov         al,byte ptr [edi+5]
77F83B18  test        al,4
77F83B1A  je          77F83B88
77F83B1C  test        al,2
77F83B1E  movzx       ecx,word ptr [edi]
77F83B21  lea         ecx,[ecx*8-10h]
77F83B28  mov         dword ptr [ebp+14h],ecx
77F83B2B  je          77F83B36

Note that this is reproducible down to the exact same memory addresses and assembly instuctions for every crash, but shouldn't be an exploit by someone as I connect to a random server and mIRC crashes within 2 minutes.

Appreciate any help, let me know any more info you need me to provide to trace this bug. Is anyone having the same problem ?