The new forums will be named Coin Return (based on the most recent vote)! You can check on the status and timeline of the transition to the new forums here.
The Guiding Principles and New Rules document is now in effect.

wuauclt.exe has encountered a problem and needs to close.....

Teslan26Teslan26 Registered User regular
Hi, there might be rather a lot of words here as I try and give a good impression of where I am and how I got there.


XP pro, service pack 3, it has always been set to update itself automatically.

5 days ago I installed a new second hard drive, and by installed I mean plugged in and it auto installed itself. No problems.

Yesterday the computer would not boot. It was crashing as soon as mup.sys was loaded (I am told that means it had begun trying to allocate resources). After removing the new hard drive, it booted fine, I am suspecting that in the move the SATA cable had come loose? Reconnected the hard drive and making sure everything was secure. Computer booted fine.

However now Avast was not starting properly. Uninstalled and reinstalled that. Did a boot scan and another normal full scan. Nothing came up.

Last night the title error (wuauclt.exe has encountered a problem and needs to close. We are sorry for the inconvenience.) began occuring every minute or so. Tried stopping the process in task manager to minimal effect. It is located in system32 as would be expected, so it is a legitimate process. It is, however, breaking regularly. Every time it crashes I get a small freeze and then the reporter box appears. Only thing I can think of is turning automatic updates off.

Ooh, new thing. No sound.

I really do not want to have to re-format, use the windows disk to attempt a repair? Any other obvious thoughts?

Teslan26 on

Posts

  • Teslan26Teslan26 Registered User regular
    edited December 2010
    Restarted. Failed to boot, unable to find \windows\system32\config\system

    Have the windows disk, it puts me into the recovery console. No real idea how to use that.

    Teslan26 on
  • Teslan26Teslan26 Registered User regular
    edited December 2010
    Chkdsk on the windows install tells me this:

    CHKDSK found one or more errors on the volume


    There is no repair option if I go through set up, so there appears to only be the option to use the recovery console in order to restore windows.

    Teslan26 on
  • GreenishGreenish Registered User regular
    edited December 2010
    The command you are looking for to run in the recovery console is

    chkdsk C: /f /r

    This takes forever.

    If that doesn't work then try a repair install. Go through windows setup and hit enter to setup windows, then F8 to agree, then R to repair.

    Greenish on
  • Teslan26Teslan26 Registered User regular
    edited December 2010
    Greenish wrote: »
    The command you are looking for to run in the recovery console is

    chkdsk C: /f /r

    This takes forever.

    If that doesn't work then try a repair install. Go through windows setup and hit enter to setup windows, then F8 to agree, then R to repair.

    there is, i'm afraid, no repair option when I do that.

    I shall try the chkdsk command and report back. chances that my hard drive is failing? 4+ years old.

    Teslan26 on
  • Teslan26Teslan26 Registered User regular
    edited December 2010
    The checkdisk doodad has now resulted in the repair option being there when I run the setup. That is a massive step forward, thank you.




    Edit: Step back again. Ran the repair tool, and am now back where I was before running chkdsk.

    Gash

    Teslan26 on
  • SpudgeSpudge Witty comments go next to this blue dot thingyRegistered User regular
    edited December 2010
    Most likely your HDD is toasting, though it could be RAM too. I've seen this caused by both

    This should help though

    Spudge on
    Play With Me
    Xbox - IT Jerk
    PSN - MicroChrist

    I'm too fuckin' poor to play
    WordsWFriends - zeewoot
Sign In or Register to comment.