Re: [BUG] nVidia problems

1. DriverPack Chipset
-ALL Chipset drivers are put together, to support ALL hwids. The theory behind this is easy: although there may be newer versions of drivers for specific Chipsets, old hwids are STILL supported in the newer .inf files. That implies that the newer drivers do support the older devices, which may seem to NOT be supported officially through this drivers.
I've been using this approach for a very long time (at least more than a year) and so far it has always proved to be working.
-Note that the nVidia Ethernet and nVidia Audio drivers are included in DriverPack LAN and Sound, respectively.

2. DriverPack LAN
There are only problems with nForce 3 drivers, that share some hwids with nForce 4 ethernet devices and therefore get the wrong drivers installed, resulting in an unusable networking device, that cannot even be disabled anymore...

3. DriverPack MassStorage
-nVidia's mass storage device drivers have been bad since the nForce 2 days: the well-known IDE filter driver that caused so many problems. That got fixed. Then nForce 3 got released, and the drivers were good. nForce 4 showed up, bye bye unified drivers, hello problems. That would not have been a problem, if nVidia wouldn't have decided to MAKE it a problem. They're reusing the same hwids for incompatible devices. Pure misery.
-My policy is to always have the latest drivers. But above that, there is stability. If I can make everything work in an out-of-the-box way and thereby not be completely up-to-date, then I'll choose that path. But that hasn't been the case for the nVidia mass storage devices for a long time (it HAS been that way though).
-As many will agree, I've invested a LOT of time in trying to find THE best solution. But there isn't. I don't remember who found it, but there is someone who found that you could use the mass storage drivers for nForce 1/2/3 for nForce 4 too. Ever since, most installations do succeed, but SpaceCommanderTravis' installation did not, unfortunately.
-I have contacted nVidia several times, but of course I've never got a reply.

General conclusion
If someone can come up with a very reliable solution, I'll implement it. But I have already spent so much time on the nVidia issues that I can assure you that the problem does not lie in our methods, but in nVidia's. The very least they could do, is at least provide a guide how you could make ONE install disc for ALL nVidia platforms, in such a way that all drivers would be up-to-date. Since it's their fault they've made this mess. As far as my experience goes, this problem is not to be solved in a good, clean way. It can only be solved by applying hacks.

P.S.: kudos for hmaster10. If that method seems to be working, that'd be great. But can you imagine that ALL sysadmins would be prepared to do such an awful lot of efforts to get JUST ONE system installed? In that same time, you'd get many other systems installed, if they weren't using an nForce 3 or higher chipset.

Founder of DriverPacks.net — wimleers.com

Re: [BUG] nVidia problems

about nVidia mess, I just came up with this idea. I don't know how hard it'd be to implement it, so forgive me if this sounds like waste of time.

basically most problem lies with same HWID being shared by nf3 and nf4 solutions. (nf2 is fine right?)

then how about create two separate packs for nf3 and nf4, and integrate it to xp cd.

During install, if any one of those trouble HWID comes up, Setup prompts (like cmd window) for user input.   "Press 1 if you have nf3, press 2 if you have nf4.. etc)

User will input what setup they have, and the setup will call appropriate drivers.

Just my thoughts smile

Re: [BUG] nVidia problems

larciel wrote:

about nVidia mess, I just came up with this idea. I don't know how hard it'd be to implement it, so forgive me if this sounds like waste of time.

basically most problem lies with same HWID being shared by nf3 and nf4 solutions. (nf2 is fine right?)

then how about create two separate packs for nf3 and nf4, and integrate it to xp cd.

During install, if any one of those trouble HWID comes up, Setup prompts (like cmd window) for user input.   "Press 1 if you have nf3, press 2 if you have nf4.. etc)

User will input what setup they have, and the setup will call appropriate drivers.

Just my thoughts smile

That would completely void the concept of an unattended installation, and would be simply unacceptable for professional deployment. But I'm working on another idea that I got while I was typing the post above...

