Windows Explorer crashes after i open the Recycle Bin in Win 7!

windows 7 x64bit home sp1

hi

when i open the recycle bin it crashes after 5 seconds:

WITH GUEST ACCOUNT I DON'T HAVE THAT PROBLEM

Problem signature:
Problem Event Name: APPCRASH
Application Name: explorer.exe
Application Version: 6.1.7601.17567
Application Timestamp: 4d672ee4
Fault Module Name: msmpeg2vdec.dll
Fault Module Version: 6.1.7140.0
Fault Module Timestamp: 4a5bdff2
Exception Code: c0000005
Exception Offset: 00000000000a80f5
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 2057
Additional Information 1: 157c
Additional Information 2: 157c8b2638efd604f74d89935d9a0992
Additional Information 3: 6496
Additional Information 4: 6496ba3188636da259d515b634b984b6

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

Log Name: Application
Source: Application Error
Date: 21/05/2012 19:20:49
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: dell
Description:
Faulting application name: Explorer.EXE, version: 6.1.7601.17567, time stamp: 0x4d672ee4
Faulting module name: msmpeg2vdec.dll, version: 6.1.7140.0, time stamp: 0x4a5bdff2
Exception code: 0xc0000005
Fault offset: 0x00000000000a80f5
Faulting process id: 0xa70
Faulting application start time: 0x01cd377e69d99e22
Faulting application path: C:\Windows\Explorer.EXE
Faulting module path: C:\Windows\System32\msmpeg2vdec.dll
Report Id: b0b1eb67-a371-11e1-8715-002564eceab5
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2012-05-21T18:20:49.000000000Z" />
<EventRecordID>36768</EventRecordID>
<Channel>Application</Channel>
<Computer>dell</Computer>
<Security />
</System>
<EventData>
<Data>Explorer.EXE</Data>
<Data>6.1.7601.17567</Data>
<Data>4d672ee4</Data>
<Data>msmpeg2vdec.dll</Data>
<Data>6.1.7140.0</Data>
<Data>4a5bdff2</Data>
<Data>c0000005</Data>
<Data>00000000000a80f5</Data>
<Data>a70</Data>
<Data>01cd377e69d99e22</Data>
<Data>C:\Windows\Explorer.EXE</Data>
<Data>C:\Windows\System32\msmpeg2vdec.dll</Data>
<Data>b0b1eb67-a371-11e1-8715-002564eceab5</Data>
</EventData>
</Event>


i don't know if this helps but i had this too:

COM SURROGATE

Description
Faulting Application Path: C:\Windows\System32\dllhost.exe

Problem signature
Problem Event Name: APPCRASH
Application Name: DllHost.exe
Application Version: 6.1.7600.16385
Application Timestamp: 4a5bca54
Fault Module Name: msmpeg2vdec.dll
Fault Module Version: 6.1.7140.0
Fault Module Timestamp: 4a5bdff2
Exception Code: c0000005
Exception Offset: 00000000000a80f5
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 2057
Additional Information 1: 22a3
Additional Information 2: 22a319d0bcfdc0bd56963acb8c273c3e
Additional Information 3: bfa8
Additional Information 4: bfa86845f197dd93d51468b9088994c2

Files that help describe the problem
WERInternalMetadata.xml
AppCompat.txt
memory.hdmp
minidump.mdmp

You may want to take a look at: Fix a corrupted user profile

These crashes were caused by memory corruption/exception (Cx05) probably a driver.
Please run these two tests to verify your memory and find which driver is causing the problem.

* If you are overclocking anything reset to default before running these tests.
In other words STOP!!!

* If you have a Raid update its Driver.



Memtest.

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

*Boot from the CD, and leave it running for at least 5-7 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

Any errors are indicative of a memory problem.

If a known good stick fails in a motherboard slot it is probably the slot.

RAM - Test with Memtest86+






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 stuff 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"IRP Logging and Force Pending I/O Requests. and click "Next"
NOTE: You can use Low Resource Simulation if you'd like.
From my limited experimentation it makes the BSOD's come faster.
- 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.

If you are using win 8 add these
- Concurrency Stress Test
- DDI compliance checking

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.
Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.


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.

Thanks to JCGriff2 & Usasma.

Sysnative Forums

Driver Reference Table (DRT)

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

Driver Verifier

Using Driver Verifier (Windows Drivers)

i don't have the problem anymore

i don't know why

if happens again, i will do that

thanks

You are welcome.
Thanks for letting us know all is well.