Skip to content
Customer portal
Contact
  • There are no suggestions because the search field is empty.

ONE TIMING crashes without an Error-Message

If ONE TIMING closes unexpectedly without displaying an error message, collect Windows Crash Logs and contact PACETEQ support for troubleshooting.

Overview

If ONE TIMING crashes without showing any error message or window, it is important to inform PACETEQ support and provide detailed crash information. Supplying Windows Crash Logs and relevant context will help the PACETEQ team diagnose and resolve the issue efficiently.

 

Contacting PACETEQ

If you experience a crash without an error window, please create a support ticket at support.paceteq.com.

 

Required Information: Windows Crash Logs

To assist PACETEQ in troubleshooting, please include the relevant Windows Crash Logs with your support ticket.

How to Save Windows Event Viewer Logs

  1. Open Event Viewer:

    • Type “Event Viewer” in the Windows search bar and select it from the results.

  2. Navigate to Application Logs:

    • In the left panel, expand Windows Logs and click on Application.

  3. Find ONE TIMING Events:

    • In the right-hand pane, select Find and enter OneTiming to locate the latest crash reports.
    • Look for both Application Error and .NET Runtime errors.

    Example: 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:

Example: .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)
  1. Export the Log:
    • Right-click on any relevant event and select Save Selected Events.
    • Choose a location and select EVTX as the file format.

This will create a log file that you can attach to your support ticket for further analysis.

 

Additional Information

When submitting your ticket, please also include:

  • Your current layout file (if possible)
  • Details about active sessions during the crash
  • Any other relevant information (e.g., network stability, first-time use on this PC, recent updates)

Providing as much context as possible will help PACETEQ resolve your issue more quickly.

 

Related Articles