BSOD (Blue Screen of Death) crash using Sighthound

[CrazyFin]

Hi,

After I purchased the Pro license of Sighthound and started to use it more heavily I have started to see occasional reboots of my computer.

I am currently using 3 of the AXIS P3346-VE 3MP IP cameras on a quite good computer with:
Windows 7 Ultimate Pro 64 bit
Intel Core i5 3570K
32 GB RAM (Corsair CMX16GX3M2A1333C9)
Asus Z77 Pro3 mainboard with built in graphis Intel(R) HD Graphics 4000
Another graphics card NVIDIA GeForce 9600 GT from XFX Pine Group Inc
3 SSD disks: Corsair Force 3, KINGSTON SV300S37A60 and INTEL SS DSC2CT060A3
For storage of the videos I have a 2TB ST320005 42AS.

I did NOT have these reboots/crashes before installation of Sighthound.

I have now changed the system settings to get a true BSOD instead of reboot so I might be able to get more info when the next BSOD happens.

I just wanted to have a quick first check if you have any idea on where to start looking. (Graphics card drivers are up to date, checked with respectively video card graphics manufacturer.)

[ryan]

Sorry to hear you're experiencing blue screens on your machine. It should be impossible for an application like Sighthound Video to cause a blue screen, it does not have sufficient low level access on the system. It would instead be the ultimate actions of a driver or faulty hardware triggering the blue screen.

I'd first suggest making sure all of your drivers for every bit of your system are up to date including network cards, and then running system diagnostics if you haven't. Particularly a good memory test like http://www.memtest.org/

[ryan]

More information on how to potentially diagnose a crash dump to figure out what kernel module or driver may be at fault (assuming it isn't a hardware issue) can be found here: https://stackoverflow.com/questions/146 ... n-of-death

[CrazyFin]

Ok will of course run Memtest (I use Memtest86+) as one of the tests.

I also just updated my Nvidia drivers (eventhough it was just one month old).
The video card is Nvidia GeForce 9600 GT and driver version now is 337.88

I have had problems that no minidump file has been generated when I have gotten the BSOD:s but I suspect that this is due to the fact that I have set the paging file size manually and not letting Windows 7 to manage it automatically. I did get mini dumps previously BEFORE making changes to the paging file configurations.
I have now restored the default settings for the paging file and letting Windows manage them (which is the default setting).

Anyway, I had an older dump file from before I changed the paging file settings and it is definately Sighthound causing the crashes when I use WinDbg to analyze the file BUT it also looks like the system file "ntkrnlmp.exe" is involved. See some output from the WinDbg here (I have attached the dmp file as well):

Debugging Details:
------------------
BUGCHECK_STR: 0x1a_41284
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: Sighthound Age
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff80002f1c727 to fffff80002ec5bc0
STACK_TEXT:
fffff880`0b3497d8 fffff800`02f1c727 : 00000000`0000001a 00000000`00041284 00000000`1bbfa001 00000000`000127c4 : nt!KeBugCheckEx
fffff880`0b3497e0 fffff800`02ef6ef0 : fffff700`01080000 fc400007`58eac867 b8f00008`01f41c66 fffff680`0002de38 : nt! ?? ::FNODOBFM::`string'+0x4ad3
fffff880`0b349820 fffff800`02eb23df : fffffa80`00000000 00000000`1bc80fff 00000000`00000000 00000000`00000000 : nt!MiDeleteVirtualAddresses+0x4e8
fffff880`0b3499e0 fffff800`02ec4e53 : ffffffff`ffffffff 00000000`0008e320 00000000`0008e318 fffffa80`00008000 : nt!NtFreeVirtualMemory+0x61f
fffff880`0b349ae0 00000000`77b3149a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0008e2e8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77b3149a

STACK_COMMAND: kb
FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+4ad3
fffff800`02f1c727 cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+4ad3
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 531590fb
FAILURE_BUCKET_ID: X64_0x1a_41284_nt!_??_::FNODOBFM::_string_+4ad3
BUCKET_ID: X64_0x1a_41284_nt!_??_::FNODOBFM::_string_+4ad3
Followup: MachineOwner

[CrazyFin]

I have not been able to do full Memtest86+ yet (I am using the latest version from http://www.memtest.org/).

However, I did replace all memory sticks (4x8GB for a total of 32GB) with 2x8GB (total 16GB) with a totally different brand (HyperX HX316C10FWK2/16) and I haven´t had a BSOD (yet!) for a week.
Looks promising!

I will report back in about 1-2 weeks again to confirm if it has been stable during another 1-2 weeks.

Meanwhile I´ll test the 4 memorysticks (Corsair CMX16GX3M2A1333C9) thoroughly on another machine where I can run the Memtest86+ for 12-18 hours.

[ryan]

Glad to hear you might have narrowed down the problem. RAM is definitely a common cause of random kernel bluescreens, hopefully memtest turns something up and can let you know which stick is faulty.