Failed Device Initialization with Creative ASIO driver

フォーラム TuneBrowser Failed Device Initialization with Creative ASIO driver

  • このトピックには3件の返信、2人の参加者があり、最後にTikiにより4週、 1日前に更新されました。
4件の投稿を表示中 - 1 - 4件目 (全4件中)
  • 投稿者
    投稿
  • #14736
    storaid
    参加者

    Hello, Tiki

    I have used ASIO Tester and confirmed that it works normally.

    But I don’t know why it failed to initialize with TuneBrowser.

    Is there any way to check further?

    Thanks

    
    
    2024/01/18 23:22:24,626: UL05660: T05b3c: User selected player by toolbar.
    2024/01/18 23:22:24,627: UL05661: T05b3c: Set AbortPlayPreparing flag.
    2024/01/18 23:22:24,627: UL05662: T02c1c: PlayerCmdThread end.
    2024/01/18 23:22:24,631: UL05664: T01d2c: Stage: [EndDevice]
    2024/01/18 23:22:24,631: UL05665: T01d2c: Release AudioClient 00000272B8AED320.
    2024/01/18 23:22:24,631: UL05666: T01d2c: Release EndpointVolume 00000272853DB920.
    2024/01/18 23:22:24,631: UL05667: T01d2c: Release MMDevice 00000272B7444090.
    2024/01/18 23:22:24,631: UL05668: T05b3c: Stage: [EndPlayer]
    2024/01/18 23:22:24,631: UL05669: T05b3c: Player module [WASAPI: SONY TV *30 (NVIDIA High Definition Audio)] ended.
    2024/01/18 23:22:24,631: UL05671: T01d2c: PlayerCtrlThread end.
    2024/01/18 23:22:24,631: UL05674: T05b3c: Fisnished player object: [WASAPI: SONY TV *30 (NVIDIA High Definition Audio)]
    2024/01/18 23:22:24,632: UL05675: T05b3c: Created player object: [ASIO: Creative Sound Blaster ASIO]
    2024/01/18 23:22:24,636: UL05676: T05b3c: Current tune: [\\10.1.1.127\music\[Hi-Res]TVアニメ「葬送のフリーレン」OPテーマ「勇者」/YOASOBI\01.勇者.flac:0]
    2024/01/18 23:22:24,636: UL05677: T05b3c: Post PlayerNotify: 7023 [Update]
    2024/01/18 23:22:24,636: UL05678: T05b3c: Current tune adjusted to sequence position 0.
    2024/01/18 23:22:24,636: UL05679: T05b3c: Stage: [InitializePlayer]
    2024/01/18 23:22:24,636: UL05681: T02598: PlayerCtrlThread begin.
    2024/01/18 23:22:24,638: UL05683: T05b3c: Player module [ASIO: Creative Sound Blaster ASIO] initialized.
    2024/01/18 23:22:24,638: UL05684: T06820: PlayerCmdThread begin.
    2024/01/18 23:22:24,638: UL05685: T02598: Stage: [InitializeDevice]
    2024/01/18 23:22:24,639: UL05686: T02598: Creating ASIOProxyProcess.
    2024/01/18 23:22:24,642: UL05687: T02598: Creating ASIOProxyProcess completed.
    2024/01/18 23:22:24,644: UL05689: T02598: ASIOProxyProcess: Call : [Initialize] Param:0
    2024/01/18 23:22:24,660: UL05690: T02598: Prx: 2024/01/18 23:22:24,652.499: T06bb8: Detail log disabled.
    2024/01/18 23:22:24,660: UL05691: T02598: Prx: 2024/01/18 23:22:24,652.502: T06bb8: Processors: 24.
    2024/01/18 23:22:24,660: UL05692: T02598: Prx: 2024/01/18 23:22:24,652.736: T06bb8: Opening ASIO driver ID:0: Creative Sound Blaster ASIO
    2024/01/18 23:22:24,660: UL05693: T02598: Prx: 2024/01/18 23:22:24,652.742: T06bb8: Calling ASIOOpenDriver_SEH_Wrapper
    2024/01/18 23:22:24,660: UL05694: T02598: Prx: 2024/01/18 23:22:24,653.754: T06bb8: Calling ASIOOpenDriver_SEH_Wrapper completed: 0
    2024/01/18 23:22:24,660: UL05695: T02598: Prx: 2024/01/18 23:22:24,653.763: T06bb8: Driver stage: [None ] -> [Loaded ]
    2024/01/18 23:22:24,660: UL05696: T02598: Prx: 2024/01/18 23:22:24,653.766: T06bb8: Calling ASIODriverInit_SEH_Wrapper
    2024/01/18 23:22:24,660: UL05697: T02598: Prx: 2024/01/18 23:22:24,660.326: T06bb8: Error: Failed to call ASIODriverInit_SEH_Wrapper. Status: 0xC0000005
    2024/01/18 23:22:24,660: UL05698: T02598: Prx: 2024/01/18 23:22:24,660.330: T06bb8: Error: - Driver: [Creative Sound Blaster ASIO]
    2024/01/18 23:22:24,660: UL05699: T02598: Prx: 2024/01/18 23:22:24,660.332: T06bb8: Error: - Detected access violation in ASIO driver.
    2024/01/18 23:22:24,660: UL05700: T02598: Prx: 2024/01/18 23:22:24,660.347: T06bb8: Error: Failed to initialize ASIO driver.
    2024/01/18 23:22:24,660: UL05701: T02598: Prx: 2024/01/18 23:22:24,660.354: T06bb8: Calling ASIOCloseDriver_SEH_Wrapper
    2024/01/18 23:22:24,660: UL05702: T02598: Prx: 2024/01/18 23:22:24,660.437: T06bb8: Calling ASIOCloseDriver_SEH_Wrapper completed: 0
    2024/01/18 23:22:24,660: UL05703: T02598: Prx: 2024/01/18 23:22:24,660.446: T06bb8: Driver stage: [Loaded ] -> [None ]
    2024/01/18 23:22:24,660: UL05704: T02598: Prx: 2024/01/18 23:22:24,660.450: T06bb8: Calling ASIODeleteDriverList_SEH_Wrapper
    2024/01/18 23:22:24,660: UL05705: T02598: Prx: 2024/01/18 23:22:24,660.454: T06bb8: Calling ASIODeleteDriverList_SEH_Wrapper completed: 0
    2024/01/18 23:22:24,660: UL05706: T02598: ASIOProxyProcess: Done : [Initialize] Result:0 Wait:0
    2024/01/18 23:22:24,660: UL05707: T02598: Error: Initialize ASIO driver failed. End device.
    2024/01/18 23:22:24,660: UL05708: T02598: ASIOProxyProcess: Call : [End] Param:0
    2024/01/18 23:22:24,660: UL05709: T02598: ASIOProxyProcess: Done : [End] Result:1 Wait:0
    2024/01/18 23:22:24,660: UL05710: T02598: ASIOProxyProcess: Call : [Quit] Param:0
    2024/01/18 23:22:24,660: UL05711: T02598: Prx: 2024/01/18 23:22:24,660.639: T06bb8: ASIOProxyProcess is going down.
    2024/01/18 23:22:24,660: UL05712: T02598: ASIOProxyProcess: Done : [Quit] Result:1 Wait:0
    2024/01/18 23:22:24,663: UL05713: T02598: Terminating for ASIOProxyProcess completed.
    2024/01/18 23:22:24,663: UL05717: T02598: Error: InitializeDevice result: NG
    2024/01/18 23:22:24,663: UL05718: T05b3c: Error: Player device initialization failed: [ASIO: Creative Sound Blaster ASIO]
    2024/01/18 23:22:24,670: UL05719: T05b3c: Proc PlayerNotify: 7023 [Update]
    
    
    #14737
    storaid
    参加者

    Hi,

    I attempted to use the WinDbg tool for detection, trying to find some clues.

    When TuneBrowser is using Creative ASIO device, it triggers the following exception:

    
    
    This exception may be expected and handled. CtUsAs64!DllInstall+0x721b: 00000000<code>61dc02d7 f30f6f0408 movdqu xmm0,xmmword ptr [rax+rcx] ds:00000212</code>5044a008=????????????????????????????????
    
    

    Based on my investigation, it is possible that it is affected by the Memory Integrity security feature of Windows Security.

    Therefore, I disabled it and tried again.

    Now it’s working.

    I don’t know why this happened!

    Because when I tested under Foobar 2000, the Creative ASIO Driver worked perfectly fine.

    #14739
    Tiki
    キーマスター

    Hello.

    2024/01/18 23:22:24,660.326: T06bb8: Error: Failed to call ASIODriverInit_SEH_Wrapper. Status: 0xC0000005
    2024/01/18 23:22:24,660.330: T06bb8: Error: - Driver: [Creative Sound Blaster ASIO]
    2024/01/18 23:22:24,660.332: T06bb8: Error: - Detected access violation in ASIO driver.

     

    ASIO driver is causing access violation while initializing. Unfortunately, I do not know why the access violation is occurring or what the difference is between foobar2000 and TuneBrowser.

    Here is a similar information:

    creative サウンドカードのASIOドライバの使い方について

    #14781
    Tiki
    キーマスター

    時間が経過しましたので、このトピックはクローズさせていただきます。

4件の投稿を表示中 - 1 - 4件目 (全4件中)
  • トピック「Failed Device Initialization with Creative ASIO driver」には新しい返信をつけることはできません。