Recurring BSODs on Blue Iris PC, "Memory Management"

S

Schrodinger's Cat

Young grasshopper
Nov 17, 2020
54
23
USA
This has happened 3 times now in the last week, I haven't been able to narrow down what action I'm doing that might cause it or if Blue Iris is related or not. The computer will BSOD with a stop code "MEMORY MANAGEMENT", count to 100% and "restart" and then lock up with a black screen and not actually restart. It will sit like this indefinitely, cams offline, until I power cycle it at which point it comes back as normal.

Most recently, it happened while scrolling through a video clip via UI3 on another PC. I do not recall the circumstances of the other crashes or if I was using it at the time.

It's a HP EliteDesk 800 SFF, i4 4590, 8GB RAM. It's run fantastically for 4 years and generally hums in the mid teens for CPU % and around 50% memory utilization. It usually runs headless but I've had a monitor plugged into it since this started happening, that's how I figured out it was BSODing (didn't even know what was going on the first time my cams were offline for a full day before I realized).

Has anybody dealt with such a problem?
 
  • Like
Reactions: mat200
Which version of Windows?
Any recent updates to Windows, video card driver or ????
 
  • Like
Reactions: mat200 and Flintstone61
Definitely check the version of your video card driver. Especially if it's Intel Integrated Graphics. Since a few years back, Microsoft switched video drivers to kernel mode, and believe it or don't, the specific version of Intel video driver you are currently using COULD possibly be the source of the BSOD.
 
  • Like
Reactions: mat200, Flintstone61 and TonyR
WIndows 10. I haven't done any recent updating or work on the computer. It generally sits out of sight out of mind and just runs Blue Iris.

It does have a video card which which processes images with DeepStack which is sent to it by AITool version 2.0.1206

I ran windows memory diagnostics as well as MemTest86 (USB boot). Both came back clean. I ran Chkdsk on all my drives, it seemed to do something, the event viewer logs for that are below.


Code: 
Checking file system on C:
The type of the file system is NTFS.


A disk check has been scheduled.
Windows will now check the disk.                         

Stage 1: Examining basic file system structure ...
  931840 file records processed.                                                         
File verification completed.
 Phase duration (File record verification): 12.48 seconds.
  43756 large file records processed.                                   
 Phase duration (Orphan file record recovery): 0.00 milliseconds.
  0 bad file records processed.                                     
 Phase duration (Bad file record checking): 0.73 milliseconds.

Stage 2: Examining file name linkage ...
  93784 reparse records processed.                                       
  1470644 index entries processed.                                                       
Index verification completed.
 Phase duration (Index verification): 59.17 seconds.
  0 unindexed files scanned.                                         
 Phase duration (Orphan reconnection): 9.63 seconds.
  0 unindexed files recovered to lost and found.                     
 Phase duration (Orphan recovery to lost and found): 10.39 seconds.
  93784 reparse records processed.                                       
 Phase duration (Reparse point and Object ID verification): 183.74 milliseconds.

Stage 3: Examining security descriptors ...
Cleaning up 3132 unused index entries from index $SII of file 0x9.
Cleaning up 3132 unused index entries from index $SDH of file 0x9.
Cleaning up 3132 unused security descriptors.
Security descriptor verification completed.
 Phase duration (Security descriptor verification): 125.22 milliseconds.
  269403 data files processed.                                           
 Phase duration (Data attribute verification): 0.83 milliseconds.
CHKDSK is verifying Usn Journal...
  40917784 USN bytes processed.                                                           
Usn Journal verification completed.
 Phase duration (USN journal verification): 270.00 milliseconds.
CHKDSK discovered free space marked as allocated in the volume bitmap.

Windows has made corrections to the file system.
No further action is required.

 249282556 KB total disk space.
 172194400 KB in 534150 files.
    461076 KB in 269404 indexes.
         0 KB in bad sectors.
   1059628 KB in use by the system.
     65536 KB occupied by the log file.
  75567452 KB available on disk.

      4096 bytes in each allocation unit.
  62320639 total allocation units on disk.
  18891863 allocation units available on disk.
Total duration: 1.54 minutes (92475 ms).


Code: 
Chkdsk was executed in read/write mode. 

Checking file system on F:
The type of the file system is NTFS.

Chkdsk cannot run because the volume is in use by another
process.  Chkdsk may run if this volume is dismounted first.
ALL OPENED HANDLES TO THIS VOLUME WOULD THEN BE INVALID.
Would you like to force a dismount on this volume? (Y/N) Volume dismounted.  All opened handles to this volume are now invalid.
Volume label is WD Purple.

Stage 1: Examining basic file system structure ...
  33280 file records processed.                                                         File verification completed.
 Phase duration (File record verification): 3.29 seconds.
  19627 large file records processed.                                     Phase duration (Orphan file record recovery): 0.00 milliseconds.
  0 bad file records processed.                                       Phase duration (Bad file record checking): 0.47 milliseconds.

Stage 2: Examining file name linkage ...
  53 reparse records processed.                                         33578 index entries processed.                                                        Index verification completed.
 Phase duration (Index verification): 575.28 milliseconds.
  0 unindexed files scanned.                                          Phase duration (Orphan reconnection): 7.50 milliseconds.
  0 unindexed files recovered to lost and found.                      Phase duration (Orphan recovery to lost and found): 1.75 milliseconds.
  53 reparse records processed.                                        Phase duration (Reparse point and Object ID verification): 2.29 milliseconds.

Stage 3: Examining security descriptors ...
Cleaning up 4 unused index entries from index $SII of file 0x9.
Cleaning up 4 unused index entries from index $SDH of file 0x9.
Cleaning up 4 unused security descriptors.
Security descriptor verification completed.
 Phase duration (Security descriptor verification): 15.32 milliseconds.
  149 data files processed.                                             Phase duration (Data attribute verification): 0.52 milliseconds.

Windows has scanned the file system and found no problems.
No further action is required.

   3815429 MB total disk space.
   3602760 MB in 7332 files.
      2988 KB in 151 indexes.
         0 KB in bad sectors.
    219771 KB in use by the system.
     65536 KB occupied by the log file.
 217550768 KB available on disk.

      4096 bytes in each allocation unit.
 976750079 total allocation units on disk.
  54387692 allocation units available on disk.
Total duration: 3.91 seconds (3917 ms).
 
clone that C drive, just in case things go wonky....
 
  • Like
Reactions: mat200 and TonyR
You must log in or register to reply here.
Top Bottom