If the system crashes
What we need from you if you get a BSOD (system crash)
If you encounter a crash (so-called BSOD), and suspect that our product is the cause of the problem, please take a crash dump and send it to us. Below you will find information about how to enable crash dump generation and collect crash dumps.
Also we need the following information which appears on the Blue Screen of Death (example message follows):
STOP: 0x00000022 (0x00240076, 0xF7A07AA8, 0xF7A077A8, 0xF7800C82) cbdisk2.sys - Address F7800C82 base at F77CD000, DateStamp 447d6975
Enabling a Kernel-Mode Dump File (© 2005 Microsoft Corporation)
During a system crash, the Windows crash dump settings determine whether a dump file will be created, and if so, what size the dump file will be. The Windows Control Panel controls the kernel-mode crash dump settings. Only a system administrator can modify these settings. To change these settings, go to Control Panel and click on the System icon. Select the Advanced panel. In Windows NT 4.0 and Windows 2000, click on Startup and Recovery. In Windows XP and later versions of Windows, click on the Settings button in the Startup and Recovery section. You will see the Startup and Recovery Dialog Box.
Under Write Debugging Information, you can select which of the three sizes of dump files you wish to have as the default. Only one dump file can be created for any given crash. The default crash dump size is Small Memory Dump. See Varieties of Kernel-Mode Dump Files for a description of the three file types. After selecting the dump file size, you can accept or change the default dump file path and file name. You can also select or deselect any of the Write an event to the system log, Send an administrative alert, and Automatically reboot options. If you make any changes, the system will reboot after you click OK. The settings that you select will apply to any kernel-mode dump file created by a system crash, regardless of whether the system crash was accidental or whether it was caused by the debugger. See Forcing a System Crash for details on causing a deliberate crash. However, these settings do not affect dump files created by the .dump command. See Creating a Dump File Without a System Crash for details on using this command.
If the system hangs (is stuck)
In this situation we need to create a memory dump (see above). To initiate a crash do the following:
You must ensure the following three settings before the keyboard can cause a system crash: If you wish a crash dump file to be written, you must enable such dump files, choose the path and file name, and select the size of the dump file. For more information, see Enabling a Kernel-Mode Dump File.
- With PS/2 keyboards, you must enable the keyboard-initiated crash in the registry. In the registry key HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\i8042prt\Parameters, create a value named CrashOnCtrlScroll, and set it equal to a REG_DWORD value of 0x01.
- With USB keyboards, you must enable the keyboard-initiated crash in the registry. In the registry key HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\kbdhid\Parameters, create a value named CrashOnCtrlScroll, and set it equal to a REG_DWORD value of 0x01.
You must restart the system for these settings to take effect.
After this is completed, the keyboard crash can be initiated by using the following hotkey sequence: Hold down the rightmost CTRL key, and press the SCROLL LOCK key twice.