Question Im unable to boot into windows.

[DragonBeast13]

I'll start at the beginning for context.A few days ago I slammed my desk (don't ask why) and I got a blue screen. I thought nothing of it until a day or 2 later something similar happened, however this time when I tried to turn it back on, I got to the login page of Windows, typed my password in, and blue-screened immediately. I've been unable to boot since then. I've tried many things. No, it's not a hardware issue - everything is connected and detected by the computer. I checked. Twice. I also used kali linux since I have a USB to check if everything is working properly. It is. I tried running different commands in cmd from WinRe but with no luck. That was until yesterday
.I figured out that if I leave the PC trying to load into Windows long enough, I get an error:

WerFault.exe - Application Error

The instruction at 0x00007ffb581ad4d2 referenced memory at 0x0000000000000007. The memory could not be read.

Click on OK to terminate the program.
Click on CANCEL to debug the program.

(Im unable to click on either one)
.I was looking at possible solutions and tried running a few bcdboot commands, however got a problem with bootrec /fixboot - access is denied. I tried fixing it by following the instructions here- https://answers.microsoft.com/en-us...s-denied/747c4180-7ff3-4bc2-b6cc-81e572d546df . At one point, I read somewhere that the issue could be coming from safe boot being enabled in the bios, so I restarted and went in to check, it was indeed on and when I turned it off, restarted and tried to get into WinRE I got this:
Recovery
Your PC/Device needs to be repaired
The Boot Configuration Data file doesn't contain valid information for an operating system.
File: \BCDError Code: 0xc0000098
You'll need to use recovery tools, if you don't have any installation media (like a disc or USB device) contact your PC administrator or PC/Device manufacturer

Press F1 to enter Recovery Environment
Press Esc for UEFI Firmware Settings.

I DID manage to fix this and am now able to boot into WinRE normally. However the other issue persists- can't boot into windows. Another thing that may be important - when I try booting into Safe Mode, I get this error:
LogonUI.exe - System error
The system detected an overrun of stack-based buffer in this application. This overrun could potentially allow a malicious user to gain control of this application.

Here's a list of my parts (it's a desktop).
CPU: Ryzen 7 5700x
GPU: Gigabyte RTX 3050 OC
RAM: 4 x 8GB Patriot Viper Steel
MOBO: Asrock B450M Steel Legend
SSD (with the OS on it) - Adata XPG Gammix S11 Pro 512GB
PSU: Aerocool Lux 750W Bronze
I use Windows 10 Pro 64 bit

 

[Ralston18]

Update your post to include system hardware specs and OS information.

Desktop, laptop? Where does the system sit in relation to the desk?

Update your post to include full system hardware specs and OS information.

= = = =

Offer to chat noted. However, under no circumstances should you provide any such information to anyone agreeing to chat. This is a world wide Forum and any chat conversations may end badly.

 

[USAFRet]

The back story:

Question - Can't boot into windows after hitting my desk.

So a few days ago I was playing some game and naturally got mad, so I hit my desk. My PC is located at the other end of the desk and at that second I got a blue screen. I thought nothing of it (maybe some connecter moved or something) and everything was fine. Then, yesterday something similar...

forums.tomshardware.com

 

[DragonBeast13]

Update your post to include system hardware specs and OS information.

Desktop, laptop? Where does the system sit in relation to the desk?

Update your post to include full system hardware specs and OS information.

= = = =

Offer to chat noted. However, under no circumstances should you provide any such information to anyone agreeing to chat. This is a world wide Forum and any chat conversations may end badly.

I've updated with the software and hardware info. As the other person noted, I did already post about this but I had far less info back then and just thought I should redo it.

The PC is on top of the desk, at the furthest end from where I hit it.


Also, I'm sorry for the offer at the end, I didn't know this wasn't allowed

 

[Ralston18]

- No problem regarding "chat offer". Key point being that you did not engage anyone. That is for your protection.

= = = =

This motherboard?

https://download.asrock.com/Manual/B450 Steel Legend.pdf

Try clearing CMOS per physically numbered Page 27. (Check that the CMOS battery is fully in place.)

Again doublecheck by sight and feel that all connectors, cards, RAM, jumpers, and case connections are fully and firmly in place. Remember to check the I/O panel and all applicable cables.

With power off and unplugged use a bright light to inspect for any signs of damage.

Next try reverting back to a single RAM module and then work your way through the various RAM configurations suppored via the Motherboard's User Guide/Manual.

Overall premise being that the hit to the desk jolted something loose and/or resulted in some component breaking or getting zapped.

Work from as basic configuration as possible and add thereafter.

Immediate objective simply being to achieve a sucessful boot into Windows.

There may be other ideas and suggestions posted.

 

[DragonBeast13]

Clearing CMOS is something a few others have suggested so it's the first thing I'll try tomorrow since I don't have the jumper required and will need to get one (I know I can use a screwdriver, I just don't wanna risk touching something else for example).

I am certain everything in the computer is in place. I also tried booting my friend's PC with my SSD, and vice versa, with my computer working fine with another SSD with Windows on it, and my friend's PC having the same issue as me with my SSD inside of it. So I guess the hit somehow caused a software issue, something that corrupted the Windows installation. I have checked with bootlog and noticed that a few drivers aren't loading so I may look into that. I'll update with more information later