Solved

WaitForSingleObject crash

Posted on 2013-06-28
4
1,186 Views
Last Modified: 2016-02-25
I have a windows service (running on XP) which has run for years until recently, whereby the service crashes on a particualr machine when calling

      DWORD waitErr = WaitForSingleObject(hClient,INFINITE);

where I can confirm at time of calling that hClient is not null.

      hClient = CreateThread(0, 0, (LPTHREAD_START_ROUTINE)ClientThread, 0, 0, &clientThreadID);
      
I cannot even wrap a try/catch around it, as it blows as soon as WaitForSingleObject is called.

The only error I can find is in the Windows Event logs:
Faulting application myservice.exe, version 3.20.0.0, faulting module swi_ifslsp.dll, version 3.2.100.0, fault address 0x0000349a.

swi_ifslsp.dll is reported as part of sophos AV products, however I have disabled all services relating to sophos and the error still occurs.

How can I resolve this implosion?.
0
Comment
Question by:brenlex
  • 2
4 Comments
 
LVL 86

Expert Comment

by:jkr
ID: 39284610
Can you check if that DLL is listed under 'AppInit_DLLs' as described in http://support.microsoft.com/kb/197571 ("Working with the AppInit_DLLs registry value")? If so, it is probably used for API hooking and that mechanism interferes with your wait operation. Try to rename the registry entry to prevent it from loading.
0
 
LVL 33

Expert Comment

by:sarabande
ID: 39294121
it is more likely that the client thread function is crashing. a crash in the thread would also crash the main thread depending on the severity. also if the thread corrupted some memory it could have effects on the call stack and that could spoil the call of WaitForSingleObject.

you could add a sleep at the begin of the thread proc such that the wait call in the main thread happens earlier. if it crashes after sleep you might add log messages yourself to the client thread to narrow the issue.

note, if the machine is a multi-core or even multi-processor computer, your issues may come from code that is not thread-safe. if it runs ok before, it could be due by other factors such that the machine is more or less busy.

Sara
0
 

Accepted Solution

by:
brenlex earned 0 total points
ID: 39299798
In the end it was indeed the Sophos LSP dll causing the problem!

Command line: netsh winsock show catalog highlighted its presence as part of a Web Intelligence service.

Customer disabled and problem disappeared.
0
 

Author Closing Comment

by:brenlex
ID: 39309772
Specific to Sophos.
0

Featured Post

Is Your Active Directory as Secure as You Think?

More than 75% of all records are compromised because of the loss or theft of a privileged credential. Experts have been exploring Active Directory infrastructure to identify key threats and establish best practices for keeping data safe. Attend this month’s webinar to learn more.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

For both online and offline retail, the cross-channel business is the most recent pattern in the B2C trade space.
When you start your Windows 10 PC and got an "Operating system not found" error or just saw  "Auto repair for startup" or a blinking cursor with black screen. A loop for Auto repair will start but fix nothing.  You will be panic as there are no back…
The goal of this video is to provide viewers with basic examples to understand opening and writing to files in the C programming language.
The viewer will learn how to use the return statement in functions in C++. The video will also teach the user how to pass data to a function and have the function return data back for further processing.

862 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

29 Experts available now in Live!

Get 1:1 Help Now