Do make sure after these changes you still have audio problems, not just high DPC readings. I personally would not worry if I could not see or hear any performance problems.
Yeah, the sound artifacts are the first thing I notice, then I look over to the other monitor at the DPC monitor tool and it's pegged.
Are there not Intel SATA connectors on that 'board? The downloads offered for it suggest that there are.
I'd fully uninstall EasyTune (and any other motherboard/graphics 'utilities') to test (assuming they were installed this time); note that even if you don't have them running, it doesn't mean that the drivers are not loaded (similar applies to antivirus software/suites and firewalls, disabling them won't completely disable them, drivers are still loaded and frequently still 'blocking').
The intermittent nature of the trigger makes me wonder if some Scheduled Task or power-saving feature isn't behind this.
Yeah, when I did the reinstall I didn't install any of Gigabyte's tools (EasyTune, DES2, etc etc). I also haven't installed a virus scanner yet. Windows Firewall is on, but that's it.
As for the Intel SATA connectors, there are 6 of them, and thats what I had everything plugged into at first. My recent experiment of putting the SSD on the Marvell controller and the older Western Digital HD back on the Intel Sata2 has resulted in the following. The SCSIPORT.sys driver has dropped completely off the chart, and only ATAPORT.SYS now shows issues.
So yeah, I'm *thinking* this means one of a few things:
1) There's something up with that older HD.
2) There's something up with that controller (it's in a different SATA2 port, but still the same controller)
3) There's something else up and it only manifests when reading from the slower HD.
I'm going to try moving the older HD onto the GSATA2 controller (currently haven't used this controller at all) to see if I can isolate if it's #1 or #2 above. I'm leaning towards #1 unfortunately.
The issue popped up right at system boot this time, and what's interesting is that right around the same time, this showed up in the Kernel-EventTracing log: "Session "NT Kernel Logger" failed to start with the following error: 0xC0000035" Not sure if that's related or not. Going to see if it occurs again. There are no other errors like that from other times I've had the issue occur (like *right now* as I'm typing this)
I'm also considering putting both controllers in AHCI mode (currently in IDE I believe). Pretty sure I'm going to have to do the whole registry edit, multi reboot nonsense to get that set though. Meh.
Thanks for all your advice folks.