AnsweredAssumed Answered

HBCC M segment is crashing DCS 2.2 on Windows 10 64bit FCU 17.11.4

Question asked by astrix_au on Dec 11, 2017
Latest reply on Jun 9, 2018 by astrix_au

Hi guys,


Before updating to Fall creators update I was running the Creators update and I could use HBCC to increase my GPU VRAM while aying DCS 2.2 on my MSI RX VEGA 64 Wave.


Since updating Windows 10 to FCU whenever I try and use HBCC segmentation DCS 2.2 crashes after loading my plane and after a second it crashes.


After doing the segmentation the GPU VRAM available changes in the Task Manager from 8GB to 12GB but the system RAM is still showing 16GB, shouldn't it show 12GB available system RAM?


My system memory is  2x 8GB KIngston total 16.0GB Dual-Channel DDR3 @ 799MHz (10-10-10-27).


Is there something in FCU that is causing the issue, I used the latest DDUv17.0.8.0 after uninstalling the Radeon Drivers  and reinstalled 17.11.4 so driver install should be good, DDU deactivates automatic hardware driver updates since after updating to FCU even if you have edited a group policy to stop automatic hardware updates only after using DDU does it stop doing it itself and stays on the Microsoft Basic driver, there is a message in DDU telling you of this that I haven't seen before.


Please help fix this issue as at 2560x1440p 2xMSSA DCS 2.2 it can use 7.9-8GB VRAM just doing a quick dogfight in the Spitfire!


Please let me know if you guys need any more info from me regarding my setup.


EDIT: This important info I added from a post on the 26/12/17.

I reverted Radeon settings to 17.10.1 and DCS 2.2 didn't crash with 12 GB segmentation on my RX Vega64. I think I know why I thought it was Windows 10 FCU because the next driver has FCU support and I installed it when I first tried Windows 10 FCU but DCS was crashing as I had HBCC on, I think it will happen with 17.10.2 I will test possibly tomorrow.


So it is the driver at fault and not the game, I guess that is good to know.



Radeon Software Version - 17.11.4

Radeon Software Edition - Crimson ReLive

Graphics Chipset - Radeon RX Vega

High Bandwidth Cache Size - 8176 MB

High Bandwidth Cache Type - HBM2

Core Clock - 1750 MHz

Windows Version - Windows 10 (64 bit)

System Memory - 16 GB

CPU Type - Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz





Radeon Settings Version - 2017.1127.1953.35761

Driver Packaging Version - 17.40.2511.1015-171127a1-320995E-CrimsonReLive

Provider - Advanced Micro Devices, Inc.

2D Driver Version -

Direct3D® Version -

OpenGL® Version -

OpenCL™ Version - 23.20.793.1024

AMD Mantle Version - Not Available

AMD Mantle API Version - Not Available

AMD Audio Driver Version -

Vulkan™ Driver Version - 1.7.0

Vulkan™ API Version - 1.0.54





Graphics Card Manufacturer - Built by AMD

Graphics Chipset - Radeon RX Vega

Device ID - 687F

Vendor ID - 1002

SubSystem ID - 0B36

SubSystem Vendor ID - 1002

Revision ID - C0

Bus Type - PCI Express 3.0

Current Bus Settings - PCI Express 3.0 x16

BIOS Version -

BIOS Part Number - 113-D0500500-104

BIOS Date - 2017/08/11 17:31

High Bandwidth Cache Size - 8176 MB

High Bandwidth Cache Type - HBM2

High Bandwidth Cache Clock - 945 MHz

Core Clock - 1750 MHz

High Bandwidth Cache Bandwidth - 483 GByte/s

Memory Bit Rate - 1.89 Gbps

2D Driver File Path - /REGISTRY/MACHINE/SYSTEM/ControlSet001/Control/Class/{4d36e968-e325-11ce-bfc1-08002be10318}/0000






Piriform Speccy Summary

Operating System

Windows 10 Pro 64-bit


Intel Core i7 4770K @ 3.50GHz 36 °C

Haswell 22nm Technology


16.0GB Dual-Channel DDR3 @ 799MHz (10-10-10-27)




BenQ XL2730Z (2560x1440@144Hz)

8176MB ATI Radeon RX Vega (ATI) 28 °C


1863GB TOSHIBA DT01ACA200 (SATA) 38 °C

2794GB TOSHIBA DT01ACA300 (SATA) 38 °C

232GB Samsung SSD 840 EVO 250GB (SSD) 28 °C

465GB Samsung SSD 840 EVO 500GB (SSD) 34 °C

Optical Drives

No optical disk drives detected


Realtek High Definition Audio






Thanks AMD and anyone else helping with this issue.

Kind Regards