[ecpd01]

Machine starts to boot to UBCD4WIN CD, loads Windows, gets just past shell selection, then BSOD indicating issue with iastor55_SY. 3 burn attempts, same result. Followed posted instructions and searched forum for insight. Hard Drive is SATA RAID0 Array. Do I need to press F6 when prompted and feed RAID drivers? Thx for any help

[cdob]

ecpd01, on Apr 24 2009, 09:53 PM, said:

Hard Drive is SATA RAID0 Array.

Which hardware do you use?

Which raid controller do you use?

Which HardwareID goes to this controller?

Run

devcon hwids *cc_01* *scsi* *raid*

Post the result.
http://support.micro....com/kb/311272/

[ecpd01]

Asus P5N-E SLI MB. Onboard nForce RAID and SATA Controllers. Devcon output:

ACPI\NVRAIDBUS\3&2411E6FE&0
Name: NVIDIA nForce" RAID Class Controller
Hardware ID's:
ACPI\NVRAIDBUS
*NVRAIDBUS
IDE\DISKWDC_WD1500ADFD-00NLR5___________________21.07QR5\R2020202057202D444D5750413134323930343137
Name: WDC WD1500ADFD-00NLR5
Hardware ID's:
IDE\DiskWDC_WD1500ADFD-00NLR5___________________21.07QR5
IDE\WDC_WD1500ADFD-00NLR5___________________21.07QR5
IDE\DiskWDC_WD1500ADFD-00NLR5___________________
WDC_WD1500ADFD-00NLR5___________________21.07QR5
GenNvRaidDisk
Compatible ID's:
GenNvRaidDisk
IDE\DISKWDC_WD1500ADFD-00NLR5___________________21.07QR5\R2020202057202D444D5750413134323938353537
Name: WDC WD1500ADFD-00NLR5
Hardware ID's:
IDE\DiskWDC_WD1500ADFD-00NLR5___________________21.07QR5
IDE\WDC_WD1500ADFD-00NLR5___________________21.07QR5
IDE\DiskWDC_WD1500ADFD-00NLR5___________________
WDC_WD1500ADFD-00NLR5___________________21.07QR5
GenNvRaidDisk
Compatible ID's:
GenNvRaidDisk
PCI\VEN_10DE&DEV_0265&SUBSYS_81BC1043&REV_A1\3&2411E6FE&0&68
Name: Standard Dual Channel PCI IDE Controller
Hardware ID's:
PCI\VEN_10DE&DEV_0265&SUBSYS_81BC1043&REV_A1
PCI\VEN_10DE&DEV_0265&SUBSYS_81BC1043
PCI\VEN_10DE&DEV_0265&CC_01018A
PCI\VEN_10DE&DEV_0265&CC_0101
Compatible ID's:
PCI\VEN_10DE&DEV_0265&REV_A1
PCI\VEN_10DE&DEV_0265
PCI\VEN_10DE&CC_01018A
PCI\VEN_10DE&CC_0101
PCI\VEN_10DE
PCI\CC_01018A
PCI\CC_0101
PCI\VEN_10DE&DEV_0266&SUBSYS_81BC1043&REV_A1\3&2411E6FE&0&70
Name: NVIDIA nForce 430/410 Serial ATA Controller
Hardware ID's:
PCI\VEN_10DE&DEV_0266&SUBSYS_81BC1043&REV_A1
PCI\VEN_10DE&DEV_0266&SUBSYS_81BC1043
PCI\VEN_10DE&DEV_0266&CC_010485
PCI\VEN_10DE&DEV_0266&CC_0104
Compatible ID's:
PCI\VEN_10DE&DEV_0266&REV_A1
PCI\VEN_10DE&DEV_0266
PCI\VEN_10DE&CC_010485
PCI\VEN_10DE&CC_0104
PCI\VEN_10DE
PCI\CC_010485
PCI\CC_0104
SCSI\DISK____NVIDIA__STRIPE___279.47G\1
Name: NVIDIA STRIPE 279.47G
Hardware ID's:
SCSI\Disk____NVIDIA__STRIPE___279.47G
GenDisk
Compatible ID's:
SCSI\Disk
SCSI\RAW

[cdob]

That's strange behaviour.
Which BSOD do you get?
Which windows source files do you use?

There are already drivers included for a PCI\VEN_10DE&DEV_0266 and *NVRAIDBUS.

