OS: Windows 7 Evaluation copy Build 7100 (the most recent Release Candidate)

This started happening within the last week. I don't remember installing any new software and no hardware has been installed recently. Basically any time I try to save anything or open up my C drive to navigate to different folders explorer crashes. It gives me the option to restart explorer which it does but the problems mentioned before remains. I can open outlook and send emails, browse the Internet, etc... but as soon as I try to open a folder explorer.exe crashes. I pasted the error details below:

Problem signature:
Problem Event Name: APPCRASH
Application Name: Explorer.EXE
Application Version: 6.1.7100.0
Application Timestamp: 49ee918d
Fault Module Name: PROPSYS.dll
Fault Module Version: 7.0.7100.0
Fault Module Timestamp: 49eea66e
Exception Code: c0000005
Exception Offset: 00044f82
OS Version: 6.1.7100.2.0.0.256.1
Locale ID: 1033
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789

Read our privacy statement online:
http://go.microsoft.com/fwlink/?link...8&clcid=0x0409

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

What I've tried so far:

• I tried re-registering the PROPSYS.dll, that didn't help
  
• I disabled all non-Microsoft services and all startup items in msconfig, rebooted and the problem remains.
  
• I booted into safe mode
  
• booted into Last known Good Configuration
  
• I couldn't do a system restore because for some reason it was turned off
  
• Searching the web for answers but the only solution I've found is to install windows 7 which obviously wont work for me.

I probably tried a few other things to remedy the issue that I forgot about but the list above contains what i remember trying. Any help or ideas would be greatly appreciated.

Thanks.

This happened to me while I was using the beta in late January. Unfortunately, I never found a solution for it. Also unfortunately, I can't read and understand Microsoft error messages Are there any system restore points? Windows automatically creates them when installing updates, and I know last Tuesday was a patch day. If it's any consolation, after a format/reinstall or moving on to a new build of Windows 7, the problem has never re-occurred.

Haaha this is the sign of malware activity rootkit which is injected into explorer.exe using .dll injection which keeps crashing ,this is due to security holes in windows 7. I recommend you to get windows 7 rtm as soon as possible.

Not what I wanted to hear fellas but I sure do appreciate the replies.

@ MSherwood - As I said in my original post, this is not a beta version; it’s the most recent Release Candidate. I'm pretty sure there's a difference. I also said in my original post, there are no restore points. For some reason I must have turned it off. In my search for a solution I read that this does not fix the problem so it probably wouldn’t have helped anyways, but of course I’ll never know for sure. Come on now MSherwood, pay attention! but seriously, thanks for your input.

@ nikitash - Virtual Slap in the face to you for laughing at me. This is my work PC, I don't go to naughty sites or to the typical virus ridden dark corners of the web. I'd be really surprised if it was mal-ware, virus, etc... but it does behave like one. I'll be upgrading to a retail version soon. Hope that does the trick.

Here's a few more things I tried:

• I ran SpinRite which did not find any problems
• I have Trend Micro Antivirus updated and running
• I ran malwarebytes, it didn't find anything.

Thanks again to both of you for your replies. Anyone else who’d like to chime in please don’t be shy. I’d rather find a real solution than just a quick fix.

@ nikitash or anyone else who might know, is it possible to upgrade from a Release Canidate to a full retail version? You say:

Are you saying I should simply start over, wipe my machine and do a clean install or is it possible to upgrade from a RC to a full retail version?

Thanks

It is possible to install the way you mention, however, it isn't supported. For peace of mind & to prevent similar issues arising again, i advise you should do a 'clean' install. (this is last resort)
I highly doubt it is any nasties causing this and the virtual slap in the face to nikitash is probably well within reason

