Weird AppCrash issue: Logitecg SetPoint crashes when Outlook launched

[Kari]

Weird AppCrash issue: Logitech SetPoint crashes when Outlook launched

These two, Logitech SetPoint 6.15 and Outlook 2010, should logically thinking have nothing in common. Short problem description:

Using Logitech bluetooth mouse, keyboard & mediapad combo, software and drivers SetPoint version 6.15. Working surprisingly good, using laptop's internal bluetooth radio instead of Logitech's Bluetooth dongle.

Each and every time I launch Outlook 2010, SetPoint crashes. In my case it means quite often, Outlook being my default email client. I have to manually relaunch SetPoint, and it works flawless, Outlook still running, until Outlook is closed and launched again. At this point, SetPoint crashes again and has to be relaunched.

After SetPoint crashes, I can still use my keyboard and mouse normally, only the special buttons and functions are disabled. For basic functions I don't need SetPoint. But because I have these devices precisely because of these extra features, it is not a desirable option to me. I'd rather solve this issue.

Weird, I have absolutely no idea why this happens. Any suggestions welcome.

Kari

Fault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: SetPoint.exe
P2: 6.15.6.0
P3: 4c253e05
P4: mfc90u.dll
P5: 9.0.30729.4148
P6: 4a5967eb
P7: c0000005
P8: 000000000009105c
P9: 
P10: 

Attached files:

These files may be available here:
d:\Users\Kari\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_SetPoint.exe_7ca78fd91b5f444cd75fd6ef1814db43f1695_0aba33ad

Analysis symbol: 
Rechecking for solution: 0
Report Id: bb51800e-038c-11e0-9d8e-001eecafca7e

 

[Golden]

Hi Kari,

I'm not sure this helps you, but just for more information for you in case it helps you track down the problem:

I use Logitech Setpoint 4.60.122 and Outlook 2010 without any issues. I use a Logitech backlit keyboard and Logitech MX518 mouse.

Hopefully someone can help you soon,
Golden

 

[Kari]

Thanks for your response, Golden, but I really don't want to go back to older versions of Setpoint. I had always connection problems and mouse sometimes behaving funny when using that old Setpoint.

 

[severedsolo]

Hi Kari, wow thats a doozy.

The only thing I can think of is that it has something to do with the "Email" button that comes on most keyboards. How are you launching Outlook? are you pressing the "Email" button on the keyboard or are you launching it manually (from the taskbar etc.)

Perhaps Outlook is not communicating with SetPoint correctly when SetPoint asks for the default Email Client? or more likely, Setpoint is not asking for it properly.

I assume your running the latest version of SetPoint?

Don't know if that helps, just an idea.

 

[Anak]

Kari,

What I've found so far:
From post #3

what is an access violation, a C0000005? This is the translated #GP code the fault handler raises, which the operating system displays as an 'Access Violation', whos numerical form is c thousand 5. Its the operating system telling you that a program has malfunctioned and tried to reference no mans land. It has nothing specific to do with any particular program, or a brand of software, this is straight from the CPU and kernel of the operating system.

what causes "Exception code: C0000005 ACCESS_VIOLATION"

 

[Kari]

This happens both when launching Outlook from Windows or keyboard. But thanks, there I have a clue at least, had not thought that Setpoint and Outlook indeed have something in common, the mail buttons both in my keyboard and mediapad.

Severed, I think you are on something here. The appcrash is because SetPoint Event handler; this event might have something to do with these mail buttons controlled with SetPoint.

 

[severedsolo]

Kari, it seems there is a Setpoint 6.20 available, it might be worth upgrading to see if that fixes it. A quick google suggests that that particular error code is quite common with Setpoint:

Download SetPoint 6.20 - FileHippo.com

 

[Bill2]

This thread seems to have some info that may help.

SetPoint and Outlook 2010 - Logitech Forums

 

[Kari]

Thanks, Bill, I had not seen that. Seems I'm not alone with this.

 

[OEM]

You might be able to (at the very least, if all else fails) setup a "task scheduler" to auto restart the Setpoint service. Pretty sure you can do that if it notices the service has stopped, it will have a setting in the task setup to auto start service when stopped.

 

[gregrocker]

Hi Kari -

I find that if I report the problem, Win7 will often return a Problem Solution - although not always right away and sometimes without cueing it in Action Center. I periodically type Solutions in Start Search box.

I only mention it because it appears you chose to Close the Program rather than Report It, which most Users do while not knowing that WIn7 is much more interactive than previous OS's.

Sometimes it will return a Solution even if you don't report it.

I have always avoided Setpoint due to similar problems, but understand why you need it if you want the extra features. Sometimes a newer or older version will help.

 

[Kari]

Greg, I normally always report an appcrash. This SetPoint, I already have a routine: first time every day it happens, I click Check online for solution and report it, then rest of the day I just click Close. I think I've "searched online solution" and reported it now at least hundred times (this has been happening a couple of months now)

 

[severedsolo]

Kari did you try version 6.20 which I linked to in a previous post?

 

[Kari]

Yes, sorry I forgot to mention that. I tried 6.20, the appcrash is still there.

EDIT: Again, I forgot to mention something: your link was for an x86 version, but I found x64 from Logitech.

 

[Kari]

I'm so fed up with issue I have to bump the thread.

Nothing I can find on the net, especially on Logitech support helps. I've tried older versions of SetPoint, everything I can think of, even disabling Mail button on keyboard and assigning another function to that (in case this issue is related to that?).

Once again, a short problem description: Logitech mouse and keyboard work fine without SetPoint and Logitech drivers, but they only have basic functions. To be able to use extra buttons and features I need SetPoint. When I launch Outlook 2010, SetPoint crashes every single time. Outlook and SetPoint can co-exist if I after launching Outlook relaunch Setpoint when it has crashed, which always happens within 10 to 20 seconds after launching Outlook.

Kari

 

[niemiro]

Hello Kari!

A few things:

1: Does Setpoint crash if you launch Outlook in Safe Mode/No addons mode?

2: Do you have the Business Contact Manager (BCM) installed?

3: I notice "Debug the Program" is an option. Do you have Visual Studio installed? Which version? Is anything of yours (for example, DirectX) set to Debug Mode rather than Release Mode, as I have seen just a few issues arising from this less tested of modes.

Thanks!

Richard

 

[Kari]

Thanks for replying, Niemiro.

1: Yes
2: Yes
3: Visual Studio 2010 Premium installed. As far as I know, no apps set to Debug Mode.

One workaround would be to have Outlook start automatically when Windows is booted, then launch SetPoint manually when Outlook is already running or set it to start delayed to assure Outlook already runs. As I have mentioned, SetPoint has no problems to stay stable when it is launched when Outlook is already running. This works but being only a workaround I really would like to find a solution.

Kari