• Tim545
  • DriverPacks newbie
  • Offline
  • Registered: 2006-10-01
  • Posts: 8

Topic: [NEEDS REPLY] Install works on Virtal PC but get BSOD on actual PC

This is my first post.  I hope I selected the correct topic area.

I'm new to slipstreaming and drivepacks, but have been reading to get up-to-date.  What I've read in this and other forums has helped much ... and I thank you.

My first creation (using nLite) was a simply one, incorporating SP2 and Ryan's updates, followed MSFN guide, and it worked.  I successfully tested using MS Virtual PC.  Next I wanted to add driverpacks, figuring that if I used all of them, I could generate a generic install where I could simply update serial info and I'd be all set.  Downloaded latest DP_packs, latest Ryan Addons, lates software, and generated. 

During creation I received the "Created OemPnpDriversPath entry. The length is 5916, which EXCEEDS the 4096 characters limit" message it was pointed out on this forum that this was simply a warning, not an error.  I did rename all directories to one-character folder names and placed everything off the root in hopes I could get this warning to go away, but it did not help.  I proceeded.

Tested the completed ISO using Virtual PC successfully.  When I installed on fresh harddrive on PC, everything seemed to work sucessfully until it showed WinXP splash screen than crashed with BSD.  I figured the problem was probably a device driver issue, and given that this is an older system with a PCI SIIG USB2.0 + 1394 + UltraATA 133 RAID Controller Card (that frequently gives me problems when not trying to slipstream), I concluded that I would try manually updating drivers for this first.  I booted into Safe Mode, inserted CD and attempted to install drivers from CD.  This was my first anomaly, when I directed driver update direct to this CD to install -- I apparently was redirected to driverpack install because next I saw KTD Screen doing the update.  This confused me, and still does.

