Well that was fun
at about 7pm last night my pc blue screened, then came back on.
each time I rebooted same thing. Blue screen, then would boot again
So I dropped in a cloned drive from about 6 months ago and it was fine...
so... cloned that one to my c drive... and rebooted
blue screen... and that was it !!! the C drive would do NOTHING!
so back in with the old clone
I looked up the Kmode thing and it sems that its either "old driver" related r a ram problem.
looked through device manager and everything was ok.
so ran a load of ram tests...
everything was ok.
Then after a bunch of updates.. when I got to the 2004 build of windows 10 all of a sudden...
my pc was as I had it at 6pm... which rather freaked me out. Made no sense at all.
it was when I was about to clone this setup that I realised the PC had booted from a different drive… not what I thought was my C drive… (another clone drive that I keep in the PC for if things go squirley)
so then I started booting off that( (Western Digital), and the main drive (Samsung M2 drive) to see what happened
The Western Digital drive was booting fine... the Samsung M2 drive caused blue screen every time....
so what was happening in the first place was that the Samsung drive would crash and windows then booted from the western digital... only i hadn’t figure that out.....
(I got 2 hours sleep last night trying to get this sorted so I could actually work)
Now... hard drives as we all know don’t have drivers right?
Well no... turns out the M2 ones use a driver... and from 7pm last night the windows one suddenly was not up to it apparently.
installed Samsung drivers and bingo.
How the hell are you supposed to know this stuff?!
Anyhoo… its all good again… and as it wall was before the disaster !!
So just a heads up really….
If you are running M2 drives… try the manufacturers drivers…
Bookmarks