Bias fx 2 crash windows 11
-
Hey all,
I have been using bias fx 2 as both standalone and as a vst in daw's.
But i've just built a new pc 6 month back and installed windows 11, and the application keeps crashing (bsod), when i try to use it both from standalone version but also from daw's.It happens when the application tries to open, it stays a little while on the loading screen, then it just goes to blue screen of death (bsod).
I have tried deleting the folders which has already been suggested by Positive grid, the %appdata%/positive grid one and such.
SETUP
Audio Interface: Motu m2.
Processor: Amd ryzen 7 5800x
GPU: Nvidia geforce rtx 3060 tiCrash dump
******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* KERNEL_SECURITY_CHECK_FAILURE (139) A kernel component has corrupted a critical data structure. The corruption could potentially allow a malicious user to gain control of this machine. Arguments: Arg1: 0000000000000003, A LIST_ENTRY has been corrupted (i.e. double remove). Arg2: fffff680cc4a7840, Address of the trap frame for the exception that caused the BugCheck Arg3: fffff680cc4a7798, Address of the exception record for the exception that caused the BugCheck Arg4: 0000000000000000, Reserved Debugging Details: ------------------ KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 1984 Key : Analysis.DebugAnalysisManager Value: Create Key : Analysis.Elapsed.mSec Value: 6978 Key : Analysis.Init.CPU.mSec Value: 764 Key : Analysis.Init.Elapsed.mSec Value: 11831 Key : Analysis.Memory.CommitPeak.Mb Value: 95 Key : Bugcheck.Code.DumpHeader Value: 0x139 Key : Bugcheck.Code.KiBugCheckData Value: 0x139 Key : Bugcheck.Code.Register Value: 0x139 Key : Dump.Attributes.AsUlong Value: 1000 Key : FailFast.Name Value: CORRUPT_LIST_ENTRY Key : FailFast.Type Value: 3 Key : WER.OS.Branch Value: co_release Key : WER.OS.Timestamp Value: 2021-06-04T16:28:00Z Key : WER.OS.Version Value: 10.0.22000.1 FILE_IN_CAB: MEMORY.DMP DUMP_FILE_ATTRIBUTES: 0x1000 BUGCHECK_CODE: 139 BUGCHECK_P1: 3 BUGCHECK_P2: fffff680cc4a7840 BUGCHECK_P3: fffff680cc4a7798 BUGCHECK_P4: 0 TRAP_FRAME: fffff680cc4a7840 -- (.trap 0xfffff680cc4a7840) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=ffffa984e608d788 rbx=0000000000000000 rcx=0000000000000003 rdx=ffffa984e608d780 rsi=0000000000000000 rdi=0000000000000000 rip=fffff8016c63f465 rsp=fffff680cc4a79d0 rbp=fffff680cc4a7a88 r8=ffffa984e567ccc0 r9=fffff8016c200000 r10=0000000000000000 r11=ffff930ebb3ea740 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz na po cy nt!KiWakeQueueWaiter+0x1c2825: fffff801`6c63f465 cd29 int 29h Resetting default scope EXCEPTION_RECORD: fffff680cc4a7798 -- (.exr 0xfffff680cc4a7798) ExceptionAddress: fffff8016c63f465 (nt!KiWakeQueueWaiter+0x00000000001c2825) ExceptionCode: c0000409 (Security check failure or stack buffer overrun) ExceptionFlags: 00000001 NumberParameters: 1 Parameter[0]: 0000000000000003 Subcode: 0x3 FAST_FAIL_CORRUPT_LIST_ENTRY PROCESS_NAME: NisSrv.exe ERROR_CODE: (NTSTATUS) 0xc0000409 - The system detected an overrun of a stack-based buffer in this application. This overrun could potentially allow a malicious user to gain control of this application. EXCEPTION_CODE_STR: c0000409 EXCEPTION_PARAMETER1: 0000000000000003 EXCEPTION_STR: 0xc0000409 STACK_TEXT: fffff680`cc4a7518 fffff801`6c62d9a9 : 00000000`00000139 00000000`00000003 fffff680`cc4a7840 fffff680`cc4a7798 : nt!KeBugCheckEx fffff680`cc4a7520 fffff801`6c62ddf2 : 00000000`00000000 00000000`00000000 00000000`00000000 ffffa984`e5448710 : nt!KiBugCheckDispatch+0x69 fffff680`cc4a7660 fffff801`6c62c0d2 : ffffa984`e5448710 00000000`00000000 ffffa984`ebcc0500 000000d7`24f7f908 : nt!KiFastFailDispatch+0xb2 fffff680`cc4a7840 fffff801`6c63f465 : ffffa984`e61130c0 00000000`00000001 ffffa984`d0ef7820 00000000`00000001 : nt!KiRaiseSecurityCheckFailure+0x312 fffff680`cc4a79d0 fffff801`6c47bfc8 : fffff680`cc4a7a88 ffffa984`e608d780 ffffa984`e608d780 ffffa984`e608d788 : nt!KiWakeQueueWaiter+0x1c2825 fffff680`cc4a7a20 fffff801`6c62d378 : ffffa984`e6108080 ffffa984`e18b6d00 000001ea`51226bf8 00000000`00000000 : nt!NtReleaseWorkerFactoryWorker+0x238 fffff680`cc4a7aa0 00007ffe`02286a74 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28 000000d7`24c7a8a8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffe`02286a74 SYMBOL_NAME: nt!KiFastFailDispatch+b2 MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe STACK_COMMAND: .cxr; .ecxr ; kb BUCKET_ID_FUNC_OFFSET: b2 FAILURE_BUCKET_ID: 0x139_3_CORRUPT_LIST_ENTRY_nt!KiFastFailDispatch OS_VERSION: 10.0.22000.1 BUILDLAB_STR: co_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {3aede96a-54dd-40d6-d4cb-2a161a843851} Followup: MachineOwner -
@emil-rauff-andersen said in Bias fx 2 crash windows 11:
OSNAME: Windows 10 OS_VERSION: 10.0.22000.1
Did you upgrade your windows 10, to Windows 11?
Crash report lists "OSNAME: Windows 10"
May have been an issue with the upgrade to your PC.. If it was an upgrade, you may need to back up all data, format the drive and get a fresh install of just windows 11..
-
@emil-rauff-andersen said in Bias fx 2 crash windows 11:
0x139_3_CORRUP
I think you have Windows Operating system issues.
-
@compman67 Hey compman67 thank you for taking the time to answer.
The windows installation is a clean installation of windows 11. The version you refer to is still w11
https://docs.microsoft.com/en-us/answers/questions/586619/windows-11-build-ver-is-still-10022000194.htmlAs for the corruption of the data, i have no clue as to what caused it, says the process NisSrv.exe caused it, but that is the microsoft defender realtime inspection.
Could it be because i don't have a integrated graphic card, and therefore it fails to load GUI?
-
@emil-rauff-andersen
Got the application able to not bsod my computer, when i deactivated my windows defender, and used reaper to load the vst. Seems like realtime virus protection didn't want to cooperate with bias.Now bias fx 2 is stuck on the loading screen, but the audio goes through with effects. Tried to delete the relative folders /documents/positive grid & /%appdata%/positive grid and launch the application again same result.
image of stuck loading screen -
Okay, I get it...
NisSrv.exe
"Older""Not officially part of windows"
That explains why it shows Windows 10 in the logs you posted..
"If you’ve opened Task Manager in Windows, you might see some process and wonder what they are doing. Here’s a look at NisSrv.exe, why it’s running, and if it’s safe.
NisSrv.exe is also known as Microsoft NetworkRealtime Inspection Service. That’s a fancy way of saying that is part of Microsoft Malware Protection or Microsoft Security Essentials on older PCs.
The software is created by Microsoft and is known to be safe. However, it can cause issues with your computer and cause slowness if it gets corrupted.
It’s not “officially” part of Windows, but it is important. On older systems you should be able to find it in the subdirectory C:\Program Files. It does not appear on the taskbar and does not need to be visible by Windows. If you don’t want it, you can use Control Panel to completely remove it. However, it is known to be safe and an important part of your malware protection on Windows 7 machines still running MSE. You won’t find it in Windows 10."
-
