• Registered: 2006-08-18
  • Posts: 22

Topic: BSOD with SiI 3112 SATAlink controler

Yay, I've got the good ol' SiI 3112 SATAlink controler which seems to be causing a lot of problems for a lot of people.

However, I've only experienced problems just last week, when I tried to make a nice new WinXP cd. I am now presented with a nice BSOD after textmode install, with a nice 0x0000007B stop error. This happens with the last 2 MassStorage packages. I have now installed an older version again, with MS_DP version 7.01.1, which installs just fine. On a sidenote, both images with the latest DP_MS packs work fine on a Virtual Machine and on an actual PC.

BTW, I tried to download the "save_hwids.exe" in Bashrat's sig, but that link is broken. I used DevCon instead, and that generated the following HWID for my Silicon Image controler.

PCI\VEN_1095&DEV_3112&SUBSYS_31121095&REV_02\4&3B1D9AB8&0&4040
    Name: Silicon Image SiI 3112 SATALink Controller
    Hardware ID's:
        PCI\VEN_1095&DEV_3112&SUBSYS_31121095&REV_02
        PCI\VEN_1095&DEV_3112&SUBSYS_31121095
        PCI\VEN_1095&DEV_3112&CC_018000
        PCI\VEN_1095&DEV_3112&CC_0180
    Compatible ID's:
        PCI\VEN_1095&DEV_3112&REV_02
        PCI\VEN_1095&DEV_3112
        PCI\VEN_1095&CC_018000
        PCI\VEN_1095&CC_0180
        PCI\VEN_1095
        PCI\CC_018000
        PCI\CC_0180

I checked both the MassStorage ini-files in my old and my new image, and the only difference in the Silicon Image 3112 SATAlink section is the addition of this puppy in the newest DP_MS driverpack ini-file. The rest is the same.

PCI\VEN_1095&DEV_3512&SUBSYS_000E182D

Also, in the DP_MS Storage pack, at location "\D\M\S\4", there is an extra file in the older file.
DPM7011.7z has a file "SiiSup.vxd" whereas DPM706.7z does not, but since Windows XP doesn't use .vxd's it can hardly be the problem.




I'm not sure if you need any more information, but if you'd like me to try certain things out I'm willing to spend some time into it.

Last edited by Stiertje (2007-06-20 13:36:38)

  • Jaak
  • Old Timer Rookie
  • Offline
  • From: Eeklo, in the East Flanders
  • Registered: 2006-07-23
  • Posts: 3,594

Re: BSOD with SiI 3112 SATAlink controler

do you have 7zip?
HWids tool in one of the packed binaries.

today, while looking for a HWID match (looking for overlap) I spotted (yet another) overlap. (3114R and 3114r5)

we really need a database.

The answer was 42?
Kind regards, Jaak.
  • Registered: 2006-08-18
  • Posts: 22

Re: BSOD with SiI 3112 SATAlink controler

Hmn, can't seem to find that file. I only find "DevCon.exe" which I already used. DevCon does the job, but is a little overabundant in its information.

  • Registered: 2006-08-18
  • Posts: 22

Re: BSOD with SiI 3112 SATAlink controler

Tried again, and I see what the problem is. During textmode it selects the SATARaid version instead of the SATALink one

Darn, stupid Silicon Image, and I just have to have it tongue



Anyway, this is just the first time I've ever had major problems (apart from the JMicron problems) and I've installed many computers with these packs. Keep up the good work, and if you ever find a solution you want tested, I'm willing to try it out for ya.



