Discussion in 'Windows 10' started by slayer62, May 30, 2019.
for me is really stable for daily usage, even using old hardware.
The first thing i do after a clean install is to burn the system in. Running all types of benchmarks. Haven't seen any latency issue on any of the pc/notebooks we have at work.
At the moment I have a i9-9820X with 2x RTX 2080 Ti in SLI that's been running for weeks without issue.
I've even got it installed on a dual xeon server and that's fine as well...
I had to make a new microsoft account just to upvote it because it said my original account did not have access in the feedback app. So before you make assumptions about stuff you dont know educate yourself first xD. Considering that how many people do you think are actually going to do what I did to upvote it on something Microsoft probably doesn't even look at with how crap their q/a has been.
I noticed my ThinkPad W540 being uncharacteristically sluggish earlier and I have no idea why. The System process was going at a consistent ~10% for as long as I chose to watch it in Task Manager, so then I fired up Process Explorer and watched, nothing noted except that constant ~10% usage. Not sure what's going on, so I decided to shut everything down and fired up DPC Latency Checker and it's showing a consistent ~1000 µs level of latency and again, it should be less. I didn't bother checking it with 1809, but I know on this laptop with Windows 7 Pro x64 on it, the average latency was like ~300 µs. I have Wi-Fi off, using the latest drivers for every piece of hardware in this machine (Intel-based across the board, CPU, chipset, USB ports, Wi-Fi, etc, only big non-Intel hardware is the Nvidia Quadro K2100m GPU and I rarely actually use that in day to day operation, just gaming), Windows 10 Pro for Workstations fully updated.
Running LatencyMon 6.71 for about 20 minutes now, it says everything is working as expected since I rebooted but I'll leave it going and see if the same sluggish behavior returns. So far since the reboot the System process is "keeping quiet" so to speak, showing typical ~0.1% usage.
But that's another issue I just noted: been attempting to update for a few hours now and this one isn't working for whatever reason (this has nothing to do with this thread topic, of course), I suppose I'll give it a few more attempts overnight then just hope it'll work itself out:
You need to login to view this posts content.
You better lower your tone and upvote your education for yourself. I'm working professionally as a consulent with Windows since 1.0 came out, so I guess I know a liitle bit about how Windows works. Of course does MS not look at questions with only a few upvotes. You can tell if they look after something when there is an ufficial reply on a feedback question.
Besides that, nobody denies that some people and you have this bug, but it doesn't seem to affect the majority or at least they're not aware about it as they're not gamers. For most people this build is stable and running smooth, way better than the previous build.
For me it was stable and smooth as well but with random hard hitting DPC Latency spikes. On my system if you asked without me looking at LatencyMon how the build was I would say it was great. Regardless the DPC spikes are real. They do affect audio buffers depending on what is going on when the spike hits. It does need to be fixed as soon as possible. This problem does affect everyone I have spoken to with 1903 and all of my PCs with different CPUs and motherboards. You just may not notice them as they don't cause anything major unless it is a hard to run game or it involves audio buffers. Posts about this issue are everywhere now so hopefully it gets fixed soon.
Yeah for me the same last post in this Thread have a good one
2 minutes is not enough run it for like 30 to an hour just doing normal stuff and see if ntoskrnl goes kaboom with a 700+ spike. If you are one of the lucky ones who only gets a 650 to 750 ish spikes you prob wont notice it ever like how it was for me. The spikes though can be as big as 2500 which is crazy.
Any non trolls who still have 1903 can you check and see if the 175 update fixes the issue?
I haven't tested anything but it's no surprise to me if this issue won't get any fix over 1903(fix may come on next feature versions)
1809 terminal has lots of performance and ui bugs, they said it will never be fixed on 1809 itself
they fix some kind of bugs only on next feature releases, let's hope this one is not one of them
I kinda think you are right but dont want to believe you are right if that makes sense this issue sucks
no it doesn't.
seems to only affect cpu's newer than haswell and amd cpu's since Fx
It seems pretty normal, for me that is. I got an audio lag by launching Latency Monitor, before it even starting monitoring.
The audio lag before it starts is normal depending on pc load at the time of starting. The ntoskrnl spike is the 1903 gift that sadly keeps on giving