Error 0xc0000001 BSOD

Some of the findings were:

a) New Windows installation
b) Multiple unexpected shutdowns and restarts without BSOD
c) Very old Legacy BIOS with a fewer older versions available
d) Insufficient free space data drive
e) Disabled recovery partition
f) Recurrent drive file system corruption


Please perform the following steps:


1) Run Sea Tools for Windows or Sea Tools bootable Long Generic test > post a share link

SeaTools | Support Seagate US

https://www.seagate.com/content/dam/...sInstaller.exe

https://www.seagate.com/content/dam/...lsBootable.zip




2) If the drive fails the Long Generic test then backup files and replace the drive




3) If the drive passes the Long Generic test then open administrative command prompt and copy and paste:

chkdsk /b /v

Run on all drives using the syntax chkdsk /b /v C: or chkdsk /b /v D: or chkdsk /b /v E: , etc.

Make sure that the chkdsk switches run on the Windows drive overnight while sleeping.


C:\WINDOWS\system32>chkdsk /b /v
The type of the file system is NTFS.
Cannot lock current drive.

Chkdsk cannot run because the volume is in use by another
process. Would you like to schedule this volume to be
checked the next time the system restarts? (Y/N)


Type: y

Reboot as needed.





4) On a working Windows computer create a bootable Windows 10 Media Creation Tool (MCT) (Windows 10 iso):

Download Windows 10 ISO File

https://www.microsoft.com/en-us/soft...load/windows10




BIOS Version/Date American Megatrends Inc. F4, 8/3/2013

Code:

------------------------
Disk & DVD/CD-ROM Drives
------------------------
      Drive: C:
 Free Space: 18.4 GB
Total Space: 121.6 GB
File System: NTFS
      Model: SAMSUNG SSD PM851 2.5 7mm 128GB

      Drive: D:
 Free Space: 257.0 GB
Total Space: 953.9 GB
File System: NTFS
      Model: ST1000DM003-1CH162

      Drive: E:
 Free Space: 74.4 GB
Total Space: 300.0 GB
File System: NTFS
      Model: ST1000DM010-2EP102

      Drive: F:
 Free Space: 90.5 GB
Total Space: 653.9 GB
File System: NTFS
      Model: ST1000DM010-2EP102

Code:

Event[9359]:
  Log Name: Application
  Source: Chkdsk
  Date: 2024-05-21T01:29:03.5800000Z
  Event ID: 26228
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-L31C3AP
  Description: 
Chkdsk was executed in verify mode on a volume snapshot.  

Checking file system on \Device\HarddiskVolume2
Volume label is WIN10.

Examining 20 corruption records ...

Record 1 of 20: Bad index "$I30" in directory "\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Bayonetta.exe_b25158a24d871a652f856f85e54fc2bc94b234d_555f263d_28be1bca-754a-4e0a-9ccd-78ffb5902165 <0xe,0xb4a94>" ... The multi-sector header signature for VCN 0x0 of index $I30
in file 0xb4a94 is incorrect.
4d 54 2b 30 35 30 30 20 ?? ?? ?? ?? ?? ?? ?? ??  MT+0500 ........
corruption found.

Record 2 of 20: Bad index "$I30" in directory "\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_DevilMayCry4Spec_4b345fde355832f1e55af147510a51d51864c5f_3d8920e5_7f017d5c-def9-4554-a35d-f02c040d2584 <0x6,0xb4c6b>" ... The multi-sector header signature for VCN 0x0 of index $I30
in file 0xb4c6b is incorrect.
ea 08 3e 4d 11 19 dd f6 ?? ?? ?? ?? ?? ?? ?? ??  Ω.>M..▌÷........
corruption found.

