Crashes with ASIO4ALL/Reaper/Potato

[ArdRhi]

Ok, I'm having a major problem here. I'm getting random crashes. Either it's shutting down the machine, or, just a few minutes ago, a BSOD. Thankfully it wrote a DMP file.

I'm trying to LEARN to use a DAW (Reaper) and I have Potato installed. I'm also interfacing with MuseScore, a notation program that can play back the score you create. I'm taking a music theory course, and this is a necessary tool for the course.

I have the ASIO4ALL driver installed, and it works...except for these random crashes. This is the first crash where I got a dump file out of it, so this is the first time I could analyze anything. In the analysis of the DMP file with WinDbg Preview, it appears to be the ASIO connection that's failing. So I searched for that on the web. Turns out there's an issue using ASIO4ALL with Voicemeeter, primarily being that it's not necessary, according to the documentation. But I'm at a real loss to figure out how to get rid of ASIO4ALL and instead use the built-in ASIO in Potato. Are there instructions for getting it to work with a DAW? I have never done the more advanced things with VM, such as "patch insert" or anything like that, so #ExplainItToMeAsIfI'mFive, if someone could please take the time. I don't want my system to get damaged by these crashes. I've tried everything else I can think of, and it's only because this dump analysis mentions Voicemeeter that I'm even going down this route.

I searched the Forum topics, and while there's some stuff about DAWs, they're mostly CUBASE, which I don't use, and it's all old, from last year sometime. So can someone please help me out and tell me what I've got messed up and how to un-mess it? I'd really appreciate the help!

I got WinDbg Preview loaded, and this is the result of analyzing the file:

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: ffffb281afba1000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff80776ee2a82, address which referenced memory

Debugging Details:
------------------


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 2608

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 4628

Key : Analysis.Init.CPU.mSec
Value: 609

Key : Analysis.Init.Elapsed.mSec
Value: 46799

Key : Analysis.Memory.CommitPeak.Mb
Value: 78

Key : WER.OS.Branch
Value: vb_release

Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z

Key : WER.OS.Version
Value: 10.0.19041.1


BUGCHECK_CODE: d1

BUGCHECK_P1: ffffb281afba1000

BUGCHECK_P2: 2

BUGCHECK_P3: 1

BUGCHECK_P4: fffff80776ee2a82

WRITE_ADDRESS: ffffb281afba1000

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

PROCESS_NAME: System

TRAP_FRAME: ffffd60277c4f2b0 -- (.trap 0xffffd60277c4f2b0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80776ee2a82 rsp=ffffd60277c4f440 rbp=0000000000000e1b
r8=0000000000000091 r9=ffffb281afba1002 r10=0000000000000001
r11=0000000000000093 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
vbaudio_vmvaio64_win10+0x2a82:
fffff807`76ee2a82 418841fe mov byte ptr [r9-2],al ds:ffffb281`afba1000=??
Resetting default scope

STACK_TEXT:
ffffd602`77c4f168 fffff807`60e09169 : 00000000`0000000a ffffb281`afba1000 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
ffffd602`77c4f170 fffff807`60e05469 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
ffffd602`77c4f2b0 fffff807`76ee2a82 : 00000000`00000002 00000000`73496350 00000000`00000080 00000000`00000de2 : nt!KiPageFault+0x469
ffffd602`77c4f440 fffff807`76ee3243 : ffffd88c`20380000 ffffb281`afba0fe8 ffffd88c`20380000 00000000`000000a0 : vbaudio_vmvaio64_win10+0x2a82
ffffd602`77c4f500 fffff807`76ee4803 : ffffd88c`20380000 ffffb281`afba0fe8 00000000`000043c8 00000000`00000000 : vbaudio_vmvaio64_win10+0x3243
ffffd602`77c4f5b0 fffff807`79810a5b : ffffd88c`2858b060 ffffd88c`21f316d0 00000000`000043c8 ffffd602`77c4f710 : vbaudio_vmvaio64_win10+0x4803
ffffd602`77c4f600 fffff807`798117c7 : 00000000`00000002 ffffd602`77c4f6b8 00000000`00000018 00000000`000043c8 : portcls!CPortPinWaveCyclic::Copy+0xa3
ffffd602`77c4f650 fffff807`7980b895 : ffffd88c`0000fa98 ffffd88c`00000000 ffffd88c`00000000 00000000`00000000 : portcls!CPortPinWaveCyclic::RequestService+0x337
ffffd602`77c4f700 fffff807`60c9a3ae : ffffb281`ab445240 ffffd602`77c4fa90 ffffb281`ab442180 ffffd88c`00000002 : portcls!CServiceGroup::ServiceDpc+0x75
ffffd602`77c4f760 fffff807`60c99694 : 00000000`00000000 00000000`00000000 00000000`00140001 00000000`00762533 : nt!KiExecuteAllDpcs+0x30e
ffffd602`77c4f8d0 fffff807`60dfad3e : ffffffff`00000000 ffffb281`ab442180 ffffb281`ab44d240 ffffd88c`35de1080 : nt!KiRetireDpcList+0x1f4
ffffd602`77c4fb60 00000000`00000000 : ffffd602`77c50000 ffffd602`77c49000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x9e


SYMBOL_NAME: vbaudio_vmvaio64_win10+2a82

MODULE_NAME: vbaudio_vmvaio64_win10

IMAGE_NAME: vbaudio_vmvaio64_win10.sys

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 2a82

FAILURE_BUCKET_ID: AV_vbaudio_vmvaio64_win10!unknown_function

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {122563d5-ffb5-b28e-3914-ab08f3db2b96}

[xcasxcursex]

By the way, you should have a talk with your course handler about removing the evil Muse Group from their curriculum. Frankly after their repeated attacks against both the musician and programming community, I outright refuse to use their software at all, and you should, too.

Now that we have that out of the way, this one is interesting because a BSOD means a hardware fault or an error in the driver handling that hardware. Looking at the dump I don't see any sign of ASIO4ALL (but you said you saw the ASIO connection in the dumps? Am I missing something here?) and it really looks like the VM cable crashed but obviously that's not normal, so that leaves us with the question of why it crashes on your machine but nobody else's.

First and most obvious thing would be to completely uninstall and reinstall voicemeeter, but I'll assume you already tried that (including all of the reboots and everything as per the instructions on this forum). Next up I'd be looking at disk corruption. Just run chkdsk on it and see what it says. I can't help but wonder if you have your PC overclocked. If you do, clear your CMOS and run it stock and see how you fare.

More logs is always good Let us know how it goes....

[Natrox]

I'd like to chime in with a few things:
- The crash itself seems to occur in the VB VAOI driver (vbaudio_vmvaio64_win10).
- Perhaps ASIO4ALL hooks itself into existing AIO implementations? This is a stretch, so I don't know.
- You should be able to safely get rid of ASIO4ALL and switch your inputs to VAOI. These devices should also properly show up in Reaper.
- An DRIVER_IRQL_NOT_LESS_OR_EQUAL is the fancy driver way of saying "Access Violation" - the complication here is that these can also be caused by memory module errors. As xcasxcursex mentions, a chkdsk first is a good bet, then a BIOS check to see if your memory settings make sense. If you've tuned your memory, it might be unstable. If you have not, you might be looking at faulty RAM. Download a copy of Memtest86 and write it to a USB pendrive - if it shows any errors during the tests, you're looking at a hardware problem.