Jump to content
Sign in to follow this  
ImmutableOdd

SAS won't complete scan except in safe mode

Recommended Posts

I'm running SAS Free 4.46.1000 (def ver Core: 6000 Trace:3812) on a ThinkPad T21 laptop. I run SAS on several other PCs without issue.

I recently installed SAS on this ThinkPad and it consistently hangs at one of two points during the memory scan phase. These hang points are:

C:\WINNT\SYSTEM32\LTMSG.EXE

C:\PROGRA~1\UTILIT~1\TP98TRAY.EXE

Even when I exclude these paths in SAS the scans will hang indefinitely at the same points. For example, at the 'Excluded folders To Scan' screen in SAS if I navigate to C:\Program Files\Utilities\ and add this path to the folder exclusion list the next scan attempt still hangs at C:\PROGRA~1\UTILIT~1\TP98TRAY.EXE just as before.

Does anyone have any thoughts on this matter? It doesn't seem reasonable that I should have to boot into safe mode each time I wish to run an SAS scan.

Thanks in advance.

Share this post


Link to post
Share on other sites

I'm running SAS Free 4.46.1000 (def ver Core: 6000 Trace:3812) on a ThinkPad T21 laptop. I run SAS on several other PCs without issue.

I recently installed SAS on this ThinkPad and it consistently hangs at one of two points during the memory scan phase. These hang points are:

C:\WINNT\SYSTEM32\LTMSG.EXE

C:\PROGRA~1\UTILIT~1\TP98TRAY.EXE

Even when I exclude these paths in SAS the scans will hang indefinitely at the same points. For example, at the 'Excluded folders To Scan' screen in SAS if I navigate to C:\Program Files\Utilities\ and add this path to the folder exclusion list the next scan attempt still hangs at C:\PROGRA~1\UTILIT~1\TP98TRAY.EXE just as before.

Does anyone have any thoughts on this matter? It doesn't seem reasonable that I should have to boot into safe mode each time I wish to run an SAS scan.

Thanks in advance.

Update:

I've discovered that this laptop loads 2 instances of rundll32.exe and that if I kill one of them the SAS scans will finish without a hitch. Both instances of rundll32.exe load each time the laptop is booted and each one consumes different amounts of memory. I don't know why there are two instances of this item running but I do know that simply killing one of them allows me to use the SAS scan function successfully.

Share this post


Link to post
Share on other sites

Please submit a Customer Service Request at our support page, Ill get a diagnostic over your way so we can figure out your infection.

Thanks for the reply.

Actually, it's not an infection. I did some troubleshooting relating to the dual rundll32.exe instances and discovered that they are both loaded from the HKLM run key. The relevant startup items at that location are as follows:

"SoundFusion"="RunDll32 cwcprops.cpl,CrystalControlWnd"

"BMMGAG"="RunDll32 C:\\PROGRA~1\\ThinkPad\\UTILIT~1\\pwrmonit.dll,StartPwrMonitor"

Eliminating either of those respective items from the run key will result in the corresponding instance of rundll32.exe in task manager being nonexistent. However, deleting the first item (ie, the one that loads the SoundFusion tray icon - SoundFusion is the audio driver that came with the ThinkPad) makes no difference as far as the SAS scan stalls - the scans still stall at the same points. But deleting the BMMGAG item from the run key (ie, the thinkpad power monitor feature) results in unimpeded SAS scanning.

So unless there's another fix, I'll simply have to stop the power monitor rundll32.exe process prior to scanning with SAS each time. Additionally, I checked and there are no other files named rundll32.exe on the HDD other than the one at C:\WINNT\System32\ and a backup at C:\WINNT\System32\dllcache.

Share this post


Link to post
Share on other sites

I'd submit a Customer Support ticket and let the gurus figure out what the problem is. You should not have to shut down your computer's power monitor to get SAS to complete its scan. Let the gurus figure out how to make SAS work properly with your computer's software configuration. :wink:

Share this post


Link to post
Share on other sites

You should not have to shut down your computer's power monitor to get SAS to complete its scan.

I agree. But I will say that it's markedly better than being required to reboot into safe mode to run the scans :wink:

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

×
×
  • Create New...