So I rebooted again, this time using SIIG total install software (which I don't like using) and forced a complete software installation.  This did not help.  I continued manually updating drivers one at a time and rebooting, hoping I could determine which driver was casuing the problem.  Still nothing works. 

I guess I know enough to be dangerous, but not enough to really understand what is going on. 

I am following the protocol I've seen in other posts and including the log files.  I can't figure out how folks post these files into the windows

If anybody could provide me with guidance, I would be grateful.

DPs_BASE.log

2006-09-29 09:45:17 : <INIT> DriverPacks BASE 6.08.6 initialized.
2006-09-29 09:45:17 : <INIT> Host environment: WIN_XP Service Pack 2 on X86 CPU.
2006-09-29 09:45:17 : <INIT> Detected settings file "D:\XDP\DPs_BASE.ini".
2006-09-29 09:45:17 : <INIT> Windows XP Professional -  Retail SP2 detected.
2006-09-29 09:45:17 : <INIT> The platform wnt5_x86-32_disc will be used (which is the 'disc' installation platform for the OS family 'wnt5_x86-32').
2006-09-29 09:45:17 : <INIT> Imported settings from settings file.
2006-09-29 09:45:17 : <INIT> Detected DriverPack Chipset 6.09.1!
2006-09-29 09:45:17 : <INIT> Detected DriverPack CPU 6.09.1!
2006-09-29 09:45:17 : <INIT> Detected DriverPack Graphics A 6.09!
2006-09-29 09:45:17 : <INIT> Detected DriverPack Graphics B 6.08!
2006-09-29 09:45:17 : <INIT> Detected DriverPack Graphics C 6.03!
2006-09-29 09:45:17 : <INIT> Detected DriverPack LAN 6.08.1!
2006-09-29 09:45:17 : <INIT> Detected DriverPack MassStorage 6.08!
2006-09-29 09:45:17 : <INIT> Detected DriverPack Sound A 6.08.1!
2006-09-29 09:45:17 : <INIT> Detected DriverPack Sound B 6.08!
2006-09-29 09:45:17 : <INIT> Detected DriverPack WLAN 6.08!
2006-09-29 09:45:17 : <INIT> Could not detect any 3rd party DriverPacks.
2006-09-29 09:45:17 : <INIT> DriverPacks scanned sucessfully.
2006-09-29 09:45:17 : <GUI>  Initialized GUI.
2006-09-29 09:45:17 : <GUI>  Created a list of all available language files.
2006-09-29 09:45:17 : <GUI>  Set the last used language, English, as the GUI language.
2006-09-29 09:45:26 : <GUI>  Windows XP Professional -  Retail SP2 detected.
2006-09-29 09:45:26 : <GUI>  The platform wnt5_x86-32_disc will be used (which is the 'disc' installation platform for the OS family 'wnt5_x86-32').
2006-09-29 09:45:50 : <GUI>  Changed Windows installation files OR export (depending on the installation platform) location to D:\XP.
2006-09-29 09:45:50 : <GUI>  Windows XP Professional -  Retail SP2 detected.
2006-09-29 09:45:50 : <GUI>  The platform wnt5_x86-32_disc will be used (which is the 'disc' installation platform for the OS family 'wnt5_x86-32').
2006-09-29 09:46:09 : <GUI>  Refreshed UpdateChecker with success.
2006-09-29 09:46:09 : <GUI>  Refreshed UpdateChecker with success.
2006-09-29 09:46:12 : <GUI>  Saved settings!
2006-09-29 09:46:12 : <GUI>  Closed GUI.
2006-09-29 09:46:12 : <SEL>  Selected module: mod_slip_wxp_x86-32_disc_m1.
2006-09-29 09:46:13 : <PREP> Removed all attributes from \I386.
2006-09-29 09:46:13 : <PREP> Created a backup of \I386\winnt.sif.
2006-09-29 09:46:13 : <PREP> Created a backup of \I386\txtsetup.sif.
2006-09-29 09:46:13 : <PREP> Created a backup of \I386\dosnet.inf.
2006-09-29 09:46:13 : <PREP> Created temporary working directory.
2006-09-29 09:46:13 : <SLIP> QuickStream Cache available for DriverPack Chipset!
2006-09-29 09:46:13 : <SLIP> QuickStream Cache available for DriverPack CPU!
2006-09-29 09:46:13 : <SLIP> QuickStream Cache available for DriverPack Graphics A!
2006-09-29 09:46:13 : <SLIP> QuickStream Cache available for DriverPack Graphics B!
2006-09-29 09:46:13 : <SLIP> QuickStream Cache available for DriverPack Graphics C!
2006-09-29 09:46:13 : <SLIP> QuickStream Cache available for DriverPack LAN!
2006-09-29 09:46:13 : <SLIP> QuickStream Cache available for DriverPack MassStorage!
2006-09-29 09:46:13 : <SLIP> QuickStream Cache available for DriverPack Sound A!
2006-09-29 09:46:13 : <SLIP> QuickStream Cache available for DriverPack Sound B!
2006-09-29 09:46:13 : <SLIP> QuickStream Cache available for DriverPack WLAN!
2006-09-29 09:46:18 : <SLIP> Slipstreamed DriverPack Chipset using the QuickStream Cache.
2006-09-29 09:46:18 : <SLIP> Slipstreamed DriverPack CPU using the QuickStream Cache.
2006-09-29 09:46:46 : <SLIP> Slipstreamed DriverPack Graphics A using the QuickStream Cache.
2006-09-29 09:47:14 : <SLIP> Slipstreamed DriverPack Graphics B using the QuickStream Cache.
2006-09-29 09:47:25 : <SLIP> Slipstreamed DriverPack Graphics C using the QuickStream Cache.
2006-09-29 09:47:34 : <SLIP> Slipstreamed DriverPack LAN using the QuickStream Cache.
2006-09-29 09:47:40 : <SLIP> Slipstreamed DriverPack MassStorage using the QuickStream Cache.
2006-09-29 09:47:59 : <SLIP> Slipstreamed DriverPack Sound A using the QuickStream Cache.
2006-09-29 09:48:25 : <SLIP> Slipstreamed DriverPack Sound B using the QuickStream Cache.
2006-09-29 09:48:45 : <SLIP> Slipstreamed DriverPack WLAN using the QuickStream Cache.
2006-09-29 09:48:46 : <SLIP> Copied Intel chipset drivers' .inf files to \$OEM$\$$\INF.
2006-09-29 09:48:46 : <SLIP> English (RyanVM's) UpdatePack detected: no HDA hotfix will be slipstreamed.
2006-09-29 09:48:46 : <SLIP> QuickStream Cache available for DriverPack MassStorage text mode drivers!
2006-09-29 09:48:46 : <SLIP> Slipstreamed DP MassStorage text mode drivers using QuickStream Cache.
2006-09-29 09:48:58 : <SLIP> Removed entries from \I386\txtsetup.sif that will be updated.
2006-09-29 09:49:01 : <SLIP> Removed entries from \I386\dosnet.inf that will be updated.
2006-09-29 09:50:10 : <SLIP> Updated \I386\dosnet.inf and \I386\txtsetup.sif to support DP MassStorage text mode drivers.
2006-09-29 09:50:10 : <SLIP> Extracted bin\DPsFnshr.7z to \$OEM$\$1.
2006-09-29 09:50:11 : <WARN> Created OemPnpDriversPath entry. The length is 5916, which EXCEEDS the 4096 characters limit. You can continue the installation, but the paths listed after the 4096 characters limit will NOT be processed. You may want to remove some DriverPacks or switch to method 2.
2006-09-29 09:59:36 : <SLIP> Added OemPnpDriversPath entry to \I386\winnt.sif.
2006-09-29 09:59:37 : <SLIP> Updated \I386\winnt.sif to support method 1.
2006-09-29 09:59:37 : <SLIP> Updated DPsFnshr.ini to enable KTD.
2006-09-29 09:59:37 : <SLIP> Updated \I386\winnt.sif's GUIRunOnce section.
2006-09-29 09:59:37 : <SLIP> Slipstream finished in 13 minutes and 25 seconds.
2006-09-29 09:59:38 : <CLNP> Temporary working directory successfully deleted.
2006-09-29 09:59:38 : Program terminated.

DPsFnshr.log

2006-09-29 11:35:52 : <INIT> DriverPacks Finisher 6.08.6 initialized.
2006-09-29 11:35:52 : <INIT> Detected platform wnt5_x86-32.
2006-09-29 11:35:52 : <INIT> Start logging of the HWIDs for relevant devices present in this system.
2006-09-29 11:35:52 : <INIT> 1. ACPI devices

ACPI\AUTHENTICAMD_-_X86_FAMILY_6_MODEL_6\_0                 : AMD Athlon(tm) Processor
ACPI\FIXEDBUTTON\2&DABA3FF&0                                : ACPI Fixed Feature Button
ACPI\PNP0100\4&102163C3&0                                   : System timer
ACPI\PNP0200\4&102163C3&0                                   : Direct memory access controller
ACPI\PNP0303\4&102163C3&0                                   : Standard 101/102-Key or Microsoft Natural PS/2 Keyboard
ACPI\PNP0400\4&102163C3&0                                   : Printer Port (LPT1)
ACPI\PNP0501\1                                              : Communications Port (COM1)
ACPI\PNP0501\2                                              : Communications Port (COM1)
ACPI\PNP0700\4&102163C3&0                                   : Standard floppy disk controller
ACPI\PNP0800\4&102163C3&0                                   : System speaker
ACPI\PNP0A03\2&DABA3FF&0                                    : PCI bus
ACPI\PNP0B00\4&102163C3&0                                   : System CMOS/real time clock
ACPI\PNP0C04\4&102163C3&0                                   : Numeric data processor
ACPI\PNP0C0E\2&DABA3FF&0                                    : ACPI Sleep Button
ACPI\PNP0F03\4&102163C3&0                                   : Microsoft PS/2 Mouse
ACPI_HAL\PNP0C08\0                                          : Microsoft ACPI-Compliant System
ROOT\ACPI_HAL\0000                                          : Advanced Configuration and Power Interface (ACPI) PC
17 matching device(s) found.

2006-09-29 11:35:52 : <INIT> 2. PCI devices

PCI\VEN_1033&DEV_0035&SUBSYS_003514DB&REV_41\4&36EC0E2&0&4068: NEC PCI to USB Open Host Controller
PCI\VEN_1033&DEV_0035&SUBSYS_003514DB&REV_41\4&36EC0E2&0&4168: NEC PCI to USB Open Host Controller
PCI\VEN_1033&DEV_00E0&SUBSYS_00E014DB&REV_02\4&36EC0E2&0&4268: NEC PCI to USB Enhanced Host Controller (B1)
PCI\VEN_1039&DEV_0001&SUBSYS_00000000&REV_00\3&61AAA01&0&08 : PCI to PCI Bridge
PCI\VEN_1039&DEV_0008&SUBSYS_00000000&REV_00\3&61AAA01&0&10 : SIS PCI to ISA bridge
PCI\VEN_1039&DEV_0735&SUBSYS_00000000&REV_01\3&61AAA01&0&00 : SiS735/733  Host CPU Bridge
PCI\VEN_1039&DEV_0900&SUBSYS_09001039&REV_90\3&61AAA01&0&18 : SiS 900 PCI Fast Ethernet Adapter
PCI\VEN_1039&DEV_5513&SUBSYS_55131039&REV_D0\3&61AAA01&0&15 : SiS PCI IDE Controller
PCI\VEN_1039&DEV_7001&SUBSYS_70011039&REV_07\3&61AAA01&0&12 : SiS 7001 PCI to USB Open Host Controller
PCI\VEN_1039&DEV_7001&SUBSYS_70011039&REV_07\3&61AAA01&0&13 : SiS 7001 PCI to USB Open Host Controller
PCI\VEN_1039&DEV_7012&SUBSYS_030013F6&REV_A0\3&61AAA01&0&17 : C-Media AC97 Audio Device
PCI\VEN_1095&DEV_0680&SUBSYS_36801095&REV_02\4&36EC0E2&0&5068: Silicon Image SiI 0680 Ultra-133 Medley ATA Raid Controller
PCI\VEN_1106&DEV_3044&SUBSYS_304414DB&REV_46\4&36EC0E2&0&4868: VIA OHCI Compliant IEEE 1394 Host Controller
PCI\VEN_3388&DEV_0021&SUBSYS_00000000&REV_15\3&61AAA01&0&68 : PCI standard PCI-to-PCI bridge
14 matching device(s) found.

2006-09-29 11:35:52 : <INIT> 3. HDAUDIO devices

No matching devices found.

2006-09-29 11:35:52 : <INIT> 4. USB devices

USB\ROOT_HUB\4&133E0718&0                                   : USB Root Hub
USB\ROOT_HUB\4&845673&0                                     : USB Root Hub
USB\ROOT_HUB\5&24EBAC68&0                                   : USB Root Hub
USB\ROOT_HUB\5&5425326&0                                    : USB Root Hub
USB\ROOT_HUB20\5&13EE05C9&0                                 : USB Root Hub
USB\VID_0409&PID_0058\6&1081BD6A&0&2                        : Generic USB Hub
6 matching device(s) found.

2006-09-29 11:35:52 : <INIT> Logging of HWIDs complete.
2006-09-29 11:35:52 : <INIT> Processed settings.
2006-09-29 11:35:53 : <FLTR> Collected the HWIDs for this system.
2006-09-29 11:35:53 : <FLTR> Verifying requirements for exception [wnt5_x86-32__0001__D-G-A-1] (1 of 21 exceptions).
2006-09-29 11:35:53 : <FLTR> 	1. tagFiles (ALL tagFiles must be found)
2006-09-29 11:35:53 : <FLTR> 		Found tagfile "C:\ATICCC.ins" (1/2).
2006-09-29 11:35:53 : <FLTR> 		! Could not find tagfile 'C:\D\G\A\1\ATICCC.exe' (2 of 2 tagfiles).
2006-09-29 11:35:53 : <FLTR> 	=> This exception will not be applied.
2006-09-29 11:35:53 : <FLTR> Verifying requirements for exception [wnt5_x86-32__0002__D-G-A-1] (2 of 21 exceptions).
2006-09-29 11:35:53 : <FLTR> 	1. tagFiles (ALL tagFiles must be found)
2006-09-29 11:35:53 : <FLTR> 		! Could not find tagfile 'C:\ATICCP.ins' (1 of 2 tagfiles).
2006-09-29 11:35:53 : <FLTR> 	=> This exception will not be applied.
2006-09-29 11:35:53 : <FLTR> Verifying requirements for exception [wnt5_x86-32__0021__D-G-A-2] (3 of 21 exceptions).
2006-09-29 11:35:53 : <FLTR> 	1. tagFiles (ALL tagFiles must be found)
2006-09-29 11:35:53 : <FLTR> 		Found tagfile "C:\ATICCC.ins" (1/2).
2006-09-29 11:35:53 : <FLTR> 		! Could not find tagfile 'C:\D\G\A\1\ATICCC.exe' (2 of 2 tagfiles).
2006-09-29 11:35:53 : <FLTR> 	=> This exception will not be applied.
2006-09-29 11:35:53 : <FLTR> Verifying requirements for exception [wnt5_x86-32__0022__D-G-A-2] (4 of 21 exceptions).
2006-09-29 11:35:53 : <FLTR> 	1. tagFiles (ALL tagFiles must be found)
2006-09-29 11:35:53 : <FLTR> 		! Could not find tagfile 'C:\ATICCP.ins' (1 of 2 tagfiles).
2006-09-29 11:35:53 : <FLTR> 	=> This exception will not be applied.
2006-09-29 11:35:53 : <FLTR> Verifying requirements for exception [wnt5_x86-32__0003__D-G-A-3] (5 of 21 exceptions).
2006-09-29 11:35:53 : <FLTR> 	1. tagFiles (ALL tagFiles must be found)
2006-09-29 11:35:53 : <FLTR> 		! Could not find tagfile 'C:\D\G\A\3\CPanel.exe' (1 of 1 tagfiles).
2006-09-29 11:35:53 : <FLTR> 	=> This exception will not be applied.
2006-09-29 11:35:53 : <FLTR> Verifying requirements for exception [wnt5_x86-32__0004__D-G-3-1] (6 of 21 exceptions).
2006-09-29 11:35:53 : <FLTR> 	1. tagFiles (ALL tagFiles must be found)
2006-09-29 11:35:53 : <FLTR> 		! Could not find tagfile 'C:\WINDOWS\system32\3dfxV2ps.dll' (1 of 1 tagfiles).
2006-09-29 11:35:53 : <FLTR> 	=> This exception will not be applied.
2006-09-29 11:35:53 : <FLTR> Verifying requirements for exception [wnt5_x86-32__0005__D-G-S-1] (7 of 21 exceptions).
2006-09-29 11:35:53 : <FLTR> 	1. tagFiles (ALL tagFiles must be found)
2006-09-29 11:35:53 : <FLTR> 		! Could not find tagfile 'C:\WINDOWS\system32\drivers\sigrp.sys' (1 of 1 tagfiles).
2006-09-29 11:35:53 : <FLTR> 	=> This exception will not be applied.
2006-09-29 11:35:53 : <FLTR> Verifying requirements for exception [wnt5_x86-32__0007__D-S-CR-1] (8 of 21 exceptions).
2006-09-29 11:35:53 : <FLTR> 	1. tagFiles (ALL tagFiles must be found)
2006-09-29 11:35:53 : <FLTR> 		! Could not find tagfile 'C:\WINDOWS\system32\drivers\ha20x2k.sys' (1 of 2 tagfiles).
2006-09-29 11:35:53 : <FLTR> 	=> This exception will not be applied.
2006-09-29 11:35:53 : <FLTR> Verifying requirements for exception [wnt5_x86-32__0008__D-S-CR-2] (9 of 21 exceptions).
2006-09-29 11:35:53 : <FLTR> 	1. tagFiles (ALL tagFiles must be found)
2006-09-29 11:35:53 : <FLTR> 		! Could not find tagfile 'C:\WINDOWS\system32\drivers\ha10x2k.sys' (1 of 3 tagfiles).
2006-09-29 11:35:53 : <FLTR> 	=> This exception will not be applied.
2006-09-29 11:35:53 : <FLTR> Verifying requirements for exception [wnt5_x86-32__0009__D-S-CR-3] (10 of 21 exceptions).
2006-09-29 11:35:53 : <FLTR> 	1. tagFiles (ALL tagFiles must be found)
2006-09-29 11:35:53 : <FLTR> 		! Could not find tagfile 'C:\WINDOWS\system32\drivers\P17.sys' (1 of 2 tagfiles).
2006-09-29 11:35:53 : <FLTR> 	=> This exception will not be applied.
2006-09-29 11:35:53 : <FLTR> Verifying requirements for exception [wnt5_x86-32__0010__D-S-H-2] (11 of 21 exceptions).
2006-09-29 11:35:53 : <FLTR> 	4. +infFiles (ANY +infFiles must be matched)
2006-09-29 11:35:53 : <FLTR> 		! Could not match any of the +infFiles.
2006-09-29 11:35:53 : <FLTR> 	=> This exception will not be applied.
2006-09-29 11:35:53 : <FLTR> Verifying requirements for exception [wnt5_x86-32__0011__D-S-N] (12 of 21 exceptions).
2006-09-29 11:35:53 : <FLTR> 	1. tagFiles (ALL tagFiles must be found)
2006-09-29 11:35:53 : <FLTR> 		! Could not find tagfile 'C:\WINDOWS\system32\drivers\nvapu.sys' (1 of 1 tagfiles).
2006-09-29 11:35:53 : <FLTR> 	=> This exception will not be applied.
2006-09-29 11:35:53 : <FLTR> Verifying requirements for exception [wnt5_x86-32__0012__D-S-S-U] (13 of 21 exceptions).
2006-09-29 11:35:53 : <FLTR> 	1. tagFiles (ALL tagFiles must be found)
2006-09-29 11:35:53 : <FLTR> 		! Could not find tagfile 'C:\WINDOWS\system32\drivers\sthda.sys' (1 of 1 tagfiles).
2006-09-29 11:35:53 : <FLTR> 	=> This exception will not be applied.
2006-09-29 11:35:53 : <FLTR> Verifying requirements for exception [wnt5_x86-32__0013__D-S-SI-1] (14 of 21 exceptions).
2006-09-29 11:35:53 : <FLTR> 	1. tagFiles (ALL tagFiles must be found)
2006-09-29 11:35:53 : <FLTR> 		! Could not find tagfile 'C:\WINDOWS\system32\drivers\sis7012.sys' (1 of 1 tagfiles).
2006-09-29 11:35:53 : <FLTR> 	=> This exception will not be applied.
2006-09-29 11:35:53 : <FLTR> Verifying requirements for exception [wnt5_x86-32__0014__D-S-SI-2] (15 of 21 exceptions).
2006-09-29 11:35:53 : <FLTR> 	1. tagFiles (ALL tagFiles must be found)
2006-09-29 11:35:53 : <FLTR> 		! Could not find tagfile 'C:\WINDOWS\system32\drivers\sis7018.sys' (1 of 1 tagfiles).
2006-09-29 11:35:53 : <FLTR> 	=> This exception will not be applied.
2006-09-29 11:35:53 : <FLTR> Verifying requirements for exception [wnt5_x86-32__0015__D-S-T-2] (16 of 21 exceptions).
2006-09-29 11:35:53 : <FLTR> 	1. tagFiles (ALL tagFiles must be found)
2006-09-29 11:35:53 : <FLTR> 		! Could not find tagfile 'C:\WINDOWS\system32\drivers\FM801.sys' (1 of 1 tagfiles).
2006-09-29 11:35:53 : <FLTR> 	=> This exception will not be applied.
2006-09-29 11:35:53 : <FLTR> Verifying requirements for exception [wnt5_x86-32__0016__D-S-T-3] (17 of 21 exceptions).
2006-09-29 11:35:53 : <FLTR> 	1. tagFiles (ALL tagFiles must be found)
2006-09-29 11:35:53 : <FLTR> 		! Could not find tagfile 'C:\WINDOWS\system32\drivers\cmaudio.sys' (1 of 1 tagfiles).
2006-09-29 11:35:53 : <FLTR> 	=> This exception will not be applied.
2006-09-29 11:35:53 : <FLTR> Verifying requirements for exception [wnt5_x86-32__0017__D-S-T-4] (18 of 21 exceptions).
2006-09-29 11:35:53 : <FLTR> 	1. tagFiles (ALL tagFiles must be found)
2006-09-29 11:35:53 : <FLTR> 		! Could not find tagfile 'C:\WINDOWS\system32\drivers\TT1724ht.sys' (1 of 1 tagfiles).
2006-09-29 11:35:53 : <FLTR> 	=> This exception will not be applied.
2006-09-29 11:35:53 : <FLTR> Verifying requirements for exception [wnt5_x86-32__0018__D-S-T-5] (19 of 21 exceptions).
2006-09-29 11:35:53 : <FLTR> 	1. tagFiles (ALL tagFiles must be found)
2006-09-29 11:35:53 : <FLTR> 		! Could not find tagfile 'C:\WINDOWS\system32\drivers\dmxsens.sys' (1 of 1 tagfiles).
2006-09-29 11:35:53 : <FLTR> 	=> This exception will not be applied.
2006-09-29 11:35:53 : <FLTR> Verifying requirements for exception [wnt5_x86-32__0019__D-S-V-1] (20 of 21 exceptions).
2006-09-29 11:35:53 : <FLTR> 	1. tagFiles (ALL tagFiles must be found)
2006-09-29 11:35:53 : <FLTR> 		! Could not find tagfile 'C:\WINDOWS\system32\drivers\envysens.sys' (1 of 1 tagfiles).
2006-09-29 11:35:53 : <FLTR> 	=> This exception will not be applied.
2006-09-29 11:35:53 : <FLTR> Verifying requirements for exception [wnt5_x86-32__0020__D-S-V-2] (21 of 21 exceptions).
2006-09-29 11:35:53 : <FLTR> 	1. tagFiles (ALL tagFiles must be found)
2006-09-29 11:35:53 : <FLTR> 		! Could not find tagfile 'C:\WINDOWS\system32\drivers\vinyl97.sys' (1 of 2 tagfiles).
2006-09-29 11:35:53 : <FLTR> 	=> This exception will not be applied.
2006-09-29 11:35:53 : <FLTR> Finished filtering exceptions.
2006-09-29 11:35:53 : <EXEC> No exceptions left to execute: none have met all requirements!
2006-09-29 11:35:53 : <KTD>  KTD cache location set: "C:\WINDOWS\DriverPacks".
2006-09-29 11:35:53 : <KTD>  KTD is enabled, in PATHS mode.
2006-09-29 11:35:53 : <KTD>  Copy drivers inside "C:\D\M" to "C:\WINDOWS\DriverPacks\D\M".
2006-09-29 11:36:13 : <KTD>  Successfully created the "%KTD%" environment variable, it has been set to "C:\WINDOWS\DriverPacks". It will be available after the next reboot.
2006-09-29 11:36:14 : <KTD>  Successfully updated the DevicePath registry value!
2006-09-29 11:36:37 : <KTD>  Successfully created the .pnf files. KTD has been applied! It will be available after the next reboot.
2006-09-29 11:37:29 : <CLNP> Deleted the DriverPacks, which were located in 'C:\D'.
2006-09-29 11:37:29 : <CLNP> Deleted 'C:\hwids.dat'!
2006-09-29 11:37:29 : <CLNP> Deleted 'C:\DPsFnshr.ini'!
2006-09-29 11:37:29 : <CLNP> Deleted 'C:\devcon.exe'!
2006-09-29 11:37:29 : <CLNP> Deleted 'C:\makePNF.exe'!
2006-09-29 11:37:29 : <CLNP> Deleted 'C:\addUsepmtimer.exe'!
2006-09-29 11:37:29 : <CLNP> Deleted 'C:\ATICCC.ins'!
2006-09-29 11:37:29 : <CLNP> Added new value to the RunOnce key in the registry: the DriverPacks Finisher itself will get deleted after the next reboot.
2006-09-29 11:37:29 : Program terminated.
  • From: Hasselt, Belgium
  • Registered: 2006-05-26
  • Posts: 2,609

Re: [NEEDS REPLY] Install works on Virtal PC but get BSOD on actual PC

Can you post the exact error code that was shown in the BSOD?

Founder of DriverPacks.net — wimleers.com

Wim Leers's Website

  • Tim545
  • DriverPacks newbie
  • Offline
  • Registered: 2006-10-01
  • Posts: 8

Re: [NEEDS REPLY] Install works on Virtal PC but get BSOD on actual PC

The BSOD appears for only an instant before the system reboots.  I don't know how to get this info.  Is there a way?

  • From: Hasselt, Belgium
  • Registered: 2006-05-26
  • Posts: 2,609

Re: [NEEDS REPLY] Install works on Virtal PC but get BSOD on actual PC

Tim545 wrote:

The BSOD appears for only an instant before the system reboots.  I don't know how to get this info.  Is there a way?

I quickly made an FAQ topic about that.

Founder of DriverPacks.net — wimleers.com

Wim Leers's Website

  • Tim545
  • DriverPacks newbie
  • Offline
  • Registered: 2006-10-01
  • Posts: 8

Re: [NEEDS REPLY] Install works on Virtal PC but get BSOD on actual PC

DRIVER_IRQL_NOT_LESS_OR_EQUAL
Tech Info:
*** STOP: 0x000000D1 (0x00000000,0x00000002,0x00000000,0xF6DFBA96)

I hope that means something to you.  Remember, I have attempted to update my drivers from a CD.  I could do a fresh install if it would help.

Sorry my questions forced you to add an FAQ entry.

  • Jaak
  • Old Timer Rookie
  • Offline
  • From: Eeklo, in the East Flanders
  • Registered: 2006-07-23
  • Posts: 3,594

Re: [NEEDS REPLY] Install works on Virtal PC but get BSOD on actual PC

hi

what slot is that PCI SATA card plugged into?
Some moboes have master PCI slots, and the slot closest to AGP is (based on experience) not the best place for a extra controller, since it shares a hardwired IRQ-line with AGP.

it's just a gutfeeling.

Last edited by jtdoom (2006-10-01 09:44:30)

The answer was 42?
Kind regards, Jaak.
  • Tim545
  • DriverPacks newbie
  • Offline
  • Registered: 2006-10-01
  • Posts: 8

Re: [NEEDS REPLY] Install works on Virtal PC but get BSOD on actual PC

jtdoom & Bashart,

I didn't modify my system whasoever from the previous install.  What I did was simply replace the existing C: drive with one I had as a spare for testing my first install.  Following jtdoom's recommendation, it occurred to me -- I'm not booting off the SIIG card, but off the MB IDE.  I remember several years ago that I had a terrible time getting my system to recognize it AND it was moving the card to a different slot that solved my problem (but I had forgotten all about that).  There are only two cards in the system, the video card and this SIIG card.  I just pulled the card out of my system (it's used for additional drives I want to add later that my MB will not support) and it booted into windows with the following error message "Files that are required for Windows to run properly have been replaced by unrecognized versions.  To maintian system stability Windows must restore the original versions of the files.  Insert your Windows XP Pro Service Pack 2 CD now."  Which I did, but I was told this was the wrong CD.  So I inserted Win XP Pro.  It didn't like that either.  So I ignored the error message and came up into windows.  I shut down and reinserted the SIIG card (it was two slots away from the video card, so I move it three over) and it booted into Windows.  The system is EXTREMELY slow.  From startup screen on it very slow.

I was surprised that moving the SIIG card would make a difference because I built it with everything in the same locations on previsous manual rebuild.

Is it possible I did something wrong slipstreaming things together for the slowness to being occuring?

Thank you both for your help.

  • Tim545
  • DriverPacks newbie
  • Offline
  • Registered: 2006-10-01
  • Posts: 8

Re: [NEEDS REPLY] Install works on Virtal PC but get BSOD on actual PC

The slow problem with my Win install as something to do with Windows Explorer.  If I attempt to use it and have the Task Manager running it hangs and say Not Responding, they without doing anything, I have a second one running with same message.  I can't get it to work.  Tomorrow I think I'll simply try a fresh install using same boot DVD disk.

  • From: Hasselt, Belgium
  • Registered: 2006-05-26
  • Posts: 2,609

Re: [NEEDS REPLY] Install works on Virtal PC but get BSOD on actual PC

1) What is SIIG? It's just a brand, right? And it actually is a SATA controller? Please tell me the full product name so I can verify that a driver that supports this device is present.
2) The DriverPacks Finisher automatically runs during the first login, which is in your case during the logging in into safemode. Nothing odd about that.
3) I'd suggest that you reinstall your system, keeping the SIIG card in its new location.

