Windows Registry Hive Rusak (BAD_SYSTEM_CONFIG_INFO BSOD): Kenapa RegBack Kosong ing Windows 10/11 lan Cara Mulihake Hives saka VSS Shadow Copies¶

Deleng Windows 10, Windows 11, utawa mesin Windows Server kacilakan nalika wiwitan menyang Layar Biru Pati sing ora ana telas (BSOD) tampilan loop Stop code: BAD_SYSTEM_CONFIG_INFO (0x00000074),CRITICAL_PROCESS_DIED, utawa layar Windows Boot Manager ireng sing nyatakake \Windows\System32\config\SYSTEM is missing or contains errors (Status: 0xc000014c / 0xc0000225) tegese siji utawa luwih saka sarang registri biner inti Windows (SYSTEM, SOFTWARE, SAM, SECURITY, DEFAULT) utawa Data Konfigurasi Boot (BCD) toko ambruk nalika listrik mati, mateni paksa, utawa nganyari kumulatif gagal. Luwih elek, nalika pangurus ngetutake tutorial online lawas sing ngandhani supaya mbukak Lingkungan Pemulihan Windows (WinRE) Command Prompt lan nyalin file registri serep saka C:\Windows\System32\config\RegBack\, padha nemokake sing ** ing RegBack folder kosong (utawa ngemot 0-byte berkas)**. Miwiti ing Windows 10 versi 1803 lan ing kabeh mbangun Windows 11, Microsoft mateni permanen RegIdleBackup tugas kanggo ngirit ruang disk. Aja ngilangke lan instal maneh Windows: PC sampeyan meh mesthi nyimpen salinan kabeh sarang pendaptaran sing didhelikake Volume Shadow Copy Service (VSS) snapshot (HarddiskVolumeShadowCopyN) lan transaksi .LOG1 / .LOG2 jurnal sing bisa extract ing 3 menit saka WinRE. Kanggo ngatasi masalah driver utawa hardware BSOD umum, waca Layar biru Windows (BSOD) lan ndandani boot; yen BitLocker njaluk kunci pemulihan 48 digit sadurunge mbukak Command Prompt, takon Kunci kunci pemulihan enkripsi BitLocker, FileVault, lan LUKS lan reset TPM lan SSD lan NVMe modus mung maca dadakan lan TRIM mateni nylametake. Yen kegagalan sistem iki mateni stasiun kerja klinis rumah sakit, kiriman darurat (CAD), utawa kontrol kaslametan urip, nelpon nomer darurat lokal (911 ing Amerika Serikat lan Kanada, 112 liwat Uni Eropa, 999 ing Inggris) utawa priksa direktori kita nomer darurat.

Apa iki saiki¶

