Unsolved
This post is more than 5 years old
2 Posts
0
11967
February 14th, 2012 04:00
Optiplex 990 - Windows 7 Combo Cab BSOD
Hi Folks,
We are currently using SCCM 2007 SP3 to deploy to Dell Optiplex 990 workstations, and applying the following cab file: DT 1.0 (03/10/2011)
This is applied using a WMI query as per the readme, and applies succesfully.. however we appear to recieve random blue screens of death and cannot trace the cause other than a kernel error... Machines tend to last anything from 10 mins, up to a few weeks before BSOD's occur and I am starting to tear my hair out as it is like a ticking timebomb :(
The machines are configured with Intel AMT as disabled, and the SATA mode is set to "AHCI"
I have set the SATA mode in other configurations, but the error is still present
I have included two examples of the minidumps, but need advice on how to proceed?
Any assistance you can provide on this issue would be greatly appreciated :)
Bugcheck 1 - This includes our Syamantec Endpoint Protection client:
*******************************************************************************
* *
* 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: 00000003, Process
Arg2: 87ad6b18, Terminating object
Arg3: 87ad6c84, Process image file name
Arg4: 82c32d60, Explanatory message (ascii)
Debugging Details:
------------------
*** WARNING: Unable to verify timestamp for SYMEVENT.SYS
*** ERROR: Module load completed but symbols could not be loaded for SYMEVENT.SYS
PROCESS_OBJECT: 87ad6b18
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MODULE_NAME: smss
FAULTING_MODULE: 00000000
PROCESS_NAME: KillRegister.e
BUGCHECK_STR: 0xF4_KillRegister.e
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 82cf8159 to 82af8ef4
STACK_TEXT:
9f31dc18 82cf8159 000000f4 00000003 87ad6b18 nt!KeBugCheckEx+0x1e
9f31dc3c 82c75cdc 82c32d60 87ad6c84 87ad6d88 nt!PspCatchCriticalBreak+0x71
9f31dc6c 82c75c1f 87ad6b18 85a013c0 00000000 nt!PspTerminateAllThreads+0x2d
9f31dca0 91dc8a39 00000028 00000000 85fdbad0 nt!NtTerminateProcess+0x1a2
WARNING: Stack unwind information not available. Following frames may be wrong.
9f31dd24 82a5821a 00000028 00000000 0031b5d8 SYMEVENT+0x14a39
9f31dd24 00000028 00000028 00000000 0031b5d8 nt!KiFastCallEntry+0x12a
9f31dd94 00000000 772b70b4 0000001b 00000246 0x28
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: smss.exe
FAILURE_BUCKET_ID: 0xF4_KillRegister.e_IMAGE_smss.exe
BUCKET_ID: 0xF4_KillRegister.e_IMAGE_smss.exe
Followup: MachineOwner
---------
Bugcheck 2 - This is a fresh build without symantec:
*******************************************************************************
* *
* 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: 00000003, Process
Arg2: b71374a8, Terminating object
Arg3: b7137614, Process image file name
Arg4: 82c55d60, Explanatory message (ascii)
Debugging Details:
------------------
PROCESS_OBJECT: b71374a8
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MODULE_NAME: smss
FAULTING_MODULE: 00000000
PROCESS_NAME: KillRegister.e
BUGCHECK_STR: 0xF4_KillRegister.e
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 82d1b159 to 82b1bef4
STACK_TEXT:
d8013b9c 82d1b159 000000f4 00000003 b71374a8 nt!KeBugCheckEx+0x1e
d8013bc0 82c98cdc 82c55d60 b7137614 b7137718 nt!PspCatchCriticalBreak+0x71
d8013bf0 82c98c1f b71374a8 99362218 00000000 nt!PspTerminateAllThreads+0x2d
d8013c24 82a7b21a 00000028 00000000 0012b8c0 nt!NtTerminateProcess+0x1a2
d8013c24 775870b4 00000028 00000000 0012b8c0 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
0012b8c0 00000000 00000000 00000000 00000000 0x775870b4
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: smss.exe
FAILURE_BUCKET_ID: 0xF4_KillRegister.e_VRF_IMAGE_smss.exe
BUCKET_ID: 0xF4_KillRegister.e_VRF_IMAGE_smss.exe
Followup: MachineOwner
---------



cycletech
6 Posts
1
February 14th, 2012 09:00
Hello,
if you feel the BSOD issue is caused by the Symantec Endpoint Protection install, I suggest you open a case with support. Please be prepared to provide the full dump for analysis.
www.symantec.com/.../contact_techsupp_static.jsp
Best,
Thomas
Gomezie
2 Posts
0
February 15th, 2012 00:00
I am actually thinking the route cause is not actually Symantec.. hence why I included an dump file without Symantec present.... This is because a few identical machines using the same build crashed without symantec in place and had the same bugcheck string
The only thing thats tacked onto the SCCM task sequence after deployment is the SCCM client... I am wondering if the remote agent is having issues with the drivers being used in this combo cab.
These items appear to backup this theory:
social.technet.microsoft.com/.../b93f5a3e-9aba-47e7-9d81-c9757df75162
www.symantec.com/.../managed-sep-1105002333-32bit-and-windows-7-32bit-blue-screen-death