Sudden BSOD, hard drive and SSD, temporarily invisible

Page 1 of 2 12 LastLast

  1. Posts : 374
    Windows 10-64 bit (version 1909 build 18363.628)
       #1

    Sudden BSOD, hard drive and SSD, temporarily invisible


    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
    CBS.zip

    I am also enclosing reports about my hard drives which were generated by Hard Disk Sentinel software.
    HARD DRIVE REPORTS.zip

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


  2. Posts : 98
    Win 10 Pro 21H2
       #2

    I'll put my money on its being a RAM problem.

    I've had enough wild unpredictability and inconsistent symptoms caused by RAM to conclude when everything else seems to be OK, the problem is RAM.
      My Computer


  3. Posts : 890
    10 Pro/11 Pro Dual Boot
       #3

    archz2 said:
    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
    CBS.zip

    I am also enclosing reports about my hard drives which were generated by Hard Disk Sentinel software.
    HARD DRIVE REPORTS.zip

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

    Before posting a BSOD thread, please read the instructions here: Blue Screen of Death (BSOD) Posting Instructions

    If you need to add new information, please make a new post in your initial BSOD thread. Please do not make an extra new thread.
      My Computers


  4. Posts : 374
    Windows 10-64 bit (version 1909 build 18363.628)
    Thread Starter
       #4

    Here is the zip file for log collector.

    - - - Updated - - -

    bratkinson said:
    I'll put my money on its being a RAM problem.

    I've had enough wild unpredictability and inconsistent symptoms caused by RAM to conclude when everything else seems to be OK, the problem is RAM.

    Okay. I have two RAM sticks of 8GB each installed in my laptop. How do I fully ensure that it's a RAM problem and whether both sticks have to be replaced or only one? And which one do I replace?

    - - - Updated - - -

    Today when I restarted my laptop, I got this BSOD. 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.
    Sudden BSOD, hard drive and SSD, temporarily invisible-img20220708190710.jpg

    I feel that this error is something to do with the EFI system partition on my SATA hard drive.

    Sudden BSOD, hard drive and SSD, temporarily invisible-image.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.
    Sudden BSOD, hard drive and SSD, temporarily invisible Attached Files
      My Computer


  5. Posts : 98
    Win 10 Pro 21H2
       #5

    The boot failure blue screen happening during a reboot but not 30 minutes later tells me it's a temperature problem. In that vein, I'm still thinking it could be RAM getting too hot. But it could be the C: drive SSD as well although CHKDSK didn't find any errors.

    I'd start with the easier of the two...remove one of the sticks of RAM and see if the problem happens. If so, swap it with the other and try again. Hopefully, 1 stick is bad and the other is good. Alternatively, download a RAM testing program that will thoroughly stress-test your RAM and it would show any problems. I'd do the download if the problem doesn't go away after both sticks of RAM have been tried individually.

    If the RAM proves to be good, then try the same procedure with the SSDs. It's the old process of elimination. Prove what it's NOT, and what's left has to be the solution.
      My Computer


  6. Posts : 2,800
    Windows 7 Pro
       #6

    Hi,

    If this is a clean installation you are working on ?

    I would remove all drives except the SSD I want to be my System drive and delete all partitions on it and redo a clean installation.

    I would then connect back the HDD, remove all partitions on it and create one simple NTFS volume.

    Out of curiosity... How did you end up with two simple volumes with different size and the Same Drive letter "D" on the same physical disk ???
      My Computers


  7. Posts : 374
    Windows 10-64 bit (version 1909 build 18363.628)
    Thread Starter
       #7

    bratkinson said:
    The boot failure blue screen happening during a reboot but not 30 minutes later tells me it's a temperature problem. In that vein, I'm still thinking it could be RAM getting too hot. But it could be the C: drive SSD as well although CHKDSK didn't find any errors.

    I'd start with the easier of the two...remove one of the sticks of RAM and see if the problem happens. If so, swap it with the other and try again. Hopefully, 1 stick is bad and the other is good. Alternatively, download a RAM testing program that will thoroughly stress-test your RAM and it would show any problems. I'd do the download if the problem doesn't go away after both sticks of RAM have been tried individually.

    If the RAM proves to be good, then try the same procedure with the SSDs. It's the old process of elimination. Prove what it's NOT, and what's left has to be the solution.
    Alright. Tinkering with my laptop hardware physically isn't something I'm too comfortable with. I'd proceed with the RAM testing using a software. Should I use this one?
    MemTest86 - Download now!

    - - - Updated - - -

    MaloK said:
    Hi,If this is a clean installation you are working on ?
    Kind of, yeah. The formatting of SSD and clean installation of Windows mentioned in the original post was done on Sunday 3rd July.
    MaloK said:
    I would remove all drives except the SSD I want to be my System drive and delete all partitions on it and redo a clean installation.I would then connect back the HDD, remove all partitions on it and create one simple NTFS volume.
    I deleted all the partition on SSD, formatted them and did a fresh install of Windows on 3rd July itself. I didn't disconnect my HDD while doing all this.
    MaloK said:
    Out of curiosity... How did you end up with two simple volumes with different size and the Same Drive letter "D" on the same physical disk ???
    Whoa! I have no idea. I just noticed! Sharing another screenshot which shows disk management and my explorer side by side.

    Sudden BSOD, hard drive and SSD, temporarily invisible-image.png
      My Computer


  8. Posts : 98
    Win 10 Pro 21H2
       #8

    Memtest86 is what I used 4 years ago while trying to figure out why my computer would randomly freeze for a minute or two, then pick up where it left off like nothing happened. It showed me, even with tests that ran several hours, that my RAM was OK.

    Looking at your latest post, I noticed that your SSD boot drive is not in the drive 0 slot. I know that should be OK but I've never dealt with it before. Double check the 'boot sequence' settings in BIOS to unconditionally force drive 0 to be the first boot drive. Letting BIOS figure it out for itself might be why you got the 'no bootable drive' BSOD.
      My Computer


  9. Posts : 2,800
    Windows 7 Pro
       #9

    Loll, from your screen shots your logical drives are adding up to expected size. But how this could occurred is beyond my understanding.

    But... Since the drive is dynamic.

    You could maybe have merged two partitions, I never tried such operations.

    At the moment your boot files are residing on your logically flawed "dynamic" disk. You can revert from it to Basic disk but it have a chance to fail.

    That is why I suggested a clean install with only your SSD installed before adding any data drives...

    In you case the data drive should also be cleaned and reinitialized properly before use.
      My Computers


  10. Posts : 4,511
    several
       #10

    It is more usual to span across different disks.

    Third party partitioners can often merge partitions , but I am not sure how many will do it with dynamic disks.
    Aomei partition assistant has something called dynamic disk manager which comes with pro version, I have never used it, but it might be able to do that. It might then be able to convert the disk.


    https://answers.microsoft.com/en-us/...6-9a90457bb4e4
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 17:41.
Find Us




Windows 10 Forums