BTW, download link for the HWID tool works again. Here's my HWID listing

 
=========== 
PCI devices 
=========== 
 
 
PCI\VEN_1002&DEV_5159&SUBSYS_7C02174B&REV_00\4&3B1D9AB8&0&4840: RADEON 7000 SERIES          
PCI\VEN_1095&DEV_3112&SUBSYS_31121095&REV_02\4&3B1D9AB8&0&4040: Silicon Image SiI 3112 SATALink Controller
PCI\VEN_10DE&DEV_0060&SUBSYS_00000000&REV_A4\3&13C0B0C5&0&08: PCI standard ISA bridge
PCI\VEN_10DE&DEV_0064&SUBSYS_0C111043&REV_A2\3&13C0B0C5&0&09: NVIDIA nForce PCI System Management
PCI\VEN_10DE&DEV_0065&SUBSYS_0C111043&REV_A2\3&13C0B0C5&0&48: NVIDIA nForce2 ATA Controller
PCI\VEN_10DE&DEV_0066&SUBSYS_80A71043&REV_A1\3&13C0B0C5&0&20: NVIDIA nForce Networking Controller
PCI\VEN_10DE&DEV_0067&SUBSYS_0C111043&REV_A4\3&13C0B0C5&0&10: Standard OpenHCD USB Host Controller
PCI\VEN_10DE&DEV_0067&SUBSYS_0C111043&REV_A4\3&13C0B0C5&0&11: Standard OpenHCD USB Host Controller
PCI\VEN_10DE&DEV_0068&SUBSYS_0C111043&REV_A4\3&13C0B0C5&0&12: Standard Enhanced PCI to USB Host Controller
PCI\VEN_10DE&DEV_006A&SUBSYS_80951043&REV_A1\3&13C0B0C5&0&30: Realtek AC'97 Audio
PCI\VEN_10DE&DEV_006C&SUBSYS_00000000&REV_A3\3&13C0B0C5&0&40: PCI standard PCI-to-PCI bridge
PCI\VEN_10DE&DEV_01E0&SUBSYS_00000000&REV_C1\3&13C0B0C5&0&00: PCI standard host CPU bridge
PCI\VEN_10DE&DEV_01E8&SUBSYS_00000000&REV_C1\3&13C0B0C5&0&F0: NVIDIA nForce2 AGP Host to PCI Bridge
PCI\VEN_10DE&DEV_01EA&SUBSYS_80AC1043&REV_C1\3&13C0B0C5&0&01: NVIDIA nForce2 400 Memory Controller
PCI\VEN_10DE&DEV_01EC&SUBSYS_80AC1043&REV_C1\3&13C0B0C5&0&04: NVIDIA nForce2 Memory Controller
PCI\VEN_10DE&DEV_01ED&SUBSYS_80AC1043&REV_C1\3&13C0B0C5&0&03: NVIDIA nForce2 Memory Controller
PCI\VEN_10DE&DEV_01EE&SUBSYS_80AC1043&REV_C1\3&13C0B0C5&0&02: NVIDIA nForce2 Memory Controller
PCI\VEN_10DE&DEV_01EF&SUBSYS_80AC1043&REV_C1\3&13C0B0C5&0&05: NVIDIA nForce2 Memory Controller
PCI\VEN_10DE&DEV_0221&SUBSYS_00000000&REV_A1\4&102AC5BC&0&00F0: NVIDIA GeForce 6200 
19 matching device(s) found.
 
 
=========== 
USB devices 
=========== 
 
USB\ROOT_HUB\4&36CE346&0                                    : USB Root Hub
USB\ROOT_HUB\4&37090E00&0                                   : USB Root Hub
USB\ROOT_HUB20\4&B74B78&0                                   : USB Root Hub
USB\VID_046D&PID_0920\5&13E31E82&0&1                        : Logitech QuickCam Express
4 matching device(s) found.

Last edited by Stiertje (2007-06-22 05:18:08)

  • Jaak
  • Old Timer Rookie
  • Offline
  • From: Eeklo, in the East Flanders
  • Registered: 2006-07-23
  • Posts: 3,594

Re: BSOD with SiI 3112 SATAlink controler

hi Stiertje,
you got on the NEWS page.  smile

This post was instrumental in finding the cause.
The new release should work for you.
It worked for other machines that would fail before this last update.

The answer was 42?
Kind regards, Jaak.
  • Registered: 2006-08-18
  • Posts: 22

Re: BSOD with SiI 3112 SATAlink controler

jtdoom wrote:

hi Stiertje,
you got on the NEWS page.  smile

This post was instrumental in finding the cause.
The new release should work for you.
It worked for other machines that would fail before this last update.

I saw I was on the front-page. What an honor tongue

Anyway, I've only had little time to try out a test cd, but that one still recognises my sata card as SATARaid instea of SATALink. I have only tested textmode though, so it might even be possible that the installation will continue without problems. Regretfully I haven't had time to test that.

It is also possible that nLite messes things up. At the moment I use the following sequence for my cd's

