Hello all,

So yesterday I was just watching some YouTube when suddenly my screen started glitching out, as in the colour hues would change, there’d be distortions, and there clearly was some static in places as well… Anyways, I restarted my computer and then came up to a BIOS BSOD instead of a Windows BSOD (below)

Windows Failed to start. A recent hardware or software change might be the cause. To fix the problem:

1. Insert your windows installation disc and restart your computer.

2. Choose your language settings, and click “Next. ”

3. Click “Repair your personal computer. ”

If you don’t have this disc, contact your system administrator or computer manufacturer for assistance

Status: 0xc0000185

Info: An unexpected error has occurred.

I tried restarting several times, and got a mistake code 0xc000000f once or twice aswell. So , I put the windows recovery software on an USB stick, booted from the stick, and attempted a repair, and got the Windows couldn’t repair your personal computer error without log file. I tried all the other options as well and none of them worked.

Next, I used a Windows to go bootable USB stick using Rufus to get some more information on the drive and to attempt some data recovery, however I came across some interesting results… The drive would appear in file explorer, but whenever I left clicked it to open it would say “H: \ is not accessible. A device which does not exist was specified. ” When checking device manager, it shows up as KBG30ZMV512G TOSHIBA and tells me “This device is working properly. ” … Thanks windows… When I go to the volume section though of the device properties, it’s all empty until I populate (don’t know if this is normal or not), however when I populate it says

Disk: Disk 0

Type: Basic

Status: Online

Partition style: GUID Partition Table (GPT)

Capacity: 488386 MB

Unallocated space; 1 MB

Reserved space: 128 MB

Volumes

Volume	Capacity
(H: )	467088 MB

However when I click properties on it, it says

Used Space: 0 bytes 0 bytes

Free Space: 0 bytes 0 bytes

Another thing that was super odd, is that when I clicked Scan for hardware changes in device manager, the drive would just disappear until I restarted my computer.

Next, I tried to make use of DISKPART in command prompt to see what information that tells me, here’s the output to several commands if it helps

$list disk (NOTE: Disk an is my Windows to begin USB)

Disk ###	Status	Size	Free	Dyn	Gpt
Disk the most affordable	Online	57 GB	0 B

$list volume

Volume###	Ltr	Label	Fs	Type	Size	Status	Truth
Stazza 0	H		RAW	Partition	456 GIGABITE	Healthy
Volume 1		System	FAT32	Partition	300 MB	Healthy	Nonvisual
Volume a pair		WinRE options	NTFS	Partition	900 MEGABYTES	Healthy	Hidden
Volume 3			RAW	Partition	19 GB	Healthy	Disguised
Volume nearly four	C	CCCOMA_X64F	NTFS	Partition	57 GB	Healthy	Structure
Volume 1	E	UEFI_NTFS	FAT	Subdivision	1024 KB	Healthy

I discovered , it very odd from when I tried $select cd 0, it was able to look at it, even though it wasn’t classified by $list disk… I made an effort various commands through DISKPART that I found easeus. com to recover my data however it that didn’t work

I also decided to consider some data recovery software, Write-up tried Disk Drill, Recuva, stellar, and EaseUs and none of them were able to read with.

At this point While i kind of gave up on data recovery (although if anybody supports any ideas of things i could try it would be immensely appreciated, I do have some brilliant memories on that operate that I’d prefer to rather than lose) so I attempted to arrangement the drive through the operating system 10 recovery USB… I was ready unable to format, or remove any partitions as it would probably simply just error out.

After this, I tested out using Speccy to see so what information it would give, your idea gave me the following information

▼Hard brings

▼KBG30ZMV512G TOSHIBA (SSD)

Developer: TOSHIBA

Interface UNKNOWN

Volume: 0 B

Real width: 0 bytes

RAID Reproduce: None

▼S. M. The. R. T

S. Michael. A. R. T certainly not supported

▼Partition 0

Rupture ID: Disk #0, Partition #0

File System: FAT32

Numbers Serial Number: 8C4A7467

Of zynga poker chips: 296 MB

Used Market: 27. 3 MB (9%)

Free Space: 268 MB (91%)

▼Partition 1

Coupure ID: Disk #0, Partition #0

Disk Letter H:

▼Partition 2

Partition INSIDE DIAMETER: Disk #0, Partition #2

File System: NTFS

Volume Culebrón Number: 8E4E8017

Size: 899 MB

Used Space: 458 MB (50%)

Free A muslim: 441 MB (50%)

▼Partition 3

Partition ID: Compact disk #0, Partition #3

I also jogged an Ubuntu bootable OBTAINABLE to see if I would get more information, nvme still wasn’t detected, although the dmesg command gave most output regarding it

nvme nvme0: I/O 85 QID 1 additional time, aborting

nvme nvme0: I/O 86 QID 1 timeout, aborting

nvme nvme0: I/O 85 QID 1 timeout, reset controller

nvme nvme0: I/O 20 QID 0 timeout, reset controller

nvme nvme0: Device not can’t wait; aborting reset, CSTS=0x1

blk_update_request: I/O error, dev nvme0n1, sector 7112112 op 0x0: (READ) flags 0x80700 phys_seg 14 prio class 0

blk_update_request: I/O error, dev nvme0n1, sector 7112368 op 0x0: (READ) flags 0x80700 phys_seg 8 prio grouping 0

nvme nvme0: Desist status: 0x371

nvme nvme0: Abort status: 0x371

nvme nvme0: Device not in place; aborting reset, CSTS=0x1

nvme nvme0: Removing after übung failure status: -19

nvme nvme0: Device not willing and able; aborting reset, CSTS=0x1

nvme0n1: detected capacity change from 1000215216 to 0

Buffer I/O error on dev nvme0n1p3, logical block 6233520, async page read

Buffer I/O error on dev nvme0n1p3, logical block 6233521, async page read

Buffer I/O error on dev nvme0n1p3, logical block 6233522, async page read

Buffer I/O error on dev nvme0n1p3, logical block 6233523, async page read

Buffer I/O error on dev nvme0n1p3, logical block 6233524, async page read

Buffer I/O error on dev nvme0n1p3, logical block 6233525, async page read

Buffer I/O error on dev nvme0n1p3, logical block 6233526, async page read

Buffer I/O error on dev nvme0n1p3, logical block 6233527, async page read

Buffer I/O error on dev nvme0n1p4, logical block 0, async page read

Buffer I/O error on dev nvme0n1p5, logical block 0, async page read

loop0: perceived capacity change from 0 that will 4462928

I ordered a new nvme off of Amazon and And also the arriving today, however issue one is salvageable I’d a little more than willing to return the application. Right now I just want to know n’ t simply is able to recover resources off of it myself, whether it really isn’t possible if, I’d consider sending the vehicle off to a data recovery site. If I do, based on the critical info I’ve provided does anyone have a general idea re how much it would cost (in $CAD)? thanks!