Moved to DriverPack MassStorage.

Founder of DriverPacks.net — wimleers.com

Wim Leers's Website

  • Tim545
  • DriverPacks newbie
  • Offline
  • Registered: 2006-10-01
  • Posts: 8

Re: [NEEDS REPLY] Install works on Virtal PC but get BSOD on actual PC

1. Correct.  I'm trying to come up-to-speed here quickly.  I have a SIIG USB2.0+1394+UltraATA 133 RAID card that purchased and install several years ago.  It has been nothing but problems for me.  I have a different vendors card installed on another system that has not caused me such problems.  BTW, SIIG offers terrible tech support.  Sorry Bashrat for using incorrect terminology here.  I very much respect and appreciate what you do.

2. The slowness I was referring to wasn't that of logging into safemode, which I did often, but when I finally succesfully logged in from normal startup.  I'm certian "something" is messed up with Windows Explorer, I simply don't know what it is.

3. I will reinstall.  I've been out with a cold for a couple lost days.  I was thinking about simply removing this card for a fresh install, then adding it back in later, but based on your comment I will leave it where it is to see of things work.

  • Jaak
  • Old Timer Rookie
  • Offline
  • From: Eeklo, in the East Flanders
  • Registered: 2006-07-23
  • Posts: 3,594

Re: [NEEDS REPLY] Install works on Virtal PC but get BSOD on actual PC

