Announcement

Collapse
No announcement yet.

Burnuntest V9.2(1002) Data Verify Failure

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

  • David (PassMark)
    replied
    V8 and V9 are both pretty old now.
    It would be better if you were using the current software.

    In the V9 log there was this error,
    Value Read: 55, Value Expected: 237

    In binary:
    Read: 0011 0111
    Expected: 1110 1101

    So this isn't the typical single bit flip error that is the most common failure. But there was only a couple of bad bytes found in 2 hours as well.

    I would,
    0) Update to V10 of BurnInTest.
    1) Run the disk test just by itself to see if the error can be reproducible more quickly.
    2) If you have multiple machines with the same spec (a production line scenario) then see if the same error happens on the other machines.
    3) Preserve the test files on disk (see above) and then check the values in the test files
    4) If the error can be reproduced, replace the drive and see if the error goes away.
    5) If the error doesn't resolve itself with a new SSD, then replace with a different model SSD and re-test.
    6) If the error doesn't resolve itself and happens with multiple SSDs from different vendors, try a different M2 slot, different RAM, different CPU, different MB, in that order. If this is a laptop and everything is soldered down then you are in trouble (as they should make things that are repairable).

    Leave a comment:


  • Jack51041
    replied
    Hi David,
    this is V9.1 pro data verify failure log file.
    Attached Files

    Leave a comment:


  • Jack51041
    replied
    Hi David,
    We used V9.1 Pro 1009 to run again and the Data Verify failure same as before, to swap the disk it cannot fix, the V8.1 log detail as the following.


    BurnInTest results
    BurnInTest Version V8.1 Pro 1025
    Date Tue Dec 13 07:22:33 2022
    Logging level Normal
    System summary

    System summary
    Windows 10 Professional Edition build 22621 (64-bit),
    1 x AMD Eng Sample: 100-000000777-40_Y [1203.1 MHz],
    7.3GB RAM,
    AMD Radeon(TM) Graphics,
    477GB SSD,
    General
    System Name: DESKTOP-JAHM8DF
    Motherboard Manufacturer: ECS
    Motherboard Name: SP41MD
    Motherboard Version: Default string
    Motherboard Serial Number: Default string
    BIOS Manufacturer: American Megatrends International, LLC.
    BIOS Version: 1.01.00.STD T01
    BIOS Release Date: 12/08/2022
    BIOS Serial Number: Default string
    CPU
    CPU manufacturer: AuthenticAMD
    CPU Type: AMD Eng Sample: 100-000000777-40_Y
    CPUID Family 17, Model A0, Stepping 0
    Physical CPU's: 1
    Cores per CPU: 4
    Hyperthreading: Not capable
    CPU features: MMX SSE SSE2 SSE3 SSSE3 SSE4.1 SSE4.2 SSE4a DEP PAE AMD64 AES Turbo core AVX AVX2 XOP FMA3
    Clock frequencies:
    - Measured CPU speed: 1203.1 MHz [Turbo core: 4163.4MHz]
    - Multiplier: x3.3
    - Reference Clock: 368.5 MHz
    Cache per CPU package:
    - L1 Instruction Cache: 4 x 32 KB
    - L1 data cache: 4 x 32 KB
    - L2 cache: 4 x 512 KB
    - L3 cache: 4 MB
    Memory
    Total Physical Memory: 7481MB
    Available Physical Memory: 5731MB
    Memory devices:
    : 4096MB, 5500MHz,
    : 4096MB, 5500MHz,
    Virtual memory: C:\pagefile.sys (allocated base size 1216MB)
    Memory SPD

    Graphics
    AMD Radeon(TM) Graphics
    Chip Type: AMD Radeon Graphics Processor (0x1506)
    DAC Type: Internal DAC(400MHz)
    Memory: 512MB
    BIOS: 102-MENDOCINO-006
    Driver provider: Advanced Micro Devices, Inc.
    Driver version: 31.0.12042.4
    Driver date: 10-19-2022
    Monitor 1: 1366x768x32 60Hz (Primary monitor)
    Disk volumes
    C: Local Drive, \\?\Volume{061caf0c-c6b0-4a69-a499-9f836bf6bbc0}\, NTFS, (476.28GB total, 447.82GB free)
    Disk drives
    Disk drive: Model: Phison PM8512GPMCB47ECS-E13T2 Serial: 511220624023000014 (Disk: 0, Size: 476.94GB, Volumes: C)
    Optical drives

    Network
    Realtek PCIe GbE Family Controller (MAC: 1C:69:7A1:06:2D)
    Ports
    Keyboard Port: PS/2 connector
    Mouse Port: PS/2 connector
    USB
    USB xHCI Compliant Host Controller
    USB xHCI Compliant Host Controller
    USB xHCI Compliant Host Controller
    - MediaTek Inc. Wireless_Device (SN: 000000000)
    Result summary
    Test Start time Mon Dec 12 15:47:11 2022
    Test Stop time Tue Dec 13 07:14:33 2022
    Test Duration 015h 27m 22s
    Temperature CPU 0 (Min/Current/Max) 47.0C / 61.0C / 65.0C
    Temperature HDD 0 (Phison PM8512GPMCB47ECS-E13T2) (Min/Current/Max) 35.0C / 47.0C / 59.0C
    Test Cycles Operations Result Errors Last Error
    CPU 3462 137 Trillion PASS 0 No errors
    GPGPU 1852 2.8 Quadrillion PASS 0 No errors
    Memory (RAM) 194 1.532 Trillion PASS 0 No errors
    2D Graphics 430 738145 PASS 0 No errors
    3D Graphics 69 2.090 Million PASS 0 No errors
    Temperature - - PASS 0 No errors
    Sound 305 1.022 Billion PASS 0 No errors
    Disk (C 2896 31.586 Trillion FAIL 3 Data Verify failure
    TEST RUN FAILED
    Detailed event log
    Event
    LOG NOTE: 2022-12-12 15:47:13, Status, Main Tests started
    LOG NOTE: 2022-12-12 15:47:14, 3D Graphics, 3D test starting: Duty cycle = 100. Test on primary monitor (0). (x,y) = (310,200). WxH = 300x200.
    INFORMATION: 2022-12-12 17:35:21, Disk, C: Butterfly seeking skipped for this disk (SSD/NVMe)
    SERIOUS: 2022-12-12 21:13:10, Disk, C: Data Verify failure
    LOG NOTE: 2022-12-12 21:13:10, Disk, File: C:\BurnInTest test files\~bittestC00074, Value Read: 243, Value Expected: 241, Offset in file 5039522579, Ops: 10380025790464
    LOG NOTE: 2022-12-12 21:13:10, Disk, Disk Error (C: Data Verify failure in Cycle 963 with pattern Random data, random seeking
    INFORMATION: 2022-12-12 21:53:54, Disk, C: Butterfly seeking skipped for this disk (SSD/NVMe)
    INFORMATION: 2022-12-13 02:13:49, Disk, C: Butterfly seeking skipped for this disk (SSD/NVMe)
    SERIOUS: 2022-12-13 03:36:56, Disk, C: Data Verify failure
    LOG NOTE: 2022-12-13 03:36:56, Disk, File: C:\BurnInTest test files\~bittestC00050, Value Read: 231, Value Expected: 229, Offset in file 4248201011, Ops: 24738483142656
    LOG NOTE: 2022-12-13 03:36:56, Disk, Disk Error (C: Data Verify failure in Cycle 2274 with pattern Random data pattern
    SERIOUS: 2022-12-13 03:53:07, Disk, C: Data Verify failure
    LOG NOTE: 2022-12-13 03:53:07, Disk, File: C:\BurnInTest test files\~bittestC00066, Value Read: 240, Value Expected: 242, Offset in file 553602291, Ops: 24897791197184
    LOG NOTE: 2022-12-13 03:53:07, Disk, Disk Error (C: Data Verify failure in Cycle 2290 with pattern Random data pattern
    INFORMATION: 2022-12-13 06:34:51, Disk, C: Butterfly seeking skipped for this disk (SSD/NVMe)
    LOG NOTE: 2022-12-13 07:14:32, GPGPU, GPGPU ops for AMD Radeon(TM) Graphics: 2786297.21 billion
    LOG NOTE: 2022-12-13 07:14:34, Status, Test run stopped
    Report by PassMark BurnInTest V8.1 Pro, www.passmark.com, Report date: 13/Dec/2022

    Leave a comment:


  • David (PassMark)
    replied
    We released V8 in 2014. So it is getting rather old now, and we no longer support it.

    Likely it was a real hardware failure however. From the information provided we can't tell you the root cause.

    Leave a comment:


  • Jack51041
    replied
    Dear Sir,
    We got "data verify failure" for disk testing as well, but if we ran only disk testing and the verify failure is gone, what's the root cause? does it pass or is it burn in 8.1 1025 issue?

    Leave a comment:


  • SMTY
    replied
    Hi Richard
    If it happens twice, I would try to check Burn in V10
    Is there some option to set the burn tool to stop trimming , write and read on false comparisons? (includes, another slot)
    I mean burn-in validation C.D.E.F but E data validation failed, now C.D.F will be removed.
    Thanks

    Leave a comment:


  • Richard (PassMark)
    replied
    The data from the disk is read into RAM by the CPU, possibly the scope for the real root cause to be elsewhere. e.g. a bad byte in RAM that happened to be being used as a disk I/O buffer. If the error is not reproducible, then it is possible it is a 'soft' error, https://en.wikipedia.org/wiki/Soft_error

    Or if it is reproducible, then it fairly serious error for a hard drive. Check the Windows Event log, possibly there may be a corresponding event around the time the error happened.

    We are no longer supporting older versions of BurnInTest. V9.x is no longer being supported as development has moved onto V10. For further support, try testing with the latest release of the software.

    Leave a comment:


  • SMTY
    replied
    Hi Richard
    Thanks
    it is showing read 0xffffffff,
    We keep disk test files on failure
    Using the third tool winhex to read the file, the data we get is correct.
    Click image for larger version

Name:	image.png
Views:	431
Size:	65.5 KB
ID:	53554
    Click image for larger version

Name:	image.png
Views:	453
Size:	426.8 KB
ID:	53555
    Click image for larger version

Name:	image.png
Views:	444
Size:	414.3 KB
ID:	53556
    Thanks

    Leave a comment:


  • Richard (PassMark)
    replied
    What is the unit of the offset?​​​​​​ byte? sector?
    We need to check file "bitttestK00069" offset 318636032 bytes?
    The offset is in bytes from the start of the file. If you did not enable keep disk test files on error, then likely the file is no longer on the system. To keep disk test files on the system, specify the -K command line parameter when starting BurnInTest. From the help file:

    "-K

    Keep disk test files. Specifies not to delete the disk drive test files when an error (e.g. Verification error) occurs. This is intended to assist investigating disk errors. It is recommended that this option is used in conjunction with the Auto Stop Tests on Error feature within Preferences. Once the test files have been investigated, they should be deleted manually."

    What does "Ops" mean?
    The current number of operations (e.g. read/write) that has been performed at the time of the error.

    Leave a comment:


  • SMTY
    started a topic Burnuntest V9.2(1002) Data Verify Failure

    Burnuntest V9.2(1002) Data Verify Failure

    Hi
    I got an error: " data verify failure".
    The error log shows: "Disk, File: K:\BurnInTest files\~bitttestK00069, Value Read: 4294967295(0xFFFFFFFF), Value Expected: 0, Offset in file 318636032(0x12FE0000), Ops: 9742057472(0x244AC0000)".
    What is the unit of the offset?​​​​​​ byte? sector?
    We need to check file "bitttestK00069" offset 318636032 bytes?
    What does "Ops" mean?

    Thanks
Working...
X