Big ERROR after creating RIS Image

[tsystems]

Hi Gyus, Im new here.

Lately, Ive made an RIS image in my company. The company has over 200 PCs, which all are the same:

-Dell Optiplex GX620

-Intel Pentium D

-Foxconn MB i945G

-ATI Radeon x600 dual DVI

-2x512MB DDR2 RAM

-DVDRW Drive

-2x 1707FP Dell 17" LCD monitors

So I made a new WindowsXP SP2 installation, downloaded all hotfixes, installed the new Intel INF chipset driver from intel's homepage, Broadcom Gigabit driver, ATI 6.7 drivers with control center, Office 2003+updates, some VPN clients (cisco and checkpoint), Adobe Reader 7, and some other small company programs. Everything was good and worked properly. Then I turned on the RIS image creator in the windows installation, turned off all local services that were written in the tab and started the image creator. Everything was succesfull after the creating of the image. Than I switched to restart the computer and than it came! BLUE SCREEN with some obligate warnings and codes. The main warning was something like: "Driver LIRQ less or equal.." or something similar...

Do you know whats wrong? Are some orginal drivers from manufacture pages wrong, or not recommended for the RIS?

THANX

[Br4tt3]

Hi!

If the machine was succesfully installed into Win32 (logged on once for example), and it BSOD:ed when performing an additional reboot, my guess is that it was some kind of driver added late in process, like a kernel filter driver or something. Try installing the machine with just the drivers for the HW, if succesfull when fully installed and rebooted, then add something more and so on... then u will know where in the process it messes up.

P.S I am also running Dell GX620's as one of the company's standard models if there is anything that u wanna check out...

Edited August 7, 2006 by Br4tt3

[RogueSpear]

Video adapter drivers are very well known to throw up those IRQ less or equal BSODs.

[cluberti]

Also, the bugcheck or STOP code on the screen will likely tell you the actual image name that caused it, if you don't have the thing set to automatically reboot. That'd take the guesswork out of it...