Windows 10: System Crash Without Blue Screen

Yesterday, my PC suddenly crashed, but instead of a Blue Screen, the screen just went black. After about 10 seconds, the system restarted on its own. There was no error message or warning before it happened.I checked Event Viewer, and i can see this errors : -The previous system shutdown at 10:53:37 PM on ‎3/‎29/‎2025 was unexpected. 6008 at 11:23:46-The description for Event ID 56 from source Application Popup cannot be found. Either the component that raises&

:)

 

my system keeps on crashing. (blue screen)

Hello Harrison,

A stop error (also called a "blue screen" error) can occur if a problem causes your PC to shut down or restart unexpectedly. These errors can be caused by both hardware and software issues.

To better assist you with your concern, I'd like to know the following:

• Confirm which build is currently installed on your device. To check, follow the steps below:

• Press Windows key + R, then type in winver.
• Click OK.

• Were there any recent changes made prior to this issue?
• What is the make and model of your device?

Meanwhile, we recommend performing the suggested steps in this article to troubleshoot blue screen issues
on Windows 10.

Looking forward to your response.

Regards.

 

Crash/blue screen

Hi

I assume from the title of your post Crash/Blue Screen that the PC has crashed and produced a *BSOD=[Blue Screen Of Death] =Blue Screen; and that the PC recovered from this; if and when you see the Blue Screen write the Stop Code down; recover the PC or use one that is working to access the net and look up the Stop Code.

nb: You may be able to view this with a [*BlueScreenView] application, google for this.

Edit Link - Blue screen of death (STOP error) information in dump files.

Description
===========

BlueScreenView scans all your minidump files created during 'blue screen
of death' crashes, and displays the information about all crashes in one
table. For each crash, BlueScreenView displays the minidump filename, the
date/time of the crash, the basic crash information displayed in the blue
screen (Bug Check Code and 4 parameters), and the details of the driver
or module that possibly caused the crash (filename, product name, file
description, and file version).
For each crash displayed in the upper pane, you can view the details of
the device drivers loaded during the crash in the lower pane.
BlueScreenView also mark the drivers that their addresses found in the
crash stack, so you can easily locate the suspected drivers that possibly
caused the crash.

atb

Law-II

 

Blue Screen - PAGE_FAULT_IN_NONPAGED_AREA

Correct, the page file was turned off for a while. This was one of the steps listed as a possible solution to the blue screen crash we were getting. The last crash or two were run with the page file system turned back on and set to "system managed size"