PROB | Drivers from CD: Simple Method: BSOD

[Unlock]

My problem:

1)Start installation windows

2)start driver.cmd and I see all operation after, pc restart and blue screen

WHY?

I've many drivers for more pc in drivers directory...Is the problem it?

Edited March 18, 2006 by Bâshrat the Sneaky

[Unlock]

31 guys have read and nobody responds.....MMMMMMMMM

[Guest]

Need more info. Can you post the contents of your driver.cmd and some system specs?

Have you narrowed down which driver(s) may be causing the problem?

[Unlock]

driver.cmd

@ECHO OFF

TITLE Drivers-from-CD Installation

color 1F

:: Set Current Drive as CD

CD /D "%~dp0"

:: Set Drivers Location Folder

SET DRV=Drivers

:: Ticker script

ECHO.exec hide %CD%\Process.exe -r setup.exe >%SystemDrive%\Ticker.ncl

ECHO.wait 10000 >>%SystemDrive%\Ticker.ncl

ECHO.exec hide %CD%\Process.exe -p SetupCopyOEMInf.exe high >>%SystemDrive%\Ticker.ncl

ECHO.exec hide %CD%\Process.exe -s setup.exe >>%SystemDrive%\Ticker.ncl

ECHO.wait 50000 >>%SystemDrive%\Ticker.ncl

ECHO.script %SystemDrive%\Ticker.ncl >>%SystemDrive%\Ticker.ncl

:: Pre-Install (Suspend Setup, and Set Setup to Low Priority)

.\Process.exe -s setup.exe

.\Process.exe -p setup.exe low

:: Allow for Unsigned Drivers

START .\WatchDriverSigningPolicy.exe

:: If Compressed Drivers Exist, Unzip Them & Change Drivers Location Folder to Hard Drive

IF EXIST Drivers.7z (

SET DRV=%SystemDrive%\Drivers

.\7za.exe x -y -aoa -o"%SystemDrive%\Drivers" ".\Drivers.7z"

)

:: Run NirCmd Ticker Script (code above)

START .\NirCmd.exe script %SystemDrive%\Ticker.ncl

:: Install Drivers

.\SetupCopyOEMInf.exe "%DRV%"

:: Post-Install (Close NirCmd, Setup Priority back to Normal, Resume Setup)

.\Process.exe -k NirCmd.exe

.\Process.exe -p setup.exe normal

.\Process.exe -r setup.exe

:: Delete Ticker File

DEL %SystemDrive%\Ticker.ncl

EXIT

I dont kwon wich driver create the problem, because i see blue screen but pc restart immediately.

My folder of drivers is 900mb I've a lot of driver for many device

[Sonic]

I think it's driver issue, try to not install audio driver.

[Unlock]

Ok I try.

I think, when driver.cmd search in all folder , windows it would not have to use those not correct or I think wrong

[Unlock]

this is driver that generate error protcls.sys, when windows is installing the peripheral ones

[Sonic]

I suppose you have HD audio sound card, you will need update for windows to update/support HD audio, but I'm not certain, search on forum with this file, you find the solution ...

Goodbye.

[Joc]

Well, I use this simple method too. I have only 4 drivers to install, and I started to select the buggy driver. And finally, found it. On my system I got the BSoD when the Forceware 8x.xx installed! Without it everything worked perfectly.

Try something: after BsoD start the Windows in safe mode, install the forceware and restart. Everything will OK.

There was a problem with nvidia mass storage driver too in text mode if I remember well.

Ideas?

(sorry about my english, I am a beginner and I write from my pda)

Joc

[Joc]

Solved the BSoD 0x7e: everything is working correctly with Forceware 77.72!

Joc

[Crusty01]

Unlock, your first post gives WAY too little information for anyone to even bother answering your question.

Standard details are your OS with service packs and hotfixes added, hardware of the pc that gives the problem, methods used for unattended install, and in this case the exact blue screen message. The details needed vary from issue to issue.

Better to give too many than too few details.

From now on, do this for EVERY question.

[Unlock]

Unlock, your first post gives WAY too little information for anyone to even bother answering your question.

Standard details are your OS with service packs and hotfixes added, hardware of the pc that gives the problem, methods used for unattended install, and in this case the exact blue screen message. The details needed vary from issue to issue.

Better to give too many than too few details.

From now on, do this for EVERY question.

ok

1) xp pro sp2

2) hot not install

3) pc asus barebone or others

4) methods used for unattended.....2

4) driver that generate error protcls.sys