Win 10 AU - Very High ISR counts for DirectX Kernel Trace Debug

NoChance

NoChance

Well-known member
Joined
Sep 2, 2016
Posts
59
https://www.sysnative.com/forums/wi...0-au-very-high-isr-counts-directx-kernel.html

I posted the above in the windows 10 forum, though a friend suggested that if I was looking for someone to look at a trace, I should post it here.


Who would I send the trace to?

Some Info:
1511 was the original OS install, by me. Upgraded to 1607 (Pro)
I use vpn occasionally, though it doesn't run by default. (OpenVPN)
PS is 1150W Seasonic, platinum.
No daemon tools like stuff.
Kaspersky is the AV, most of its crap is turned off except the actual AV (have tried with it uninstalled)
firewall is Comodo.
Brand new build.

System Specs from Speccy:

Read More:
 
> firewall is Comodo.

do you think that is a good idea?
get rid of^^



 
I've done all my tests without it installed on fresh installs. I've used Comodo for years and know how to get rid of the extra crap, and make it do exactly what I want. If you get rid of the invasive stuff, its pretty simple. That being said, I get your point. Both Kaspersky and Comodo are like dangerous pets you keep in the house.
 
Ok,
however with those Spwcs one can see some interesting configuration and drivers which might not work well with AU on an Skylake-System.

Given that, this Specs are pretty useless to find out the culprit, a dump might reveal more or eventual an xperf trace.

at this point, a reliable statement can't be given, so i'm out and i 'm sure none will dig into this without much more further information.

regards
Michael
 
When I saw your reply earlier, I thought this was the other thread. Sorry. I have the speccy info there. Any other items I can provide. I sent a pm to the dropbox for the trace.

The problem exists on clean installs of both 1511 and 1607 versions of windows. Clean to me = fresh from install, no windows update, all default microsoft drivers used where applicable.

I tried with most of my onboard peripherals disabled as well (Asmedia Sata, Asmedia USB, bluetooth, wifi, lan ports, Alpine Ridge, Realtek Sound) and with the only devices installed being my mouse and keyboard (no sound).

There are two processes that dominate ISR's.

WDF01000.sys - Looks to be coming from dwm.exe during any USB activity (no usb activity, no ISR's)
dxgkrnl.sys - Direct X kernal constant ISR's regardless of what I'm doing

Have tried all Nvidia drivers, using DDU to wipe between each.

nvlddmkm.sys has a ton of DPC's as well, which I'm sure is tied to the directX kernel issue.


Thanks for any help!
 
Ok,

thx i will look into it later.

some things i discovered,
NVMe Samsung SSD 950
this will usually need a special driver, MS'es iastor will not handle this properly, nor is the chipset handled correctly by MS clean install.
Intels Rapid storage is a good idea too, even in Win10 & AU.

depending on USB3, Intels chipset handles this better.

This Dataram, Inc. RAMDiskVE
might work well on a system with all those drivers from Intel or your Vendor.

not easy to grab through a bunch of text, so this a first shot and worth a try.

regards
Michael
 
Moin,

had a look in your xtrace and as suggested, drivers, drivers...

your USBlyzer is eating the most time / performance causing hickup.
Next is the filterdriver (Win) which is no surprise and the next is NTFS.Sys running wild and hig.

so it's your work to install the missing drivers and uninstall that old? USBlyzer to get a most stable system.

regards
michael
 
I thought I'd update this as I see there are some incorrect things still floating around in other forums.

The usblyzer is a red herring. It was added just before this dump to see if I could log USB commands in the hope of identifying a USB driver bug. It has been removed.

To date, the issue still occurs up to and through Nvidia drivers 375.57.

It occurs across 3 motherboards, (Asus Z170 Premium, Asus Maximus VIII Formula, MSI Mpower Platinum), on all bios revisions of each board, on Windows 7 and Windows 10, on all Nvidia drivers since card release, on 2 separate nvidia 1080 gtx founders edition cards.

So so the issue still exists. When I get it solved, I'll be sure to post here.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top