BurnIn Test 10.1 (1004) showed Disk is full on WIN11.26100.3476 (24H2)

[EricChu]

I used BurnIn Test 10.1 (1004) to do verification test to my PCIe SSD (1TB) ,

after test for 45hrs (expect 168hrs) , the tool showed "Error writing to disk -Disk is full" ,

Could you help me to check this issue ? if you need more information , plz let me know , thanks .


My PC info as below ,
M/B: Asus ROG MAXIMUS Z790 HERO BTF
CPU: Intel i5-14500
Drive: PCIe SSD 1TB
OS: WIN11.26100.3476 (24H2)

[David (PassMark)]

V10 is old now. So you could try V11, but the outcome might be the same in this case,

If you got an error about the disk being full, then likely the disk was full (unexpectedly). Did you check?

Likely it means some other software was also writing significant amounts of data to the disk at the same time as BurnInTest was running. That other task filled up the disk, leaving no space for the test data used by BurnInTest.

An example of how this might happen would be Windows downloading and installing a large update in the background. But it could be any software that uses significant disk space.

[EricChu]

Thanks for the reply , but I still have another question ,

before I used the same platform , same BurnIn tool but different OS (WIN11.22621.1992 , 22H2) , I never meet the Disk is full issue , it just happened when OS updated to 24H2 ,

it means BurnIn V10 have compatibility issue with OS 24H2 or other situations ? please confirm that , thanks .

[David (PassMark)]

We don't think it is a question of compatibility. As previously noted. If you got an error about the disk being full, then likely the disk was full (unexpectedly).

Likely it means some other software was also writing significant amounts of data to the disk at the same time as BurnInTest was running. That other task filled up the disk, leaving no space for the test data used by BurnInTest. Or you have set a quota for disk space for the current user. This could happen with any version of Windows.

This error isn't new to Windows 2024H2. Here is a post from 22 years ago on Windows 2000.
https://forums.passmark.com/burninte...-is-full-error
and even then the cause of the disk full error, was a full disk. If you want to get to the bottom of it some investigation is required on your side.