Win 10 AU - Very High ISR counts for DirectX Kernel
- Thread starter NoChance
- Start date
A popular suggestion is to set the Maximum Pre-Rendered Frames from 1 to 4
NoChance
Well-known member
- Sep 2, 2016
- 59
I'm assuming that I have a driver conflict, bad driver, or bad Windows setup.
I picked up a hard drive this afternoon. I'm going to do a clean install of the latest iso I can download and see, without any special driver install, if it's there at time 0. If it is, I'll try to install 1511 and see if it's there at time 0.
I picked up a hard drive this afternoon. I'm going to do a clean install of the latest iso I can download and see, without any special driver install, if it's there at time 0. If it is, I'll try to install 1511 and see if it's there at time 0.
Did you try these commands on fallout 4 console?
Code:
tMta ON
tMtrdfl ON
tMtr ppldWhen fallout 4 "falls" (
) in the graph, I noticed these two files:
C:\WINDOWS\system32\DRIVERS\CMUACWO.sys
C:\WINDOWS\system32\DRIVERS\portcls.sys
They appear in the speccy log under "USB Audio Class 1.0 and 2.0 Device Driver With MS Effect", Date 3-25-2015, Version 8.1.12.31.
I can't find that on cmedia website, but I found "usb audio class 2.0" devices:
Is there your model between them?
) in the graph, I noticed these two files:C:\WINDOWS\system32\DRIVERS\CMUACWO.sys
C:\WINDOWS\system32\DRIVERS\portcls.sys
They appear in the speccy log under "USB Audio Class 1.0 and 2.0 Device Driver With MS Effect", Date 3-25-2015, Version 8.1.12.31.
I can't find that on cmedia website, but I found "usb audio class 2.0" devices:
On their download webpage there are 2016 versions (by the way, windows 10 isn't listed...).
Is there your model between them?
Another file that comes up is "nvwgf2umx.dll".
You can try to rename it (restart windows) and see what happens.
You can try to rename it (restart windows) and see what happens.
NoChance
Well-known member
- Sep 2, 2016
- 59
Cm6631a is the cmedia chipset.
The problem exists on a fresh install of 1607 (without any sound existing). I had a heck of a time figuring out to disable secure boot to install win 10 on a gpt drive.
Anyway, I'm going to install 1511 in a bit and see if that does any better.
I believe the nv* driver is an nvidia driver.
The problem exists on a fresh install of 1607 (without any sound existing). I had a heck of a time figuring out to disable secure boot to install win 10 on a gpt drive.
Anyway, I'm going to install 1511 in a bit and see if that does any better.
I believe the nv* driver is an nvidia driver.
It seems Cm6631a doesn't need drivers (I can't find them)...
It could be absurd to try intel hd 530 with fallout 4, but does the problem exist without NVidia drivers/software? Did you try it just for curiosity?
It could be absurd to try intel hd 530 with fallout 4, but does the problem exist without NVidia drivers/software? Did you try it just for curiosity?
NoChance
Well-known member
- Sep 2, 2016
- 59
Cmedia releases drivers to the oems only. So I get the drivers from the Device maker. The problem was just there without any loaded though, so that's not probably it.
I did run fallout with the hd530. At everything on the lowest it could get, at 1080p, it was 7ish fps.
I did run fallout with the hd530. At everything on the lowest it could get, at 1080p, it was 7ish fps.
Well, you can still try to rename that file (nvwgf2umx.dll) if your machine continues to refuse its own configuration.
Otherwise I'm afraid I'm out of ideas :noidea:
You can finally try to contact asus and NVidia supports (if you didn't already do it).
Otherwise I'm afraid I'm out of ideas :noidea:
You can finally try to contact asus and NVidia supports (if you didn't already do it).
Well I have another idea but you have probably already tried it: NVidia Threaded optimization either on or off (avoid auto).
Did you try it?
Did you try it?
NoChance
Well-known member
- Sep 2, 2016
- 59
Yes. I have tried the threaded options.
1511 also shows the wdf01000.sys USB issue on a clean install. That tells me that the issue is Windows 10, or my motherboard.
Do you see high isr from it?
the nvidia issue is there on 1511 with the launch drivers, though not nearly as bad.
1511 also shows the wdf01000.sys USB issue on a clean install. That tells me that the issue is Windows 10, or my motherboard.
Do you see high isr from it?
the nvidia issue is there on 1511 with the launch drivers, though not nearly as bad.
When there's the worst drop, these are the first in DPC graph (by duration):
Wdf01000.sys
nvlddmkm.sys
dxgkrnl.sys
ntoskrnl.exe
portcls.sys
And ISR:
dxgkrnl.sys
Wdf01000.sys
ndis.sys
storport.sys
But I'm not sure how they should be interpreted...
Wdf01000.sys
nvlddmkm.sys
dxgkrnl.sys
ntoskrnl.exe
portcls.sys
And ISR:
dxgkrnl.sys
Wdf01000.sys
ndis.sys
storport.sys
But I'm not sure how they should be interpreted...
OldGrayGary
Visiting Expert
- Jan 25, 2013
- 599
Hi again all
I know it sounds extreme ... but if the motherboard is still under warranty, it might be worthwhile to try a different board. I'd mentioned another ASUS Z170 user who had success by switching to an MSI Z170 board. Many of the same features, little of the same headaches (everything worked OK from the get-go, as a matter of fact). If you want to view that thread (it's rather remarkable how many system components are the same in your system and his)... it's here in the Windows 10 forum, the original poster is BestLux.
I don't think that every ASUS Z170 board has these stutter issues, but it's looking more and more like some certainly do. It might be nothing more than a production problem, and some boards have a defect. Might be hard for quality control to detect (but not so hard for the unlucky few who get the problem boards).
Hard to know! ... One thing is certain: systems with high-end components should produce high-end performance. You've paid good money, and the vendors need to come through.
One way or another -- hope it works out. You've been throwing a lot of effort into the troubleshooting [xilolee too -- you guys are marathoners!] ... I hope a resolution shows up soon!
I know it sounds extreme ... but if the motherboard is still under warranty, it might be worthwhile to try a different board. I'd mentioned another ASUS Z170 user who had success by switching to an MSI Z170 board. Many of the same features, little of the same headaches (everything worked OK from the get-go, as a matter of fact). If you want to view that thread (it's rather remarkable how many system components are the same in your system and his)... it's here in the Windows 10 forum, the original poster is BestLux.
I don't think that every ASUS Z170 board has these stutter issues, but it's looking more and more like some certainly do. It might be nothing more than a production problem, and some boards have a defect. Might be hard for quality control to detect (but not so hard for the unlucky few who get the problem boards).
Hard to know! ... One thing is certain: systems with high-end components should produce high-end performance. You've paid good money, and the vendors need to come through.
One way or another -- hope it works out. You've been throwing a lot of effort into the troubleshooting [xilolee too -- you guys are marathoners!] ... I hope a resolution shows up soon!
Hi Aphantos. :welcome:
Did you also check all things like NoChance did?
Did you also check all things like NoChance did?
Has Sysnative Forums helped you? Please consider donating to help us support the site!