Windows Explorer "Not Responding" at random times

I'm running Windows 7 Professional 64-bit and I've been having problems with windows explorer frequently crashing randomly whether I'm browsing through files or saving a file. For this specific error I was trying to save a .doc file as a .pdf and got this in the details section:

Description:
A problem caused this program to stop interacting with Windows.

Problem signature:
Problem Event Name: AppHangB1
Application Name: WINWORD.EXE
Application Version: 12.0.6545.5000
Application Timestamp: 4c653e57
Hang Signature: a834
Hang Type: 1
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 4105
Additional Hang Signature 1: a834002f0437dc337706e2c608a62061
Additional Hang Signature 2: 7fda
Additional Hang Signature 3: 7fdadc9449791d39cd5923adf7d05fe6
Additional Hang Signature 4: 6bd9
Additional Hang Signature 5: 6bd93e65b6a60d6e1e0145d8d4f146e7
Additional Hang Signature 6: 1ed1
Additional Hang Signature 7: 1ed137538074b3066a9b7feb202b161e

I have no idea what this means so let me know if you need more info. Thanks!

To check for freezing/crashing you need to check several things. First find what is logged in event viewer.


Event viewer.

Type eventvwr in search and go to the windows log>application tab.
Look for errors. Errors have red in the left hand column.

Look for errors that say app hang, or app crash, or anything related to the problem.
When you find them either take a screenshot of them and upload them to us, or note the event ID and source codes and look them up in google. If you cant find them in google tell us what they are.

The file 'Unititled2' is for this specific error.Attachment 192227
Attachment 192226

booyaka said:

The file 'Unititled2' is for this specific error.Attachment 192227
Attachment 192226

The exception code indicates a memory exception. Probably caused by a driver. I would run driver verifier to find which driver is at fault.


Driver verifier

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

I'd suggest that you first backup your data and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

Driver Verifier - Enable and Disable


Further Reading
Using Driver Verifier to identify issues with Windows drivers for advanced users

Occasionally this problem can be associated with a certain program, but there's still an underlying problem with the OS. Don't believe me? Google this: "windows 7" "not responding". Include the quotes. There are over one million hits! When is MS going to address this ?!?!!? I'm REALLY sick of having to fight with this issue on my users' computers.

jcesten said:

Occasionally this problem can be associated with a certain program, but there's still an underlying problem with the OS. Don't believe me? Google this: "windows 7" "not responding". Include the quotes. There are over one million hits! When is MS going to address this ?!?!!? I'm REALLY sick of having to fight with this issue on my users' computers.

Those Event ID's and source codes are often seen. Have you run a system file check?

Run a system file check to verify and repair your system files.

To do this type cmd in search, then right click to run as administrator, then
SFC /SCANNOW

It may need to be run up to three times before successful
Let us know the results from the report at the end.

Read here for more information SFC /SCANNOW Command - System File Checker