Author Topic: FATAL ERROR: Unhandled c0000409h Exception at 574affebh  (Read 4928 times)

0 Members and 1 Guest are viewing this topic.

Luke

  • Guest
FATAL ERROR: Unhandled c0000409h Exception at 574affebh
« on: August 23, 2007, 04:23:00 PM »
FATAL ERROR: Unhandled c0000409h Exception at 574affebh
I seem to randomly get the FATAL ERROR. I am not positive it is being caused by my custom menu but that is the only thing I notice I'm doing (loading it) when it crashes. I have 3 other custom menus that seem to be no problem at all. This 1 menu worked on 2005, 2006, 2007 and even 2008. But every now and again when I load the menu or CUI it will blow up and give me the error. So far the only fix seems to be uninstalling and reinstalling 2008.

However, it only seems to be a problem on my machine. 4 other users are using the same menu on their machine and no problems at all.

If it makes any difference they are all running Windows XP but I'm running Window XP 64 bit however 64 bit was giving us problems so my system was setup as 32 bit.

I bet I used it for 3-4 months on 2008 before it ever gave me any problems.

Please help. I'm spending as much time uninstalling and re-installing acad as I actually am drawing.

deegeecees

  • Guest
Re: FATAL ERROR: Unhandled c0000409h Exception at 574affebh
« Reply #1 on: August 23, 2007, 06:13:28 PM »
Quote
I'm running Window XP 64 bit however 64 bit was giving us problems so my system was setup as 32 bit

Shot in the dark: This may be the culprit.

uncoolperson

  • Guest
Re: FATAL ERROR: Unhandled c0000409h Exception at 574affebh
« Reply #2 on: August 23, 2007, 07:06:48 PM »
But every now and again when I load the menu or CUI it will blow up and give me the error.


have you tried remaking the menu (thinking from back in the mns days...haven't had the fun of playing with cui yet), do the cui's have a compiled menu file (if so try tossing it)

Arizona

  • Guest
Re: FATAL ERROR: Unhandled c0000409h Exception at 574affebh
« Reply #3 on: August 24, 2007, 07:13:33 AM »
Quote
I'm running Window XP 64 bit however 64 bit was giving us problems so my system was setup as 32 bit

Shot in the dark: This may be the culprit.
I was thinking the same thing :-)