BSOD from serviio

Had my win 7 machine BSOD after using serviio: here is the debug stack:


Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\070315-15256-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

WARNING: Inaccessible path: 'U:\bin\Spring\Lab\test\{develop}96.0.1-167-ge18b9de_spring_dbg'
Symbol search path is: SRV*c:\symbols\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is: U:\bin\Spring\Lab\test\{develop}96.0.1-167-ge18b9de_spring_dbg
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18869.amd64fre.win7sp1_gdr.150525-0603
Machine Name:
Kernel base = 0xfffff800`02262000 PsLoadedModuleList = 0xfffff800`024a9730
Debug session time: Fri Jul 3 13:46:04.587 2015 (UTC + 3:00)
System Uptime: 0 days 2:14:09.321
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck F4, {3, fffffa8005a0e880, fffffa8005a0eb60, fffff800025d9e20}

Probably caused by : _

Followup: MachineOwner
---------

3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

CRITICAL_OBJECT_TERMINATION (f4)
A process or thread crucial to system operation has unexpectedly exited or been
terminated.
Several processes and threads are necessary for the operation of the
system; when they are terminated (for any reason), the system can no
longer function.
Arguments:
Arg1: 0000000000000003, Process
Arg2: fffffa8005a0e880, Terminating object
Arg3: fffffa8005a0eb60, Process image file name
Arg4: fffff800025d9e20, Explanatory message (ascii)

Debugging Details:
------------------


PROCESS_OBJECT: fffffa8005a0e880

IMAGE_NAME: _

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MODULE_NAME: _

FAULTING_MODULE: 0000000000000000

PROCESS_NAME: ServiioService

BUGCHECK_STR: 0xF4_ServiioService

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff8000266c582 to fffff800022d68c0

STACK_TEXT:
fffff880`0a3b3b08 fffff800`0266c582 : 00000000`000000f4 00000000`00000003 fffffa80`05a0e880 fffffa80`05a0eb60 : nt!KeBugCheckEx
fffff880`0a3b3b10 fffff800`0262299b : ffffffff`ffffffff fffffa80`06807b50 fffffa80`05a0e880 fffffa80`03f74b10 : nt!PspCatchCriticalBreak+0x92
fffff880`0a3b3b50 fffff800`0258e26c : ffffffff`ffffffff 00000000`00000001 fffffa80`05a0e880 00000000`00000008 : nt! ?? ::NNGAKEGL::`string'+0x29d16
fffff880`0a3b3ba0 fffff800`022d5b53 : fffffa80`05a0e880 00000000`ffffffff fffffa80`06807b50 00000000`00000268 : nt!NtTerminateProcess+0xf4
fffff880`0a3b3c20 00000000`77a0de7a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`2941e808 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77a0de7a


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

FAILURE_BUCKET_ID: X64_0xF4_ServiioService_IMAGE__

BUCKET_ID: X64_0xF4_ServiioService_IMAGE__

Followup: MachineOwner
---------

[atc98092]

It's been so long since I've encountered a BSOD I had to look hard to see what crashed

It is certainly listing the Serviio service as what caught the crash, but I note the entry further down that mentions:

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

CURRENT_IRQL: 0

Don't you just love a driver identifying itself as a Vista driver on a Win 7 box?

BSOD is almost always related to a hardware/driver issue, typically the driver for something like a video card or drive interface. You might check to make sure everything is up to date and try Serviio again. I'm running Serviio on a box with an add-on SATA card as well as all the MB devices, including the on board graphics and sound. Never had an issue. Whatever caused your crash, Serviio was just the one that caught the final snap. I doubt it's anything specific to Serviio.