PC restarts when playing games [Detailed]

[Guest]

My computer annoyingly restarts whenever I'm playing games.

My PC specs:

http://imgur.com/0tTJ6mi

OS: Windows 8 64bit

Motherboard: Gigabyte Technology Co., Ltd. GA-78LMT-USB3 (Socket M2)

GPU: V193W (1440x900@60Hz) 2048MB ATI AMD Radeon R9 200 Series (MSI)

PSU: Unsure but 700w (Gold)


I have had problems before this problem but sorted them out a few months ago when my computer combusted up because of the PSU (I don't think it was enought Watt)

My computer has been working fine since the previous problem which happend about 4 months ago.

It started happening about 2-3 days ago on the first day it was not as bad maybe happening once a day (of gaming) and didn't happen again


It is not overheating here are the Temps:
Before: http://imgur.com/Z6FjYX5
After playing for 1 minute: http://imgur.com/HrywXJE [CSGO]

How long it took to restart:

time: 04:38:31 m:s:ms [CSGO]
time: 02:41:57 [CSGO]

From what I've saw it's pretty random.
And only happens with demanding games like cs, and archeage
not with Hearthstone


My computer can be overclocked yes, but it isn't it's the way it came (Wasn't pre overclocked)
: http://imgur.com/PZdfGBb\

Might have missed out alot of information just tell me and I will add it to this.

Event Logs:

Spoiler

Happened before 41:

(Going from bottom to top)

The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

File System Filter 'npsvctrig' (6.2, ‎2012‎-‎07‎-‎26T03:27:33.000000000Z) has successfully loaded and registered with Filter Manager.

Volume C: (\Device\HarddiskVolume2) is healthy. No action is needed.

File System Filter 'FileInfo' (6.2, ‎2012‎-‎07‎-‎26T03:28:02.000000000Z) has successfully loaded and registered with Filter Manager.

The bootmgr spent 0 ms waiting for user input.

There are 0x1 boot options on this system.

The boot type was 0x0.

The last shutdown's success status was false. The last boot's success status was true.

The operating system started at system time ‎2014‎-‎09‎-‎18T15:14:06.487753900Z.

The system uptime is 17 seconds.

The Event log service was started.

After 41: (Different restart)

Processor 0 in group 0 exposes the following power management capabilities:

Idle state type: ACPI Idle (C) States (2 state(s))

Performance state type: ACPI Performance (P) / Throttle (T) States
Nominal Frequency (MHz): 3800
Maximum performance percentage: 100
Minimum performance percentage: 36
Minimum throttle percentage: 36

Processor 1 in group 0 exposes the following power management capabilities:

Idle state type: ACPI Idle (C) States (2 state(s))

Performance state type: ACPI Performance (P) / Throttle (T) States
Nominal Frequency (MHz): 3800
Maximum performance percentage: 100
Minimum performance percentage: 36
Minimum throttle percentage: 36

Processor 2 in group 0 exposes the following power management capabilities:

Idle state type: ACPI Idle (C) States (2 state(s))

Performance state type: ACPI Performance (P) / Throttle (T) States
Nominal Frequency (MHz): 3800
Maximum performance percentage: 100
Minimum performance percentage: 36
Minimum throttle percentage: 36

Processor 3 in group 0 exposes the following power management capabilities:

Idle state type: ACPI Idle (C) States (2 state(s))

Performance state type: ACPI Performance (P) / Throttle (T) States
Nominal Frequency (MHz): 3800
Maximum performance percentage: 100
Minimum performance percentage: 36
Minimum throttle percentage: 36

Volume \\?\Volume{e0c069ab-6d86-11e3-be65-806e6f6e6963} (\Device\HarddiskVolume1) is healthy. No action is needed.

Custom dynamic link libraries are being loaded for every application. The system administrator should review the list of libraries to ensure they are related to trusted applications. Please visit http://support.microsoft.com/kb/197571 for more information.

File System Filter 'luafv' (6.2, ‎2012‎-‎07‎-‎26T03:29:13.000000000Z) has successfully loaded and registered with Filter Manager.

The following boot-start or system-start driver(s) did not load:
dam

^^ I'm guessing that part does not look good.

Thanks in advance!

 

[thently]

Everytime I have ever had odd reboots like this it was power supply related. I would look into power supply the motherboard.. Not allot of other things can make computer reboot.

Thent

 

[dextermat]

+1 psu related problem.

But I would aslo look into malware:

Boot in safe mode and do a scan / cleanup with adwcleaner / rogukiller / junkware removal tool / malwarebytes

If you are heavily infected, run combofix

 

[HEXiT]

last reboot took over 4 mins? that normally points to software timing out. so you should have a log of the errors in the admin tools event viewer.
look in the logs and look for error 41. errors below it happend befor the restart, errors above it occured on the reboot.
post what you find.

 

[Guest]

last reboot took over 4 mins? that normally points to software timing out. so you should have a log of the errors in the admin tools event viewer.
look in the logs and look for error 41. errors below it happend befor the restart, errors above it occured on the reboot.
post what you find.

Yep, found it 41

Happened before 41:

(Going from bottom to top)

The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

File System Filter 'npsvctrig' (6.2, ‎2012‎-‎07‎-‎26T03:27:33.000000000Z) has successfully loaded and registered with Filter Manager.

Volume C: (\Device\HarddiskVolume2) is healthy. No action is needed.

File System Filter 'FileInfo' (6.2, ‎2012‎-‎07‎-‎26T03:28:02.000000000Z) has successfully loaded and registered with Filter Manager.

The bootmgr spent 0 ms waiting for user input.

There are 0x1 boot options on this system.

The boot type was 0x0.

The last shutdown's success status was false. The last boot's success status was true.

The operating system started at system time ‎2014‎-‎09‎-‎18T15:14:06.487753900Z.

The system uptime is 17 seconds.

The Event log service was started.

After 41: (Different restart)

Processor 0 in group 0 exposes the following power management capabilities:

Idle state type: ACPI Idle (C) States (2 state(s))

Performance state type: ACPI Performance (P) / Throttle (T) States
Nominal Frequency (MHz): 3800
Maximum performance percentage: 100
Minimum performance percentage: 36
Minimum throttle percentage: 36

Processor 1 in group 0 exposes the following power management capabilities:

Idle state type: ACPI Idle (C) States (2 state(s))

Performance state type: ACPI Performance (P) / Throttle (T) States
Nominal Frequency (MHz): 3800
Maximum performance percentage: 100
Minimum performance percentage: 36
Minimum throttle percentage: 36

Processor 2 in group 0 exposes the following power management capabilities:

Idle state type: ACPI Idle (C) States (2 state(s))

Performance state type: ACPI Performance (P) / Throttle (T) States
Nominal Frequency (MHz): 3800
Maximum performance percentage: 100
Minimum performance percentage: 36
Minimum throttle percentage: 36

Processor 3 in group 0 exposes the following power management capabilities:

Idle state type: ACPI Idle (C) States (2 state(s))

Performance state type: ACPI Performance (P) / Throttle (T) States
Nominal Frequency (MHz): 3800
Maximum performance percentage: 100
Minimum performance percentage: 36
Minimum throttle percentage: 36

Volume \\?\Volume{e0c069ab-6d86-11e3-be65-806e6f6e6963} (\Device\HarddiskVolume1) is healthy. No action is needed.

Custom dynamic link libraries are being loaded for every application. The system administrator should review the list of libraries to ensure they are related to trusted applications. Please visit http://support.microsoft.com/kb/197571 for more information.

File System Filter 'luafv' (6.2, ‎2012‎-‎07‎-‎26T03:29:13.000000000Z) has successfully loaded and registered with Filter Manager.

The following boot-start or system-start driver(s) did not load:
dam

^^ I'm guessing that part does not look good.

 

[Guest]

Help pls ;(

 

[HEXiT]

open regedit and look in this path...
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Windows
look for appinit_dll right click on the data tab if its not clear clear it. apply and reboot...
this will stop the api's loading the dlls. it may cause windows to fail to boot so make sure you create a restore point before you edit the registry.

 

[Guest]

open regedit and look in this path...
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Windows
look for appinit_dll right click on the data tab if its not clear clear it. apply and reboot...
this will stop the api's loading the dlls. it may cause windows to fail to boot so make sure you create a restore point before you edit the registry.

It is already clear
http://imgur.com/CzyWQ9B

 

[HEXiT]

then i would be looking at either possible malware. (quick scan with malwarebytes will catch most things) if you find something scan properly.
if not look at the psu...
normally i would recommend bluescreenviewer but the sites down atm. although you may be still able to get a copy off CNET.
it makes the crash log easier to read.
so if you want to try that and post the results... il have another look but im starting to think it may be an issue elsewhere.

 

[Guest]

then i would be looking at either possible malware. (quick scan with malwarebytes will catch most things) if you find something scan properly.
if not look at the psu...
normally i would recommend bluescreenviewer but the sites down atm. although you may be still able to get a copy off CNET.
it makes the crash log easier to read.
so if you want to try that and post the results... il have another look but im starting to think it may be an issue elsewhere.

1 minute in to scanning it found 250 threats but then my computer restarted so, yeah.
http://imgur.com/ZXUauny

306 now -.-

I had high hopes but it lasted 6:19 ;(
Okay, it now lasted 25:17 which is a vast improvement
and I have realised both times have crashed when I've tabbed out (and one previous but I wasn't tracking)

 

[HEXiT]

250+ threats means potentially a dead o.s effectivley infected down to the core.
so unless your really confident in your scanner i would say forget repairing just fresh install...

if you are gonna spend the next 6-10 hours repairing, make sure you run sfc /scannow from the run bar to repair the base elements of your o.s. before you do anything. it can save a lot of work later on.

 

[opusminus]

Resolved post...please delete this post =)