Sudden BSOD, hard drive and SSD temporarily invisible

archz2

Well-known member
Joined
May 6, 2019
Posts
77
I am running Windows 10 Home Single Language, version 21H2, OS build 19044.1766. Recently I faced a trouble where my laptop kept going into startup loop. Discussion posted here.
Stuck in startup repair boot loop, C drive is in RAW


I eventually formatted my SSD and installed windows in it on 3rd July. The laptop ran absolutely fine on 4th July and 5th July. Today, 6th July all of a sudden while working, my laptop showed a blue screen and rebooted. The BSOD came for a split second and I could not photograph it. Then my laptop got into a startup repair loop. I booted using Win PE bootable drive and to my shock, neither my SSD nor my hard drive were being shown in the windows explorer. Then I rebooted my laptop again.

It got to my desktop screen normally. Then I ran chkdsk /f /r c: Then I agreed on the cmd prompt to run chkdsk after the laptop starts. The chkdsk ran during startup and then the laptop booted normally.


Then after my laptop booted normally, I ran sfc/ scannow in the admin cmd prompt.


After the scan got complete. I got this message.
Windows Resource Protection found corrupt files but was unable to fix some of them.
For online repairs, details are included in the CBS log file located at
windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline
repairs, details are included in the log file provided by the /OFFLOGFILE flag.



I tried rebooting my laptop into safemode (in order to run sfc scannow, so it fixes errors) and I got the same blue screen again. Then my laptop closed and started normally. So far it's running fine now but I'm quite concerned.

I ran "DISM /Online /Cleanup-Image /CheckHealth" in the admin cmd prompt and got this message.

No component store corruption detected.
The operation completed successfully.


I wanted to get the srt log file that gets mentioned when windows fails to repair startup. Unfortunately the folder "C:\Windows\System32\LogFiles\srt" does not exist.

Enclosing the cbs log. which was created during the sfc scannow process
I am also enclosing reports about my hard drives which were generated by Hard Disk Sentinel software.

I don't know what's going on. Please help.
 

Attachments

Last edited:
Today when I restarted my laptop, I got this BSOD.
IMG20220708190710.jpg







I kept pressing enter but I kept getting the same screen. Then I tried to run startup repair using bootable win10 usb drive but it failed to fix the trouble. Then I ran command prompt and I faced the same issue as before. None of my hard drives were listed in the diskpart.

I shutdown my laptop and went away for a while to do other work.

I returned after maybe 30 minutes or so and my laptop booted normally. I ran sfc /scannow and it found no issues.


I feel that this error is something to do with the EFI system partition on my D drive.
1657291212229.png

I recently did a clean installation of windows on my SSD (i.e. the C partition) by formatting it and deleting all the partitions on it by using the windows 10 installation UI. The installation of windows should have created a new EFI partition on my SSD but somehow it didn't. I don't know why.


When I bought this laptop originally in 2019, it came just with a SATA hard drive and I installed the OS on that. After 4-5 months, I installed an SSD into it and migrated the windows installation and software installation data using samsung utility that came with my SSD. The EFI partition that is seen in the SATA drive is from that period.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top