[SLV] BSOD on AMD PCI\VEN_1022&DEV_7409&CC_0101

Answers to above questions:

did you use nlite or somthing to remove drivers from your source?

Answer --  No nlite or somthing, no did not remove drivers from source XP service pack 3 slip-streamed.  UBCD4win v3.50 straight from the download. If I remove the MassStorage plugin no problems, If I use the mass-storage plugin (MassStorage, 8.05) from UBCD4Win v3.22  NO problems, boots fine. If I use the current DriverPacks BASE v8.12.4 with v9.01 - DriverPack MassStorage on UBCD4Win v3.22 the STOP error DOES occur.

If you need more or I missed something you'd like to know I try to post tomorrow morning.

That is perfect... good details and trouble shooting...

Well done! we will address this issue soon!

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!.

Thanks! for the plugin fix back at ubcd4win.com forum.

http://ubcd4win.com/forum/index.php?sho … entry73451

Yes it is a slot A motherboard and some years old.

I work with quite a lot of very old slot A motherboards and most are fine, but this one is a little confusing, as mentioned above.

I have worked with another slot A board with some unusual problems which would only boot XP with a small customized CD bootable that then loaded XP. Win ME on this same machine needed a similar start-up disk on Floppy. That machine has now been running this way stably for over two years.

Point is that some of these types of hardware faults (broken hardware) and hardware deficiencies,  once remedied in software are quite stable and keep these machine in use and out of the landfill.

I can do some more tests with different approaches on this motherboard (SpaceWalker-Shuttle-AI61) once I have physical access to it again, probably in about two weeks +-, ... if anyone desires more information on this matter. Just let me know and tell me what types of testing you'd like.

Last edited by cfp (2009-05-23 09:08:11)

I don't hardware to test.
Contrary I doubt mentioned HardwareID works that way.
Remove all HardwareIDs from amdbusdr.sys.

No, the correct file is referenced.
However there is a missing second one: AmdEide.sys.
And there are missing two addional HardwareIDs: AMD_Primary_IDE_Channel and AMD_Secondary_IDE_Channel

Idea, not tested

[AM]
ms_count=2
ms_1_deviceName="AMD PCI Bus Master IDE"
ms_1_tag="amdide"
ms_1_sysFile="amdbusdr.sys"
ms_1_hwids="PCI\VEN_1022&DEV_7409,PCI\VEN_1022&DEV_7411,PCI\VEN_1022&DEV_7441,PCI\VEN_1022&DEV_7469"
ms_1_isBusExtender=true
ms_1_exc_replaceifOS="w2k3"
ms_2_deviceName="AMD IDE Channel"
ms_2_tag="AmdEide"
ms_2_sysFile="AmdEide.sys"
ms_2_hwids="AMD_Primary_IDE_Channel, AMD_Secondary_IDE_Channel"
ms_2_isBusExtender=false

And I've no idea,

Problem SOLVED!

Here is edited mass storage INI file [AM] and [AM1] sections:

cdob, your idea worked! I made a couple of changes just so things were easier to follow.

1) Changed   [AM]   ms_1_tag="amdide"   to   ms_1_tag="amdbusdr"
     so that the \i386\  file amdbusdr.sys is not renamed to amdide.sys

2) Changed   [AM1]   ms_1_tag="amdide1"   to   ms_1_sysFile="amdide.sys"   
     so that  the \i386\  file amdide.sys is not renamed to amdide1.sys

Although everything works fine with the files renamed, it was less confusing  if files kept the same names as that in the original driver's directory in \D\M\AM\  and \D\M\AM1\ that ended up in \i386\ and to see things in txtsetup.sif.

3) Removed a space int the line:
    ms_2_hwids="AMD_Primary_IDE_Channel, AMD_Secondary_IDE_Channel"
    ms_2_hwids="AMD_Primary_IDE_Channel,AMD_Secondary_IDE_Channel"

The new DriverPack_MassStorage_wnt5_x86-32.ini file was put in the DP_MassStorage_wnt5_x86-32_901.7z file and BASE v8.12.4 was used.

