SeeDk
asked on
Windows 7: Excel 2010 randomly crashes, no error messages, files go missing
The PC is running Windows 7 64bit and Office 2010 32bit.
One user has been experiencing this strange issue for a few months.
Office 2010 is installed.
Occasionally, Excel will randomly shut down with no prompt or warning. When it is opened again, a file being worked on will be missing.
The files the users works on are on a network share.
In today's case, the file was still listed under the AutoRecovery menu along with the file path but the file was not actually located at the file path (or anywhere else).
It is not at the AutoSave file location either, though other files are.
It is also not located in c:\users\username\appdata\ local\temp .
It is not on the network share.
The Event Viewer has no error about this at all (or at least I don't see it.)
Due to this issue, I recently replaced the PC with one created from a clean image with 16GB RAM.
The issue still occurs today.
It appears to be a bug in Excel but the issue is difficult to reproduce and is costing the user hours of work each time it occurs.
Has anyone seen anything like this before?
Is there any sort of logging tool I could run which is better than Event Viewer which would could offer more insight into the cause of this?
One user has been experiencing this strange issue for a few months.
Office 2010 is installed.
Occasionally, Excel will randomly shut down with no prompt or warning. When it is opened again, a file being worked on will be missing.
The files the users works on are on a network share.
In today's case, the file was still listed under the AutoRecovery menu along with the file path but the file was not actually located at the file path (or anywhere else).
It is not at the AutoSave file location either, though other files are.
It is also not located in c:\users\username\appdata\
It is not on the network share.
The Event Viewer has no error about this at all (or at least I don't see it.)
Due to this issue, I recently replaced the PC with one created from a clean image with 16GB RAM.
The issue still occurs today.
It appears to be a bug in Excel but the issue is difficult to reproduce and is costing the user hours of work each time it occurs.
Has anyone seen anything like this before?
Is there any sort of logging tool I could run which is better than Event Viewer which would could offer more insight into the cause of this?
ASKER
1. Yes, there is nothing logged. These crashed are never logged in Event Viewer. I don't know why.
2. This is a brand new install with Windows fully up to date. I'd think this should mean Office is fully patched as well but maybe it is not. How could I confirm this?
3. Since this is a new install, no I haven't. But on the other PC's this user had (this is his 2nd replacement because of this issue), the repair did not work.
As mentioned in #3, since his PC has been replaced twice already and the issue keeps occuring, I'm inclined to think it's some sort of Excel bug.
2. This is a brand new install with Windows fully up to date. I'd think this should mean Office is fully patched as well but maybe it is not. How could I confirm this?
3. Since this is a new install, no I haven't. But on the other PC's this user had (this is his 2nd replacement because of this issue), the repair did not work.
As mentioned in #3, since his PC has been replaced twice already and the issue keeps occuring, I'm inclined to think it's some sort of Excel bug.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Windows Updates were installed over the weekend. Not much was updated since the machine was mostly up to date before giving it to the user.
The issue hasn't occurred again since the OP, will leave this question open for another week in case it does.
The issue hasn't occurred again since the OP, will leave this question open for another week in case it does.
No comment has been added to this question in more than 21 days, so it is now classified as abandoned.
I have recommended this question be closed as follows:
Accept: Rizzle (https:#a41729810)
If you feel this question should be closed differently, post an objection and the moderators will review all objections and close it as they feel fit. If no one objects, this question will be closed automatically the way described above.
frankhelk
Experts-Exchange Cleanup Volunteer
I have recommended this question be closed as follows:
Accept: Rizzle (https:#a41729810)
If you feel this question should be closed differently, post an objection and the moderators will review all objections and close it as they feel fit. If no one objects, this question will be closed automatically the way described above.
frankhelk
Experts-Exchange Cleanup Volunteer
Is MS Office fully patched? Have you tried a repair of Office?