Astrix_au Posted December 19, 2017 Posted December 19, 2017 Hi guys, I thought I'd just edit and re post my post I made to AMD regarding High Bandwidth Cache Controller crashing DCS 2.X which increases GPU VRAM from 8GB to whatever amount you set using system ram throught the new architecture of the GPU. Before updating to Fall creators update I was running the Creators update and I could use HBCC to increase my GPU VRAM while playing 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 or 2.1 previously crashes after loading my plane or after a little while, it always happens on the spitfire dogfight mission and Dora dogfight quick mission too. The spit instantly and the Dora after a little while. I included here the crash logs for you guys. 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. 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® Core 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 - 8.1.1.1624 Direct3D® Version - 9.14.10.01304 OpenGL® Version - 6.14.10.13497 OpenCL™ Version - 23.20.793.1024 AMD Mantle Version - Not Available AMD Mantle API Version - Not Available AMD Audio Driver Version - 10.0.1.6 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 - 016.001.001.000 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 CPU Intel Core i7 4770K @ 3.50GHz 36 °C Haswell 22nm Technology RAM 16.0GB Dual-Channel DDR3 @ 799MHz (10-10-10-27) Motherboard ASUSTeK COMPUTER INC. MAXIMUS VI FORMULA (SOCKET 1150) 34 °C Graphics BenQ XL2730Z (2560x1440@144Hz) 8176MB ATI Radeon RX Vega (ATI) 28 °C Storage 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 Audio Realtek High Definition Audiodcs.log-20171217-070806.zipdcs.log-20171217-072727.zipdcs.log-20171217-065110.zip
Astrix_au Posted December 24, 2017 Author Posted December 24, 2017 I did a fresh install of windows 10 1709 and the issue is still happening on 17.2.1 :( I want to be able to increase my GPU VRAM on my RX Vega 64 liquid :( without turning on HBCC segmentation to increase VRAM I get no crashes.
Astrix_au Posted December 25, 2017 Author Posted December 25, 2017 (edited) I think I found the cause. Since it wasn't the update the was broken after doinbg a fresh install. it had to be something else at the time I fist tried the update since I also updated the driver when I first tried Windows 10 FCU 1709. The last driver before FCU support works just fine with HBCC and DCS 2.2 (17.10.1), it must be the driver that gave initial support for 1709 which was 17.10.2. I installed 17.10.1 yesterday and the crashing issue with DCS 2.2 when increasing my VRAM disapeared. I know if I try 17.10.2 the issue will come back, I haven't tried that driver yet but I will update here when I test it to verify. The latest driver has so many new features so it sucks to have to use one from so many releases back. I let AMD know but being holidays and they have a skeleton crew on it could be sometime before it gets fixed. I worked it out by looking at videos I remember it was working when I had it activated and then looked at all the drivers at around that time, at the time I wanted to try the bleeding edge and try their first 1709 support after my PC updated a month after it's release. Glad to have finally found what was causing it, wasted so much time doing a fresh install during my holidays :( going back to work tomorrow. Edited December 25, 2017 by Astrix_au
Astrix_au Posted June 10, 2018 Author Posted June 10, 2018 Its' still crashing with Normandy and the Spitfire dogfight server with HBCC segmentation on the latest DCS/2.5.2.18307 and using AMD 18.5.2 driver. The F/A-18 carrier takeoff didn't crash at all and I had 14GB BBCC segmentation on my 8GB RX Vega 64 liquid. Below are the crash files for the spitfire dogfight crash.dcs.log-20180610-030503.zip
Recommended Posts