Founder of DriverPacks.net — wimleers.com

Re: [BUG] nVidia problems

hey, it's just one stroke of a key wink

anyways, hope this mess gets cleaned by nVidia soon

Re: [BUG] nVidia problems

larciel wrote:

hey, it's just one stroke of a key wink

anyways, hope this mess gets cleaned by nVidia soon

Don't hope for that wink

They promised unified drivers for their chipsets... there are now TWELVE chipset packages... how unified roll mad

Founder of DriverPacks.net — wimleers.com

Re: [BUG] nVidia problems

Tried to install on NVata today .....NO GO

i leave the masstorage out for now , back to press F6

Re: [BUG] nVidia problems

JHH wrote:

In the Media Shield user guide, it gives instructions for slipstreaming the sata-raid drivers into the CD.  The guide can be downloaded at this website

http://www.nvidia.com/object/feature_raid.html

The instructions start on page 150 of the guide.

Intresting

Re: [BUG] nVidia problems

muiz3 wrote:
JHH wrote:

In the Media Shield user guide, it gives instructions for slipstreaming the sata-raid drivers into the CD.  The guide can be downloaded at this website

http://www.nvidia.com/object/feature_raid.html

The instructions start on page 150 of the guide.

Intresting

Interesting indeed! They use the SATARAID driver, while I'm using the 'legacy' driver. This method has been working for a long time now, so I wonder why it no longer works...

Founder of DriverPacks.net — wimleers.com

Re: [BUG] nVidia problems

Hi Bâshrat the Sneaky, maybe you remember me from the MSFN forum. I used your pack a lot and think you are doing a great job! I tried to use your Driverpack (earlier versions) for my BartCD but it did not work for me. sad So I had to solve the problem with a other method...
Anyway, I had the same problems with the NVIDIA drivers and i know it is more pain than you actually could benefit from it.
My question is, did you finally found a solution for the nforce chipset and is your pack also working for the BartCD (I was very happy as I saw this option)?

Re: [BUG] nVidia problems

Any more news on that nVidia subject ? (DP 6.10 is marked as BSOD-able on all nVidia chipsets sad sad )

Re: [BUG] nVidia problems

I've found these two projects which packs nForce drivers :
1/ MEI's nWare Release 06.10
2/ nForce 11.10 Unified Remix

These drivers are not slipstream-able :-s ... however in MEI's post on page 2 it seems that the neverending BSOD is solved smile.

Last edited by maxximum (2007-01-03 02:10:57)

Re: [BUG] nVidia problems

To everyone with nforce:

There are currently indications that nforce problems have been solved in the latest DP base + DP masstorage final.
A specific driver of which we found out it conflicted with the silicon drivers was removed in the latest DP masstorage. It could very well have been that this driver conflicted with nforce aswell.

Can everbody please test this, and report the results back in this topic?

Last edited by ruudboek (2007-01-20 22:39:31)

Re: [BUG] nVidia problems

I slipstreamed the newest driver packs (including Mass Storage textmode) using method 2.  Installing on an ASUS A8N-VM CSM with nForce 430 chipset with two 80GB SATA HDD's in a RAID 1, the Windows install didn't recoginize the RAID controller.  So, I had to install using F6.  So I can confirm that something is wrong with the textmode, and nForce raid...

Here is some interesting reading from nVidia's website on installing the RAID drivers from a floppy using the good ole F6 method :-)

When OS reads the floppy it will show the following:
    NVIDIA RAID CLASS DRIVER (required)
    NVIDIA nForce storage Controller (required)

Both of thes MUST be installed if RAID is enabled on the installation port.

Maybe this has somethig to do with the problem...  Dunno, I've been sliptreaming XP CD's for a few years, but just started using DriverPacks.

KevRo

Re: [BUG] nVidia problems

ruudboek wrote:

To everyone with nforce:

