Announcement

Collapse
No announcement yet.

Passmark BurnInTest "Parallel port" (LPT1) test fail on Win11 SV2 but pass on SV1.

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

  • Passmark BurnInTest "Parallel port" (LPT1) test fail on Win11 SV2 but pass on SV1.

    Passmark BurnInTest "Parallel port" (LPT1) test fail on Win11 SV2 but pass on Win11 SV1 (the same App and loopback). This seems App and OS compatibility issue. How to solve on Win11 SV2 ?

  • #2
    Where did you find a Win11 machine with a parallel port?

    Comment


    • #3
      My PC (Intel W580) still has LPT port.
      Click image for larger version

Name:	LPT.png
Views:	182
Size:	286.5 KB
ID:	54037

      Comment


      • #4
        Pretty sure the Intel W580 chipset doesn't have parallel port support.

        More likely whatever motherboard you have has some old SuperIO chip on it.

        Can you run just the parallel port test on this machine and collect the BurnInTest debug log.


        Comment


        • #5
          Originally posted by Jim Chen View Post
          Passmark BurnInTest "Parallel port" (LPT1) test fail on Win11 SV2 but pass on Win11 SV1 (the same App and loopback). This seems App and OS compatibility issue. How to solve on Win11 SV2 ?
          Can you please also check you are using the latest version of BurnInTest, the SV2 / 22H2 release of Windows caused a bunch of device driver issues that should be resolved in the latest version.

          Comment


          • #6
            BurnIn Test v10.2 log as attached.
            Attached Files

            Comment


            • #7
              Please update to the latest build (V10.2 build 1004).

              Comment


              • #8
                v10.2 build 1004 still fail. Log file is in attached.
                Attached Files

                Comment


                • #9
                  Thanks, our device driver is now loading correctly so it can see and access the port.

                  It seems other people have had similar issues with parallel access in Windows 11 22H2 though so I would say this is either a 22H2 bug as it's likely not much parallel port testing was done for the release or it's a similar issue to what we experienced where your parallel port might need another driver that is no longer loaded correctly by 22H2.
                  There may an event logged in the event viewer referencing the parallel port.

                  Comment

                  Working...
                  X