UNSOLVED

vbscript2

updated

3 years ago

Closed

V

vbscript2

1 Rookie

•

3 Posts

1

346

July 11th, 2023 06:00

Aurora R15, RTX 4080, AWCC running stuttering in VR, workaround

I mostly just wanted to post this here in case it may be helpful to anyone else in the future:

I recently got my new Aurora R15 with an RTX 4080. Flat screen games seemed fine, but when I set my Index up on it, I was getting extreme stuttering, even just in the SteamVR Home app. After looking through several issues that seemed to exist between SteamVR and the NVidia drivers that were causing similar issues several months ago, I had tried several different things and the stuttering remained. This was happening just as bad at 90 Hz, 120 Hz, and 144 Hz (even though the exact same Index has been running flawlessly at 144 Hz on my RTX 2070 Super paired with a far older 5th-gen i7 CPU in a different computer for the last 3 years.)

Then I just disabled the AWCC service (and all of the other Dell services, such as those related to  SA (SupportAssist)) and the problem completely vanished. Instead of having many reprojected frames about every 1.5 seconds, I now have none at all, as expected. Turned the AWCC service back on just to check whether running that without SA was a problem or not and the stuttering was back and still pretty bad, though it subjectively didn't feel quite as bad was when SA was also running. I then turned the AWCC service back off again and all is good, so this confirms that the AWCC service was indeed the problem.

So, if you're planning to use your Alienware system for VR (at least with an RTX 40-series card,) you'll likely need to disable AWCC once you get your fan and overclocking settings configured as you want them.

It would be great if Dell (or, if it's a bug with the driver query API, NVidia?) could fix this, as being able to control the lights, fans, and overclocking and monitor temperatures without bringing the video card to its knees would be handy.

To disable the AWCC service, of course, one option is to simply uninstall AWCC entirely. However, if you want to leave it installed in case you need to adjust settings, you can manually turn its background service on and off. By default, it starts up when Windows starts up. However, you can change this in the Services control panel (or with the command-line utilities, such as sc.)

To disable the AWCC service from the Services control panel:
- Run services.msc
- Scroll down to AWCCService.
- Right-click AWCCService and select "Stop"
- Right-click AWCCService and select "Properties"
- Change "Startup type" to either "Manual" or "Disabled"

(As the names of those options imply, "Manual" means that a command has to be issued to Windows manually to start the AWCC service rather than it starting automatically when the computer boots, while "Disabled" means that it can't be started at all until the startup type is changed to something else.)

  • Vanadiel

    8 Professor

    •

    7094 Posts

    •

    29695 Points

    76

    0

    Posted July 11th, 2023 06:00

    This is a known issue with AWCC and Support assist. My understanding is that it has to do with the way Microsoft Defender uses Core isolation and memory integrity.

    You could try disabling core isolation and see if that takes care of the issue. I realize people don't always like turning off security features, but this feature was introduced not that long ago and if you were secure for years prior to that, I don't see a reason why you would be even more secure with this turned on, considering how it interferes with some processes and applications.