teamviewer.com link icon
or
Ask The Community

Version 15 Crashing Often

Latest version of teamviewer 15 just keeps on crashing. My computer is running a newly installed Windows 10 x64 Pro 1909. It stay connected to the internet all the time. No sleep here.

Crashes 1-2 a day, random times

Faulting application name: TeamViewer.exe, version: 15.1.3937.0, time stamp: 0x5df7ae92
Faulting module name: TeamViewer.exe, version: 15.1.3937.0, time stamp: 0x5df7ae92
Exception code: 0xc0000005
Fault offset: 0x01248503
Faulting process id: 0x1aa0
Faulting application start time: 0x01d5cc964583c580
Faulting application path: C:\Program Files (x86)\TeamViewer\TeamViewer.exe
Faulting module path: C:\Program Files (x86)\TeamViewer\TeamViewer.exe
Report Id: 0644640a-ca87-4316-b917-39c5df8bc07b
Faulting package full name:
Faulting package-relative application ID:

 

Comments

  • Ryan_O
    Ryan_O Posts: 1

    Same. Commercial license, sometimes it crashes a few times a day, sometimes it goes a day or two before crashing. 99% of cases the faulting application and module are TeamViewer.exe, but one instance the faulting module was kernelbase.dll All of this began with updating to version 15.

  • MRDC
    MRDC Posts: 3

    Same thing. Dunno what to do... :(

    Faulting application name: TeamViewer.exe, version: 15.1.3937.0, time stamp: 0x5df7ae92
    Faulting module name: TeamViewer.exe, version: 15.1.3937.0, time stamp: 0x5df7ae92
    Exception code: 0xc0000005
    Fault offset: 0x01248503
    Faulting process ID: 0x7248
    Faulting application start time: 0x01d5d3cc1b30f801
    Faulting application path: C:\Program Files (x86)\TeamViewer\TeamViewer.exe
    Faulting module path: C:\Program Files (x86)\TeamViewer\TeamViewer.exe
    Report ID: 
    Faulting package full name:
    Faulting package-relative application ID:

  • Having the same issues with commercial license

    Have opened a support case ID: [The personal information has been removed as per the community guidelines.]

    Untitled.png

  • New version 15.2.... seems to have fix this issue. Thank you!

Sign In or Register to comment.