Record 3 of 20: Bad index "$I30" in directory "\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_GTAIV.exe_35ecdb41c35ea9e361ba5f622bed3e42d678cfde_a883fc16_88c8ad80-a9fa-4f38-bb24-5307eeda4b92 <0x10,0x52b77>" ... The multi-sector header signature for VCN 0x0 of index $I30
in file 0x52b77 is incorrect.
ff d8 ff e0 00 10 4a 46 ?? ?? ?? ?? ?? ?? ?? ??   ╪ α..JF........
corruption found.

Record 4 of 20: Bad index "$I30" in directory "\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_GTAIV.exe_35ecdb41c35ea9e361ba5f622bed3e42d678cfde_a883fc16_c74d1c58-37ba-4d2f-95e2-ea806589b846 <0xa,0xabdb6>" ... The multi-sector header signature for VCN 0x0 of index $I30
in file 0xabdb6 is incorrect.
3c 3f 78 6d 6c 20 76 65 ?? ?? ?? ?? ?? ?? ?? ??  <?xml ve........
corruption found.

Record 5 of 20: Bad index "$I30" in directory "\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_HMSC.exe_a48a978f439fce18f5cb7d6b5eee13b15c24e540_82f467f5_0ef6b526-4c23-4739-bcdc-d48f4f05aa26 <0x3f,0x14479>" ... The multi-sector header signature for VCN 0x0 of index $I30
in file 0x14479 is incorrect.
52 49 46 46 fa 02 00 00 ?? ?? ?? ?? ?? ?? ?? ??  RIFF·...........
corruption found.

Record 6 of 20: Bad index "$I30" in directory "\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_HMSC.exe_a48a978f439fce18f5cb7d6b5eee13b15c24e540_82f467f5_23d9e895-e3dd-4f8f-97e0-144b3db3adb0 <0x7,0x3ab8d>" ... The multi-sector header signature for VCN 0x0 of index $I30
in file 0x3ab8d is incorrect.
1f 8b 08 00 00 00 00 00 ?? ?? ?? ?? ?? ?? ?? ??  .?..............
corruption found.

Record 7 of 20: Bad index "$I30" in directory "\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_HMSC.exe_a48a978f439fce18f5cb7d6b5eee13b15c24e540_82f467f5_735eedae-cb9a-48c8-975f-189a05cbcc85 <0xa,0x74f03>" ... The multi-sector header signature for VCN 0x0 of index $I30
in file 0x74f03 is incorrect.
94 d1 83 d0 b6 d0 b5 20 ?? ?? ?? ?? ?? ?? ?? ??  ?╤?╨╢╨╡ ........
corruption found.

Record 8 of 20: Bad index "$I30" in directory "\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_HMSC.exe_a48a978f439fce18f5cb7d6b5eee13b15c24e540_82f467f5_95dcffd5-5d05-41fc-b939-af6149e6344f <0x5,0x81668>" ... The multi-sector header signature for VCN 0x0 of index $I30
in file 0x81668 is incorrect.
3c 76 61 6c 75 65 20 6e ?? ?? ?? ?? ?? ?? ?? ??  <value n........
corruption found.

Record 9 of 20: Bad index "$I30" in directory "\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_HMSC.exe_a48a978f439fce18f5cb7d6b5eee13b15c24e540_82f467f5_a9130cd3-5d2f-4897-9276-55b806f6f8b6 <0xc,0x7cc27>" ... The multi-sector header signature for VCN 0x0 of index $I30
in file 0x7cc27 is incorrect.
1f 8b 08 00 00 00 00 00 ?? ?? ?? ?? ?? ?? ?? ??  .?..............
corruption found.

Record 10 of 20: Bad index "$I30" in directory "\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_HMSC.exe_a48a978f439fce18f5cb7d6b5eee13b15c24e540_82f467f5_bf25c48e-ad06-416e-a7d0-d60121e1a73f <0x8,0x7cd00>" ... The USA check value, 0x6f, at block 0x1 is incorrect.
The expected value is 0x64.
The multi-sector header signature for VCN 0x0 of index $I30
in file 0x7cd00 is incorrect.
42 41 41 44 72 00 09 00 ?? ?? ?? ?? ?? ?? ?? ??  BAADr.	.........
corruption found.

