Topic: [Help me] BSOD 7b with Chipset Driverpack on Nvidia hardware

I'm using the chipset Driverpack "DP_Chipset_wnt5_x86-32_909r4.7z" and I get a BSOD on startup.  I'm not using any other driverpacks with the chipset driverpack.  The BSOD is STOP 0x0000007b (0xf78ca528, 0xc0000034, 0x00000000, 0x00000000)  I have tried the latest nightly chipset "DP_Chipset_wnt5_x86-32_909r4.7z" and it fails too.  If I don't use any Driverpacks, Windows will boot fine with no BSOD on startup.

Here are my HWid's

PCI Devices 
PCI\VEN_10DE&DEV_0AA3&SUBSYS_3651103C&REV_B1\3&2411E6FE&2&1D: NVIDIA nForce System Management Controller
PCI\VEN_10DE&DEV_0AB0&SUBSYS_3651103C&REV_B1\3&2411E6FE&2&50: NVIDIA nForce 10/100 Mbps Ethernet 
PCI\VEN_10DE&DEV_0AA4&SUBSYS_3651103C&REV_B1\3&2411E6FE&2&19: PCI standard RAM Controller
PCI\VEN_10DE&DEV_0AB9&SUBSYS_3651103C&REV_B1\3&2411E6FE&2&58: NVIDIA nForce Serial ATA Controller
PCI\VEN_10DE&DEV_0876&SUBSYS_3651103C&REV_B1\4&31496BF&0&0080: NVIDIA ION
PCI\VEN_10DE&DEV_0AA5&SUBSYS_3651103C&REV_B1\3&2411E6FE&2&20: Standard OpenHCD USB Host Controller
PCI\VEN_10DE&DEV_0AC0&SUBSYS_3651103C&REV_B1\3&2411E6FE&2&40: High Definition Audio Controller
PCI\VEN_10DE&DEV_0A82&SUBSYS_3651103C&REV_B1\3&2411E6FE&2&00: PCI standard host CPU bridge
PCI\VEN_10DE&DEV_0AA6&SUBSYS_3651103C&REV_B1\3&2411E6FE&2&21: Standard Enhanced PCI to USB Host Controller
PCI\VEN_10DE&DEV_0AC6&SUBSYS_3651103C&REV_B1\3&2411E6FE&2&A8: PCI standard PCI-to-PCI bridge
PCI\VEN_10DE&DEV_0A88&SUBSYS_3651103C&REV_B1\3&2411E6FE&2&01: PCI standard RAM Controller
PCI\VEN_10DE&DEV_0AA7&SUBSYS_3651103C&REV_B1\3&2411E6FE&2&30: Standard OpenHCD USB Host Controller
PCI\VEN_10DE&DEV_0AC7&SUBSYS_3651103C&REV_B1\3&2411E6FE&2&B0: PCI standard PCI-to-PCI bridge
PCI\VEN_10DE&DEV_0A89&SUBSYS_3651103C&REV_B1\3&2411E6FE&2&1B: PCI standard RAM Controller
PCI\VEN_10DE&DEV_0AA9&SUBSYS_3651103C&REV_B1\3&2411E6FE&2&31: Standard Enhanced PCI to USB Host Controller
PCI\VEN_14E4&DEV_4353&SUBSYS_1509103C&REV_01\4&34E7A9F&0&00A8: Broadcom 43224AG 802.11a/b/g/draft-n Wi-Fi Adapter
PCI\VEN_10DE&DEV_0AA0&SUBSYS_3651103C&REV_B1\3&2411E6FE&2&80: PCI standard PCI-to-PCI bridge
PCI\VEN_10DE&DEV_0AAB&SUBSYS_3651103C&REV_B1\3&2411E6FE&2&48: PCI standard PCI-to-PCI bridge
PCI\VEN_10DE&DEV_0AA2&SUBSYS_3651103C&REV_B1\3&2411E6FE&2&1A: NVIDIA nForce PCI System Management
PCI\VEN_10DE&DEV_0AAE&SUBSYS_3651103C&REV_B3\3&2411E6FE&2&18: PCI standard ISA bridge
20 matching device(s) found.
USB Devices 
USB\VID_03F0&PID_1F1D&MI_02\6&5E8F568&0&0002                : HP un2400 Mobile Broadband Module Modem
USB\VID_03F0&PID_1F1D&MI_03\6&5E8F568&0&0003                : HP un2400 Mobile Broadband Module Ethernet Adaptor
USB\VID_03F0&PID_231D\5&199D7B88&0&4                        : HP Integrated Module with Bluetooth 2.1 Wireless Technology
USB\VID_5986&PID_0182\5&37079FE0&0&2                        : USB Composite Device
USB\VID_5986&PID_0182&MI_00\6&3AC1FE7C&0&0000               : HP Webcam-50
USB\ROOT_HUB\4&32EE9570&0                                   : USB Root Hub
USB\VID_045E&PID_0040\5&199D7B88&0&1                        : Microsoft USB Wheel Mouse Optical
USB\ROOT_HUB\4&7900E16&0                                    : USB Root Hub
USB\ROOT_HUB20\4&36083375&0                                 : USB Root Hub
USB\ROOT_HUB20\4&4D1C408&0                                  : USB Root Hub
USB\VID_03F0&PID_1F1D\5&35BB7027&0&5                        : HP USB Composite Device
USB\VID_0951&PID_1621\0018F30C9F555B9414080015              : USB Mass Storage Device
USB\VID_03F0&PID_1F1D&MI_00\6&5E8F568&0&0000                : HP un2400 Mobile Broadband Module (COM3)
USBSTOR\DISK&VEN_KINGSTON&PROD_DATATRAVELER_150&REV_PMAP\0018F30C9F555B9414080015&0: Kingston DataTraveler 150 USB Device
USB\VID_03F0&PID_1F1D&MI_01\6&5E8F568&0&0001                : HP un2400 Mobile Broadband Module Device  (COM4)
15 matching device(s) found.
Input Devices 
HID\VID_045E&PID_0040\6&100099E0&0&0000                     : Microsoft USB Wheel Mouse Optical
HID\{84A1E9B8-12BA-4A9C-8AB0-A43784E0D149}_LOCALMFG&0000\8&120CA44F&0&0000: HID-compliant consumer control device
2 matching device(s) found.
ACPI Devices 
ACPI\PNP0303\4&5C91EB2&0                                    : Standard PS/2 Keyboard
ROOT\ACPI_HAL\0000                                          : ACPI x86-based PC
ACPI\PNP0800\4&5C91EB2&0                                    : System speaker
ACPI\PNP0A08\1                                              : PCI bus
ACPI\PNP0B00\4&5C91EB2&0                                    : System CMOS/real time clock
ACPI\PNP0C01\4&5C91EB2&0                                    : System board
ACPI\ACPI0003\2&DABA3FF&2                                   : Microsoft AC Adapter
ACPI\PNP0C02\5                                              : Motherboard resources
ACPI\AUI1101\4&5C91EB2&0                                    : Alps Pointing-device
ACPI\PNP0C04\4&5C91EB2&0                                    : Numeric data processor
ACPI\FIXEDBUTTON\2&DABA3FF&2                                : ACPI Fixed Feature Button
ACPI\PNP0C09\1                                              : Microsoft ACPI-Compliant Embedded Controller
ACPI\PNP0C0A\1                                              : Microsoft ACPI-Compliant Control Method Battery
ACPI\GENUINEINTEL_-_X86_FAMILY_6_MODEL_28_-__________INTEL(R)_ATOM(TM)_CPU_N270___@_1.60GHZ\_0: Intel(R) Atom(TM) CPU N270   @ 1.60GHz
ACPI\PNP0C0C\2&DABA3FF&2                                    : ACPI Power Button
ACPI\PNP0C0D\2&DABA3FF&2                                    : ACPI Lid
ACPI\PNP0C0E\2&DABA3FF&2                                    : ACPI Sleep Button
ACPI\PNP0C14\0                                              : Microsoft Windows Management Interface for ACPI
ACPI\GENUINEINTEL_-_X86_FAMILY_6_MODEL_28_-__________INTEL(R)_ATOM(TM)_CPU_N270___@_1.60GHZ\_1: Intel(R) Atom(TM) CPU N270   @ 1.60GHz
ACPI\PNP0C14\NVIF                                           : Microsoft Windows Management Interface for ACPI
ACPI\THERMALZONE\TZ0_                                       : ACPI Thermal Zone
ACPI_HAL\PNP0C08\0                                          : Microsoft ACPI-Compliant System
ACPI\PNP0000\4&5C91EB2&0                                    : Programmable interrupt controller
ACPI\PNP0100\4&5C91EB2&0                                    : System timer
ACPI\PNP0103\3&2411E6FE&2                                   : High precision event timer
ACPI\PNP0200\4&5C91EB2&0                                    : Direct memory access controller
26 matching device(s) found.
 HDA Audio 
