BSOD randomly after upgrade of drives

I have a machine that I upgraded the drives. Originally the boot.ini had this:
multi(0)disk(0)rdisk(0)partition(1) - for Windows was on the first disk on the first partition.

In the process of upgrading the drives, Windows made the second drive Disk (0) and now Windows is on Disk (1). When first edited the boot.ini to:
multi(0)disk(1)rdisk(0)partition(1) - but Windows failed to load. Yet if I left the original Windows would load, even though in Disk Management the OS drive is listed as Disk (1).

Now I seem to have a problem where data that is moved off of the drives, either through the network or to a tape drive connected via another SCSI adapter, causes a BSOD. Yet moving data from drive to drive on the same adapter has caused so far no issues.

Shouldn't the boot.ini say Disk (1) if Windows labels this drive as Disk (1)?

The BSOD that I get is in reference to the drive controller driver. I am wondering if Windows is confused, as I am, about the boot.ini, and is not properly loading the driver.