DEP error and Explorer.exe crash on multiple computers?
Posted on 2008-10-01
Since Monday (it's now Wednesday) some users on our network have been getting the Data Execution error and when clicking close Explorer.exe error occurs, task bar disappears and comes back and all is fine again.
It seems to happen when programs are closed.
It started on one machine, then a 2nd machine started yesterday and today a 3rd machine. I am worried this issue is spread to the whole network. It is very annoying and obviously a huge interruption to work.
I'm not going to post the whole message as I have trouble replicating the error on demand and don't have a copy of it, however when I did some googling on the error, because the event error says unkown module in explorer.exe caused the error I presume the whole message won't help in this case.
So I guess I am asking, has anyone else had a issue like this recently?
Could it be an antivirus (sophos) update? The 3 machines in question all have sophos and office. 2 have SP3 and 1 has SP2. 2 have office 2007 and 1 has office 2003, so only sophos is the same on all machines, yet all our other 15 machines remain unaffected so far.
If it is a Sophos update causing this then I expect all machines to suffer from it soon and I expect many people around the world to have the same issue.
I don't think it's a domain error as one machine is set to log on locally and not the domain.
The machines in question also lost their desktop wallpaper randomly over the past few weeks so this could be related.
I have used shell viewer to close all non-microsoft modules but I think this led to the corruption of an outlook mail box, either way I tried disabling different modules on each machine and so far the problem hasnt occurred.
The only other thing I can think would cause this would be Spiceworks, perhaps it's scanning and causing this.
If anyone has seen a similar issue or could take a guess at what it is to help save me some time it would be much appreciated.
Otherwise I will have to figure out what module is causing the issue and then try to fix the problem from the source and not the explorer.exe module.
...All machines are windows XP