Burn Test Log Errors

[samsam]

Hello!

I have these errors and am not sure whats going on with my m.2 drive:

PassMark BurnInTest Log file - https://www.passmark.com
================================================== ======

Date: Thu Nov 5 17:46:54 2020

BurnInTest V9.1 Pro 1009 (64-bit)

*** Unlicensed trial version ***

System summary:
Windows 10 Professional Edition build 19041 (64-bit),
1 x Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz,
15.9GB RAM,
AMD Radeon RX 580,
2 x 1863GB HDD, 238GB SSD, 2 x 894GB SSD, 447GB SSD,


General:
System Name: NUNO-CASA
System Model: Z370 AORUS Gaming K3
Motherboard Manufacturer: Gigabyte Technology Co., Ltd.
Motherboard Name: Z370 AORUS Gaming K3-CF
Motherboard Version: x.x
Motherboard Serial Number: Default string
BIOS Manufacturer: American Megatrends Inc.
BIOS Version: F13
BIOS Release Date: 03/22/2019
BIOS Serial Number: Default string
TPM: Not found
Webcam SparkoCam Video

CPU:
CPU manufacturer: GenuineIntel
CPU Type: Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz
Codename: Coffee Lake
CPUID: Family 6, Model 9E, Stepping A
Socket: LGA 1151
Lithography: 14nm
Physical CPU's: 1
Cores per CPU: 6
Hyperthreading: Enabled
CPU features: MMX SSE SSE2 SSE3 SSSE3 SSE4.1 SSE4.2 DEP PAE Intel64 Turbo AES AVX AVX2 FMA3
Clock frequencies:
- Measured CPU speed: 3696.2 MHz [Turbo: 4795.1MHz]
- Multiplier: x37.0 [Turbo: x48.0]
- Base Clock: 100.0 MHz
- Multiplier range: Min: x8, Max non turbo: x37 [Ratio: 4C: x48, 3C: x48, 2C: x48, 1C: x48]
Cache per CPU package:
- L1 Instruction Cache: 4 x 32 KB
- L1 data cache: 4 x 32 KB
- L2 cache: 4 x 256 KB
- L3 cache: 12 MB

Memory
Total Physical Memory: 16326MB
Available Physical Memory: 12031MB
Memory devices:
Slot 1:
- 8GB DDR4 SDRAM PC4-19207
- Crucial Technology BLS8G4D240FSC.16FBD, serial#: 0xA32B0E82
- XMP: 1.20V, Clk: 1200.5MHz, Timings 16-16-16-39
Slot 2:
- 8GB DDR4 SDRAM PC4-19207
- Crucial Technology BLS8G4D240FSC.16FBD, serial#: 0xA91D725E
- XMP: 1.20V, Clk: 1200.5MHz, Timings 16-16-16-39
Slot 3:
- Not populated
Slot 4:
- Not populated
Virtual memory: C:\pagefile.sys (allocated base size 2432MB)

Memory SPD:
DIMM#0
Memory type: DDR4 SDRAM
SPD revision: 1.1
Manufacturer: Crucial Technology
Serial number: A32B0E82
Part number: BLS8G4D240FSC.16FBD
Clock speed: 1200.5 MHz
Memory size: 8192 MB
ECC: No
Module voltage: 1.2V
XMP Revision: 2.0
[XMP Profile 1] Module voltage: 1.20V
[XMP Profile 1] Clock speed: 1200.5 MHz
[XMP Profile 1] Minimum clock cycle time (tCK): 0.833 ns
[XMP Profile 1] Supported CAS latencies: 7 8 9 10 11 12 13 14 15 16 17 18 19 20

