Another DPC Latency problem / audio glitches

[ra78]

Dear сolleagues,
I would be grateful for your professional look at my long lasting problem.

1/ Application: Audio Production, though as checked today with all the periferals off,
and all BIOS all throttling options off, it has nothing to do neither with my DAW nor with WiFi adapters nor with FW card (the card chip complies with my interface recomendations +
it was doublechecked with USB card - glitches remain).

With all the periferals on - Ataport.sys and wdf01000.sys report highest latencies time.
With all the periferals off - Ataport.sys and ntoskrnl.exte report highest latencies.

Printscreens attached are from OFF state.


2/ OS WIN7x64, Originally Installed, no changes in OS type
Acquired something like two years ago, Refurbished from Dell with one year warranty, via local distributor.
Reinstalled OS beginning October trying to solve this clicking issue

3/ Computer Brand Name: Dell System DB2
Operating System: Microsoft Windows 7 Professional (x64) Build 7601
Service Pack: Service Pack 1
Processor: Intel Core i7-2620M (2700.0 MHz)
Motherboard: DELL 08YFGW (Intel QM67 (Cougar Point)

)
Memory: 8 GBytes (Dual-Channel)
Hard Drive: WDC WD2500BEKT-75PVMT0 (238,475 MBytes (250 GB))
Optical Drive: TEAC DVD-ROM DV18SA (CD-ROM drive)
Display Adapter: AMD FirePro M5950 [DELL]
Audio Adapter: Intel Cougar Point PCH - High Definition Audio Controller

ATI/AMD Turks/Whistler/Onega/Lombok/Thames - High Definition Audio Controller
Network Adapter: Intel 82579LM (Lewisville) Gigabit Ethernet Controller
Intel Centrino Ultimate-N 6300 AGN 3x3 HMC WiFi Adapter
Monitor: Samsung 184HT





Hopefully I've fulfilled all the requirements, if not, kindly let me know what is missing.


Please help.

Greetings from Kiev,
Andrey

 

[ra78]

... and not sure if it's relevant - yesterday I've tried to launch up msconfig in diagnostic mode - nothing changes. clicks are still there.

 

[ra78]

Dear Sysnative, is there anybody how got a chance to have a look at my problem?
Need help badly.

Thanks,
ra

 

[TomasD]

Having XPERF long might be a good starting point.

Could you please run Windows SDK setup and select to install "Windows Performance Toolkit"? Once it's installed run the following command from elevated (Run As Administrator) command prompt:

xperf -on PROC_THREAD+LOADER+PROFILE+INTERRUPT+DPC -stackwalk Profile -BufferSize 1024 -MinBuffers 256 -MaxBuffers 256 -MaxFile 256 -FileMode Circular

Now, play some audio until you experience the glitches you mentioned. Once you do, run the following command to stop the logging:

xperf -stop -d C:\CPU.etl

Attach the C:\CPU.etl log file here.

 

[ra78]

Hi, Thomas.
Thanks A LOT for coming back. I've installed everything, and then trying to run the command- got a notification that something wrong with the registry (have a look at the prinscreen attached). I've introduced the change, rebooted and run the diagnostics. Link to ETL file is attached - both uncompressed and compressed version (73/11Mb correspondigly) where rejected - no info on file size limitations was found. So if you do not mind here's the link to sendspace - Download CPU.zip from Sendspace.com



Thanks and greetings from Kiev's Euromaidan people,
Andrey

 

[TomasD]

Hi,

thanks for your time generating the log. This is what I see:




I suspect the outdated driver (released back in 2007 for Windows XP) for your KORG ZERO4 mixer to be causing the issues. Could you please try downloading and installing these drivers - View attachment 6017

 

[ra78]

Hi, Tomas. Thanks a lot for prompt response. My system says that that's the same driver version that is already installed.
Indeed I got lots of issues with this mixer, and the driver is very old.

But it is confirmed by tests LatencyMon/DPC checker tests, that problem lays somewhere else:

With all the periferals on - Ataport.sys and wdf01000.sys report highest latencies time.
With all the periferals off - Ataport.sys and ntoskrnl.exte report highest latencies.

With all periferals off, including Korg - I have very high latency spikes and audio glitches even with onboard IDT card.


Or am I getting these reports wrong?



Thanks,
Andrey

 

