inaccessible_boot_device BSOD Windows 10

Sky-Knight said:
thanks to Win10 hating platters.
Click to expand...

Where do you get this stuff from?! It bears no resemblance to the reality I've been living with for years, where most of the machines I deal with are now Windows 10 machines, if they weren't at the outset, and are humming along quite nicely with conventional HDDs.
 
britechguy said:
Where do you get this stuff from?! It bears no resemblance to the reality I've been living with for years, where most of the machines I deal with are now Windows 10 machines, if they weren't at the outset, and are humming along quite nicely with conventional HDDs.
Click to expand...
You live in a magic fairy land I guess? Every single Win10 I've had on a platter has failed during an update somewhere. Sure, I can fix it with a DISM command, or I can SSD the thing and never see it again.

Age of the machine doesn't matter... the platter is the problem. It's happened hundreds of times, so it's not like I've got a small sample.

I swear the things reboot before something is complete during an update sometimes... and splat goes the OS. I've never quite nailed it down, all I know is an SSD equipped Win10 box never comes back for repairs, the platters do.
 
Sky-Knight said:
You live in a magic fairy land I guess? Every single Win10 I've had on a platter has failed during an update somewhere. Sure, I can fix it with a DISM command, or I can SSD the thing and never see it again.

Age of the machine doesn't matter... the platter is the problem. It's happened hundreds of times, so it's not like I've got a small sample.

I swear the things reboot before something is complete during an update sometimes... and splat goes the OS. I've never quite nailed it down, all I know is an SSD equipped Win10 box never comes back for repairs, the platters do.
Click to expand...
I had my first SSD failure last week. A Kingston (not mine). They're right, the failure is sudden and total.
 
I have yet to experience any solid-state storage device failure that isn't sudden and total. And heaven forfend that it's not backed up, as data recovery from any of them is far more expensive, and the result far less certain, than from HDDs.

That's one of the reasons I would never even consider using SSDs for backup purposes at this point in time.
 
I have seen one, and only one. It was blue screening the PC and failed the manufacture diagnostic test, Micron. But it amazingly let me clone without errors. Kept looking for the crosstown bus to hit me. Went too well...LOL.
 
I've had two SSDs over the years fail, and neither were sudden... but both were total.

They started out as intermittent hard locks, but spread out over 3-4 months which eventually resulted in the machine simply not booting due to dead drive.

The problem is... a hard lock? In a machine attached to known dirty power? Once a quarter? There are 1000 things that can do that. It's like trying to have a doctor diagnose why your stomach hurts...

So I think failing SSDs do have symptoms prior to fault, but they're so very mild that they easily go overlooked. But yeah... SSDs have a lower fault rate, but when they do fault... they fault BIG!

I use platters for backups, not because I don't trust or want SSD there... but because I can get much greater storage volume for less money. Doing an image chain on SSD is EXPENSIVE.
 
I may have one that is failing. AData 480GB, suddenly Windows 8 Embedded won't open certain apps and files show up as can't be read.

I replaced the SSD with a 64GB DOM for the moment, and after a reload from Dell's Recovery USB, the client is back up and working, I copied files over I needed (nothing that I couldn't live without but still glad to get).

Gonna test the drive, but not holding my breath.
 
glennd said:
I had my first SSD failure last week. A Kingston (not mine). They're right, the failure is sudden and total.
Click to expand...
Same was a Kingston - total sudden failure. I think what happens with them is the NAND Flash overheats over time, which end-users wouldnt really notice. Then to the point of it canna take any more captain. The Kingston model's are on the low end scale. So it goes to the old adage "You get what you pay for".
 
I've never had a Samsung, or WD Blue SSD fail.

I've got one in a laptop that's an old 120gb Samsung 840 EVO with over 2 PB written to it... it should be toast! Wear leveling is at 0... but the thing keeps working!

It's not doing anything even remotely important anymore... I just keep writing junk to it to see when it'll die!
 
