Igor Pro 8 crashes with exception code 0xc0000005

Share icon

Fri, 04/14/2023 - 09:26 am

I have been using Igor Pro 8 for 6 months now and since yesterday it started to crash without warning. Igor Pro 8 just closes and gives no error messages. The computer is running Windows 10 64-bit. Looking in windows event logs, we found the following reports from the latest crash. Does anyone know what causes these crashes and how to fix them? Thank you.

—-----------------------------------------------------------------------------------------------------------

Logged: 4/14/2023 11:28:55 AM

Log Name: Application

Source: .NET Runtime

 

Application: Igor64.exe

Framework Version: v4.0.30319

Description: The process was terminated due to an unhandled exception.

Exception Info: exception code c0000005, exception address 00007FF7598799F0

—--------------------------------------------------------------------------------------------------------------

Logged: 4/14/2023 11:28:55 AM

Log Name: Application

Source: Application Error

 

Faulting application name: Igor64.exe, version: 8.0.4.2, time stamp: 0x5dd3f8e8

Faulting module name: Igor64.exe, version: 8.0.4.2, time stamp: 0x5dd3f8e8

Exception code: 0xc0000005

Fault offset: 0x0000000006eb99f0

Faulting process id: 0x3500

Faulting application start time: 0x01d96e4dc3b2d95e

Faulting application path: C:\Program Files\WaveMetrics\Igor Pro 8 Folder\IgorBinaries_x64\Igor64.exe

Faulting module path: C:\Program Files\WaveMetrics\Igor Pro 8 Folder\IgorBinaries_x64\Igor64.exe

Report Id: 5abfa6d7-3410-4e37-8286-3d9bf175fd9a

Faulting package full name: 

Faulting package-relative application ID: 

—----------------------------------------------------------------------------------------------------------

 

 application error log .NetRuntime error log

Please execute the following command on Igor's command line:

DisplayHelpTopic "Crashes On Windows"

Then follow the instructions there. The exception cited in your report is a simple crash due to Igor accessing memory that it shouldn't access, but there is no way to determine the cause of the crash from that exception code. Greater than 90% of crashes are caused by that same code.

April 14, 2023 at 09:38 am - Permalink