I can't start Windows.
I can't start Windows.
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-...e572d546df
. 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
The back story: Question - Can't start Windows after hitting my desk. A few days ago, while playing a game, I got frustrated and hit my desk. My PC was on the opposite side of the desk, and at that moment, I saw a blue screen. I didn’t think much of it (perhaps a cable shifted or something) and everything seemed normal. Then, yesterday something similar happened... forums.
I've made the updates to the software and hardware details. As mentioned earlier, I had limited information then and just wanted to refresh the post.
The PC is placed on top of the desk, at the farthest side from where I hit it.
Also, I regret the offer at the end—I didn't realize it wasn't permitted.
No worries about the "chat offer". The main focus is that you didn’t interact with anyone, just for your safety.
= = = =
This motherboard?
https://download.asrock.com/Manual/B450 Steel Legend.pdf
Consider resetting CMOS by physically moving Page 27 and ensuring the battery is securely positioned.
Verify again by visually and physically confirming all connectors, cards, RAM, jumpers, and case connections are properly seated.
Inspect the I/O panel and all relevant cables.
When power is off and the device is unplugged, use a bright light to look for any damage.
Then try restoring it to a single RAM module and proceed through the supported configurations in the User Guide/Manual.
The goal is to get a successful boot into Windows.
Other suggestions might be available.
Clearing CMOS is something others have recommended, so I plan to try it tomorrow because I don’t have the jumper and will need to obtain one (I understand I can use a screwdriver, but I prefer not to risk touching anything else).
I am confident everything is set correctly. I also tested booting my friend’s PC using my SSD, and vice versa; my computer worked fine with another SSD running Windows, while my friend’s PC had the same problem with their SSD inside. This suggests the issue might be a software problem that corrupted the Windows installation. I reviewed the bootlog and noticed several drivers weren’t loading, so I’ll investigate further. I’ll provide more details later.