"ah yes 0x0042cbe4. it's a bug in mirc actually. mirc doesn't check the requested memory so if your paging file has errors things could go wrong."
As a programmer who
thought to know how memory paging worked, I would be pleased if somebody can explain what are these so-called errors in paging file
. Never heard of that. Whatever I doubt that any operating system would be stable for a long time with a damaged paging process... (I'm also experiencing the crash but my uptime is usually 3 or 4 weeks, rebooting only for the monthly Windoze updates).
Seems rather that some pointer is not correctly initialized and that the application would work 'hopefully' if the memory at this adress is (or not) zero. And this would very well explain why it crashes
randomly. By experience, with this kind of bug, it depends of the machine (in particular the amount of RAM), on how many other applications are running at the same time, etc.
Whatever, this bug is really annoying and I also vote for a rapid fix. Please.
