New
#11
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?
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?
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
You're welcome. I am very glad to hear it is back up and running! Thanks for posting back your steps.
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.
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!
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.
Last edited by Casp; 04 Mar 2012 at 08:41.
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:
- Shut down and turn off your computer.
- Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
- Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
- 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.