Looks as april fools update installed to me. Otherwise use 2.8C, whats the problem?:-)
I am having some issues upgrading to 2.9e. When I use 2.8C on my Vega rigs (Beta Blockchain drivers), I have no issues. If I try 2.9e, I run into this issue:
2018.05.21:22:58:46.662: main Phoenix Miner 2.9e Windows/msvc - Release
2018.05.21:22:58:46.662: main Cmd line: -amd -pool us1.ethermine.org:4444 -wal 0x61cab7e0c6cefc6bb9FC6005ef9850764fe4C561.vega1 -coin ETH -pass X
2018.05.21:22:58:47.804: main Available GPUs for mining:
2018.05.21:22:58:47.805: main GPU1: 687F:C1 (pcie 3), OpenCL 2.0, 8 GB VRAM, 64 CUs
2018.05.21:22:58:47.805: main GPU2: 687F:C1 (pcie 7), OpenCL 2.0, 8 GB VRAM, 64 CUs
2018.05.21:22:58:47.805: main GPU3: 687F:C1 (pcie 10), OpenCL 2.0, 8 GB VRAM, 64 CUs
2018.05.21:22:58:47.805: main GPU4: 687F:C1 (pcie 13), OpenCL 2.0, 8 GB VRAM, 64 CUs
2018.05.21:22:58:47.805: main GPU5: 687F:C1 (pcie 18), OpenCL 2.0, 8 GB VRAM, 64 CUs
2018.05.21:22:58:47.805: main GPU6: 687F:C1 (pcie 21), OpenCL 2.0, 8 GB VRAM, 64 CUs
2018.05.21:22:58:47.828: main ADL library initialized
2018.05.21:22:58:48.186: main Listening for CDM remote manager at port 3333 in read-only mode
2018.05.21:22:58:48.187: main Eth: the pool list contains 3 pools
2018.05.21:22:58:48.187: main Eth: primary pool: us1.ethermine.org:4444
2018.05.21:22:58:48.187: main Starting GPU mining
2018.05.21:22:58:48.187: main Matched GPU1 to ADL adapter index 24 (method 1)
2018.05.21:22:58:48.214: main GPU1: Using the X2 ODN API
2018.05.21:22:58:48.214: main GPU1: Created ADL monitor for adapter 24; overdrive version: 7
2018.05.21:22:58:48.218: main GPU1: using the blockchain beta driver
2018.05.21:22:58:48.218: main Matched GPU2 to ADL adapter index 30 (method 1)
2018.05.21:22:58:48.241: main GPU2: Using the X2 ODN API
2018.05.21:22:58:48.241: main GPU2: Created ADL monitor for adapter 30; overdrive version: 7
2018.05.21:22:58:48.241: main GPU2: using the blockchain beta driver
2018.05.21:22:58:48.241: main Matched GPU3 to ADL adapter index 12 (method 1)
2018.05.21:22:58:48.264: main GPU3: Using the X2 ODN API
2018.05.21:22:58:48.264: main GPU3: Created ADL monitor for adapter 12; overdrive version: 7
2018.05.21:22:58:48.264: main GPU3: using the blockchain beta driver
2018.05.21:22:58:48.264: main Matched GPU4 to ADL adapter index 18 (method 1)
2018.05.21:22:58:48.291: main GPU4: Using the X2 ODN API
2018.05.21:22:58:48.291: main GPU4: Created ADL monitor for adapter 18; overdrive version: 7
2018.05.21:22:58:48.291: main GPU4: using the blockchain beta driver
2018.05.21:22:58:48.291: main Matched GPU5 to ADL adapter index 6 (method 1)
2018.05.21:22:58:48.318: main GPU5: Using the X2 ODN API
2018.05.21:22:58:48.318: main GPU5: Created ADL monitor for adapter 6; overdrive version: 7
2018.05.21:22:58:48.318: main GPU5: using the blockchain beta driver
2018.05.21:22:58:48.318: main Matched GPU6 to ADL adapter index 0 (method 1)
2018.05.21:22:58:48.344: main GPU6: Using the X2 ODN API
2018.05.21:22:58:48.344: main GPU6: Created ADL monitor for adapter 0; overdrive version: 7
2018.05.21:22:58:48.344: main GPU6: using the blockchain beta driver
2018.05.21:22:58:48.344: wdog Starting watchdog thread
2018.05.21:22:58:48.345: main Eth: Connecting to ethash pool us1.ethermine.org:4444 (proto: EthProxy)
2018.05.21:22:58:48.480: eths Eth: Connected to ethash pool us1.ethermine.org:4444 (18.219.59.155)
2018.05.21:22:58:48.480: eths Eth: Send: {"id":1,"jsonrpc":"2.0","method":"eth_submitLogin","worker":"eth1.0","params":["0x61cab7e0c6cefc6bb9FC6005ef9850764fe4C561.vega1","5tarwar5"]}
2018.05.21:22:58:48.546: main GPU1: 30C 58%, GPU2: 29C 58%, GPU3: 32C 58%, GPU4: 28C 58%, GPU5: 30C 58%, GPU6: 30C 59%
2018.05.21:22:58:48.564: eths Eth: Received: {"id":1,"jsonrpc":"2.0","result":true}
2018.05.21:22:58:48.565: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}
2018.05.21:22:58:48.639: eths Eth: Received: {"id":5,"jsonrpc":"2.0","result":["0xacb4fe231378097ab12add466b810ebdda1b1095c501cc06d1ecc25a704b2d9b","0xc16796d9b504e2ac0305bf673638b84a7d0278ba389d82377cde63edcca1a1bb","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x564bc8"]}
2018.05.21:22:58:48.639: eths Eth: New job #acb4fe23 from us1.ethermine.org:4444; diff: 4000MH
2018.05.21:22:58:48.640: GPU1 GPU1: Starting up... (0)
2018.05.21:22:58:48.640: GPU1 Eth: Generating light cache for epoch #188
2018.05.21:22:58:48.641: GPU2 GPU2: Starting up... (0)
2018.05.21:22:58:48.643: GPU3 GPU3: Starting up... (0)
2018.05.21:22:58:48.645: GPU4 GPU4: Starting up... (0)
2018.05.21:22:58:48.647: GPU5 GPU5: Starting up... (0)
2018.05.21:22:58:48.649: GPU6 GPU6: Starting up... (0)
2018.05.21:22:58:50.737: GPU1 build: Failed to GPU1 program: clBuildProgram (-11)
2018.05.21:22:58:50.738: GPU1 GPU1: Failed to load kernels: clCreateKernel (-46)
2018.05.21:22:58:50.933: GPU2 build: Failed to GPU2 program: clBuildProgram (-11)
2018.05.21:22:58:50.933: GPU2 GPU2: Failed to load kernels: clCreateKernel (-46)
2018.05.21:22:58:51.125: GPU3 build: Failed to GPU3 program: clBuildProgram (-11)
2018.05.21:22:58:51.125: GPU3 GPU3: Failed to load kernels: clCreateKernel (-46)
2018.05.21:22:58:51.314: GPU4 build: Failed to GPU4 program: clBuildProgram (-11)
2018.05.21:22:58:51.314: GPU4 GPU4: Failed to load kernels: clCreateKernel (-46)
2018.05.21:22:58:51.346: wdog Thread(s) not responding. Restarting.
2018.05.21:22:58:51.513: GPU5 build: Failed to GPU5 program: clBuildProgram (-11)
2018.05.21:22:58:51.513: GPU5 GPU5: Failed to load kernels: clCreateKernel (-46)
2018.05.21:22:58:51.708: GPU6 build: Failed to GPU6 program: clBuildProgram (-11)
2018.05.21:22:58:51.708: GPU6 GPU6: Failed to load kernels: clCreateKernel (-46)
2018.05.21:22:58:53.360: main Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00
2018.05.21:22:58:53.360: main GPUs: 1: 0.000 MH/s (0) 2: 0.000 MH/s (0) 3: 0.000 MH/s (0) 4: 0.000 MH/s (0) 5: 0.000 MH/s (0) 6: 0.000 MH/s (0)
There is a bug with 2.9e as it appears the kernels used to build with were Vega 56 only and not Vega 64. Developer is aware of issue. Just verify if it is indeed the case, Vega 64s you see this issue. Also what card versions? Mine are Power Color Vega 64s. What brand are yours? I found issue was due to Windows April 1803 update. I then tried both 18.3.4 as well as new 18.4.1 AMD drivers with similar no luck.