V1S restart/shutdown problems

Hi,

I just got my V1S yesterday night. I haven't yet messed around with any settings or done a clean install and this is the first time I've used Vista at all, so maybe I'm just uneducated.

I started up my computer, went through all the prompts, started playing around with a few things, and immediately had a problem with Windows Live Messenger. The entire thing froze. Ctrl-alt-delete to end the program wasn't working. The whole computer was having problems, so I tried to restart.

Enter a 25 minute wait at "logging off" (or maybe it was "shutting down"?) I wasn't sure if this was normal for the first shut-down after booting up the computer, but I was getting impatient, so I eventually manually restarted the computer.

Twice after that, I had smooth shut-downs, but then today I started up the computer and it said there was some kind of error upon startup. It went too fast for me to read the error message, but when I tried to shut down the computer a little later, it took a long time and then the screen went black although the power button and lights on the bottom were still on. I couldn't get the screen to light up again, but it was obviously still not off. After another long wait, I manually shut it down.

Next time I turned on the computer, everything was very sluggish and at 11:54 I tried to shut it down. It is now 12:19 (25 minutes later!) and the computer is still sitting on "Windows is configuring updates...", not any closer to shutting down.

Is it normal for Vista to be buggy until I take some kind of special action? Has anyone else had these problems on stock settings? Do you think a clean install might fix these problems, or should I be worried about something beyond startup/shut-down?

Any help is appreciated!

 

Gah, I left the room after my post, came back, and saw the blue screen of death!

It had some long thing about driver/software failures that I might have had and gave me some instructions, but I didn't have time to fully read it before the computer restarted itself and said that the computer had detected an unsafe shut down.

This is not good

Now it is checking my discs for consistency.

Ok now it is on. I will continue to update if anything else goes wrong :S

 

I would suggest:

Recover Windows entirely to eliminate software issues.
Check RAM with MemTest86+ (google for it and take it from there). BSODs and random errors make me immediately think about bad RAM.

not necessarily in this order.

 

Hi, thanks for the help.
I ran a recovery earlier today after a little bit of sleep and calming down, and it seems to have fixed the problems, but I might do a memtest later, once I get some cds, just to be safe.

 

just letting you know as a piece of information.

On the f3sv, its quite common for the notebook to not shutdown/restart properly until better cam drivers are installed. If youre still running stock cam drivers. take a moment update them and see if that helps maybe.

 

I didnt know about the camera drivers, but I reinstalled vista thinking it would solve the problem. Alas, the problem still plagues me.

On a brighter note, the machine boots noticeably faster now that the bloat is gone. I guess now we'll have to wait for updated camera drivers? The V1S is still pretty brand new, so all the drivers on the site are still the initial releases.

It is really frustrating to have a computer that doesnt shut down when you tell it.

 

have you tried the RAM tests, if you're getting the same type of random errors as in the first post?

 

no random errors to speak of for me. just the issue with shuting down the machine. i'll keep my eyes peeled for some new camera drivers . . .

 

pressing the bluetooth quick key on system shutdownfailure worked for me fine, quite odd, but it works...

im also on the hunt for some better cam drivers... D-Max A311 is the PID for my v1s im guessing we all have the same one...

 

Pressing the bluetooth button to turn service on then off also worked for me to complete shutdown.

 

Then it's pretty clearly a bug in the BT driver or utility...

 

Woohoo! It worked for me too!

So now I'm waiting for a BLUETOOTH driver . . .

Thanks for the help everyone!