My blueiris system of 24 cameras keep crashing.
I have replaced the hard drive and power supply so far.
Not sure if blueiris is causing the issue but I have attached the crash logs.
What could be causing this?
I have replaced the hard drive and power supply so far.
Not sure if blueiris is causing the issue but I have attached the crash logs.
What could be causing this?
Code:System Information (local) Computer name: DESKTOP-HGL5G7L Windows version: Windows 10, 10.0, version 2009, build: 19045 (x64) Windows dir: C:\windows Hardware: MS-7D46, Micro-Star International Co., Ltd., PRO H610M-G DDR4 (MS-7D46) CPU: GenuineIntel 12th Gen Intel(R) Core(TM) i7-12700K 8664, level: 6 Processor count: 20 logical processors, active mask: 1048575 RAM: 16165.4MB Crash Dump Analysis Crash dumps are enabled on your computer. Crash dump directories: C:\Windows C:\Windows\Minidump On Thu 12/4/2025 9:20:53 AM your computer crashed or a problem was reported Crash dump file: C:\Windows\Minidump\120425-9187-01.dmp (Minidump) Bugcheck code: 0x3B(0xC0000005, 0xFFFFF80709F98B0B, 0xFFFFB68199C5EA10, 0x0) Bugcheck name: SYSTEM_SERVICE_EXCEPTION Driver or module in which error occurred: FLTMGR.SYS (FLTMGR+0x8B0B) File path: C:\windows\System32\drivers\FLTMGR.SYS Description: Microsoft Filesystem Filter Manager Product: Microsoft® Windows® Operating System Company: Microsoft Corporation Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code. Analysis: This is a typical software problem. Most likely this is caused by a bug in a driver. The crash took place in a file system driver. Since a problem was detected with a file system driver, it's suggested that you run CHKDSK to check your drive(s) for errors. On Thu 12/4/2025 9:20:53 AM your computer crashed or a problem was reported Crash dump file: C:\Windows\MEMORY.DMP (Kernel memory dump) Bugcheck code: 0x3B(0xC0000005, 0xFFFFF80709F98B0B, 0xFFFFB68199C5EA10, 0x0) Bugcheck name: SYSTEM_SERVICE_EXCEPTION Driver or module in which error occurred: FLTMGR.SYS (FLTMGR!FltPerformSynchronousIo+0x74B) File path: C:\windows\System32\drivers\FLTMGR.SYS Description: Microsoft Filesystem Filter Manager Product: Microsoft® Windows® Operating System Company: Microsoft Corporation Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code. Analysis: This is a typical software problem. Most likely this is caused by a bug in a driver. The crash took place in a file system driver. Since a problem was detected with a file system driver, it's suggested that you run CHKDSK to check your drive(s) for errors. On Wed 12/3/2025 4:14:11 PM your computer crashed or a problem was reported Crash dump file: C:\Windows\Minidump\120325-9265-01.dmp (Minidump) Bugcheck code: 0x1A(0x41792, 0xFFFF8B800080D828, 0x100000000000000, 0x0) Bugcheck name: MEMORY_MANAGEMENT Bug check description: This indicates that a severe memory management error occurred. Analysis: A corrupted PTE has been detected. This is possibly a software problem. This is a typical case of memory corruption. This bugcheck is often associated with overheating problems. Read this article on memory corruption. Read this article on thermal issues On Wed 12/3/2025 3:57:52 PM your computer crashed or a problem was reported Crash dump file: C:\Windows\Minidump\120325-10437-01.dmp (Minidump) Bugcheck code: 0x3B(0xC0000005, 0xFFFFFC90B5840825, 0xFFFF8F0E631AEAF0, 0x0) Bugcheck name: SYSTEM_SERVICE_EXCEPTION Driver or module in which error occurred: win32kfull.sys (win32kfull+0x160825) File path: C:\windows\System32\win32kfull.sys Description: Full/Desktop Win32k Kernel Driver Product: Microsoft® Windows® Operating System Company: Microsoft Corporation Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code. Analysis: This is a typical software problem. Most likely this is caused by a bug in a driver. Since there is no other responsible driver detected, it is suggested that you look for an updated driver for your graphics hardware. It's also possible that your graphics hardware was non-functional or overheated. On Wed 12/3/2025 3:36:02 PM your computer crashed or a problem was reported Crash dump file: C:\Windows\Minidump\120325-9843-01.dmp (Minidump) Bugcheck code: 0x1A(0x41792, 0xFFFF8900014AA758, 0x40000000000000, 0x0) Bugcheck name: MEMORY_MANAGEMENT Bug check description: This indicates that a severe memory management error occurred. Analysis: A corrupted PTE has been detected. This is possibly a software problem. This is a typical case of memory corruption. This bugcheck is often associated with overheating problems. Read this article on memory corruption. Read this article on thermal issues On Thu 11/27/2025 4:04:16 AM your computer crashed or a problem was reported Crash dump file: C:\Windows\LiveKernelReports\ResourceTimeout-20251127-0404.dmp (Kernel memory dump) Bugcheck code: 0x1CC(0xFFFFCB8DD693C8D0, 0xFFFFCB8DD6C82040, 0x2, 0x96) Bugcheck name: EXRESOURCE_TIMEOUT_LIVEDUMP Driver or module in which error occurred: (0xfffff806`12dac0d4) Bug check description: A kernel ERESOURCE has timed out. This can indicate a deadlock condition or heavy contention which can cause performance issues. Analysis: This is likely caused by a hardware problem, but there is a possibility that this is caused by a misbehaving driver. This bugcheck indicates that a timeout has occurred. This may be caused by a hardware failure such as a thermal issue or a bug in a driver for a hardware device. Read this article on thermal issues A full memory dump will likely provide more useful information on the cause of this particular bugcheck. The following dump file was found but appeared to be corrupt: C:\Windows\Minidump\120425-8421-01.dmp The following dump file was found but appeared to be corrupt: C:\Windows\LiveKernelReports\NDIS-20251201-1226.dmp Conclusion 8 crash dumps have been found and analyzed. Only 6 are included in this report. If one or more dump files were found that could not be analyzed, it means they are corrupted. It's an emergency measure for the system to write out a crash dump file and because of this, it's not uncommon for this process to fail. Often, but not always, it points to a problem in the storage stack. For instance, if the disk that should write out the crash dump file has failed, there will be no crash dump file written out. It is suggested that you run CHKDSK on your system drive to check your drive for errors. No offending third party drivers have been found. Consider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you. Read the suggestions displayed in the bugcheck analysis above. The analysis process took 0:00:08 (h:mm:ss).
Last edited:
