Computer restarts when exiting game

Toggle sidebar Toggle sidebar
S

Sikkan

Reputable
Dec 5, 2014
10
0
4,520
Hi,

My computer has been rebooting when I EXIT games. It doesn't happen all the time, so far it has done so 3 times. It's Kernel-Power critical error in the event viewer. No BSOD.

The first time I was playing battlefield 4, the second time I was playing assassins creed unity but it didn't happen immediately on exit, I started watching a VLC video right after playing and then it rebooted, and the third time it just rebooted immediately upon exiting the game (AC Unity).

I've been playing both games with no reboot upon exit too, so I'm not able to replicate it every time.

It seems to happen only when they computer has been under heavy load (only reboots after exiting game, never during or before so far). It has not happened when playing less intensive games like Left 4 Dead 2 or Dark Souls or other older games, even after hour-long sessions.

I tried turning off Intel Speedstep but didn't work.

Idle CPU temps are between 29c-32c, and 60c-64c under full load. Running Prime95 Small FFT for about 10-20 minutes it does not go above 75c. CPU cooler is CM Hyper Evo 212.

GPU idle temps for the bottom card is 35c-37c and about 69c under full load. Top card is hotter, idling at 43c-45c and around 79c under full load. Full load being 99% when playing AC Unity (not sure about bf4).

My system is brand new and I've not had it for a month even.
My specs are:

OS: Win 8.1 64-bit (all updates)
Processor: i5-4670K stock speed
GPU: MSI 970 Gaming 4G SLI (Latest drivers)
Motherboard: MSI Z97 Gaming 7
RAM: 16GB Kingston HyperX Black
HDDs: 240GB SSD, 750GB HDD, 1TB HDD
PSU: Corsair AX860 (Platinum)

Thoughts?
 
Solution
S
I think I solved the problem. Faulty surge protector. It died when I touched it accidentally with my foot.

I did plug in the PSU in another surge protector in my last post and kept everything else in the old one. Computer never restarted once I did that. But then when my old protector died and remembering the spark I think it was probably the culprit the whole time. So bought a new one and all seems fine so far.
Sort by date Sort by votes
S

Sikkan

Reputable
Dec 5, 2014
10
0
4,520
It happened again after exiting Assassins Creed Unity. Probably played a little under an hour.

Voltages as of this moment, while idle.

+5V = 5.000 V
+12V = 11.176 V
3VCC = 3.344 V

I can post max values after a gaming session if you like provided it doesn't reboot on me.
 
Upvote 0 Downvote
S

Sikkan

Reputable
Dec 5, 2014
10
0
4,520
I ran driver verifier and got an error from e22w8 something which apparently is my network driver. I reinstalled it and I'll report back if that fixed it. Any other suggestions on what it might be are still welcome.
 
Upvote 0 Downvote
S

Sikkan

Reputable
Dec 5, 2014
10
0
4,520
So I've played assassins creed unity a bit now and then both short and long sessions and it hasn't restarted on me as of yet when exiting. I'll have to try it out some more to be absolutely certain. I also opened the computer and reseated the 24 pin atx, it looked like it wasn't properly seated but I could be wrong.
 
Upvote 0 Downvote
S

Sikkan

Reputable
Dec 5, 2014
10
0
4,520
12v goes down to 11.000 while playing intensive games but this is from HWMonitor. I've read software voltage measurements are very unreliable so I'll try with a multimeter but I'll have to get one first.
 
Upvote 0 Downvote
A

ashleyriot1

Honorable
Jan 5, 2014
32
0
10,540
I was having the same problem. MSI tech support got back to me saying it could only be a problem caused by the motherboard. Though I doubted it, I replaced it and now problem solved. Try bread-boarding your system with a friends mobo perhaps? Hopefully its not the PSU - yours is much better than mine (cx500) Good luck
 
Upvote 0 Downvote
S

Sikkan

