Application crash log file

For example, this issue may occur in the following scenario:. One user logs off. This causes the other users of the application to experience an application crash or unresponsiveness. Depending on the OS version, this issue occurs when either the first or last user of the application logs off, as follows:. This issue occurs because of the way that the redirector handles the File Control Block FCB for the binary in question.

When the first user logs off, the FCB is orphaned. This causes the application to crash or become unresponsive on subsequent uses. In Windows Server R2, the FCB is owned by the last user who opened the file, and previous users experience the issue when the last user logs off. Technically the FCB is not owned by any specific user. It's just a shared structure that represents a file.

Privacy Policy Update. When a program crashes the process has stopped working or disappears , an event log file can be helpful for the development team to troubleshoot problems. Follow the steps below to find event logs:. By using the website, you agree to our use of cookies. Head to our cookie statement to learn more about cookies and manage cookies on this website. Hi, Firstname Lastname. View Account. Sign Out.

Creative Suite Director Suite. Video Editing PowerDirector. View All Products. Volume Licensing. Becoming an Affiliate. Thanks for reading! Justin is a technical writer. When he's not writing, there's a 99 percent chance he's reading, playing video games or listening to music. Follow these steps: Just follow the steps below and you should be able to view all the crash logs easily in Windows 10!

Configure the advanced system settings of your Windows 10 operating system Open Event Viewer Create a custom view Export the crash logs Step 1: Configure the advanced system settings of your Windows 10 operating system To make full use of Event Viewer , you need to configure the advanced system settings of your Windows 10 OS. On your keyboard, press the Windows logo key and R at the same time to open the Run dialog. Type control and then press Enter to open the Control Panel.

Type advanced in the search box in the upper-right corner and then click View advanced system settings. Navigate to the Advanced tab and then click Settings… in the Startup and Recovery section. Configure the settings in the System failure section the same way you see on the screenshot below. Then click OK to save the changes. Note: The option Automatically restart has little to do with Event Viewer.

By unchecking the box next to Automatically restart , you tell Windows 10 not to reboot and to save the crash dump file when there is a system failure. If you check this box, you may not see the BSOD error message. Then select Event Viewer to open it. There are 2 methods to view the information of a certain event: Start from the left panel to view events Start from Summary of Administrative Events to view events Start from the left panel to view events In the left panel, double-click a category to expand it.

Click one event in the list and the detailed information will show up in the bottom of the window. Step 3: Create a custom view By creating a custom view , you can view the crash logs more quickly.

Here is how to do it: In the left panel, click Event Viewer Local in the left panel. In the Actions section, click Create Custom View…. In the pop-up window, under the Filter tab, click the downward arrow next to Logged to select a time range. Then check the boxes before Critical , Warning and Error to select the Event levels. Click the By log option button to create the custom view by log.