He's already tried a (what I assume is fresh) install on a separate hard drive, so it's not that I don't think
sluggish performance and freezes are almost always 2 things, memory or disk drive.
I previously repaired a laptop that didn't used storahci.sys but still had sluggish performance, you could try going to the registry and disable msisupported anyway, if the key and dword value don't exist you need to create them (I had to in that laptop), after I did that the laptop worked as fast as it should. the worst that could happen is nothing at all.
Windows event logger most of the time is a convoluted mess of hoops to jump through providing less than useful reports. I've had an issue with Tabletop Simulator crashing when I close out of it. It tells me nothing. Just that the application hung, various IDs, and to check the action center, which is empty. Then an addition application error that just says it failed due to 0xc0000005 which is a memory violation. Great, that could mean almost literally anything. Reinstalling the program hasn't helped, but neither does this cause any serious issues.
Actually, check disk is something done by the MS-Dos on Windows systems or whatever Dos the system has if not on Windows. The different programs that do the check, even if they are from hardware manufacturers, simply are a front-end, not a new algorithm. They do the exact thing typing into command line does, only more user friendly, that's all.
But it cant be the HDD because i installed one that was freshly bought it was in its original package it came with.
Oh sry i accidently put my reply into the quote
Fair enough, disabling drivers, editing registry, and swapping hardware are all extremes. Which Is why in my reply I suggested none of them. I keep tools around on my pc for simple diagnostics for when things go wrong. I treat my PC like others treat cars: when something is face value and unobviously wrong, test hardware with diagnostics first; the last thing you want to happen is a random and permanent unexpected failure. After that's solved, go through checking software. Non-destructive official ways to do it like restore and system integrity checks come first and will usually solve any problem with the operating system. After that comes the narrowing down of finding out what is wrong. For most people, this is too much of a pain and too hard to do; their only option is to start over again.
You have any source for that information? I'm curious about this one.
No matter what you use to do the disk check, it's always actually done by the Dos and no matter what, no user program has enough priviledges over the Dos for security reasons. Windows and generally only the OS is allowed to interract with it, reason why we get things like CMD or PowerShell. Disk check done during startup is done after the BIOS loads and before Windows does, so no program can interfere with it more than just call for the commands to be executed. The algorithm is exactly the same for those commands. Letting everyone just mess with the command instructions and algorithms would only increase security risks and could cause parts to fail. Better use a code that's guaranteed to work rather than one that may fry parts by accident, right?
You CAN change the algorithm for disk checks and Dos commands though if you modify the Dos itself or are on OSs with increased functionality such as Ubuntu/Windows 2016/etc. (generally supercomputer/server OSs).
Was my first thought since I came here. PSU[emoji106]No matter what you use to do the disk check, it's always actually done by the Dos and no matter what, no user program has enough priviledges over the Dos for security reasons. Windows and generally only the OS is allowed to interract with it, reason why we get things like CMD or PowerShell. Disk check done during startup is done after the BIOS loads and before Windows does, so no program can interfere with it more than just call for the commands to be executed. The algorithm is exactly the same for those commands. Letting everyone just mess with the command instructions and algorithms would only increase security risks and could cause parts to fail. Better use a code that's guaranteed to work rather than one that may fry parts by accident, right?
On topic now, thinking about this, I get a feeling the issue is somewhere no one mentioned... It's VERY likely it's the PSU causing the issue, it may suddenly give less charge, not enough to shut down, but enough to cause everything to hang and once something hangs due to low power, even if it goes back to normal it will stay frozen. Did you try pulling out any network cables by the way when it froze last time like I suggested? When it freezes, just pull out the network cable or whatever you are using and if it unfreezes it means that the issue is there. Additionally, do the fans just go crazy and get all loud when it freezes? I got a hunch...
@
RedColoredStars:
@
SylverReZ:
@
SylverReZ:
@
RedColoredStars:
