Question Fell asleep watching Dune then woke up to BSOD. Now "error: no such partition. grub rescue".

[Ripper509]

The reason why I mentioned the first part is because I don't know what could have happened to cause the bsod.

I have a Windows 10 and I am using a Kingston m.2 2 TB nvme drive as my OS drive. This might be the second time something like this has happened if not the third time within the past year so if I do somehow recover and resolve this issue I will be purchasing a new SSD drive as soon as possible. That said, I have done the following: I have enabled CSM support and selected the Kingston drive as boot priority #1 and that hasn't worked.

I then inserted Windows 10 media USB and try to repair startup but I get an error message. I then tried opening the command prompt and tried the all "bootrec" commands but to no avail.

Here is an interesting piece of information. Depending whether CSM is enable or disabled, my Gigabyte BIOS shows my Kingston m.2 drive—or should I say it is being recognized—by the BIOS but if I insert my Windows 10 media USB then choose install then search for a volume, disc or drive for the clean install, Windows does not see or recognize my Kingston m.2 drive. Something similar also occurs under the grub rescue command prompt. If I type LS, sometimes I will see an hd4 but even then when I do the set boot command it tells me the file system is unknown. At this point I'm at my wit's end and I don't know what to do everything was literally working when I was watching doing I fell asleep and woke up to a paused bsod. And then when I restarted a computer this is when this issue has happened.

Please don't tell me that my m.2 drive is fried. Both the BIOS and windows recognize all my other drives but there not used for the operating system just holding games and movies. Thank you for your time consideration and help.

Computer: GIGABYTE B660M DS3H AX DDR4

CPU: Intel Core i5-12600KF (Alder Lake-S 640, C0)

               3700 MHz (37.00x100.0) @ 4688 MHz (47.00x99.8)

Motherboard: GIGABYTE B660M DS3H AX DDR4

BIOS: F6a, 03/28/2022

Chipset: Intel B660 (Alder Lake-S PCH)

Memory: 32768 MBytes @ 1795 MHz, 18-22-22-42

               - 16384 MB PC28700 DDR4 SDRAM - Team Group TEAMGROUP-UD4-3600

               - 16384 MB PC28700 DDR4 SDRAM - Team Group TEAMGROUP-UD4-3600

Graphics: AMD Radeon RX 6800 XT

               AMD Radeon RX 6800 XT, 16384 MB GDDR6 SDRAM

Drive: Samsung SSD 840 EVO 120GB, 117.2 GB, Serial ATA 6Gb/s @ 6Gb/s

Drive: CT1000MX500SSD1, 976.8 GB, Serial ATA 6Gb/s @ 6Gb/s

Drive: KINGSTON SNVS2000G, 1953.5 GB, NVMe

Drive: TOSHIBA MQ01ABD100, 976.8 GB, Serial ATA 3Gb/s @ 3Gb/s <-> USB

Sound: Intel Alder Lake-S PCH - cAVS (Audio, Voice, Speech)

Sound: ATI/AMD Navi2x - High Definition Audio Controller

Network: Intel Wi-Fi 6 AX201 160MHz

Network: RealTek Semiconductor RTL8125 Gaming 2.5GbE Family Ethernet Controller

OS: Microsoft Windows 10 Professional (x64) Build 19043.1766 (21H1)

 

[Lutfij]

Welcome to the forums, newcomer!

When posting a thread of troubleshooting nature, it's customary to include your full system's specs. Please list the specs to your build like so:
CPU:
CPU cooler:
Motherboard:
Ram:
SSD/HDD:
GPU:
PSU:
Chassis:
OS:
Monitor:
include the age of the PSU apart from it's make and model. BIOS version for your motherboard?

Could be possible that the OS drive has conked out. You should try another port/slot on your motherboard to rule out a faulty slot. You could also take the presumed culprit SSD and then drop it into another known working motherboard to rule out your board's BIOS being the root issue.

 

[dwd999]

The reason why I mentioned the first part is because I don't know what could have happened to cause the bsod.

I have a Windows 10 and I am using a Kingston m.2 2 TB nvme drive as my OS drive. This might be the second time something like this has happened if not the third time within the past year so if I do somehow recover and resolve this issue I will be purchasing a new SSD drive as soon as possible. That said, I have done the following: I have enabled CSM support and selected the Kingston drive as boot priority #1 and that hasn't worked.

I then inserted Windows 10 media USB and try to repair startup but I get an error message. I then tried opening the command prompt and tried the all "bootrec" commands but to no avail.

Here is an interesting piece of information. Depending whether CSM is enable or disabled, my Gigabyte BIOS shows my Kingston m.2 drive—or should I say it is being recognized—by the BIOS but if I insert my Windows 10 media USB then choose install then search for a volume, disc or drive for the clean install, Windows does not see or recognize my Kingston m.2 drive. Something similar also occurs under the grub rescue command prompt. If I type LS, sometimes I will see an hd4 but even then when I do the set boot command it tells me the file system is unknown. At this point I'm at my wit's end and I don't know what to do everything was literally working when I was watching doing I fell asleep and woke up to a paused bsod. And then when I restarted a computer this is when this issue has happened.

Please don't tell me that my m.2 drive is fried. Both the BIOS and windows recognize all my other drives but there not used for the operating system just holding games and movies. Thank you for your time consideration and help.

It is possible that the data needed to boot the kingston was damaged and cannot be repaired using the windows media. So I would think outside of the windows box and boot from a usb containing a linux distro. If that successfully boots it would allow a review of the files available on the kingston and rescue of any essential data, or worse case scenario confirm if the kingston is dead. Then all of the existing data and partitions on the kingston could be deleted, leaving only the GPT table header and windows could be reinstalled.

 

[Ripper509]

Welcome to the forums, newcomer!

When posting a thread of troubleshooting nature, it's customary to include your full system's specs. Please list the specs to your build like so:
CPU:
CPU cooler:
Motherboard:
Ram:
SSD/HDD:
GPU:
PSU:
Chassis:
OS:
Monitor:
include the age of the PSU apart from it's make and model. BIOS version for your motherboard?

Could be possible that the OS drive has conked out. You should try another port/slot on your motherboard to rule out a faulty slot. You could also take the presumed culprit SSD and then drop it into another known working motherboard to rule out your board's BIOS being the root issue.

Updated

 

[Ripper509]

Still nothing. In Gigabyte BIOS, if I disable CSM then I shows my M.2 drive but it's not bootable. When I enable it, I get the grub rescue.

 

[dwd999]

Still nothing. In Gigabyte BIOS, if I disable CSM then I shows my M.2 drive but it's not bootable. When I enable it, I get the grub rescue.

Random thoughts: what is this "grub rescue" and where is it coming from? And how many drives did you have connected when you installed Windows? The installer generally works better if only 1 drive is connected at installation time; others can be connected after installation is complete.

 

[Ripper509]

Random thoughts: what is this "grub rescue" and where is it coming from? And how many drives did you have connected when you installed Windows? The installer generally works better if only 1 drive is connected at installation time; others can be connected after installation is complete.

Command prompt at boot.

 

[Ripper509]

At this point, I might have to take it to a repair shop.

 

[Ripper509]

https://imgur.com/a/A2Vvjt6

View: https://imgur.com/a/A2Vvjt6