Two problems, basically

[Casp]

Hi,

First of all, sorry to make another topic / thread so soon after I made the other one regarding a high usage of RAM.

My first problem, and biggest problem, would be that my explorer.exe keeps crashing instantly after starting up. I tried searching this forum and it came up with Troubleshooting Explorer.exe Crashing Issues - Windows 7 Forums. As you can read, on the first step it says I have to try an sfc /scannow which leads to my second problem, it gives me the error that I have to be a computer administrator, which I am.

Picture 1, the explorer.exe crash.

Picture 2, the non-admin admin problem.

Thanks in advance!

 

[bru]

I think I can help get your SFC working. You need to right click the command prompt and select "run as administrator". Then the SFC /SCANNOW should work.

 

[Casp]

I think I can help get your SFC working. You need to right click the command prompt and select "run as administrator". Then the SFC /SCANNOW should work.

Alright, this one works! Didn't even think of it. Thanks!

Running fine so far. Now just one problem left, anyone has an idea?

 

[writhziden]

Let us know the results of the system file check. We can proceed from there.

There a couple other steps that can be tried that are not included in that thread by Capt.Jack Sparrow. One is similar to the step outlined in 1., the other is the Microsoft Fix It tool. Also, 3. now has a Windows 7 version: Fix a corrupted user profile

 

[Casp]

I have completed the scan and it brought me that there is a corrupted file in my file system (obviously!). It also tells me that it couldn't fixed it 'cause of a reason. A log file has been made with the details, but I cannot look into that 'cause of my problem with the folders.

 

[writhziden]

You may need to run the SFC up to three times to fix any problems. Let us know if you still have errors on a fourth run.

 

[Casp]

You may need to run the SFC up to three times to fix any problems. Let us know if you still have errors on a fourth run.

After reading your comment, I wanted to try again.

Pressed Start > Searched for "cmd" > Instant explorer.exe, 7 times in a row? I'm so lost here..

 

[writhziden]

Alright, try to http://www.sevenforums.com/tutorial...ation-conflicts-performing-clean-startup.html and see if the problem is related to software on the system causing conflicts.

You could also try running SFC by using the http://www.sevenforums.com/tutorials/666-advanced-boot-options.html to get into http://www.sevenforums.com/tutorials/69585-safe-mode.html.

http://www.sevenforums.com/tutorials/139810-sfc-scannow-run-command-prompt-boot.html may also be helpful.

 

[Layback Bear]

Rebooting between every sfc /scannow is a must.

 

[Casp]

Alright, try to http://www.sevenforums.com/tutorial...ation-conflicts-performing-clean-startup.html and see if the problem is related to software on the system causing conflicts.

You could also try running SFC by using the http://www.sevenforums.com/tutorials/666-advanced-boot-options.html to get into http://www.sevenforums.com/tutorials/69585-safe-mode.html.

http://www.sevenforums.com/tutorials/139810-sfc-scannow-run-command-prompt-boot.html may also be helpful.

Rebooting between every sfc /scannow is a must.

Hm, none of these things just listed worked. However, I was not able to try the last one (http://www.sevenforums.com/tutorials/139810-sfc-scannow-run-command-prompt-boot.html) because I did not yet create a repair disk nor do I have the installation DVD since I bought the laptop pre-installed with Windows 7 Home Premium x64.

In fact, I followed the first step from the first topic listed ( http://www.sevenforums.com/tutorial...ation-conflicts-performing-clean-startup.html) and it said to restart the computer, so I did. However, now I can't get into my msconfig anymore because of the explorer.exe crash problem. http://www.sevenforums.com/tutorial...ation-conflicts-performing-clean-startup.html http://www.sevenforums.com/tutorials/139810-sfc-scannow-run-command-prompt-boot.html

 

[writhziden]

Yeah, the clean startup was a long shot considering there are errors found with sfc... What happens if you try to run sfc in safe mode?

 

[Casp]

Alright this is fixed. I just used the sfc /scannow command a couple of times, went into Safe Mode with Command Prompt. Used it again, restarted it. Read something about a corrupted user account in one of the topics linked above, so I tried to make a test account. I made the user account and it was working fine, so I went back on my original user account and then suddenly it was working fine.

Thanks to:
- Bru
- Layback Bear

Special thanks to:
- writhziden
http://www.sevenforums.com/member.php?u=74329

 

[writhziden]

You're welcome. I am very glad to hear it is back up and running! Thanks for posting back your steps.

 

[bru]

That's good news.

Interesting about how the new user account figured in. I take it you had not tried the original user account until you had created the new account.

I think I have the need to replace my user account to fix some problems but really don't want to. I wonder if creating a new account may "fix" the existing one.

 

[Casp]

That's good news.

Interesting about how the new user account figured in. I take it you had not tried the original user account until you had created the new account.

I think I have the need to replace my user account to fix some problems but really don't want to. I wonder if creating a new account may "fix" the existing one.

Can't it be that the new user account made some changes / "fixes" to the registry, and that's why it was fixed somehow?

 

[writhziden]

Depends. Did you try the old account after doing SFC? Or did you create the new account after doing SFC and then you found the old account worked?

I would be very surprised if creating a new user fixed the registry for the old user, but I wouldn't discount it entirely. Windows does some strange/miraculous things to fix itself from time to time.

 

[Casp]

Depends. Did you try the old account after doing SFC? Or did you create the new account after doing SFC and then you found the old account worked?

I would be very surprised if creating a new user fixed the registry for the old user, but I wouldn't discount it entirely. Windows does some strange/miraculous things to fix itself from time to time.

I tried to do 4 SFCs on the old account because you guys told me it could take up to 3-4 tries before it's fixed. Then I made the account, restarted my computer and tried it out. It was working fine there, so I logged on my original account and it was gone. And until now it's still gone!

 

[Layback Bear]

Your fixed, that is good to read. I run sfc /scannow a couple times a week for maintenance.

 

[Casp]

Ok, so today I tried to make a new folder on my desktop. I created it, tried to access it. Boom, error's back. Tried to do the same steps as I did before to get it working again, didn't work. Tried to create a new user account again, logged it on, tried to access my folders and it crashed right after. However, this time it left me with an error message:

The instruction at referenced memory at 0x800051da to 0x02ae0000. A read or write operation on memory failed: written.

Could it be that my RAM-memory is damaged? I recently had my harddisk crashed and after the fix, I started to have problems with it. I brought it back to the local electronics store here, could it be that they somehow managed to damage my computer heavily? Installed RAM-memory is still 6GB if I look at my computer's properties.

 

[writhziden]

Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).

If you swap any memory components, follow these steps for ESD safety:

1. Shut down and turn off your computer.
2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working.

Once these steps have been followed, it is safe to remove and replace components within your computer.