Ultimate Boot CD for Windows delivers BSOD (Page 1 of 2)

Might want to post the exact BSOD error code too.  Could be something unrelated to the NTLDR memory issue.

I recently upgraded to UBCD4WIN 3.13, and built it with Windows XP Professional Service Pack 3. The error is still there, and the text on the BSOD, gives the following information:

A problem has been detected and Windows has been shut down to prevent damage to your computer.

The problem seems to be caused by the following file: 3ware9k.SY_

The driver mistakenly marked a part of it's image pagable instead of nonpagable.

Then after the standard directions:

Technical Information:

*** STOP: 0x000000D3 (0xF693CEC0,0x00000002,0x00000001,0x8040F37F)

3ware9k.SY_

sound good but tellme how do youc ompress a file ? I use expand to decompress, for compressing i have no clue. I've searched for un-expand tool and no luck.

Read BEFORE you post  HWID's Tool  DriverPacks tutorial  DriverForge & FindHWIDs



Donate!

I see..
DriverPack MassStorage 7092 used 3ware9k tagname
DriverPack MassStorage 711 uses a new tagname (it updated to the 2006 version then)
and dpm805xx will have to use a the 2008 version of this driver.

(funny how some drivers behave when they get renamed by a tag.. but, since we have not used 3ware9k tag since november 2007 I get this feeling this happened after restreaming the plugin.)

the 2008 version presents me with a problem.. it has two INF files now..

Last edited by Jaak (2008-05-20 12:50:35)

I use makecab, included with Windows XP. It can be used for single files too.

Just replacing the .sys file in the pack is not ok? It works for me...
For as far is I know the entire 9xxx series use the same driver.

JakeLD?
can you update the 3ware for us and create a testpack?

I would also like to get the VIA hyperion driver removed or zeroed.
(I'll explain the reason, when I araxis'd a  clean SP2 and SP3 it looked like that SP3 has updated or added the hyperion.)

The txtmode driver for hyperion was added to DriverPack MassStorage not too long ago.
(the 571 issues could  magically dissolve. SP2 may benefit((what was natively supported in SP2 by its via driver?? I dunno), but it sure looks like SP3 will have real issue in Via if we leave all via in the DriverPack MassStorage.)

I figure we'll find out what HWIDS in VIA SP3 natively supports, compare that to what HWIDS SP2 natively supports, then do some magic.
JakeLD is very good at this, and we have a large reporter group when things are WRONG.

Please folks, we do need pre-release testers..
We know we have many lurkers, we know we have a good many users doing massive rollouts and quite a few more serious pop & mom stores and repair IT folks.
Jeff thinks we see less than 1 percent of our DriverPacks users submit a post.

I think less than 35 percent of the posts are helping us in the first post, and the people who really want to help you want you to help us by submitting more data and logs.

No he really was ON target overall...
we do need people to post win or loose so we can make DriverPacks rock solid.
without people who post thier hwids we don't have them
(you have to possess the hardware to get the hwids)
We live or die by knowing what devices report what specific HWID's

Thanks for posting yours!

Have you tried just useing the current pack - instead of the one that came with your build?
I belive the included pack is from last year...

DP BartPE Tutorial   DP_BASE Tutorial   HWID's Tool     Read BEFORE you post    UserBars!

The DriverPacks, the DP_Base program, and Support Forum are FREE!.

About the VIA thing.
XP SP2 has VIAIDE which supports 571 and no other
XP SP3 has VIAIDE which supports 571 and no other (the driver also showed same when I did a binary compare..)
windows 2003 has support for 571
windows 2000 does not have support for 571

The hyperion (VIBUS) we load has support for 571 and ANOTHER.
What triggered my attention to this is basically this.
DriverPacks BASE 7052 loaded this later on.
DriverPacks BASE 805 has changed something in load order.
The busdrivers now show before scsi?

and 3waredrv loaded after ali and Qware and adaptec.. ??
It is first in INI, it should have loaded first.

Ok, if you say so, I am lucky. Strange that your test with the new driver does not work. I do not have enough understanding of hardware-id's to see why I am lucky though.

I do not know how to put another pack in to the UBCD4WIN, but my workaround (replacing the .sys file) is easy and works for me.

I remember causing a false corrupt driver message when I tried to load it from floppy long ago during Windows XP setup wit $OEM$ preinstall, luckily nLite warns for this issue now.

Also, are you sure you did not use a 32-bit driver in a 64-bit environment?

Sorry if I sound stupid, but I don't understand why I am lucky that the .sys file replacing works. I have noticed the driver archive contains two INF files, but I also know nLite can slipstream it into my XP Setup CD without problems.

2006 had fourth line as this
PCI\VEN_13C1&DEV_1004&SUBSYS_100513C1

2008 has fourth line as this
PCI\VEN_13C1&DEV_1005&SUBSYS_100513C1

I will try this again, with this

[3]
ms_count=1
ms_1_deviceName="3ware AMMC 9000/9500 Series SATA RAID Controller"
ms_1_tag="3wareDrv"
ms_1_sysFile="3wareDrv.SYS"
ms_1_hwids="PCI\VEN_13C1&DEV_1002&SUBSYS_100213C1,PCI\VEN_13C1&DEV_1003&SUBSYS_100313C1,PCI\VEN_13C1&DEV_1004&SUBSYS_100413C1,PCI\VEN_13C1&DEV_1005&SUBSYS_100513C1,SCSI\Processor__AMCC__SATA_RAID_9500S_,SCSI\Processor__AMCC__SATA_RAID_9550SX,SCSI\Processor__AMCC__SATA_RAID_9650SE,SCSI\Processor__AMCC___SAS_RAID_9690SA"
ms_1_isBusExtender=false

I just noticed that the HWID posted was the fourth?
And PE does not care for that?
The CAT for the 2008 version has DEV_1005&SUBSYS_100513C1 inside, so that new INF file is not wrong..
I've added the SCSI lines to the INI hoping that will work.

Last edited by Jaak (2008-05-27 18:10:44)