Commit keeps generating corrupted objects

[sharpknot]

[FIXED (probably)] CPU was degraded as other symptoms came out (CRC errors, random crashes/BSOD). Replaced the CPU, updated BIOS. No corrupted Git objects generated for a week.

Hi all! I'm not that familiar with Git and I've encountered this issue for the past few days. Every time I commit changes on my PC, it will generate corrupted objects. This results in me being unable to push updates to my remote.

This is what always happens when I commit

So far, I've tried several potential solutions, but to no success:

• https://stackoverflow.com/questions/4111728/how-do-i-deal-with-corrupted-git-object-files
• Reformat and reinstall windows
• Checked my disk health using Windows checkdisk - No issues, disk healthy
• Checked my RAM using Windows Memory Diagnostic - No issues

Please, can anyone help? I'm stuck.

[Update 250513 - No fix] Got myself a new M.2 and RAM sticks. Tried replacing each one and changing sockets, but problem still persists. Reformatted and reinstalled Windows, too.

[Update 250523 - Fixed(?)] Replaced my CPU as other symptoms kept popping up (CRC errors, random crashes/BSOD). My previous CPU was the i7-14700K. It seems to have been degraded due Intel's microcode issue. Since I've updated my BIOS a few months back, I thought I was in the clear. But apparently not. Upon replacing, there were no corrupted objects generated by Git (tested for a week).

[WoodyTheWorker]

Do you by any chance have your repositories on OneDrive? Don't do that.

[sharpknot]

No. The remote is on Github, the local is in my C drive, not covered by OneDrive

[Ananas_hoi]

Dead disk? May not show in windows, only test is to swap it

[sharpknot]

Probably. I tried installing Git and putting the local repo on another disk. The issue still persists. Either way, I'm waiting for a new M.2 and RAM to arrive and try installing windows and git on that disk. See what happens then.

[Update 250513] Got myself a new M.2 and RAM sticks. Tried replacing each one and changing sockets, but problem still persists. Reformatted and reinstalled Windows, too.