Try edit \plugin\DriverPacks.net\MassStorage\MassStorage.inf, comment line

;"txtsetup.sif","SCSI.Load","iastor55", "iastor55.SY_,4"

[RedDelPaPa]

cdob, on 26 April 2009 - 02:24 AM, said:

That's strange behaviour.
Which BSOD do you get?
Which windows source files do you use?

There are already drivers included for a PCI\VEN_10DE&DEV_0266 and *NVRAIDBUS.

Try edit \plugin\DriverPacks.net\MassStorage\MassStorage.inf, comment line

;"txtsetup.sif","SCSI.Load","iastor55", "iastor55.SY_,4"

That doesn't resolve the problem though. All that does it make the CD boot the machine with no disk access. Has anyone solved this problem by getting iastor55 to load without a BSOD?

I'm seeing the exact same problem on a ASUS P4C800-E Deluxe with the ICH5R.

Thanks,
N8

[rdsok]

It is not the same problem... Intel and nForce drivers are made by different companies.


UBCD4Win, arguably,has the most complete set of drivers included with it to help in this type of situation. They were developed by the Driverpacks.net development team which represents the most complete set of drivers available anywhere... but still it is limited to what has already been or can be included so it can't have every single driver since new ones are developed all of the time.

So in situations like this the user needs to add the proper drivers for their system and disable the included drivers so no conflicts will mess you up and overwrite the drivers you supply. We also strongly recommend that the user report the issue in the Driverpacks.net forum so that other users will not have to worry about it later as they develop new driverpacks.

First you must locate the proper drivers for your system or its motherboard. Go to the manufacturers or motherboard's website and download the XP ( or Win2k3 drivers if that is the source files you are building from ) Floppy/F6 drivers. These are the same drivers that a user would use when installing XP ( or Win2k3 ) so should be easy to locate.

Next you need to create a folder for them. In the [UBCD4Win]\drivers folder create a folder named SCSIAdapter and in that folder another for your drivers called MyDriver... the path should be [UBCD4Win]\drivers\SCSIAdapter\MyDriver. Then extract the drivers you downloaded into that folder.

Next in the UBCD4WinBuilder go into the Plugins area and disable the "# DriverPacks.net - MassStorage" plugin so you don't get a conflict with these drivers. Rebuild the project and create a new disk and test.

[RedDelPaPa]

rdsok, on 20 September 2009 - 02:46 PM, said:

It is not the same problem... Intel and nForce drivers are made by different companies.


UBCD4Win, arguably,has the most complete set of drivers included with it to help in this type of situation. They were developed by the Driverpacks.net development team which represents the most complete set of drivers available anywhere... but still it is limited to what has already been or can be included so it can't have every single driver since new ones are developed all of the time.

So in situations like this the user needs to add the proper drivers for their system and disable the included drivers so no conflicts will mess you up and overwrite the drivers you supply. We also strongly recommend that the user report the issue in the Driverpacks.net forum so that other users will not have to worry about it later as they develop new driverpacks.

First you must locate the proper drivers for your system or its motherboard. Go to the manufacturers or motherboard's website and download the XP ( or Win2k3 drivers if that is the source files you are building from ) Floppy/F6 drivers. These are the same drivers that a user would use when installing XP ( or Win2k3 ) so should be easy to locate.

Next you need to create a folder for them. In the [UBCD4Win]\drivers folder create a folder named SCSIAdapter and in that folder another for your drivers called MyDriver... the path should be [UBCD4Win]\drivers\SCSIAdapter\MyDriver. Then extract the drivers you downloaded into that folder.

Next in the UBCD4WinBuilder go into the Plugins area and disable the "# DriverPacks.net - MassStorage" plugin so you don't get a conflict with these drivers. Rebuild the project and create a new disk and test.

You must not have understood my post. I am experiencing the exact same symptom(instead of problem) as the original poster.

"Machine starts to boot to UBCD4WIN CD, loads Windows, gets just past shell selection, then BSOD indicating issue with iastor55_SY. 3 burn attempts, same result"

I've built a disk with the mass storage drivers disabled and it boots. But it's useless for anything other than testing purposes. No disk access because the ICH5R drivers are absent. I'm new to this, but I think it may be a conflict, or driver load order issue. Your thoughts?

Thanks,
N8

[rdsok]

My thoughts are the same... follow my instructions to add the drivers for your system as stated