Topic: Digicheck Auto Close

Hi i have a UFX+ using thunderbolt on Windows 10, whenever i run digicheck it asks for the temp folder and when i press ok it just auto closes. Am i missing something? I've tried different directories like desktop, other drives, running as administrator etc but to no avail.

2

Re: Digicheck Auto Close

You have hard drives in the multiple TB size? Try one with less space.

Regards
Matthias Carstens
RME

3 (edited by Potscrubber 2019-11-25 08:13:22)

Re: Digicheck Auto Close

Hi MC
I've got this issue too just suddenly after years of flawless Digicheck on this system.  Looking in the event log, there's a  memory access violation exception code 0xc0000005. Tried full uninstall/reinstall (now every run is an initial run asking for temp folder).  Digicheck window is created and is all white, then DC crashes and WerFault.exe is seen in the task manager.  Tried windows update, and sfc /scannow.

Win 10 x64 1903

Text exports from the two events every time I try and launch Digicheck (Information Event ID 1001 and Error Event ID 1000)

Level    Date and Time    Source    Event ID    Task Category
Information    25/11/2019 5:36:35 PM    Windows Error Reporting    1001    None    "Fault bucket 1279207897827364676, type 1
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: digicheck.exe
P2: 5.92.0.0
P3: 5b9b79ce
P4: digicheck.exe
P5: 5.92.0.0
P6: 5b9b79ce
P7: c0000005
P8: 0000a9a6
P9: 
P10: 

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER95E8.tmp.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9666.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9677.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9685.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER96A5.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_digicheck.exe_fec04f02f10838feb6c63c6badeb3baad5dc0b3_41d01b94_8b71a8a8-fdcf-483f-a9bb-ed1ffa757f62

Analysis symbol: 
Rechecking for solution: 0
Report Id: e828261f-e5c0-4828-a753-9796c80b1b4e
Report Status: 268435456
Hashed bucket: efc6d2d9b4ad2fc8d1c0a8ce37dfcf44
Cab Guid: 0"
Level    Date and Time    Source    Event ID    Task Category
Error    25/11/2019 5:36:33 PM    Application Error    1000    (100)    "Faulting application name: digicheck.exe, version: 5.92.0.0, time stamp: 0x5b9b79ce
Faulting module name: digicheck.exe, version: 5.92.0.0, time stamp: 0x5b9b79ce
Exception code: 0xc0000005
Fault offset: 0x0000a9a6
Faulting process id: 0x1478
Faulting application start time: 0x01d5a349e5ed54a2
Faulting application path: C:\Program Files (x86)\RME\Digicheck5\digicheck.exe
Faulting module path: C:\Program Files (x86)\RME\Digicheck5\digicheck.exe
Report Id: e828261f-e5c0-4828-a753-9796c80b1b4e
Faulting package full name: 
Faulting package-relative application ID: "
Madiface XT, Madiface, 3x Micstasy, ADI8QS
Sequoia 17, W10 x64
https://bsound.co.nz/tools-nix

4

Re: Digicheck Auto Close

More details needed here. Your crash seems related to the temp path function. What and how many hard drives do you have (max space, how many partitions, formatting...)? Did that change since DC crashes? Can you still select a temp directory and did you try to use one at a different location?

Regards
Matthias Carstens
RME

5 (edited by Potscrubber 2019-12-14 09:54:18)

Re: Digicheck Auto Close

Do you mean Windows temp path (not DC global record temp) ?  My win temp is still C:\Users\User\AppData\Local\Temp
I don't remember changing anything in the last few days when DC started crashing.  Though looking at the disk management below, the disk numbers seemed to have changed their order somehow from normal.
Your last question: You mean a DC temp directory?  yes - but DC crashes after selection.
DC only started asking for temp dir since I uninstalled/reinstalled.  It was also crashing before that (and not asking for temp dir).

Madiface XT, Madiface, 3x Micstasy, ADI8QS
Sequoia 17, W10 x64
https://bsound.co.nz/tools-nix

6

Re: Digicheck Auto Close

I meant the DC temp path. It crashes even if you select whatever Dir you have on drive D: or E:?

Regards
Matthias Carstens
RME

Re: Digicheck Auto Close

Yeah, or C:.  But it started crashing before I uninstalled/reinstalled, when it still "knew" it's previous temp path.

Madiface XT, Madiface, 3x Micstasy, ADI8QS
Sequoia 17, W10 x64
https://bsound.co.nz/tools-nix

8

Re: Digicheck Auto Close

Uninstalling DC does not delete the main registry entries (all settings of DC). Maybe these are corrupted. You could use a registry editor to delete them. Path:

HKEY_CURRENT_USER\Software\RME\DIGICheck

After deleting everything below 'DIGICheck' just restart DC. Maybe this helps.

Regards
Matthias Carstens
RME

9 (edited by Potscrubber 2019-11-26 11:24:15)

Re: Digicheck Auto Close

Unfortunately, no change.  It stopped working somewhere in the last week, but the only maintenance done on the machine would be a few plugin installs/uninstalls.

Does DC have any dependencies?  Can I collect any further diagnostic information anywhere?

Wow I didn't realise how often in a day I glance over at DC.

Here is a GIF of how it plays out (ends with me refreshing the Application Event Log):

http://www.bsound.co.nz/downloads/DC_SS.gif

Madiface XT, Madiface, 3x Micstasy, ADI8QS
Sequoia 17, W10 x64
https://bsound.co.nz/tools-nix

10

Re: Digicheck Auto Close

Cool wink

I mean not cool that it crashes. We'll discuss how to proceed.

Regards
Matthias Carstens
RME

Re: Digicheck Auto Close

Frustratingly, the solution for me was to uninstall and reinstall my driver_pciefx_win_214.  Frustrating because it was the last of 20 things I tried, because I didn't think of it sooner (the driver has appeared to be running perfectly), and a little bit because there was no indication that Digicheck was having a device issue: the exception thrown is a very general memory access violation.

Madiface XT, Madiface, 3x Micstasy, ADI8QS
Sequoia 17, W10 x64
https://bsound.co.nz/tools-nix