looks like GameGuard's npggNT64.des file is the possible culprit
Code:
Event[162]:
Log Name: Application
Source: Application Error
Date: 2012-07-10T18:43:31.000
Event ID: 1000
Task: Application Crashing Events
Level: Error
Opcode: Info
Keyword: Classic
User: N/A
User Name: N/A
Computer: TONY-PC
Description:
Faulting application name: wininit.exe, version: 6.1.7600.16385, time stamp: 0x4a5bc8c4
Faulting module name: npggNT64.des, version: 2011.10.10.1, time stamp: 0x4e924fe6
Exception code: 0xc0000005
Fault offset: 0x0000000000031e00
Faulting process id: 0x220
Faulting application start time: 0x01cd5f04ed82dc52
Faulting application path: C:\Windows\system32\wininit.exe
Faulting module path: c:\sg interactive\grand chase\GameGuard\npggNT64.des
Report Id: d1679207-caf9-11e1-a8ed-c80aa975f27f
Code:
1: 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: fffffa8006a633e0, Terminating object
Arg3: fffffa8006a636c0, Process image file name
Arg4: fffff80003193510, Explanatory message (ascii)
Debugging Details:
------------------
PROCESS_OBJECT: fffffa8006a633e0
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MODULE_NAME: wininit
FAULTING_MODULE: 0000000000000000
PROCESS_NAME: WerFault.exe
BUGCHECK_STR: 0xF4_WerFault.exe
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff8000321b892 to fffff80002e941c0
STACK_TEXT:
fffff880`037cfac8 fffff800`0321b892 : 00000000`000000f4 00000000`00000003 fffffa80`06a633e0 fffffa80`06a636c0 : nt!KeBugCheckEx
fffff880`037cfad0 fffff800`031c7e8b : ffffffff`ffffffff fffffa80`028822e0 fffffa80`06a633e0 fffffa80`02f4c060 : nt!PspCatchCriticalBreak+0x92
fffff880`037cfb10 fffff800`03146f74 : ffffffff`ffffffff 00000000`00000001 fffffa80`06a633e0 00000000`00000008 : nt! ?? ::NNGAKEGL::`string'+0x176d6
fffff880`037cfb60 fffff800`02e93453 : fffffa80`06a633e0 fffff880`000000ff fffffa80`028822e0 00000000`00000000 : nt!NtTerminateProcess+0xf4
fffff880`037cfbe0 00000000`76d015da : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0016d2d8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76d015da
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: wininit.exe
FAILURE_BUCKET_ID: X64_0xF4_WerFault.exe_IMAGE_wininit.exe
BUCKET_ID: X64_0xF4_WerFault.exe_IMAGE_wininit.exe
Followup: MachineOwner
---------
does your other application that uses gameguard have the same version of that npggNT64.des file?