1st pass - nLite - Removing components and old drivers
2nd pass - RyanVM - Slipstream RyanVM Updates and Addons
3rd pass - nLite - Removing additional components (all regional settings and keyboards)
4th pass - nLite - Options and Tweaks (I like to keep them seperate)
5th pass - Driverpacks - Slipstream driverpacks (all packs + some 3rd party)
6th pass - nLite - Unattended settings + ISO

I hope it isn't nLite, but I'm going to try the driverpacks only and see what happens.




Anyway, many thanks for the effort.

[EDIT]
Typo
[/EDIT]

Last edited by Stiertje (2007-06-28 19:08:41)

  • Jaak
  • Old Timer Rookie
  • Offline
  • From: Eeklo, in the East Flanders
  • Registered: 2006-07-23
  • Posts: 3,594

Re: BSOD with SiI 3112 SATAlink controler

first thing you should look at is WINNT.SIF.
Nlite probably undid the change DPsBase made

when I do something like this for a final build..

X- - nLite - I previously did Unattended settings, and saved the WINNT.SIF file to a folder which has a few variants in it. (for re-use)
copy a source from storage drive to working folder
copy WINNT.SIF into it (if it is not yet in it)

nLite - (SP slipstream, if needed) Remove (Dotnet and little else) components , Options and Tweaks, LANGUAGES (99 Mb), regional settings and keyboards.
RyanVM - Slipstream RyanVM (previously tested and known good Updates) and Addons (dotnet and a few others).

