Announcement

Collapse
No announcement yet.

3D graphics error : " No operations reported in timeout period "

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
  • #1

    3D graphics error : " No operations reported in timeout period "

    Hi Passmark ,
    Do you have any idea about this error ?
    When I run Bunin test for 4 hours , then system got a 3D graphics error : " No operations reported in timeout period "
    this fail at first round in 3D test : "3D Graphics 1 55783 FAIL 1 No operations reported in timeout period"

    below information was from the log file of burin test :

    **************
    RESULT SUMMARY
    **************
    Test Start time: Fri Aug 16 00:24:27 2024
    Test Stop time: Fri Aug 16 04:24:34 2024
    Test Duration: 004h 00m 07s
    Disk (C Speeds MB/s (Read/Write) 147.0 / 135.7

    Test Name Cycles Operations Result Errors Last Error
    CPU 863 10.950 Trillion PASS 0 No errors
    GPGPU 958 357 Trillion PASS 0 No errors
    Memory (RAM) 64 1.100 Trillion PASS 0 No errors
    2D Graphics 995 1.529 Trillion PASS 0 No errors
    3D Graphics 1 55783 FAIL 1 No operations reported in timeout period
    Sound 217 244 Million PASS 0 No errors
    Video Playback 665 8512 PASS 0 No errors
    Disk (C 388 1.920 Trillion PASS 0 No errors
    Network 1 45 1.800 Million PASS 0 No errors
    TEST RUN FAILED

    ******************
    DETAILED EVENT LOG
    ******************
    LOG NOTE: 2024-08-16 00:24:27, Status, PassMark BurnInTest 10.2 1013 (64-bit)
    LOG NOTE: 2024-08-16 00:24:27, BurnInTest, Perform test: CPU at 50%
    LOG NOTE: 2024-08-16 00:24:27, BurnInTest, Perform test: GPGPU at 50%
    LOG NOTE: 2024-08-16 00:24:27, BurnInTest, Perform test: Memory (RAM) at 50%
    LOG NOTE: 2024-08-16 00:24:27, BurnInTest, Perform test: 2D Graphics at 50%
    LOG NOTE: 2024-08-16 00:24:27, BurnInTest, Perform test: 3D Graphics at 50%
    LOG NOTE: 2024-08-16 00:24:27, BurnInTest, Perform test: Sound at 50%
    LOG NOTE: 2024-08-16 00:24:27, BurnInTest, Perform test: Video Playback at 50%
    LOG NOTE: 2024-08-16 00:24:27, BurnInTest, Perform test: Disk at 100%
    LOG NOTE: 2024-08-16 00:24:27, BurnInTest, Perform test: Disk end marker at 50%
    LOG NOTE: 2024-08-16 00:24:27, BurnInTest, Perform test: Network at 50%
    LOG NOTE: 2024-08-16 00:24:29, Status, Main Tests started
    LOG NOTE: 2024-08-16 00:24:31, 3D Graphics, 3D test starting: Duty cycle = 50. Test on primary monitor (1). (x,y) = (880,447). WxH = 800x600.
    LOG NOTE: 2024-08-16 00:24:31, 3D Graphics, Starting DX12 Test
    LOG NOTE: 2024-08-16 00:24:31, Video, Video test starting: Duty cycle = 50. Test on primary monitor (1). (x,y) = (0,32). WxH = 525x313.
    LOG NOTE: 2024-08-16 00:24:36, 3D Graphics, 3D DX12 test 1 - Running on NVIDIA GeForce MX570 A
    LOG NOTE: 2024-08-16 00:24:50, Memory (RAM), Process 0, Shared interface: BIT_Memory_Test-4036-0 (0)
    LOG NOTE: 2024-08-16 00:24:50, Memory (RAM), Process 1, Shared interface: BIT_Memory_Test-4036-1 (1)
    WARNING: 2024-08-16 00:45:28, 3D Graphics, No operations reported in timeout period
    LOG NOTE: 2024-08-16 00:53:42, 3D Graphics, 3D DX12 test 1 - Running on NVIDIA GeForce MX570 A
    LOG NOTE: 2024-08-16 01:11:31, 3D Graphics, 3D DX12 test 1 - Running on NVIDIA GeForce MX570 A
    LOG NOTE: 2024-08-16 01:44:11, 3D Graphics, 3D DX12 test 1 - Running on NVIDIA GeForce MX570 A
    INFORMATION: 2024-08-16 01:48:56, Disk, C: Butterfly seeking skipped for this disk (SSD/NVMe)
    LOG NOTE: 2024-08-16 02:02:39, 3D Graphics, 3D DX12 test 1 - Running on NVIDIA GeForce MX570 A
    LOG NOTE: 2024-08-16 02:20:55, 3D Graphics, 3D DX12 test 1 - Running on NVIDIA GeForce MX570 A
    LOG NOTE: 2024-08-16 02:39:21, 3D Graphics, 3D DX12 test 1 - Running on NVIDIA GeForce MX570 A
    LOG NOTE: 2024-08-16 02:56:58, 3D Graphics, 3D DX12 test 1 - Running on NVIDIA GeForce MX570 A
    LOG NOTE: 2024-08-16 03:14:40, 3D Graphics, 3D DX12 test 1 - Running on NVIDIA GeForce MX570 A
    LOG NOTE: 2024-08-16 03:33:43, 3D Graphics, 3D DX12 test 1 - Running on NVIDIA GeForce MX570 A
    LOG NOTE: 2024-08-16 03:59:31, 3D Graphics, 3D DX12 test 1 - Running on NVIDIA GeForce MX570 A
    LOG NOTE: 2024-08-16 04:17:20, 3D Graphics, 3D DX12 test 1 - Running on NVIDIA GeForce MX570 A
    LOG NOTE: 2024-08-16 04:24:29, GPGPU, GPGPU ops for 1: NVIDIA GeForce MX570 A: 320356.23 billion
    LOG NOTE: 2024-08-16 04:24:29, GPGPU, GPGPU ops for 2: Intel(R) Graphics: 37251.15 billion
    LOG NOTE: 2024-08-16 04:24:42, Status, Test run stopped


    ​​

    Click image for larger version Name: 3D_fail.jpg Views: 149 Size: 314.3 KB ID: 57553
    Tags: None
  • #2
    It isn't a known issue (with this card), but the GeForce MX570 A also isn't a common card. We've seen other cards / device driver combos cause this however.

    LOG NOTE: 2024-08-16 04:17:20, 3D Graphics, 3D DX12 test 1 - Running on NVIDIA GeForce MX570 A​
    Maybe the video card device driver crashed (or a bug). Or it is hardware failure.

    Might be worth looking in the Window event log around 2024-08-16 04:17:20 to see if there where any reported errors.

    If the problem is consistent and can be reproduced, then debug mode might also log additional information
    https://www.passmark.com/support/bitdebug.php

    Running just the 3D test by itself at 100% might also be interesting (i.e. trying to narrow down the combination of factors that provoke the issue).

    Comment

    • #3
      Hi , David ,

      I caputre log by debug mode , could you help to check logs as attachment ?
      Is it an issue related with Bunin tool ?
      Attached Files

      Comment

      • #4
        Each 3 minutes there is a check done (called the watchdog) to confirm that expecting activities are progressing.
        Sometimes if the hardware suddenly resets or there is a driver crash, the fault might go unnoticed otherwise.

        Log showed this.

        LOG NOTE: 2024-08-30 03:01:44, Operation watchdog for 3D Graphics is 35290 (previous 34976) <== Roughly 2 Frames per second
        LOG NOTE: 2024-08-30 03:04:44, Operation watchdog for 3D Graphics is 35653 (previous 35290)
        LOG NOTE: 2024-08-30 03:07:44, Operation watchdog for 3D Graphics is 36016 (previous 35653)
        LOG NOTE: 2024-08-30 03:10:44, Operation watchdog for 3D Graphics is 36367 (previous 36016)
        LOG NOTE: 2024-08-30 03:13:44, Operation watchdog for 3D Graphics is 36490 (previous 36367)
        WARNING: 2024-08-30 03:16:44, 3D Graphics, No operations reported in timeout period
        LOG NOTE: 2024-08-30 03:16:44, Operation watchdog triggered for 3D Graphics is 36490 (previous 36490) <== No frames for 3 minutes !!
        LOG NOTE: 2024-08-30 03:19:44, Operation watchdog for 3D Graphics is 36498 (previous 36490) <== Test restarted here and continued again without problem
        LOG NOTE: 2024-08-30 03:22:44, Operation watchdog for 3D Graphics is 36807 (previous 3649
        LOG NOTE: 2024-08-30 03:25:44, Operation watchdog for 3D Graphics is 37126 (previous 36807)
        LOG NOTE: 2024-08-30 03:28:44, Operation watchdog for 3D Graphics is 37445 (previous 37126)
        LOG NOTE: 2024-08-30 03:31:44, Operation watchdog for 3D Graphics is 37714 (previous 37445)​

        So the 3D rendering progressed fine until 2024-08-30 03:13:44. But then, for reasons unknown, the task stopped progressing. No more frames were rendered for a 3 minute period. This eventually produced the warning you have seen. There were no other errors in the log. Other tasks (CPU, Disk, RAM, Network) continued without problem during this period, so the machine was not asleep or frozen or something like that.

        So that's all we can tell you. With the machine under fairly high load, it looks like the 3D function stopped for around at 3min period.

        Comment

        • #5
          Hi David ,

          No frames for 3 minutes
          -> I check log of GPU , GPU still work and keep P-state at P0/P3 in that 3 mins. So I am confusing about why your log show "no frames for 3 minutes".

          LeoYS

          Comment

          • #6
            From my previous post:

            Might be worth looking in the Window event log around 2024-08-16 04:17:20 to see if there where any reported errors.

            Running just the 3D test by itself at 100% might also be interesting (i.e. trying to narrow down the combination of factors that provoke the issue).​

            Would also be interesting to know if it was a one off issue or reproducible and if reproducible, did it happen after the same test duration each time (i.e. could be driver not freeing resources).

            Comment

            • #7
              Hi David ,

              I didn't see abnormal event in Windows event log around 2024-08-16 04:17:20.
              Running just the 3D test by itself at 100% might also be interesting
              -> default setting of 3D graphics test was 50% , I used 50% can repro issue within 4 hours.

              LeoYS
              Last edited by Leoys_Lee; Sep-05-2024, 03:27 AM.

              Comment

              • #8
                Can you run in debug mode (see above) and post the log from the run with just the 3D test running (50% or 100%).
                If it takes 4hours exactly each time, it is likely a resource issue (i.e. a driver bug).

                Comment

                • #9
                  Hi David ,

                  I had posted before as attachment. running 50% for 4 hours.

                  LeoYS
                  Attached Files

                  Comment

                  • #10
                    The logs you posted don't match your description.
                    The logs show many different tests running at the same time and not just the 3D test.

                    Comment

                    Previous template Next
                    Working...
                    X