Start a new topic
Solved

Neon crash on close

  • Name der fehlerhaften Anwendung: Helium.App.exe, Version: 0.5.492.0, Zeitstempel: 0x56f171ac
  • Name des fehlerhaften Moduls: KERNELBASE.dll, Version: 6.1.7601.18798, Zeitstempel: 0x5507b485
  • Ausnahmecode: 0xc0020001
  • Fehleroffset: 0x0000c42d
  • ID des fehlerhaften Prozesses: 0x15a0
  • Startzeit der fehlerhaften Anwendung: 0x01d18511571e39c2
  • Pfad der fehlerhaften Anwendung: C:\Program Files (x86)\Imploded Software\Helium\Helium.App.exe
  • Pfad des fehlerhaften Moduls: C:\Windows\syswow64\KERNELBASE.dll
  • Berichtskennung: cce252dd-f104-11e5-bae7-f0afc85a91bd


greets



Can anyone else reproduce this problem?

I cannot force this to happen on my two machines.

i will download the new build and Report if the error gone or not


greets

same Trouble..


Protokollname: Application
Quelle:  Application Error
Datum:  26.03.2016 10:09:11
Ereignis-ID:  1000
Aufgabenkategorie:(100)
Ebene:  Fehler
Schlüsselwörter:Klassisch
Benutzer:  Nicht zutreffend
Computer:  BrewIdeas
Beschreibung:
Name der fehlerhaften Anwendung: Helium.App.exe, Version: 0.5.495.0, Zeitstempel: 0x56f4178d
Name des fehlerhaften Moduls: KERNELBASE.dll, Version: 6.1.7601.18798, Zeitstempel: 0x5507b485
Ausnahmecode: 0xc0020001
Fehleroffset: 0x0000c42d
ID des fehlerhaften Prozesses: 0x174c
Startzeit der fehlerhaften Anwendung: 0x01d1873f15526da1
Pfad der fehlerhaften Anwendung: C:\Program Files (x86)\Imploded Software\Helium\Helium.App.exe
Pfad des fehlerhaften Moduls: C:\Windows\syswow64\KERNELBASE.dll
Berichtskennung: 66e0210e-f332-11e5-a7cb-9ea2acc4babc
Ereignis-XML:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
  <Provider Name="Application Error" />
  <EventID Qualifiers="0">1000</EventID>
  <Level>2</Level>
  <Task>100</Task>
  <Keywords>0x80000000000000</Keywords>
  <TimeCreated SystemTime="2016-03-26T09:09:11.000000000Z" />
  <EventRecordID>284309</EventRecordID>
  <Channel>Application</Channel>
  <Computer>BrewIdeas</Computer>
  <Security />
  </System>
  <EventData>
  <Data>Helium.App.exe</Data>
  <Data>0.5.495.0</Data>
  <Data>56f4178d</Data>
  <Data>KERNELBASE.dll</Data>
  <Data>6.1.7601.18798</Data>
  <Data>5507b485</Data>
  <Data>c0020001</Data>
  <Data>0000c42d</Data>
  <Data>174c</Data>
  <Data>01d1873f15526da1</Data>
  <Data>C:\Program Files (x86)\Imploded Software\Helium\Helium.App.exe</Data>
  <Data>C:\Windows\syswow64\KERNELBASE.dll</Data>
  <Data>66e0210e-f332-11e5-a7cb-9ea2acc4babc</Data>
  </EventData>
</Event>


2 > 3 execute after Change wasapi Option

Neon Crash


greets

Is sound playing when this happens?

According to the crashlog is seems to happen in kernalbase, which indicates it is a system related crash.

yes with and without.


>>which indicates it is a system related Crash.

No..

http://stackoverflow.com/questions/11835748/0xc0020001-the-string-binding-is-invalid-only-occurring-in-wpf


greets

What happens if you try this:


1) Start Neon

2) Change device


Will the crash the occur?


If so, will it happen for any device you change to or is it related to a specific device?

NO..

Start NEON

Change Status of Wasapi ON/Exclusive OFF
next start Wasapi OFF/Without Exclusiv
and so on...
after Change it by me the error occurred with and without playing Sound.

not always


so i think Tread or Timing issues


greets

Sorry, no luck. Tested like this:


1) Started Neon

2) Played a file

3) Inactivated WASAPI exclusive > restart

4) Played a file

5) Inactivated WASAPI > restart

6) Played a file 

7) Activated WASAPI > restart

8) Played a file

9) Activated Exclusive mode > restart

10) Played a file

11) Repeated the steps 3 times


Tested with build 496 (automatic restart) on two different Win10 machines.


Can anyone else reproduce it?

with or without MessageDialog .. ;)

i can reproduce it allways.


I'm sorry
I can only post what my WindowsLogfile deposited me
after the Crash of Neon.


greets

sorry

I do not want to annoy you
But back after 6 execute...


Protokollname: Application
Quelle:  Application Error
Datum:  26.03.2016 13:13:21
Ereignis-ID:  1000
Aufgabenkategorie:(100)
Ebene:  Fehler
Schlüsselwörter:Klassisch
Benutzer:  Nicht zutreffend
Computer:  BrewIdeas
Beschreibung:
Name der fehlerhaften Anwendung: Helium.App.exe, Version: 0.5.495.0, Zeitstempel: 0x56f4178d
Name des fehlerhaften Moduls: KERNELBASE.dll, Version: 6.1.7601.18798, Zeitstempel: 0x5507b485
Ausnahmecode: 0xc0020001
Fehleroffset: 0x0000c42d
ID des fehlerhaften Prozesses: 0xd68
Startzeit der fehlerhaften Anwendung: 0x01d18758d74c520d
Pfad der fehlerhaften Anwendung: C:\Program Files (x86)\Imploded Software\Helium\Helium.App.exe
Pfad des fehlerhaften Moduls: C:\Windows\syswow64\KERNELBASE.dll
Berichtskennung: 217708e4-f34c-11e5-a7cb-9ea2acc4babc
Ereignis-XML:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
  <Provider Name="Application Error" />
  <EventID Qualifiers="0">1000</EventID>
  <Level>2</Level>
  <Task>100</Task>
  <Keywords>0x80000000000000</Keywords>
  <TimeCreated SystemTime="2016-03-26T12:13:21.000000000Z" />
  <EventRecordID>284310</EventRecordID>
  <Channel>Application</Channel>
  <Computer>BrewIdeas</Computer>
  <Security />
  </System>
  <EventData>
  <Data>Helium.App.exe</Data>
  <Data>0.5.495.0</Data>
  <Data>56f4178d</Data>
  <Data>KERNELBASE.dll</Data>
  <Data>6.1.7601.18798</Data>
  <Data>5507b485</Data>
  <Data>c0020001</Data>
  <Data>0000c42d</Data>
  <Data>d68</Data>
  <Data>01d18758d74c520d</Data>
  <Data>C:\Program Files (x86)\Imploded Software\Helium\Helium.App.exe</Data>
  <Data>C:\Windows\syswow64\KERNELBASE.dll</Data>
  <Data>217708e4-f34c-11e5-a7cb-9ea2acc4babc</Data>
  </EventData>
</Event>


OK should wait for other User (that is not fixed)


greets

Picture with 496 i hope you can see it

if not then

http://home.arcor.de/weiss.em/26.03.png


greets


last 6 error with 496


i hope other user can reproduce it.


greets

I get exactly the same error, but only when i close the application during playback.

@Alex:

Can you please let me know of the exact steps you perform when this error occurs?


Thanks.

Login or Signup to post a comment