No STOP errors with UBCD4win v3.50, v3.22 or with XP service pack 3 slip-streamed.  In UBCD4win Device Manager everything looked good with IDE controller and the two IDE channels.

Here is link to new DriverPack_MassStorage_wnt5_x86-32.ini  and  DP_MassStorage_wnt5_x86-32_901.7z

http://computerfixpro.com/DP_MassStorag … 901.7z.zip

Last edited by cfp (2009-05-25 15:37:23)

excellent... well done everyone

there is another mistake not mentioned... AM1 is NOT a bus extender. ***(correction below, AM1 IS a bus extender)***

so applying what we know...

[AM]
ms_count=2
ms_1_deviceName="AMD PCI Bus Master IDE"
ms_1_tag="amdide"
ms_1_sysFile="amdbusdr.sys"
ms_1_hwids="PCI\VEN_1022&DEV_7409,PCI\VEN_1022&DEV_7411,PCI\VEN_1022&DEV_7441,PCI\VEN_1022&DEV_7469"
ms_1_isBusExtender=true
ms_1_exc_replaceifOS="w2k3"
ms_2_deviceName="AMD IDE Channel"
ms_2_tag="AmdEide"
ms_2_sysFile="AmdEide.sys"
ms_2_hwids="AMD_Primary_IDE_Channel,AMD_Secondary_IDE_Channel"
ms_2_isBusExtender=false

[AM1]
ms_count=1  
ms_1_deviceName="AMD PCI SATA/IDE"   
ms_1_tag="amdide1"   
ms_1_sysFile="amdide.sys"   
ms_1_hwids="PCI\VEN_1002&DEV_4390,PCI\VEN_1002&DEV_439C,PCI\VEN_1002&DEV_438C,PCI\VEN_1002&DEV_4376"
ms_1_isBusExtender=true

If you were really, really motivated to help us...
Could you please test this @ BartPE - Win 2K3 source?

edit...

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!.

but I see in  \M\AM1\amdhdc.inf:
-  I couldn't find that line when I read the inf,
    you are correct, and it was correct before, it IS a bus extender.

Windows 2003 uses / includes a driver with the file name amdide.sys...
- so we must 'tag' our driver with the same name, and add the replace tag too... (for 2k3)
if a driver upgrades existing support then the driver must be named (Tag name) the same as the driver it is replacing...

Your code is valid for xp but probably fails at 2k3...
the corrected code above should work for 2K, XP and 2K3...

Code in my last post is now corrected ....

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!.

Test Results:

CODE posted by OverFlow 2009-05-25 11:32:06 (above) integrated

Link to new DriverPack_MassStorage_wnt5_x86-32.ini  and  DP_MassStorage_wnt5_x86-32_901.7z
http://computerfixpro.com/DP_MassStorag … 901.7z.zip

DriverPacks BASE v8.12.4

Hardware: SpaceWalker-Shuttle-AI61-motherboard

Source: W2K3 SP1 R2

UBCD4Win 3.22 -- PASS

UBCD4Win 3.50 -- PASS

DriverPacks into a source for DISC install of W2K3 SP1 R2 -- PASS

________________________________________________________

In all cases the original   amdide.sys 7,680 bytes version 5.2.3790.3959 (srv03_sp2_rtm.070216-1710)
is replaced by                amdide.sys 29,696 bytes version AMD 8.2.8 (original name - amdbusdr.sys)

Confirmed by Device Manager new amdide.sys 29,696 bytes version AMD 8.2.8 is LOADED properly.

AMDEIDE.SYS  -- LOADED

--------------------------------------------------------------

AMDIDE1.SY_   --  correctly exists at %windir%\SYSTEM32\DRIVERS\  (original name - amdide.sys)

.
#############################################

BSOD
STOP: 0X0000007B (0XFA2F3528, 0XC0000034, 0X00000000, 0X00000000)

STILL occurs with W2K3 ONLY IF  original DriverPack_MassStorage_wnt5_x86-32.ini
is used --> UBCD4Win 3.22, UBCD4Win 3.50, and DISC install of W2K3 SP1 R2.

#############################################