Thanks! I'll test and update if needed.
1 2012-07-11 07:40:28
Re: Latest DPMS fails with older Nvidia chipset and HDDs (7 replies, posted in DriverPack Mass Storage)
2 2012-07-11 05:05:55
Re: Latest DPMS fails with older Nvidia chipset and HDDs (7 replies, posted in DriverPack Mass Storage)
I did some further troubleshooting, and the responsible of the installation failure was not the Chipset DP but the MassStorage DP (not the text mode part - I just deleted the DPM1206.7z file from the OEM folder and it installed successfully).
* On the text mode part, the controller is listed as "nvlegacy [MBR]"
* The exact BSOD is as follows:
STOP: 0x0000007B (0xB84C3524, 0xC0000034, 0x00000000, 0x00000000)
* I also have the installation logs from the failed attempt (did not boot in safe mode, but I plugged the drive onto a working PC). The section from setupapi.log relevant to the SATA controller is the following (the log is in Spanish, but you should be able to figure it out). Anyway, I am not sure if this is still relevant since the responsible was not the Chipset DP.
#-166 Función de instalación de dispositivo: DIF_INSTALLDEVICE.
#I123 Realizando instalación completa de "PCI\VEN_10DE&DEV_03F6&SUBSYS_54051565&REV_A2\3&267A616A&0&40".
#W100 La retirada de la petición durante la instalación de "PCI\VEN_10DE&DEV_03F6&SUBSYS_54051565&REV_A2\3&267A616A&0&40" fue vetada por "IDE\DiskST500DM002-1BD142_______________________KC45____\202020202020202020202020325A53413838444C" (tipo de veto 6 PNP_VetoDevice)
#W104 El dispositivo "PCI\VEN_10DE&DEV_03F6&SUBSYS_54051565&REV_A2\3&267A616A&0&40" necesita reiniciarse: error al eliminar consulta (instalar) CfgMgr32 devuelto: 0x17. CR_REMOVE_VETOED
#I121 La instalación del dispositivo de "PCI\VEN_10DE&DEV_03F6&SUBSYS_54051565&REV_A2\3&267A616A&0&40" terminó correctamente.
[2012/07/10 20:54:47 776.1692 Driver Install]
#-019 Buscando Id. de hardware: pci\ven_10de&dev_03f6&subsys_54051565&rev_a2,pci\ven_10de&dev_03f6&subsys_54051565,pci\ven_10de&dev_03f6&cc_010185,pci\ven_10de&dev_03f6&cc_0101
#-018 Buscando Id. compatibles: pci\ven_10de&dev_03f6&rev_a2,pci\ven_10de&dev_03f6,pci\ven_10de&cc_010185,pci\ven_10de&cc_0101,pci\ven_10de,pci\cc_010185,pci\cc_0101
#-198 Línea de comando procesada: "C:\WINDOWS\system32\setup.exe" -newsetup
#I022 Encontrado "PCI\VEN_10DE&DEV_03F6&CC_0101" en C:\WINDOWS\Inf\oem6.inf; Dispositivo: "NVIDIA nForce Serial ATA Controller"; Controlador: "NVIDIA nForce Serial ATA Controller"; Proveedor: "NVIDIA Corporation"; Fab: "NVIDIA Corporation"; Nombre de sección:"NVStor_Inst".
#I023 Sección de instalación actual: [NVStor_Inst.NTx86]. Rango: 0x00000003. Fecha de controlador efectiva: 04/09/2010.
#I393 Modificando la caché de INF "C:\WINDOWS\Inf\INFCACHE.1".
#I022 Encontrado "PCI\CC_0101" en C:\WINDOWS\Inf\mshdc.inf; Dispositivo: "Controladora estándar PCI IDE de doble canal"; Controlador: "Controladora estándar PCI IDE de doble canal"; Proveedor: "Microsoft"; Fab: "(Tarjetas controladoras estándar IDE ATA/ATAPI)"; Nombre de sección:"pciide_Inst".
#I023 Sección de instalación actual: [pciide_Inst]. Rango: 0x00003006. Fecha de controlador efectiva: 07/01/2001.
#I022 Encontrado "PCI\VEN_10DE&DEV_03F6&CC_0101" en C:\D\M\N\nvatabus.inf; Dispositivo: "NVIDIA MCP61 Serial ATA Controller"; Controlador: "NVIDIA MCP61 Serial ATA Controller"; Proveedor: "NVIDIA Corporation"; Fab: "NVIDIA Corporation"; Nombre de sección:"Crush11_Inst".
#I087 El nodo del controlador no es de confianza. Intervalo cambiado desde 0x00000003 a 0x00008003.
#I023 Sección de instalación actual: [Crush11_Inst.NTx86]. Rango: 0x00008003. Fecha de controlador efectiva: 04/24/2006.
#I022 Encontrado "PCI\VEN_10DE&DEV_03F6&CC_0101" en C:\D\M\N6\nvgts.inf; Dispositivo: "NVIDIA nForce Serial ATA Controller"; Controlador: "NVIDIA nForce Serial ATA Controller"; Proveedor: "NVIDIA Corporation"; Fab: "NVIDIA Corporation"; Nombre de sección:"NVStor_Inst".
#I023 Sección de instalación actual: [NVStor_Inst.NTx86]. Rango: 0x00000003. Fecha de controlador efectiva: 11/12/2008.
#I022 Encontrado "PCI\VEN_10DE&DEV_03F6&CC_0101" en C:\D\M\N7\nvgts.inf; Dispositivo: "NVIDIA nForce Serial ATA Controller"; Controlador: "NVIDIA nForce Serial ATA Controller"; Proveedor: "NVIDIA Corporation"; Fab: "NVIDIA Corporation"; Nombre de sección:"NVStor_Inst".
#I023 Sección de instalación actual: [NVStor_Inst.NTx86]. Rango: 0x00000003. Fecha de controlador efectiva: 04/09/2010.
#-147 Cargar el módulo de instalación de clase para "Controladora IDE".
#E360 Se instalará el archivo no asignado o firmado incorrectamente "C:\WINDOWS\system32\SysSetup.Dll" para el controlador "Controladora IDE" (directiva=omitir). Error 0x800b0100: No hay ninguna firma presente en el asunto.
#-148 Carga del módulo coinstalador para "Controladora IDE".
#E360 Se instalará el archivo no asignado o firmado incorrectamente "C:\WINDOWS\system32\SysSetup.Dll" para el controlador "Controladora IDE" (directiva=omitir). Error 0x800b0100: No hay ninguna firma presente en el asunto.
#-166 Función de instalación de dispositivo: DIF_SELECTBESTCOMPATDRV.
#I063 El controlador seleccionado se instala desde la sección [NVStor_Inst] in "c:\windows\inf\oem6.inf".
#I320 El GUID de clase del dispositivo se conservará como {4D36E96A-E325-11CE-BFC1-08002BE10318}.
#I060 Se ha establecido el controlador seleccionado.
#I058 Se ha seleccionado el mejor controlador compatible.
#-124 Realizando instalación sólo de copia de "PCI\VEN_10DE&DEV_03F6&SUBSYS_54051565&REV_A2\3&267A616A&0&41".
#-166 Función de instalación de dispositivo: DIF_REGISTER_COINSTALLERS.
#I056 Coinstaladores registrados.
#-148 Carga del módulo coinstalador para "NVIDIA nForce Serial ATA Controller".
#E360 Se instalará el archivo no asignado o firmado incorrectamente "C:\WINDOWS\system32\SysSetup.Dll" para el controlador "NVIDIA nForce Serial ATA Controller" (directiva=omitir). Error 0x800b0100: No hay ninguna firma presente en el asunto.
#-166 Función de instalación de dispositivo: DIF_INSTALLINTERFACES.
#-011 Instalando sección [NVStor_Inst.NTx86.Interfaces] desde "c:\windows\inf\oem6.inf".
#I054 Se han instalado las interfaces.
#-166 Función de instalación de dispositivo: DIF_INSTALLDEVICE.
#I123 Realizando instalación completa de "PCI\VEN_10DE&DEV_03F6&SUBSYS_54051565&REV_A2\3&267A616A&0&41".
#I121 La instalación del dispositivo de "PCI\VEN_10DE&DEV_03F6&SUBSYS_54051565&REV_A2\3&267A616A&0&41" terminó correctamente.Please tell me if any additional information is needed!
Thanks!
Cheers!
3 2012-07-09 05:13:11
Re: Latest DPMS fails with older Nvidia chipset and HDDs (7 replies, posted in DriverPack Mass Storage)
Well, I tried that. If I attach the new drive to an XP running machine with nvidia chipset (installed with DriverPacks, I have all the PCs around me installed with DriverPacks!!), the disk is recognized in Device Manager, but not in Disk Management. Furthermore, testdisk for example (the "rawest" thing to deal to deal with HDDs that I know) reports the disk as being 2 TB (when actually it is 500 GB).
Anyway, I found a W7 machine with some Intel-whatever chipset, on which it was recognized fine. I formatted to a single volume, and ran the installation on it on the nvidia MB, but failed the same way 
The point is that the text-mode part of the installation properly recognizes and handles the drive, formats it, and installs everything. The BSOD comes after the installation finishes (and the Windows mode driver is installed).
Running the installation without the Chipset DP succeeds. Manually installing the latest nvidia drivers afterwards does not generare any issues as well. That's why I believe the problem here is the SATA controller driver not liking the disks (which BTW, I don't yet understand what's the deal with these 4K drives, since this one is *only* 500 GB)
I know it is very strange, it took me quite a while to realize what was going on.
To be sincere, I am not that handy at troubleshooting drivers at the moment (your fault, DP has been a tough cookie! Had worked flawlessly on every-single-PC I ran it on ;D ), anyway I'll try to track down which the specific driver that is causing the issue.
Any help is appreciated!
Cheers!
4 2012-07-07 10:17:08
Topic: Latest DPMS fails with older Nvidia chipset and HDDs (7 replies, posted in DriverPack Mass Storage)
Hi! I have a WinXP PXE unattended installation running over Linux, and has been working flawlessly for months. I had also included pretty every DriverPack on it and so far has been rock solid...
Until today, when I got some of the latest HDD Seagate Barracuda 500GB ST500DM002, and tried to run the usual installation over it, but failed. BSOD 0x7B (UNMOUNTABLE BOOT VOLUME) after the installation was completed (on the system first real start).
At first I thought the HDD was defective, but 2 of the same model failed the same way on the same mobo. Some further troubleshooting indicated that the SATA driver included in the DriverPack for some reason does not like these disks. The motherboard we are talking about is a Biostar N68S3+ (NVIDIA MCP68S)
I installed WinXP on this machine onto another WD disk, it worked fine. Hooked up the new disk, it was recognized on the Device Manager, but not in Disk Management. Some Seagate tools and testdisk reported the disk as being 2 TB (WTF!). After that, I updated the nForce drivers with the latest ones from the nVidia website, and the disk was recognized properly.
Then, I removed the Chipset DriverPack from the installation source and ran it again over the Seagate disk, it succeded without BSOD.
The issue occurs, at least, with versions 11.09 and 12.06 (latest) of the DriverPack.
I will be glad to provide more information on request, as well as to try anything relevant to get it solved.
Thanks!