Just a note to share I had multiple BSOD crashes with BI version 5.8.0.16 after updating yesterday. First BSOD just after midnight which was like 12 hours after upgrading to latest stable, a couple more crashes this morning when I started using the workstation. When viewing Windows mini dump file in WinDbg BlueIris.exe is the only problem process reported. Issues resolved at least so far by downgrading back to BI version 5.7.9.12. I suppose the crashes could be caused by a conflict with MalwareBytes premium, but I am not encountering crashes on earlier stable versions of BI5 with MalwareBytes premium running.
Just in case it helps....
Edition Windows 11 Pro for Workstations
Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz 3.60 GHz
64.0 GB (63.8 GB usable)
Version 22H2
Installed on 11/8/2022
OS build 22621.2715
Experience Windows Feature Experience Pack 1000.22677.1000.0
DUMP_FILE_ATTRIBUTES: 0x1808
Kernel Generated Triage Dump
READ_ADDRESS: fffff80554b1d470: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
unable to get nt!MmSpecialPagesInUse
0000000000000000
PROCESS_NAME: BlueIris.exe
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
TRAP_FRAME: fffffe8fd8876f00 -- (.trap 0xfffffe8fd8876f00)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=8020d5084b930000
rdx=000000000000009e rsi=0000000000000000 rdi=0000000000000000
rip=0000000000000000 rsp=fffffe8fd8877098 rbp=ffff9e013fe1c780
r8=00000000000000cc r9=0000000000000001 r10=0000000000000000
r11=fffffe8fd88775c0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz ac pe nc
00000000`00000000 ?? ???
Resetting default scope
IP_IN_FREE_BLOCK: 0
FAILED_INSTRUCTION_ADDRESS:
+0
STACK_TEXT:
fffffe8f`d8876db8 fffff805`5422bfa9 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000008 : nt!KeBugCheckEx
fffffe8f`d8876dc0 fffff805`54227634 : ffff8300`004eeff8 fffff805`54051795 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffffe8f`d8876f00 00000000`00000000 : 81000009`8c7de867 ffff8300`004efff8 fffff805`54050780 ffff9e01`3fe1c780 : nt!KiPageFault+0x474
SYMBOL_NAME: nt!KiPageFault+474
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
IMAGE_VERSION: 10.0.22621.2715
STACK_COMMAND: .cxr; .ecxr ; kb
BUCKET_ID_FUNC_OFFSET: 474
FAILURE_BUCKET_ID: AV_CODE_AV_NULL_IP_nt!KiPageFault
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {4ce35ff9-c5cf-d66d-0323-0f05e33f6692}
BSOD crashes with 5.8.0.16, stable with 5.7.9.12
Re: BSOD crashes with 5.8.0.16, stable with 5.7.9.12
Hi,
I'm assuming you have added the BI5 folder exceptions to Malwarebytes as stated in the BI5 help file.
I am running Malwarebytes premium with Win11 and BI5 v5.8.1.1 and am not having these issues.
I'm assuming you have added the BI5 folder exceptions to Malwarebytes as stated in the BI5 help file.
I am running Malwarebytes premium with Win11 and BI5 v5.8.1.1 and am not having these issues.
Forum Moderator.
Problem ? Ask and we will try to assist, but please check the Help file.
Problem ? Ask and we will try to assist, but please check the Help file.
Re: BSOD crashes with 5.8.0.16, stable with 5.7.9.12
Great reply. I didn't see that advice previously. I just allow-listed all my BI folders and executables to MalwareBytes. I will see if that helps with the next upgrade. Interestingly though I've been running without BI allow-listed in MB for years and not previously encountered obvious issues.
Re: BSOD crashes with 5.8.0.16, stable with 5.7.9.12
It appears the problem is something else and not recent BI release related. I reverted to previous BI stable version 5.7.9.12 when posting above. A few hours later I got another BSOD, this time the offending process in the Windows dump file was Blue Iris Tools .exe. I just allow-listed BI Tools to MalwareBytes premium as well. Will see if that repeats. These kinds of crashes seem like they could be antivirus/antimalware related. I haven't had any crashes or glitches in a couple years, but I'm leaning towards perhaps some recent MalwareBytes issue causing problems. Or a Windows update, but I haven't run any updates or installed new software manually recently...