Announcement

Collapse
No announcement yet.

DirectIO - Bluescreen issue on Lenovo

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • #16
    Originally posted by keith View Post

    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
    Attached Files

    Comment


    • #17
      Originally posted by aquartar View Post


      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

      Comment


      • #18
        Originally posted by keith View Post

        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?

        Attached Files

        Comment


        • #19
          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

          Comment


          • #20
            Originally posted by aquartar View Post

            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

            Comment


            • #21
              Originally posted by keith View Post

              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.

              Comment


              • #22
                Originally posted by keith View Post

                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.

                Comment


                • #23
                  jordanhawk​,

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

                  Comment


                  • #24
                    Originally posted by keith View Post

                    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.

                    Comment


                    • #25
                      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.

                      Comment


                      • #26
                        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

                        Comment


                        • #27
                          I have a lenovo P520c, I launch the application, it gets to the part where its reading system info, when it hits the memory part it crashes. Directlo.sys error. After I restart, and try to reopen it, it gives me startup error #4

                          I dont know where to locate these logs.

                          Comment


                          • #28
                            Originally posted by MurderMittens View Post
                            I have a lenovo P520c, I launch the application, it gets to the part where its reading system info, when it hits the memory part it crashes. Directlo.sys error. After I restart, and try to reopen it, it gives me startup error #4
                            If you are not using the latest release and build of PerformanceTest, make sure to update to the newest.

                            PassMark Performance Test download page

                            For Startup Error 4, refer to the following forum post, where it mentions V9, swap it with V11.

                            Startup error number: 4 - what is it? - PassMark Support Forums

                            Originally posted by MurderMittens View Post
                            I dont know where to locate these logs.
                            If there was a crash dump created, it would be created in the Documents folder, e.g. "C:\Users\<Username>\Documents\PassMark\Performanc eTest11". The other logs are not automatically created. To have PerformanceTest start with debug logging, see https://www.passmark.com/support/per.../debug-log.php

                            Comment


                            • #29
                              Hello,

                              I have the same problem with BSOD (SYSTEM_SERVICE_EXCEPTION) on the DirectIo64.sys driver​ every time I run the HDD performance test.
                              I'm using the latest release and build of PerformanceTest and Windows 11.

                              I did a quick research, it fails on the RDMSR instruction (DirectIo64 + 0x12d5). The DirectIo64.sys tries to read from MSR 0x300 and gets a #GP exception. I checked the Intel docs, 300H is MSR_SGXOWNEREPOCH0. I guess this is related to Intel SGX (Intel Software Guard Extensions).

                              Comment


                              • #30
                                Joe,

                                Can you provide some additional details. What hardware are you using?

                                Can you provide a debug log
                                https://www.passmark.com/support/per.../debug-log.php

                                Does the problem happen 100% of the time? Do any of the HDD tests trigger the problem, or just one?
                                Note that this issue isn't identical to the one initially reported (as that had nothing to do with the HDD test).

                                Update: We don't think 300H is MSR_SGXOWNEREPOCH0. But there was an issue similar to this on Skylake CPUs that was fixed a couple of weeks ago. We'll have a public patch shortly. I don't know if it is your issue, as no hardware details were provided.

                                Comment

                                Working...
                                X