it booted into windows with the following error message "Files that are required for Windows to run properly have been replaced by unrecognized versions.

couple days ago I had that too, but it went on after I had put in the slipstreamed CD.
(I thought it could be Nlite messing up something.. so did not report this)

Tim545, There WAS a bad 6.09 base file on the server for couple days.
This was replaced last saturday.

I suggest you download a fresh 6.09 BASE .
and, DO keep your copy of 6.08.6. ( 6.08.6 is doing fine here).

for what it is worth.
I would replace a card which was giving me trouble time and again.
Sometimes it is just your luck that it won't work well with your type of motherboard.
I've seen that happen all too often...
I had a really good mobo for testing stuff in years ago. (an Iwill VD133)
a card what had issues in a machine was put in it, and if it had no issues I'd recommend they use another brand/model. I sorta wore out the slots on two such boards...

The answer was 42?
Kind regards, Jaak.
  • From: Hasselt, Belgium
  • Registered: 2006-05-26
  • Posts: 2,609

Re: [NEEDS REPLY] Install works on Virtal PC but get BSOD on actual PC

Tim545 wrote:

1. Correct.  I'm trying to come up-to-speed here quickly.  I have a SIIG USB2.0+1394+UltraATA 133 RAID card that purchased and install several years ago.  It has been nothing but problems for me.  I have a different vendors card installed on another system that has not caused me such problems.  BTW, SIIG offers terrible tech support.  Sorry Bashrat for using incorrect terminology here.  I very much respect and appreciate what you do.