frase said:
Same was a Kingston - total sudden failure. I think what happens with them is the NAND Flash overheats over time, which end-users wouldnt really notice. Then to the point of it canna take any more captain. The Kingston model's are on the low end scale. So it goes to the old adage "You get what you pay for".
Click to expand...
The NAND Flash chips do NOT overheat. If anything, the controller (CPU), that does all the work, may overheat.

NAND flash chips simply degrade over time due to either write cycling or cell leakage, both causing bad sectors.

In terms of write cycling, once a drive's overprovisioning (reserved blocks) runs out mitigating for bad sectors, then it goes into read-only-mode (if supported), SSD becomes unresponsive, firmware (e.g. translator) becomes corrupt and so on.

Of course, if there are electronic faults triggering component damage (e.g. diodes, resistors, capacitors, etc), then yes components may get hot.
 
Sky-Knight said:
I've never had a Samsung, or WD Blue SSD fail.

I've got one in a laptop that's an old 120gb Samsung 840 EVO with over 2 PB written to it... it should be toast! Wear leveling is at 0... but the thing keeps working!

It's not doing anything even remotely important anymore... I just keep writing junk to it to see when it'll die!
Click to expand...
That model is likely an early version of higher quality TLC NAND chips. These were the more durable and stable in terms of NAND wear leveling.

With the ever demand for capacity increase, NAND technologies have evolved into lower quality NAND technologies, from the early SLC (most durable) to MLC, TLC and now QLC, I believe. Going from left to right in that order, NAND write wear leveling has decreased considerably from one technology to another.
Here is a short article showing a good representation of that:

How do manufacturers battle to make it seem SSDs stay as durable as possible eventhough the NAND flash quality is worse?
1) Very complex algorithms for ECC correction (which consequently makes the data recovery process much more complex, hence costly; REMINDER: this also applies to USB flash drives, Micro SD and SD Cards, especially the generic and cheap ones from Amazon, Ebay, etc)
2) Larger overprovisioning for bad blocks reallocation (it makes sense in increasing the overprovisioning blocks, as the drives' capacities have increased)

The reason we see less failures in SSDs is two fold, especially in home users computers, mostly PCs, is that home users do NOT write a whole much to them. So, that prevents wear-n-tear.

Also, manufacturers have improved in the other early problematic areas, with regard to firmware bugs, electronic issues, data loss on power outages, etc.
There still are some major flaws, but they are less frequent.
 
Last edited:
labtech said:
The NAND Flash chips do NOT overheat. If anything, the controller (CPU), that does all the work, may overheat.

NAND flash chips simply degrade over time due to either write cycling or cell leakage, both causing bad sectors.

In terms of write cycling, once a drive's overprovisioning (reserved blocks) runs out mitigating for bad sectors, then it goes into read-only-mode (if supported), SSD becomes unresponsive, firmware (e.g. translator) becomes corrupt and so on.

Of course, if there are electronic faults triggering component damage (e.g. diodes, resistors, capacitors, etc), then yes components may get hot.
Click to expand...

@labtech sorry I mean the CPU. I stand corrected - or sit for that matter. I have bookmarked that page also thanks.
 
You must log in or register to reply here.

Similar threads

Appletax
AVG hosed the OS - BSODs, bootrec/fixboot "Access is Denied"
2
Replies
25
Views
967
britechguy
britechguy
frase
System will not power off
Replies
13
Views
611
frase
frase
Appletax
[SOLVED] Computer occasionally deletes audio drivers on Dell Vostro 7500
Replies
3
Views
473
Appletax
Appletax
Appletax
[SOLVED] Intel Rapid Restore Driver Causes BSOD - DRIVER_POWER_STATE_FAILURE
Replies
3
Views
421
Appletax
Appletax
Appletax
[TIP] Manually Resize Recovery Partition in Win 10 so Updates Do Not Fail
Replies
3
Views
275
ThatPlace928
ThatPlace928
Back
Top