10-20-2015, 03:49 AM
My Win7 system has similar erratic crashes/restarts with Version 1.7.0
System is dual quad Xeon (old Dell T5500). Using VCOM to connect to Serial GPS over LAN.
NTP is Disabled.
Almost always bkttimesync restarts OK.
On the 10 recent cases I checked, the Fault Offset was always 0x0000cf69 (of course the Process id varied):
---Example---
Faulting application name: BktTimeSync.exe, version: 1.7.0.0, time stamp: 0x54df1300
Faulting module name: BktTimeSync.exe, version: 1.7.0.0, time stamp: 0x54df1300
Exception code: 0xc0000005
Fault offset: 0x0000cf69
Faulting process id: 0x1be4
Faulting application start time: 0x01d0d594283b9a02
Faulting application path: C:\Program Files (x86)\BktTimeSync\BktTimeSync.exe
Faulting module path: C:\Program Files (x86)\BktTimeSync\BktTimeSync.exe
Report Id: 6e857c7b-41ca-11e5-9ecc-00256497738f
---
In the Event Log: Application there are 3 separate Event Id's:
- EventID 1000
- EventID 9010
- EventID 1001
I've now Enabled the Diagnostic Log.
BTW: After closing the GUI the Log was still locked; I found a bkttimesync.exe still running. I used Task Manager to kill it.
I tested Run/Close again & it terminated properly; when it crash/restarts again, I'll look for multiple bkttimesync.exe's
Q: Is it worth experimenting with Compatibility Mode?
Thanks, Roger.
System is dual quad Xeon (old Dell T5500). Using VCOM to connect to Serial GPS over LAN.
NTP is Disabled.
Almost always bkttimesync restarts OK.
On the 10 recent cases I checked, the Fault Offset was always 0x0000cf69 (of course the Process id varied):
---Example---
Faulting application name: BktTimeSync.exe, version: 1.7.0.0, time stamp: 0x54df1300
Faulting module name: BktTimeSync.exe, version: 1.7.0.0, time stamp: 0x54df1300
Exception code: 0xc0000005
Fault offset: 0x0000cf69
Faulting process id: 0x1be4
Faulting application start time: 0x01d0d594283b9a02
Faulting application path: C:\Program Files (x86)\BktTimeSync\BktTimeSync.exe
Faulting module path: C:\Program Files (x86)\BktTimeSync\BktTimeSync.exe
Report Id: 6e857c7b-41ca-11e5-9ecc-00256497738f
---
In the Event Log: Application there are 3 separate Event Id's:
- EventID 1000
- EventID 9010
- EventID 1001
I've now Enabled the Diagnostic Log.
BTW: After closing the GUI the Log was still locked; I found a bkttimesync.exe still running. I used Task Manager to kill it.
I tested Run/Close again & it terminated properly; when it crash/restarts again, I'll look for multiple bkttimesync.exe's
Q: Is it worth experimenting with Compatibility Mode?
Thanks, Roger.