1. ** AJA klik "Reset PC iki -> Copot kabeh" utawa nyalin wuta 0-byte file metu saka C:\Windows\System32\config\RegBack\**: Yen mlayu copy C:\Windows\System32\config\RegBack\* C:\Windows\System32\config\ ing Windows 10 (1803+) utawa Windows 11 tanpa mriksa dir RegBack pisanan, sampeyan bakal nimpa hives pendaptaran sebagian rusak karo 0-byte file kosong, numpes hives isih lan nggawe Recovery akeh harder.
2. ** Boot menyang Windows Recovery Environment (WinRE) lan mbukak Troubleshoot -> Advanced options -> Command Prompt**:
3. Yen Windows gagal boot kaping telu saurutan, kanthi otomatis mbukak ** Repair Otomatis -> Pilihan Lanjut **.
4. Utawa, boot saka sembarang Windows 10 / 11 USB Instalasi Media, penet Shift + F10 (utawa Shift + Fn + F10 ing laptop) langsung ing layar pilihan basa wiwitan, lan munggah X:\Sources> Command Prompt langsung mbukak tanpa ngeklik menu.
5. ** Temokake huruf drive sing bener saka partisi Windows sampeyan (diskpart -> list vol), kaya sing asring D: utawa E: nang WinRE, NOT C:**: Ing lingkungan pemulihan, C: asring diutus kanggo 100 megabyte System Reserved utawa Recovery partisi nalika instalasi Windows sampeyan lagi aktif D: utawa E:. Mlayu dir C:\Windows, dir D:\Windows, dir E:\Windows kanggo konfirmasi huruf drive sing ngemot \Windows\System32\config\.
6. ** Tansah gawe serep sing ana (malah rusak) config\ folder menyang C:\Config_Backup\ Sadurunge ndemek file siji**: Run mkdir D:\Config_Backup lan xcopy /h /i /c /k /e /r /y D:\Windows\System32\config D:\Config_Backup. Sampeyan kudu ngreksa loro lima file hive utama (SYSTEM, SOFTWARE, SAM, SECURITY, DEFAULT) lan file log transaksi sing didhelikake (SYSTEM.LOG1, SYSTEM.LOG2, SOFTWARE.LOG1, SOFTWARE.LOG2).
7. ** Sadurunge ngganti hive, priksa manawa BCD (Boot Configuration Data) truncation utawa log transaksi sarang kotor (.LOG1 / .LOG2) iku sabab nyata saka BAD_SYSTEM_CONFIG_INFO**:
8. Ing 30% saka BAD_SYSTEM_CONFIG_INFO BSODs, hives pendaptaran 100 persen nggoleki lan BCD toko mung wis rusak truncatememory / numproc bendera (msconfig trap) utawa kabutuhan reg load kanggo muter maneh .LOG1/.LOG2 log transaksi kanthi otomatis.
9. Yen SYSTEM utawa SOFTWARE bener rusak, extract salinan sehat langsung saka VSS Shadow Copy (\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy1\Windows\System32\config\) nggunakake vssadmin list shadows: Malah nalika System Restore (rstrui.exe) gagal karo kesalahan ing GUI, volume VSS Shadow Copy ndasari ana ing disk lan ngijini sampeyan nyalin resik SYSTEM lan SOFTWARE hives langsung menyang \Windows\System32\config\ nggunakake copy utawa robocopy.

Pohon keputusan: BAD_SYSTEM_CONFIG_INFO (0x00000074) lan 0xc000014c triase pendaptaran¶

Gunakake flowchart iki saka WinRE Command Prompt (Shift + F10) kanggo nemtokake file sing rusak lan mulihake tanpa kelangan program utawa akun pangguna sing diinstal:

flowchart TD
    Start["Windows Kacilakan nalika Boot: BAD_SYSTEM_CONFIG_INFO (0x74) utawa 0xc000014c"] --> OpenCmd["Boot menyang WinRE utawa Windows USB -> Bukak Command Prompt (Shift + F10)"]

    OpenCmd --> FindDrive["Temokake True Windows Drive Letter (contone D :) liwat: diskpart -> list vol -> metu"]
    FindDrive --> BackupFirst["Gawe serep Folder Konfigurasi Saiki (Kalebu Didhelikake .LOG1/.LOG2): xcopy /h D:\\Windows\\System32\\config D:\\Config_Orig\\"]

    BackupFirst --> CheckBcd["Priksa 1: Mbukak bcdedit -> Apa Wong Nyetel truncatememory utawa numproc ing msconfig?"]
    CheckBcd -->|"Ya: truncatememory utawa badvalue Saiki"| FixBcd["Run: bcdedit /deletevalue {default} truncatememory AND bcdedit /deletevalue {default} numproc -> Reboot"]

    CheckBcd -->|"No: BCD Clean"| TestReplay["Priksa 2: Test & Replay Transaksi Log (.LOG1/.LOG2) kanggo Saben Hive liwat reg mbukak HKLM\\TempHive"]

    TestReplay --> WhichBroken{"Apa reg mbukak Sukses lan Muter maneh .LOG1/.LOG2 Cleanly?"}
    WhichBroken -->|"Ya: reg mbukak Log Transaksi Reged Diputer maneh -> Mbongkar liwat reg unload"| BootFixed["Urip maneh PC: Header Hive Dirty Didandani ing Panggonan kanthi Zero Rollback"]

    WhichBroken -->|"Ora: SISTEM utawa SOFTWARE Ngasilake 'Database pendaptaran konfigurasi rusak' utawa 0 Byte"| CheckVss["Run: vssadmin dhaptar bayangan"]

    CheckVss --> HasVss{"Apa Salinan Shadow Volume Didhaptar (HarddiskVolumeShadowCopy1..N)?"}

    HasVss -->|"Ya: Shadow Copies Ana"| CopyVss["Nyalin ONLY Hive Rusak (eg SYSTEM / SOFTWARE) saka Newest HarddiskVolumeShadowCopyN menyang D:\\Windows\\System32\\config\\"]

    HasVss -->|"No: 0 Shadow Copies Listed"| CheckAlt["Priksa Sumber Hive Alternatif: D:\\Windows\\System32\\config\\TxR\\ UTAWA Windows.old UTAWA WinSxS Component Hive Repair"]

