inability to reboot

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have been using Vista since its general release without any major issues.

But now I cannot load vista
When i restart i get to the vista load screen and when i press F8 i can get
to the menu.
I can get it to load in all safe modes but that is it.
Last good config does not work nor do any of the other menu choices (4-8)
when clicked a black screen loads that shows my mouse and the vista build
info but desktop or user settings will not load at all.
This is new and i have not installed any new hardware.
Earlier I did have 2 crashes (BSOD) and assumed the info was sent to MS,
but i didn't recieve a popup telling me the reason for the crash. And now i
cannot get to it to relay that info to anyone that can help.

Any info would be a help
thanks
 
Hi,

At a guess I'd say it's probably unstable drivers. Not all device drivers
are loaded in safe mode, which is why you can boot there but not in normal
mode. You might run the event viewer in safe mode to see if the system logs
show any useful information. Details of the BSOD error messages might give
an indicator as well.

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP

Windows help - www.rickrogers.org
 
laineya--

If you have a Vista DVD, there is a promising "feature" or utility in Vista
called Win RE or Windows Recovery Environment.

***Accessing Windows RE (Repair Environment):***

1) Insert Media into PC (the DVD you burned)

2) ***You will see on the Vista logo setup screen after lang. options in the
lower left corner, a link called "System Recovery Options."***

3) Select your OS for repair.

4) Its been my experience that you can see some causes of the crash from
theWin RE feature:

You'll have a choice there of using:

1) Startup Repair
2) System Restore
3) Complete PC Restore

CH

______________________________________________
 
I had a similar but not quite the same situation yesterday. My problem
was the graphics driver and the way Vista implements new display
settings. Anyway here is something to try.

It looks like driver problems of some kind and I'd guess video or sound
so try this;

Boot into safe mode.
Go to device manager and disable your video and sound card drivers.
Boot normally into Vista and, if you get in, you know it has to do with
one of those drivers. If so go to device manager again and select update
driver and let windows go to the net to find new ones if poss. If it
doesn't find a new one then go to the web sites of the makers and see if
you can get alternative drivers.

I found that if I reloaded the original driver I still had a problem
when rebooting.
 
Bernie said:
I had a similar but not quite the same situation yesterday. My problem
was the graphics driver and the way Vista implements new display
settings. Anyway here is something to try.

It looks like driver problems of some kind and I'd guess video or sound
so try this;

Boot into safe mode.
Go to device manager and disable your video and sound card drivers.
Boot normally into Vista and, if you get in, you know it has to do with
one of those drivers. If so go to device manager again and select update
driver and let windows go to the net to find new ones if poss. If it
doesn't find a new one then go to the web sites of the makers and see if
you can get alternative drivers.

I found that if I reloaded the original driver I still had a problem
when rebooting.




I want to thank everyone that replied to my post.
Click to expand...
I had to reinstall vista on that partition tho, due to the fact that when in
safe mode my keyboard would not function, so any attempt to access say the
device manager was out of the question.
I really like Vista and altho I am aware this is a beta, I am still using it
as my primary OS ( I know I know LOL) thankfully XP is still on the other
partition.
Have a great day one and all.
 
Bernie said:
I had a similar but not quite the same situation yesterday. My problem was
the graphics driver and the way Vista implements new display settings.
Anyway here is something to try.

It looks like driver problems of some kind and I'd guess video or sound so
try this;

Boot into safe mode.
Go to device manager and disable your video and sound card drivers.
Boot normally into Vista and, if you get in, you know it has to do with
one of those drivers. If so go to device manager again and select update
driver and let windows go to the net to find new ones if poss. If it
doesn't find a new one then go to the web sites of the makers and see if
you can get alternative drivers.

I found that if I reloaded the original driver I still had a problem when
rebooting.
Click to expand...
 
Drivers are always high on the list of possible Windows No Boots, but then that poses the question of which driver you try. If you go to your cmd prompt in XP or Vista and type the cmd driverquery you have roughly 150-200 kernel drivers and 30-40 non kernel drivers and some of them are software although software drivers are rarely mentioned. I've seen people on the MSFT driver device team glibly state in chats that hardware drivers cause 80% of blue screens and that's not exactly the whole picture and leaves out a way to configure driver verifier to prevent them--it's a non-nuanced over simplification.

