Topic: [SOLVED] SiI 3112r controller doesnt work: 0x7B BSOD

Hi Bashrat, long time not heard of me!
Was a bit busy smile
Nice to see that you're still doing a very nice job over here.

Ontopic:

Now i thought to make a new UA XPcd with the latest drivers because my system had a few "bugs".
All the current available driverpacks used.

I'm unable to get my harddrives recognised properly during text mode setup!
Just plain XPsp2 with ONLY driverpacks doesn't even work in any way or settings through the base pack. (method1 / 2)
It only will show two Sata hdd's without any existing partitions or raid configuration on it. (current config like: C:\ , D:\ etc..)

It says that they have an unrecognised filesystem.. When i use my old cd with basepack v5.0.5.2 it will show flawlessly what the current config is.
I suspect that there is something not okay with the latest drivers.

Someone over here who can confirm this? (or prove the opposite ofcourse)
Really need to get it running, try'd all the ways i could think of.
Has been too long ago to jump fully into the files sad

I'm willing to test things if neccesary, thnx in advance.

my HWid:

=========== 
PCI devices 
=========== 
 
 
PCI\VEN_1095&DEV_3112&SUBSYS_61121095&REV_02\4&3B1D9AB8&0&5840: Silicon Image SiI 3112 SATARaid 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: NVIDIA(R) nForce(TM) Audio Codec Interface
PCI\VEN_10DE&DEV_006B&SUBSYS_0C111043&REV_A2\3&13C0B0C5&0&28: NVIDIA(R) nForce(TM) MCP Audio Processing Unit
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_01EB&SUBSYS_80AC1043&REV_C1\3&13C0B0C5&0&01: NVIDIA nForce2 Ultra 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_0343&SUBSYS_81711043&REV_A1\4&102AC5BC&0&00F0: NVIDIA GeForce FX 5700LE
PCI\VEN_11AB&DEV_4320&SUBSYS_811A1043&REV_13\4&3B1D9AB8&0&2040: Marvell Yukon 88E8001/8003/8010 PCI Gigabit Ethernet Controller
PCI\VEN_8086&DEV_1040&SUBSYS_10008086&REV_00\4&3B1D9AB8&0&4840: Intel(R) 536EP Modem
21 matching device(s) found.

Last edited by Bâshrat the Sneaky (2006-08-04 17:46:49)

Re: [SOLVED] SiI 3112r controller doesnt work: 0x7B BSOD

Same here...cept with Intel Sata Raid.

The following sentence is false.
The preceding sentence is true.

Re: [SOLVED] SiI 3112r controller doesnt work: 0x7B BSOD

Update;
I saw the post from VoYaGeRTM1977 and downloaded the new drivers.
Then i try'd to compare things/files, but then thought about integrate them with Nlite on top of my latest (not working!) XPcd  with the driverpacks allready included. I mentioned in my first post the not recognised partitions/hdd drives.

Like what the.. let's try!

And that works flawless, it recognised my current config like the old driverpack in textmode.
I skipped out with the F3 and didn't do an actual install, but hoped it could bring some life in my problem here wink

I could try to incorporate them in the latest driverpac / my XPCD to test, but i'm much too long out of it to "just do so".. (shame)

Any help with that, or just an answer to hold on untill a fix comes around would be appreciated!

@razormoon
Perhaps give that a try also, maybe it works for you 2!?

Re: [SOLVED] SiI 3112r controller doesnt work: 0x7B BSOD

same with 3512 , they dont work , keep getting BSOD

Re: [SOLVED] SiI 3112r controller doesnt work: 0x7B BSOD

same to me..
to install windows, need to use a floppy with other drivers that i downloaded from silicon-image website.

why this problem? i think that the real problem, are the si driver that are included in the masstorage driverpack.. have you fized this in the new release???

Can you make me betatester??

thanks a lot

Re: [SOLVED] SiI 3112r controller doesnt work: 0x7B BSOD

I don't have the slightest clue what's causing this... Let's hope a driver update will fix it.

EDIT: What's the error code of the BSOD? 0x7B?

Last edited by Bâshrat the Sneaky (2006-08-02 04:33:30)

