Win 10 - Continuing Saga of Win 10 Unreliability

Win 10 - Continuing Saga of Win 10 Unreliability (Totally Bad OS Release!!!)

Ya know it's gonna be a another Win 10 Bad Day when, Ya return to a black screen and blinking cursor on your new Win 10 Pro machine AGAIN!!! And, of Course, it won't even boot either...
This is my fourth attempt to use Win 10 as a mission critical Development/ProdSupport workstation, and they all end up as a Non Bootable, Non Recoverable, DEAD Box!!!

This happens a Lot to me. Sometimes repair tells me "Disk is locked", or other errors, but I have learned when Win 10 dies - remove the sys disk, put it in another working machine, and run a chkdsk on it.
Here's the result of my last Win 10 Failure.... Click these images to Enlarge for Readability.


Now, after I ran a Chkdsk /F and the Intel SSD diagnostics on the sys disk, and replaced it in the new Win box - all fired up OK and the box will probably run about a week before failing again.
There isn't anything wrong with the Hardware here... Its Win 10!

This is a Brand New box, a New Clean Install, and it didnt even last a week!
For those who want the hardware, All Brand New: Asus H170M-Plus, I5-6600, 16G HyperX DDR4(2400), 250G Intel SSD & WD 1T HDD, all else integrated, default settings and fired up perfectly and cleanly installed the first time.
It is a full workstation install, Win 10 pro, IIS, Office 2016 pro+, SqlServer 2016Dev, VS2015ProU3 - All Pure Vanilla outa the Box Legal MS Software! Yep, takes about 2 days to get all installed and functioning cause its window's updating itself almost constantly on every Feature and Product installed. I can get a few Solution's to build and run, Just not for very long (plus Debug and Publish just doesnt have authority to do the job even when run as admin)

I'm sayin Win 10 is a Bum, Busted, Bad OS release...
Here Proof! Click Start Menu->, Click Settings(gear) icon -> click Update & Security,
At Update History --- You clearly See "No Updates have been installed yet."
Then Click the Blue "Uninstall updates" - and Behold...
You Now see the " Currently installed updates" - 100 updates Installed !!!! Oh Yea 100 updates...

Now Who Ya Gonna Believe? (or rather, which screen ya gonna believe?)
Win 10's Terminally ILL.

Y'all know the definition of Insanity: One who keeps doin that same thing expecting a different result...
It's clear, The Emperor has no clothes, Bill's Gone, Win 10's Busted!
(3[Viasta, 8 & 10] outa the last 4 have been BAD!)

But Please, Prove Me wrong here...
Anybody out there with a full fledged mission critical Business Win 10 machine Please step up and show me what I'm doin wrong...

Yes, Anything is possible, however unlikely for this SSD... Cause:
1. Passes Every Intel Toolbox test (Quick, Complete & Smart Diagnostics)
2. SiSoft Sandra Benchmark & Stress tests
3. It's been Proven Reliable - (from another machine, Securely erased, and Repartitioned (both Reserved & System) and formatted by Win 10 itself on installation!
Definitely Highly Unlikely this Intel SSD has Ever made a Mistake!

Ever Use SiSoft Sandra (lite), Here's a Snip... It's a great Freebe

As you can see above, my SSD benchmark (at 503.x) is just a hare above the Std bench for like devices( 500.x)
I use Sandra on all my boxes, not to get the best performance, but just to insure all is al least runnin as it should and well matched for the system as a whole. Good ole Sandra can identify Bad components Right Away...
This box checks out (Benches) almost perfectly average for is components, Not Super Fast, but definitely Swift & Smooth... Reliablity and No Problems is the Goal!

Plus, this is the 4th time I've taken a run at Win 10 - and its trashed its system drive 4 outa 4 times! (3 other drives!)
Now, What would you suspect?
Win 10 just aint passin Product Acceptance tests for my Mission critical $$$$'s and income.

Like any new vehicle - if the driver does not have confidence in the machine, they will not feel comfortable driving it. And the machine is a complex system of engineered and serviced parts, as well as the human user, any of which is not performing adequately can make the whole machine less than 100% safe or reliable.
Trying to pull apart Windows that states it has not received any Windows updates yet, by showing all the updates that the (optional, user chosen) programs and features installed have received already is like trying to compare pomegranates to cumquats - they are different entities. It's only proof of a poor comparison.
The definition of insanity here is trying to work in the same environment as something you cannot get along with.

If you cannot change yourself, by your own reckoning, stick to the Windows 7 that you think is not "bad".

You still have 3 years and 4 days until Windows 7 is completely abandoned by MS.

Perhaps Windows 10 won't look so "bad" then.

But you'll have a hell of a lot of Windows 7 updates on top of your SP1 installation to complain about before you can even get to complaining about the updates for your development software.

A lot of folk here will tell you that if you have your system running in a VM, you can take regular snapshots of the VM and return to a snapshot at any time after your development work completely fubars the system. It's a different way of working, and may give you the peace of mind to stop worrying if your system's about to crash and burn, enabling you to work through the failures, rather than consider them barriers to progress, and blaming the OS as being your enemy, rather than a facilitator.

It still amazes me that people have issues on one box and then take the giant leap to say Windows 10 is awful....despite that fact that hundreds of millions of computers worldwide are running it perfectly fine.

Wouldn't common sense kick in at some point?

Anywho, it sounds like you have a hardware issue (potentially memory, if you haven't checked) or are continuing to load a bad driver that's causing issues. It could even be as simple as a bad SATA cable.

Suggest having a look at event viewer errors and warnings may give a clue as to what is actually going wrong.

Just a thought. I've built two systems with a Gigabyte motherboard using Sandisk ExtremePro SSDs. The first was a new motherboard with a 480 GB drive. No issues. Second was an older motherboard with a 240 GB drive. System would power down everytime it booted with the SSD connected. The SSD works fine in other systems, current firmware, passed all Sandisk diagnostics No matter what I tried, just would not work properly. Finally brought up the system on a WD Velociraptor drive with no issues. Will consider a SSD later.
Nothing from Sandisk support.

It may just be that your SSD and motherboard just don't like each other. May want to try a different brand SSD.

Just some thoughts.