PC got freeze or BSOD when launching the game

[鬼櫻]

I’ve been dealing with this issue since launch day. When I get lucky, I can play the game smoothly for a while, but most of the time, it crashes and freezes my PC repeatedly. Even after rebooting multiple times, the problem persists, and it’s incredibly frustrating. I’ve tried every suggestion I could find on this forum and Reddit, including reinstalling the game, doing a clean reinstall of my NVIDIA drivers, rolling back to a previous NVIDIA driver version, clearing the download cache, and more—nothing has worked.

Some users have mentioned that DS4 might be causing crashes or freezes lately, but I’m using a wired Xbox 360 controller. If I disable Steam Input, the game doesn’t even recognize my controller.

Is there anything else I can try to fix this? Thanks for any help!

[鬼櫻]

Ursprünglich geschrieben von アンジェル:

Ursprünglich geschrieben von 鬼櫻:

Yup, in both safe mode and command line mode

Then it can be only fixed in startup repair mode.

That is so annoying - but at least it is not that bad if you got the drive from your friend.

The startup repair mode is a tad difficult to get into. I think you need to keep pressing F8 or DEL while booting the system, then you get asked in that special repair mode.

Have you done that before?

I saw that in the boot menu. And all it does is just loading for a few second and bring me back to the menu.

[アンジェル]

Ursprünglich geschrieben von c3lix:

Try this
https://answers.microsoft.com/en-us/windows/forum/all/windows-10-bootrec-fixboot-access-is-denied/747c4180-7ff3-4bc2-b6cc-81e572d546df

ONCE you are in Windows take a Look at the Windows Event Manager, it should Show the Problem of the errors

That is a good tip. I did something similar.

For me it was

diskpart
select disk 2
list part
select partition 1
del par override
exit

Very important: you need to identify the one you are using, and the one you are not using - and then select to delete the one you are not using. BE VERY CAREFUL ABOUT THAT!!!

First in cmd as admin

diskpart

there you see the partitions

then check which is okay and which not. You can alternatively right click on Windows icon in taskbar and select disk management to find it.

[鬼櫻]

Ursprünglich geschrieben von アンジェル:

Ursprünglich geschrieben von c3lix:

Try this
https://answers.microsoft.com/en-us/windows/forum/all/windows-10-bootrec-fixboot-access-is-denied/747c4180-7ff3-4bc2-b6cc-81e572d546df

ONCE you are in Windows take a Look at the Windows Event Manager, it should Show the Problem of the errors

That is a good tip. I did something similar.

For me it was

diskpart
select disk 2
list part
select partition 1
del par override
exit

Very important: you need to identify the one you are using, and the one you are not using - and then select to delete the one you are not using. BE VERY CAREFUL ABOUT THAT!!!

First in cmd as admin

diskpart

there you see the partitions

then check which is okay and which not. You can alternatively right click on Windows icon in taskbar and select disk management to find it.

I am now using a media usb to use the startup repair. Hope this can help.

Update: nvm, it fail to fix

[鬼櫻]

Ursprünglich geschrieben von c3lix:

Try this
https://answers.microsoft.com/en-us/windows/forum/all/windows-10-bootrec-fixboot-access-is-denied/747c4180-7ff3-4bc2-b6cc-81e572d546df

ONCE you are in Windows take a Look at the Windows Event Manager, it should Show the Problem of the errors

It seems that none of my drive is labeled as EFI
https://uploadimage.io/image/1000051344.MW2Am

[アンジェル]

Ursprünglich geschrieben von 鬼櫻:

Ursprünglich geschrieben von アンジェル:

That is a good tip. I did something similar.

For me it was

diskpart
select disk 2
list part
select partition 1
del par override
exit

Very important: you need to identify the one you are using, and the one you are not using - and then select to delete the one you are not using. BE VERY CAREFUL ABOUT THAT!!!

First in cmd as admin

diskpart

there you see the partitions

then check which is okay and which not. You can alternatively right click on Windows icon in taskbar and select disk management to find it.

I am now using a media usb to use the startup repair. Hope this can help.

Update: nvm, it fail to fix

Ursprünglich geschrieben von 鬼櫻:

Ursprünglich geschrieben von c3lix:

Try this
https://answers.microsoft.com/en-us/windows/forum/all/windows-10-bootrec-fixboot-access-is-denied/747c4180-7ff3-4bc2-b6cc-81e572d546df

ONCE you are in Windows take a Look at the Windows Event Manager, it should Show the Problem of the errors

It seems that none of my drive is labeled as EFI
https://uploadimage.io/image/1000051344.MW2Am

Unfortunately I cannot read that. If I have to guess disk 5 might be an issue, but it is worth to check with Windows disk management

and normally the commands above:

bootrec /FixMbr
bootrec /FixBoot
bootrec /ScanOs
bootrec /RebuildBcd

are supposed to fix it - while in repair mode, were you able to try them out again?

[鬼櫻]

Ursprünglich geschrieben von アンジェル:

Ursprünglich geschrieben von 鬼櫻:

I am now using a media usb to use the startup repair. Hope this can help.

Update: nvm, it fail to fix

Ursprünglich geschrieben von 鬼櫻:

It seems that none of my drive is labeled as EFI
https://uploadimage.io/image/1000051344.MW2Am

Unfortunately I cannot read that. If I have to guess disk 5 might be an issue, but it is worth to check with Windows disk management

and normally the commands above:

bootrec /FixMbr
bootrec /FixBoot
bootrec /ScanOs
bootrec /RebuildBcd

are supposed to fix it - while in repair mode, were you able to try them out again?

https://uploadimage.io/image/image.MWcV1
I think the Disk 0 part 1 and Disk 1 part 2 is used for EFI
What should I do next?

Edit: I am now working with Grok step by step and it definec Disk 0 Vol 1 is the part we want. After assigned it as V:, I can find it in the File Explorer. When I click on it, access denied again. I will keep going with Grok now

[アンジェル]

Ursprünglich geschrieben von 鬼櫻:

Ursprünglich geschrieben von アンジェル:

Unfortunately I cannot read that. If I have to guess disk 5 might be an issue, but it is worth to check with Windows disk management

and normally the commands above:

bootrec /FixMbr
bootrec /FixBoot
bootrec /ScanOs
bootrec /RebuildBcd

are supposed to fix it - while in repair mode, were you able to try them out again?

https://uploadimage.io/image/image.MWcV1
I think the Disk 0 part 1 and Disk 1 part 2 is used for EFI
What should I do next?

Edit: I am now working with Grok step by step and it definec Disk 0 Vol 1 is the part we want. After assigned it as V:, I can find it in the File Explorer. When I click on it, access denied again. I will keep going with Grok now

From my point of view it is disk 1-1 , 1-2, 1-5 which are causing the troubles and should be removed (all on D: according to the image).

So if that is correct it should be in terminal in safe mode

diskpart
select disk 1
list part
select partition 1
del par override
select partition 2
del par override
select partition 6
del par override
exit

Please check if it is shown correctly using the diskpart tool

[アンジェル]

Post Scriptum: thinking about that, considering how small D: is, it might be much easier for you putting all data from D: to C: , then just format D: completely using the disk management tool, making the whole partition a storage partion.

What do you think about that?

[鬼櫻]

Ursprünglich geschrieben von アンジェル:

Post Scriptum: thinking about that, considering how small D: is, it might be much easier for you putting all data from D: to C: , then just format D: completely using the disk management tool, making the whole partition a storage partion.

What do you think about that?

I think it is a good idea, but I just formatted disk 0 vol 1. Do I need to format D: in the property or in cmd?

[アンジェル]

Ursprünglich geschrieben von 鬼櫻:

Ursprünglich geschrieben von アンジェル:

Post Scriptum: thinking about that, considering how small D: is, it might be much easier for you putting all data from D: to C: , then just format D: completely using the disk management tool, making the whole partition a storage partion.

What do you think about that?

I think it is a good idea, but I just formatted disk 0 vol 1. Do I need to format D: in the property or in cmd?

You can use the disk management tool for formatting it completely - that is definitely easier. Just right click on the parts, and delete volume - one by one, until it changes from a drive with many partitions just to one single drive. So it looks like this when you are done
https://i.ibb.co/7tQ2T8XF/screenshot-1742232852.png

Afterwards, it might be necessary to reinstall the efi, if you formatted 0-1

so it is correctly only on C: and not on D:

[鬼櫻]

Ursprünglich geschrieben von アンジェル:

Ursprünglich geschrieben von 鬼櫻:

I think it is a good idea, but I just formatted disk 0 vol 1. Do I need to format D: in the property or in cmd?

You can use the disk management tool for formatting it completely - that is definitely easier. Just right click on the parts, and delete volume - one by one, until it changes from a drive with many partitions just to one single drive. So it looks like this when you are done
https://i.ibb.co/7tQ2T8XF/screenshot-1742232852.png

Afterwards, it might be necessary to reinstall the efi, if you formatted 0-1

so it is correctly only on C: and not on D:

I have reinstalled the efi on d0v1 according to Grok. But I still cannot run the fixboot command after all the task. I have formatted D: as well, but all the vol are still here. I think I need to do it in command line.

On the other hand, should I turn back on the UEFI mode and Secure Boot?

Edit: I have run the command line as well and all here is the disk list:
https://uploadimage.io/image/image.MWiir

[アンジェル]

Ursprünglich geschrieben von 鬼櫻:

Ursprünglich geschrieben von アンジェル:

You can use the disk management tool for formatting it completely - that is definitely easier. Just right click on the parts, and delete volume - one by one, until it changes from a drive with many partitions just to one single drive. So it looks like this when you are done
https://i.ibb.co/7tQ2T8XF/screenshot-1742232852.png

Afterwards, it might be necessary to reinstall the efi, if you formatted 0-1

so it is correctly only on C: and not on D:

I have reinstalled the efi on d0v1 according to Grok. But I still cannot run the fixboot command after all the task. I have formatted D: as well, but all the vol are still here. I think I need to do it in command line.

On the other hand, should I turn back on the UEFI mode and Secure Boot?

Edit: I have run the command line as well and all here is the disk list:
https://uploadimage.io/image/image.MWiir

Yeah. Seems the command line approach is safer with safe mode.

And when you are done, yes, turn back on UEFI mode and secure boot after everything is good. That way you will be protected from actual boot malware

[鬼櫻]

Ursprünglich geschrieben von アンジェル:

Ursprünglich geschrieben von 鬼櫻:

I have reinstalled the efi on d0v1 according to Grok. But I still cannot run the fixboot command after all the task. I have formatted D: as well, but all the vol are still here. I think I need to do it in command line.

On the other hand, should I turn back on the UEFI mode and Secure Boot?

Edit: I have run the command line as well and all here is the disk list:
https://uploadimage.io/image/image.MWiir

Yeah. Seems the command line approach is safer with safe mode.

And when you are done, yes, turn back on UEFI mode and secure boot after everything is good. That way you will be protected from actual boot malware :mhwgood:

Thanks so much for your help and time, I really appreciate it. You nearly being my tech support for whole day. Wish you a good day mate!

[アンジェル]

Ursprünglich geschrieben von 鬼櫻:

Ursprünglich geschrieben von アンジェル:

Yeah. Seems the command line approach is safer with safe mode.

And when you are done, yes, turn back on UEFI mode and secure boot after everything is good. That way you will be protected from actual boot malware

Thanks so much for your help and time, I really appreciate it. You nearly being my tech support for whole day. Wish you a good day mate!

You too. Happy Hunting!

[mudcrab]

check the minidump file and use windbg to review error code.
search the error code on google for solution.

also probably wise to do an in-place window upgrade:
https://answers.microsoft.com/en-us/windows/forum/all/how-to-run-in-place-upgrade-in-windows-11/4d469147-2747-4dcb-88a4-aae9273a4500