Reputable
Dec 5, 2014
10
0
4,520
So it after a long while without it happening at all it just did randomly while watching youtube videos, which it never has before.

I've been smelling a burning smell for brief moments. It's like a very very brief whiff I get all of a sudden (kinda like if you sat a dust bunny on fire) and seems to be coming from where the computer is, but when I go sniff the computer I smell nothing out of the ordinary. I even shut it down and open the case and sniff EVERYTHING but still nothing weird, feels like I'm going crazy. ALL temps are normal aswell I just don't get where it is coming from, if it even comes from the computer. There is a radiator close by but it smells of nothing. Gaah.

The computer works wonderfully for days and weeks and then just random kernel-power. I just can't replicate it, it's completely random. I switched outlet now so we'll see if it makes a difference. I remember my surge protector sparked kinda violently when I plugged in my screen I think when I first put everything together, but didn't think much of it. It's in a different surge protector in a different outlet now though.

Really concerned with the smell though. The weird thing is as I said I have sniffed every component and it just smells normal.

I should add that the 5v sometimes fluctuates between 5.000v and 5.040v.

ashleyriot1, how long has it been since you replaced it?

 
Upvote 0 Downvote
A

ashleyriot1

Honorable
Jan 5, 2014
32
0
10,540
That 5v rail looks fine. I've been using my new motherboard for about a week it's ok so far. I'm told it's caused by hardware stepping down after heavy use to conserve power but for some reason the voltage to the Gpu was cut too much after intensive use causing the card to power off. I found I was losing signal rather than power although a reboot always followed shortly after.
 
Upvote 0 Downvote
S

Sikkan

Reputable
Dec 5, 2014
10
0
4,520
I think I solved the problem. Faulty surge protector. It died when I touched it accidentally with my foot.

I did plug in the PSU in another surge protector in my last post and kept everything else in the old one. Computer never restarted once I did that. But then when my old protector died and remembering the spark I think it was probably the culprit the whole time. So bought a new one and all seems fine so far.
 
Upvote 0 Downvote
Solution
S

Sikkan

Reputable
Dec 5, 2014
10
0
4,520
So the problem is NOT solved. I have found out it's my nvidia drivers not responding causing a timeout detection and recovery error or TDR. Again it only ever happens after I have exited a game and then 5-10 seconds later boom, black screen and restart.

This is from a memory dump:


Microsoft (R) Windows Debugger Version 6.3.9600.17298 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\LiveKernelReports\WATCHDOG\WD-20150131-0811-04.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Symbol Path validation summary **************
Response Time (ms) Location
OK C:\localsymbols
Symbol search path is: C:\localsymbols
Executable search path is:
Windows 8 Kernel Version 9600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 9600.17476.amd64fre.winblue_r5.141029-1500
Machine Name:
Kernel base = 0xfffff803`72884000 PsLoadedModuleList = 0xfffff803`72b5d250
Debug session time: Sat Jan 31 08:11:22.266 2015 (UTC + 1:00)
System Uptime: 0 days 0:33:22.902
Loading Kernel Symbols
...............................................................
................................................................
........................
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 141, {ffffe0005242a250, fffff801523e781c, 0, 230}

Unable to load image nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+13e81c )

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

3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

VIDEO_ENGINE_TIMEOUT_DETECTED (141)
One of the the display engines failed to respond in timely fashion.
(This code can never be used for a real bugcheck.)
Arguments:
Arg1: ffffe0005242a250, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff801523e781c, The pointer into responsible device driver module (e.g owner tag).
Arg3: 0000000000000000, The secondary driver specific bucketing key.
Arg4: 0000000000000230, Optional internal context dependent data.

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


