Hey guys! My name is Max and I'm new here! I usually don't like to pester people with questions on forums, but rather read and fix problems myself. Well, today, after 8 hours I've finally reached my limit!
I have two TC Electronic interfaces: Konnekt 6 and Impact Twin. My OS is Win7 and I'm using a firewire interface with a Texas Instruments chipset(The one that TC explicitly states it's interfaces will tolerate). Point being I'm able to test my system using two different interfaces, alas, with the same negative results. I think I'll just cut the long story short and say that I found this thread on your forum:
https://www.sysnative.com/forums/wi...her-dpc-latency-problem-audio-glitches-3.html
I checked my system(while running a video on youtube) with DPC Latency Checker, LatencyMon and the latter told me that the supposed culprit is the wdf01000.sys, but from what I've read it's just a lowly(lol) low level kernel driver and is not the cause for the ridiculous latency spikes I'm getting.
So as per your instructions(in the link above) I've downloaded and ran the xperf diagnostics tool.
My first question is how do I find the info about what exact drivers have been "talking" to Wdf01000.sys? It's a massive file and I just can't find the info about the driver interactions the way Tomas did in that previous post.
And my second question is-did I run the diagnostics too right? I did everything like Tomas said(again, in the link above), however, in the command prompt the thing ran for about a second or two. Then I punched in the command to generate the report file.
So, the bottom line is: I have a bunch of these report files...maybe you guys can give me some pointers on how to read them instead of uploading them?
But if you'd like to take a look at them I have another question: how do I "compress" these files before uploading? I've read in another thread of yours that I should do that.
PS: I also ran xperf as specified here:
https://www.sysnative.com/forums/wi...ues-with-wpa-windows-windows-vista-7-8-a.html , however it also didn't run for too long and I haven't been able to decipher the file.
Help me, Tomas-you're my only hope!:grin1:
