Some issues about USB3.2 test and DX12 3D test in BIT

[Shimmer]

Dear guys,
We met some issues during the burnintest,they are not in the same project.
1、The first question is that when we use a 1T disk to test USB3.2,the burnin software will occasionally freeze at the unresponsive interface at 0 degrees and 40 degrees.However, using loopback 3.0 can pass it,we can also accept this solusion.

Previously a colleague's explanation was that "the burnin software enumerates storage devices.Some disk device boards are not fully compatible, causing the enumeration to get stuck, which is manifested as software not responding",but no detailed theoretical basis was provided.Now I have encountered the same problem. I hope you can help provide a principle analysis for reference in the future.
The software and OS versions we have tried are listed:

BurnInTest Professional edition V10.2 (32 & 64 bit) build 1009
BurnInTest Professional edition V9.0 (32 & 64 bit) Build 1014
BurnInTest Professional edition V10.2 (32 & 64 bit) Build 1015
BurnInTest Professional edition V10.2 (32 & 64 bit) Build 1016
BurnInTest Professional edition V11 (x86 -64 bit) Build 1016
BurnInTest Professional edition V9.0 (32 & 64 bit) Build 1014
OS:
Win10_1909
Win10 21H2 IOT


2、The second question is that when we test DX12 with the newest BIT V11 and BIT V10,an error occus.But when we test DX9 with BIT V10 ,it can pass.The solution we can also accept.I'd like to ask you to help provide some professional analysis.Thanks for your help
By the way, this issue occurs in projects equipped with DDR5:



***************
DETAILED EVENT LOG
******************
INFORMATION: 2025-12-01 11:15:12, Disk, D: Butterfly seeking skipped for this disk (SSD/NVMe)
INFORMATION: 2025-12-01 11:17:17, Disk, E: Butterfly seeking skipped for this disk (SSD/NVMe)
INFORMATION: 2025-12-01 11:25:42, Disk, G: Butterfly seeking skipped for this disk (SSD/NVMe)
INFORMATION: 2025-12-01 11:32:52, Disk, D: Butterfly seeking skipped for this disk (SSD/NVMe)
SERIOUS: 2025-12-01 11:33:55, 3D Graphics, An error occured during the DX12 3D test
LOG NOTE: 2025-12-01 11:33:55, 3D Graphics, Unable to run the DirectX 12 Test (exit code 0xC0000409), your card may not support this version of DirectX or the D3D12Test64.exe executable is being prevented from launching by an external program(eg security or anti - virus software).
LOG NOTE: 2025-12-01 11:41:45, Status, Summary results written to log file (3)

[David (PassMark)]

we use a 1T disk to test USB3.2,the burnin software will occasionally freeze at the unresponsive interface at 0 degrees and 40 degrees.However, using loopback 3.0 can pass it,we can also accept this solusion.

Yes, we suggest using our USB loopback plugs for testing USB ports.
By using a external hard disk for testing a USB port you are never sure if any failure is due to the USB port failing or the external HDD failing. You'll probably find your HDD isn't rated to work below 0C or above 40C. Also if there are errors on the HDD, Windows can attempt to read / write the same sector many times with a timeout each time. This can result in a system freeze. If you were using a SSD instead of a a HDD, then these have write limits after which they will start to fail.

the burnin software enumerates storage devices.Some disk device boards are not fully compatible, causing the enumeration to get stuck

Yes, storage devices are enumerated (or to be more precise we ask Windows what drives it knows about). We are not aware of any disk devices that are supported by Windows and not supported by BurnInTest. We are also not aware of any freezes during enumeration of working disk devices. But as noted above, some devices that have an ongoing hardware failure, or are connected via unreliable networking can be very slow to respond. They should timeout eventually however.

when we test DX12 with the newest BIT V11 and BIT V10,an error occus

Video card device drivers crashing under high load or low RAM conditions is fairly common. Plus there are a lot of old (and even new) video drivers with bugs.
The DX12 test is a lot higher load than the older DX9 test.

[Shimmer]

Hi David,
Thanks for your explanation,they are useful for our issues,I will use this as a reference to resolve the bug.

Therefore,if possible---I'd like to obtain a more detailed, principle-level understanding of the differences between DX12 and DX9 testing,in addition,the differences between loopback and disk of USB3.2 testing.
Tks again.

[David (PassMark)]

the differences between loopback and disk of USB3.2 testing.

See my previous post.

There are also some details in the User's Guide as to how the tests work.