home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 1
Support
Watch / Listen Media
Television (MyTV frontend and TV-Server)
Live TV Stutter since Win 10 upgrade
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="mm1352000" data-source="post: 1185165" data-attributes="member: 82144"><p>First, thank you for your patience and for collecting all that data - it's much appreciated. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite24" alt="(y)" title="Thumbs Up (y)" loading="lazy" data-shortname="(y)" /></p><p></p><p>If you're slightly confused, I'm <em>very</em> confused! <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile :)" loading="lazy" data-shortname=":)" /></p><p>Like I said in my previous reply, LatencyMon was intended to be a way to test the validity of the assumption that hardware, BIOS and drivers are identical. Anyhow, let's dive into the results.</p><p></p><p>Starting with the task manager results...</p><p>Memory and network look fine. Disk is a little more bursty than I'd have expected, but not greatly concerning. However my problem radar was well and truly going off the moment I saw the "system" process using so much CPU. I don't think that's normal at all.</p><p></p><p>Coming to the LatencyMon results...</p><p>Given the details in the "drivers" section, it certainly does appear like there's a network-related issue. When analysing I look first to the "highest execution" column. For a well behaving driver, that value shouldn't be over 500 us. nds.sys - part of the Windows networking stack - has definitely exceeded that... but then so has the NVidia GPU driver.</p><p></p><p>Based on the DPC count and total execution time we can calculate an average DPC execution time. nvlddmdkm.sys comes out at ~0.03 ms, whereas nds.sys comes out with ~0.07 ms. Given that result and the fact that the nds.sys DPC count is more than 6 times the nvlddmkm.sys count (which implies it has a much higher influence overall), the natural conclusion would be that first priority should be looking at the NIC driver. That's not to say that the GPU driver is okay.</p><p></p><p>Side-note for just a moment...</p><p>The hard page-fault resolution time from the "main" section stands out like a sore thumb. I have to confess that I'm not exactly sure what it means, and I've never seen anything like that before. LatencyMon manual gives a little guidance:</p><p><a href="http://www.resplendence.com/latencymon_using" target="_blank">http://www.resplendence.com/latencymon_using</a></p><p></p><p>Based on that, I'd suggest to focus on the DPC latency issues for now.</p><p>...though I did wonder whether your SSD might need a trim?</p><p>According to your older log files you only had 13.6 GB free.</p><p></p><p>Back to network-related stuff...</p><p>Looking back at your older log files it appears like you have 2 NICs:</p><p> Name: Realtek PCIe GBE Family Controller</p><p>Device ID: PCI\VEN_10EC&DEV_8168&SUBSYS_816819DA&REV_07\4&314741E0&0&00E0</p><p> Driver: n/a</p><p></p><p> Name: Intel(R) Centrino(R) Wireless-N 2230</p><p>Device ID: PCI\VEN_8086&DEV_0887&SUBSYS_40628086&REV_C4\4&3919A947&0&00E3</p><p> Driver: n/a</p><p></p><p><strong>Do you use both NICs?</strong></p><p>If no, please disable the one you don't use. That alone can make a difference. Hopefully you don't use the WiFi one. WiFi drivers are notorious for causing problems.</p><p></p><p><strong>Which driver versions do you have for each NIC?</strong></p><p><strong>Where did you get the drivers from?</strong></p><p>(Please answer for all your clients.)</p><p>Normally I'd recommend to get the latest drivers direct from Realtek and Intel rather than using Microsoft Update or mobo/system vendor (ie. Zotac in your case) drivers. However in some cases the latest driver is actually not the best... and/or the driver from the mobo/system vendor can perform better.</p></blockquote><p></p>
[QUOTE="mm1352000, post: 1185165, member: 82144"] First, thank you for your patience and for collecting all that data - it's much appreciated. (y) If you're slightly confused, I'm [I]very[/I] confused! :) Like I said in my previous reply, LatencyMon was intended to be a way to test the validity of the assumption that hardware, BIOS and drivers are identical. Anyhow, let's dive into the results. Starting with the task manager results... Memory and network look fine. Disk is a little more bursty than I'd have expected, but not greatly concerning. However my problem radar was well and truly going off the moment I saw the "system" process using so much CPU. I don't think that's normal at all. Coming to the LatencyMon results... Given the details in the "drivers" section, it certainly does appear like there's a network-related issue. When analysing I look first to the "highest execution" column. For a well behaving driver, that value shouldn't be over 500 us. nds.sys - part of the Windows networking stack - has definitely exceeded that... but then so has the NVidia GPU driver. Based on the DPC count and total execution time we can calculate an average DPC execution time. nvlddmdkm.sys comes out at ~0.03 ms, whereas nds.sys comes out with ~0.07 ms. Given that result and the fact that the nds.sys DPC count is more than 6 times the nvlddmkm.sys count (which implies it has a much higher influence overall), the natural conclusion would be that first priority should be looking at the NIC driver. That's not to say that the GPU driver is okay. Side-note for just a moment... The hard page-fault resolution time from the "main" section stands out like a sore thumb. I have to confess that I'm not exactly sure what it means, and I've never seen anything like that before. LatencyMon manual gives a little guidance: [URL]http://www.resplendence.com/latencymon_using[/URL] Based on that, I'd suggest to focus on the DPC latency issues for now. ...though I did wonder whether your SSD might need a trim? According to your older log files you only had 13.6 GB free. Back to network-related stuff... Looking back at your older log files it appears like you have 2 NICs: Name: Realtek PCIe GBE Family Controller Device ID: PCI\VEN_10EC&DEV_8168&SUBSYS_816819DA&REV_07\4&314741E0&0&00E0 Driver: n/a Name: Intel(R) Centrino(R) Wireless-N 2230 Device ID: PCI\VEN_8086&DEV_0887&SUBSYS_40628086&REV_C4\4&3919A947&0&00E3 Driver: n/a [B]Do you use both NICs?[/B] If no, please disable the one you don't use. That alone can make a difference. Hopefully you don't use the WiFi one. WiFi drivers are notorious for causing problems. [B]Which driver versions do you have for each NIC? Where did you get the drivers from?[/B] (Please answer for all your clients.) Normally I'd recommend to get the latest drivers direct from Realtek and Intel rather than using Microsoft Update or mobo/system vendor (ie. Zotac in your case) drivers. However in some cases the latest driver is actually not the best... and/or the driver from the mobo/system vendor can perform better. [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Support
Watch / Listen Media
Television (MyTV frontend and TV-Server)
Live TV Stutter since Win 10 upgrade
Contact us
RSS
Top
Bottom