Getting repeated PixInsight crashes on new UHD monitor

[dstevenson]

Hi there.

Bought a nice new UHD monitor and getting lots of PixInsight crashes. I've noticed it has happened a few times when going into documentation (new habit as I've found the documentation is actually quite useful  ).

Is there some debugging I can turn on which will help pd the problem?

David

[jerryyyyy]

I have been getting my share of crashes too but using an LG 4k TV for display.

[Juan Conejero]

This is not reproducible. We test and use PixInsight 1.8.6 regularly on a variety of monitors and screen resolutions, including 4K and 5K monitors on all supported platforms, without any problems.

This is useless as a bug report. Can you share some data to help us identify the problem? A good start might be:

- Your operating system (Windows/macOS/Linux/FreeBSD? which version?)

- A description of your computer (CPU? graphics card? brand?)

- What type of 'crashes'? Error messages? Symptoms?

[jerryyyyy]

I am using a Dell Precision Laptop M5510 Xenon E3  processor with 8 cores.  NVIDIA Quadro M1000M.  Windows 10 1803.

Applications just dies and there is no PI error message.  I was hoping it was just a graphics driver error, but it is in the kernel. 

In the event viewer you get (see below for one other type of crash):

Log Name:      Application
Source:        Application Error
Date:          6/30/2019 7:02:41 AM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      SLE-5B4-422-DGT
Description:
Faulting application name: PixInsight.exe, version: 1.8.6.1457, time stamp: 0x5c472890
Faulting module name: ntdll.dll, version: 10.0.17134.799, time stamp: 0x7f828745
Exception code: 0xc0000374
Fault offset: 0x00000000000f479b
Faulting process id: 0x5ddc
Faulting application start time: 0x01d52f465bb22f69
Faulting application path: C:\Program Files\PixInsight\bin\PixInsight.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: 130375d5-d3b4-414a-bc7c-41b9419bdd4f
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2019-06-30T14:02:41.759956200Z" />
    <EventRecordID>59118</EventRecordID>
    <Channel>Application</Channel>
    <Computer>SLE-5B4-422-DGT</Computer>
    <Security />
  </System>
  <EventData>
    <Data>PixInsight.exe</Data>
    <Data>1.8.6.1457</Data>
    <Data>5c472890</Data>
    <Data>ntdll.dll</Data>
    <Data>10.0.17134.799</Data>
    <Data>7f828745</Data>
    <Data>c0000374</Data>
    <Data>00000000000f479b</Data>
    <Data>5ddc</Data>
    <Data>01d52f465bb22f69</Data>
    <Data>C:\Program Files\PixInsight\bin\PixInsight.exe</Data>
    <Data>C:\WINDOWS\SYSTEM32\ntdll.dll</Data>
    <Data>130375d5-d3b4-414a-bc7c-41b9419bdd4f</Data>
    <Data>
    </Data>
    <Data>
    </Data>
  </EventData>
</Event>

Yesterday there were 3 of there two the same as above, the other cited another dll:

Log Name:      Application
Source:        Application Error
Date:          6/30/2019 6:18:34 AM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      SLE-5B4-422-DGT
Description:
Faulting application name: PixInsight.exe, version: 1.8.6.1457, time stamp: 0x5c472890
Faulting module name: ucrtbase.dll, version: 10.0.17134.677, time stamp: 0x9f346d3f
Exception code: 0xc0000409
Fault offset: 0x000000000006e14e
Faulting process id: 0x68c8
Faulting application start time: 0x01d52f45e9c0831b
Faulting application path: C:\Program Files\PixInsight\bin\PixInsight.exe
Faulting module path: C:\WINDOWS\System32\ucrtbase.dll
Report Id: f47f3e35-d508-4181-a6cd-274cad658d63
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2019-06-30T13:18:34.884529700Z" />
    <EventRecordID>59105</EventRecordID>
    <Channel>Application</Channel>
    <Computer>SLE-5B4-422-DGT</Computer>
    <Security />
  </System>
  <EventData>
    <Data>PixInsight.exe</Data>
    <Data>1.8.6.1457</Data>
    <Data>5c472890</Data>
    <Data>ucrtbase.dll</Data>
    <Data>10.0.17134.677</Data>
    <Data>9f346d3f</Data>
    <Data>c0000409</Data>
    <Data>000000000006e14e</Data>
    <Data>68c8</Data>
    <Data>01d52f45e9c0831b</Data>
    <Data>C:\Program Files\PixInsight\bin\PixInsight.exe</Data>
    <Data>C:\WINDOWS\System32\ucrtbase.dll</Data>
    <Data>f47f3e35-d508-4181-a6cd-274cad658d63</Data>
    <Data>
    </Data>
    <Data>
    </Data>
  </EventData>
</Event>

[Juan Conejero]

Thank you for posting these error logs. They are signaling heap corruption and stack overrun, which are extremely bad problems and some of the worst bugs that a software application can have. However, I cannot reproduce these problems on any of our working and testing Windows 10 machines after hours of stress tests with big projects. They don't happen on macOS, Linux and FreeBSD, either.

If these problems were happening consistently as you describe them, this forum as well as our email support inbox would be stuffed with hundreds or thousands of similar error reports, and this does not happen. With the data I have at hand now, only three Windows users have reported similar logs to our support with version 1.8.6, and in one case at least the issue was fixed by a clean Windows reinstall.

I'll keep trying to reproduce these problems by running more and even harder stress tests on our machines. Can you please try on a different computer?