Triggering a Stop Error to test if a Dump File is created!
To ascertain that a dump file is created when a Stop error occurs, you need to simulate a Stop error. You can manually initiate a Stop error by creating a registry value and pressing a special character sequence. Then, after Windows 7 restarts you can verify that the dump file was actually created.
To initiate a crash dump manually, follow these steps:
- Start the registry editor, by typing regedit in the Start menu search text box and press enter. If you get a User Account Control (UAC) prompt, click ok. Remember that you require administrator-level permissions to edit the registry
- In HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\i8042prt\Parameters, create a new DWORD called CrashOnCtrlScroll with a value of 1 as shown below:
Hive: HKEY_LOCAL_MACHINE
Key: SYSTEM\CurrentControlSet\ Services\i8042prt\Parameters
DWORD (32-bit) Value name: CrashOnCtrlScroll
DWORD Value data: 1 - Close the registry editor and then restart the computer
- Log on to Windows 7. While holding down the right Ctrl key, press the Scroll lock key twice to initiate a Stop error.
Note: You cannot manually initiate a Stop error on a virtual machine that has VM extension tools installed.
A word of caution – incorrectly editing the registry may severely damage your system. The above modifications are intended for Windows advanced users who are familiar with the registry editor. Users are also reminded to back up the registry before making any critical changes.