Copy/SAVE that folder to storage.  (example, HOME_NL_OEMgold\XHNL_gold_SP2_LiteRVM\
Driverpacks - Slipstream driverpacks (all packs + some 3rd party)
make ISO (RVM or Nlite) XHNL_gold_SP2_LiteRVM70626.iso
rename the working folder to XHNL_gold_SP2_LiteRVM70626

after test in VPC and live machine tell me this is a good one, I can drop in variants of WINNT.SIF,

If the WIINT.SIF is one that does not autopartition/autoformat.. then I can also add a few lines just before EXIT in presetup.cmd

REM +==========================================================================+
REM |   Make CD usable for XP UPGRADE REPAIR method                    |
REM |   WINNTUPG  folder is needed   for this            |
REM |--------------------------------------------------------------------------|
DEL /F %systemroot%\system32\setupold.exe
The answer was 42?
Kind regards, Jaak.
  • Jaak
  • Old Timer Rookie
  • Offline
  • From: Eeklo, in the East Flanders
  • Registered: 2006-07-23
  • Posts: 3,594

Re: BSOD with SiI 3112 SATAlink controler

What brand and model (plus revision) motherboard do you have this problem on?

The answer was 42?
Kind regards, Jaak.
  • Registered: 2006-08-18
  • Posts: 22

Re: BSOD with SiI 3112 SATAlink controler

jtdoom wrote:

What brand and model (plus revision) motherboard do you have this problem on?

I've got an Asus A7N8X-X mobo and a SiI3112A PCI addin card for SATA disks. I also updated the bios of the Silicon Image card, to no avail.

I also checked your advice regarding the WINNT.SIF file. Driverpacks only adds "MsDosInitiated=No" to the WINNT.SIF file, and that line is also present in the nLite version. nLite only makes it "MsDosInitiated=0" which also works, since this value only tells setup to expect only a cd instead of floppydisks.

I've done installations with this disk, both on virtual machines as on real hardware, and none had problems. Only my own friggin' computer tongue

Anyway, I see that there is another update for the Mass Storage pack and I'm already building an image with it, so we'll see how it all works out. I'll ofcourse let you know how things worked out.

  • Jaak
  • Old Timer Rookie
  • Offline
  • From: Eeklo, in the East Flanders
  • Registered: 2006-07-23
  • Posts: 3,594

Re: BSOD with SiI 3112 SATAlink controler

hi
does it have  OemPreinstall=Yes  or     OemPreinstall=1 in winnt.sif ?

The answer was 42?
Kind regards, Jaak.
  • Jaak
  • Old Timer Rookie
  • Offline
  • From: Eeklo, in the East Flanders
  • Registered: 2006-07-23
  • Posts: 3,594

Re: BSOD with SiI 3112 SATAlink controler

I asked, because that is a line that MUST say NO or zero

The answer was 42?
Kind regards, Jaak.
  • Registered: 2006-08-18
  • Posts: 22

Re: BSOD with SiI 3112 SATAlink controler

jtdoom wrote:

hi
does it have  OemPreinstall=Yes  or     OemPreinstall=1 in winnt.sif ?

Here's my WINNT.SIF

[Data]
AutomaticUpdates="No"
Autopartition=0
MsDosInitiated=0
UnattendedInstall="Yes"

[Unattended]
UnattendMode=DefaultHide
UnattendSwitch="Yes"
OemPreinstall="Yes"
OemSkipEula="Yes"
ComputerType="Advanced Configuration and Power Interface (ACPI) PC", Retail
FileSystem=*
WaitForReboot="No"
NoWaitAfterTextMode=1
NoWaitAfterGUIMode=1
DriverSigningPolicy=Ignore
NonDriverSigningPolicy=Ignore
Hibernation="No"

[Display]
Xresolution=1152
Yresolution=864
BitsPerPel=32
Vrefresh=75

[SystemRestore]
DisableSR=1
CreateFirstRunRp=0

[GuiUnattended]
EncryptedAdminPassword="No"
AutoLogon="Yes"
AutoLogonCount=1
AdminPassword="XXXXXXXXX"
TimeZone=110
OEMSkipRegional=1
OemSkipWelcome=1

[Shell]
DefaultThemesOff="Yes"

[Components]

[UserData]
ProductKey="XXXXX-XXXXX-XXXXX-XXXXX-XXXXX"
ComputerName=XXXXXX
FullName="XXXXXX"
OrgName="XXXXXX"

[RegionalSettings]
SystemLocale="0409"
UserLocale="0409"
UserLocale_DefaultUser="0409"
InputLocale="0409:00000409"
InputLocale_DefaultUser="0409:00000409"

[Networking]
InstallDefaultComponents="Yes"

[Identification]
JoinWorkgroup="XXXXXX"

So basically it's just a simple Unattended Answer file.

I've done simulated installations with this build, and installations on actual machines, and all were good.




BTW, what does the following line mean?

Signature = "$Chicago$"

The old driverpack has this signature, whereas the new driverpack has a different one

Signature="$Windows NT$"

I'm not sure if this signifies something. It probably has something to do with the dropped Windows 98/ME and NT4 support, but it's the only real difference I can see.

Last edited by Stiertje (2007-07-02 03:09:50)

  • Jaak
  • Old Timer Rookie
  • Offline
  • From: Eeklo, in the East Flanders
  • Registered: 2006-07-23
  • Posts: 3,594

Re: BSOD with SiI 3112 SATAlink controler

hi
suppose you still needed a floppy because there is no good txtmode driver, then OemPreinstall=Yes says you cannot use the floppy.

The answer was 42?
Kind regards, Jaak.
  • Jaak
  • Old Timer Rookie
  • Offline
  • From: Eeklo, in the East Flanders
  • Registered: 2006-07-23
  • Posts: 3,594

Re: BSOD with SiI 3112 SATAlink controler

does mass storage 707 fix the BSOD?

The answer was 42?
Kind regards, Jaak.
  • Registered: 2006-08-18
  • Posts: 22

Re: BSOD with SiI 3112 SATAlink controler

jtdoom wrote:

hi
suppose you still needed a floppy because there is no good txtmode driver, then OemPreinstall=Yes says you cannot use the floppy.

I've made many disks with driverpacks, and just recently (after 7.04) it started BSOD'ing. Older builds worked like a charm.

Anyway, I don't think it is a faulty driver. My SATA card is recognized as an SiI3112r instead of the base SiI3112. This probably screws up the GUI mode setup because of the discrepancies between the Raid and the Base card drivers.

I'm going to make another build with the 7.07 MassStorage pack. /me is crossing his fingers.

  • Helmi
  • Moderator & Translator (German)
  • Offline
  • From: Germany
  • Registered: 2006-05-27
  • Posts: 1,799

Re: BSOD with SiI 3112 SATAlink controler

Stiertje wrote:

BTW, what does the following line mean?

Signature = "$Chicago$"

Just FYI, Chicago is the codename of your Win ver.
Same as the next OS is supposed to be called Vienna.
(there were some other names but I forgot sad)

MS somehow has it with cities, just as the two big CPU makers (Intel, AMD) do.

http://d1syubgj0w3cyv.cloudfront.net/cdn/farfuture/AeXmpESLemRyQ4RE-dgdjRhN_hKaXMe7woWjOK2wsnk/perpetual:forever/userbar/moderator-3.png

Coming up next - useful links:
• If you like this project, please support it with your donation!      • Grab your HW info (HWIDs) here!     
• If you are a newbie, be sure to check out the DriverPacks tutorial!     • Here's how to create your own DP!
  • Jaak
  • Old Timer Rookie
  • Offline
  • From: Eeklo, in the East Flanders
  • Registered: 2006-07-23
  • Posts: 3,594

Re: BSOD with SiI 3112 SATAlink controler

Stiertje is one of the people that still had problems, and the driver he says works has NO specific sub/Rev info in HWID for that card.
(not Integrated in mobo. It's a card..)

While I was trying to fix the issue, I got interrupted by real life, and later on a 'half fix' got uploaded because  the fix was in two files, and one of them was not even uploaded and the other was what I had when I got interupted, not what I had when I finished..

After the BIG typo, Krell mentioned that ''typo'' Which I knew was intended for Stiertje.
(erm, Krell did not spot no such INF had the HWID.)  and I have then done some more work, more checking, and 7.07 came along.

All in all, I am ashamed of the rush jobs I published.
The reason why  those rush jobs even got online, is that fixes were needed, and testers are in short supply.
I had the time, because this was ONE week of holiday I had for . The good accident happened, a critical typo.
Mass Storage fell flat.
I am lucky because it got the detectives out. And that typo then got guys to look at stuff and tell us about it, what actually revealed things that had been there for quite a while.

All these things/fixes are in 7.07.
Those detectives, they could be testers.
It was not my intention to make such a mess (e.g. a comma kils DriverPacks.)
But, you know, it were not the first time guys tried to fix it and got "backfire."
It may sound boastful, but I tried to fix a few as a return of favour, and think I done more than a few.

don't shoot the girl, the pianist loves her.

The answer was 42?
Kind regards, Jaak.
  • Jaak
  • Old Timer Rookie
  • Offline
  • From: Eeklo, in the East Flanders
  • Registered: 2006-07-23
  • Posts: 3,594

Re: BSOD with SiI 3112 SATAlink controler

besides, I am a blonde..

The answer was 42?
Kind regards, Jaak.
  • Registered: 2006-08-18
  • Posts: 22

Re: BSOD with SiI 3112 SATAlink controler

jtdoom wrote:

besides, I am a blonde..

You know what they say about blondes. tongue

Anyway, I still had no luck with the new MassStorage pack, so I'm going to try out some different angles.

- Slipstream an older pack, notably 7.04 which has worked before
- Only slipstream driverpacks and nothing else
- And if that doesn't help, only slipstream MassStorage driverpack

Will let you know what I find out.

  • Registered: 2006-08-18
  • Posts: 22

Re: BSOD with SiI 3112 SATAlink controler

Darn, no luck.

When I only use Driverpacks and nothing else I still recieve the BSOD, but now before I even have the chance of choosing a partition.

BTW, I also found a HWID overlap between [S-4] and [S-5]

PCI\VEN_1095&DEV_3512&SUBSYS_02B71014
  • Jaak
  • Old Timer Rookie
  • Offline
  • From: Eeklo, in the East Flanders
  • Registered: 2006-07-23
  • Posts: 3,594

Re: BSOD with SiI 3112 SATAlink controler

Hi, that overlap is no longer in 7.07

txt search /// one INF, and 1 INI and matching folders.

I am still baffled about this one.
when u test, and it gets correctly identified, you want to immediately run save-Hwids because I am not going to give up on that card.

edit, change that line in winntsif, or use a vanilla XP with floppy

it will take you 2 hours, I know, but after that run save-hwid because we do need that extra string after ver2
(which does NOT show in ANY official driver we have, and not in the one what you told us works for you.)

Last edited by jtdoom (2007-07-03 07:46:18)

The answer was 42?
Kind regards, Jaak.
  • Registered: 2006-08-18
  • Posts: 22

Re: BSOD with SiI 3112 SATAlink controler

Sorry bro, HWID overlap is still in the file "DriverPack_MassStorage_blablabla.ini". I even re-downloaded the pack to be sure.
And with the overlap I mean it's an overlap inside the INI file, not in the actual folders. I'm not sure if it matters, just thought you should know.

Well, I'm gonna try and get you that vanilla HWID of my card. Will let you know in an hour or so.

  • Registered: 2006-08-18
  • Posts: 22

Re: BSOD with SiI 3112 SATAlink controler

Fresh delivery of HWID's. Doesn't seem to be different though.

 
=========== 
PCI devices 
=========== 
 
 
PCI\VEN_1002&DEV_5159&SUBSYS_7C02174B&REV_00\4&3B1D9AB8&0&4840: RADEON 7000 SERIES          
PCI\VEN_1095&DEV_3112&SUBSYS_31121095&REV_02\4&3B1D9AB8&0&4040: Silicon Image SiI 3112 SATALink Controller
PCI\VEN_10DE&DEV_0060&SUBSYS_00000000&REV_A4\3&13C0B0C5&0&08: PCI standard ISA bridge
PCI\VEN_10DE&DEV_0064&SUBSYS_0C111043&REV_A2\3&13C0B0C5&0&09: NVIDIA nForce PCI System Management
PCI\VEN_10DE&DEV_0065&SUBSYS_0C111043&REV_A2\3&13C0B0C5&0&48: NVIDIA nForce2 ATA Controller
PCI\VEN_10DE&DEV_0066&SUBSYS_80A71043&REV_A1\3&13C0B0C5&0&20: NVIDIA nForce Networking Controller
PCI\VEN_10DE&DEV_0067&SUBSYS_0C111043&REV_A4\3&13C0B0C5&0&10: Standard OpenHCD USB Host Controller
PCI\VEN_10DE&DEV_0067&SUBSYS_0C111043&REV_A4\3&13C0B0C5&0&11: Standard OpenHCD USB Host Controller
PCI\VEN_10DE&DEV_0068&SUBSYS_0C111043&REV_A4\3&13C0B0C5&0&12: Standard Enhanced PCI to USB Host Controller
PCI\VEN_10DE&DEV_006A&SUBSYS_80951043&REV_A1\3&13C0B0C5&0&30: Realtek AC'97 Audio
PCI\VEN_10DE&DEV_006C&SUBSYS_00000000&REV_A3\3&13C0B0C5&0&40: PCI standard PCI-to-PCI bridge
PCI\VEN_10DE&DEV_01E0&SUBSYS_00000000&REV_C1\3&13C0B0C5&0&00: PCI standard host CPU bridge
PCI\VEN_10DE&DEV_01E8&SUBSYS_00000000&REV_C1\3&13C0B0C5&0&F0: NVIDIA nForce2 AGP Host to PCI Bridge
PCI\VEN_10DE&DEV_01EA&SUBSYS_80AC1043&REV_C1\3&13C0B0C5&0&01: NVIDIA nForce2 400 Memory Controller
PCI\VEN_10DE&DEV_01EC&SUBSYS_80AC1043&REV_C1\3&13C0B0C5&0&04: NVIDIA nForce2 Memory Controller
PCI\VEN_10DE&DEV_01ED&SUBSYS_80AC1043&REV_C1\3&13C0B0C5&0&03: NVIDIA nForce2 Memory Controller
PCI\VEN_10DE&DEV_01EE&SUBSYS_80AC1043&REV_C1\3&13C0B0C5&0&02: NVIDIA nForce2 Memory Controller
PCI\VEN_10DE&DEV_01EF&SUBSYS_80AC1043&REV_C1\3&13C0B0C5&0&05: NVIDIA nForce2 Memory Controller
PCI\VEN_10DE&DEV_0221&SUBSYS_00000000&REV_A1\4&102AC5BC&0&00F0: NVIDIA GeForce 6200 
19 matching device(s) found.
 
 
=========== 
USB devices 
=========== 
 
USB\ROOT_HUB\4&36CE346&0                                    : USB Root Hub
USB\ROOT_HUB\4&37090E00&0                                   : USB Root Hub
USB\ROOT_HUB20\4&B74B78&0                                   : USB Root Hub
USB\VID_046D&PID_0920\5&13E31E82&0&1                        : Logitech QuickCam Express
4 matching device(s) found.
 
=========== 
PCI devices 
=========== 
 
 
PCI\VEN_1002&DEV_5159&SUBSYS_7C02174B&REV_00\4&3B1D9AB8&0&4840: RADEON 7000 SERIES          
PCI\VEN_1095&DEV_3112&SUBSYS_31121095&REV_02\4&3B1D9AB8&0&4040: Silicon Image SiI 3112 SATALink Controller
PCI\VEN_10DE&DEV_0060&SUBSYS_00000000&REV_A4\3&13C0B0C5&0&08: PCI standard ISA bridge
PCI\VEN_10DE&DEV_0064&SUBSYS_0C111043&REV_A2\3&13C0B0C5&0&09: NVIDIA nForce PCI System Management
PCI\VEN_10DE&DEV_0065&SUBSYS_0C111043&REV_A2\3&13C0B0C5&0&48: NVIDIA nForce2 ATA Controller
PCI\VEN_10DE&DEV_0066&SUBSYS_80A71043&REV_A1\3&13C0B0C5&0&20: NVIDIA nForce Networking Controller
PCI\VEN_10DE&DEV_0067&SUBSYS_0C111043&REV_A4\3&13C0B0C5&0&10: Standard OpenHCD USB Host Controller
PCI\VEN_10DE&DEV_0067&SUBSYS_0C111043&REV_A4\3&13C0B0C5&0&11: Standard OpenHCD USB Host Controller
PCI\VEN_10DE&DEV_0068&SUBSYS_0C111043&REV_A4\3&13C0B0C5&0&12: Standard Enhanced PCI to USB Host Controller
PCI\VEN_10DE&DEV_006A&SUBSYS_80951043&REV_A1\3&13C0B0C5&0&30: Realtek AC'97 Audio
PCI\VEN_10DE&DEV_006C&SUBSYS_00000000&REV_A3\3&13C0B0C5&0&40: PCI standard PCI-to-PCI bridge
PCI\VEN_10DE&DEV_01E0&SUBSYS_00000000&REV_C1\3&13C0B0C5&0&00: PCI standard host CPU bridge
PCI\VEN_10DE&DEV_01E8&SUBSYS_00000000&REV_C1\3&13C0B0C5&0&F0: NVIDIA nForce2 AGP Host to PCI Bridge
PCI\VEN_10DE&DEV_01EA&SUBSYS_80AC1043&REV_C1\3&13C0B0C5&0&01: NVIDIA nForce2 400 Memory Controller
PCI\VEN_10DE&DEV_01EC&SUBSYS_80AC1043&REV_C1\3&13C0B0C5&0&04: NVIDIA nForce2 Memory Controller
PCI\VEN_10DE&DEV_01ED&SUBSYS_80AC1043&REV_C1\3&13C0B0C5&0&03: NVIDIA nForce2 Memory Controller
PCI\VEN_10DE&DEV_01EE&SUBSYS_80AC1043&REV_C1\3&13C0B0C5&0&02: NVIDIA nForce2 Memory Controller
PCI\VEN_10DE&DEV_01EF&SUBSYS_80AC1043&REV_C1\3&13C0B0C5&0&05: NVIDIA nForce2 Memory Controller
PCI\VEN_10DE&DEV_0221&SUBSYS_00000000&REV_A1\4&102AC5BC&0&00F0: NVIDIA GeForce 6200 
19 matching device(s) found.
 
 
=========== 
USB devices 
=========== 
 
USB\ROOT_HUB\4&36CE346&0                                    : USB Root Hub
USB\ROOT_HUB\4&37090E00&0                                   : USB Root Hub
USB\ROOT_HUB20\4&B74B78&0                                   : USB Root Hub
USB\VID_046D&PID_0920\5&13E31E82&0&1                        : Logitech QuickCam Express
USB\VID_05E3&PID_0702\5&221832C9&0&3                        : USB Mass Storage Device
USBSTOR\DISK&VEN_TOSHIBA&PROD_MK4025GAS&REV_0811\6&38C08D00&0: TOSHIBA MK4025GAS USB Device
6 matching device(s) found.
 
=========== 
PCI devices 
=========== 
 
 
PCI\VEN_1002&DEV_5159&SUBSYS_7C02174B&REV_00\4&3B1D9AB8&0&4840: RADEON 7000 / RADEON VE Family (Microsoft Corporation)
PCI\VEN_1095&DEV_3112&SUBSYS_31121095&REV_02\4&3B1D9AB8&0&4040: Silicon Image SiI 3112 SATALink Controller
PCI\VEN_10DE&DEV_0060&SUBSYS_00000000&REV_A4\3&13C0B0C5&0&08: PCI standard ISA bridge
PCI\VEN_10DE&DEV_0064&SUBSYS_0C111043&REV_A2\3&13C0B0C5&0&09: SM Bus Controller
PCI\VEN_10DE&DEV_0065&SUBSYS_0C111043&REV_A2\3&13C0B0C5&0&48: Standard Dual Channel PCI IDE Controller
PCI\VEN_10DE&DEV_0066&SUBSYS_80A71043&REV_A1\3&13C0B0C5&0&20: Ethernet Controller
PCI\VEN_10DE&DEV_0067&SUBSYS_0C111043&REV_A4\3&13C0B0C5&0&10: Standard OpenHCD USB Host Controller
PCI\VEN_10DE&DEV_0067&SUBSYS_0C111043&REV_A4\3&13C0B0C5&0&11: Standard OpenHCD USB Host Controller
PCI\VEN_10DE&DEV_0068&SUBSYS_0C111043&REV_A4\3&13C0B0C5&0&12: Standard Enhanced PCI to USB Host Controller
PCI\VEN_10DE&DEV_006A&SUBSYS_80951043&REV_A1\3&13C0B0C5&0&30: Multimedia Audio Controller
PCI\VEN_10DE&DEV_006C&SUBSYS_00000000&REV_A3\3&13C0B0C5&0&40: PCI standard PCI-to-PCI bridge
PCI\VEN_10DE&DEV_01E0&SUBSYS_00000000&REV_C1\3&13C0B0C5&0&00: PCI standard host CPU bridge
PCI\VEN_10DE&DEV_01E8&SUBSYS_00000000&REV_C1\3&13C0B0C5&0&F0: PCI standard PCI-to-PCI bridge
PCI\VEN_10DE&DEV_01EA&SUBSYS_80AC1043&REV_C1\3&13C0B0C5&0&01: PCI standard RAM Controller
PCI\VEN_10DE&DEV_01EC&SUBSYS_80AC1043&REV_C1\3&13C0B0C5&0&04: PCI standard RAM Controller
PCI\VEN_10DE&DEV_01ED&SUBSYS_80AC1043&REV_C1\3&13C0B0C5&0&03: PCI standard RAM Controller
PCI\VEN_10DE&DEV_01EE&SUBSYS_80AC1043&REV_C1\3&13C0B0C5&0&02: PCI standard RAM Controller
PCI\VEN_10DE&DEV_01EF&SUBSYS_80AC1043&REV_C1\3&13C0B0C5&0&05: PCI standard RAM Controller
PCI\VEN_10DE&DEV_0221&SUBSYS_00000000&REV_A1\4&102AC5BC&0&00F0: Video Controller (VGA Compatible)
19 matching device(s) found.
 
 
=========== 
USB devices 
=========== 
 
USB\ROOT_HUB\4&36CE346&0                                    : USB Root Hub
USB\ROOT_HUB\4&37090E00&0                                   : USB Root Hub
USB\ROOT_HUB20\4&B74B78&0                                   : USB Root Hub
USB\VID_046D&PID_0920\5&13E31E82&0&1                        : USB Device
USB\VID_05E3&PID_0702\5&221832C9&0&3                        : USB Mass Storage Device
USBSTOR\DISK&VEN_TOSHIBA&PROD_MK4025GAS&REV_0811\6&38C08D00&0: TOSHIBA MK4025GAS USB Device
6 matching device(s) found.

It even recognized and had drivers for my Radeon 7000 graphics card. Go figure how old that crap card is tongue

Last edited by Stiertje (2007-07-03 08:57:52)

  • Jaak
  • Old Timer Rookie
  • Offline
  • From: Eeklo, in the East Flanders
  • Registered: 2006-07-23
  • Posts: 3,594

Re: BSOD with SiI 3112 SATAlink controler

PCI\VEN_1095&DEV_3512&SUBSYS_02B71014 found in older driver/newer driver for S-4,

you were right.. I removed it from INI in S-5 now.

I think we are looking at a SiL Image BIOS problem here.
The updated S-4 supports a newer BIOS variant of this chip.

see here
http://forum.driverpacks.net/viewtopic. … 406#p12406

The answer was 42?
Kind regards, Jaak.