Founder of DriverPacks.net — wimleers.com

Re: [SOLVED] SiI 3112r controller doesnt work: 0x7B BSOD

@Bâshrat the Sneaky ..
i think that the error code is yet 0x7B.. it's caused by an erroneus driver for si3112r and si3112 sata driver... if you go to siliconimage website, you can download the fixed and correct driver.. if you want, i send you by mail the driver!!!

by and thanks a lot

Re: [SOLVED] SiI 3112r controller doesnt work: 0x7B BSOD

the link for the fixed driver are:

SI3112 BASE driver

SI3112 SATA RAID driver

bye Bâshrat the Sneaky!!! and thanks

Re: [SOLVED] SiI 3112r controller doesnt work: 0x7B BSOD

So the driver that I've included was actually a CORRUPT one, put online by Silicon Image? I'm glad I'm not to blame, except for being so slow in updating the DriverPack.

All Silicon Image drivers have been updated already!

Founder of DriverPacks.net — wimleers.com

Re: [SOLVED] SiI 3112r controller doesnt work: 0x7B BSOD

same with 3512
And they also say on their site that when you want to use the latest version of the drivers you need to update your sata bios.

I will help people with this if needed.

Last edited by muiz3 (2006-08-03 14:23:09)

Re: [SOLVED] SiI 3112r controller doesnt work: 0x7B BSOD

remove SI3112 BASE driver
only use SI3112 SATA RAID driver
maybe pass

sorry?my english is poor?
i am a chinese

sorry ? my english is poor

Re: [SOLVED] SiI 3112r controller doesnt work: 0x7B BSOD

muniao wrote:

remove SI3112 BASE driver
only use SI3112 SATA RAID driver
maybe pass

sorry?my english is poor?
i am a chinese

DriverPack MassStorage 6.08 will be released together with DriverPack Sound B 6.08, it's probably solved by a driver update wink

Founder of DriverPacks.net — wimleers.com

Re: [SOLVED] SiI 3112r controller doesnt work: 0x7B BSOD

Hi folks!
Sorry to reopen this thread but I still have serious troubles with installing XP on a SATA disk with the actual driverpack. The Bluscreen 0x0000007B appears after the computer tries to start GUI Mode of Setup routine.

I have an ASUS A7n8x Deluxe rev. 2.0 board with 1008 Bios and SATA BIOS v4.2.47
I´ve tried all possible BIOS settings (switched to SATA, RAID, tried to set SCSI as first boot device and so on...) but it seems all senseless ;(

Its now the third day trying that, and im out of ideas by now.

Those are the procedures, I've tried by now:

1) Slipstreamed your original driverpacks MassStorage, Chipset, Lan, Sound and WLAN (did i understand that correctly that the corrected Sil drivers are already included?) -> BSOD

2) replaced drivers in folder 4 and 5 with the new SIl drivers, slipstreamed them -> BSOD

3) deleted directory 4 as well as 5A and replaced the driver in 5 with the original ASUS driver (which worked pretty fine all the last years when loaded from floppy disk. But at those times my bios was only 1006)
I´ve tried this, cause someone wrote only the 3112r driver is needed not the 3112 (makes sense, ASUS only put this driver on his cd)
Any way it failed to ;-( -> BSOD

4) I put the new SIl driver 3112r on floppy disk pressed F6 when asked for additional drivers, selected the correct driver but then Windows said there is an Error in the sysfile with Errorcode 4 (I've tried both, the Windows Xp and the Windows NT/2000 driver)

5) Meanwhile I´ve found a Microsoft Sil driver from Feb2006, tried to install it with F6, but the result was the same -> BSOD

[EDIT] I've switched now to a bios mod from trats whichs is a modified version of 1008 but with SIl version 4274. I tried all the above tings again -> still BSODs ;-(


Well and here I am now - I do not have any ideas what to do now
Have I forgotten something?
Is there something wrong replacing your drivers manually in your Massstorage driver pack?

I'm open for any suggestions
thx a lot
Jukuhullui

Last edited by jukuhullui (2006-08-12 23:06:27)

