What Went Wrong with My PC?

ImaDirt 0 Reputation points
2023-06-26T21:48:09.4166667+00:00

Need actual pros to help me here

https://pcpartpicker.com/list/RfF6JM

(List of Parts)

A few days ago I left my computer on in a minecraft world overnight. When I woke up it was in the BIOS. When I came home my ssd wasn’t detected in the boot menu. But after a few restarts I got my windows running perfectly. I got curious, so the next night I left my computer on and once again it was in the bios. This time it didn’t work. I ram the windows startup pair, but much to my despair, it gave me the red box with secure boot.

Errors I’ve recieved (That I remember):

Ntoskrnl.exe startup error while booting to hdd

/bcd startup error booting to hdd

Clock watchdog timeout installing windows

Windows crashes on install

And the most recent and important error, The headed checksum… while booting

What I have Tried In Order (Ran in repair windows or compact os)

Windows Repair - This caused me to get the secure boot red screen :/

Secure Boot on and off, and csm on and off - Holy shit the amount of times I have done this is horrific

Updating Bios - Nothing

Clearing CMOS - Also nothing

Compact OS - Worked twice, then crashed and stopped working.

Moving Ram - Didn’t do anything

Switching m.2 slots - Nothing

New windows install - Oddly crashed when I installed it with an ssd but installed when I installed it onto a hdd.

New SSD - same errors and I can’t even install windows on to it

chkdsk - errors every time doesn’t seem to do much.

sfc - similar to chkdsk doesn’t do anything and claims it can’t.

DISM - Exact same.

What I think it is-

bios setting

Windows for business | Windows Client for IT Pros | User experience | Other
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Limitless Technology 44,776 Reputation points
    2023-06-27T14:50:33.31+00:00

    Hello there,

    Have you checked the Event Viewer for any trace?

    If you cannot find anything in Event Viewer I would suggest you use tools like Procmon to find the root cause for this behaviour.

    Have you made any recent updates that you are aware of on this device? If so try uninstalling them and check if this sorts out the issue

    If you encounter an "ntoskrnl.exe" startup error while booting your computer to the HDD (hard disk drive), it typically indicates a problem with the Windows operating system. Here are some steps you can take to troubleshoot and resolve the issue:

    Restart your computer: First, try restarting your computer to see if the error resolves itself. In some cases, it could be a temporary glitch.

    Check hardware connections: Ensure that all hardware components, such as the HDD, RAM modules, and cables, are properly connected. Make sure there are no loose connections or faulty cables.

    Run startup repair: Boot your computer from a Windows installation or recovery media. Select the option to "Repair your computer" and choose "Startup Repair." This will attempt to fix any startup issues automatically.

    Check for disk errors: Use the Windows built-in disk checking utility, called "chkdsk," to scan and repair any errors on your HDD. Open Command Prompt as an administrator and run the command: chkdsk /f /r C: (replace "C:" with the appropriate drive letter if your Windows installation is on a different drive).

    Restore from a system restore point: If you have previously created a system restore point, you can try restoring your computer to a previous state where it was functioning properly. Boot your computer from a Windows installation or recovery media and choose the option to "Repair your computer." Select "System Restore" and follow the on-screen instructions.

    I used AI provided by ChatGPT to formulate part of this response. I have verified that the information is accurate before sharing it with you.

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.