buzz forums

Faulting application name: scan.x64.exe, version: 0.0.0.0, time stamp: 0x5ca48c8e
Faulting module name: VPRE-73HE.dll, version: 2.5.8.0, time stamp: 0x617175b7
Exception code: 0xc0000005
Fault offset: 0x00000000000f4655
Faulting process id: 0x88c
Faulting application start time: 0x01d7cf75de5ab6df
Faulting application path: C:\Program Files (x86)\Jeskola\Buzz\bin64\scan.x64.exe
Faulting module path: C:\Program Files\Vstplugins\Black Rooster Audio\VPRE-73HE.dll
Report Id: c22f0dce-d293-4a95-a783-550e7b661226
Faulting package full name:
Faulting package-relative application ID:

polac wrote: ↑Thu Oct 28, 2021 10:08 am I really hope the save bug is sorted out, fingers crossed.

1. Start Buzz 32, create a more complex song including many big VSTs.
2. Add 64bit version of Ozone 8 Standard before Master and select some preset.
3. Save song
4. Load song.
5. If problem occurred, then Ozone crashes when loading and I actually need to rename ozone dll/remove it so that I can load the song again. You might need to play around with the song machines to find correct combination.

• If you are able to create this reproducible setup then saving the song with Ozone 8 64bit and closing Buzz will not close vst.x64.dll process (hinting that something went wrong when saving).
• Interestingly 32bit version of Ozone 8 will not reproduce this issue in the song where 64bit Ozone does.

One issue I noticed that might be easier to reproduce.

Start Buzz 32, create a more complex song including many big VSTs.
Add 64bit version of Ozone 8 Standard before Master and select some preset.
Save song
Load song.
If problem occurred, then Ozone crashes when loading and I actually need to rename ozone dll/remove it so that I can load the song again. You might need to play around with the song machines to find correct combination.

mcbpete wrote: ↑Tue Nov 02, 2021 11:01 pm Never knew about the application until last year when I got a new (and rather troublesome to initially diagnose the fault) laptop, and got tech support to aid my repair via this tool - but since have got rather 'obsessed' with Window's built in app Reliability Monitor (more specifically getting a run of days without any kind of warning or critical events so the graph heads towards a fabled 10/10 score ). I notice that if I load Buzz with any new VST (or VSTi) installed since last loading (specifically new, rather than updates to older existing versions of the VST/i) that Reliability Monitor will always complain of a critical event claiming that scan.x64.exe has 'stopped working'.

There doesn't actually seem to be any visible problem, Polac will successfully scan that plugin and add it to my machine index, just wondering quite why Windows itself seems to kick up a fuss regarding what seems to be a non-issue. Does anyone else get this critical event logged in Reliability Monitor ?

Here's an example error log (Had just installed Black Rooster Audio - VPRE-73HE before launching Buzz). The plugin itself works perfectly and appears in the gear list:

Faulting application name: scan.x64.exe, version: 0.0.0.0, time stamp: 0x5ca48c8e
Faulting module name: VPRE-73HE.dll, version: 2.5.8.0, time stamp: 0x617175b7
Exception code: 0xc0000005
Fault offset: 0x00000000000f4655
Faulting process id: 0x88c
Faulting application start time: 0x01d7cf75de5ab6df
Faulting application path: C:\Program Files (x86)\Jeskola\Buzz\bin64\scan.x64.exe
Faulting module path: C:\Program Files\Vstplugins\Black Rooster Audio\VPRE-73HE.dll
Report Id: c22f0dce-d293-4a95-a783-550e7b661226
Faulting package full name:
Faulting package-relative application ID:

(apologies to those that have now also fallen for the compulsion of getting a 10/10 score run in Reliability Monitor!)

rav wrote: ↑Fri Jan 21, 2022 11:11 am Is audio input to VST3 instruments working for you? New version of Surge XT is released only in VST3 format and it's not possible to use as FX in VST3 format. Tried in another DAW and it works.

domtron wrote: ↑Fri Jun 17, 2022 5:10 pm Scanning "for new" gave me loads of problems. An all updated Windows 11 has problems to start "Child processes". Be careful if you want to scan plugins. Net Framework is a mess on Windows 11. Otherwise, you need to hammer the Buzz exe to actually let Windows 11 find "the Child" by accident

viewtopic.php?f=2&t=2829

For now I leave Buzz open.

polac wrote: ↑Thu Jul 07, 2022 10:10 am Cannot test under Windows 11 as my pc doesn't meet the requirements and I don't plan to buy a new pc for the next 2-3 years.

polac wrote: ↑Thu Jul 07, 2022 10:10 am

domtron wrote: ↑Fri Jun 17, 2022 5:10 pm Scanning "for new" gave me loads of problems. An all updated Windows 11 has problems to start "Child processes". Be careful if you want to scan plugins. Net Framework is a mess on Windows 11. Otherwise, you need to hammer the Buzz exe to actually let Windows 11 find "the Child" by accident

viewtopic.php?f=2&t=2829

For now I leave Buzz open.

Cannot test under Windows 11 as my pc doesn't meet the requirements and I don't plan to buy a new pc for the next 2-3 years.

domtron wrote: ↑Thu Jul 14, 2022 5:40 am I don't think it has nesserarily something to do with Windows 11. I killed the VST scanning process ( actually Buzz itself ) from the Task Manager because I thought it took too long for me at that day and that caused the crash. "temporalsounds" had the same problem and that was probably on Windows 10.

domtron wrote: ↑Fri Jun 17, 2022 5:10 pm I don't think it has nesserarily something to do with Windows 11. I killed the VST scanning process ( actually Buzz itself ) from the Task Manager because I thought it took too long for me at that day and that caused the crash. "temporalsounds" had the same problem and that was probably on Windows 10.