Process Lasso 3.60 x64 problem

Started by af4t, June 13, 2009, 07:51:44 AM

Previous topic - Next topic


I am running 3.60.5 x64 on Vista Ultimate (x64) .... which regularly pops up a message saying that the Process Lasso Core Engine has stopped working, with these details:

Problem signature:
  Problem Event Name:   BEX64
  Application Name:   processgovernor.exe
  Application Version:
  Application Timestamp:   4a328f7c
  Fault Module Name:   StackHash_8f43
  Fault Module Version:
  Fault Module Timestamp:   00000000
  Exception Offset:   0000000000000000
  Exception Code:   c0000005
  Exception Data:   0000000000000008
  OS Version:   6.0.6002.
  Locale ID:   1033
  Additional Information 1:   8f43
  Additional Information 2:   fa64aa6fb4a701f3d2f7c7b5dd0aa254
  Additional Information 3:   b9ce
  Additional Information 4:   892941c528917ee73881a3005c34e0e1

I will get this message usually within the first minute after system start, then again periodically after restarting the governor with the tray icon.  It has been seeming to mitigate the problem if I import the digital signature certificate for processgovernor.exe, but this doesn't ever last past rebooting.

There are usually two users logged into the system, but this doesn't seem to make a difference, it happens with only one (myself) logged in also.  It happens with processgovernor.exe having normal rights, highest rights, or installed as a system service, I have tried all three options.

Vista Ultimate x64 is installed as a dual boot system with Vista Home Premium x32 ... I never have this issue with the 32-bit OS.

Wish I had more technical expertise to give you additional details ....

Any ideas how to stop this annoying behavior?


Jeremy Collake

Thank you for reporting this anomaly. I am very concerned about it, as a crash like this is surely affecting other users. My primary development system is now running an x64 OS, so the x64 build does get pretty well tested (as does the x32 build). I need to find out what is different on your system than in my test beds. The crash may be some timing issue, but this seems less likely as I'd surely have seen it myself at least once, and you would surely not see it so frequently.

Can you please post your configuration file and log? Alternatively, you can email them to The path to them is listed in the about box. This may give me some clue as to what is going on.

Thanks again for the report, and I appreciate any time you're able to give in helping track down the cause.
Software Engineer. Bitsum LLC.



I will let it happen a few more times to gather evidence for you.

It did happen twice last night, I did not have system services excluded from Pro Balance and the crash happened right after adjustments to svchost.exe ... now have system services excluded from Pro Balance to see what happens.

Jeremy Collake

Great, I appreciate your willingness to help investigate. Please keep me updated.
Software Engineer. Bitsum LLC.

Jeremy Collake

For readers: This problem was tracked down to customized CPU Throttling on an application. A fix is still pending, but this errata should not affect many users at all.
Software Engineer. Bitsum LLC.