Wininit.exe

edisdaboss

Distinguished
Jun 14, 2010
8
0
18,510
I did the debug on my memory.dmp file and i have no idea how i got this but but i followed some website

I was reading then I got to the part where is says
"DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT"
mabye this is one of the reasons why my comp restarts randomly during the game play so let me know if this is normal or should i delete wininit.exe like most ppl say only I dont wanna make any wrong moves







*******************************************************************************
* *
* 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: 876dad40, Terminating object
Arg3: 876daeac, Process image file name
Arg4: 82a38d90, Explanatory message (ascii)

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


PROCESS_OBJECT: 876dad40

IMAGE_NAME: wininit.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MODULE_NAME: wininit

FAULTING_MODULE: 00000000

PROCESS_NAME: wininit.exe

EXCEPTION_CODE: (NTSTATUS) 0xc00000fd - A new guard page for the stack cannot be created.

BUGCHECK_STR: 0xF4_C00000FD

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

CURRENT_IRQL: 0

STACK_TEXT:
8f329c9c 82aec0d3 000000f4 00000003 876dad40 nt!KeBugCheckEx+0x1e
8f329cc0 82a6fe84 82a38d90 876daeac 876dafb0 nt!PspCatchCriticalBreak+0x71
8f329cf0 82a71d1f 876dad40 876d8520 c00000fd nt!PspTerminateAllThreads+0x2d
8f329d24 8285344a ffffffff c00000fd 0022fc7c nt!NtTerminateProcess+0x1a2
8f329d24 772d64f4 ffffffff c00000fd 0022fc7c nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
0022fc7c 00000000 00000000 00000000 00000000 0x772d64f4


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

FAILURE_BUCKET_ID: 0xF4_C00000FD_IMAGE_wininit.exe

BUCKET_ID: 0xF4_C00000FD_IMAGE_wininit.exe

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

1: kd> lmvm wininit
start end module name
1: kd> lmvm wininit
start end module name
1: kd> !process ffffffff876dad40 3
PROCESS 876dad40 SessionId: 0 Cid: 019c Peb: 7ffdd000 ParentCid: 0154
DirBase: ce8280a0 ObjectTable: 95503fc0 HandleCount: 4.
Image: wininit.exe
VadRoot 876b14a8 Vads 23 Clone 0 Private 219. Modified 277. Locked 0.
DeviceMap 8c408b10
Token 95501db0
ElapsedTime 00:00:00.343
UserTime 00:00:00.000
KernelTime 00:00:00.000
QuotaPoolUsage[PagedPool] 0
QuotaPoolUsage[NonPagedPool] 0
Working Set Sizes (now,min,max) (454, 50, 345) (1816KB, 200KB, 1380KB)
PeakWorkingSetSize 454
VirtualSize 9 Mb
PeakVirtualSize 9 Mb
PageFaultCount 727
MemoryPriority BACKGROUND
BasePriority 8
CommitCharge 234

THREAD 876d8520 Cid 019c.01a0 Teb: 7ffdf000 Win32Thread: 00000000 RUNNING on processor 1
 
WinInit.exe is a carry over from a Win9x scheme that was used on startup. WinInit.exe runs and looks for a file called WinInit.INI. If its found, it processes the commands found in this file. ,BUT if you have this file PLEASE download MalWareBytes and run mbam.exe on the entire computer
http://www.malwarebytes.org/
download the free version