Have you tried system restore or booting into safe mode??? (couldn't resist sorry!)

Are all of your drivers up to date?
Are you using x86 or x64 Win7 RC? (FYI it still is classed as a beta)
Is the OS otherwise is sound working order?
Do you have many network drives connected to the machine at work?
Do you have access to the event viewer, if so maybe you could upload the logs that are relevant so we can take a look?

@ benodiktine - Virtual Slap in the face to you for laughing at me. This is my work PC, I don't go to naughty sites or to the typical virus ridden dark corners of the web. I'd be really surprised if it was mal-ware, virus, etc... but it does behave like one. I'll be upgrading to a retail version soon. Hope that does the trick.[/list]


Virtual slap? You should really need to go doctor and get check up.

What i am saying is that RC version of windows 7 have full of bugs and security holes and it is unsafe for production PC. As microsoft mentioned dont use RC on your production or work PC.

I told you get Windows 7 RTM final because this will iron out all the bugs remaining in RC version and gives you more reliablity and secure enviroment.

As said in the maintenance phase of SDLC (software development lifecycle) If you fix old/current bugs you will get new ones may be major or minor bugs.

So be careful while using any beta or RC version. Good luck

@ nikitash:

My doctor told me that virtual slaps are a positive and healthy way for an avid internet user to express his or her feelings towards another internet user across the vast endless space that is the interweb. That being said, super triple power double virtual slap to you! If my virtual slaps don't make sense to you, just know they're a friendly joke and join a virtual self defense class.

Back to the subject at hand, I understand everything you're saying but before I do install the RTM I’d like to figure this out. Thanks for your input.

@ rsvr85:

I was about to give you a virtual kick in the nuts when I read that you recommend a system restore/safe mode boot but then I read that you were joking so lucky for you, your balls will go virtually unharmed.

Anyway, I have an RTM version now so I’m going to try to upgrade the RC just to see if it fixes my issue and to see if it’s actually possible, you say it is but I'm a bit skeptical. Afterwards, whether it fixes the issue or not, I’ll do a clean install to ensure I have the most stable install possible. But before all that I'm going to give this nasty problem a few more virtual stabs. People of the internet, your help is welcome and greatly appreciated.

Q. Are all of your drivers up to date?


A. I think so. Everything had been working fine for weeks, maybe months (I don’t remember exactly when I installed the RC) and then out of nowhere it went wacky on me.

Q. Are you using x86 or x64 Win7 RC? (FYI it still is classed as a beta)


A. I’m using x86. So Windows 7 RC is classified as a beta is it… good to know.

Q. Is the OS otherwise in sound working order?


A. Yeah. Outlook incoming/outgoing mail works, IE8, web apps, installed apps, app shortcuts, etc… but when I do any of the following, open files, folders, or HDD’s (local or networked) explorer.exe crashes. Like I said before, I can open apps, word, excel, etc… but when I try to open or save a file from the apps file menu explorer.exe crashes.

Q. Do you have many network drives connected to the machine at work?


A. I have 2 network drives connected, but I think I eliminated them as a potential problem when I booted into safe mode w/o networking and the problem remained, don’t you think?

Q. Do you have access to the event viewer, if so maybe you could upload the logs that are relevant so we can take a look?


A. I do have access to the event viewer. I made explorer.exe crash and here are the relevant logs that appeared after.

START

One System Log:
_________________________________________________________________________________________________________________________________

Log Name: System
Source: Service Control Manager
Date: 11/6/2009 4:28:51 PM
Event ID: 7034
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: IL20WS03.RemoteNetworkSupport.local
Description:
The Windows Search service terminated unexpectedly. It has done this 110 time(s).

Ten Application Logs:
_________________________________________________________________________________________________________________________________
01
Log Name: Application
Source: Application Error
Date: 11/6/2009 4:28:24 PM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: IL20WS03.RemoteNetworkSupport.local
Description:
Faulting application name: explorer.exe, version: 6.1.7100.0, time stamp: 0x49ee918d
Faulting module name: PROPSYS.dll, version: 7.0.7100.0, time stamp: 0x49eea66e
Exception code: 0xc0000005
Fault offset: 0x00044f82
Faulting process id: 0x1030
Faulting application start time: 0x01ca5f2b90655983
Faulting application path: C:\Windows\explorer.exe
Faulting module path: C:\Windows\system32\PROPSYS.dll
Report Id: b18ec2aa-cb23-11de-ba07-000cf1c836a1
_________________________________________________________________________________________________________________________________
02
Log Name: Application
Source: Windows Error Reporting
Date: 11/6/2009 4:28:29 PM
Event ID: 1001
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: IL20WS03.RemoteNetworkSupport.local
Description:
Fault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: explorer.exe
P2: 6.1.7100.0
P3: 49ee918d
P4: PROPSYS.dll
P5: 7.0.7100.0
P6: 49eea66e
P7: c0000005
P8: 00044f82
P9:
P10:

Attached files:

These files may be available here:
C:\Users\bortega\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_explorer.exe_e0e06042a37b60c70262a1afc3267db722d964f_0b3a7dea

Analysis symbol:
Rechecking for solution: 0
Report Id: b18ec2aa-cb23-11de-ba07-000cf1c836a1
Report Status: 0
_________________________________________________________________________________________________________________________________
03
Log Name: Application
Source: ESENT
Date: 11/6/2009 4:28:42 PM
Event ID: 102
Task Category: General
Level: Information
Keywords: Classic
User: N/A
Computer: IL20WS03.RemoteNetworkSupport.local
Description:
Windows (4568) Windows: The database engine (6.01.7100.0000) started a new instance (0).
_________________________________________________________________________________________________________________________________
04
Log Name: Application
Source: ESENT
Date: 11/6/2009 4:28:42 PM
Event ID: 300
Task Category: Logging/Recovery
Level: Information
Keywords: Classic
User: N/A
Computer: IL20WS03.RemoteNetworkSupport.local
Description:
Windows (4568) Windows: The database engine is initiating recovery steps.
_________________________________________________________________________________________________________________________________
05
Log Name: Application
Source: ESENT
Date: 11/6/2009 4:28:43 PM
Event ID: 301
Task Category: Logging/Recovery
Level: Information
Keywords: Classic
User: N/A
Computer: IL20WS03.RemoteNetworkSupport.local
Description:
Windows (4568) Windows: The database engine has begun replaying logfile C:\ProgramData\Microsoft\Search\Data\Applications\Windows\MSS.log.
_________________________________________________________________________________________________________________________________
06
Log Name: Application
Source: ESENT
Date: 11/6/2009 4:28:43 PM
Event ID: 302
Task Category: Logging/Recovery
Level: Information
Keywords: Classic
User: N/A
Computer: IL20WS03.RemoteNetworkSupport.local
Description:
Windows (4568) Windows: The database engine has successfully completed recovery steps.
_________________________________________________________________________________________________________________________________
07
Log Name: Application
Source: Microsoft-Windows-Search
Date: 11/6/2009 4:28:46 PM
Event ID: 1003
Task Category: Search service
Level: Information
Keywords: Classic
User: N/A
Computer: IL20WS03.RemoteNetworkSupport.local
Description:
The Windows Search Service started.
_________________________________________________________________________________________________________________________________
08
Log Name: Application
Source: Application Error
Date: 11/6/2009 4:28:51 PM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: IL20WS03.RemoteNetworkSupport.local
Description:
Faulting application name: SearchIndexer.exe, version: 7.0.7100.0, time stamp: 0x49ee994c
Faulting module name: propsys.dll, version: 7.0.7100.0, time stamp: 0x49eea66e
Exception code: 0xc0000096
Fault offset: 0x00045712
Faulting process id: 0x11d8
Faulting application start time: 0x01ca5f307d10cf96
Faulting application path: C:\Windows\system32\SearchIndexer.exe
Faulting module path: C:\Windows\system32\propsys.dll
Report Id: c1a5acd8-cb23-11de-ba07-000cf1c836a1
_________________________________________________________________________________________________________________________________
09
Log Name: Application
Source: Application Error
Date: 11/6/2009 4:28:51 PM
Event ID: 1005
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: IL20WS03.RemoteNetworkSupport.local
Description:
Windows cannot access the file for one of the following reasons: there is a problem with the network connection, the disk that the file is stored on, or the storage drivers installed on this computer; or the disk is missing. Windows closed the program Microsoft Windows Search Indexer because of this error.

Program: Microsoft Windows Search Indexer
File:

The error value is listed in the Additional Data section.
User Action
1. Open the file again. This situation might be a temporary problem that corrects itself when the program runs again.
2. If the file still cannot be accessed and
- It is on the network, your network administrator should verify that there is not a problem with the network and that the server can be contacted.
- It is on a removable disk, for example, a floppy disk or CD-ROM, verify that the disk is fully inserted into the computer.
3. Check and repair the file system by running CHKDSK. To run CHKDSK, click Start, click Run, type CMD, and then click OK. At the command prompt, type CHKDSK /F, and then press ENTER.
4. If the problem persists, restore the file from a backup copy.
5. Determine whether other files on the same disk can be opened. If not, the disk might be damaged. If it is a hard disk, contact your administrator or computer hardware vendor for further assistance.

Additional Data
Error value: 00000000
Disk type: 0
_________________________________________________________________________________________________________________________________
10
Log Name: Application
Source: Windows Error Reporting
Date: 11/6/2009 4:28:51 PM
Event ID: 1001
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: IL20WS03.RemoteNetworkSupport.local
Description:
Fault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: SearchIndexer.exe
P2: 7.0.7100.0
P3: 49ee994c
P4: propsys.dll
P5: 7.0.7100.0
P6: 49eea66e
P7: c0000096
P8: 00045712
P9:
P10:

Attached files:

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_SearchIndexer.ex_a9ecf1653fe7720da9b173dacc94dc2d32b24a3_120ad263

Analysis symbol:
Rechecking for solution: 0
Report Id: c1a5acd8-cb23-11de-ba07-000cf1c836a1
Report Status: 4
_________________________________________________________________________________________________________________________________

END

I looked at the logs briefly and noticed 3 files came up a lot:

• SearchIndexer.exe
  
• explorer.exe
  
• PROPSYS.dll

Let me know if you have any ideas or suggestions. I'm going to take a closer look at this later. I'll let you know if I find anything.


Many thanks to all of you.

Not matter how big your virtual kick in the nuts would've been, my trusty firewall is always here to block it.

Why not just clean install W7 RTM now. Why bother trying to upgrade RC to RTM? (trust me, it is possible )

@benodiktine

Now you have prove me son u really an psycho kid who needs mental doctor to tighten your brain nuts and make you understand that give respect to others to get respect.

You are a indiscipline child who needs slap on your face daily by you parents just before sleep and in the morning so that you understand how to talk with manners.

You at this forum not asking for help but finding ways to harm and disrespecting our respected members of this forum.

Watch your language before admin ban u.