FAULTING_IP:
nvlddmkm+13e81c
fffff801`523e781c ?? ???

DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_ENGINE_TIMEOUT

TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b


CUSTOMER_CRASH_COUNT: 4

BUGCHECK_STR: 0x141

PROCESS_NAME: System

CURRENT_IRQL: 0

ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre

STACK_TEXT:
ffffd001`4e53a600 fffff801`51bfba94 : ffffe000`4e0ff000 ffffe000`5242a250 ffffd001`4e53a709 ffffe000`52779370 : watchdog!WdDbgReportRecreate+0x10c
ffffd001`4e53a650 fffff801`51ca4b13 : ffffd001`00000000 00000000`00000000 ffffd001`4e53a6d8 ffffe000`00000001 : dxgkrnl!TdrUpdateDbgReport+0xc0
ffffd001`4e53a6a0 fffff801`51ce8c23 : ffffe000`4e0fd000 00000000`00000000 00000000`00000001 ffffe000`4e0ff001 : dxgmms1!VidSchiResetEngine+0x427
ffffd001`4e53a770 fffff801`51cd9f48 : ffffd001`4e53a8a0 ffffe000`4e0fd000 00000000`00000102 ffffe000`4e0ff000 : dxgmms1!VidSchiResetEngines+0x83
ffffd001`4e53a7b0 fffff801`51cb61e9 : ffffe000`4e0fd000 ffffe000`4e0ff000 00000000`00000004 00000000`00000004 : dxgmms1!VidSchWaitForCompletionEvent+0x197d8
ffffd001`4e53a860 fffff801`51c8f928 : ffffe000`4e425c70 ffffe000`4e0ff000 ffffe000`4e4ec740 00000000`00000000 : dxgmms1!VidSchiWaitForCompletePreemption+0x7d
ffffd001`4e53a950 fffff801`51c95c89 : ffffe000`4e425c70 ffffe000`4e425c70 ffffd001`4e53aa90 ffffe000`4e0ff000 : dxgmms1!VidSchiCompletePreemption+0x28
ffffd001`4e53a990 fffff801`51ccbfb8 : ffffe000`4e0ff000 ffffe000`4e0ff000 ffffe000`4e425c70 ffffe000`00000000 : dxgmms1!VidSchiScheduleCommandToRun+0x679
ffffd001`4e53ab50 fffff801`51ccbf7d : ffffe000`4e0ff000 ffffe000`00000000 00000000`00000080 ffffe000`4e06c880 : dxgmms1!VidSchiRun_PriorityTable+0x38
ffffd001`4e53abc0 fffff803`72985440 : ffffd001`4f4682c0 ffffe000`4e06c880 ffffd001`4e53ac90 fffff803`729d7e7d : dxgmms1!VidSchiWorkerThread+0x8d
ffffd001`4e53ac00 fffff803`729db0c6 : ffffd001`4f45c180 ffffe000`4e06c880 ffffd001`4f4682c0 00000000`00000000 : nt!PspSystemThreadStartup+0x58
ffffd001`4e53ac60 00000000`00000000 : ffffd001`4e53b000 ffffd001`4e535000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
nvlddmkm+13e81c
fffff801`523e781c ?? ???

SYMBOL_NAME: nvlddmkm+13e81c

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 54b0548e

FAILURE_BUCKET_ID: 0x141_IMAGE_nvlddmkm.sys

BUCKET_ID: 0x141_IMAGE_nvlddmkm.sys

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x141_image_nvlddmkm.sys

FAILURE_ID_HASH: {4664cac2-c7ab-571c-719f-1f53c923c833}

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

 
Upvote 0 Downvote
S

Sikkan

Reputable
Dec 5, 2014
10
0
4,520
I think I finally solved the problem. I read the MSi forum and found a thread about my exact problem and apparently it has to do with SLI. Having been running in SLI all the time since putting the computer together I tried running single GPU mode and didn't crash. Someone solved the problem by simply moving the SLI bridge to the 2nd set of SLI ports, and this worked for me aswell.

Hopyfully it is permanently fixed now. If I don't reply to this thread again within one or two weeks, consider this problem solved.
 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom