PC gives BSOD when loading Windows after clearing cmos

[new boy]

I was messing about with ram settings and got myself into an unrecoverable boot loop. I cleared the cmos by shorting the jumpers and now it posts fine and I can get into the bios but when loading into windows it crashes to a blue screen saying there is a problem with your device.

Pc specs are
windows 11
9800x3d
Asus tuf gaming b650m plus
32gb 6000mhz cl30 ram
9070XT

I've tried changing the following settings in bios with no luck

Launch CSM - default is disabled which I think is correct? I've tried enabling it though that reveals several other settings and I've not tried toggling each one between UEFI and legacy

Under secure boot OS type default is other OS but I've changed it to windows UEFI mode.

I've tried loading optimised default settings and then trying the above again.

is there anything else I might be missing? Id rather not reinstall windows if possible as I would loose like a month of progress on a single player game I'm playing but I guess it's not the end of the world if I have to...

Thanks

 

[Tetras]

is there anything else I might be missing? Id rather not reinstall windows if possible as I would loose like a month of progress on a single player game I'm playing but I guess it's not the end of the world if I have to...

If you have a spare drive you could disconnect the existing, install Windows fresh on the spare and grab the files on a secondary.

I cleared the cmos by shorting the jumpers and now it posts fine and I can get into the bios but when loading into windows it crashes to a blue screen saying there is a problem with your device.

That sounds like it corrupted the booting part?

Under secure boot OS type default is other OS but I've changed it to windows UEFI mode.

Is that what it was originally?

I assume you didn't use Windows Hello or have Bitlocker enabled?

 

[new boy]

If you have a spare drive you could disconnect the existing, install Windows fresh on the spare and grab the files on a secondary.


That sounds like it corrupted the booting part?


Is that what it was originally?

I assume you didn't use Windows Hello or have Bitlocker enabled?

Could probably find a spare sata SSD

Yeah I guess that's what messed it up

I'm not entirely sure what settings I had originally to be honest. When I first tried to install windows 11 it said my hardware was not compatible and I then changed some settings in the bios in order for the install to go ahead, I can't remember exactly what I changed though

I've not heard of hello or bitlocker, so if I would have to go out of my way to use them then I guess I do not use them.

 

[Fluffybob]

If you have a win11 usb you could always try a repair.

 

[new boy]

If you have a win11 usb you could always try a repair.

Repair was successful! The install looks like a complete wreck so I'll probably do a fresh install tomorrow, but I've managed to save my precious diablo 2 resurrected characters which is all I need lol.

Had to go through a chain of verifying email addresses that I haven't used for like 10 years which was fun.

I've not tried restarting it yet, scared I won't get back in.

 

[dazzlaa]

Good news! The lure of added performance can always end in disaster but happy you’ve made progress. I had an odd one last week where my system kept blue screening. Hadn’t changed settings or anything and it turned out to be a malfunctioning Nvme drive. That took a while to figure out! I usually remove all USB devices when diagnosing too, food for thought.

 

[ForrestGrump]

Repair was successful! The install looks like a complete wreck so I'll probably do a fresh install tomorrow, but I've managed to save my precious diablo 2 resurrected characters which is all I need lol.

Had to go through a chain of verifying email addresses that I haven't used for like 10 years which was fun.

I've not tried restarting it yet, scared I won't get back in.

Word to the wise. Always have your ‘my documents’’ folder on a drive other than your OS.
(Separate partition if not possible)

Following this procedure since Win 98 days has saved my bacon from a corrupt Windows install enough times to still recommend this policy today.

Be aware though, not all games honour this. Some store them in the roaming profile, some store them in the application data folder.

At the very least, use this as an opportunity to devise a backup plan for your data. You won’t always be so lucky. And it becomes a habit that you’ll be glad off if and when that time comes.