public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Rupin Dhanoa <hellyeah94545@yahoo.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: installer crashed on Windows 11; ERROR_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION}
Date: Fri, 23 Jun 2023 19:18:19 +0000 (UTC)	[thread overview]
Message-ID: <693296707.4317444.1687547899502@mail.yahoo.com> (raw)
In-Reply-To: <693296707.4317444.1687547899502.ref@mail.yahoo.com>

[-- Attachment #1: Type: text/plain, Size: 5918 bytes --]

Hi Guys,setup-x86_64.exe crashing from me on Windows 11 (Version 10.0.22621 Build 22621) on dell laptop (12th Gen  Intel i7-12800H, 2400 Mhz).Memory dump analysis in Windows debugger shows:----------------------------ERROR_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION}  Illegal Instruction  An attempt was made to execute an illegal instruction.

EXCEPTION_CODE_STR:  c000001d----------------------------
Below is Windows debugger memory dump analysis full output:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Windows Debugger full output:~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~Microsoft (R) Windows Debugger Version 10.0.25877.1004 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\3423599\AppData\Local\CrashDumps\setup-x86_64 (4).exe.18808.dmp]
User Mini Dump File with Full Memory: Only application data is available


************* Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       srv*
Symbol search path is: srv*
Executable search path is: 
Windows 10 Version 22621 MP (20 procs) Free x64
Product: WinNt, suite: SingleUserTS
Edition build lab: 22621.1.amd64fre.ni_release.220506-1250
Debug session time: Fri Jun 23 14:57:47.000 2023 (UTC - 4:00)
System Uptime: 4 days 6:22:50.601
Process Uptime: 0 days 0:00:02.000
............................
This dump file has an exception of interest stored in it.
The stored exception information can be accessed via .ecxr.
(4978.db10): Illegal instruction - code c000001d (first/second chance not available)

+------------------------------------------------------------------------+
| This target supports Hardware-enforced Stack Protection. A HW based    |
| "Shadow Stack" may be available to assist in debugging and analysis.   |
| See aka.ms/userhsp for more info.                                      |
|                                                                        |
| dps @ssp                                                               |
|                                                                        |
+------------------------------------------------------------------------+

For analysis of this file, run !analyze -v
*** WARNING: Unable to verify timestamp for setup-x86_64 (4).exe
setup_x86_64__4_+0x105c27:
00000000`00505c27 d6              ???
0:000> !analyze -v
*******************************************************************************
*                                                                             *
*                        Exception Analysis                                   *
*                                                                             *
*******************************************************************************


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1202

    Key  : Analysis.Elapsed.mSec
    Value: 6707

    Key  : Analysis.IO.Other.Mb
    Value: 6

    Key  : Analysis.IO.Read.Mb
    Value: 0

    Key  : Analysis.IO.Write.Mb
    Value: 17

    Key  : Analysis.Init.CPU.mSec
    Value: 77

    Key  : Analysis.Init.Elapsed.mSec
    Value: 8442

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 103

    Key  : Failure.Bucket
    Value: ILLEGAL_INSTRUCTION_c000001d_setup-x86_64_(4).exe!Unknown

    Key  : Failure.Hash
    Value: {907c0b84-d3f6-bacc-6ae8-dce0ed8b49d4}

    Key  : Timeline.OS.Boot.DeltaSec
    Value: 368570

    Key  : Timeline.Process.Start.DeltaSec
    Value: 2

    Key  : WER.OS.Branch
    Value: ni_release

    Key  : WER.OS.Version
    Value: 10.0.22621.1


FILE_IN_CAB:  setup-x86_64 (4).exe.18808.dmp

NTGLOBALFLAG:  0

PROCESS_BAM_CURRENT_THROTTLED: 0

PROCESS_BAM_PREVIOUS_THROTTLED: 0

APPLICATION_VERIFIER_FLAGS:  0

CONTEXT:  (.ecxr)
rax=0000000000000224 rbx=00000000007b80d0 rcx=0000000000905b48
rdx=0000000000000352 rsi=0000000000401000 rdi=00000000008f0008
rip=0000000000505c27 rsp=0000000000b0fed8 rbp=0000000000000000
 r8=0000000000b0d4e0  r9=0000000000b0d4b8 r10=00000000007f38c0
r11=00000000008a0712 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
cs=0033  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00010200
setup_x86_64__4_+0x105c27:
00000000`00505c27 d6              ???
Resetting default scope

EXCEPTION_RECORD:  (.exr -1)
ExceptionAddress: 0000000000505c27 (setup_x86_64__4_+0x0000000000105c27)
   ExceptionCode: c000001d (Illegal instruction)
  ExceptionFlags: 00000000
NumberParameters: 0

PROCESS_NAME:  setup-x86_64 (4).exe

ERROR_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION}  Illegal Instruction  An attempt was made to execute an illegal instruction.

EXCEPTION_CODE_STR:  c000001d

STACK_TEXT:  
00000000`00b0fed8 00000000`008f4c4d     : 00000000`00000000 00000000`004f24da 00000000`006e13fc 00000000`00b0c040 : setup_x86_64__4_+0x105c27
00000000`00b0fee0 00000000`00000000     : 00000000`004f24da 00000000`006e13fc 00000000`00b0c040 00000000`00401000 : setup_x86_64__4_!BZ2_bzerror+0x365f8d


FAILED_INSTRUCTION_ADDRESS: 
setup_x86_64__4_+105c27
00000000`00505c27 d6              ???

SYMBOL_NAME:  setup_x86_64__4_+105c27

MODULE_NAME: setup_x86_64__4_

IMAGE_NAME:  setup-x86_64 (4).exe

STACK_COMMAND:  dt ntdll!LdrpLastDllInitializer BaseDllName ; dt ntdll!LdrpFailureData ; ~0s; .ecxr ; kb

FAILURE_BUCKET_ID:  ILLEGAL_INSTRUCTION_c000001d_setup-x86_64_(4).exe!Unknown

OS_VERSION:  10.0.22621.1

BUILDLAB_STR:  ni_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {907c0b84-d3f6-bacc-6ae8-dce0ed8b49d4}

Followup:     MachineOwner
---------
Thank you,Rupin



       reply	other threads:[~2023-06-23 19:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <693296707.4317444.1687547899502.ref@mail.yahoo.com>
2023-06-23 19:18 ` Rupin Dhanoa [this message]
     [not found] <1733727758.3053362.1687548411342.ref@mail.yahoo.com>
2023-06-23 19:26 ` Rupin Dhanoa
2023-06-27 19:43   ` Jon Turney
2023-07-02 15:14     ` Rupin Dhanoa
2023-07-16 12:20       ` Jon Turney

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=693296707.4317444.1687547899502@mail.yahoo.com \
    --to=hellyeah94545@yahoo.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).