In some cases the reason for a bluescreen or page fault exception without call stack can be analyzed by Beckhoff. These are the steps to provide all necessary data for analyzation:
- Open the startup and recovery settings on the target system:
Control Panel > System and Security > System Advanced system settings > Advanced > Startup and Recovery Settings
- Select the option kernel memory dump and activate the checkbox for overwriting existing files:
- Close the dialog with OK.
Do you get following error?
Only if you get this error:
Open the virtual memory settings on the target system:
Control Panel > System and Security > System > Advanced system settings > Advanced > Performance Settings > Advanced > Change virtual memory
Then activate the checkbox to automatically manage paging file size for all drives, acknowledge all dialogs with OK and restart Windows.
- This step is only necessary if you do not get a dump file (MEMORY.DMP), for example in case of an exception without call stack:
Add following registry key as DWORD (32-bit) with value 1 in the Registry Editor on the target system:
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Beckhoff\TwinCAT3\System\ForceExceptionMemoryDump
Attention: This registry key causes a system crash instead of a page fault exception. After analyzation you must reset this key to 0 or delete it.
- Restart Windows of the target system.
- Reproduce the bluescreen or exception.
- Copy the dump file from the target system:
C:\Windows\MEMORY.DMP
- Copy the whole content of the TwinCAT boot folder from the target system:
C:\TwinCAT\3.1\Boot\
It usually contains a copy of the PLC project if you have used the Control plus default settings in TwinCAT:
- If your TwinCAT version provides following update function execute it on your development system:
- Make a copy of the PLC project on your development computer (...\Stat000\Plc\).
- Send all data (MEMORY.DMP, boot folder, Plc project) to your local Beckhoff contact via fileexchange.beckhoff.com or ask the Nexeed helpdesk.