Record 11 of 20: Bad index "$I30" in directory "\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_HMSC.exe_a48a978f439fce18f5cb7d6b5eee13b15c24e540_82f467f5_ef258f9c-71d2-4c39-8dd8-390169eb06c5 <0xe,0x45069>" ... The multi-sector header signature for VCN 0x0 of index $I30
in file 0x45069 is incorrect.
45 42 2f 77 51 45 41 77 ?? ?? ?? ?? ?? ?? ?? ??  EB/wQEAw........
corruption found.

Record 12 of 20: Bad index "$I30" in directory "\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_LaunchGTAIV.exe_3786fecb81ef0a78ca4bc5a324d233dda653a8_d8c86f6d_2a6ec83b-af5d-4731-92cf-9964f76abbd4 <0xb,0x4cf1c>" ... The multi-sector header signature for VCN 0x0 of index $I30
in file 0x4cf1c is incorrect.
00 00 00 00 00 00 00 00 ?? ?? ?? ?? ?? ?? ?? ??  ................
corruption found.

Record 13 of 20: Bad index "$I30" in directory "\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_LaunchGTAIV.exe_3786fecb81ef0a78ca4bc5a324d233dda653a8_d8c86f6d_41695d1f-f6a2-4e8a-aa49-5b0d37fd113e <0x10,0x4cc4a>" ... The multi-sector header signature for VCN 0x0 of index $I30
in file 0x4cc4a is incorrect.
13 53 14 00 e4 f4 57 f6 ?? ?? ?? ?? ?? ?? ?? ??  .S..Σ⌠W÷........
corruption found.

Record 14 of 20: Bad index "$I30" in directory "\ProgramData\Microsoft\Windows\WER\ReportArchive\Critical_10.0.19041.1940__4ad7265fc2878c3f5aa33335e5363f162973124d_00000000_9a54102c-f017-4bcc-9d34-5ec71f01c44a <0x1f,0x8e0>" ... The multi-sector header signature for VCN 0x0 of index $I30
in file 0x8e0 is incorrect.
1f 8b 08 00 00 00 00 00 ?? ?? ?? ?? ?? ?? ?? ??  .?..............
corruption found.

Record 15 of 20: Bad index "$I30" in directory "\ProgramData\Microsoft\Windows\WER\ReportArchive\Critical_10.0.19041.4289__a3e39dd0c8bdd0ff24d54f1c65037bde44c755_00000000_13d82d2b-6e1c-4452-986d-a26c4cf792f0 <0x3,0x52829>" ... The multi-sector header signature for VCN 0x0 of index $I30
in file 0x52829 is incorrect.
ff d8 ff e0 00 10 4a 46 ?? ?? ?? ?? ?? ?? ?? ??   ╪ α..JF........
corruption found.

Record 16 of 20: Bad index "$I30" in directory "\ProgramData\Microsoft\Windows\WER\ReportArchive\Critical_10.0.19041.4351__9c579aacff4e4b22f5ce5d2cbd9eefd2658962f_00000000_29319a0b-5462-4bf8-9dd8-9678e2508e5d <0x1,0xa6c99>" ... The multi-sector header signature for VCN 0x0 of index $I30
in file 0xa6c99 is incorrect.
53 65 73 73 69 6f 6e 49 ?? ?? ?? ?? ?? ?? ?? ??  SessionI........
corruption found.

