Multiple BEX64 crashes, reboots from bugcheck, Blue screens, VSTs causing black screens....

Question

Multiple BEX64 crashes, reboots from bugcheck, Blue screens, VSTs causing black screens....

Derek b 0

I have been attempting to get a VST update to work properly and have started investigating Event viewer and Reliability Monitor and seen multiple BEX64 shutdown, application failures, windows failures and warnings as well as information. I do not see blue screens but they are listed in the monitor. I had 2 instances of Blackscreen shutdowns after updating or downgrading a specific app. Windows is up to date, there are no driver issues that I can see.

Most recent :

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000010d (0x0000000000000005, 0x0000000000000000, 0x0000000000001203, 0xffffd505eeaeddd0). A dump was saved in: C:\WINDOWS\Minidump\110526-19093-01.dmp. Report Id: [PII removed]

Another issue looks odd,cause is listed Awe.zip. I have no idea what this is, I could not locate in any programs.

User's image

Latest Minidump zip

[PII removed]

Previous Minidump zips

[PII removed]

I've done an offline scan for malware, nothing came up.

I have a system info available if that helps, I'm not sure if I should post it here.

To sum up, I'm having odd behaviour after attempting to update a Music Instrument VST which caused 2 Black screen shutdowns immediately upon opening. Windows is displaying Blue screen shutdowns that I have not actually seen on the monitor and the manufacturer of the VST is unable to pinpoint a reason for this glitch in their software. We've tryed uninstalling and de-authorizing. The update cannot seem to display the contents stored in the documents folder, the Previous version does show all components in the documents folder.

I've tried the DSIM and SFC tools without any success. I'm seeing other programs hang or crash after the Black Screen incidents.

Device name [PII removed]

Processor 13th Gen Intel(R) Core(TM) i5-13500 (2.50 GHz)

Installed RAM 32.0 GB (31.8 GB usable)

Graphics card Intel(R) UHD Graphics 770 (128 MB)

Storage 6.59 TB of 15.04 TB used

Device ID [PII removed]

Product ID [PII removed]

System type 64-bit operating system, x64-based processor

Pen and touch No pen or touch input is available for this display

Edition Windows 11 Pro

Version 26H2

Installed on ‎2025-‎05-‎21

OS build 26300.9818

Experience Windows Feature Experience Pack 1000.26100.385.0

0 comments

1 answer

Your answer

Answer 1

Kai-H 30,915 Microsoft External Staff Moderator

(Please note that our forum is a public platform, and we will modify your question to hide your personal information in the description. Kindly ensure that you hide any personal or organizational information the next time you post an error or other details to protect personal data.)

Hi, @Derek b

The blue screen code you posted (0x10D, WDF_VIOLATION, first value 0x5) means a third-party hardware driver sent Windows bad data and Windows shut down to protect itself. The Microsoft documentation describes this case as a driver passing the wrong type of handle to Windows. Since it started with the VST update, the likely cause is a driver for your audio interface, MIDI keyboard/controller, or the plugin's copy-protection software, not Windows itself. That would also explain why SFC and DISM found nothing.

The AweZip entry isn't related. AweZip is a third-party zip app from the Microsoft Store, and that report only says its right-click menu add-on froze inside COM Surrogate (dllhost.exe), which is a normal Windows process. If you don't use AweZip, you can uninstall it in Settings > Apps > Installed apps.

Here are some suggestions you can try:

Unplug all USB audio and MIDI devices, then open the VST on its own. If it stops crashing, one of those devices' drivers is the problem.

Download the latest driver for your audio interface from the manufacturer's website, not from Windows Update. Do the same for any MIDI controller software. Audio drivers often fall behind the Windows build, so a fresh vendor driver usually fixes this.

If the plugin uses iLok/PACE or another license manager, uninstall it, reinstall the newest version, and then reauthorize.

Open the minidump with a free tool like BlueScreenView and check the "Caused By Driver" column. The .sys file named there tells you which hardware or software is at fault.

If you still get black screens, start in Safe Mode and remove the plugin update completely, along with any driver it installed.

If you post the driver name from step 4 here, I can help narrow it down.

Derek b 0 Reputation points

2026-11-10T22:08:26.3766667+00:00

It seems I'm getting the same result on each minidump report, most recent Nov 03 and 05 and a couple in Feb. Kernel Mode Driver Framework

Crash Nov 05.txt
Derek b 0 Reputation points

2026-11-11T00:39:17.0266667+00:00

I attempted to re register the affected river but got an error instead.
Kai-H 30,915 Reputation points Microsoft External Staff Moderator

2026-11-11T09:11:29.6866667+00:00

Hi, @Derek b

Thanks for checking. Good news first: that regsvr32 error is nothing to worry about. Wdf01000.sys is a kernel driver, not a DLL, so regsvr32 can't register or unregister it. The error just means it refused, and nothing was changed.

The result you're seeing is expected. Wdf01000.sys is the Windows framework that other drivers run on top of, so BlueScreenView always blames it when a driver misbehaves. The real culprit is the driver that called it, and BlueScreenView can't see that far. Since the crashes go back to February, it's probably a driver that has been on the PC for a while and the VST update just made it act up more often.

Download the free tool WhoCrashed (Resplendence), install it, and click Analyze. It reads the same minidumps but usually names the actual third-party .sys file. Post what it says here.

If it still only shows Wdf01000.sys, turn on Driver Verifier so Windows catches the bad driver directly: open Command Prompt as admin, type verifier, choose "Create standard settings", then "Select driver names from a list", and tick every driver that is not from Microsoft. Restart. The next blue screen will name the faulty driver. To turn it off afterward, run verifier /reset. Do a restore point first, and if the PC won't boot, run verifier /reset from Safe Mode.

While waiting, open Device Manager and check Sound, video and game controllers, and Universal Serial Bus controllers for any audio interface, MIDI, or USB driver dated 2024 or earlier. Update those from the manufacturer's site.

Once we have the driver name, the fix is usually just updating or removing that one piece of software.