Skip to main content ↑ ↓

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: Vista 64 "Add New" ASIO crash (Read 2426 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Vista 64 "Add New" ASIO crash

This happens every time I try to "Add New" in the Asio Virtual Devices menu.  Using the latest Foobar and ASIO out component, also tried an older version.  Everything works just fine in XP x86.  I'm using both onboard audio and a firewire Focusrite Saffire LE and Mbox 2.  I use the Saffire for 5.1 out, but I don't think that matters since it works fine as a normal 2 channel DS output.

Any ideas?  If I can't get this working to upmix .mp3s onto my 5.1 system then what the hell is the point of Vista?  Foobar is more important than the OS itself, at least for me.

Problem signature:
  Problem Event Name:   APPCRASH
  Application Name:   foobar2000.exe
  Application Version:   0.9.5.4
  Application Timestamp:   486fdd8a
  Fault Module Name:   kernel32.dll
  Fault Module Version:   6.0.6001.18000
  Fault Module Timestamp:   4791a81d
  Exception Code:   e06d7363
  Exception Offset:   0002f35f
  OS Version:   6.0.6001.2.1.0.256.1
  Locale ID:   1033
  Additional Information 1:   1739
  Additional Information 2:   3c3cf0b351726b85a2b6d24ff0a86110
  Additional Information 3:   7d1c
  Additional Information 4:   1d1d64b872c793392285053bf8183ae1

Read our privacy statement:
  http://go.microsoft.com/fwlink/?linkid=501...mp;clcid=0x0409
 

Vista 64 "Add New" ASIO crash

Reply #1 –
Same problem here, but with Windows 7, build 7000.

1. Start foobar
2. Ctrl+P
3. Playback->Output->ASIO Virtual Devices
4. Press Add New
5. *bang*

I have tried "Run as administrator", compatibility xp/vista - all with the same result.

---

eventlog:

Fault bucket 1123118101, type 1
Event Name: APPCRASH
Response: Not available
Cab Id: 574566923

Problem signature:
P1: foobar2000.exe
P2: 0.9.6.2
P3: 49834dc2
P4: KERNELBASE.dll
P5: 6.1.7000.0
P6: 49433de1
P7: e06d7363
P8: 0000ae33
P9:
P10:

Attached files:
C:\Users\Morten Teinum\AppData\Local\Temp\WERCE2E.tmp.WERInternalMetadata.xml
C:\Users\Morten Teinum\AppData\Local\Temp\WERE67A.tmp.appcompat.txt
C:\Users\Morten Teinum\AppData\Local\Temp\WERE6B9.tmp.mdmp

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_foobar2000.exe_f19314aa781c642fdecefe61a460c69ac84a3_cab_13b82c8a

Analysis symbol: APPLICATION_FAULT_e06d7363_ole32.dll!LoadLibraryWithLogging
Rechecking for solution: 0
Report Id: 2d79e6f3-f244-11dd-8db5-0014c2dd0cff
Report Status: 24

-----

Faulting application name: foobar2000.exe, version: 0.9.6.2, time stamp: 0x49834dc2
Faulting module name: KERNELBASE.dll, version: 6.1.7000.0, time stamp: 0x49433de1
Exception code: 0xe06d7363
Fault offset: 0x0000ae33
Faulting process id: 0x1360
Faulting application start time: 0x01c9865259019e19
Faulting application path: C:\Program Files\foobar2000\foobar2000.exe
Faulting module path: C:\Windows\system32\KERNELBASE.dll
Report Id: bf315f3f-f245-11dd-8db5-0014c2dd0cff

----

Regarding "Analysis symbol: APPLICATION_FAULT_e06d7363_ole32.dll!LoadLibraryWithLogging", this is different from time to time.

I have tried "ASIO caps_009.1 x86", and this can communicate sucessfully with the asio driver and control panel. The same is true with VSTHost.

The asio driver is only available when running the programs as adminsitrator.

Hardware: Digidesig mbox 2 mini
Software: ASIO Digidesign Driver 7.4

foo_out_asio.dll: 1.2.6

Any idea?