DIMM#1
Memory type: DDR4 SDRAM
SPD revision: 1.1
Manufacturer: Crucial Technology
Serial number: A91D725E
Part number: BLS8G4D240FSC.16FBD
Clock speed: 1200.5 MHz
Memory size: 8192 MB
ECC: No
Module voltage: 1.2V
XMP Revision: 2.0
[XMP Profile 1] Module voltage: 1.20V
[XMP Profile 1] Clock speed: 1200.5 MHz
[XMP Profile 1] Minimum clock cycle time (tCK): 0.833 ns
[XMP Profile 1] Supported CAS latencies: 7 8 9 10 11 12 13 14 15 16 17 18 19 20


Graphics
AMD Radeon RX 580
Chip Type: 0x67DF
DAC Type: Internal DAC(400MHz)
Memory: 4096MB
BIOS: 113-1E3660EU-O55
Driver provider: Advanced Micro Devices, Inc.
Driver version: 17.7
Driver date: 3-3-2018
Monitor 1: 1920x1080x32 59Hz 96 DPI (Primary monitor)

Disk volumes
C: Local Drive, \\?\Volume{70260e5b-0868-4a6b-b7f3-3b00a33fadd5}\, NTFS, (444.94GB total, 340.19GB free)
D: Local Drive, \\?\Volume{e89a8b62-b932-40bc-a9f2-daf18a9146a4}\, SEAGATE2TB, FAT32, (1862.37GB total, 1729.29GB free)
F: Local Drive, \\?\Volume{b639860a-0000-0000-0000-100000000000}\, Segate 2, NTFS, (1863.02GB total, 1862.63GB free)
G: Local Drive, \\?\Volume{b2516892-36ad-4aad-a300-d05c31861297}\, Recuperação, NTFS, (1.83GB total, 1.78GB free)
H: Local Drive, \\?\Volume{307676db-0000-0000-0000-100000000000}\, samsung256, NTFS, (238.47GB total, 238.29GB free)
M: Local Drive, \\?\Volume{ec5d3a80-b2af-01d6-4099-2ef65759eb00}\, CORSAIR1, NTFS, (894.25GB total, 894.13GB free)
N: Local Drive, \\?\Volume{e2afc779-0000-0000-0000-100000000000}\, CORSAIR2, NTFS, (894.25GB total, 894.12GB free)

Disk drives
Unidade: Model: ST2000VN000-1HJ164 Serial: Z52035D9 (Disk: 2, Size: 1863.01GB, Interface: SATA, Volumes: D)
Unidade: Model: ST2000DM001-1CH164 Serial: W1E6R17B (Disk: 3, Size: 1863.01GB, Interface: SATA, Volumes: F)
Unidade: Model: Samsung SSD 850 PRO 256GB Serial: S1SUNSAG345048P (Disk: 1, Size: 238.47GB, Interface: SATA, Volumes: H)
Unidade: Model: Force MP510 Serial: 19188207000127715022 (Disk: 5, Size: 894.25GB, Interface: NVMe, Volumes: N)
Unidade: Model: BLUERAY SSD Serial: 1814022601005 (Disk: 0, Size: 447.13GB, Interface: SATA, Volumes: C G)
Unidade: Model: Force MP510 Serial: 19188207000127715021 (Disk: 4, Size: 894.25GB, Interface: NVMe, Volumes: M)

Optical drives

Network
Intel(R) Ethernet Connection (2) I219-V (Speed: 1Gb/s) (MAC: E05:5E:29:C7:19) (IPv4: 192.168.0.102)

Ports
Mouse Port: PS/2 connector
Keyboard Port: PS/2 connector

USB
Controlador Anfitrião Compatível Com USB xHCI
- Logitech USB Receiver
Controlador Anfitrião Compatível Com USB xHCI
Controlador Anfitrião Compatível Com USB xHCI


