- From FredBh: The Alps filter driver product version less than 5.3 should be blocked from installation. XP will BSOD with this driver as it touches invalid memory addresses. The mouclass driver will work just fine and support the touchpad. The filter only provides some valueadd functionality. - Customer Impact: About 40% of laptops use this driver and touchpad. ITS HUGE. - From Bug: Alps touchpad drivers no longer mentioned in upgrade report. - Entry has been modified to handle the driver properly for upgrade. - Changed name from Alps Touchpad to the Alps Pointing-device. - Destroys pagefile. - v1.0.0.6 driver's LINK_DATE is "03/22/2000 14:17:07". This driver doesn't seem to trash the pagefile. - The driver block entry on this application has been commented out per Georger's request and converted to a WINNT_UPGRADE entry to warn users at time of upgrade about the bad driver. - This is a case where a driver is trying to write to protected kernel memory. The application causes a bug check upon launch. - The driver block entry on this application has been commented out per Georger's request and converted to a WINNT_UPGRADE entry to warn users at time of upgrade about the bad driver. - There will be no entry in the upgrade report because the driver is installed to the applications directory. - AVM Ken! installs a network driver which causes a bluescreen under WinXP. - The driver block entry on this application has been commented out per Georger's request and converted to a WINNT_UPGRADE entry to warn users at time of upgrade about the bad driver. - per chasat Otman5.sys causes blue screen on clean installs and upgrades to Whistler. This problem does not occur on Win2k. It repros on Whistler and upg's to Whistler 100% - this driver is installed on both client and server, so we can't punt to server Affected Applications: Cristie Data Products Ltd - PC Bax DuoCor - XactCopy E-Vault - Network Data Protection Teradactyl - TIBS (True Incremental Backup System) VERITAS- Backup Exec 8.5 VERITAS- NetBackup VERITAS -NetBackup Professional - added block for scsiopt.sys which blue screens on reboot - added blocks 04mmdat.sys, 0archqic.sys,0dlttape.sys, 0exabmqic.sys, 0exabyte1.sys, 0exabyte2.sys, 0tandmqic.sys, 0tandqic.sys, 0wangqic.sys, 0wangqic2.sys, halfinch.sys, sonysdx.sys, tratapi.sys, and trscsi.sys, and increased scsiopt.sys to 4.x per VERITAS - From Bug: This driver bugchecks when launched and appears to be passing in a NULL pointer. - Easy CD Creator less than 4.03 is bad and installs drivers that bugcheck. - Matching info for 4.02e and 4.03 are included here for reference - Easy CD Creator 5 installs TakeTwo PrtSeqRd.sys upperfilter driver that is not supported anymore in 5.3.1.154. - This driver has problems in Windows Server 2003 that prevent VolSnap to snap volumes properly and causing bugcheck 0x7b. - Combined multiple entries for cdr4vsd.sys and cdr4_2k.sys to have one appshelp meesage under CD Recording Software as requested by Roxio. - This is a case where a driver is trying to write to protected kernel memory. The application causes a bug check upon launch. - Modified version information to be based on link_date since the product version was not updated for later versions of the driver. - This driver does not support Windows Server 2003 and needs to be disabled for the upgrade to continue. - per cpiccini: - Clean install W2K. Install Conexant softmodem using vendor drivers from web or on a pre-install. - Upgrade to XP. During upgrade your Winachsf.sys will cause a C4 Bugcheck and or reference a null pointer. Per CPiccini: System locks on installation/upgrade with driver and hardware loaded under XP Added UPTO_LINK_DATE="07/01/2001" - Driver attempts to read from hardcoded address 0xa000003c - 0xa0000000 is where win32k.sys would load in win2k without 3gb and TS. - Confirmed this driver bluescreens with Win2k under such a scenario - Bad driver that we tested with has LINK_DATE="02/19/1999 18:43:50" - The driver block entry on this application has been commented out per Georger's request and converted to a WINNT_UPGRADE entry to warn users at time of upgrade about the bad driver. - This is a case where a driver is trying to write to protected kernel memory. The application causes a bug check upon launch. - Modified the current matching information for dne2000.sys and added an entry for dne.sys. - Modified existing entry to handle upto 2.0.5 down from 2.0.6.7 - DirectCD driver (cdudf.sys) up to PRODUCT_VERSION="3.01e (192S5)" or BIN_PRODUCT_VERSION="4.3.1.192" has problem and causing Bugcheck. - Added matching info to match on bad 5.x drivers - Added matching info to match on upto 3.05 drivers - Beta feedback has been overwhelming. Users do not care that there is a BSOD on shutdown. They want to be able to write to their CDs. Since 3.05 does not have problems with DVD drives like 5.0 and 5.01 do, revert the 07/03/2001 change. - The below driver bug checks under WinXP when trying to write to read only memory. - The driver block entry on this application has been commented out per Georger's request and converted to a WINNT_UPGRADE entry to warn users at time of upgrade about the bad driver. - This driver bugchecks the system with error code 0xa when the device is installed - Their next version [1.0.1.0] works fine on Windows XP - per ValW from exchange team: - Currently when we attempt to install E2K SP1 on Whistler, we blue screen. - Problem is IFS driver (exIFS) touches the device object after it had already been dereferenced while unloading the driver. - per gregmar from Enterprise Server team: - Currently when an attempt to upgrade from W2K to Windows Server 2003 with File and Print Services for Netware, there is blue screen at reboot everytime. - The blue screen also happens with a clean install of Windows Server 2003 The problem is with the FPNWSRV.SYS driver - as the NWSSVC service tries to start, the FPNWSRV.SYS is loaded at boot and results in a STOP 0X7E. - Issa needs to provide internal only description. description: - per dgolds and paul terry of CA versions of INO_FILTR.sys prior to 5/1/2001 link date cause - bluescreens or hung setup on OS upgrades and under clean installs of Windows XP. These versions - of the driver are just incompatible with Windows XP. - This driver bugchecks the system with error code 0x5 when the system boots up - This driver is installed as part of the IomegaWare 3.0.6 suite - Their next version [3.1] appears to work fine on Windows XP - Because the new driver has the same BIN_PRODUCT_VERSION, the UPTO_LINK_DATE attribute needs to be used - Driver bluescreens system after reboot. - Bluescreens on boot. - Increased version # from 1.28.0.0 to 2.638.0.0. They still haven't fixed these problems. - per vupham, massau, atkura, spowers: - Upgrade : System Crashes in NEC IEEE1394 Network Driver for W2K after Upgrade W2k to XP - Driver is preloaded on NEC Win2K machines - Renamed Driver Name as per company request. - Norton Speed Disk installs a driver which bugchecks under XP. Blocking the driver per Symantec's Leo Cohen's request. - (From FredBh and HiroI) The NEC OneTouchStartButton filter driver (product version less than or equal to 5.0.2195.7) should be blocked from installation. XP will BSOD with this driver load, for example on OS upgrade. - Customer Impact: NEC Jpn keyboards have this issue. NEC wants to prevent people from reloading these drivers of Win2k CD. - Blocking pavdrv.sys UPTO_BIN_PRODUCT_VERSION="5.0.2195.0" per dgold's request. This will allow the latest version of the driver, BIN_PRODUCT_VERSION="5.0.2195.1" to still function under XP. - per nitapan and peterwie - machine hangs at boot when driver is loaded: - driver tried to allocate 10 map registers but was only given 8. - It didn't notice that and then tried to perform and i/o which required all ten. Since 10 will never be avaialble the i/o will simply hang until the end of tiem. - newer versions work, only revision 1.10.6.0 is bad - per nitapan, shawm, peter cook: - bluescreens on upgrades and clean installs - a flat out mess - BIN_PRODUCT_VERSION="5.0.2195.176" works without bluescreening - This driver bugchecks the system with error code 0x9 when the device is connected - Their next version [4.2.3.20] works fine on Windows XP - The driver block entry for this application has been commented out and converted to a WINNT_UPGRADE entry to warn users at time of upgrade about the bad driver. - Sony 1394 driver submitted by SPowers. Bluescreens on WinXP. - Writes directly to the kernel service tables. NT 5.1 made these tables read only, so this driver bluescreens on boot. - New driver is still writing to the tables (a bad thing) but at least now they change the pages to read/write before clobbering them so there is no bluescreen. - Changed UPTO_BIN_PRODUCT_VERSION to 10.3.1.13 (from 10.3.1.12). - Issa needs to provide internal only description. - per KKusaba: - The driver causes the system crash during upgrade from Win2k to XP. - When the driver is loaded, XP will crash. - When the user uses the utility app for the audio player, XP will crash. - Phoenix will release a fixed version of driver by the time XP ships. - The version number of the fixed driver will be 1.2. - per KKusaba: - The driver causes the system crash during upgrade from Win2k to XP. - When the driver is loaded, XP will crash. - When the user uses the utility app for the audio player, XP will crash. - Phoenix will release a fixed version of driver by the time XP ships. - The version number of the fixed driver will be 1.2. - per KKusaba: - The driver causes the system crash during upgrade from Win2k to XP. - When the driver is loaded, XP will crash. - When the user uses the utility app for the audio player, XP will crash. - Phoenix will release a fixed version of driver by the time XP ships. - The version number of the fixed driver will be 1.2. - per KKusaba: - The driver causes the system crash during upgrade from Win2k to XP. - When the driver is loaded, XP will crash. - When the user uses the utility app for the audio player, XP will crash. - Phoenix will release a fixed version of driver by the time XP ships. - The version number of the fixed driver will be 1.2. - fastcdmp.sys is using SeCreateClientSecurity (paged function) at DISPATCH_LEVEL. This is illegal way to call that function since there is no way for fastcdmp.sys to lower IRQL to passive level in order to call that function. - The driver block entry on this application has been commented out per Georger's request and converted to a WINNT_UPGRADE entry to warn users at time of upgrade about the bad driver. - (From FredBh) The Xircom USB to Serial driver (product versions below 2.5) should be blocked from installation. XP will BSOD both during setup and after setup with this driver. Just NTCompat fix is not enough. BSOD is consistant. Customer has to unplug this device and never replug it in. NO UNINSTALL UTILITY. - This problem is caused by the bug of YAMAHA driver. The driver has a routine to identify the version of OS. But there's a bug and the version of PortCls is updated at this XP SP1, then the driver fails to identify the version and fails to retrieve the necessary values then crash. YAMAHA is currently working on a fix. The version of fixed driver will be 6.13.10.2151 for YACXG.SYS and 6.13.10.3151 for YACXGC.SYS. - The application causes a blue screen under WinXP on boot with the following error: DRIVER_IRQL_NOT_LESS_OR_EQUAL. - The following entries will block the driver in Windows XP, and list the driver in the NT migration report as incompatible. - The latest version of the application, v2.6, installs an updated vsdatant.sys driver which also causes a BSOD. Modified the matching info to handle versions up to the latest. - Per GeorgeR (and others), removing driver block but leaving NTCOMPAT warning/disable of the driver. See dbu.xml for the WINNT_UPGRADE entry (APP NAME="ZoneAlarm"). - Adding in driver block for the newest versions of vsdatant.sys that we know about. The application blue screens again under windows server 2003.