Announcement

Collapse
No announcement yet.

BurninTset 10.2 shows a 2D graphic test error:Error verifying data in GPU memory.

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

  • BurninTset 10.2 shows a 2D graphic test error:Error verifying data in GPU memory.

    After I upgraded the Windows OS from 23H2 to 24H2, a 2D graphic test error appeared when running the BurninTest10.2 program.

  • #2
    Error verifying data in GPU memory means that the data read from the video RAM doesn't match the data written to it.

    This is typically a device driver bug messing up the memory allocations (e.g. allocating the same video RAM twice) or a hardware failure in the video RAM.

    Comment


    • #3
      However, this error did not occur on Win11 23H2 OS, only when I updated the OS to WIN11 24H2 did this error occur.Click image for larger version

Name:	image.png
Views:	3
Size:	895.3 KB
ID:	58046

      Comment


      • #4
        Maybe update came with a new video card device driver version?
        Did you compare the versions?

        Comment


        • #5
          The graphics driver was not updated and is the same version, only the operating system was updated.

          Comment


          • #6
            Maybe it is a real hardware fault in that case. Did you try swapping the video card?

            Comment


            • #7
              My PC is an integrated graphics card, not a discrect graphics card, so it can't be swapped. And my PC has tested MemTest86, and the result is pass. So I don't think it's an HW issue.

              Comment


              • #8
                You should
                1) Reproduce the test several times and make sure this happens 100% of the time on 24H2.
                2) Revert to 23H2 and check the problem never happens, even when you do several runs.

                As it might just be a co-incidence.

                Might just be a purely random hardware fault (or driver bug). RAM faults and software errors are not always consistent.

                Comment


                • #9
                  I have verified several times that this error occurs 100% on a 24H2OS, and it never occur when I return the OS to 23H2 , so it is not a coincidence.

                  Comment

                  Working...
                  X