Program Error

[grantb]

I keep getting the following error:

EXCEL.exe has generated errors and will be closed by Windows. You will need to restart the program.

An error log is being created.

What does this message mean? In the past I was getting a message similar to this, but said it was an application error and had to do with the memory. The computer department at my company has completely redone my computer and it still seems to be happening.

Also, where do you view the error log?

 

[santeria]

It's usually a memory address-ing error.
The log will often go to Dr Watson, but the more recent systems will log it to the event log in the system... depends on what system you have too, and how IT has set it up, cos some IT depts will disable the Event Viewer capacity.

 

[grantb]

Is there anyway this can be fixed?

Thanks.

 

[santeria]

Depends on what your system is, how it is set up on a network, and wether the Error or event Log is available to you.

I have an opinion as to what has happened, and what needs to be done, but check and see if the log or event file is accessable to you.

 

[grantb]

Yes, the Event Viewer is accessible to me. What is your thought on this?

 

[santeria]

Does it record the event error that shut down the Program?
What does it say?
How many errors occur at the time of the shutdown?

 

[grantb]

At the time of shutdown only one error occurs. I had one earlier this morning, and the following message was in my Event Viewer, under the Application log.

The application, , generated an application error The error occurred on 12/23/2003 @ 07:45:08.091 The exception generated was c0000005 at address 3006FE66 (<nosymbols>)

This is the message in Event Viewer from yesterday's program error:

The application, , generated an application error The error occurred on 12/22/2003 @ 08:54:34.981 The exception generated was c0000005 at address 301B5BFF (<nosymbols>)

Will this information help you?

 

[santeria]

Looks like a Sector error on the Hard drive.
If the temp file brought down is written to corrupted disc space, then that would explain it;
But it could also be a corrupt file written to good disc space.

I'd still do the disc defrag, then optimise as well... usually at the same function, unless the defrag errors and wants a low level scan done.
I'd try the defrag first on the local disc, then if that fails, I'd approach the network guys about a file recovery.