HDAUDIO\FUNC_01&VEN_10DE&DEV_0007&SUBSYS_10DE0101&REV_1001\4&176018E0&0&0301: NVIDIA High Definition Audio
HDAUDIO\FUNC_01&VEN_111D&DEV_7605&SUBSYS_103C3651&REV_1004\4&176018E0&0&0001: IDT High Definition Audio CODEC
2 matching device(s) found.
RAID Devices 
    Name: NVIDIA nForce Serial ATA Controller
    Hardware ID's:
    Compatible ID's:
1 matching device(s) found.

Here is my DPs_BASE.log file:

2010-01-04 11:03:43 : <INIT> DriverPacks BASE 8.12.5 initialized.
2010-01-04 11:03:43 : <INIT> Host environment: WIN_XP Service Pack 3 on X86 CPU.
2010-01-04 11:03:43 : <INIT> Created temporary working directory.
2010-01-04 11:03:43 : <INIT> Imported proxy settings from Internet Explorer.
2010-01-04 11:03:43 : <INIT> Start scanning for DriverPacks for the wnt5_x86-32 platform.
2010-01-04 11:03:43 : <INIT> 	Could not detect any (official) DriverPacks.
2010-01-04 11:03:43 : <INIT> 	Could not detect any 3rd party DriverPacks for wnt5_x86-32.
2010-01-04 11:03:43 : <INIT> 	Finished scanning.
2010-01-04 11:03:43 : <INIT> Detected settings file "C:\UBCD4Win350\plugin\\BASE\DPs_BASE.ini".
2010-01-04 11:03:43 : <INIT> [Settings]\DPsMethod not specified: default (2) was set.
2010-01-04 11:03:43 : <INIT> [Settings]\finisherMethod not specified: default (GUIRunOnce) was set.
2010-01-04 11:03:43 : <INIT> [OptionalSettings]\KTD not specified: default (none) was set.
2010-01-04 11:03:43 : <INIT> [OptionalSettings]\QSC not specified: default (yes) was set.
2010-01-04 11:03:43 : <INIT> [OptionalSettingsOther]\ATI_cpl not specified: default (None) was set.
2010-01-04 11:03:43 : <INIT> [OptionalSettingsOther]\Nvidia_cpl not specified: default (None) was set.
2010-01-04 11:03:43 : <INIT> wnt5_x86-32_bartpe is the selected installation platform .
2010-01-04 11:03:43 : <INIT> Imported settings from settings file.
2010-01-04 11:03:43 : <INIT> [OptionalSettings]\QSC BartPE default (no)    was set.
2010-01-04 11:03:43 : <GUI>  Initialized GUI.
2010-01-04 11:03:43 : <GUI>  Created a list of all available language files.
2010-01-04 11:03:43 : <GUI>  Set the last used language, English, as the GUI language.
2010-01-04 11:03:47 : <GUI>  Refreshed UpdateChecker with success.
2010-01-04 11:03:59 : <GUI>  Downloaded DriverPack Chipset 9.02.
2010-01-04 11:03:59 : <GUI>  Start scanning for DriverPacks for the wnt5_x86-32 platform.
2010-01-04 11:03:59 : <GUI>  	Detected DriverPack Chipset 902!
2010-01-04 11:03:59 : <GUI>  	Could not detect any 3rd party DriverPacks for wnt5_x86-32.
2010-01-04 11:03:59 : <GUI>  	Finished scanning.
2010-01-04 11:04:00 : <GUI>  Refreshed UpdateChecker with success.
2010-01-04 11:04:04 : <GUI>  Saved settings!
2010-01-04 11:04:04 : <GUI>  Closed GUI.
2010-01-04 11:04:04 : <SEL>  Selected module: mod_slip_wnt5_x86-32_bartpe.
2010-01-04 11:04:05 : <PREP> C:\UBCD4Win350\plugin\\Chipset was deleted.
2010-01-04 11:04:05 : <PREP> C:\UBCD4Win350\plugin\\Chipset\Chipset.inf info written.
2010-01-04 11:04:05 : <PREP> C:\UBCD4Win350\plugin\\CPU was deleted.
2010-01-04 11:04:06 : <PREP> C:\UBCD4Win350\plugin\\LAN was deleted.
2010-01-04 11:04:07 : <PREP> C:\UBCD4Win350\plugin\\WLAN was deleted.
2010-01-04 11:04:13 : <PLUGIN> Extracted DriverPack Chipset.
2010-01-04 11:04:13 : <PLUGIN> Started CAB compressing DriverPack Chipset (estimated 0.4 minutes).
2010-01-04 11:04:13 : <PLUGIN> C:\UBCD4Win350\plugin\\BASE\tmp\DriverPacks\DriverPack Chipset\DriverPack_Chipset_wnt5_x86-32.ini
2010-01-04 11:04:19 : <PLUGIN> C:\UBCD4Win350\plugin\\BASE\tmp\DriverPacks\DriverPack Chipset\D\C\I2\2, \wnt5, HECI.IN?
2010-01-04 11:04:19 : <PLUGIN> C:\UBCD4Win350\plugin\\BASE\tmp\DriverPacks\DriverPack Chipset\D\C\I2\2, \wnt5, HECI.INF
2010-01-04 11:04:19 : <PLUGIN> C:\UBCD4Win350\plugin\\BASE\tmp\DriverPacks\DriverPack Chipset\D\C\I2\2, \wnt5, HECI.SY?
2010-01-04 11:04:19 : <PLUGIN> C:\UBCD4Win350\plugin\\BASE\tmp\DriverPacks\DriverPack Chipset\D\C\I2\2, \wnt5, HECI2K.SY?
2010-01-04 11:04:19 : <PLUGIN> C:\UBCD4Win350\plugin\\BASE\tmp\DriverPacks\DriverPack Chipset\D\C\I2\3, \wnt5, HECI.IN?
2010-01-04 11:04:19 : <PLUGIN> C:\UBCD4Win350\plugin\\BASE\tmp\DriverPacks\DriverPack Chipset\D\C\I2\3, \wnt5, HECI.INF
2010-01-04 11:04:19 : <PLUGIN> C:\UBCD4Win350\plugin\\BASE\tmp\DriverPacks\DriverPack Chipset\D\C\I2\3, \wnt5, HECI.SY?
2010-01-04 11:04:19 : <PLUGIN> C:\UBCD4Win350\plugin\\BASE\tmp\DriverPacks\DriverPack Chipset\D\C\I2\4, \wnt5, HECI.IN?
2010-01-04 11:04:19 : <PLUGIN> C:\UBCD4Win350\plugin\\BASE\tmp\DriverPacks\DriverPack Chipset\D\C\I2\4, \wnt5, HECI.INF
2010-01-04 11:04:19 : <PLUGIN> C:\UBCD4Win350\plugin\\BASE\tmp\DriverPacks\DriverPack Chipset\D\C\I2\4, \wnt5, HECI.SY?
2010-01-04 11:04:19 : <PLUGIN> C:\UBCD4Win350\plugin\\BASE\tmp\DriverPacks\DriverPack Chipset\D\C\I3\2, \wnt5, MESRL.IN?
2010-01-04 11:04:19 : <PLUGIN> C:\UBCD4Win350\plugin\\BASE\tmp\DriverPacks\DriverPack Chipset\D\C\I3\2, \wnt5, MESRL.INF
2010-01-04 11:04:19 : <PLUGIN> C:\UBCD4Win350\plugin\\BASE\tmp\DriverPacks\DriverPack Chipset\D\C\I3\2, \wnt5, MESRLE.IN?
2010-01-04 11:04:19 : <PLUGIN> C:\UBCD4Win350\plugin\\BASE\tmp\DriverPacks\DriverPack Chipset\D\C\I3\2, \wnt5, MESRLE.INF
2010-01-04 11:04:19 : <PLUGIN> C:\UBCD4Win350\plugin\\BASE\tmp\DriverPacks\DriverPack Chipset\D\C\I3\3, \wnt5, MESRL.IN?
2010-01-04 11:04:19 : <PLUGIN> C:\UBCD4Win350\plugin\\BASE\tmp\DriverPacks\DriverPack Chipset\D\C\I3\3, \wnt5, MESRL.INF
2010-01-04 11:04:19 : <PLUGIN> C:\UBCD4Win350\plugin\\BASE\tmp\DriverPacks\DriverPack Chipset\D\C\I3\3, \wnt5, MESRLE.IN?
2010-01-04 11:04:19 : <PLUGIN> C:\UBCD4Win350\plugin\\BASE\tmp\DriverPacks\DriverPack Chipset\D\C\I3\3, \wnt5, MESRLE.INF
2010-01-04 11:04:21 : <PLUGIN> C:\UBCD4Win350\plugin\\BASE\tmp\DriverPacks\DriverPack Chipset\D\C\N4, \wnt5, NF4SYS.IN?
2010-01-04 11:04:21 : <PLUGIN> C:\UBCD4Win350\plugin\\BASE\tmp\DriverPacks\DriverPack Chipset\D\C\N4, \wnt5, NF4SYS.INF
2010-01-04 11:04:21 : <PLUGIN> C:\UBCD4Win350\plugin\\BASE\tmp\DriverPacks\DriverPack Chipset\D\C\N4, \wnt5, NVCOSMU.DL?
2010-01-04 11:04:21 : <PLUGIN> C:\UBCD4Win350\plugin\\BASE\tmp\DriverPacks\DriverPack Chipset\D\C\N4, \wnt5, NVSMBUS.IN?
2010-01-04 11:04:21 : <PLUGIN> C:\UBCD4Win350\plugin\\BASE\tmp\DriverPacks\DriverPack Chipset\D\C\N4, \wnt5, NVSMBUS.INF
2010-01-04 11:04:21 : <PLUGIN> C:\UBCD4Win350\plugin\\BASE\tmp\DriverPacks\DriverPack Chipset\D\C\N4, \wnt5, NVSMU.SY?
2010-01-04 11:04:21 : <PLUGIN> C:\UBCD4Win350\plugin\\BASE\tmp\DriverPacks\DriverPack Chipset\D\C\N4, \wnt5, SMUC.IN?
2010-01-04 11:04:21 : <PLUGIN> C:\UBCD4Win350\plugin\\BASE\tmp\DriverPacks\DriverPack Chipset\D\C\N4, \wnt5, SMUC.INF
2010-01-04 11:04:22 : <PLUGIN> Finished CAB compressing DriverPack Chipset.
2010-01-04 11:04:23 : <PLUGIN> Saved settings!
2010-01-04 11:04:23 : <PLUGIN> Slipstream finished in 19 seconds.
2010-01-04 11:04:24 : <CLNP> Temporary working directory successfully deleted.
- = DriverPacks BASE ini settings used = -
; preferred language
prefLang	= "English"
; yes/no, enable or disable the wizard-style buttons, if not specified: yes
wizardButtons	= "yes"
; yes/no, enable or disable the GUI, if not specified: yes
GUI		= "yes"

