Sign up now and we'll notify you when your product is ready for testing.
Product(s): PerfectDisk 10 Professional, PerfectDisk 11 Professional, PerfectDisk 2008 Professional, PerfectDisk 10 Home, PerfectDisk 11 Home, PerfectDisk 11 VMware Workstation, PerfectDisk 10 VMware Workstation
Last Update: 05/21/10
Windows Version(s): Windows 7,Windows Vista,Windows XP,Windows Home Server,Windows Server 2008,Windows Server 2003,Windows 2000
There are only 2 things that can cause Windows to crash:
There are several 3rd party software programs that have drivers that are known to cause Windows to crash when PerfectDisk is run on the system:
| Software | Driver Name |
| IBM's Rapid Restore | ibmfilter.sys - update available from IBM |
| EMC/Legato's RepliStor | replistor.sys - fixed in RepliStor Version 6 |
| New Softwares Folder Lock | WinDrvNT.sys - Fixed in FolderLock 6 |
| Hide Folder | HF30XP.sys - contact Hide Folder technical support for assistance |
| Universal Shield/Lock Folder | US30XP.sys - update available from Everstrike |
| BitDefender/FileSpy | filespy.sys and bdfsdrv.sys - fixed in BitDefender V10 |
| Kerio Personal Firewall | fwdrv.sys - update available from Kerio |
| INVISUS PC Security Solution | fwdrv.sys - INVISUS uses an older Kerio driver that has this bug. Contact INVISUS for assistance. |
| Norton Internet Security | SPBBCDrv.sys |
| RamDiskXP | ramdiskxp.sys - contact Cenatek, the developer of RamDiskXP, for assistance |
| WinAntiVirus PRO | fopn.sys - contact WinSoftware technical support for assistance |
| Window Vista | Bug in ntfs.sys will cause Windows Vista to crash when defragmenting external drives. Raxco has confirmed that this bug in NTFS has been fixed in Vista SP1 |
| WebSense | wscam6300.sys - fixed in wscam6300.sys version 6.3.1.102 |
| F-Secure | fssm32.exe 5.43 build 10371 - contact F-Secure technical support for assistance |
Please check to see if you have any of the listed programs installed on your computer and click on the appropriate link above for suggested workarounds or bug fixes from the program manufacturer.
If you do not have any of the listed programs installed, then Raxco Technical Support can assist in identifying the 3rd party driver that is causing Windows to crash. In order to identify the 3rd party driver, Windows will need to be configured to write a memory dump on Windows crash via the steps below:
After Windows has been configured to write a memory dump, re-create the crash. Windows will create a file called memory.dmp that can be found in the Windows folder if you are running Windows XP/Vista or the WINNT folder if you are running Windows 2000.
After Windows has written this dump file, please contact Raxco Technical Support and we will provide instructions on how to get this dump file to us so that we can analyze and tell you what 3rd party driver has caused Windows to crash. Raxco can then notify both Microsoft and the 3rd party software developer that there is a bug with the indicated driver.
