Forum Discussion
Computer continuously crashing, different errors.
Previously imaged on windows 11 my computer would crash from time to time. Often when left along and not in active use. Tried playing a video to see if that would keep it up but it did not. After a while my computer stopped turning on going into a constant loop of the errors below. first 3 being blue screen and last being a pop up that would come up instead of a login screen. I tried to re image the computer but i continued to receive blue screen alerts. After looking up the alerts I saw it may be related to a RAM issue so I tested the RAM sticks 1 by 1, bought new RAM but still had the same issue. I brought it to a tech store which stated it seemed to be a problem with the ssd. i purchased a new SSD, installed windows 10 this time but still seem to be having issues with blue screen though not as often. Currently running into an issue where I've downloaded the below update, computer is pending restart but it never installs on updated. Seeking any help with this.
2025-10 Cumulative Update for Windows 10 Version 22H2 for x64-based Systems (KB5066791)
Attempted_execute_of_noexecute_MEMORY
IRQL_NOT_LESS_OR_EQUAL
ntoskrnl.exer
pop up: sign-in process initialization failure ; interactive sign-in process initialization has failed. please check the event log for details.
1 Reply
Because crashes continue after a clean image, replacement SSD, different Windows versions, and RAM changes, do not assume ntoskrnl.exe is the cause; it is often where Windows detected corruption. Restore BIOS defaults, disable XMP or overclocking, and install current BIOS, chipset, storage, and graphics drivers from the manufacturer. Disconnect nonessential devices and test one known-good memory module in each supported slot. Check Event Viewer for WHEA-Logger events at crash times, run Windows Memory Diagnostic, and preserve C:\Windows\Minidump before reinstalling. Microsoft treats varied stop codes as potentially hardware, driver, or software related, so dump stacks and WHEA data matter more than the kernel filename. Do not keep forcing KB5066791 while the machine is unstable. If it also crashes in Windows Recovery or a clean installer, arrange motherboard, CPU, power-supply, and GPU diagnostics. Otherwise, analyze the dumps with WinDbg or provide them to Microsoft support.
