I have come across a user having a problem with a faint white screen coming over their whole screen with the "Not Responding" error on top of the current open window above the address bar. This error freezes the user's PC from 30 seconds to 1 minute. This error seems to happen while the user is only working within Microsoft Office applications, mostly within Microsoft Project (That is the main application that this user works with everyday). I have looked into the user's PC and they are not running extra programs in the background or services that would bog down the PC overall. The even viewer log error details are as follows:
Faulting application name: WINPROJ.EXE, version 11.3.2007.1529, time stamp 0x465bf9b1
Faulting module name: ntdll.dll, version: 6.1.7600.16915, time stamp: 0x4ec49caf
Exception code: 0xc0000374
Fault Offset: 0x000c33bb
Faulting process id: 0xaf4
Faulting application start time: 0x01cdb9007f27256f
Faulting application path: C:\Program Files\Microsoft Office\OFFICE11\WINPROJ.EXE
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: e4b8f6b6-24f3-11e2-a1e6-b499bae70793
Log Name: Application - Source: Application Error - Event ID: 1000 - Level: Error - User: N/A - Logged: (Today) - Task Category - (100) - Keywords: Classic - Computer: (Computer name.network. . .)
The user goes into his Microsoft Project open project and makes some changes, highlights some cells and goes to make some changes and then the faint white screen comes up with the "Not Responding" screen appears. Some background information. This problem happens both on wireless and docked plugged into the LAN. Our user's have a network drive (home drive) located about two blocks away at my location. This problem is not specific to accessing information only on the network drive though, already tried that scenario. This user does not have administrative rights. I took my laptop over to their location/building and tried to replicate the issue myself and I was not able to do so. I did not stay more than a hour and a half (may need to stay there all day to replicate). Multiple user's in that building report having this specific issue that the one user I am working with now is reporting the faint white screen "not responding" error. All operating machines are using Windows 7. This happens on both laptops and desktops. There is not a ton of software or processes running in the background to bog down the user's computer.
Does anyone have any ideas??