HardHang every night, no BSOD, not fixed in startup, common 0xC000000D

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.

Vir Gnarus said:

… 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. Still, it is your last software option before proceeding with the hardware swapping.

Perfect – Please let me know me which software to uninstall – I’m all for a clean computer. I’m imagining I’ll go to Control Panel\ Programs and Features, and uninstall a bunch of them & reboot. If there is anything else, please specify.

Vir Gnarus said:

… 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.

Painful, but Fine. As soon as I uninstall the Mobo gimmicks (above), I’m buying another PSU online, installing it, and will let you know what happens ASAP.

Vir Gnarus said:

Concerning your attached report… …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 had 2 sets of "Audio" in the computer, but only one Audio device attached… I just disabled one of them manually. Disabled one, tested and it worked, didn't even try the other one.

Wait -- What about these lines:
Motherboard Device Configured Fail Count -16 Tests-Failed: 1 - Motherboard devices.
PlugAndPlay Device Configured Fail Count -179 Tests-Failed: 1 - PlugAndPlay devices.

These are the 2 lines in the report that failed …(Basic System Check, Hardware device and driver hecks, Failed). If both these are the same “manually disabled” Audio, then nevermind - don’t even bother writing. Now, if there is something failing in the Mobo or plugn'play… let me know.

Vir Gnarus said:

It's always difficult for me to lead people into spending money… but we've done all we can ... 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… Of course, you can always take it to a local repair shop…

I have Teamviewer, so I could give you access to the computer… not sure if the tools you’re talking about would work.

I don’t have a trusted repairshop to take it to – I’d take it to you if you were in Massachusetts, and front the money happily to have it fix for good.

I'm not aware of what software you have installed, but you should able to get a good idea what to look for by going on your mobo vendor's website and check their list of drivers and utilities for your mobo, as that'll mention the software you may have installed. Driver Sweeper is also a good option for cleaning that stuff off, though they've changed things up (including name) so I'm not sure how it is now, but it's definitely worth a look. It usually will be able to clean off anything left over from ordinary uninstalls.

As for the device failed, yes it's referring to the same device (it being a motherboard device and also plug n play).

The teamviewer thing is probably not an option, as it most likely goes against some form of support policy on this forum, and I wouldn't advise it anyways. Plus, it wouldn't do us any good, as everything I need requires direct access to the PC in a physical manner (including the live kernel debugger).

Oh, and sorry mate, down in NC here. :|

Either the PSU you purchased has its own problems (hopefully not!) or you may have actually been dealing with at least two bad pieces of hardware before. Again, very difficult to tell without proper tools and access to a nearby professional.

If you have any other system floating around, try placing the new drive into that system and test to see if things are stable. If they are, it's time to replace either the mobo or CPU.

As long as you can confirm that they are stable and reliable parts, you should be able to setup another PC with em and test. You are not benchmarking, but merely stress testing for purposes of trying to provoke the suspect part into having some bad behavior. If you're experiencing systems similar or identical in the test PC to what is being witnessed on your main PC, then it's evident that part is bad.

Hmm, the hiccups appear to be small interrupt/DPC hangs in which something in high IRQL (that is, something of very high hardware priority I/O) is taking too long and is holding up everything else. Usually this is a drive problem, but what we've been been dealing with in the past I can't attribute to being drive-related. There is a way to monitor interrupt/DPC latency issues like this, which are explained here. When you get to the point where you actually start xperf up in the command line, you want to change the "latency" option to "Latency+FILE_IO+FILE_IO_INIT+NETWORKTRACE". Let it log your symptoms for a duration of the hiccup symptoms and then stop it as instructed in the article and then provide us the ETL log file through some means (like Mirrorcreator.com).