Re: [SOLVED] SiI 3112r controller doesnt work: 0x7B BSOD

these driver can't simple integral
because when bios and setting is different, then the driver is different
when the bios setting is sata(not raid),si3112 maybe use "pciide"  driver

sorry ? my english is poor

Re: [SOLVED] SiI 3112r controller doesnt work: 0x7B BSOD

@jukuhullul: did you update to the latest BIOS?

Founder of DriverPacks.net — wimleers.com

Re: [SOLVED] SiI 3112r controller doesnt work: 0x7B BSOD

well,
I've tried 5 different bios, the 1007, the 1008 orginal ones from asus, the modded version with the 4250er SATA SIL Version (which worked for most of the people and their SATA disks) and the lastest modded 1008r3 with the 4276er SATA Sil Version.

There was no difference, everytime I've tried, I got the same BSOD after the dosbased filecopy process of windows installation.

Funny thing: I also tried the original XP CD with slipstreamed SP2 in it, ut without driverpackages, and got the same bluescreen shortly after starting the installation, which tells me, your drivers are not as bad as I thought :-)

@your new driverpack: I slipstreamed the massstorage package and your new basedriver package, which worked without errors. But now an error occured during the filecopy process of the dosbased windows installer, saying newdev.dll can't be copied. Perhaps only an error in image creation? I will test it tomorrow....I´ve tried that 4 times, everytime it was the same dll.

Re: [SOLVED] SiI 3112r controller doesnt work: 0x7B BSOD

Are you using the latest DriverPack Sound B? Please post your DPs_BASE.log!

Founder of DriverPacks.net — wimleers.com

Re: [SOLVED] SiI 3112r controller doesnt work: 0x7B BSOD

muniao wrote:

these driver can't simple integral
because when bios and setting is different, then the driver is different
when the bios setting is sata(not raid),si3112 maybe use "pciide"  driver

I'm not sure if I understand you correctly. I know that a different SATA Bios version could need a new driver version. But as "muiz3" said: for the now in the driverpackage included drivers I need the latest SIL Bios, which is 4276. So this should work, because its exactly the bios I already have flashed on my computer.

what do you mean with with "bios and setting is different"? And why should si32212 use pciide, when SATA (not Raid) is activated in bios?

Re: [SOLVED] SiI 3112r controller doesnt work: 0x7B BSOD

Bâshrat the Sneaky wrote:

Are you using the latest DriverPack Sound B? Please post your DPs_BASE.log!

Wow - that was quick :-)

here it is:

