Windows Vista Vista can't get to desktop or safemode

I need help describing my problem. What is the name of the screen that you see with the various users listed as Vista Boots?

I need to know that because whatever the name of that screen is, it is the last screen I see, for about 5 or 10 seconds, before the computer I am working on shuts down and restarts.

I cannot get to the desktop (it reboots as soon as I try to click on a user and the word "Welcome" appears), I cannot start it safe mode (it reboots before it gets there), I cannot start it with automatic restart on system failure disabled– it just restarts so I do not see any bsods and error numbers . I cannot believe that Microsoft designed this OS so that it cannot be overlaid, (reinstalled over itself) without destroying users accounts and programs the way that XP could

I have cleaned a number of virus from the system and check the drives physical interity by scanning it with another computer. I have also found (and removed) one stick of bad memory. I have tried working with the Windows RE (Windows Recovery Environment) from the installation DVD. It runs through its startup recovery, it reports that Startup Repair could not detect any problems, yet when I the machine and then it reboots when it gets to whatever that screen is called.

I can get to the Windows RE command prompt (not safe mode command prompt) if I boot from the install DVD. I have tried to run SFC, eventmon, and eventvwr from there but they don’t seem to work.

Can anyone help me?

 

Hi and welcome to the BBS,

Look through the motherboard manual for the computer. If you have removed one RAM module, you may need to put the remaining module into a different slot for it to work on it's own. Some manufacturer's information is not clear whether a "matched pair" of RAM modules is necessary for the system to run correctly. If you replaced both modules, they may not be compatible with the motherboard.

Viruses are usually intended to cause damage to the system. Depending on their nature, they may be able to be removed without damage to the system, but their intention I expect, is the opposite. In the situation you describe, I might expect that the registry was damaged. I might try some of the repairs you describe, but not waste too much time before backing up the data and reformatting. Even if the system got going again, I would always be wondering if it was working correctly. I would not hesitate to reformat, rather than patch back together an "iffy" system.

Matt

 

Mattman, thanks for responding to my question.

As to checking if the motherboard needs both sticks of ram, I should have mentioned that I did do a test fresh install, on a separate drive, to see if there might be some physical cause for the rebooting. It seems to work ok.

I am, however, a little shocked by your suggestion that since the machine was infected it is probably best to wipe the drive and start again. I understand your reasoning and the concept is supported by other mega-geeks (Leo La Port for one I think) but this is a family’s machine "“ six users as I recall, replete with all of the memories and data that entails. I have been able to salvage the drive but it will be a nightmare to restore. And if that is all they wanted they could have taken it to the Geek Dogs or some "$99.00 fixes all" shop.

Besides, if I do that, I won’t learn how to fix Vista

 

Thanks Arie, I must say that I am impressed with the group. I have posted this questions to several of the "Leading" communities and this is the only one I have any response from so far.

Thanks for the link. I had come across that and did not see the answer I was looking for. I had assumed I was just too dumb to see it.

Perhaps I am asking the question the wrong way. Let me try another approach. Given that I have the hard drive from the machine in question and several other XP/Vista machines at my disposal, Is there any way to view the event view, performance monitor or anything else that might help me identify the problem?

 

I certainly wouldn't discourage you from learning about Windows

If it is not possible to boot into Safe Mode though, that's when most of us start looking at reinstalling Windows. Vista has a different system which you are trying now, but as I was saying, if the registry is corrupt I doubt you might ever get it working 100% again.

I don't go looking for fast processors or large amounts of RAM, great graphics, etc, but I do want the operating system working correctly.

If they were actually viruses, their aim is to damage the system. Removing them doesn't mean the damage has been reversed.
________________________________________________________________
I am like you, I like to find out why the system is not working. I have found though, that getting an "adaptable" system is more important. What will the family members do if it cannot be fixed? What would they do if the HDD failed? Is the system backed-up? I think all the experienced people here will tell you to always expect the worst outcome. Getting the system back to where it was previously is the aim. Ask anyone that looks after business data.

Getting them back to a working system in the event of a catastrophe would be something I would be concentrating on. OEM manufacturer's technicians working on the machine under warranty would have advised reformatting as soon as they heard the word "virus ".

Finding out how to avoid getting viruses and other malware is what I try to advise my family members on.

Learn, learn, learn, yes. Don't forget about avoiding problems from where they stem or having an "emergency backup plan" either.

Matt

 

I think I have found (great geek forgive me) a simpler way. Allow me to explain. I did pursue the information about wevtutil a bit. I found that it does not exist in Windows XP (totally irrelevant information to this discussion but it does sound good). And tried a few of its commands . While doing so, in the process so to speak, I found out where the log files actually live, C:\windows\system32\winevt\logs. Armed with that knowledge I found that I could attach the hard drive from the crashed machine to a working Vista (did not try attaching to an XP "“ but that might work as well) machine and opened them directly from there.

End result is "“ correct me if I am wrong- that the command prompt option of Windows RE, like its predecessor the Windows Recovery Consol, is for the most part, an interesting curiosity, since most if not all of its functions can be performed quicker and slicker by slaving the hard drive in question to a functioning machine.

Now that I can read the logs the question arises "¦ What the hell am I looking for? Which if any of them is the "Performance Monitorâ€? Most importantly, where would I find clues as to what is causing the system to reboot after reaching the login screen?

 

For a couple of reasons. First of all, it is a new tool and I think the more I use it the quicker I will learn about it. Also, I think I have seen that it can list historical incidents where the machine may have had trouble, any of which could be a clue to what is causing the problem.

Where do you think I should be looking?

 

It is one thing when I don’t know what I am talking about, it quite another when you don’t know what I am talking about.

It could mean that I am more lost than I know.

So, where do we go from here