AnsweredAssumed Answered

DirectX12 Multi GPU - Hard Reset / Reboot on any driver newer than 16.8.3

Question asked by nospheratu on Apr 9, 2017
Latest reply on Jun 15, 2017 by nospheratu

I am experiencing a hard reset/reboot on DirectX12 Multi GPU on any driver newer than the "non-whql-win10-64bit-radeon-software-crimson-16.8.3-aug30" driver with two 7970M cards.

 

I am using 3DMark's TimeSpy benchmark as a reference. My system specifications are below.

 

  • AMD Graphics Card
    • 2x Radeon 7970M
  • Desktop or Laptop System
    • Laptop - Alienware M17X R2
  • Operating System
    • Windows 10 64bit version 1703 (OS Build 15063.13)
  • Driver version installed
    • non-whql-win10-64bit-radeon-software-crimson-16.9.1-sep7 or newer
  • Display Devices
    • Samsung 170CT, Hardware ID: Monitor\SEC5443 [DELL P/N: J2CY8], default laptop display, 1920x1200 60hz
  • Motherboard
    • Default Alienware M17x R2 motherboard with Intel PM55 chipset
  • CPU
    • Intel Core i7 920XM
  • Power Supply Unit  Make, Model & Wattage
    • Dell 300W external Laptop PSU
  • RAM
    • 2 x 4GB Samsung DDR3

 

3DMark Version Information

TimeSpy 1.0

SystemInfo 5.0.609.0

GUI 2.3.3682 64

 

I run the TimeSpy benchmark at default settings. As soon as the application switches to fullscreen mode for the benchmark the PC immediately hard resets/reboots (The Timespy loading screen does not even appear). As a result there is no BSOD logged. If I disable CrossFire under Radeon Settings the benchmark runs fine albeit with one card. With the 16.8.3 driver mentioned above the benchmark runs perfectly well with CrossFire enabled under Radeon Settings.

 

Has anyone here experienced anything similar with DirectX12 Multi GPU?

 

I've experienced this issue with the below drivers

non-whql-win10-64bit-radeon-software-crimson-16.9.1-sep7

whql-win10-64bit-radeon-software-crimson-16.9.1-sep13

whql-win7-64bit-radeon-software-crimson-16.9.1-sep13

non-whql-win7-64bit-radeon-software-crimson-16.9.2-sep16

non-whql-win10-64bit-radeon-software-crimson-16.9.2-sep21

 

non-whql-win10-64bit-radeon-software-crimson-16.10.1-oct6

Non-WHQL-Win7-64Bit-Radeon-Software-Crimson-16.10.1-Oct6

whql-win10-64bit-radeon-software-crimson-16.10.1-oct13

whql-win7-64bit-radeon-software-crimson-16.10.1-oct13

non-whql-win10-64bit-radeon-software-crimson-16.10.2-oct19

non-whql-win7-64bit-radeon-software-crimson-16.10.2-oct19

non-whql-win10-64bit-radeon-software-crimson-16.10.3-oct27

non-whql-win10-64bit-radeon-software-crimson-16.11.3-nov8

non-whql-win10-64bit-radeon-software-crimson-16.11.5-nov25

win10-64bit-radeon-software-crimson-relive-16.12.1-dec7

non-whql-win10-64bit-radeon-software-crimson-relive-16.12.2-dec19

win10-64bit-radeon-software-crimson-relive-16.12.2-jan3

non-whql-win10-64bit-radeon-software-crimson-relive-17.1.1-jan16

non-whql-win10-64bit-radeon-software-crimson-relive-17.1.2-jan25

non-whql-win10-64bit-radeon-software-crimson-relive-17.2.1-feb10

whql-win10-64bit-radeon-software-crimson-relive-17.2.1-feb22

non-whql-win10-64bit-radeon-software-crimson-relive-17.3.1-mar3

non-whql-win10-64bit-radeon-software-crimson-relive-17.3.2-mar15

non-whql-win10-64bit-radeon-software-crimson-relive-17.3.3-mar16

Couldn't test "non-whql-win10-64bit-radeon-software-crimson-relive-17.4.1-apr3" as I'm getting BSOD's like many other members here (unrelated issue).

Outcomes