2006-08-12 13:57:20 : <INIT> DriverPacks BASE 6.08.1 initialized.
2006-08-12 13:57:20 : <INIT> Host environment: WIN_XP Service Pack 1 on X86 CPU.
2006-08-12 13:57:20 : <INIT> Detected settings file "X:\Software\Treiber, Codecs & Patches\WinXP Stuff & Tuning\Tools\Slipstreaming\Hotfixes and Drivers\DriverPacks\DriverBase 6061\DPs_BASE.ini".
2006-08-12 13:57:20 : <INIT> The platform wnt5_x86-32_disc will be used (which is the 'disc' installation platform for the OS family 'wnt5_x86-32').
2006-08-12 13:57:20 : <INIT> Imported settings from settings file.
2006-08-12 13:57:20 : <INIT> Detected DriverPack Chipset 6.08!
2006-08-12 13:57:20 : <INIT> Detected DriverPack Graphics A 6.08!
2006-08-12 13:57:20 : <INIT> Detected DriverPack Graphics B 6.03!
2006-08-12 13:57:20 : <INIT> Detected DriverPack Graphics C 6.03!
2006-08-12 13:57:20 : <INIT> Detected DriverPack LAN 6.05.1!
2006-08-12 13:57:20 : <INIT> Detected DriverPack LAN 6.08!
2006-08-12 13:57:20 : <INIT> Detected DriverPack MassStorage 6.08!
2006-08-12 13:57:20 : <INIT> Detected DriverPack Sound A 6.06.1!
2006-08-12 13:57:20 : <INIT> Detected DriverPack Sound B 6.06!
2006-08-12 13:57:20 : <INIT> Detected DriverPack WLAN 6.05!
2006-08-12 13:57:20 : <INIT> Could not detect any 3rd party DriverPacks.
2006-08-12 13:57:20 : <INIT> DriverPacks scanned sucessfully.
2006-08-12 13:57:20 : <GUI>  Initialized GUI.
2006-08-12 13:57:20 : <GUI>  Created a list of all available language files.
2006-08-12 13:57:21 : <GUI>  Set the last used language, English, as the GUI language.
2006-08-12 13:57:28 : <GUI>  Refreshed UpdateChecker with success.
2006-08-12 13:57:38 : <GUI>  Saved settings!
2006-08-12 13:57:38 : <GUI>  Closed GUI.
2006-08-12 13:57:38 : <SEL>  Selected module: mod_slip_wxp_x86-32_disc_m2.
2006-08-12 13:57:50 : <PREP> Removed all attributes from \I386.
2006-08-12 13:57:50 : <PREP> Deleted old DriverPacks.
2006-08-12 13:57:50 : <PREP> Deleted old method 2 related files.
2006-08-12 13:57:51 : <PREP> Restored original mass storage text mode driver adpu160m.sys.
2006-08-12 13:57:51 : <PREP> Restored original mass storage text mode driver ALIIDE.sys.
2006-08-12 13:57:51 : <PREP> Restored original mass storage text mode driver dac2w2k.sys.
2006-08-12 13:57:51 : <PREP> Restored original mass storage text mode driver dac960nt.sys.
2006-08-12 13:57:51 : <PREP> Restored original mass storage text mode driver dpti2o.sys.
2006-08-12 13:57:51 : <PREP> Restored original mass storage text mode driver hpt3xx.sys.
2006-08-12 13:57:51 : <PREP> Restored original mass storage text mode driver mraid35x.sys.
2006-08-12 13:57:51 : <PREP> Restored original mass storage text mode driver ql12160.sys.
2006-08-12 13:57:51 : <PREP> Restored original mass storage text mode driver ultra.sys.
2006-08-12 13:57:51 : <PREP> Deleted old DriverPack MassStorage text mode drivers.
2006-08-12 13:57:52 : <PREP> Cleaned up \I386\svcpack.inf.
2006-08-12 13:57:52 : <PREP> Unslipstreamed KB883667, KB888111, KB913425.
2006-08-12 13:57:52 : <PREP> Restored \I386\winnt.sif.
2006-08-12 13:57:52 : <PREP> Restored \I386\txtsetup.sif.
2006-08-12 13:57:52 : <PREP> Restored \I386\dosnet.inf.
2006-08-12 13:57:52 : <PREP> Restored original setup: method 2 was used previously.
2006-08-12 13:57:52 : <PREP> Cleaned up \$OEM$\cmdlines.txt.
2006-08-12 13:57:52 : <PREP> Created temporary working directory.
2006-08-12 13:57:52 : <SLIP> Extracted necessary files for method 2.
2006-08-12 13:57:52 : <SLIP> Created necessary directory structure for method 2.
2006-08-12 13:57:53 : <SLIP> Copied files necessary for method 2.
2006-08-12 13:58:08 : <SLIP> Copied DriverPacks to \OEM.
2006-08-12 13:58:08 : <SLIP> Extracted and deleted \I386\svcpack.in_.
2006-08-12 13:58:08 : <SLIP> Updated \I386\svcpack.inf file to support KB888111 and KB913425.
2006-08-12 13:58:09 : <SLIP> Updated \I386\txtsetup.sif file to support KB888111.
2006-08-12 13:58:10 : <SLIP> Updated \I386\dosnet.inf file to support KB888111.
2006-08-12 13:58:10 : <SLIP> Updated \I386\dosnet.inf file to support KB913425.
2006-08-12 13:58:13 : <SLIP> Extracted DriverPack MassStorage to a temporary working directory.
2006-08-12 13:58:29 : <SLIP> Created QuickStream Cache for DriverPack MassStorage text mode drivers.
2006-08-12 13:58:29 : <SLIP> Slipstreamed DP MassStorage text mode drivers using QuickStream Cache.
2006-08-12 13:58:33 : <SLIP> Removed entries from \I386\txtsetup.sif that will be updated.
2006-08-12 13:58:33 : <SLIP> Removed entries from \I386\dosnet.inf that will be updated.
2006-08-12 13:58:56 : <SLIP> Updated \I386\dosnet.inf and \I386\txtsetup.sif to support DP MassStorage text mode drivers.
2006-08-12 13:58:57 : <SLIP> Compressed setup.exe to SETUP.EX_.
2006-08-12 13:58:57 : <SLIP> Deleted old presetup.cmd file from \I386.
2006-08-12 13:58:57 : <SLIP> Created \I386\presetup.cmd file.
2006-08-12 13:58:57 : <SLIP> Updated \I386\txtsetup.sif to support method 2.
2006-08-12 13:58:57 : <SLIP> Updated \I386\dosnet.inf to support method 2.
2006-08-12 13:58:57 : <SLIP> Updated \I386\winnt.sif to support method 2.
2006-08-12 13:58:57 : <SLIP> Updated DPsFnshr.ini to disable KTD.
2006-08-12 13:58:57 : <SLIP> Updated \$OEM$\cmdlines.txt to execute ROE.exe.
2006-08-12 13:58:57 : <SLIP> Slipstream finished in 1 minutes and 19 seconds.
2006-08-12 13:59:12 : <CLNP> Temporary working directory successfully deleted.
2006-08-12 13:59:12 : Program terminated.

