Discussion in 'Computers' started by Ringel05, Nov 1, 2019.
Thanks but already been done.
If you say so......... Obviously you don't know how to configure it so it doesn't suck. Besides, try playing Windows based games on a Linux machine...... Ain't gonna work. This is my gamer.
I am one who likes DOS and run XP for my other uses.
When you ran your partition manager, did you do a sector check?
Yes. I even ran DISM restore health and sfc /scannow a few times. Said everything was fixed then it would start all over again.
I even tried to install my old Win 7 via the install disc, it would get to the language select and neither my mouse or keyboard would work, apparently the USB drivers weren't there.
If it turns out that the Media Creation thumb drive which I've used on about 4 different machines has corrupted then I can make a new one and try it, if the problem still persists then I'll contact MS support for a possible install disc. That is as long as the Linux I have on it doesn't crash telling me it's the mobo.
Everyone has their favorites.
I'm going to assume you have opened the device manager and all the drivers are working.
You've probably also done a google search, but I'll post a link to what I found on new windows builds.
Windows 10 Blue Screen of Death – You Can Quickly Fix It
Good luck. I'd be interested in hearing what you end up with as a final solution.
I've been thinking of building a gamer system but the only real experience I have with the m.2 drive is the upgrade to my wife's Dell system.
Done it at least fifteen times........ and yup, been to that site and many others a few times, followed all the instructions and nope, nothing stuck, problem continued. That's why I'm thinking something in the Win 10 core is corrupted and won't fix unless I use a new Media Creation Tool or a legal MS disc.
Rebooted back to the HDD (Win 10) yesterday to check out some things I had just thought about. Ended up updating more drivers plus a couple of other maintenance items, it's been running since yesterday without a BSOD. The HDD BSOD from a few days back could have been due to out of date or bad drivers that I missed the first time also it's is entirely possible the M.2 drive is indeed bad. Might clone the HDD to the M.2 and see what happens.
In my checking there was something I hadn't done, I have Speccy loaded and ran it to check sensors, it was telling me all 6 cores were running at 80 C......... No friggin way, the fans would be going nuts and I'd have a sunburn on the right side of my face.........
Figured Speccy wasn't reading it correctly, bad sensors or incorrect target readings, investigated online and sure enough that was the typical consensus. Loaded HWiNFO64, an obviously much better package and everything is reading correctly and well within normal parameters.
By the way, HWiNFO64 has a free version which I used and a paid Pro version if anyone is interested.
One of the things I noticed was when the HDD had the BSOD a few days back it was after playing some games on Steam, the drivers/etc that needed upgrading were all gaming related, C++ etc. I'll continue to run it in Win 10 and see what happens. With any luck I may have discovered what the problem was, more research is indicating M.2 drive controllers definitely can have some issues. Apparently the Intel controllers are fine but the Marvel controllers can be unstable, mine's probably hooked up to a Marvel controller.
Separate names with a comma.