; disc/bartpe/multibootDisc
instPlatform	= "bartpe"
; trailing backslash is allowed, but not necessary
location	= "C:\UBCD4Win350\plugin"
; none/all/select, if select, specify them below, if not specified: all
DriverPacks	= "select"
; 1/2, method to install the DriverPacks, if not specified: 2
DPsMethod	= "2"
; GUIRunOnce/RunOnceEx/custom, if not specified: GUIRunOnce
finisherMethod	= "GUIRunOnce"

; this section is optional!
; none/all/select/paths/patterns, enable or disable Keep The Drivers (KTD) , if not specified: none
KTD		= "false"
; <path>, to specify a custom KTD cache location, if not specified: default (%SystemRoot%\DriverPacks)
KTDlocation	= "%SystemRoot%\DriverPacks"
; yes/no, enable or disable QuickStream Cache (QSC), if not specified: yes
QSC		= "no"

; you should only add this section if you've set [Settings]\DriverPacks to "select"
DP_Chipset	= "yes"
DP_MassStorage_textmode = "no"
2010-01-04 11:04:24 : <CLNP> Create a DPs_Base.log backup @ C:\UBCD4Win350\plugin\\BASE\LogFiles\DPs_BASE_10-01-04_11-04.log
2010-01-04 11:04:24 : <CLNP> Program terminated.

