OSCAR Crash on Oximeter Import

[TiredUser]

Hello,

New to Oscar. I have imported my sleep sessions for two nights currently. (Oximeter only. Trying to see if it's worth paying for a doctor or I don't have any problems.) I am currently trying to import my third night and when I go to import it goes to 94% (sometimes 95%) pauses for a second then crashes. I am using a Contec CMS50DA+. Windows 10 Pro. Oscar 64bit.

This is the message that I get in Windows Event Viewer. Any ideas on what to do to resolve or a way to download the information and manually import into Oscar? Thanks!

Code:

Faulting application name: OSCAR.exe, version: 1.1.0.0, time stamp: 0x5e9a1b19
Faulting module name: Qt5Core.dll, version: 5.12.8.0, time stamp: 0x5e83606f
Exception code: 0xc00000fd
Fault offset: 0x0000000000326f76
Faulting process id: 0x1e70
Faulting application start time: 0x01d63428d0dc5c6a
Faulting application path: C:\Program Files\OSCAR\OSCAR.exe
Faulting module path: C:\Program Files\OSCAR\Qt5Core.dll
Report Id: 08282d3f-a963-4b19-a23b-226f512f0fad
Faulting package full name:
Faulting package-relative application ID:

Code:

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

Problem signature:
P1: OSCAR.exe
P2: 1.1.0.0
P3: 5e9a1b19
P4: Qt5Gui.dll
P5: 5.12.8.0
P6: 5e8362b4
P7: c00000fd
P8: 000000000043e496
P9:
P10:

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE646.tmp.mdmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE712.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE723.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE732.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE753.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_OSCAR.exe_127bd5abe88285a9abc26156b8fa39c8478988_86503205_9fbe7043-a652-4694-b144-8700c66c6df9

Analysis symbol:
Rechecking for solution: 0
Report Id: e8565cbc-0896-4c0a-bf04-b1723568f529
Report Status: 268435456
Hashed bucket: 289baf6cc09ece1af72e87905f36b0a7
Cab Guid: 0

[Crimson Nape]

Are you importing directly or from the SpO2 file? Also, have you tried re-booting your PC?

[TiredUser]

Directly from the device. I have just rebooted and tried again but got the same thing.

[Crimson Nape]

In an effort to try to isolate the problem, can you try importing the SpO2 file? (. . . I realize you might not have the SpO2Assasiant program loaded on your PC.)

[TiredUser]

It took me a bit to track down the SP02 program. I was able to load it up and then manually import into Oscar. When I try the import again it still fails.

[GuyScharf]

If you are willing to send us a zipped copy of your SpO2 data file, we can see if we can reproduce your failure. Please name the zip file with the login name that you use here so we know who the zip file is from.

Then direct your browser to Bonjour's dropbox folder for diagnostic data, https://www.dropbox.com/request/6VeFzBXa4qZ37EgphL5b and follow the directions for uploading your file.

Please reply to this message if you upload a file so I know to look for it.

The OSCAR Team will use your file only for analyzing your problem and for developing OSCAR.  We will never pass your data on to anyone outside of the team.

[Crimson Nape]

A couple of other thoughts; Did you use the USB cable that came with the CMS-50DA+?  Which Oximeter type did you select, or did you try both?  Also, did you try using a different USB port on your PC?  The reason I'm asking all this is that the CMS-50 importer has been pretty stable.

[TiredUser]

If you are willing to send us a zipped copy of your SpO2 data file, we can see if we can reproduce your failure. Please name the zip file with the login name that you use here so we know who the zip file is from.

Then direct your browser to Bonjour's dropbox folder for diagnostic data, and follow the directions for uploading your file.

Please reply to this message if you upload a file so I know to look for it.

The OSCAR Team will use your file only for analyzing your problem and for developing OSCAR.  We will never pass your data on to anyone outside of the team.

Done. Just to expand a little bit. I am able to import this SpO2 file. I do have to close and reopen OSCAR to have it show up in my days. But just out of curiosity, I tried the import again from the device and that failed.

A couple of other thoughts; Did you use the USB cable that came with the CMS-50DA+?  Which Oximeter type did you select, or did you try both?  Also, did you try using a different USB port on your PC?  The reason I'm asking all this is that the CMS-50 importer has been pretty stable.

I was using the cable that came with it and out of curiosity I changed the cable but same thing. I had already tried different usb ports this morning but tried again and same thing. (The SpO2 Assistant did work to get the data so thanks for pointing me in that direction.) I had tried changing the device type but it just says waiting for device to upload and there isn't an upload option on it so I went back to the default. Here is a short clip of what it's doing and all of the settings.

https://www dropbox com/s/ygnt5jns5k51e2k/oscar%20crash.mp4?dl=0

[Crimson Nape]

Unfortunately, that isn't a shared link.

[GuyScharf]

Done. Just to expand a little bit. I am able to import this SpO2 file. I do have to close and reopen OSCAR to have it show up in my days. But just out of curiosity, I tried the import again from the device and that failed.

Sorry, I misunderstood your message that importing from the SpO2 file failed the second time.  But apparently you were referring to direct import from the device.

I'll look at it anyway to see if there is anything interesting to see.