Our batch job server runs approximately 70 jobs. It spontaneously rebooted yesterday. After analyzing the dump file, we determined that Visual Cron caused the fatal error. The previous post https://www.visualcron.c....aspx?g=posts&t=3389  reports this same issue. There is a response that version 5.7.7 fixed the bug causing the error. Apparently there is another bug that's caused the BSOD.

Details from .dmp file:
*******************************************************************************
* *
* 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: fffffa803b027530, Terminating object
Arg3: fffffa803b027810, Process image file name
Arg4: fffff800021d3600, Explanatory message (ascii)

Debugging Details:

---

ETW minidump data unavailable

DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 7601.23807.amd64fre.win7sp1_ldr.170512-0600

SYSTEM_MANUFACTURER: HP

SYSTEM_PRODUCT_NAME: ProLiant DL385 G7

SYSTEM_SKU: 573122-B21

BIOS_VENDOR: HP

BIOS_VERSION: A18

BIOS_DATE: 12/08/2012

DUMP_TYPE: 2

BUGCHECK_P1: 3

BUGCHECK_P2: fffffa803b027530

BUGCHECK_P3: fffffa803b027810

BUGCHECK_P4: fffff800021d3600

PROCESS_NAME: csrss.exe

CRITICAL_PROCESS: csrss.exe

EXCEPTION_CODE: (Win32) 0x22f8c210 (586727952) - <Unable to get error code text>

ERROR_CODE: (NTSTATUS) 0x22f8c210 - <Unable to get error code text>

CPU_COUNT: 18

CPU_MHZ: 9c4

CPU_VENDOR: AuthenticAMD

CPU_FAMILY: 10

CPU_MODEL: 9

CPU_STEPPING: 1

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT_SERVER

BUGCHECK_STR: 0xF4

CURRENT_IRQL: 0

ANALYSIS_SESSION_HOST: DMLYTEST

ANALYSIS_SESSION_TIME: 09-20-2017 09:46:30.0271

ANALYSIS_VERSION: 10.0.15063.468 amd64fre

STACK_TEXT:
fffff880`12388b18 fffff800`0225cec2 : 00000000`000000f4 00000000`00000003 fffffa80`3b027530 fffffa80`3b027810 : nt!KeBugCheckEx
fffff880`12388b20 fffff800`0221a75b : 00000000`00000001 fffffa80`22f8c210 fffffa80`3b027530 fffffa80`233b0001 : nt!PspCatchCriticalBreak+0x92
fffff880`12388b60 fffff800`02183a84 : 00000000`00000001 00000000`0003e0c4 fffffa80`3b027530 fffffa80`00000008 : nt! ?? ::NNGAKEGL::`string'+0x26fa6
fffff880`12388bb0 fffff800`01ec90d3 : 00000000`0003e0c4 fffffa80`22f8c210 fffffa80`3b027530 00000000`0003e0c4 : nt!NtTerminateProcess+0x284
fffff880`12388c20 00000000`77c4bffa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`2983e9e8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77c4bffa


STACK_COMMAND: kb

THREAD_SHA1_HASH_MOD_FUNC: e9460336222f4471d8ae88a3d24ad7df3aff8ef1

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 1ee52c215f4cc194e05204859a3549a3ac611ab4

THREAD_SHA1_HASH_MOD: f08ac56120cad14894587db086f77ce277bfae84

SYMBOL_NAME: ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME: Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP: 0

FAILURE_BUCKET_ID: X64_0xF4_csrss.exe_BUGCHECK_CRITICAL_PROCESS_TERMINATED_BY_VisualCronServ_22f8c210_ANALYSIS_INCONCLUSIVE

BUCKET_ID: X64_0xF4_csrss.exe_BUGCHECK_CRITICAL_PROCESS_TERMINATED_BY_VisualCronServ_22f8c210_ANALYSIS_INCONCLUSIVE

PRIMARY_PROBLEM_CLASS: X64_0xF4_csrss.exe_BUGCHECK_CRITICAL_PROCESS_TERMINATED_BY_VisualCronServ_22f8c210_ANALYSIS_INCONCLUSIVE

TARGET_TIME: 2017-09-19T18:32:00.000Z

OSBUILD: 7601

OSSERVICEPACK: 1000

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 18

PRODUCT_TYPE: 3

OSPLATFORM_TYPE: x64

OSNAME: Windows 7

OSEDITION: Windows 7 Server (Service Pack 1) Enterprise TerminalServer

OS_LOCALE:

USER_LCID: 0

OSBUILD_TIMESTAMP: 2017-05-12 10:49:14

BUILDDATESTAMP_STR: 170512-0600

BUILDLAB_STR: win7sp1_ldr

BUILDOSVER_STR: 6.1.7601.23807.amd64fre.win7sp1_ldr.170512-0600

ANALYSIS_SESSION_ELAPSED_TIME: 8b4

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:x64_0xf4_csrss.exe_bugcheck_critical_process_terminated_by_visualcronserv_22f8c210_analysis_inconclusive

FAILURE_ID_HASH: {51e51394-af7c-6bda-2da9-db061871c049}

Please make sure you run the latest build and have turned on Extended debugging. If it happens again we need the file log_serverDATE.txt along with the file time time it happened. Thank you!

---

Bad pool caller BSOD  errors can be fixed through various methods. One of the easiest methods is to delete the programs that you installed just now. In case you don't want to remove them, then it is best to shut them down and see in case the issue has been resolved or comes back. There are antivirus tools and other software that could be causing some trouble with another part of your PC, such as a driver, causing the 0xC2 error. In case this works to stop the BSOD, you have to look for another program. Another thing that can be done is to scan for hardware changes by launching Device Manager, right-clicking your PC at the top of the list, selecting Scan for hardware changes, and then going for rebooting. It will initiate Windows to check for drivers, but it might not run for all devices.