Tried the hotfix, and unfortunately it did not help... According to the minidump vappcollector is listed as the culprit, which is a sub process of the SCCM client. We disabled the SMS Agent Host service and the crashing has stopped; We are now trying to determine why the SCCM client is crashing some PC's. Perhaps its time to open a thread in the System Center forums!

Win7 32bit PC's, several reports of this issue have come in since 6/22/11. All of the minidumps are almost identical. Anyone else having this issue? Microsoft (R) Windows Debugger Version 6.12.0002.633 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\softwareDump\062911-19593-02.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16792.x86fre.win7_gdr.110408-1633 Machine Name: Kernel base = 0x82a0c000 PsLoadedModuleList = 0x82b54810 Debug session time: Wed Jun 29 11:44:19.335 2011 (UTC - 4:00) System Uptime: 0 days 0:03:40.501 Loading Kernel Symbols ............................................................... ................................................................ ................... Loading User Symbols Loading unloaded module list ...... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1, {82c55513, 0, ffe4, 0} Probably caused by : ntkrpamp.exe ( nt!NtQueryInformationProcess+0 ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* APC_INDEX_MISMATCH (1) This is a kernel internal error. The most common reason to see this bugcheck is when a filesystem or a driver has a mismatched number of calls to disable and re-enable APCs. The key data item is the Thread->KernelApcDisable field. A negative value indicates that a driver has disabled APC calls without re-enabling them. A positive value indicates that the reverse is true. This check is made on exit from a system call. Arguments: Arg1: 82c55513, address of system function (system call) Arg2: 00000000, Thread->ApcStateIndex << 8 | Previous ApcStateIndex Arg3: 0000ffe4, Thread->KernelApcDisable Arg4: 00000000, Previous KernelApcDisable Debugging Details: ------------------ FAULTING_IP: nt!NtQueryInformationProcess+0 82c55513 68c4020000 push 2C4h CUSTOMER_CRASH_COUNT: 2 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x1 PROCESS_NAME: VAppCollector. CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from 77626344 to 82a4f7a3 STACK_TEXT: 9e40fd34 77626344 badb0d00 0024f548 00000000 nt!KiServiceExit2+0x17a WARNING: Frame IP not in any known module. Following frames may be wrong. 0024f560 00000000 00000000 00000000 00000000 0x77626344 STACK_COMMAND: .bugcheck ; kb FOLLOWUP_IP: nt!NtQueryInformationProcess+0 82c55513 68c4020000 push 2C4h SYMBOL_NAME: nt!NtQueryInformationProcess+0 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrpamp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4d9fd915 FAILURE_BUCKET_ID: 0x1_SysCallNum_ea_nt!NtQueryInformationProcess+0 BUCKET_ID: 0x1_SysCallNum_ea_nt!NtQueryInformationProcess+0 Followup: MachineOwner ---------

found the cause of the issue and a solution! The App-V Client was corrupted, causing the vAppCollector portion of the SCCM client to blow up. See this thread http://social.technet.microsoft.com/Forums/en-US/configmgrgeneral/thread/83f5d973-41e4-49a9-8f84-cfd2097a0996

Take a look at the Microsoft KB article on this error @ http://support.microsoft.com/kb/2203330Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.