Re: [SOLVED] SiI 3112r controller doesnt work: 0x7B BSOD

Everything seems to go right there... so that leaves me with only one choice: I need the HWID of your SiI 3112r controller, but the problem is that your installation doesn't start... If you have a spare PATA HDD, I'd suggest that you install Windows on that one, then get the HWID and then report it back. A lot of work, but I don't have a crystal ball either.

Founder of DriverPacks.net — wimleers.com

Re: [SOLVED] SiI 3112r controller doesnt work: 0x7B BSOD

Bâshrat the Sneaky wrote:

Everything seems to go right there... so that leaves me with only one choice: I need the HWID of your SiI 3112r controller, but the problem is that your installation doesn't start... If you have a spare PATA HDD, I'd suggest that you install Windows on that one, then get the HWID and then report it back. A lot of work, but I don't have a crystal ball either.

Ahm...I have another disk already running with winxp on the same machine. Is that adequate enought? Oh and from where can I extract the HWID?

Ohh and Bashrat: Thx!!

Re: [SOLVED] SiI 3112r controller doesnt work: 0x7B BSOD

jukuhullui wrote:

Oh and from where can I extract the HWID?

Check Bâshrat the Sneaky's sig.
Click the link, DL the tool, execute and post the contents of the .TXT file wink

Re: [SOLVED] SiI 3112r controller doesnt work: 0x7B BSOD

:-) Ok, thx for this advice Helmi - I was wondering all the time what his signature was meaning...