Record 17 of 20: Bad index "$I30" in directory "\ProgramData\Microsoft\Windows\WER\ReportArchive\NonCritical_0x800705b4_f6af8dae9a82e3dbd1cf7871cc546685b47fd939_00000000_772bdcac-5f71-48df-a167-a404ae2ce2a4 <0x3,0x8a69c>" ... The multi-sector header signature for VCN 0x0 of index $I30
in file 0x8a69c is incorrect.
7b 46 49 4c 45 5f 51 55 ?? ?? ?? ?? ?? ?? ?? ??  {FILE_QU........
corruption found.

Record 18 of 20: Bad index "$I30" in directory "\ProgramData\Microsoft\Windows\WER\ReportArchive\NonCritical_0x80070666_e752fd7f4a4b18e6c82988f17c3670e64aa0e92f_00000000_55e8684e-9b6f-4b2d-87c6-e6a2e04e4333 <0x4,0x8a978>" ... The multi-sector header signature for VCN 0x0 of index $I30
in file 0x8a978 is incorrect.
ff ff ff ff 76 00 6d 00 ?? ?? ?? ?? ?? ?? ?? ??      v.m.........
corruption found.

Record 19 of 20: Bad index "$I30" in directory "\ProgramData\Microsoft\Windows\WER\ReportArchive\NonCritical_MicrosoftEdgeUpd_52ab18abb961c7c7dcf243d9c186eb55ddfa3dd_00000000_3cdc9b08-5fad-495a-b43f-c2afc2a0d57b <0x3,0x15e44>" ... The multi-sector header signature for VCN 0x0 of index $I30
in file 0x15e44 is incorrect.
6c 2d 52 65 71 75 65 73 ?? ?? ?? ?? ?? ?? ?? ??  l-Reques........
corruption found.

Record 20 of 20: Bad index "$I30" in directory "\ProgramData\Microsoft\Windows\WER\ReportArchive\NonCritical_MicrosoftEdgeUpd_caf6d89f11d994fb3aa6d5c217198efa4e51a_00000000_f5eb9205-da34-41ca-9736-e12c9c4ad28a <0x7,0x4241e>" ... The multi-sector header signature for VCN 0x0 of index $I30
in file 0x4241e is incorrect.
7b 20 22 72 74 64 22 3a ?? ?? ?? ?? ?? ?? ?? ??  { "rtd":........
corruption found.

20 corruption records processed in 0.1 seconds.

Windows has examined the list of previously identified potential issues and found problems.
Please run chkdsk /scan to fully analyze the problems and queue them for repair.

Are you able to use an Uninterruptable Power Supply [UPS ]given the state of your current supply ?

Yes I can use that but I can't yet afford it, gotta make some money from my 2 youtube channels first then maybe I'll be able to invest some into my pc, I'm gonna thoroughly check the ssd drive though. Thanks alot all of you.

Yup it has passed the long generic test via seatools.

In Powershell [admin ] type in ---dism /online /cleanup-image /restorehealth ---then run it and when completed type in ---sfc /scannow ---and run it until a clean report is given.

Done, Thanks alot.

Edit: Also updated the bios to the latest version.

I've also switched back to GPT / UEFI using AOEMI Partition Assistant, why it says recoveryenabled no in bcdedit?

Also what are the benefits of the recovery partition? Why system restore becomes disabled automatically?

Well, Mr. Pentagon, you talk in too much tech language, even though I'm in the field of I.T. since very long but I don't understand much of the hardware, windows language,

winre.wim.

maybe I'm more of a software person, anyway Hibernation is already disabled, I don't know what you meant in your first paragraph really but here goes the screenshot of my usage of C: Drive:

Even One drive documents / desktop folders are in Drive D, why C is taking up too much space? I need to have a closer look.


BTW, I couldn't do anything else but to take the risk of updating the BIOS from within windows praying with my eyes closed for not running into a power cut then I even went so far and changed the boot logo as well... It worked.
Why you don't recommend moving the Appdata folder to D: ? When AOEMI parition assistant can do that safely it can even move apps and link them to another drive, I've tested moving apps to Drive D.

Alright mate, got that, Thanks alot for all of your help, and all other people who helped me, as I stated earlier not many people here can afford many things like a UPS / Backup drives etc. Hell I'm trying to buy a new GPU for my gaming channel.

1.txt - Google Drive
2.txt - Google Drive

Btw, I had another improper shutdown and the error is still there.