We are getting sidetracked here.
The problem originally happened while running DeusEX:Mankind Divided and according to the dumps did not involve my Brother printers or drivers.
I would prefer to concentrate on that aspect.
I have played hours and hours of DeusEX on the HDD Windows 10 without a crash. The SSD is a clone of that disk.
I originally suspected file corruption on the SSD.
Maybe I should re-clone the HDD to the SSD and try the game again.
The only .dmp file that has given me any meaningful information to work with is the one that objectively identifies an issue with the Brother printer/s. Hence thats the logical trail for me to follow. That's often the case with BSOD'S, they can throw up red herrings, can be long and convoluted, and require patience, persistence and a systematic approach to solve - I think you have mistaken that for 'becoming sidetracked'. All I can do is try to unravel what I see in the .dmp files.
By all means, try another disk if you think that may help, but I think at this point I'll bow out of this thread, and wish you good luck in finding the solution. Hopefully you will get your system back to where it is working as normal.
Thank you for your assistance. It is greatly appreciated.
I have an update to this thread.
I might have a possible answer to the BSOD. I attempted to clone my Windows 10 drive to the Samsung SSD (850 EVO) to see if I could "force" the error. After about an hour when the cloning was just about done (less than a minute) I started receiving "write errors".
I was using Acronis True Image 2017. I only captured 3 errors but I continued to click "ignore" and got many many errors.
I am now running an extended test on the SSD.
I'm thinking that is might be possible that the original BSOD was caused by a corrupt file from a faulty SSD.
I'll update here when I have more data.
This is getting stranger and stranger.
I took the SSD out of my primary PC and put it in my secondary Windows7 PC and cloned the OS.
I then booted from the SSD without any problems.
then I put the SSD back into my primary PC and booted it using my Windows 7 HDD and did a surface test on the SSD using MiniTool. No errors.
Then I cloned my Windows 10 HDD using the same MiniTool utility. No errors during the clone.
Added an entry in my EasyBCD for the new SSD and attempted to boot from it.
As soon as the login screen appeared it started flashing quickly. I let it do that for about 30 seconds and had to press the reset button to stop it.
Apparently during those few seconds it marked all my internal HDDs as "dirty". Why?
This is getting stranger and stranger. I'll start a new thread.
Last edited by dlwmacgregor; 05 Feb 2017 at 14:58.
Quote