DirectIO - Bluescreen issue on Lenovo

[aquartar]

Thanks for the logs.

We made a slight fix. Can you give this build a try:
https://www.passmark.com/temp/petst-11.4.1000-DIO.3.exe

Same crash -- logs attached

[keith]

Same crash -- logs attached

Thanks for the logs. We have made another attempted to workaround:
https://www.passmark.com/temp/petst-11.4.1004-DIO.4.exe

[aquartar]

Thanks for the logs. We have made another attempted to workaround:
https://www.passmark.com/temp/petst-11.4.1004-DIO.4.exe

I noticed the 1006 build that went live - is this DIO.4 different?

[David (PassMark)]

Yes it is different. Build 1006 was confirmed to fix the issues on a couple of different Lenovo machines. But it seems there are still a couple of others, like yours, that have an issue.

You said this was a "Lenovo X1 Carbon Gen 11 we got as a seed device from Lenovo".
Can you go back to Lenovo and ask them to do some testing on this particular laptop. As the behaviour is different from their other Laptops. Maybe it is some incorrect BIOS setting. I assume if this was a seed device we can't buy this exact model yet?

The 1006 build was tested on the following Lenovo machines before release and worked OK

T470 Intel - Win10
T490 Intel - Win10
T14s Gen 1 Intel - Win10 and 11
T14s Gen 1 AMD - Win10 and 11
T14s Gen 2 Intel - Win10 and 11
T14s Gen 2 AMD - Win10 and 11
T14s Gen 3 AMD - Win10 and 11
L13 Yoga Thinkpad Intel - Win11

[keith]

I noticed the 1006 build that went live - is this DIO.4 different?

We made an another attempted workaround by avoiding PCI access for this i7-1365U CPU / chipset when running in Win 10.
Can you give this build a try:
https://www.passmark.com/temp/petst-11.4.1006-DIO.5.exe

[aquartar]

We made an another attempted workaround by avoiding PCI access for this i7-1365U CPU / chipset when running in Win 10.
Can you give this build a try:
https://www.passmark.com/temp/petst-11.4.1006-DIO.5.exe

Hi Keith - I apologize - I've been off work for a few days and hadn't checked the post in a while. I'll let you know this week.

[jordanhawk]

We made an another attempted workaround by avoiding PCI access for this i7-1365U CPU / chipset when running in Win 10.
Can you give this build a try:
https://www.passmark.com/temp/petst-11.4.1006-DIO.5.exe

I am unfortunately having the same issue with a Microsoft Surface Laptop 5.. Is there a fix for this yet? It starts to read CPU info and then bluescreens with the exact same error. I have tried uninstalling and reinstalling several times with no luck.

[David (PassMark)]

jordanhawk,

Can you post the debug log files from the Surface Laptop
https://www.passmark.com/support/per.../debug-log.php

[aquartar]

We made an another attempted workaround by avoiding PCI access for this i7-1365U CPU / chipset when running in Win 10.
Can you give this build a try:
https://www.passmark.com/temp/petst-11.4.1006-DIO.5.exe

Keith - we ended up giving this device to a user for testing, and I just got it back in hand. This build seems to have helped.

[DTX2023]

Hello all,
Is there an updated build for this problem?
We're getting directio64.sys BSOD with Supermicro X13SEi-TF motherboards.
Other apps are running fine.
OS is Win 11 23H2.
Thanks,
Nic.

[David (PassMark)]

Can you

#1
For that Supermicro system can you confirm if any or all of these settings are on in BIOS
Enhanced Windows biometric security
Secure Devices (SDEV) ACPI table
Virtualization-based Security (VBS)

#2
Can you also post a photo of the BSOD. Or use Nirsoft BSOD viewer to get the data from the pervious BSOD.

#3
Let us know what version of PerformanceTest you are using and post debug logs for PerformanceTest
See,
https://www.passmark.com/support/per.../debug-log.php