PC restarts during game play

I been having this problem for while now, it started when i put new ram, my computer would restart durring the game play, so i put my old ram back and same problem so it doesnt look like ram, I can be on comp watching you tube all day and it would not shuts down or restart so in my opinion its not PSU, I ran few stress tests and nothing works fine, I really wanna get to bottom of this so i can enjoy my game times insted of being pissed. All the temps seems right just the CPU runs at 60 on stock speeds, I have reinstalled heatsink I have dusted the case, I have checked my event log and I do have Kernel-Power event 41 error,and thats the only critical,
My guess is Video card so i have concated Nevida for help and they told me same old bull reinstall drivers and did all that and they are asuming that its PSU if its PSU then it would shut down i left comp 2 days and never turned off, It only restarts when I play games i can play somethimes 3 hours and its fine after restart another 10-20 min I really cant tell , SO if you guys can help me out , it would be nice

my built
CPU:E8550
ram:i think pirtate Gseris 2x2gb=4gb mem
mother board: GIGABYTE GA-X48-DS4
PSU:antec 850w
Video card: GTX 275
6 answers Last reply
More about restarts game play
  1. Remove the video card & then try playing through on-board graphics. Post back the results.
  2. Agreed: First place to check is without the GFX card. There's a certain range of Nvidia cards that I know several people who had troubles with them, namely that the fan had failed. For low-resource things, they weren't having any problems, but as soon as they kicked into highgear, it would insta-overheat and fail.

    Two other things to check:

    1. You mentioned removing/replacing the heatsink. Did you remember to apply fresh thermal paste?

    2. PSU could be getting flakey and failing under high draw.
  3. yea it might be your graphics card becuase its turning off from something overheating so either your graphics card fan (if it has one is broken like mine did) or your cpu is overheating
  4. also i was looking at my event loger and memory.DMb

    *******************************************************************************
    * *
    * 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
  5. the_crippler said:
    Agreed: First place to check is without the GFX card. There's a certain range of Nvidia cards that I know several people who had troubles with them, namely that the fan had failed. For low-resource things, they weren't having any problems, but as soon as they kicked into highgear, it would insta-overheat and fail.

    Two other things to check:

    1. You mentioned removing/replacing the heatsink. Did you remember to apply fresh thermal paste?

    2. PSU could be getting flakey and failing under high draw.



    Yes I put new fresh thermal paste
  6. Wininit.exe is an essential background process.When it fails then there is something seriously wrong with your system.Since when is this problem happening?.If its happening of late then run a virus scan.Some worms target wininit.exe.If you're sure its not a virus then try and run system restore.
Ask a new question

Read More

PC gaming Games RAM Video Games