Announcement

Collapse
No announcement yet.

An error occured during the DX12 3D test

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • An error occured during the DX12 3D test

    We met problem when running burn-in on 3D test
    Please refer below attached file
    Could you share some suggestion?
    Thanks
    Attached Files

  • #2
    From the logs,

    +623.203s - ERROR: Asteroids::Present pNode->mCopyCommandQueue->Signal HRESULT (0x887a0005) Device removed reason (0x887a0007)
    +623.234s - DEBUG: DX12 Render call failed - code: -2005270523​

    Error code -2005270523 (0x887a0007 dxgi_error_device_reset) is a fairly common fault in 3D applications such as games. It means the device was removed from the system. i.e. likely it was a hardware failure. It looks like the video card driver may have crashed or stopped responding correctly at this point, try updating your GPU drivers.​

    Comment


    • #3
      HI Richard
      Thanks for your update.
      We did install the latest driver 2024/2/1 release GFX-31.0.101.2127
      We still duplicate issue on this version.
      Attached log for your reference. And please help to check if any suggestion for our situation.
      Thanks
      Attached Files

      Comment


      • #4
        SERIOUS: 2024-03-09 22:36:47, 3D Graphics, An error occured during the DX12 3D test
        LOG NOTE: 2024-03-09 22:36:47, 3D Graphics, Unexpected error running DirectX 12 Test. Error Number 0x887A0005 (-2005270523)
        LOG NOTE: 2024-03-09 22:36:47, 3D Graphics, The GPU device instance has been suspended. Use GetDeviceRemovedReason to determine the appropriate action.
        LOG NOTE: 2024-03-09 22:36:47, 3D Graphics, DXGI_ERROR_DEVICE_REMOVED (0x887a0005) - Device Removed reason: DXGI_ERROR_DEVICE_RESET (0x887a0007)


        Something is causing the "Device to be removed". Which might mean video card failed or video card device driver crashed.

        Try...
        ... lowering the load.
        ... running only the 3D by itself.

        Test Start time: Fri Mar 8 08:20:26 2024
        Current time: Sun Mar 10 04:12:30 2024
        Test Duration: 043h 52m 04s
        Temperature CPU 0 average (Min/Current/Max): 91.8C / 99.2C / 103.0C
        Temperature CPU 0 core 0 (Min/Current/Max): 92.0C / 98.0C / 103.0C
        Temperature CPU 0 core 1 (Min/Current/Max): 92.0C / 100.0C / 103.0C
        Temperature CPU 0 core 2 (Min/Current/Max): 91.0C / 100.0C / 103.0C
        Temperature CPU 0 core 3 (Min/Current/Max): 92.0C / 99.0C / 103.0C
        Cannot identify the machine specs from the logs, but you are running at some high temperatures. Make sure your system has adequate cooling.​

        Comment


        • #5
          Hi Richard
          Thanks for your update
          By lower the loading , attached setting for test loading screenshot
          Could you share the setting loading what you suggest?
          Thanks
          Attached Files

          Comment


          • #6
            For long duration testing it is not surprisingly to see a single 3D failure. This could be as simple as the monitor turning off or some screen popup that interrupts the 3D test. BurnInTest just reports when running the 3D test, the device was removed/lost. BurnInTest will start the test again after a duration and if it is able to acquire the device, then the test resumes.

            Did you try running the 3D test by itself?

            Could you share the setting loading what you suggest?
            https://www.passmark.com/support/bur...uty_cycles.php

            Comment

            Working...
            X