Fase 1: Kenapa BAD_SYSTEM_CONFIG_INFO mengkono lan apa RegBack kosong ing Windows 10/11¶

Sadurunge ngowahi file ing njero \Windows\System32\config\, mangertos apa limang file hive pendaptaran bener apa lan ngapa tradisional RegBack metode ora bisa digunakake maneh.

1. Anatomi saka \Windows\System32\config\¶

Nalika kernel Windows (ntoskrnl.exe) lan Boot Loader (winload.efi) diwiwiti nalika wiwitan, mbukak limang file database binar (disebut Hives, diwiwiti kanthi tandha ASCII 4-byte regf ing byte 0) saka \Windows\System32\config\:

2. Kenapa C:\Windows\System32\config\RegBack kosong ing Windows 10 (1803+) lan Windows 11¶

Saka Windows XP liwat Windows 10 versi 1709, tugas dijadwal jenenge \Microsoft\Windows\Registry\RegIdleBackup otomatis disalin SYSTEM, SOFTWARE, SAM, SECURITY, lan DEFAULT menyang \Windows\System32\config\RegBack\ kapan sistem iki nganggur. - Apa sing diganti Microsoft: Wiwit ing Windows 10 versi 1803 (Mei 2018) lan terus saben rilis Windows 11, Microsoft resmi mateni otomatis RegBack populasi kanthi standar kanggo nyuda jejak disk (didokumentasikan ing Dhukungan Microsoft KB4509719). - Asil: Kajaba sampeyan nambahake kanthi manual EnablePeriodicBackup = 1 DWORD kanggo HKLM\System\CurrentControlSet\Control\Session Manager\Configuration Manager sadurunge PC sampeyan crash, mlaku dir D:\Windows\System32\config\RegBack bakal nuduhake 0 File(s) (utawa limang file ukuran 0 bita). - **Kenapa sampeyan isih duwe serep **: Sanajan RegBack kosong, Windows 10 lan Windows 11 kanthi otomatis nggawe Volume Shadow Copy (VSS) jepretan sadurunge Nganyari Windows, instal aplikasi MSI, instalasi driver, lan checkpoint pamulihan mingguan. Saben gambar asli VSS ngemot salinan beku titik-in-wektu lengkap \Windows\System32\config\.

Fase 2: Ndandani Cepet Non-Rollback (msconfig BCD Trap & .LOG1/.LOG2 Transaksi Replay)¶

Sadurunge ngganti SYSTEM utawa SOFTWARE saka salinan bayangan, nyoba iki loro nul-rollback mbenakake ing WinRE Command Prompt (Shift + F10). Luwih saka setengah kabeh BAD_SYSTEM_CONFIG_INFO (0x00000074) kacilakan dirampungake ing kene ing sangisore 60 detik tanpa mbalekake setelan siji.

Langkah 1: Ngenali huruf drive Windows sing bener (D: vs C:) lan gawe serep config\¶

Ing X:\Sources> Jendhela Command Prompt, golek huruf drive sing ngemot instalasi Windows sampeyan:

diskpart
list volume
exit

Langsung gawe serep lengkap saka D:\Windows\System32\config (nganggo /h dadi didhelikake .LOG1 lan .LOG2 file transaksi kalebu):

mkdir D:\Config_Emergency_Backup
xcopy /h /i /c /k /e /r /y D:\Windows\System32\config D:\Config_Emergency_Backup

Langkah 2: Priksa Ndandani A: Apa ana wong sing ngganti Number of processors utawa Maximum memory ing msconfig?¶

Dokumentasi resmi Microsoft kanggo Bug Check 0x74 (BAD_SYSTEM_CONFIG_INFO) nyorot jebakan sing kondhang: pangguna mbukak **msconfig -> Boot -> Opsi lanjut ** sawise video "optimasi game" sing ala, priksa Number of processorsutawa Maximum memory (nyetel menyang 0 utawa nilai ala), lan urip maneh. Sanalika sawise urip maneh, Windows tekan permanen BAD_SYSTEM_CONFIG_INFO BSOD malah sadurunge ndemek hives pendaptaran.