There are currently indications that nforce problems have been solved in the latest DP base + DP masstorage final.
A specific driver of which we found out it conflicted with the silicon drivers was removed in the latest DP masstorage. It could very well have been that this driver conflicted with nforce aswell.

Can everbody please test this, and report the results back in this topic?

Asus A8n SLi Deluxe.  (nForce 4 chipset).

I can report a successful installation using Win XP Pro, slipstreamed SP2, RVM Update pack (but no additional addons yet),  v7.015 Driverpacks Base, and all official driverpacks at today's date, including Chipset v6.12, Graphics A v7.01, LAN v7.01 & MassStorage v7.01.1.1, including Mass Storage Text mode, using Method 2 and KTD.

In line with the earlier workaround, I turned on the NV Raid controller in the BIOS before starting, and left RAID disabled on all the drives, but left the SIL 3114 one turned off (since I don't use that).  I also had only one drive connected for this test (to NV SATA port 3).

Unlike the earlier workaround, I left the NVRaid controller enabled all the way through the install, and didn't get any blue screens.

I also disconnected all the USB and Firewire hardware before starting the installation, but these all re-connected successfully once I was into the desktop.

Last edited by SpaceCommanderTravis (2007-01-29 03:50:20)

Asus A8nSLi Deluxe;  AMD 64 3700 CPU, Asus EN 6600 GT, 2x Spinpoint 250Gb drives on NV SATA II connection, WDC 250GB & WDC 120GB drive on IDE, 2x LG GSA 4167 DVD RAM drives.

Re: [BUG] nVidia problems

I'm still not sure that I'm getting the best driver versions though.

For example, the nVidia nForce Parallel ATA controller lists it's driver version as 5.10.2600.518, and looking through the nForce4 driver package archive at http://www.nvidia.com/object/nforce_nf4_archive.html, this driver appears under v6.53 bundle from 17th March 2005 "IDE NVIDIA driver 5.18 (WHQL)".

According to the Asus support website, I need to use Driver package v6.66 or later with BIOS v 1012 onwards (and I have v1016) to avoid crashing the disc filing system.  I don't think this is affecting me at the moment, because I only have one hard drive connected up to the NV SATA port 3, but this makes me nervous about reconnecting the Hard drives on the Parallel ATA connection.

There is another IDE driver listed under driver package v6.70, which is "IDE driver version 5.52 (WHQL)", so surely this one should be used instead of v5.18?

So, to try to work out what is happening behind the scenes, if

- the Bâshrat the Sneaky Chipset DriverPack v6.12 includes v6.86 of nVidia's driver bundle for nForce 4 AMD motherboards, but
- NVidia's driver bundle does not include the IDE driver for the Parallel ATA interface,

does this mean that the installation process is instead choosing the v5.18 driver that the supported devices page for the MassStorage Controller DriverPack v7.01.1 indicates is intended for the Nforce 1/2/3 packages, since this is a driver version that is also listed by Nvidia as compatible with my Motherboard?

On a related note, is there any way to check whether or not the nVidia Driver Package v6.86, includes the same "IDE driver version 5.52 (WHQL)" that is in Driver Package v6.70.  And if not, would this require both the v6.70 and v6.86 driver bundles to be included in the Chipset Package?  Or at least for the v5.52 (PATA) IDE driver from the v6.70 driver bundle to be included in the Mass Storage Driverpack?

PS.  After previewing this, I realised that I'd been going on a bit here, so I've cut out a section from the middle of 'interim' observations.  If anyone would be interested in the extra detail, let me know.

Last edited by SpaceCommanderTravis (2007-01-29 05:41:47)

Asus A8nSLi Deluxe;  AMD 64 3700 CPU, Asus EN 6600 GT, 2x Spinpoint 250Gb drives on NV SATA II connection, WDC 250GB & WDC 120GB drive on IDE, 2x LG GSA 4167 DVD RAM drives.

Re: [BUG] nVidia problems

I've tried another installation with both the NVRaid and the Sil3114 Raid controllers turned on, and this also went without a hitch.  As before I only had one drive connected, so there wasn't any RAID array running.

Today, I've run a third installation with both the RAID controllers turned off, and this also went without any problem.

But to answer my own question about the nVidia Driver packages not including the drivers from the previous packages, I downloaded the driver bundles from nVidia's website and tried a series of installations.

For the second installation with both the RAID controllers turned on, I tried the installations in order of the version numbers.  The Bâshrat the Sneaky driverpacks had again installed v5.18 on the PATA IDE interface, and the correct v6.66 driver on the SATA IDE interfaces.

As I had expected, the PATA IDE interface driver got updated to v5.34 with the nVidia Driver bundle v6.66, but didn't change again for the v6.70 & v6.86 driver bundles.

Today, I deleted that partition and ran another installation from the same DVD, but this time installed the nVidia Driver bundles in reverse.  v6.86 & v6.70 didn't make any change to the v5.18 driver that had been installed to the PATA IDE interface.  This only changed up to the correct v5.34 driver with the nVidia Driver bundle v6.66.

So in conclusion, I'm happy that the Update Pack and Driver packs slipstreamed into my Windows XP installation disc now runs correctly for the A8n SLi Deluxe motherboard without any BSODs, but since each new driver bundle doesn't seem to include all of the drivers from the previous driver bundles that aren't updated, I don't think it is enough to replace an old driver bundle with the newer one within the DriverPacks.

I've not yet investigated whether other drivers are affected by the same problem, because I've focussed on the drivers for the hard drive controllers due to the risk of data corruption.

I've seen from earlier posts that there have been problems with nVidia sharing HWIDs across different hardware?  Would this cause problems in using drivers from previous driver bundles within the Driverpacks?  Or is this something that I'm going to have to try to customise into my own 3rd party driverpack?

I would think that if this is an nVidia Driverbundle problem that there would be a reasonable call to do this if it didn't cause other problems.

Asus A8nSLi Deluxe;  AMD 64 3700 CPU, Asus EN 6600 GT, 2x Spinpoint 250Gb drives on NV SATA II connection, WDC 250GB & WDC 120GB drive on IDE, 2x LG GSA 4167 DVD RAM drives.

Re: [BUG] nVidia problems

DP_MassStorage_wnt5_x86-32_804.7z?ASUS Z99NSeries???XP??(Chipset:nVidia 610m/MCP67 SATA Controller)
DP_MassStorage_wnt5_x86-32_8021.7z???.
(iCiba.com translate:)
DP_MassStorage_wnt5_x86-32_804.7z in ASUS Z99NSeries XP installed on-screen (Chipset: nVidia 610m/MCP67 SATA Controller)
DP_MassStorage_wnt5_x86-32_8021.7z no error.

Last edited by hirchen (2008-04-27 14:08:04)

Re: [BUG] nVidia problems

have problems with DP_MassStorage_wnt5_x86-32_804 or DP_Chipset_wnt5_x86-32_803 on ASUS M2N-VM DVI Motherboard.
With the previouse version everything was ok. But now BSOD 0x0000007B

And problem on ASUS M2N-Sli: No Hard drive found!
very strange.

Re: [BUG] nVidia problems

BSOD in Windows setup process on the notebook Acer 5520 (nvidia chipset)- DP_MassStorage_wnt5_x86-32_80X! On the version 8021 - VERY GOOD!

Worked on Windows 8.1 Pro

Re: [BUG] nVidia problems

Hwid ?

Re: [BUG] nVidia problems

BSOD in text mode just before the installation disks for the installation of choice (804f):

*** STOP: 0x0000007B(0xF7BA3524, 0xC0000034, 0x00000000,0x00000000)

===========
PCI Devices
===========
PCI\VEN_1022&DEV_1100&SUBSYS_00000000&REV_00\3&267A616A&0&C0: PCI\VEN_1022&DEV_1101&SUBSYS_00000000&REV_00\3&267A616A&0&C1: PCI\VEN_1022&DEV_1102&SUBSYS_00000000&REV_00\3&267A616A&0&C2: PCI\VEN_1022&DEV_1103&SUBSYS_00000000&REV_00\3&267A616A&0&C3: PCI\VEN_10DE&DEV_053E&SUBSYS_83081043&REV_A2\3&267A616A&0&90: NVIDIA GeForce 7025 / NVIDIA nForce 630a
PCI\VEN_10DE&DEV_0542&SUBSYS_83081043&REV_A2\3&267A616A&0&09: NVIDIA nForce PCI System Management
PCI\VEN_10DE&DEV_0547&SUBSYS_83081043&REV_A2\3&267A616A&0&00: PCI\VEN_10DE&DEV_0548&SUBSYS_00000000&REV_A2\3&267A616A&0&08: PCI\VEN_10DE&DEV_054C&SUBSYS_83081043&REV_A2\3&267A616A&0&50: NVIDIA Network Bus Enumerator
PCI\VEN_10DE&DEV_0550&SUBSYS_83081043&REV_A2\3&267A616A&0&48: PCI\VEN_10DE&DEV_055C&SUBSYS_82EA1043&REV_A1\3&267A616A&0&38: PCI\VEN_10DE&DEV_055E&SUBSYS_83081043&REV_A2\3&267A616A&0&10: PCI\VEN_10DE&DEV_055E&SUBSYS_83081043&REV_A2\3&267A616A&0&20: PCI\VEN_10DE&DEV_055F&SUBSYS_83081043&REV_A2\3&267A616A&0&11: PCI\VEN_10DE&DEV_055F&SUBSYS_83081043&REV_A2\3&267A616A&0&21: PCI\VEN_10DE&DEV_0560&SUBSYS_83081043&REV_A1\3&267A616A&0&30: PCI\VEN_10DE&DEV_0561&SUBSYS_00000000&REV_A2\3&267A616A&0&40: PCI\VEN_10DE&DEV_0562&SUBSYS_00000000&REV_A2\3&267A616A&0&58: PCI\VEN_10DE&DEV_0563&SUBSYS_00000000&REV_A2\3&267A616A&0&60: PCI\VEN_10DE&DEV_0563&SUBSYS_00000000&REV_A2\3&267A616A&0&68: PCI\VEN_10DE&DEV_0563&SUBSYS_00000000&REV_A2\3&267A616A&0&70: PCI\VEN_10DE&DEV_0563&SUBSYS_00000000&REV_A2\3&267A616A&0&78: PCI\VEN_10DE&DEV_0563&SUBSYS_00000000&REV_A2\3&267A616A&0&80: PCI\VEN_10DE&DEV_0563&SUBSYS_00000000&REV_A2\3&267A616A&0&88: 24 matching device(s) found.

===========
USB Devices
===========
USB\ROOT_HUB\4&630CC7&0 : USB\ROOT_HUB\4&F2BA159&0 : USB\ROOT_HUB20\4&150C3BAC&0 : USB\ROOT_HUB20\4&2894B81F&0 : USB\VID_069B&PID_0704\001E690105A7 : RCA USB Cable Modem
5 matching device(s) found.

=============
Input Devices
=============
No matching devices found.

============
ACPI Devices
============
ACPI\ATK0110\1010110 : ATK0110 ACPI UTILITY
ACPI\AUTHENTICAMD_-_X86_FAMILY_15_MODEL_107\_0 : AMD Athlon(tm) 64 X2 Dual Core Processor 4000+
ACPI\AUTHENTICAMD_-_X86_FAMILY_15_MODEL_107\_1 : AMD Athlon(tm) 64 X2 Dual Core Processor 4000+
ACPI\FIXEDBUTTON\2&DABA3FF&0 : ACPI\PNP0000\4&3AB42574&0 : ACPI\PNP0100\4&3AB42574&0 : ACPI\PNP0103\0 : ACPI\PNP0200\4&3AB42574&0 : ACPI\PNP0303\4&3AB42574&0 : ACPI\PNP0400\4&3AB42574&0 : ACPI\PNP0501\1 : ACPI\PNP0700\4&3AB42574&0 : ACPI\PNP0800\4&3AB42574&0 : ACPI\PNP0A03\0 : ACPI\PNP0B00\4&3AB42574&0 : CMOS ACPI\PNP0C01\1 : ACPI\PNP0C02\0 : ACPI\PNP0C02\10 : ACPI\PNP0C02\11 : ACPI\PNP0C02\2E : ACPI\PNP0C04\4&3AB42574&0 : ACPI\PNP0C0C\AA : ACPI\PNP0C14\NVIF : ACPI\PNP0F03\4&3AB42574&0 : Microsoft PS/2 ACPI_HAL\PNP0C08\0 : Microsoft ACPI-ROOT\ACPI_HAL\0000 : 26 matching device(s) found.

This is PC:
Athlon X2 4800+
2 Gb 800Mhz Dual
Asus m2n-vm dvi nvidia geforce7050/nf630a

and the same BSOD on the Asus m2n-cm dvi nvidia geforce7025/nf630a  (*** STOP: 0*0000007B (0*F78DE524, O*C0000034, 0*00000000, 0*00000000))

Last edited by SamLab (2008-05-10 20:00:07)

Worked on Windows 8.1 Pro

Re: [BUG] nVidia problems

no BSOD, but in text mode just before the installation disks for the installation of choice (804f) - black screen:

MSI P35 Neo (MS-7360)
Intel Pentium 4 631, 3000 MHz
2Gb DDR2-800 (400 ???)
NVIDIA GeForce 7600 GT (256 ??)
Realtek ALC888/S/T @ Intel 82801IB ICH9 - High Definition Audio Controller
Realtek RTL8168/8111 PCI-E Gigabit Ethernet NIC
Silicon Image SiI 0680 ATA/133 Controller
ST3500320NS (500 ??, 7200 RPM, SATA-II)
WDC WD2500JS-58NCB1 SATA-II (250 ??) - 2 ??.
Optiarc DVD RW AD-7203S (SATA)
Optiarc DVD RW AD-7173A (IDE)
FDD 3,5" MATSHITA LS-120 (IDE)
Samsung SyncMaster 940B/Fn/T (Digital) [19" LCD]

===========
PCI Devices
===========
PCI\VEN_1095&DEV_0680&SUBSYS_06801095&REV_02\4&19ABE7DE&0&08F0: Silicon Image SiI 0680 ATA/133 Controller
PCI\VEN_10DE&DEV_0391&SUBSYS_00000000&REV_A1\4&196AFE53&0&0008: NVIDIA GeForce 7600 GT
PCI\VEN_10EC&DEV_8168&SUBSYS_360C1462&REV_01\4&625283&0&00E5: Realtek RTL8168/8111 PCI-E Gigabit Ethernet NIC
PCI\VEN_11AB&DEV_6121&SUBSYS_612111AB&REV_B2\4&332B0EE8&0&00E4: Marvell 61xx RAID Controller
PCI\VEN_14F1&DEV_8880&SUBSYS_23895654&REV_0F\4&279E7BDF&0&00E2: GOTVIEW X5 DVD HYBRID PCI-E
PCI\VEN_8086&DEV_244E&SUBSYS_00000000&REV_92\3&11583659&0&F0: Intel(R) 82801 PCI Bridge - 244E
PCI\VEN_8086&DEV_2918&SUBSYS_00000000&REV_02\3&11583659&0&F8: Intel(R) ICH9 LPC Interface Controller - 2918
PCI\VEN_8086&DEV_2921&SUBSYS_73601462&REV_02\3&11583659&0&FA: Intel(R) ICH9 2 port Serial ATA Storage Controller 1 - 2921
PCI\VEN_8086&DEV_2926&SUBSYS_73601462&REV_02\3&11583659&0&FD: Intel(R) ICH9 2 port Serial ATA Storage Controller 2 - 2926
PCI\VEN_8086&DEV_2930&SUBSYS_73601462&REV_02\3&11583659&0&FB: Intel(R) ICH9 Family SMBus Controller - 2930
PCI\VEN_8086&DEV_2934&SUBSYS_73601462&REV_02\3&11583659&0&E8: Intel(R) ICH9 Family USB Universal Host Controller - 2934
PCI\VEN_8086&DEV_2935&SUBSYS_73601462&REV_02\3&11583659&0&E9: Intel(R) ICH9 Family USB Universal Host Controller - 2935
PCI\VEN_8086&DEV_2936&SUBSYS_73601462&REV_02\3&11583659&0&EA: Intel(R) ICH9 Family USB Universal Host Controller - 2936
PCI\VEN_8086&DEV_2937&SUBSYS_73601462&REV_02\3&11583659&0&D0: Intel(R) ICH9 Family USB Universal Host Controller - 2937
PCI\VEN_8086&DEV_2938&SUBSYS_73601462&REV_02\3&11583659&0&D1: Intel(R) ICH9 Family USB Universal Host Controller - 2938
PCI\VEN_8086&DEV_2939&SUBSYS_73601462&REV_02\3&11583659&0&EB: Intel(R) ICH9 Family USB Universal Host Controller - 2939
PCI\VEN_8086&DEV_293A&SUBSYS_73601462&REV_02\3&11583659&0&EF: Intel(R) ICH9 Family USB2 Enhanced Host Controller - 293A
PCI\VEN_8086&DEV_293C&SUBSYS_73601462&REV_02\3&11583659&0&D7: Intel(R) ICH9 Family USB2 Enhanced Host Controller - 293C
PCI\VEN_8086&DEV_293E&SUBSYS_73601462&REV_02\3&11583659&0&D8: PCI\VEN_8086&DEV_2940&SUBSYS_00000000&REV_02\3&11583659&0&E0: Intel(R) ICH9 Family PCI Express Root Port 1 - 2940
PCI\VEN_8086&DEV_2944&SUBSYS_00000000&REV_02\3&11583659&0&E2: Intel(R) ICH9 Family PCI Express Root Port 3 - 2944
PCI\VEN_8086&DEV_2948&SUBSYS_00000000&REV_02\3&11583659&0&E4: Intel(R) ICH9 Family PCI Express Root Port 5 - 2948
PCI\VEN_8086&DEV_294A&SUBSYS_00000000&REV_02\3&11583659&0&E5: Intel(R) ICH9 Family PCI Express Root Port 6 - 294A
PCI\VEN_8086&DEV_29C0&SUBSYS_00000000&REV_02\3&11583659&0&00: Intel(R) G33/G31/P35 Express Chipset Processor to I/O Controller - 29C0
PCI\VEN_8086&DEV_29C1&SUBSYS_00000000&REV_02\3&11583659&0&08: Intel(R) G33/G31/P35 Express Chipset PCI Express Root Port - 29C1
25 matching device(s) found.

===========
USB Devices
===========
USB\ROOT_HUB\4&1A21ADE8&0 : USB\ROOT_HUB\4&1E2A8EC6&0 : USB\ROOT_HUB\4&2032DE6F&0 : USB\ROOT_HUB\4&35A226E2&0 : USB\ROOT_HUB\4&36BC277E&0 : USB\ROOT_HUB\4&4B26575&0 : USB\ROOT_HUB20\4&EB16559&0 : USB\ROOT_HUB20\4&F586E5B&0 : USB\VID_0403&PID_6006\T2682281 : FTDI FT8U2XX Device
USB\VID_0458&PID_5003\5&1B222465&0&1 : USB HID-USB\VID_058F&PID_9254\5&16E02094&0&2 : USB\VID_0B38&PID_0003\6&8796CA9&0&1 : USB\VID_0B38&PID_0003&MI_00\7&3A545B2E&0&0000 : USB HID-USB\VID_0B38&PID_0003&MI_01\7&3A545B2E&0&0001 : USB HID-14 matching device(s) found.

=============
Input Devices
=============
HID\VID_0458&PID_5003&COL01\6&30BCB20A&0&0000 : HID-HID\VID_0458&PID_5003&COL02\6&30BCB20A&0&0001 : HID-HID\VID_0B38&PID_0003&MI_00\8&5D1C653&0&0000 : HID\VID_0B38&PID_0003&MI_01&COL01\8&23869DD6&0&0000 : HID-HID\VID_0B38&PID_0003&MI_01&COL02\8&23869DD6&0&0001 : HID-HID\VID_0B38&PID_0003&MI_01&COL03\8&23869DD6&0&0002 : HID-HID\VID_0B38&PID_0003&MI_01&COL04\8&23869DD6&0&0003 : HID-HID\VID_0B38&PID_0003&MI_01&COL05\8&23869DD6&0&0004 : HID-8 matching device(s) found.

============
ACPI Devices
============
ACPI\FIXEDBUTTON\2&DABA3FF&0 : ACPI\GENUINEINTEL_-_X86_FAMILY_15_MODEL_6\_0 : Intel(R) Pentium(R) 4 CPU 3.00GHz
ACPI\GENUINEINTEL_-_X86_FAMILY_15_MODEL_6\_1 : Intel(R) Pentium(R) 4 CPU 3.00GHz
ACPI\INT0800\4&1400782C&0 : Intel(R) 82802 Firmware ACPI\PNP0000\4&1400782C&0 : ACPI\PNP0100\4&1400782C&0 : ACPI\PNP0200\4&1400782C&0 : ACPI\PNP0501\1 : ACPI\PNP0800\4&1400782C&0 : ACPI\PNP0A08\0 : ACPI\PNP0B00\4&1400782C&0 : CMOS ACPI\PNP0C01\1 : ACPI\PNP0C01\A : ACPI\PNP0C02\0 : ACPI\PNP0C02\10 : ACPI\PNP0C02\11 : ACPI\PNP0C02\3 : ACPI\PNP0C02\4E : ACPI\PNP0C04\4&1400782C&0 : ACPI\PNP0C0C\AA : ACPI\PNP0F03\4&1400782C&0 : Microsoft PS/2 ACPI_HAL\PNP0C08\0 : Microsoft ACPI-ROOT\ACPI_HAL\0000 : 23 matching device(s) found.

Last edited by SamLab (2008-05-11 03:57:45)

Worked on Windows 8.1 Pro

Re: [BUG] nVidia problems

DP_MassStorage_wnt5_x86-32_805.7z tested on Acer Aspire 5520, MCP67M chipset. BSOD has gone. No more problems.

Re: [BUG] nVidia problems

thanks busel..
we could not sit and wait for intel's official release of a file we had in a testpack.
We had testpacks running since 804... these testpacks had a pre-release intel inside but also included the anounced NVidia update and other file updates and fixes.

So, because the fixes were important enough, and tested, the DriverPack MassStorage 805 release was done without the still unofficial intel update.

Last edited by Jaak (2008-06-02 06:57:29)

The answer was 42?
Kind regards, Jaak.

Re: [BUG] nVidia problems

Wow, DP_MassStorage_wnt5_x86-32_806A Released! Whats important new in this veryquickly build after 8.05?

Worked on Windows 8.1 Pro