How do I remove a driver if i'm getting a blue screen during start

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

Guest

I have a dell 9100 and upgraded to Vista. Everything worked perfectly until
I tried to install Alcohol 120%. In the middle of the installation I got the
dreaded blue screen of death. Vista does not start in any of the safe mode
options and when I chose to start normally, Vista starts up but goes to the
blue screen within seconds because Vista was still trying to load the drivers
from Alcohol 120%. I still have some documents that I want to save. I tried
dropping in the Vista installation DVD but it doesn't register when I restart
the computer. How do I either remove the faulty Alcohol program and drivers,
or how do I repair Vista, or how do I get back to the factory partition of
windows xp that is located on my hard drive?
 
If I were using Vista, I'd fix that driver with F8 options startup repair
which is one of the clear indications for using them:

Try F8 Win Adv Options & Win RE:

Do this:

I always try to F8 to the Windows Adv Options Menu>try 3 safe modes there (I
don't use WGA) and Last Known Good>then I go to Win RE in Vista. That gives
you a choice of Safe Mode, Safe Mode with Networking,and Safe Mode with
Command Prompt.

You will need this reference:

How to start the System Restore tool at a command prompt in Windows XP
http://support.microsoft.com/kb/304449/en-us

The command to use for system restore at the safe mode cmd prompt is:

%systemroot%\system32\restore\rstrui.exe

The reason for doing this is one of these choices may work, when the other
doesn't. My experience is that people do not fully try F8 when they think
or have said they have. It is that they can almost always reach Windows
Advanced Options though.

I would note an important problem seems to be emerging in Vista as more and
more people try Win RE. It does not seem to have the success rate that a
Repair Install from genuine MSFT Media does in XP, and as builds of Vista
march onto RTM, Desmond Lee (Product Manager for Win RE's) team seems to be
unable to fix this. I am not sure Mr. Sinofsky knows what this is or is
that curious to learn. I am sure Mr. Allchin does.

What It Can Do:

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.

How to Use Startup Repair:

***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."***

Screenshot: System Recovery Options (Lower Left Link)
http://blogs.itecn.net/photos/liuhui/images/2014/500x375.aspx

Screenshot: (Click first option "Startup Repair"
http://www.leedesmond.com/images/img_vista02ctp-installSysRecOpt2.bmp

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

Good luck,

CH
 
To get the hdw specs if you don't know them, Use

www.belarc.com/downloads and run the little app from the icon on the desktop
or type msinfo32 in the run box, or the last free Everyst Home edition
http://www.majorgeeks.com/download4181.html

You should learn them, and what they mean but to run the fixes I posted
above you don't have to know them.

As to removing or replacing the driver, it would be good to know that in
fact the driver is the cause of said blue screen. The Driver Verifier tool
was introduced by MSFT with Windows 2000. What is often overlooked and in
particular by MSFT and all of its MSKBs, although they are getting the
opportunity to learn how it can be modified to prevent a large number of
them, inspection of the antivirus program's software drivers by Driver
Verifier and *Deadlock detection can be the cause of blues screen stop
errors that crescendo in frequency that are not always remedied by a repair
install or a clean install on a particular box.

You could have someone debug. If you put driverquery in run, you are going
to see about 230-250 kernel stack drivers and 30-50 non-kernel stack drivers
quickly list.

The Video driver can be checked in safe mode --and MSFT has an MSKB on how
this is done at http://support.microsoft.com

There are articles on how to use Driver Verifier at
http://support.microsoft.com and a White Paper and ancillary information on
Vista's Driver Verifier are at

http://www.microsoft.com/whdc/DevTools/tools/vistaverifier.mspx

http://www.microsoft.com/whdc/devtools/tools/sdv-case.mspx

download.microsoft.com/download/5/b/9/5b97017b-e28a-4bae-ba48-174cf47d23cd/DEV041_WH06.ppt

news.zdnet.com/2100-3513_22-6077604.html

I have posted a long list of references to Driver Verifier a few times on
this group, and the setup and they can be searched.

CH
 
Back
Top