Priksa Data Konfigurasi Boot (BCD) nyimpen saiki:

bcdedit /enum {default}

bcdedit /deletevalue {default} truncatememory
bcdedit /deletevalue {default} numproc
bcdedit /deletevalue {default} removememory

Langkah 3: Priksa Ndandani B: Muter maneh reged .LOG1 / .LOG2 log transaksi hive ing panggonan nggunakake reg load¶

Apa yen daya dipateni nalika Windows nulis SYSTEM utawa SOFTWARE?

+-------------------------------------------------------------------------+
| HOW WINDOWS REGISTRY HIVE HEADER SEQUENCE NUMBERS WORK                  |
|                                                                         |
| Base Block Header of SYSTEM Hive (First 4,096 bytes: "regf"):           |
|   Offset 0x04: Primary Sequence Number   = 0x0004810A                   |
|   Offset 0x08: Secondary Sequence Number = 0x00048109 (MISMATCH)        |
|                                                                         |
| Why it fails at boot:                                                   |
|   Power died mid-write before Primary == Secondary. The missing         |
|   dirty pages are sitting safely inside SYSTEM.LOG1 / SYSTEM.LOG2.      |
|   If winload.efi cannot reconcile the log at early boot, it throws      |
|   0xc000014c or BAD_SYSTEM_CONFIG_INFO (0x74).                          |
|                                                                         |
| How to force-replay the .LOG1/.LOG2 file in WinRE:                      |
|   Running `reg load HKLM\Temp D:\Windows\System32\config\SYSTEM`        |
|   invokes the full WinRE Configuration Manager, which reads             |
|   SYSTEM.LOG1 + SYSTEM.LOG2, replays the dirty vector pages into        |
|   SYSTEM, sets Primary == Secondary, and flushes a clean hive on unload |
+-------------------------------------------------------------------------+

Tes saben limang hives (SYSTEM, SOFTWARE, SAM, SECURITY, DEFAULT) siji-siji ing WinRE Command Prompt nggunakake reg load:

reg load HKLM\TestSys D:\Windows\System32\config\SYSTEM

reg unload HKLM\TestSys

reg load HKLM\TestSoft D:\Windows\System32\config\SOFTWARE
reg unload HKLM\TestSoft

reg load HKLM\TestSam D:\Windows\System32\config\SAM
reg unload HKLM\TestSam

reg load HKLM\TestSec D:\Windows\System32\config\SECURITY
reg unload HKLM\TestSec

reg load HKLM\TestDef D:\Windows\System32\config\DEFAULT
reg unload HKLM\TestDef

Phase 3: Extracting Healthy Registry Hives saka VSS Salinan bayangan (HarddiskVolumeShadowCopyN)¶

Napa kita ngekstrak hive sing rusak kanthi manual saka Volume Shadow Copy tinimbang ngeklik ** Troubleshoot -> Advanced options -> System Restore ** ing GUI? 1. Pisanan, yen SYSTEM utawa SOFTWARE ora bisa diwaca, grafis System Restore (rstrui.exe) tuntunan asring tubrukan karo System Restore failed to extract the original copy of the directory from the restore point (0x80070002 / 0x80070017). 2. Kapindho, Pemulihan Sistem grafis ngganti kabeh sarang lan mbalekake atusan file driver/eksekusi ing disk, dene mung nyalin file sing rusak. SYSTEM utawa SOFTWARE sarang saka HarddiskVolumeShadowCopyN butuh 10 detik lan ninggalake sarang liyane (SAM, SECURITY) ora kena.

Langkah 1: Dhaptar kabeh Salinan Volume Shadow sing kasedhiya ing disk¶

Ing WinRE Command Prompt, mbukak:

vssadmin list shadows

Contents of shadow copy set ID: {4b9128a1-8812-4091-a910-112938475610}
   Contained 1 shadow copies at creation time: 10/30/2026 11:14:02 PM
      Shadow Copy ID: {99182736-1122-3344-5566-77889900aabb}
         Original Volume: (D:)\\?\Volume{12345678-0000-0000-0000-100000000000}\
         Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy1

Langkah 2: Verifikasi hives pendaptaran ing Volume Salinan Shadow¶

Amarga standar cd utawa dir printah kadhangkala keselak ing \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy1 path namespace kernel, sampeyan bisa ngliwati path ing kuotasi kanggo dir, utawa gawe pranala simbolis sing trep (mklink /d) ing D:\ nuding langsung menyang Shadow Copy:

# Create a folder symlink on D:\ pointing into the newest Shadow Copy (e.g., ShadowCopy1):
mklink /d D:\ShadowMount \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy1\

# Inspect the file sizes and dates of the registry hives inside that Shadow Copy:
dir D:\ShadowMount\Windows\System32\config

Langkah 3: Nyalin MUNG sarang sing rusak saka Shadow Copy menyang D:\Windows\System32\config\¶

Upamane tes sampeyan ing Tahap 2 Langkah 3 nuduhake yen SYSTEM gagal mbukak (utawa loro-lorone SYSTEM lan SOFTWAREgagal).

Jalanake printah sing tepat kanggo ngganti sing rusak SYSTEM (lan/utawa SOFTWARE) resik-resik:

# 1. Remove the dirty .LOG1 / .LOG2 files for the hive being replaced (already backed up in D:\Config_Emergency_Backup)
attrib -h -s -r D:\Windows\System32\config\SYSTEM.LOG*
del D:\Windows\System32\config\SYSTEM.LOG1
del D:\Windows\System32\config\SYSTEM.LOG2

# 2. Copy the healthy SYSTEM hive from the Shadow Copy into D:\Windows\System32\config\
copy /y D:\ShadowMount\Windows\System32\config\SYSTEM D:\Windows\System32\config\SYSTEM

# (If SOFTWARE was ALSO broken in Phase 2 Step 3, run the same for SOFTWARE:)
attrib -h -s -r D:\Windows\System32\config\SOFTWARE.LOG*
del D:\Windows\System32\config\SOFTWARE.LOG1
del D:\Windows\System32\config\SOFTWARE.LOG2
copy /y D:\ShadowMount\Windows\System32\config\SOFTWARE D:\Windows\System32\config\SOFTWARE

# 3. Clean up the temporary symlink so you don't leave a dangling link on D:\
rmdir D:\ShadowMount

Langkah 4: Priksa manawa sarang sing dipulihake kanthi resik (reg load) lan mriksa CurrentControlSet¶

Test sing mentas disalin SYSTEM sarang akeh kanthi nol kesalahan:

reg load HKLM\TestRestored D:\Windows\System32\config\SYSTEM
reg query HKLM\TestRestored\Select
reg unload HKLM\TestRestored

HKEY_LOCAL_MACHINE\TestRestored\Select
    Current    REG_DWORD    0x1
    Default    REG_DWORD    0x1
    Failed     REG_DWORD    0x0
    LastKnownGood    REG_DWORD    0x2

Fase 4: Apa yen vssadmin list shadows Nuduhake No items found (0 Salinan Shadow)?¶

Apa yen Proteksi Sistem (VSS) dipateni kabeh ing drive, RegBack kosong, lan reg load gagal ing SYSTEM utawa SOFTWARE? Sampeyan isih duwe telung dalan pemulihan mundur sadurunge nginstal maneh Windows:

Fallback 1: Ngalih Default kanggo LastKnownGood (ControlSet002) ing njero SYSTEM¶

Yen reg load HKLM\TestSys D:\Windows\System32\config\SYSTEM kasil, lan BSOD (BAD_SYSTEM_CONFIG_INFO) kedadeyan amarga driver utawa kunci layanan ing njero ControlSet001 (Current = 0x1) wis rusak nalika ControlSet002 (LastKnownGood = 0x2) ing njero padha SYSTEM sarang utuh:

reg load HKLM\TestSys D:\Windows\System32\config\SYSTEM
reg query HKLM\TestSys\Select
# If ControlSet002 exists (verify via: reg query HKLM\TestSys\ControlSet002), switch Default from 1 to 2:
reg add HKLM\TestSys\Select /v Default /t REG_DWORD /d 2 /f
reg unload HKLM\TestSys

Fallback 2: Priksa C:\Windows\System32\config\TxR\ lan C:\Windows.old\Windows\System32\config\¶

Priksa manawa fitur PC sing bubar nganyari dibangun (22H2 -> 23H2 -> 24H2) utawa duwe Manajer Transaksi Kernel (TxR) log wadah:

dir /a D:\Windows.old\Windows\System32\config
dir /a D:\Windows\System32\config\TxR