[TomasD]

Well, my concern is the FireWire driver for that mixer - Korg_1394_x64.sys. The report you attached in your first post says you have the following driver version installed:

KORG_1394    KORG_1394              KORG_1394              Kernel        Manual     Running    OK         TRUE        FALSE        0          135ÿ168    0      [B]09.02.2007 17:21:29[/B]    C:\Windows\system32\Drivers\KORG_1394_x64.sys

While the driver I attached earlier is more recent:




In addition, could you please try generating a new XPERF log, while having the peripherals off and still experiencing high DPC?

 

[ra78]

Sure. At the same time, I've doublechecked the dates of the files inside of the folders
(yours vs one from Korg.com that I have installed) - and it seems that yours' is more up-to-date - in korg folder all the files are dd 2008,
while in yours lots of them dated 2010 + some of the file sizes are bigger.

I'm installing the driver and checking +
doing on more XPERF log and sending it over within an hour.

THANKS.

Andrey

 

[ra78]

Its incredible - but you are ABSOLUTELY right,
drivers are different even having the same version numbers, that misguided me.
As of course I was checking for the updates at korg.com

It's just incredible. Keep on diggint it with DPC/Latency monitor.

So far it seems that glitches are gone, but with browser opened, and ethernet on,
DPC still yields red spikes.

Need to test it with all of, will post shortly.

Thanks.

A.

 

[ra78]

Tomas, please have a look at the report attached.

With all the periferals off, DPC still detects some reds, some of those being up to 16000.


Notwithstanding that - audio playback seems to get better, but I keep on testing it.


Do appreciate your help, indeed.


Andrey

 

[TomasD]

If the audio issues are gone, I wouldn't worry any longer. As you can see in the screenshot below, apart from a single spike, I would say DPCs are quite normal now:

 

[ra78]

Thanks for your kind assistance, Tomas. Yes, audio glitches were the most painful issue.

But I will keep on checking.

Have a positive evening)

 

[TomasD]

Thanks for your kind assistance, Tomas. Yes, audio glitches were the most painful issue.

But I will keep on checking.

Have a positive evening)

Perfect. Glad I could help and I hope the issues won't reoccur :wave:

 

[ra78]

THANKS A LOT, TOMAS! :)
GREETINGS FROM KIEV !

 

[mgrzeg]

Tomas, what is funny, instead of the KORG_1394_x64.sys on the stack I see the bco_1394_x64.sys, as this is the original file name for the KORG module (the DbgId/RSDS events point to the w:\bridgeco\audio1394\bin\fre\amd64\bco_1394_x64.pdb). How did you get the KORG names on the stack? :)

m.g.

 

[ra78]

Gentlemen, and just a question - after introduction a small change into the register (needed for running XPERF test, namely switching DisablePagingExecutive from 0 to 1) and installing the new version of the driver - I got three cases within 2 hours with Zero's FW supply interrupted resulting in losing connection with OS (I know the case as it sounds the same when the mixer starts).

May it be inter-related somehow?

As no other changes to the system has been made, and during my glitches-era I had nothing like that.

Thanks.

 

[TomasD]

It's not likely that could be related to changing DisablePagingExecutive registry key, but if you want, feel free to revert it back and reboot the computer. What I'm afraid is that the new drivers fixed audio glitches, but introduced other bugs. Zero 4 is not supported by KORG since XP, so issues are likely.

 

[ra78]

Good morning, Tomas.

I'm afraid you are right, as this morning glitching happened again. Not that often but I've heard them several times.
And still 6-7 drivers in the system execute much longer than they should and it feels like they also may add -
as HDAudio is amongst those - and I've heard that on-board audio should be disabled when using outboard audio - though still not sure if its' right or not.

If you got a minute, please have a look at prinstcreen attached.


Thanks,
Andrey

 

[TomasD]

Tomas, what is funny, instead of the KORG_1394_x64.sys on the stack I see the bco_1394_x64.sys, as this is the original file name for the KORG module (the DbgId/RSDS events point to the w:\bridgeco\audio1394\bin\fre\amd64\bco_1394_x64.pdb). How did you get the KORG names on the stack? :)

m.g.

That's strange. I cannot see bco_1394_x64.sys anywhere on the stack, neither in XPERF logs or LatencyMon screenshots Andrey attached.