**************
RESULT SUMMARY
**************
Test Start time: Thu Nov 5 17:42:45 2020
Test Stop time: Thu Nov 5 17:46:38 2020
Test Duration: 000h 03m 53s
Temperature CPU 0 average (Min/Current/Max): 28.2C / 41.3C / 46.3C
Temperature CPU 0 core 0 (Min/Current/Max): 29.0C / 45.0C / 45.0C
Temperature CPU 0 core 1 (Min/Current/Max): 29.0C / 42.0C / 45.0C
Temperature CPU 0 core 2 (Min/Current/Max): 29.0C / 43.0C / 50.0C
Temperature CPU 0 core 3 (Min/Current/Max): 28.0C / 43.0C / 48.0C
Temperature CPU 0 core 4 (Min/Current/Max): 28.0C / 41.0C / 43.0C
Temperature CPU 0 core 5 (Min/Current/Max): 26.0C / 34.0C / 47.0C
Temperature HDD 0 (BLUERAY SSD) (Min/Current/Max): 33.0C / 36.0C / 39.0C
Temperature HDD 1 (Samsung SSD 850 PRO 256GB) (Min/Current/Max): 20.0C / 20.0C / 20.0C
Temperature HDD 2 (ST2000VN000-1HJ164) (Min/Current/Max): 20.0C / 21.0C / 21.0C
Temperature HDD 3 (ST2000DM001-1CH164) (Min/Current/Max): 21.0C / 23.0C / 23.0C
Temperature HDD 4 (Force MP510) (Min/Current/Max): NA / NA / NA
Temperature HDD 5 (Force MP510) (Min/Current/Max): NA / NA / NA
Temperature GPU 0 (Radeon RX 580 Series) (Min/Current/Max): 20.0C / 24.0C / 24.0C

