ONE TIMING crashes without an Error-Message
If ONE TIMING crashes without displaying any additional error messages, it is important to inform PACETEQ about the crash. Please make sure to provide the Windows Crash Logs and any other relevant information about the circumstances surrounding the crash.
Contact PACETEQ
If ONE TIMING crashes without displaying an error window automatically, it is crucial to promptly inform PACETEQ about the issue.
You can create a ticket via support.paceteq.com.
Required Information, Windows Crash Logs
If a crash occurs without displaying an error message, it is crucial to include the Windows Crash Logs directly.
Here are the steps to save the Windows Event Viewer logs:
1. Open Event Viewer: You can open the Event Viewer by typing "Event Viewer" in the Windows search bar and clicking on "Event Viewer" in the search results.
2. Navigate to the desired log: In the left panel, navigate to "Windows Logs" and click on "Application."
3. Select "Find" in the right-hand pane and enter "OneTiming". This should find the latest OneTiming report from today
Please export both, the Application Error and .NET Runtime errors. They should look each something like this (although errors will be different):
Application Error:
Faulting application name: OneTiming.exe, version: 1.0.0.0, time stamp: 0x6492f9b1
Faulting module name: KERNELBASE.dll, version: 10.0.19041.3086, time stamp: 0xe1ac3f79
Exception code: 0xe0434352
Fault offset: 0x000000000002cf19
Faulting process id: 0x5b78
Faulting application start time: 0x01d9a44389c863ce
Faulting application path: C:\paceTeq\repos\onetiming\OneTiming\bin\Debug\OneTiming.exe
Faulting module path: C:\Windows\System32\KERNELBASE.dll
Report Id: 3a7e0781-1d0d-4f9f-a665-6a9c9309208f
Faulting package full name:
Faulting package-relative application ID:
.NET Runtime
Application: OneTiming.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.IO.FileNotFoundException
at System.Reflection.RuntimeAssembly._nLoad(System.Reflection.AssemblyName, System.String, System.Security.Policy.Evidence, System.Reflection.RuntimeAssembly, System.Threading.StackCrawlMark ByRef, IntPtr, Boolean, Boolean, Boolean)
4. Export the log: Right-click on any event in the filtered list and select "Save Selected Events." Choose a location to save the file and select "EVTX" as the file format.
This will create a record of the events in the log file, which can be used for troubleshooting in case of a program crash.
Additional Information
Providing your current layout and additional details on active sessions during the crash, along with any other relevant information such as network stability or first-time use of ONE TIMING on this PC, can be beneficial for troubleshooting purposes.