W11 Blue Screen Crash

[terrynoakes]

Hi, anyone else experience this, blue screen while using W11 latest build, though its happened also during the beta stage.
It goes blue screen then crashes to restart
On rebooting just after login the screen goes black, and the only way I can get it back, to my desk top is to reboot in safe mode, uninstall Waveform 11 and reboot. Computer will then restart to desktop as it should.
I've had 2 crashes to restart one being with an early beta. And a few blue screens that, resolve after windows has collected data?!
Anyone else?
Thanks

[dRowAudio]

Do you happen to know what the app is doing at the time of crash?
• Is it trying to load a plugin UI? (Which could indicate a graphics driver problem).
• Are you using the plugin sandboxing feature? (This is a new feature so there may be unexpected plugin behaviour causing issues although I wouldn't expect this to be able to cause a BSOD...).

[terrynoakes]

I can't remember the beta crash, though at that point I was trying the sandboxing,
So I stopped using it.
On this occasion today, I was about to record guitar a overdub using Avid 11 rack. I don't use their asio.
I use emu 1212m sound card, and asio
I'm on windows 8.1
Intel i3 CPU2120 @3.30GHz
16gb ram & ati Radeon hd5400 series graphics card.
Not much help I'm afraid sorry.
Cheers

[GuitarPlayerinNYC]

• Are you using the plugin sandboxing feature? (This is a new feature so there may be unexpected plugin behaviour causing issues although I wouldn't expect this to be able to cause a BSOD...).

I literally just upgraded to 11...

I get a "Plugin sandbox status: Disabled" message, and the icon is kind of grayed out. Do I have to turn it on someplace?

With WF10, I'd often get a "not responding" situation. I suspect it's a plugin, but can't narrow it down. There's been times I had 8 tracks loaded, with 15 plugins, and things wouldn't crash.

I just noticed a "use low Detail interface" option. Could this possibly be a fix?

Edit: When things froze, I'd end task, and reload, and things would be generally good again. Win 10, i7, 16 gigs ram.

[terrynoakes]

Yeah, you enable SB in settings plugins bottom right

[GuitarPlayerinNYC]

Thanks, Dave.

[dRowAudio]

• Are you using the plugin sandboxing feature? (This is a new feature so there may be unexpected plugin behaviour causing issues although I wouldn't expect this to be able to cause a BSOD...).

I literally just upgraded to 11...

I get a "Plugin sandbox status: Disabled" message, and the icon is kind of grayed out. Do I have to turn it on someplace?

With WF10, I'd often get a "not responding" situation. I suspect it's a plugin, but can't narrow it down. There's been times I had 8 tracks loaded, with 15 plugins, and things wouldn't crash.

I just noticed a "use low Detail interface" option. Could this possibly be a fix?

Edit: When things froze, I'd end task, and reload, and things would be generally good again. Win 10, i7, 16 gigs ram.

Hangs like that are usually inside plugins (I'm not ruling out a hang in our code, I just haven't seen any in many years). Does audio still pass when this happens?

I haven't added anything specific to plugin sandboxing to handle this case but I probably could in a future update...

If this does happen, you could try killing the sandbox process from Task Manager or Activity Monitor if you can determine which process is the sandbox (as it's a child of the main process it has the same name), that would at least let you know that it is a plugin that's hanging.

If you can narrow it down a bit let us know and we'll see if there's anything we can do our end.

[GuitarPlayerinNYC]

• Are you using the plugin sandboxing feature? (This is a new feature so there may be unexpected plugin behaviour causing issues although I wouldn't expect this to be able to cause a BSOD...).

I literally just upgraded to 11...

I get a "Plugin sandbox status: Disabled" message, and the icon is kind of grayed out. Do I have to turn it on someplace?

With WF10, I'd often get a "not responding" situation. I suspect it's a plugin, but can't narrow it down. There's been times I had 8 tracks loaded, with 15 plugins, and things wouldn't crash.

I just noticed a "use low Detail interface" option. Could this possibly be a fix?

Edit: When things froze, I'd end task, and reload, and things would be generally good again. Win 10, i7, 16 gigs ram.

Hangs like that are usually inside plugins (I'm not ruling out a hang in our code, I just haven't seen any in many years). Does audio still pass when this happens?

I haven't added anything specific to plugin sandboxing to handle this case but I probably could in a future update...

If this does happen, you could try killing the sandbox process from Task Manager or Activity Monitor if you can determine which process is the sandbox (as it's a child of the main process it has the same name), that would at least let you know that it is a plugin that's hanging.

If you can narrow it down a bit let us know and we'll see if there's anything we can do our end.

When I get a hang like that, the screen turns cloudy, and everything freezes, so no, no sound passes through.

I just literally turned on sandboxing. I'll let you know.

The upside of any crashes, after I end task, and reload, I'm right back to where I ended, meaning, I haven't lost any work. Tracktion/WF seems to be good that way.

Really appreciate your speedy input.

[dRowAudio]

Ok, if you can narrow it down to a specific plugin that might help us.

FYI, "use low Detail interface" shouldn't help with any crashes etc. all it does is reduce the complexity of some of the UI (shadows, gradients etc.) so it draws a bit quicker on older computers and feels a bit more responsive.