If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.
Announcement
Collapse
No announcement yet.
It's show "A driver cannot load on this device" when install BurnIn on SV2 OS.
Presumably you're talking about the upcoming Windows 11 update 22H2?
First check you are using the latest version of BurnInTest, if so they may have tweaked some of the driver protection settings.
Once the update is released properly we'll check it out, in the meantime you can try turning off the memory integrity setting as this is the most likely cause.
We still can find the same symptom by using BurnIn v10.1.1004 on 22H2 RTM OS.
Base on 22H2 requirement, the memory integrity need to keep enable, does PassMark have target date to fix this this symptom?
Thanks.
We've confirmed there is an issue with the Windows 11 update 22H2 causing the device driver not to load. Potentially it's due to the digital signature, despite being OK and valid Windows seems to be flagging it as unsigned.
We're looking into getting the driver resigned despite there being no changes to it.
The Windows 11 22H2 release has broken device driver signing in some way. We've had some correspondence with Microsoft where they have admitted it seems to be an issue in the 22H2 builds.
We were able to get our driver working by having it re-signed by Microsoft but it will only work in 22621/22622.436 (the previous 22H2 revisions don't work).
Currently, even with the latest OS Win11 22H2 22621.1702, this message " A driver cannot load on this device" may still appear.
Does passmark have any suggestion?
Thanks for your prompt reply.
Here provide the screenshot for you to refer.
After disabling 'Core Isolation > Memory Integrity', this windows " A driver cannot load on this device" no longer appears. F/R: 0/20.
Looks like its trying to load the older driver for some reason.
Can you run BurnInTest in debug mode (with Memory Integrity back on): https://www.passmark.com/support/bitdebug.php
Reproduce the error and send us the generated logs.
Simon (PassMark)
We have tested in debug mode again and provided the dump file to help@passmark.com.
We would like you kindly help analyze the dump and give some advise, thanks.
Comment