Thank you for any help.


Re: [Help me] BSOD 7b with Chipset Driverpack on Nvidia hardware

Moved to the ubcd4win forums.

Have you tried a normal DriverPacks BASE integration into a standard XP source to see if the driver works at all on your hardware?  And not just a BartPE problem?
I'm just trying to determine if it's an incompatible driver or a configuration problem.

Read BEFORE you post.  HWID tool   DriverPacks Tutorial   DONATE!
Not all heroes wear capes, some wear Kevlar!

Re: [Help me] BSOD 7b with Chipset Driverpack on Nvidia hardware

Why do you add Chipset files to a PE?
Is there any special reason?

Re: [Help me] BSOD 7b with Chipset Driverpack on Nvidia hardware


I just tried integrated the chipset driverpack into a standard XP SP3 CD and loaded it on the same machine.  It did not blue screen.  It must be a problem with PE.  I'm using the UBCD4win 3.50  I'm not sure how to start troubleshooting this problem.


I don't have any special reason why I add the chipset files to PE.  I just want to have the most complete set of drivers for the PE.  They are not always required.

Re: [Help me] BSOD 7b with Chipset Driverpack on Nvidia hardware

Normaly only the mass storage are needed the others are optional...
This is the way UBCD4Win is pre configured when you download it big_smile.

