Here's a real doozy !
Have been in IT for over 40 years fixing Windows PCs (even remember the 1st Tom's Hardware giving me a helping hand).
I am running 2 PCs each with 4 hard drives containing Win7 64bit, Win10 64Bit, Win10 Insider Preview and Win7 x86 (dual boot on steroids).
All was okay until last week when, following an update to Win10 build 14372, ALL drive logins (done individually) reported BSOD 34 - Cache Manager error. I tried replacing Ram and every other option to no avail. Even trying to startup using WIN10 or Win7 (legal) DVD disks still caused the error.
So, naturally I could not even boot into any safe or command mode to check the drives.
But, it was only when I removed the Win7 x86 drive that suddenly, all other Logins worked !
The bios all reported the drive- no problem.. So, it only occurs on Windows startup (7 or 10)
I have tried all windows options to see what is wrong with the drive but, once it is in the PC (not even as startup drive) that's it !
I even resorted to Ubuntu and believe it or not, it found my Win7 x86 every time, just could not fix the Windows issue.
So, I am left with a 250G drive that I cannot access (thru windows). I have an old backup from 3 months ago so have not lost the data. I just do not want to throw away a perfectly good Hard Drive.
Any ideas ???
cheers - Malc
Thanks boogieman.
I do have 2 PCs but, whenever I booted from a Boot USB, win DVD, Aomei Boot winPE bootdisk or any Hard Drive and this HD was in the mix, BSOD 34 appeared straight after the " windows Starting" /fireworks screen.
In the end I managed use the Aomei Linux boot disk and restore from an old image.
All is now back in order and yet the problem remains unanswered. Possibly a Virus but, very unlikely. Ruled out HD failure as works fine and Linux could see it.
Methinks that dual booting with Win7/Win10 is not a good mix due to Win10 disk indexing/handling issues. From now on, Win7 and Win10 live in 2 completely separate PCs.
thanks again, Malc
Have been in IT for over 40 years fixing Windows PCs (even remember the 1st Tom's Hardware giving me a helping hand).
I am running 2 PCs each with 4 hard drives containing Win7 64bit, Win10 64Bit, Win10 Insider Preview and Win7 x86 (dual boot on steroids).
All was okay until last week when, following an update to Win10 build 14372, ALL drive logins (done individually) reported BSOD 34 - Cache Manager error. I tried replacing Ram and every other option to no avail. Even trying to startup using WIN10 or Win7 (legal) DVD disks still caused the error.
So, naturally I could not even boot into any safe or command mode to check the drives.
But, it was only when I removed the Win7 x86 drive that suddenly, all other Logins worked !
The bios all reported the drive- no problem.. So, it only occurs on Windows startup (7 or 10)
I have tried all windows options to see what is wrong with the drive but, once it is in the PC (not even as startup drive) that's it !
I even resorted to Ubuntu and believe it or not, it found my Win7 x86 every time, just could not fix the Windows issue.
So, I am left with a 250G drive that I cannot access (thru windows). I have an old backup from 3 months ago so have not lost the data. I just do not want to throw away a perfectly good Hard Drive.
Any ideas ???
cheers - Malc
Thanks boogieman.
I do have 2 PCs but, whenever I booted from a Boot USB, win DVD, Aomei Boot winPE bootdisk or any Hard Drive and this HD was in the mix, BSOD 34 appeared straight after the " windows Starting" /fireworks screen.
In the end I managed use the Aomei Linux boot disk and restore from an old image.
All is now back in order and yet the problem remains unanswered. Possibly a Virus but, very unlikely. Ruled out HD failure as works fine and Linux could see it.
Methinks that dual booting with Win7/Win10 is not a good mix due to Win10 disk indexing/handling issues. From now on, Win7 and Win10 live in 2 completely separate PCs.
thanks again, Malc
Facebook
Twitter
Instagram