New
#21
Ignore my last guys, I fixed it.
If anyone else has these symptoms, check your Hard Drive Firmware version.
Thanks Crucial, thats 24 hours of my life i won't get back trying to find your stuff up.
Ignore my last guys, I fixed it.
If anyone else has these symptoms, check your Hard Drive Firmware version.
Thanks Crucial, thats 24 hours of my life i won't get back trying to find your stuff up.
We are aware of that problem, actually: https://www.sevenforums.com/crashes-d...ml#post1793840
Additionally: Why did my SSD "disappear" from my system? - Crucial Community
I had exactly the same problem and couldnt find it at all but i fixed it in the end. Wanted to share my path...
How i found it is was through opening the dump file on NirSoft, if you scroll to the right on the top section you can check which driver is repsonsible for the bsod in my case it was the ntoskrnl.exe causing the bsod. After a quick wikipedia visit i found out that that file is used for memory management etc coming from this i needed to check my harddrives and memory and so i did and found nothing....
After a short burst of frustration i was on an empty path and was so frustrated, took a small break and decided to call my whizzkid friend and he said memorycheck are often not giving faults when it does create a BSOD. So what i did was remove 1 ram slot and no problem just to be sure i used the other one and kaboom bsod in seconds after launching windows.
my lesson learned: memory tests are not 100% reliable, if i knew that before it would have safed me like a half a day of work and lots a frustration.