New
#31
Thanks mate. While the only thing unusual is the mouse cursor disappearing during the freeze, the details you've provided me show we're definitely dealing with the Trio of Trouble. Again, looks like we'll have to start with the PSU and work towards the CPU and finally the Motherboard.
As for the "software/driver update", it did work, but it only fixed that issue involving the crashes, which are seemingly unrelated to what you're experiencing here. Held-up IRPs like what was mentioned in the BSODs do not cause instalocks, but rather will either cause progressively increasing delays in response to where it's completely unresponsive, or it will cause a BSOD (like what you've experienced) after it has waited out its maximum lifetime of around 12 minutes. Updating your network drivers sounds like it's resolved your BSOD issue, but not the freezing, so I'm thinking we're dealing with two separate incidents.
If I recall correctly, you tried dealing with updating the BIOS and all your motherboard drivers, but to no avail. The only exception I can see is making sure to remove all motherboard software that came included with your motherboard. AI Charger (or some other variant USB gimmicks), monitoring software, etc., all of it has got to go. They are the only software I can see that would cause this issue right now. However, I doubt it's the case because we've come across no other data (crashdumps for example) that points to them being the case. Still, it is your last software option before proceeding with the hardware swapping.
Concerning your attached report, it's nothing entirely unusual. The Hardware/device check failure is referring to the aforementioned NVIDIA Audio in the report, in which the device was disabled either manually or for other reasons, which I'll leave to your discretion as to why it's disabled (perhaps driver issues?). I don't see it being involved here. Also, the conflicts/sharing region of the MSINFO is ok. Various and sundry items in your PC will share resources, so it's not unusual to see them listed there.
It's always difficult for me to lead people into spending money towards finding a solution since it obviously isn't the most appropriate means of solving an issue, but we've done all we can with what we have and this is all we can do given that we're trying to diagnose this problem remotely. If I had personal access to your PC, I would have other more effective tools (mobo workbench, live kernel debugger, multimeter, etc.) to ascertain a cause, but alas that's simply not the case, so we have to make do with what we got. Of course, you can always take it to a local repair shop, but it's up to you whether you'd be wanting to risk it by fronting money towards a repair shop's diagnosis rather than spending it yourself on what may end up being 3 separate PC parts (CPU, Mobo, PSU). It's your choice.
I hope the best for you, and that this problem would be resolved expediently.