Fallback 3: Muter nganyari kumulatif setengah diinstal (dism /RevertPendingActions)¶

asring, BAD_SYSTEM_CONFIG_INFO utawa CRITICAL_PROCESS_DIED occurs amarga PC ilang daya ing 30% sak Working on updates... Don't turn off your computer, budhal SOFTWARE lan \Windows\WinSxS\pending.xml metu saka sinkronisasi. Saka ing WinRE Command Prompt, ngandhani Layanan lan Manajemen Gambar Penyebaran (DISM) mesin kanggo mbalekake kabeh transaksi nganyari sing ora ditindakake marang gambar Windows offline (D:\):

mkdir D:\Scratch
dism /Image:D:\ /Cleanup-Image /RevertPendingActions /ScratchDir:D:\Scratch

Fallback 4: Ndandani Data Konfigurasi Boot sing ora bisa diwaca (BCD) toko (bootrec /rebuildbcd lan bcdboot)¶

Apa yen kabeh limang hives pendaptaran nang D:\Windows\System32\config\ mbukak lan mbongkar resik karo reg load, nanging PC isih mbuwang 0xc000014c (The Boot Configuration Data for your PC is missing or contains errors) utawa 0xc000000f? Amarga Windows BCD file sing didhelikake 100 MB Partisi Sistem FAT32 EFI (\EFI\Microsoft\Boot\BCD) dhewe disimpen ing binar sing padha regf format hive pendaptaran minangka SYSTEM lan SOFTWARE, mundhut daya bisa ngrusak ing BCD hive nalika ninggalake D:\Windows\System32\config\ ora kena. Mbangun maneh merek-anyar BCD hive ing Partisi Sistem EFI ing 15 detik:

diskpart
list volume
# Find the 100 MB to 300 MB FAT32 EFI System Partition (e.g. Volume 2)
select volume 2
assign letter=S
exit

# Back up the old broken BCD hive and generate a fresh one from D:\Windows:
ren S:\EFI\Microsoft\Boot\BCD BCD.bak
bcdboot D:\Windows /s S: /f UEFI

Tahap 5: Ngaktifake maneh otomatis RegBack serep ing Windows 10 lan Windows 11¶

Sawise PC Windows sampeyan bali ing desktop, aktifake maneh Microsoft sing wis diinstal RegIdleBackup tugas dadi C:\Windows\System32\config\RegBack\ otomatis diisi saben minggu, lan verifikasi System Restore (VSS) aktif:

• ** Aktifake maneh otomatis RegBack serep sarang ing Windows 10 (1803+) lan Windows 11**: Bukak Command Prompt (Run as Administrator) lan jalanake printah registri resmi siji iki (KB4509719):

  reg add "HKLM\System\CurrentControlSet\Control\Session Manager\Configuration Manager" /v EnablePeriodicBackup /t REG_DWORD /d 1 /f
  

  Banjur micu tugas serep sapisan langsung kanggo verifikasi C:\Windows\System32\config\RegBack isi karo salinan sehat kabeh limang hives:

  schtasks /run /tn "\Microsoft\Windows\Registry\RegIdleBackup"
  dir C:\Windows\System32\config\RegBack
  

• Verifikasi Proteksi Sistem (VSS Mulihake Points) diuripake ON kanggo C:: Tekan Win + R, jinis sysdm.cpl ,4, pilih Panjenengan C: drive, klik ** Konfigurasi **, pilih ** Aktifake proteksi sistem **, nyetel Max Usage kanggo 5% (10 GB kanggo 25 GB), banjur klik Gawe kanggo nggawe salinan bayangan garis dasar sing resik saiki.
• ** Mlayu sfc /scannow lan DISM /Online /Cleanup-Image /RestoreHealth** sawise boot menyang Windows kanggo verifikasi ora ana DLL sistem utawa manifests nyimpen komponen (COMPONENTS hive) rusak nalika kacilakan.

Nomer darurat regional lan protokol agensi¶

Nalika Windows BAD_SYSTEM_CONFIG_INFO BSOD biasane masalah IT internal utawa ndandani komputer pribadi, stasiun kerja utawa kegagalan server sing mengaruhi rumah sakit, kiriman darurat, utawa infrastruktur umum mbutuhake eskalasi langsung:

• Amerika Serikat lan Kanada: Nelpon 911 yen kacilakan Windows mateni pemantauan pasien klinis, kiriman darurat (CAD), utawa kontrol urip-safety, lan ngalih menyang prosedur downtime fasilitas. Laporake bootloop perusahaan sing nyebar amarga nganyari agen keamanan utawa kedadeyan cyber menyang CISA (1-844-Say-CISA / cisa.gov/report) utawa Pusat Keamanan Siber Kanada (1-833-CYBER-88).
• Inggris Raya: Nelpon 999 kanggo ancaman kanggo urip utawa gangguan klinis NHS akut. Laporkan insiden cyber utawa kasedhiyan utama menyang NCSC (ncsc.gov.uk) utawa NHS England Cyber Operations.
• Uni Eropa: Nelpon 112 ing kabeh negara anggota EU. Entitas sing dilindhungi miturut NIS2 Directive kudu nglaporake gangguan operasional sing signifikan menyang CSIRT nasional sajrone 24 jam.
• Australia lan Selandia Baru: Nelpon 000 ing Australia utawa 111 ing Selandia Anyar; laporake insiden infrastruktur kritis menyang ACSC (1300 CYBER1).
• India lan Asia-Pasifik: Nelpon 112 ing India kanggo nanggepi darurat; nglaporake prasarana utawa kedadeyan cyber menyang CERT-In (incident@cert-in.org.in).

Pitakonan sing kerep ditakoni¶

Apa yen profil pangguna dhewe gagal mlebu sawise boot ("We can't sign in to your account" / Profil sementara) amarga NTUSER.DAT wis rusak?¶

Saliyane limang hives sistem nang `\Windows\System32\config\`, saben akun pangguna duwe hive pendaptaran dhewe (`HKEY_CURRENT_USER`) disimpen ing **`C:\Users\\NTUSER.DAT`** (tambah `AppData\Local\Microsoft\Windows\UsrClass.dat`). Yen PC boots menyang layar login nggoleki, nanging mlebu mbukak desktop sauntara kosong amarga `NTUSER.DAT` rusak nalika mati listrik, mbukak Command Prompt munggah pangkat, mbukak `vssadmin list shadows`, lan nyalin sehat `NTUSER.DAT` metu saka `\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy1\Users\\NTUSER.DAT` (nalika mlebu menyang akun administrator kapindho utawa WinRE supaya file ora dikunci).

Ngapa WinRE njaluk 48-digit BitLocker Recovery Key sadurunge ngidini kula mbukak Command Prompt, nalika aku tau nguripake BitLocker ing dhewe?¶

Ing meh kabeh modern Windows 11 (lan Windows 10) laptop karo `TPM 2.0` lan Modern Standby, mlebu nganggo Akun Microsoft sajrone persiyapan awal kanthi otomatis ngaktifake **Enkripsi Piranti (`BitLocker`)** ing latar mburi lan upload kunci pemulihan 48 digit menyang Akun Microsoft sampeyan. Buka **`https://aka.ms/myrecoverykey`** ing smartphone sampeyan, mlebu nganggo Akun Microsoft (`@outlook.com`, `@hotmail.com`, `@gmail.com`) utawa ID Entra Kerja/Sekolah (`myaccount.microsoft.com`) digunakake ing PC sing, lan ketik tombol 48 digit cocog karo `Key ID` ditampilake ing layar. Sawise mbukak kunci, `D:\Windows\System32\config` wis rampung diakses ing WinRE Command Prompt.

Apa yen copy gagal karo The process cannot access the file because it is being used by another process nalika aku nyoba kanggo nimpa SYSTEM utawa SOFTWARE ing WinRE?¶

Kesalahan kasebut kedadeyan amarga salah siji saka rong alasan: (1) sampeyan ora sengaja ngetik `C:\Windows\System32\config\SYSTEM` nalika `C:` utawa `X:` iku sejatine disk WinRE RAM sing urip (`X:\Windows\System32\config\SYSTEM` dikunci dening WinRE dhewe; tansah verifikasi huruf drive SSD offline nyata `D:` utawa `E:` karo `diskpart -> list vol`); utawa (2) sampeyan mlayu `reg load HKLM\TestSys D:\Windows\System32\config\SYSTEM` sadurungé ing sesi lan lali kanggo mbukak **`reg unload HKLM\TestSys`** sadurunge mlaku `copy`.

