help-octave
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Octave 5.1 and 5.2 crashing on Windows 10


From: Kai Torben Ohlhus
Subject: Re: Octave 5.1 and 5.2 crashing on Windows 10
Date: Fri, 28 Feb 2020 12:28:45 +0900
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.5.0

On 2/28/20 7:19 AM, John Frain wrote:
> Has any other user detected the following problem or perhaps know of a
> solution?   
> 
> I am running Windows 10 1909 64-bit.
> 
> I have been using Octave in Windows (and Linux) for many years with
> great success.  When I tried to start octave 5.1 using the a white
> screen appeared with the octave icon and the word octave on the top
> left-hand corner of the screen and it crashed immediately. the cli
> version continued to work.  
> 
> I decided to update to 5.2 and downloaded
> octave-5.2.0_1-w64-installer.exe and installed. When the install was
> finished the readme was displayed but the gui version of octave did not
> start or had crashed before I closed the readme file. The cli version of
> octave worked as expected
> 
> I have since installed today's windows update - previous updates had
> been installed.  I have uninstalled both versions of octave and
> reinstalled 5.2.  (5.2 several times).
> 
> There are a lot of applications on this PC e.g. R, Rstudio, Maxima,
> Libre Office, Gretl, Texstudio, Tex-Live, Anaconda,  etc. etc.  All of
> these work perfectly.  Any of the versions of the octave program when
> run in a console window with or without gui or force-gui options default
> to the cli version.  Emacs octave mode works fine.
> 
> The windows event viewer gives the following error message.  It is
> strange that octave alone picks out the problem with the dntdll.dll file.
> 
> Faulting application name: octave-gui.exe, version: 0.0.0.0, time stamp:
> 0x00000000
> Faulting module name: ntdll.dll, version: 10.0.18362.657, time stamp:
> 0x64d10ee0
> Exception code: 0xc0000374
> Fault offset: 0x00000000000f92a9
> Faulting process id: 0x22ac
> Faulting application start time: 0x01d5ed84236f5f57
> Faulting application path: C:\Octave\OCTAVE~2.0\mingw64\bin\octave-gui.exe
> Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
> Report Id: 4f945789-a789-4d34-8dc9-45ec135e357e
> Faulting package full name:
> Faulting package-relative application ID: 
> 
> John C Frain, Ph.D.
> 
> Economics Department             3 Aranleigh Park
> Trinity College Dublin                 Rathfarnham
> College Green                           Dublin 14
> Dublin 2                                    Ireland
> Ireland
> www.tcd.ie/Economics/staff/frainj/home.htm
> <http://www.tcd.ie/Economics/staff/frainj/home.htm>
> mailto:address@hidden <mailto:address@hidden>
> mailto:address@hidden <mailto:address@hidden>
> 
> 

Did you use Octave 5.1 GUI until that day when you saw a white screen
only?  Or did you use an older version of Octave before?

An often occurring problem are stale config files, when having installed
older versions of Octave on the same MS Windows system before.

Did you try to remove the folder

   C:\Users\YOUR_USER_NAME\.config\octave

before starting Octave?

HTH,
Kai



reply via email to

[Prev in Thread] Current Thread [Next in Thread]