>Is there a fix for it?

Not a generic fix, for all things that cause the error, any more than there was a generic fix for GPFs.

The error is actually an operating system detected error - the memory management code in Windows determined that something attempted to access memory that either doesn't exist or it doesn't have the necessary rights to access. Any number of things can cause this generic type of error (I've found more than a few of them all by myself!) so there is no single cure for all causes.

Part of what the Win32 environment does for us is to protect the operating system and various programs from each other. When non-existant memory is referenced by a program, or it attempts to access memory belonging to another program that hasn't marked that memory as sharable, the operating system steps in to prevent the problem program from damaging other running processes. it does this in a rather unforgiving and abrupt fashion - once this type of fault is detected, the safest thing to do is to shut down the program that caused the error before it can do anything to anyone else.

Some C0000005 erros have been traced to specific problems, and workarounds have been found - the problem is, a fix for one problem is completely inapplicable to another. The best we can do is document the things that cause the errors, publish fixes and workarounds as we find them, and hope that Microsoft fixes the ones we can't fix for ourselves.

>
>>>Does anyone know anything about fatal exception error C0000005?
>>>Is there a way to look up these types of errors?
>>>
>>>thanks
>>>
>>>Jim
>>Jim,
>>
>>C0000005 is the new name for GPF. It means memory is messed up.