Apa PC sandi crash karo BAD_SYSTEM_CONFIG_INFO (0x00000074) malah ing installer Windows USB anyar sadurunge ndemek SSD?¶

Yen `BAD_SYSTEM_CONFIG_INFO` (`0x00000074`) kedadean nalika booting ** anyar Windows 10/11 USB installer stick** (ing ngendi installer mbukak dhewe `boot.wim` RAM registri hive menyang memori sistem), registri SSD sampeyan ** ora ** masalah: ** RAM sistem sampeyan (`DDR4 / DDR5`) ngrusak hive registri ing memori nalika mbukak **. Ketik motherboard sampeyan `BIOS / UEFI` setelan (`Del` utawa `F2`), mateni `XMP / EXPO` profil overclocking memori supaya RAM mlaku ing kecepatan JEDEC standar, utawa nyoba karo siji kelet RAM ing wektu nggunakake `MemTest86`.

Bisa Antivirus pihak katelu utawa Deteksi Endpoint (EDR) nganyari driver kernel nyebabake loop BSOD sing katon kaya korupsi registri?¶

ya wis. Driver keamanan mode kernel (`BOOT_START` pembalap karo `Start = 0` ing njero `HKLM\SYSTEM\ControlSet001\Services\`) dimuat dening `winload.efi` bebarengan karo `SYSTEM` hive sadurunge Windows malah initializes video. Yen cacat `.sys` file ing `D:\Windows\System32\drivers\` tubrukan nalika boot, sampeyan ora perlu ngganti hive pendaptaran: mung ngganti jeneng masalah `.sys` file ing `D:\Windows\System32\drivers\` (utawa beban `D:\Windows\System32\config\SYSTEM` karo `reg load HKLM\TestSys` lan ngganti layanan sing rusak `Start` nilai saka `0` kanggo `4` [Patèni]).

Apa iku COMPONENTS hive nang C:\Windows\System32\config\, lan apa iku 100 MB?¶

Boten kados `SYSTEM`, `SOFTWARE`, `SAM`, `SECURITY`, lan `DEFAULT` (sing dimuat ing saben boot), ing **`COMPONENTS`** sarang (`C:\Windows\System32\config\COMPONENTS`) mung dimuat sacara dinamis on-demand nalika **Windows Update (`TiWorker.exe` / Component-Based Service)** utawa `sfc /scannow` mlaku. A rusak `COMPONENTS` hive ora bakal ** ora bakal mandhegake Windows saka booting (`0x00000074`), sanajan bakal nyebabake Pembaruan Windows gagal `0x80073712` nganti didandani karo `DISM /Online /Cleanup-Image /RestoreHealth`.

Pandhuan sing gegandhengan¶

• Layar biru Windows (BSOD) lan ndandani boot
• Kunci kunci pemulihan enkripsi BitLocker, FileVault, lan LUKS lan reset TPM
• BIOS lan UEFI firmware nganyari bata, mundhut daya, lan Dual-BIOS Flashback
• SSD lan NVMe modus mung maca dadakan, 0% blok cadangan, lan TRIM mateni nylametake
• Gagal hard drive lan Recovery data
• Serep komputer, strategi 3-2-1, lan pemulihan bencana
• Nomer darurat miturut negara

Sumber lan panuntun dhumateng resmi¶

• Microsoft Sinau (learn.microsoft.com): Mriksa bug 0x74: BAD_SYSTEM_CONFIG_INFO Referensi Pemecahan Masalah Resmi (BCD truncatememory / numproc Remediasi lan Registry Hive Verifikasi).
• Dhukungan Microsoft (KB4509719): Registry sistem ora digawe serep maneh menyang RegBack folder diwiwiti ing Windows 10 versi 1803 (EnablePeriodicBackup Konfigurasi Registry).
• Microsoft Windows Internals (7^th Edition, Russinovich et al.): Configuration Manager Architecture, Registry Hive Binary Structure (regf, hbin), lan Log Transaksi Ganda (.LOG1 / .LOG2) Pamulihan.
• Dokumentasi Panyimpenan Server Microsoft: Volume Shadow Copy Service (VSS) Administrasi (vssadmin list shadows lan GLOBALROOT Akses Ruang Jeneng Piranti).
• Institut Standar lan Teknologi Nasional (NIST) (Amerika Serikat): Publikasi Khusus 800-86: Analisis lan Pemulihan Forensik Registry Windows.