2. The slowness I was referring to wasn't that of logging into safemode, which I did often, but when I finally succesfully logged in from normal startup.  I'm certian "something" is messed up with Windows Explorer, I simply don't know what it is.

3. I will reinstall.  I've been out with a cold for a couple lost days.  I was thinking about simply removing this card for a fresh install, then adding it back in later, but based on your comment I will leave it where it is to see of things work.

1. Unless that card is really crappy, it should work just fine. But considering the issues you've had with it in the past, you may want to buy a decent replacement card.

2. Yes, a reinstall might be desired, if you have such a vague issue.

3. Great. Let me know the results.

jtdoom wrote:

Tim545, There WAS a bad 6.09 base file on the server for couple days.
This was replaced last saturday.

For less than a day, actually wink And that was only the wrong DriverPacks Finisher, it could never result in a BSOD.

Founder of DriverPacks.net — wimleers.com

Wim Leers's Website

  • Registered: 2006-10-30
  • Posts: 1

Re: [NEEDS REPLY] Install works on Virtal PC but get BSOD on actual PC

I had the same issue, tried lots of different things, then I found this:
http://support.microsoft.com/kb/916595
downloaded, installed, no more problem.
Hope this helps...

  • Jaak
  • Old Timer Rookie
  • Offline
  • From: Eeklo, in the East Flanders
  • Registered: 2006-07-23
  • Posts: 3,594

Re: [NEEDS REPLY] Install works on Virtal PC but get BSOD on actual PC

hi
welcome to driverpacks.net

I could be wrong, but I think that one is about another stop error
0xD1000000 is not 0x000000D1

The KB does not warn that this fix is intended for machines with this specific stop ONLY, it is not included in RVM, and automatic updates does not load it.

it is a good find, and I downloaded the localised NL and english versions to have a look at this.

if its broken, try fix it... in this case, worth a shot...

as for me, I will do "it ain't broken, but will fix it anyhow"  and find out if it breaks anything in a virtual machine.

The answer was 42?
Kind regards, Jaak.