Share via

System crash while uploading Git

Reported
sicheng zhong 0 Reputation points
2026-04-03T19:16:06.1833333+00:00

My system crash when I use VScode to push code to github. The project (contains .git) is copyied from directory created in other system(fedora 43 workstation GNOME) via git init. However git push failed in fedora since authentication process. I wonder if the crash results to the authentication?

Windows for home | Windows 11 | Performance and system failures
0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Carl-L 12,330 Reputation points Microsoft External Staff Moderator
    2026-04-10T10:11:06.7466667+00:00

    Hello sicheng zhong,

    Welcome to Microsoft Q&A forum.

    May I know if you have already checked the AI assistant suggestion yet? If you did, may I know how it goes?

    Additionally, may I have the Event Logs requested by the AI assistant or the Minidump file at C:\Windows\Minidump to check for you?

    I'm waiting for your reply.

  2. Q&A Assist
    2026-04-03T19:16:21.27+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    The crash while pushing to GitHub is not caused by Git authentication or by the .git directory copied from Fedora. The Event Viewer entry shown is a TPM/Secure Boot maintenance warning, not a crash report, and it is unrelated to Git, VS Code, or GitHub.

    Event ID 1801 from Microsoft-Windows-TPM-WMI with the message:

    Updated Secure Boot certificates are available on this device but have not yet been applied to the firmware.

    means Windows has detected new Secure Boot certificate updates that should be applied in firmware/UEFI to maintain full protection. It is a security/firmware status notification and does not indicate a system crash or application fault.

    To troubleshoot the actual crash while using VS Code and Git:

    1. Look for Error or Critical events in Event Viewer under Windows Logs → Application and Windows Logs → System at the exact time of the crash, focusing on entries from Application Error, Kernel-Power, BugCheck, display driver, or storage drivers.
    2. Check Reliability Monitor (perfmon /rel) for a summary of application failures and Windows errors around the time of the crash.
    3. If the system is bluescreening, check for corresponding bugcheck events and minidumps in C:\Windows\Minidump.

    The TPM/Secure Boot event can be addressed separately by following the OEM/Windows guidance for applying Secure Boot certificate updates via firmware/BIOS updates, but it is not the root cause of the Git/VS Code crash.

    References:

    0 comments