A significant cause of no boots that MSFT has yet to latch onto is the way driver verifier inspects antivirus software drivers. Often disabling deadlock detection using the driver verifier tool by typing "verifier" (lose quotes) in the run box and disabling deadlock detection and inspection of your antivirus software drivers will prevent a number of BSOD stop/no boots in XP and Vista.

Disabling deadlock detection and inspection of antivirus drivers is good preventive medicine against Windows Blue Screens. This does nothing to impact the running of your Antivirus and people know the antivirus programs they choose are reliable and don't have software drivers that threaten them. Any driver can become "corrupt" of course. Most AV programs anyone will ever use come from large companies who have experience in making AV applications--Win One Care--my fave but no ready for prime time Vista included. Win One Care will work in Vista when Microsoft's Live Division learns how to call Microsoft and get this going. Both reside in buildings at Redmond. All of them have IM and cell phones. Hopefully this will happen between now and November to March 07 whenever Vista RTMs--but maybe not.

How to Use Driver Verifier to Troubleshoot Windows Drivers
http://support.microsoft.com/kb/244617/en-us


My point is that although the drivers most people think about most of the time are Video and Sound and hardware drivers , this is time consuming and hit or miss. Video and sound are mentioned because video and sound cards are two of the most publicized hardware devices due to gaming and graphics apps.

If you run Win RE's Startup Repair in Vista, it will try to check and repair the following and we're taking about under three minutes usually when it works which is often: (this is not a complete list but a list of major tasks it can perform):

1.. Registry Corruptions
2.. Missing/corrupt driver files (you don't have to guess here--it looks at all of them
3.. Missing/corrupt system files (disabled in Beta 2 as is System File Checker but present newer builds)
4.. Incompatible Driver Installation
5.. Incompatible OS update installations
6.. Startup Repair may offer a dialogue box to use System restore.
Corporater customers will be able to launch Win RE from a WDS server.

CH
 
Leineya--

******What happened when you tried Win RE from the DVD in setup as I suggested?****

My point is that although the drivers most people think about most of the time are Video and Sound and hardware drivers , this is time consuming and hit or miss. Video and sound are mentioned because video and sound cards are two of the most publicized hardware devices due to gaming and graphics apps.

If you run Win RE's Startup Repair in Vista, it will try to check and repair the following and we're taking about under three minutes usually when it works which is often: (this is not a complete list but a list of major tasks it can perform):

Registry Corruptions
Missing/corrupt driver files (you don't have to guess here--it looks at all of them
Missing/corrupt system files (disabled in Beta 2 as is System File Checker but present newer builds)
Incompatible Driver Installation
Incompatible OS update installations
Startup Repair may offer a dialogue box to use System restore.
Corporater customers will be able to launch Win RE from a WDS server.

A significant cause of no boots that MSFT has yet to latch onto is the way driver verifier inspects antivirus software drivers. Often disabling deadlock detection using the driver verifier tool by typing "verifier" (lose quotes) in the run box and disabling deadlock detection and inspection of your antivirus software drivers will prevent a number of BSOD stop/no boots in XP and Vista.

It has worked repeatedly on boxes even when you can do a repair install and get XP back intact or Win RE and get Vista back intact and the BSOD's still recur. The point is not all of them are due to the drivers themselves when a driver is involved; sometimes they are due to the way Driver Verifier inspects them in windows:

References:

Note: The principle of disabling deadlock detection and inspection of software AV app drivers applies to any AV app with software drivers--***not just Norton.

Fatal System Error: 0x000000C4 If Deadlock Detection in Driver Verifier Is Turned on and Norton Antivirus Is Installed
http://support.microsoft.com/kb/325672/en-us

http://www.osronline.com/showThread.cfm?link=77303

Locks, Deadlocks, and Synchronization
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dndevice/html/Locks_Sync.asp

Driver Verifier in Windows Vista
http://www.microsoft.com/whdc/DevTools/tools/vistaverifier.mspx


Disabling deadlock detection and inspection of antivirus drivers is good preventive medicine against Windows Blue Screens. This does nothing to impact the running of your Antivirus and people know the antivirus programs they choose are reliable and don't have software drivers that threaten them. Any driver can become "corrupt" of course. Most AV programs anyone will ever use come from large companies who have experience in making AV applications--Win One Care--my fave but no ready for prime time Vista included. Win One Care will work in Vista when Microsoft's Live Division learns how to call Microsoft and get this going. Both reside in buildings at Redmond. All of them have IM and cell phones. Hopefully this will happen between now and November to March 07 whenever Vista RTMs--but maybe not.

CH
 
Back
Top