Discussion Locked

New install of NT 4 crashes after SP &gt

0 helpful
12 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

We have a dual processor system that we are converting to an NT 4 server for an SQL 7 server.

the server contains an Intell 440-BX2 MB with on Board SCSI controller used for TAPE & CD. We also have installed an Adaptec Array 1000 PCI SCSI Raid controller for the Drive array.

The system works fine after initial install of OS. When we apply a SP greater than SP 1 the system locks up upon reboot (during the Blue Boot Screen). We originally installed OS & then SP6a from CD media. Was working until reboot above. Re-did install and ghosted OS partition to 2nd partition for archival purposes during this "debug" process (faster than re-install of base OS). When then worked back from SP6a excludin SP6 (i.e. 5,4,3, 1). I have checked the files installed on the system after SP install but before reboot, and none of the SCSI drivers are changed from orig.

Any ideas what could be going wrong ?? Never actually get to a core dumpe, etc. ... just locks up.

Thanks

Robert Rack

12 replies

by spiceman

The blue screen should have a message to tell you what driver or drivers caused the crash.

Without that information my guess is to try a re-install by taking out all devices not required like Scsi cards, network card etc. You need to ensure thatat each stage the re-boot works. Need to install one device and driver at a time and reboot and test again. Eventually you should get the problem driver or device.

good luck

by rack

The only device drivers I have loaded are: the SCSI drivers which I need; the OS is on the Adaptec SCSI Controlled drives. The other SCSI controller is for the CD Rom. Sort of hard to work with access to the drives.

The only thing I could remove at this point is the Network card.

by zs6dgb

Although the driver files may not have changed,check what devices are set to bbot or system.
The blue screen should show whether it can't find the ntoskrnl check disk administrator, letit write a signature, and run rdisk before re-start.
Also, older IE and IIS doesn't work well with SQL7(wrong DLL's). Remove IIS 2, which up-dates to ver 3 after SP. And update to IE ver5 or > .
Blue screen should show at which point in the boot sequence an error has occured.
The specific error should help you locate the exct problem.
An error in Control panel

by rack

I never quite get an error message, just the AutoCheck. See comment above for the latest info.

by zs6dgb

Although the driver files may not have changed,check what devices are set to bbot or system.
The blue screen should show whether it can't find the ntoskrnl check disk administrator, letit write a signature, and run rdisk before re-start.
Also, older IE and IIS doesn't work well with SQL7(wrong DLL's). Remove IIS 2, which up-dates to ver 3 after SP. And update to IE ver5 or > .
Blue screen should show at which point in the boot sequence an error has occured.
The specific error should help you locate the exct problem.
An error in Control panel

by rack

We are currently re-loading the OS from scratch, as our D: drive partition where we stored our Ghost image of the OS partition has somehow or other been corrupted.

Thanks

by rack

This morning I was able to reboot the system and select VGA Mode (safe mode) on boot up - I missed this chance before I left the office on Friday.

The system gets to the Blue Boot screen and starts to do an Autocheck of the drive but aborts because we have the boot Drive as FAT 16 yet for diagnostic purposes. It then tries to scan H: drive. The problem ... we don't have an H: drive yet. The following are the drives in the System:

A: Floppy
B: None.
C: NT OS Drive (Fat 16)
D: extra partition for Ghost Image storage (Fat16)
E: SCSI CD Rom Drive

Any ideas where it might be getting this H: Drive from ??

as for the other SW you mentioned ... IIS, IE 5.0, etc. I can't even boot the system that far.

Thanks

by lbischofs

Here's something that might at least help you capture the Blue screen info.
http://www.sysinternals.com/bluesave.htm
**During the Service Pack install are you possibly bypassing any interactive popups that ask if you want to skip or overwrite any files?
As for the H: drive the only thing that jumps to mind is the Home directory setting in User Manager/Profile section.

by mayon

You could have installed a SCSI driver from your SP6 that is not compatible with your
current configuration. Try using a SCSI
driver from SP1 (replacing only that particular file)and restart the system.
I think a .sys file in \system32 dir.
I have a similar situation using Symbios driver and worked.

Good Luck!

by rack

Actually it was a combination of the SCSI driver supplied by MS in the SP not being compatible with the onboard SCSI - who'd a thought ... and the onboard SCSI bios needing to be updated, along with the BIOS needing to be updated. God forbid theSP tell you this before you install it.

This discussion is closed to new replies.