How to diagnose sudden onset of crashes every time I pull data from my CMS50F?

[MrPete]

I've been using OSCAR to read and display Oximeter data for several years. Once I got the hang of it, no issues. NEVER a crash.

This week it was time to do more readings....

...and now, I can't finish reading the data without OSCAR simply disappearing via a hard crash.

In the UI I see it begin reading...then it loses sync... then poof, it's gone.

Event Viewer says this:

Code:

Faulting application name: svchost.exe_FrameServer, version: 10.0.19041.546, time stamp: 0x058e175a
Faulting module name: OpenCL.dll, version: 2.2.8.0, time stamp: 0x5f217308
Exception code: 0xc0000005
Fault offset: 0x0000000000005c98
Faulting process id: 0x5330
Faulting application start time: 0x01d804a4de5e065d
Faulting application path: C:\WINDOWS\System32\svchost.exe
Faulting module path: C:\WINDOWS\SYSTEM32\OpenCL.dll

Any thoughts? Anything I can do to help track this down? I'm a reasonably experienced tech guy (HW/FW/SW)

Thanks!

[Ratchick]

I'm not sure about the OSCAR crash, I will leave that to the people far more familiar with the underside than I am.

As an interim workaround, have you tried saving the data to your computer as an SpO2 file with the Contec software, and then uploading to OSCAR from that file, instead of pulling it from your pulse ox directly?

[Crimson Nape]

You might have had a systems update that broke something. If a PC reboot hasn't corrected the problem, then my next thought is to try and change the graphics driver, from "Desktop OpenGL" to "Software Engine". You can either go to File > Preferences > General > Graphics Engine to set this parameter. Or, hold down the <Shift> key when starting OSCAR.

- Red

[GuyScharf]

If a PC reboot hasn't corrected the problem, then my next thought is to try and change the graphics driver, from "Desktop OpenGL" to "Software Engine".

Or, if the graphics engine is already set to "Software Engine," try changing it to "Desktop OpenGL."  That sometimes fixes weird problems on Windows.

[Crimson Nape]

Good catch!

[MrPete]

I'm not sure about the OSCAR crash, I will leave that to the people far more familiar with the underside than I am.

As an interim workaround, have you tried saving the data to your computer as an SpO2 file with the Contec software, and then uploading to OSCAR from that file, instead of pulling it from your pulse ox directly?

Woah. Never tried the Contec SW to be honest.
If nothing else works I will try that...

[MrPete]

Changing the graphics driver a few times DID kick it to stop crashing. That's the good news.

Along the way, I found some anomalies, maybe bugs:

1) Starting by holding down shift does change the driver. BUT: it changes it *permanently*. I had to get back to the prefs setting in the application to reset it

2) Switching to software driver was essentially useless. Here are things that were different when starting in Software Driver for graphics (either via a pref change directly or using shift. I switched back and forth several times to verify:

- On restart after shifting to Software Driver, the app UI is completely missing: just OSCAR 1.3.0 in the top left corner
- If I then restart and hold down shift, I get a UI... but:
   - on the right it says "Profile: none" even though my profile is showing
   - I can't select the profile
   - The menus are grayed out
   - If I try to go to File->Preferences it says "please select a profile first"
   - If I use File->Edit Profile, it lets me review the profile info (it IS all there?!). 
- Once I save the profile (no changes, just save), then:
   - I still can't select the profile
   - But now I can enter File->Preferences, and set General->Graphics Driver back to openGL

And THEN... it restarts correctly and everything works as it should, including no more crashes.

Bottom line: a rather strange and fiddly sequence!

I assume at least some of the above is NOT what's intended.

Oh, one more tidbit. WHile in the (nonworking) "Software driver" mode, the debug log is endlessly filled with these lines:
228161: Warning: composeAndFlush: makeCurrent() failed
228162: Warning: composeAndFlush: makeCurrent() failed
228163: Warning: composeAndFlush: makeCurrent() failed
228164: Warning: composeAndFlush: makeCurrent() failed
...

I hope that helps a bit.

Blessings,
Pete

[GuyScharf]

1) Starting by holding down shift does change the driver. BUT: it changes it *permanently*. I had to get back to the prefs setting in the application to reset it

For better or worse, that is what it is designed to do.

2) Switching to software driver was essentially useless. Here are things that were different when starting in Software Driver for graphics (either via a pref change directly or using shift. I switched back and forth several times to verify:

....
Thanks for the details. The software driver is clearly not working with the recent versions of Windows.

Oh, one more tidbit. WHile in the (nonworking) "Software driver" mode, the debug log is endlessly filled with these lines:
228161: Warning: composeAndFlush: makeCurrent() failed

We know. That's one of the symptoms of a malfunctioning software graphics engine.

We have some work to do to straighten out this problem.

[MrPete]

We have some work to do to straighten out this problem.

Happy to help a bit with debugging/diagnostics. In the real world I'm a multi-decade vexperienced SW/FW/HW dev/architect specializing in breaking stuff.

[Gideon]

Happy to help a bit with debugging/diagnostics. In the real world I'm a multi-decade vexperienced SW/FW/HW dev/architect specializing in breaking stuff.

Shoot me a PM and tell me what platforms you are familiar with.  Interested in Development or Testing (aka breaking stuff).