So here it is:

 
=========== 
PCI devices 
=========== 
 
 
PCI\A347SCSI\0000                                           : A347SCSI SCSI Controller
PCI\D347PRT\0000                                            : D347PRT SCSI Controller
PCI\VEN_1002&DEV_4150&SUBSYS_7C19174B&REV_00\4&102AC5BC&0&00F0: SAPPHIRE RADEON 9600 PRO ATLANTIS
PCI\VEN_1002&DEV_4170&SUBSYS_7C18174B&REV_00\4&102AC5BC&0&01F0: SAPPHIRE RADEON 9600 PRO ATLANTIS - Secondary
PCI\VEN_1095&DEV_3112&SUBSYS_61121095&REV_02\4&3B1D9AB8&0&5840: RAID-Controller
PCI\VEN_10B7&DEV_9201&SUBSYS_80AB1043&REV_40\4&35344E25&0&0860: 3Com 3C920B-EMB Integrated Fast Ethernet Controller
PCI\VEN_10DE&DEV_0060&SUBSYS_00000000&REV_A4\3&13C0B0C5&0&08: PCI Standard-ISA-Brücke
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 (v2.6)
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-Hostcontroller
PCI\VEN_10DE&DEV_0067&SUBSYS_0C111043&REV_A4\3&13C0B0C5&0&11: Standard OpenHCD USB-Hostcontroller
PCI\VEN_10DE&DEV_0068&SUBSYS_0C111043&REV_A4\3&13C0B0C5&0&12: Standard erweiterter PCI-zu-USB universeller Hostcontroller
PCI\VEN_10DE&DEV_006A&SUBSYS_80951043&REV_A1\3&13C0B0C5&0&30: NVIDIA(R) nForce(TM) Audio Codec Interface
PCI\VEN_10DE&DEV_006B&SUBSYS_0C111043&REV_A2\3&13C0B0C5&0&28: NVIDIA(R) nForce(TM) MCP Audio Processing Unit
PCI\VEN_10DE&DEV_006C&SUBSYS_00000000&REV_A3\3&13C0B0C5&0&40: PCI Standard-PCI-zu-PCI-Brücke
PCI\VEN_10DE&DEV_006D&SUBSYS_00000000&REV_A3\3&13C0B0C5&0&60: PCI Standard-PCI-zu-PCI-Brücke
PCI\VEN_10DE&DEV_006E&SUBSYS_809A1043&REV_A3\3&13C0B0C5&0&68: OHCI-konformer IEEE 1394-Hostcontroller
PCI\VEN_10DE&DEV_01E0&SUBSYS_00000000&REV_C1\3&13C0B0C5&0&00: PCI Standard-Host-CPU-Brücke
PCI\VEN_10DE&DEV_01E8&SUBSYS_00000000&REV_C1\3&13C0B0C5&0&F0: NVIDIA nForce2 AGP Host to PCI Bridge
PCI\VEN_10DE&DEV_01EB&SUBSYS_80AC1043&REV_C1\3&13C0B0C5&0&01: PCI-Speicher
PCI\VEN_10DE&DEV_01EC&SUBSYS_80AC1043&REV_C1\3&13C0B0C5&0&04: PCI-Speicher
PCI\VEN_10DE&DEV_01ED&SUBSYS_80AC1043&REV_C1\3&13C0B0C5&0&03: PCI-Speicher
PCI\VEN_10DE&DEV_01EE&SUBSYS_80AC1043&REV_C1\3&13C0B0C5&0&02: PCI-Speicher
PCI\VEN_10DE&DEV_01EF&SUBSYS_80AC1043&REV_C1\3&13C0B0C5&0&05: PCI-Speicher
PCI\VEN_14F1&DEV_8800&SUBSYS_34010070&REV_03\4&3B1D9AB8&0&4040: Hauppauge WinTV 88x Video (+IR)
PCI\VEN_14F1&DEV_8811&SUBSYS_34010070&REV_03\4&3B1D9AB8&0&4140: Hauppauge WinTV 88x IR Decoder
27 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_C03E\5&DF9F058&0&1                         : USB-HID (Human Interface Device)
4 matching device(s) found.

Last edited by Bâshrat the Sneaky (2006-08-13 22:38:30)

Re: [SOLVED] SiI 3112r controller doesnt work: 0x7B BSOD

Hope it´s not a too stupid question, but to verify which driver could work with my hardware, is it possible to do it faster than reinstall windows everytime with a new driver?
e.g.: all windows files are now on SATA disk to reboot to gui-mode of installation procedure. can I simply replace the 3112r.sys and all other drivers with the ones I want to test or is this impossible?

Re: [SOLVED] SiI 3112r controller doesnt work: 0x7B BSOD

Hm, don't quite understand what you're planing to do but to verify whether a driver supports your hardware, you can simply have a look at the .INF file.

The HWIDs exctracted with Bâshrat the Sneaky's tool should be listed in the .INF if it is supported.
If they aren't listed, no drivers will get installed for the hardware.

Granted, this may take some time if you do not know exactly which .INF file to look at, but ususally you can narrow it down if you know the hardware in question (ususally the case if it's your own system! wink), so you can directly look at a specific file.

HTH!