PM 11 (1019) BSOD on app startup (Threadripper PRO 597 5WX)

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • wvb
    Junior Member
    • Sep 2024
    • 2

    #1

    PM 11 (1019) BSOD on app startup (Threadripper PRO 597 5WX)

    Repeatable BSOD when starting PM 11 (1019) on a Dell equipped with an AMD Ryzen Threadripper PRO 5975WX CPU. PM 10 worked without issues.

    I'm happy to stick with PM 10 but figured it might be helpful to report the behavior. Let me know if you'd like more information.
  • David (PassMark)
    Administrator
    • Jan 2003
    • 11092

    #2
    Hi,

    Thanks for the post. We aren't aware of any issues with the current patch release.

    We did have an issue when running in a VM (now fixed).
    And another one on a couple of specific Lenovo machines. This was worked around.

    I note you are saying you have build 1019 in the title. Which should be the latest patch at the moment. But for anyone else can you check you have the latest patch release.

    Then can you post a debug log
    https://www.passmark.com/support/per.../debug-log.php

    Comment

    • wvb
      Junior Member
      • Sep 2024
      • 2

      #3
      Finally got around to collecting debug info. The latest, 11.1 build 1002, is exhibiting the same behavior. Sent info to help @ passmark Subject includes "wvb bsod"

      Comment

      • David (PassMark)
        Administrator
        • Jan 2003
        • 11092

        #4
        We are having a look at it.

        Comment

        • keith
          Employee
          • Oct 2010
          • 718

          #5
          Originally posted by wvb
          Finally got around to collecting debug info. The latest, 11.1 build 1002, is exhibiting the same behavior. Sent info to help @ passmark Subject includes "wvb bsod"
          Thanks for the logs.

          Since PerformanceTest v11, we added support for obtaining memory controller speed and timings which requires accessing hardware registers. However, recent Win 10/11 versions have added security mechanisms that prevent access to the registers for this particular somewhat rare CPU, resulting in BSOD.

          We've sent a debug build to attempt to workaround the issue.

          Comment

          Working...