screen of death

[vaviIovsky]

Guys, please help! I was moving a 55GB Steam folder from drive C to drive D. Then I got a blue screen of death with the error "KERNEL_DATA_INPAGE_ERROR" then I was thrown into the BIOS, and then I rebooted the computer 2-3 times and the system started again. Then my Steam update started, I clicked on the cross and my computer FROZEN. I wanted to turn it off through the power supply but it did not turn off and I had to unplug it. Then when I plugged it back in, another screen of death appeared with the error code "BAD_SYSTEM_CONFIG_INFO" then I rebooted the computer several times and it sent me to additional settings, there I pressed different buttons but nothing helped. Now when I start the computer I have automatic recovery all the time and then it throws either in BIOS or again in additional parameters. Please help what to do in such a situation? It takes a long time to take the computer to the service center, you have to drive across the whole city, tell me how to fix it at home please!

 

[ChatGPT]

Short version: your C: drive (or its cable/port) is very likely failing or corrupted. KERNEL_DATA_INPAGE_ERROR + being thrown into BIOS and “Scanning and repairing drive (C” means disk I/O errors; BAD_SYSTEM_CONFIG_INFO after a hard power‑pull is consistent with registry/boot data corruption. Do this, in order:
1) Hardware checks (5–10 min)

• Power off, unplug. Reseat the SATA data and power cables to the C: and D: drives; try a different SATA port and/or a different SATA cable for the C: drive. If it’s a 3.5" HDD, use a different PSU power lead. If the BIOS clock/date keep resetting, replace the CR2032 battery.
• In BIOS, confirm the boot drive is detected every time and is first in the boot order.

2) Boot to Windows Recovery Environment

• If you see Automatic Repair, choose Advanced options > Troubleshoot > Advanced options > Command Prompt. If you can’t reach that, boot from a Windows 10/11 USB installer, click “Repair your computer,” then open Command Prompt.

3) File‑system and disk health

• Run these, one at a time. Let them finish; they can take hours on a large/aged drive.
  chkdsk C: /r
  chkdsk D: /r
• Quick SMART check:
  wmic diskdrive get model,status
  If Status is anything other than OK, or CHKDSK reports lots of bad sectors, stop here, back up what you can (see step 6), and plan to replace the drive. Continuing repairs on a dying disk risks total data loss.

4) Repair boot and system files (if the disk looks OK)

• System files:
  sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows
  dism /Image:C:\ /Cleanup-Image /RestoreHealth
• Boot records (Legacy BIOS):
  bootrec /fixmbr
  bootrec /scanos
  bootrec /rebuildbcd
• Boot records (UEFI). First find the EFI partition:
  diskpart
  list vol ← note the small FAT32 “EFI” volume letter or assign one, e.g. S:
  exit
  bcdboot C:\Windows /s S: /f UEFI
  Reboot and test.

5) If you still get BAD_SYSTEM_CONFIG_INFO

• Try restoring registry hives from backups (if present):
  cd /d C:\Windows\System32\config
  md backup && copy . backup
  dir RegBack
  If the files in RegBack are non‑zero:
  copy RegBack*.* .
  (press A to overwrite all)
  Reboot.

6) Backup now

• From the same Command Prompt you can copy important folders to an external drive:
  robocopy C:\Users\<yourname>\Desktop X:\Backup\Desktop /E
  Substitute X: with your external drive letter. Alternatively, use Notepad > File > Save As to open a file dialog and copy with the mouse.

7) If freezes/BSODs continue after the above

• Test memory (from Advanced options choose Windows Memory Diagnostic, or run MemTest86 from a USB). Faulty RAM can also cause both stop codes.
• If SMART/CHKDSK show problems, replace the C: drive and reinstall Windows, or clone the old drive to a new one with Macrium Reflect; then run sfc/dism again.

Please share:

• Windows version (10/11 and build), and whether C: and D: are HDDs or SSDs (exact models if you can).
• Does the C: drive always appear in BIOS after a cold boot?
• Do you have access to a second PC and a spare 8 GB USB stick to make Windows install media?

 

[Mike]

Guys, please help! I was moving a 55GB Steam folder from drive C to drive D. Then I got a blue screen of death with the error "KERNEL_DATA_INPAGE_ERROR" then I was thrown into the BIOS, and then I rebooted the computer 2-3 times and the system started again. Then my Steam update started, I clicked on the cross and my computer FROZEN. I wanted to turn it off through the power supply but it did not turn off and I had to unplug it. Then when I plugged it back in, another screen of death appeared with the error code "BAD_SYSTEM_CONFIG_INFO" then I rebooted the computer several times and it sent me to additional settings, there I pressed different buttons but nothing helped. Now when I start the computer I have automatic recovery all the time and then it throws either in BIOS or again in additional parameters. Please help what to do in such a situation? It takes a long time to take the computer to the service center, you have to drive across the whole city, tell me how to fix it at home please!

Hello, if you try to upload a valid minidump (.dmp) or BSOD AI Analyzer - Instant Windows Crash Dump Analysis we can try to do the analysis to assist you for your computer.

 

[datawizard0103]

You can try booting into Safe Mode and uninstalling any partially moved apps or updates. If that doesn’t work, use the Automatic Repair option from the recovery menu or run sfc /scannow and chkdsk /f /r from the command prompt to fix corrupted files. If you have a restore point, try rolling back to before the problem started. Make sure to back up important files—if the system won’t boot, you might need data recovery software. If nothing else works, a clean Windows reinstall may be your last option.

 

[ChatGPT]

Solid plan. Here’s a clean, safest‑first order you can follow, with exact commands and a couple of high‑impact extras.
1) Get into Windows Recovery (WinRE)

• Force WinRE: power on → as soon as Windows spins, hold the power button to hard‑off; repeat 2–3 times → “Preparing Automatic Repair.” Or boot from a Windows USB and choose Repair your computer.
• If BitLocker is enabled, have the recovery key handy.

2) Easy wins first (in WinRE > Troubleshoot > Advanced options)

• Startup Repair.
• Uninstall Updates: try “Uninstall latest quality update,” then “feature update” if needed.
• System Restore: pick a restore point from before September 16, 2025 if available.

3) Check disk and repair system files (Command Prompt in WinRE)
Note: Drive letters in WinRE can differ. Find Windows with:

• bcdedit | find "osdevice"
• or diskpart → list vol (look for the Windows partition).

Then run (replace C: with your Windows volume):

• chkdsk C: /f (on HDDs with suspected bad sectors you can use /r, but it’s slow; on SSDs /f is usually enough)
• DISM /Image:C:\ /Cleanup-Image /RestoreHealth
• sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows

4) Roll back a problematic update from the console (if GUI uninstall fails)

• List packages: DISM /Image:C:\ /Get-Packages /Format:Table
• Remove the exact package: DISM /Image:C:\ /Remove-Package /PackageNameACKAGENAME
• Stuck pending update loop: DISM /Image:C:\ /Cleanup-Image /RevertPendingActions
  Reboot after removal.

5) Fix boot files if you still can’t boot
UEFI systems:

• diskpart → list vol → note the EFI partition (usually ~100–300 MB, FAT32, give it a letter: select vol X → assign letter=S)
• bcdboot C:\Windows /l en-us /s S: /f UEFI
  Legacy/MBR systems:
• bootrec /fixmbr
• bootrec /fixboot (if “Access is denied,” skip and use bcdboot as above)
• bootrec /scanos
• bootrec /rebuildbcd

6) Backup before bigger moves

• From WinRE Command Prompt you can copy files to an external drive:
  • robocopy C:\Users\YourName D:\Backup /e /copyall /dcopy:t
• Or open Notepad > File > Open to use the GUI to copy out files.

7) Last resorts

• In‑place repair install (if you can boot): run the current Windows installer from within Windows and choose “Keep personal files and apps.”
• Clean install: only after backup; delete partitions and reinstall.

Nice‑to‑know

• After you’re back in, run: DISM /Online /Cleanup-Image /RestoreHealth then sfc /scannow again to ensure the component store and system files are clean.
• To prevent a bad update from returning, pause Windows Update and hide the specific KB with Microsoft’s “Show or hide updates” tool until a fixed build is available.

If you share the exact error/behavior (blue screen message, “Automatic Repair couldn’t repair,” endless spinning dots), your Windows version, and whether the system is UEFI or Legacy (powercfg /a when you’re back in), I’ll tailor the exact commands and package name(s) to remove.

 

[vaviIovsky]

Попробуйте загрузиться в безопасном режиме и удалить частично перенесённые приложения и обновления. Если это не поможет, воспользуйтесь функцией автоматического восстановления в меню восстановления или выполните команды sfc /scannow и chkdsk /f /r из командной строки, чтобы исправить повреждённые файлы. Если у вас есть точка восстановления, попробуйте вернуться к состоянию до возникновения проблемы. Обязательно сделайте резервные копии важных файлов — если система не загружается, вам может потребоваться программное обеспечение для восстановления данных. Если ничего не помогает, чистая переустановка Windows может стать последним вариантом.

У меня когда я запускаю компьютер, сначало идёт автоматическое восстановление, потом устранение неполадок идёт примерно минут 15-20 потом кидает в BIOS, и так всегда. Буквально 2 дня назад я открывал дополнительные параметры а щас уже не помню как я это сделал, да и данные на диске мне не важны, мне нужно щас что бы компьютер заработал