DriverPacks.net Forum - BSOD with SiI 3112 SATAlink controler

Re: BSOD with SiI 3112 SATAlink controler

null@example.com (Jaak) — Thu, 05 Jul 2007 05:48:54 +0000

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

Re: BSOD with SiI 3112 SATAlink controler

null@example.com (Stiertje) — Mon, 02 Jul 2007 21:25:56 +0000

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

Re: BSOD with SiI 3112 SATAlink controler

null@example.com (Stiertje) — Mon, 02 Jul 2007 20:43:05 +0000

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.

Re: BSOD with SiI 3112 SATAlink controler

null@example.com (Jaak) — Mon, 02 Jul 2007 20:05:50 +0000

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

Re: BSOD with SiI 3112 SATAlink controler

null@example.com (Stiertje) — Mon, 02 Jul 2007 20:00:37 +0000

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

Re: BSOD with SiI 3112 SATAlink controler

null@example.com (Stiertje) — Mon, 02 Jul 2007 11:01:46 +0000

jtdoom wrote:

besides, I am a blonde..

You know what they say about blondes.

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.

Re: BSOD with SiI 3112 SATAlink controler

null@example.com (Jaak) — Sun, 01 Jul 2007 23:25:10 +0000

besides, I am a blonde..

Re: BSOD with SiI 3112 SATAlink controler

null@example.com (Jaak) — Sun, 01 Jul 2007 22:21:03 +0000

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.

Re: BSOD with SiI 3112 SATAlink controler

null@example.com (Helmi) — Sun, 01 Jul 2007 20:14:44 +0000

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 )

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

Re: BSOD with SiI 3112 SATAlink controler

null@example.com (Stiertje) — Sun, 01 Jul 2007 19:39:57 +0000

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.

Re: BSOD with SiI 3112 SATAlink controler

null@example.com (Jaak) — Sun, 01 Jul 2007 16:47:37 +0000

does mass storage 707 fix the BSOD?

Re: BSOD with SiI 3112 SATAlink controler

null@example.com (Jaak) — Sun, 01 Jul 2007 16:46:38 +0000

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

Re: BSOD with SiI 3112 SATAlink controler

null@example.com (Stiertje) — Sun, 01 Jul 2007 15:37:46 +0000

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.

Re: BSOD with SiI 3112 SATAlink controler

null@example.com (Jaak) — Fri, 29 Jun 2007 19:45:35 +0000

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

Re: BSOD with SiI 3112 SATAlink controler

null@example.com (Jaak) — Fri, 29 Jun 2007 02:55:23 +0000

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