Test Name Cycles Operations Result Errors Last Error
Temperature - - PASS 0 No errors
Disk (M 19 72.029 Billion FAIL 16 Test file could not be created. Check access privileges.
Disk (N 19 72.004 Billion FAIL 16 Test file could not be created. Check access privileges.
TEST RUN FAILED

******************
DETAILED EVENT LOG
******************
LOG NOTE: 2020-11-05 17:42:46, Status, Main Tests started
SERIOUS: 2020-11-05 17:43:50, Disk, M: Error while reading from the disk
LOG NOTE: 2020-11-05 17:43:50, Disk, Verify Read File: M:\BurnInTest test files\~bittestM00004, Block Size: 4194304, Block Num: 1151, Ops: 72028782592
LOG NOTE: 2020-11-05 17:43:50, Disk, Foi especificado um dispositivo inexistente (translates to a missing device was specified). (433)
LOG NOTE: 2020-11-05 17:43:50, Disk, Disk Error (M: Error while reading from the disk in Cycle 3 with pattern Sequential data pattern
SERIOUS: 2020-11-05 17:43:52, Disk, N: Error while reading from the disk
LOG NOTE: 2020-11-05 17:43:52, Disk, Verify Read File: N:\BurnInTest test files\~bittestN00004, Block Size: 4194304, Block Num: 1145, Ops: 72003616768
LOG NOTE: 2020-11-05 17:43:52, Disk, Foi especificado um dispositivo inexistente. (433)
LOG NOTE: 2020-11-05 17:43:52, Disk, Disk Error (N: Error while reading from the disk in Cycle 3 with pattern Sequential data pattern
SERIOUS: 2020-11-05 17:44:00, Disk, M: Error while writing to the disk
LOG NOTE: 2020-11-05 17:44:00, Disk, Write File 1st Block: M:\BurnInTest test files\~bittestM00005, Block Size: 4194304, Block Num: 1, Ops: 72028782592 (A)
LOG NOTE: 2020-11-05 17:44:00, Disk, Foi especificado um dispositivo inexistente. (433)
LOG NOTE: 2020-11-05 17:44:00, Disk, Disk Error (M: Error while writing to the disk in Cycle 4 with pattern Sequential data pattern
SERIOUS: 2020-11-05 17:44:03, Disk, N: Error while writing to the disk
LOG NOTE: 2020-11-05 17:44:03, Disk, Write File 1st Block: N:\BurnInTest test files\~bittestN00005, Block Size: 4194304, Block Num: 1, Ops: 72003616768 (A)
LOG NOTE: 2020-11-05 17:44:03, Disk, Foi especificado um dispositivo inexistente. (433)
LOG NOTE: 2020-11-05 17:44:03, Disk, Disk Error (N: Error while writing to the disk in Cycle 4 with pattern Sequential data pattern
SERIOUS: 2020-11-05 17:44:12, Disk, M: Error while writing to the disk
LOG NOTE: 2020-11-05 17:44:12, Disk, Write File 1st Block: M:\BurnInTest test files\~bittestM00006, Block Size: 4194304, Block Num: 1, Ops: 72028782592 (A)
LOG NOTE: 2020-11-05 17:44:12, Disk, Foi especificado um dispositivo inexistente. (433)

LOG NOTE: 2020-11-05 17:45:39, Disk, Disk Error (M: Error while writing to the disk in Cycle 13 with pattern Sequential data pattern
SERIOUS: 2020-11-05 17:45:41, Disk, N: Error while writing to the disk
LOG NOTE: 2020-11-05 17:45:41, Disk, Write File 1st Block: N:\BurnInTest test files\~bittestN00014, Block Size: 4194304, Block Num: 1, Ops: 72003616768 (A)
LOG NOTE: 2020-11-05 17:45:41, Disk, Foi especificado um dispositivo inexistente. (433)
LOG NOTE: 2020-11-05 17:45:41, Disk, Disk Error (N: Error while writing to the disk in Cycle 13 with pattern Sequential data pattern
SERIOUS: 2020-11-05 17:45:50, Disk, M: Error while writing to the disk
LOG NOTE: 2020-11-05 17:45:50, Disk, Write File 1st Block: M:\BurnInTest test files\~bittestM00015, Block Size: 4194304, Block Num: 1, Ops: 72028782592 (A)
LOG NOTE: 2020-11-05 17:45:50, Disk, Foi especificado um dispositivo inexistente. (433)
LOG NOTE: 2020-11-05 17:45:50, Disk, Disk Error (M: Error while writing to the disk in Cycle 14 with pattern Sequential data pattern
SERIOUS: 2020-11-05 17:45:52, Disk, N: Error while writing to the disk
LOG NOTE: 2020-11-05 17:45:52, Disk, Write File 1st Block: N:\BurnInTest test files\~bittestN00015, Block Size: 4194304, Block Num: 1, Ops: 72003616768 (A)
LOG NOTE: 2020-11-05 17:45:52, Disk, Foi especificado um dispositivo inexistente. (433)
LOG NOTE: 2020-11-05 17:45:52, Disk, Disk Error (N: Error while writing to the disk in Cycle 14 with pattern Sequential data pattern
SERIOUS: 2020-11-05 17:46:01, Disk, M: Error while writing to the disk
LOG NOTE: 2020-11-05 17:46:01, Disk, Write File 1st Block: M:\BurnInTest test files\~bittestM00016, Block Size: 4194304, Block Num: 1, Ops: 72028782592 (A)
LOG NOTE: 2020-11-05 17:46:01, Disk, Foi especificado um dispositivo inexistente. (433)
LOG NOTE: 2020-11-05 17:46:01, Disk, Disk Error (M: Error while writing to the disk in Cycle 15 with pattern Sequential data pattern
SERIOUS: 2020-11-05 17:46:03, Disk, N: Error while writing to the disk
LOG NOTE: 2020-11-05 17:46:03, Disk, Write File 1st Block: N:\BurnInTest test files\~bittestN00016, Block Size: 4194304, Block Num: 1, Ops: 72003616768 (A)
LOG NOTE: 2020-11-05 17:46:03, Disk, Foi especificado um dispositivo inexistente. (433)
LOG NOTE: 2020-11-05 17:46:03, Disk, Disk Error (N: Error while writing to the disk in Cycle 15 with pattern Sequential data pattern
SERIOUS: 2020-11-05 17:46:12, Disk, M: Error while writing to the disk
LOG NOTE: 2020-11-05 17:46:12, Disk, Write File 1st Block: M:\BurnInTest test files\~bittestM00017, Block Size: 4194304, Block Num: 1, Ops: 72028782592 (A)
LOG NOTE: 2020-11-05 17:46:12, Disk, Foi especificado um dispositivo inexistente. (433)
LOG NOTE: 2020-11-05 17:46:12, Disk, Disk Error (M: Error while writing to the disk in Cycle 16 with pattern Sequential data pattern
SERIOUS: 2020-11-05 17:46:14, Disk, N: Error while writing to the disk
LOG NOTE: 2020-11-05 17:46:14, Disk, Write File 1st Block: N:\BurnInTest test files\~bittestN00017, Block Size: 4194304, Block Num: 1, Ops: 72003616768 (A)
LOG NOTE: 2020-11-05 17:46:14, Disk, Foi especificado um dispositivo inexistente. (433)
LOG NOTE: 2020-11-05 17:46:14, Disk, Disk Error (N: Error while writing to the disk in Cycle 16 with pattern Sequential data pattern
SERIOUS: 2020-11-05 17:46:23, Disk, M: Error while writing to the disk
LOG NOTE: 2020-11-05 17:46:23, Disk, Write File 1st Block: M:\BurnInTest test files\~bittestM00018, Block Size: 4194304, Block Num: 1, Ops: 72028782592 (A)
LOG NOTE: 2020-11-05 17:46:23, Disk, Foi especificado um dispositivo inexistente. (433)
LOG NOTE: 2020-11-05 17:46:23, Disk, Disk Error (M: Error while writing to the disk in Cycle 17 with pattern Sequential data pattern
SERIOUS: 2020-11-05 17:46:25, Disk, N: Error while writing to the disk
LOG NOTE: 2020-11-05 17:46:25, Disk, Write File 1st Block: N:\BurnInTest test files\~bittestN00018, Block Size: 4194304, Block Num: 1, Ops: 72003616768 (A)
LOG NOTE: 2020-11-05 17:46:25, Disk, Foi especificado um dispositivo inexistente. (433)
LOG NOTE: 2020-11-05 17:46:25, Disk, Disk Error (N: Error while writing to the disk in Cycle 17 with pattern Sequential data pattern
WARNING: 2020-11-05 17:46:34, Disk, M: Test file could not be created. Check access privileges.
LOG NOTE: 2020-11-05 17:46:34, Disk, Write File - File name: M:\BurnInTest test files\~bittestM00019
LOG NOTE: 2020-11-05 17:46:34, Disk, Foi especificado um dispositivo inexistente. (433)
LOG NOTE: 2020-11-05 17:46:34, Disk, Disk Error (M: Test file could not be created. Check access privileges. in Cycle 18 with pattern Sequential data pattern
WARNING: 2020-11-05 17:46:36, Disk, N: Test file could not be created. Check access privileges.
LOG NOTE: 2020-11-05 17:46:36, Disk, Write File - File name: N:\BurnInTest test files\~bittestN00019
LOG NOTE: 2020-11-05 17:46:36, Disk, Foi especificado um dispositivo inexistente. (433)
LOG NOTE: 2020-11-05 17:46:36, Disk, Disk Error (N: Test file could not be created. Check access privileges. in Cycle 18 with pattern Sequential data pattern
LOG NOTE: 2020-11-05 17:46:39, Status, Test run stopped

[David (PassMark)]

Looks like the SSD CORSAIR2 Force MP510 disappeared in the middle of the test.

Maybe a electrical problem or device driver?

Was this a one off problem or repeatable?

[samsam]

Hey David!

Thanks for the reply. I tried disconnecting the SSD, then reseating it, wiping Windows, then trying again.

The same issue occurred. I then tried it on another laptop, same issue. Is this SSD dead?

[David (PassMark)]

Yes, dead drive is the most likely explanation.