How to interrupt driver installation

eugeneg

How may I either identify & prevent a device driver from loading, or force a
new driver to take precedence ?

I am trying to fix a PC that had a replacement mobo fitted (by me). I boot
into Vista and it part loads numerous drivers before settling down and
letting me do whatever I want, although the driver installation does request
a restart to complete some driver installs. But if I restart the PC I get a
BSOD with stop code 7b. I am then not able to start even in safe mode. I
tried a repair install but am back to the same situation. Fortunately, I
took an image of the disk before I did anything so I can get back to being
able to boot once.

I understand that 7b indicates an inaccessible boot device, but I have run a
manufacturer's diagnostic, CHKDSK and virus scan and not found any fault.
Vista's automated repair is not able to help (beyond telling me that a
driver is bad). If I could identify which driver is causing problems I could
just disable it from starting by loading the system hive from
C:\Windows\System32\Config\System and (please correct me if I'm wrong)
changing ControlSet001\Services\????\Start to 4 I guess it is the chipset
for the IDE controllers on the motherboard that is different from the one
that the Windows version was originally installed on, but how to identify
which driver to disable ?

I saved a log file of an abortive start by booting off the installation DVD
then from recovery command prompt editing C:\Windows\INF\setupapi.app.log
and I will attach that file here. It contains several failures, but how do I
identify the particular driver that is causing my BSOD ?

The only hardware in the PC is:
mobo: Asus M2N-SLI Deluxe (that replaced an Asus M2N DH)
CPU: AMD Athlon 64 X2 Dual Core Processor 6000+
RAM: 4GB Ballistix Tracer (separately tested to be good)
Video: NVIDIA GeForce 8600 GT
HDD: WDC WD360ADFD
PSU, optical & floppy

Thanks

Mark L. Ferguson

You need to run a repair setup of the Vista install. If Windows is starting,
just put in the setup CD and run setup. It will offer the repair.

--
click the Ratings button. Voting helps the web interface.
see ''rate a post''
Mark L. Ferguson

"eugeneg" <> wrote in message
news:...
> How may I either identify & prevent a device driver from loading, or force
> a
> new driver to take precedence ?
>
> I am trying to fix a PC that had a replacement mobo fitted (by me). I boot
> into Vista and it part loads numerous drivers before settling down and
> letting me do whatever I want, although the driver installation does
> request
> a restart to complete some driver installs. But if I restart the PC I get
> a
> BSOD with stop code 7b. I am then not able to start even in safe mode. I
> tried a repair install but am back to the same situation. Fortunately, I
> took an image of the disk before I did anything so I can get back to being
> able to boot once.
>
> I understand that 7b indicates an inaccessible boot device, but I have run
> a
> manufacturer's diagnostic, CHKDSK and virus scan and not found any fault.
> Vista's automated repair is not able to help (beyond telling me that a
> driver is bad). If I could identify which driver is causing problems I
> could
> just disable it from starting by loading the system hive from
> C:\Windows\System32\Config\System and (please correct me if I'm wrong)
> changing ControlSet001\Services\????\Start to 4 I guess it is the chipset
> for the IDE controllers on the motherboard that is different from the one
> that the Windows version was originally installed on, but how to identify
> which driver to disable ?
>
> I saved a log file of an abortive start by booting off the installation
> DVD
> then from recovery command prompt editing C:\Windows\INF\setupapi.app.log
> and I will attach that file here. It contains several failures, but how do
> I
> identify the particular driver that is causing my BSOD ?
>
> The only hardware in the PC is:
> mobo: Asus M2N-SLI Deluxe (that replaced an Asus M2N DH)
> CPU: AMD Athlon 64 X2 Dual Core Processor 6000+
> RAM: 4GB Ballistix Tracer (separately tested to be good)
> Video: NVIDIA GeForce 8600 GT
> HDD: WDC WD360ADFD
> PSU, optical & floppy
>
> Thanks

eugeneg

Perhaps you missed some of the question:
"Vista's automated repair is not able to help (beyond telling me that a
driver is bad)."

"Mark L. Ferguson" wrote:
> You need to run a repair setup of the Vista install. If Windows is starting,
> just put in the setup CD and run setup. It will offer the repair.

Darrell Gorter[MSFT]

Hello,
Start from the bottom of the setupapi.log file and look for mass storage
controllers that are installed and go up in that log file.
Each of the drivers that is installed should be listed in that file,
Seeing which ones are newly installed should point to one causing the stop
error.
Thanks,
Darrell Gorter[MSFT]

This posting is provided "AS IS" with no warranties, and confers no rights
--------------------
| >Thread-Topic: How to interrupt driver installation
| >thread-index: AcjAvN9z6byCV0KgS4eppQaW3eBi+w==
| >X-WBNR-Posting-Host: 87.114.17.242
| >From: =?Utf-8?B?ZXVnZW5lZw==?= <>
| >References: <>
<>
| >Subject: Re: How to interrupt driver installation
| >Date: Wed, 28 May 2008 05:18:01 -0700
| >Lines: 8
| >Message-ID: <>
| >MIME-Version: 1.0
| >Content-Type: text/plain;
| > charset="Utf-8"
| >Content-Transfer-Encoding: 7bit
| >X-Newsreader: Microsoft CDO for Windows 2000
| >Content-Class: urn:content-classes:message
| >Importance: normal
| >Priority: normal
| >X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2992
| >Newsgroups: microsoft.public.windows.vista.general
| >Path: TK2MSFTNGHUB02.phx.gbl
| >Xref: TK2MSFTNGHUB02.phx.gbl
microsoft.public.windows.vista.general:309822
| >NNTP-Posting-Host: tk2msftibfm01.phx.gbl 10.40.244.149
| >X-Tomcat-NG: microsoft.public.windows.vista.general
| >
| >Perhaps you missed some of the question:
| >"Vista's automated repair is not able to help (beyond telling me that a
| >driver is bad)."
| >
| >"Mark L. Ferguson" wrote:
| >> You need to run a repair setup of the Vista install. If Windows is
starting,
| >> just put in the setup CD and run setup. It will offer the repair.
| >
| >