some require other plugins to function at all (sound for example)
While DriverPacks BASE will generate the plugins for packs other than Mass Storage they are considered beta / test features.

bartpe is a recovery tool not an os replacement... wink

Unless you have a specific need, then it is probably not worth the effort wink
If you have a specific need there are ways to make them work.
This will require a great deal of effort and research on your part

DP BartPE Tutorial   DP_BASE Tutorial   HWID's Tool     Read BEFORE you post    UserBars!
The DriverPacks, the DP_Base program, and Support Forum are FREE!.

Re: [Help me] BSOD 7b with Chipset Driverpack on Nvidia hardware

Ok, sounds good to me.  I have not found anything that requires the chipset driverpack to function.  I'll drop that driverpack.

Re: [Help me] BSOD 7b with Chipset Driverpack on Nvidia hardware

To clarify:
most chipset drivers contains a *.inf file only. Default windows *.sys drivers are used.
*.inf creates a nice loocking device manager with nice names.

At PE windows setup load default drivers.
Appropiate windows drivers are running for chipset.
However device manager dosn't contain nice names.
Just ignore this a as for a recovery tool.

Strange the BSOD with chipset pack. Technically it's interesting to investigate.
Contrary so far I'm convinced it's not worth the effort.

Yes, don't include chipset DriverPack to UBCD4Win.

Re: [Help me] BSOD 7b with Chipset Driverpack on Nvidia hardware

If it were not an Nvidia chipset it would not be such a PITA wink

I'm sure it is related to missing registry entries, but you know that better than I do.
It was you and Highlander that taught me how to write a plugin... big_smile!

Thanks again for that ! ! ! You da Man!

PS my second guess is the BSOD is related to version mis-match between nvidia chipset and Nvidia Mass storage.

DP BartPE Tutorial   DP_BASE Tutorial   HWID's Tool     Read BEFORE you post    UserBars!
The DriverPacks, the DP_Base program, and Support Forum are FREE!.