B-3X crashing standalone in Windows

[DKnight71]

Hello,

I was using B-3X for many months on my WIndows laptop without any issues. One day, I loaded it, tried changing presets, and boom, crash and close. This happened about a month ago. Tried uninstall, reinstall, no good. Anyone else having issues?

Thanks
Dennis

[Promidi]

Just tried it here, no problems. My configuration is as per my signature.

What are your PC specs?
Standalone or with a host? (If just crashing in host, which host?)
What sample rate, bit depth and buffer size are you using.
What audio interface are you using (updated/reinstalled drivers?)
What driver mode? (ASIO is preferred)
What have you tried so far?

We really need more information.

[DKnight71]

Understood. I will post more info shortly. Thanks

[DKnight71]

Ok here are more details

HP Envy x360 2 in 1 laptop
Windows 11 Home
23H2
OS Build 22631.3672
Intel Core Ultra 7
32 gb ram
1 tb SSD

Using Yamaha ASIO driver with Yamaha Montage M7 as the audio interface. 256 buffer size.

This crash occurs in both standalone mode and within Gig Performer 4.8.2. I am able to open the program. As soon as I try to change presets, it crashes.

[Promidi]

Is there any further details in any error messages. Windows Application Event Viewer?

If this were me my next move would be to update all drivers, not just the Yamaha Montage M7.

Head to the Yamaha website for these.

For your other drivers, you might want to head to HP

https://support.hp.com/us-en/drivers/hp ... 2101549653

[DKnight71]

HP drivers updated.
Yamaha driver is latest

Here is detail from Windows Event Viewer, Application Log:

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Application Error" Guid="{a0e9b465-b939-57d7-b27d-95d8e925ff57}" />
<EventID>1000</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>100</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2024-06-06T12:22:48.8717196Z" />
<EventRecordID>8240</EventRecordID>
<Correlation />
<Execution ProcessID="17176" ThreadID="11148" />
<Channel>Application</Channel>
<Computer>DKnightMusic-32</Computer>
<Security UserID="S-1-5-21-2706582272-2275688327-516045836-1001" />
</System>
- <EventData>
<Data Name="AppName">Hammond B-3X.exe</Data>
<Data Name="AppVersion">1.3.4.0</Data>
<Data Name="AppTimeStamp">61de9255</Data>
<Data Name="ModuleName">Hammond B-3X.exe</Data>
<Data Name="ModuleVersion">1.3.4.0</Data>
<Data Name="ModuleTimeStamp">61de9255</Data>
<Data Name="ExceptionCode">c0000005</Data>
<Data Name="FaultingOffset">00000000004ef355</Data>
<Data Name="ProcessId">0x41c4</Data>
<Data Name="ProcessCreationTime">0x1dab80c11a41db2</Data>
<Data Name="AppPath">C:\Program Files\IK Multimedia\Hammond B-3X\Hammond B-3X.exe</Data>
<Data Name="ModulePath">C:\Program Files\IK Multimedia\Hammond B-3X\Hammond B-3X.exe</Data>
<Data Name="IntegratorReportId">f392c610-a1b3-442a-b981-092365d5353d</Data>
<Data Name="PackageFullName" />
<Data Name="PackageRelativeAppId" />
</EventData>
</Event>

[Promidi]

When ever I see "ExceptionCode">c0000005" I see that as a very generic error message, which could be caused by anything.

Even though the drivers are the latest, I would still do the reinstall.

With the Yamaha drivers, I would do an uninstall then reinstall - Windows updates might have borked them

It might also be worth updating the Vdist runtimes (I am not sure it IKM use these, however) Scroll down to "X64"

https://learn.microsoft.com/en-AU/cpp/w ... w=msvc-170

Failing that, you might have to contact IKM support.

https://www.ikmultimedia.com/contact-support/sw/

[DKnight71]

This also happens using the standard Windows driver (not ASIO). It doesnt appear to be driver related. Maybe its a Windows 11 thing.

Thanks for trying to help. I appreciate it. I opened a support ticket 6 days ago and I've heard nothing yet.

[DKnight71]

Ok support replied and its fixed now.

FYI, had to uninstall B-3X. Then manually remove all registry entries related to it. Then reboot. Reinstall. And boom, working fine again.

I just don't understand what caused the issue in the first place.