You could try to set "DataCollection" registry key to "0", which is "Security only" that is present in Enterprise. However you could try to see how far the gpedit.msc "Allow Telemetry" option goes, if it does not contain a "0" then you can't probably make it.
Could anybody tell how is gaming/3D/CPU performance compared to 1803? Like any positive or negative differences?
Hasn't crashed for me at all. Are you using any custom drivers or something that could cause problems?
Parables limp . The borked game-mode and xbox feature implemetation in 1703/09 had quite some impact on game performance hence the question is indeed legit.
Re: Game mode So far my experience with 1803 was that game mode was enabled by default and there was no switch to toggle. Switch got re-added in 1809. (correct me if i'm wrong but that's what i experienced)
What MSI has for my motherboard and Nvidia for my 1070ti. And Steelseries for my mouse/keyboard. Just 2 BSODs while playing Destiny 2 and the game CTDing a few times. Was really bad 2 days ago, Destiny CTD like 4-5 times. Not really an issue in 1803. Since then I've raided the web for more recent Intel MEI and RST drivers and ran Destiny 2 as admin, reinstalled the Nvidia driver after DDU yet again and for some reason the crashes stopped. Could be a sneaky Nvidia driver fix, they repacked it for RTX 2070 launch, noticed it had different size. It's incredibly annoying that troubleshooting crashes and BSODs is such an arcane thing to do. I really wish there would be an app that's able to interpret WinDBG outputs properly and just say why and how the crash happened. I mean, what am I supposed to get out of a exception_access_violation BSOD or crash?
I am also experiencing BSOD related to high GPU usage (baking lightmap on Unity 2018.3.0b6), can you tell me your Intel MEI and RST version number that you have found stable for 1809?
I use the Intel RST that was linked above, but I might have found a newer Intel MEI (1828.12.0.1152). I don't really want to list other forums/sites as maybe they're considered competition and I also can't vouch for them, but you can google it. Anyway, I doubt I solved this. Destiny 2 just crashed yet again. No BSOD yet, just CTD. I would also be wary of what you install. Apparently you should try to match the Intel RST driver with the RST module version in your BIOS. For 16.7, you definitely need something recent. not to mention your platform might have different MEI or RST versions. The above should work for Z370 that I know. But solving crashing? I'm not sure. I suspect the OS and/or Nvidia driver aren't yet mature enough/compatible. PS: What were your BSOD(s)? Mine were: SYSTEM_SERVICE_EXCEPTION REFERENCE_BY_POINTER (afd.sys something something)
Was on 1809 with the latest available drivers from the known driver site but always getting BSOD: Video scheduler internal error, currently i am on the line with NVIDIATechnical team to check in for the crash dump, until now there is no news. I am on Asus Rampage VI Extreme, and not sure if there is RST module version listed on the bios screen. Is there any tool that i can use to check it manually through the bios update file?. From developer side, the 1809 SDK is already out since the first 1809 announcement, probably if NVIDIA using & coding it could be better compatibility with the 1809. I guess it would be another one month for NVIDIA adding official 1809 supports if it's getting re-release.