[matt.]

Ok, i work repairing computer's at a local computer shop and i've seen INCREASING!!! to the point where it isn't acually funny where people are experinceing a UserInit.exe Application Failed to load at 0xc0000005, now the Senior Techs have been playing around and they are pretty sure it's either something to do with a microsoft update or a new type of malware.

So i'm just letting you no now.
Only resuce programs like GPARTED or SystemRescue can save data, you HAVETO reinstall windows a fresh copy.

Yes i no it's absolute [bleep], i had the same application error and nothing fixed it.
you experience
Constant Application error's when first infected
Note* My Computer was honestly recently infected i mean a matter of minutes with ErrorSafe and this began 2 happen
Reboot computer and after loading screen your Userinit.exe Application error appears once again.
No Login screen appears and same with trying to login into Safe Mode
System Restore doesnt work
Last known good configuration Doesnt work
Repairing Windows using a CD WILL NOT WORK!
- After trying to repair using a Windows CD it will come close to the end of the repair, and either continue with reboot or give you an error of Internal Configuration is invailed please contact system Administrator Error code 9

Umm.. what else, yeh after you reboot you will get a Reboot cycle meaning, loading screen appears System repaing is restarting in a Blue screen (Not bsod) then loading screen appears and reboot and so on and so forth.. this happens when trying to repair windows.

I no if i'm wrong then you administrator's can have a look into it.
Thanks.

but it does seem quite suss since i've had to reinstall about 20+ Machines with the same error?
umm yeah, so advising people to do these steps probz = waste of time if im correct.

[Advertisements]

This error can be a hardware issue not just a malware error.
Without meaning to teach your grandma how to suck eggs, rather than just wiping the machines have you tested the hardware? Most common scenarios are the hard drive(s) and the memory (or, depending on the age of the board, the motherboard itself)?
I have seen similar scenarios play out and then disappear when the drive was cloned to a new one.

[Neil Jones]

This error can be a hardware issue not just a malware error.
Without meaning to teach your grandma how to suck eggs, rather than just wiping the machines have you tested the hardware? Most common scenarios are the hard drive(s) and the memory (or, depending on the age of the board, the motherboard itself)?
I have seen similar scenarios play out and then disappear when the drive was cloned to a new one.

[matt.]

yes we ghoasted hard drives, replaced ram. Hdd was not faulty.

Apparently the error code says it's a ram issue but it wasn't.
Nah, all componant's are new. but yeah we replaced them.
Even if it was faulty, Windows Repair would of at least finished to whipe over windows instead of crashing half way through.

Grandmar asks for some more suggestions.