Black Screen on Windows 10 Boot after game crashing(even in safe mode)

Hi everyone!

A couple of days ago I was playing Cyberpunk 2077 and it crashed a couple of times, I kinda fixed that by lowering the graphics, but then it crashed again and froze up my entire laptop. It wasn't overheated, I kept extra ventilation on. I forced it to shut down and ever since then I'm getting infinite black screen on boot after the MSI logo. After each 2-3 restarts I could access the blue screen with different options, such as Safe Mode. But booting the Safe Mode also ends up either in endless black screen or endless MSI logo.

I've tried fixing it with different cmd commands suggested online and Windows standard troubleshooting options from the blue screen. No luck. My Windows is installed on SSD. I've made a partition on my HDD and installed another Windows 10 there, it works absolutely fine if I choose it, but the old one still doesn't. I couldn't go into the SSD's directory in command prompt for a while, got a lot of "Access denied" stuff, but when I got into Windows and changed the security settings for the drive it became possible and now I can access everything on the drive. It doesn't seem to be damaged, but it still doesn't show up in BIOS.

I haven't downloaded any files or installed any updates or drivers recently.

I'd rather not reinstall the Windows on SSD but even if there's no other way, can I even be sure it'd help?

I'd be incredibly grateful if anyone could help me with this issue or explain how a game can possibly do this much damage, it's so confusing.

Blue Screen of Death (also known as a blue screen or BSoD) is an error screen displayed on a Windows computer system after a fatal system error, also known as a system crash: when the operating system reaches a condition where it can no longer operate safely.

Its usually buggy device driver causes the BSoD error.

BSOD - Posting Instructions

FreeBooter said:

Blue Screen of Death (also known as a blue screen or BSoD) is an error screen displayed on a Windows computer system after a fatal system error, also known as a system crash: when the operating system reaches a condition where it can no longer operate safely.

Its usually buggy device driver causes the BSoD error.

BSOD - Posting Instructions

It's not really BSoD, only the Troubleshoot screen with Advanced options in it which appears if Windows cannot start normally a few times in a row, I don't know if that counts as BSoD

Try using this boot method.

How to use a Lazesoft Windows Recovery CD or USB device to fix the boot problems if your Windows operating system does not start correctly.
"It is very common for PC users to be faced with a Windows crash. When this happens, the dreaded 'Blue Screen of Death' pops up, or your PC has a black screen and can not boot or start up"

Lazesoft Recovery Suite Home
Download Lazesoft Recovery Suite Home 4.3.1
Lazesoft Recovery Suite Free, Free Windows System Recovery, Free Data Recovery, Free Windows Password Recovery, Free Disk Clone
Screenshot ( SS )
https://i.imgur.com/c9viJO4.gif
https://i.imgur.com/LaEidXn.gif
Tutorials
Tutorials - Lazesoft Recovery Suite Software
How to Boot a Computer from a Lazesoft Recovery USB Device
How to Boot a Computer from a Lazesoft Recovery USB Device
How to Burn a Lazesoft Recovery CD
Lazesoft - How to burn a recovery CD

eeslea said:

Hi everyone!

but it still doesn't show up in BIOS.

Sorry, this isn't correct, it does.

- - - Updated - - -

jmatt said:

Try using this boot method.

Unfortunately, this didn't help.

If you open the log file, you’ll be shown details of all the tests performed by Startup Repair, with any errors discovered detailed. We can use this information to help diagnose and get to the root cause of the problem.



To open log file from the Windows Recovery Environment, click and open the Command Prompt. When the Command Prompt is open, type Notepad and press Enter key to open the Notepad application. The Startup Repair log file is located at:

Code:

C:\Windows\System32\Logfiles\Srt\SrtTrail.txt

You will need to navigate to the drive on which you have Windows installed (usually the C: drive) to see the SrtTrail.txt log file.

Sorry it's in Russian.

Диагностика средства восстановления запуска и журнал восстановления
---------------------------
Число попыток восстановления: 1

Подробные сведения о сеансе
---------------------------
Системный диск = \Device\Harddisk1
Каталог Windows = D:\WINDOWS
Запуск AutoChk = 0
Число основных причин = 1

Выполненный тест:
---------------------------
Имя: Проверка обновлений
Результат: Успешно завершено. Код ошибки = 0x0
Затраченное время = 0 мсек

Выполненный тест:
---------------------------
Имя: Проверка системного диска
Результат: Успешно завершено. Код ошибки = 0x0
Затраченное время = 16 мсек

Выполненный тест:
---------------------------
Имя: Диагностика сбоев диска
Результат: Успешно завершено. Код ошибки = 0x0
Затраченное время = 0 мсек

Выполненный тест:
---------------------------
Имя: Проверка метаданных диска
Результат: Успешно завершено. Код ошибки = 0x0
Затраченное время = 312 мсек

Выполненный тест:
---------------------------
Имя: Проверка метаданных диска
Результат: Успешно завершено. Код ошибки = 0x0
Затраченное время = 16 мсек

Выполненный тест:
---------------------------
Имя: Проверка целевой операционной системы
Результат: Успешно завершено. Код ошибки = 0x0
Затраченное время = 31 мсек

Выполненный тест:
---------------------------
Имя: Проверка содержимого тома
Результат: Успешно завершено. Код ошибки = 0x0
Затраченное время = 250 мсек

Обнаружена основная причина:
---------------------------
На диске поврежден системный том.

Исправление: Проверка файловой системы (chkdsk)
Результат: Успешно завершено. Код ошибки = 0x0
Затраченное время = 22203 мсек

---------------------------
---------------------------

The last part says there was a corrupt system volume and it was fixed with chkdsk, nothing else.

The problem is we don't know what is causing black screen so i would not know where to start troubleshooting.

"Sorry it's in Russian"
If needed again, use this.
russian to english - Google Search
Startup Repair Diagnostics and Recovery Log
---------------------------
Restore Attempts: 1

Session details
---------------------------
System Disk = \ Device \ Harddisk1
Windows directory = D: \ WINDOWS
AutoChk launch = 0
Number of root causes = 1

Test performed:
---------------------------
Name: Check for Updates
Result: Completed successfully. Error code = 0x0
Elapsed time = 0 ms

Test performed:
---------------------------
Name: Check system disk
Result: Completed successfully. Error code = 0x0
Time taken = 16 ms

Test performed:
---------------------------
Name: Diagnose Disk Failures
Result: Completed successfully. Error code = 0x0
Elapsed time = 0 ms

Test performed:
---------------------------
Name: Check disk metadata
Result: Completed successfully. Error code = 0x0
Time taken = 312 ms

Test performed:
---------------------------
Name: Check disk metadata
Result: Completed successfully. Error code = 0x0
Time taken = 16 ms

Test performed:
---------------------------
Name: Check target operating system
Result: Completed successfully. Error code = 0x0
Time elapsed = 31 ms

Test performed:
---------------------------
Name: Checking the contents of the volume
Result: Completed successfully. Error code = 0x0
Time taken = 250 ms

Root Cause Found:
---------------------------
The system volume on the disk is damaged.

Fix: File System Check (chkdsk)
Result: Completed successfully. Error code = 0x0
Time taken = 22203 ms

- - - Updated - - -

Next step.

"Root Cause Found:
---------------------------
The system volume on the disk is damaged."

Googling that error, here is a video, he uses AOMEI, this version will be Ok.
AOMEI Partition Assistant Standard Edition
Download AOMEI Partition Assistant Standard Edition 9.2
AOMEI Partition Assistant Standard Edition 9.2 Free Download - FreewareFiles.com - Utilities Category
AOMEI Partition Assistant Standard Edition 9.2 Screenshot - Freeware Files.com
Free Partition Manager Software for Windows - AOMEI Partition Assistant Standard

Video link.
How To Fix System Volume on Disk is Corrupt Error For All Windows? [Solved] - YouTube

You will have to use Diskpart command to find out the System Reserved partition drive letter.
The output of the below commands may display the name of the System Reserved partition as only System or ESP.

Type diskpart and press Enter.
Type list volume and press Enter.
Under the label row, find the label System Reserved and note its corresponding Volume number.
Now type select Volume=N and press Enter, where N is the Volume number you noted earlier.
Now type assign letter=w and press Enter.
Type exit and press Enter.
Type bcdboot C:\Windows /s w: /f ALL and press Enter.


Please replace partition letter C: with Windows installed partition letter. When computer boots into Windows Recovery Environment (WinRE) environment the drive letter assign to Windows partition may not be C: drive letter because Windows 7, 8 , 8.1 and 10 creates a separate system partition when it's installed from scratch. The system partition contains boot files WinRE assigns the system partition the C: drive letter and the Windows installed partition will be assign any other drive letter usually D: drive letter is assign to Windows installed partition. The Bcdedit /enum | find "osdevice" command can be use to find out the drive letter of the Windows installed partition the output of the Bcdedit command is similar to this osdevice partition=D:. The drive letter after partition= is the drive letter of the Windows partition.