1. Stefan B Avatar Stefan B
  2. nina
  3. NINA
  4. Issues

NINA not starting up!

Issue #1294 resolved
Peter De Groot created an issue

Hi,

On one PC following happens.

Event log:

Faulting application name: NINA.exe, version: 3.0.0.9001, time stamp: 0x65cd0000
Faulting module name: coreclr.dll, version: 8.0.324.11423, time stamp: 0x65cd500d
Exception code: 0xc0000005
Fault offset: 0x000000000018c5e4
Faulting process id: 0x12dc
Faulting application start time: 0x01da7f78bbf5fb2e
Faulting application path: C:\Program Files\N.I.N.A. - Nighttime Imaging 'N' Astronomy\NINA.exe
Faulting module path: C:\Program Files\N.I.N.A. - Nighttime Imaging 'N' Astronomy\coreclr.dll
Report Id: cb39c83f-b6a6-446d-95f5-1afd56594ff0
Faulting package full name:
Faulting package-relative application ID:

‌

AND another event:Log Name:

Application: NINA.exe
CoreCLR Version: 8.0.324.11423
.NET Version: 8.0.3
Description: The process was terminated due to an internal error in the .NET Runtime at IP 0x00007FFC9E01C5E4 (0x00007FFC9DE90000) with exit code 0x80131506.

‌

‌

Comments (16)

  2. Stefan B repo owner

    You can simply uninstall your currently not working application and use the linked installer.
    It would also be great if you could run the winver command and show the exact windows version including the build number that you are using. Maybe we can isolate the root cause of the issue more with that info.

  3. Peter De Groot reporter

    Yes that one works!

    I have 2 PC’s both with “WIN10 Version 22H22 (OS Build 19045.4170).

    On one it works on the other I had this problem.
    The only diff is the CPU type: “Intel i7-6700K” it works on the “Core(TM)2 Quad CPUQ9300” it does not! Some instructions not supported on the CPUQ9300 that de .net 8.xxx uses?

    Thanks anyway,

    Cheers Peter.

  4. Stefan B repo owner

    Interesting that the same windows build fails on the other PC. Maybe Microsoft did indeed put something in their patch that is not supported by that CPU, but we can only guess. I also need to put down the info and try to open an issue report to Microsoft about it. I’ve seen this issue mentioned in other applications too.

  6. Dale Ghent

    Oh my. The Core2 Q9300 is a very old processor, launched in 2008, and it is several major architectures behind the present. It is very likely that the .NET 8 runtime requires CPU features that aren’t found on this old microarchitecture. I can’t seem to find any list of CPUs that .NET 8 supports, but a 16 year old CPU architecture is very plausibly unable to run .NET 8. It may be that your system with the Q9300 CPU is now just too old.

  7. Peter De Groot reporter

    Indeed, an old processor, with runs WIN10 without a problem! So, it should run .net 8.
    And also .NET8-802 build from Stefan runs fine!
    Just the latest patch does not.
    If this is the case that this processor is not supported, then the .NET install at least should say that!
    .NET should accommodate itself to the processor it runs on, not the other way around.
    Just my thoughts.

  8. Dale Ghent

    Microsoft’s Windows 10 21H1 Supported Intel Processors list, which can be considered an official document on the topic, does not mention any of the Core2, pre-Nehalem generation CPU family that your Q9300 is a member of. In fact, it also doesn’t list CPU models that came immediately after yours. It would be safe to say that your continued operation of Windows 10 on that CPU is continuing more by luck than by design on Microsoft’s part. This would also apply to .NET 8.

    The idea that the software should accommodate itself to the processor’s capabilities (or lack of them) sounds convenient, but that really is not possible with the tasks that processors of the modern era are being asked to perform. Modern needs require a minimum level of support from the hardware and in some cases are not possible without newer CPU features.

  9. Dale Ghent

    I just found this document from Intel, which explains which CPU generations are supported by Windows 10. Your CPU is of the “Yorkfield” variant, based on the Penryn microarchitecture. Intel’s chart says that Penryn is not supported by Windows 10. I guess it really is just luck that you have been able to run it so far, but .NET 8 now requires something newer.

    Speaking from a systems perspective, modern low-power mini PCs will likely not only be a substantial upgrade from this older Core 2 processor in terms of performance, but also rather cheap. The PassMark scores are interesting:

    Your current Core 2 Q9300

    Versus a low-power, low-cost CPU that is commonly used in astro PC systems today:
    Intel Celeron N5105

    Nearly twice the compute power at 10% of the power consumption. Factor in faster memory and storage, and one would notice quite a difference.

  10. Stefan B repo owner

    It’s still an open question if the CPU model is really the root cause, especially since the problem arose just between a security patch release for two .NET 8 versions.

  11. Dale Ghent

    I’m not sure how we can prove that within reasonable means, but the evidence strongly suggests it.

  12. Stefan B repo owner

    Ok after digging into the .net issue tracker it seems to be indeed related to older CPU generations. Apparently the problem is arising for CPUs that don’t support SSE4. The other user we know that encounters that issue is using a Celeron T3500.
    Some more info is available here https://github.com/dotnet/runtime/issues/100264 and the links inside there.

    Looks like it will take until 8.0.5 for this problem to be fixed.

  17. Log in to comment
Assignee
–
Type
bug
Priority
blocker
Status
resolved
Component
General
Version
3.0
Votes
0
Watchers
3
Jira: the preferred issue tracker for Bitbucket. Join the team!