Windows 10: BSOD windows 11 UNEXPECTED STORE EXCEPTION bugcheck code error 154

the BSOD occurred when the PC was turned on during the password entry screen, the mouse and keyboard input devices did not respond and after about a minute the PC showed the blue screen.I attach the dump file for further information. What could be the problem?************* Preparing the environment for Debugger Extensions Gallery repositories ************** ExtensionRepository : Implicit UseExperimentalFeatureForNugetShare : false AllowNugetExeUpdate : false NonInteractiveNuget : true AllowNugetMSCredentialProviderInstall : false AllowParallelInitializationOfLocalReposi

:)

 

Unexpected store exception

Here are the images for point 14





- - - Updated - - -

15

--------------- SeaTools for Windows v1.4.0.7 ---------------
Model Number: WDC WD5000AAKX-0
Serial Number: WD-WCC2E1PHXLZK
Firmware Revision: 1H19
Long Generic - Started 23/11/2019 14:35:37
Long Generic - Pass 23/11/2019 16:08:13

--------------- SeaTools for Windows v1.4.0.7 ---------------
Model: Elements 1023
Serial: WXU1EA0KCDF2
Firmware: 2005
Long Generic - Started 23/11/2019 14:35:38
Long Generic - FAIL 23/11/2019 17:17:31

I didn't find a way to see a more generic log of the failure.

- - - Updated - - -

16











Let me know if I forgot something

 

unexpected-store-exception-bsod

I saw this error " unexpected-store-exception ", then my laptop restarted. At boot screen it shows disk checking and after completion I reached my lock screen, where I entered my password. then it goes blank. I had to force shut down. I tried to use the
steps in

Redirecting

but i cant even reach my task manager.

Please tell me what I can do to fix this

 

Unexpected store exception

Windows shutdowns occur to prevent damage.

The bugcheck was 0x00000154: UNEXPECTED_STORE_EXCEPTION
This indicates that the store component caught an unexpected exception.

There was EXCEPTION_CODE: (NTSTATUS) 0xc0000006 - The instruction at 0x%p referenced memory at 0x%p. The required data was not placed into memory because of an I/O error status of 0x%x.

Windows has exception handlers and if an exception could corrupt data or cause system malfunctions there is a bugcheck to prevent further damage.

Drive file system problems can cause BSOD.


These may be useful:
Blue screen of death - Wikipedia
Everything You Need To Know About the Blue Screen of Death
4 BSOD Errors That Can Kill Your PC and their Solutions