Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Kernel error, computer freezes while playing games.


  • Please log in to reply
6 replies to this topic

#1 Tsarkyyy

Tsarkyyy

  • Members
  • 8 posts
  • OFFLINE
  •  

Posted 26 March 2018 - 11:01 AM

To start things off, i assemble this computer myself. After first few months im getting a notification while booting saying something like "Incorrect reboot due to power surge" or something like that.
I can't replicate that, but i think it says something but i ignored it and computer was running fine... until recently.

I was playing Warframe. Did a certain mission and computer freezes! Audio slips through a little but after that, nothing responds anymore. I have to manually reboot. 
Every time i play this, my computer freezes within 5-10 mins. 

I've looking around and thinking how to fix this. I've tried a few things but nothing helps.

I do notice that in the eventvwr, the kernel error keeps popping up with a chain of events after that on light load
But it crashes on heavy load when i play a game like Warframe.
Somehow this does not happen when i play a indie game called 7 Days to Die (alpha state) It's known it has memory leak but does not crash the computer.

I'm thinking the PSU is the culprit. Its a EVGA 500B and just recently got in contact with service provider
Currently ongoing. Had to check for fluctuations on 12V in Bios.... No fluctuations AFAIK

My Specs :
http://speccy.piriform.com/results/aLEnbO56NpBQmqni4riwXBJ

And my Sysnatives are in the attachment.

I really hope you guys can help me troubleshoot this, This system is only a year old......

 

Attached Files



BC AdBot (Login to Remove)

 


#2 Tsarkyyy

Tsarkyyy
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  

Posted 28 March 2018 - 04:38 AM

EDIT : These are my specs

 

PSU : EVGA 500B

CPU : Intel Core i5-7500

Motherboard : MSI H270 Gaming M3

Memory : 1x Corsair Vengeance LPX - DDR4-2400 - 8GB

GPU : Asus STRIX-RX470-O4G-GAMING

 

 

 

I've done some troubleshooting and came up with the following results :
 

 

WhoCrashed
 

crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: atikmpag.sys (0xFFFFF8075F89F7E8) 
Bugcheck code: 0x116 (0xFFFF8181930E34A0, 0xFFFFF8075F89F7E8, 0xFFFFFFFFC0000001, 0x3)
Error: VIDEO_TDR_ERROR
file path: C:\WINDOWS\System32\DriverStore\FileRepository\c0324524.inf_amd64_0d186b68c5ea1772\atikmpag.sys
product: AMD driver
company: Advanced Micro Devices, Inc.
description: AMD multi-vendor Miniport Driver
Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed. 
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: atikmpag.sys (AMD multi-vendor Miniport Driver, Advanced Micro Devices, Inc.).

 

 

Windows Debugging Tool

 

Microsoft ® Windows Debugger Version 10.0.16299.15 AMD64

Copyright © Microsoft Corporation. All rights reserved.
 
 
Loading Dump File [C:\Windows\Minidump\032818-23796-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
 
Symbol search path is: srv*
Executable search path is: 
Windows 10 Kernel Version 16299 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 16299.15.amd64fre.rs3_release.170928-1534
Machine Name:
Kernel base = 0xfffff801`2ae9d000 PsLoadedModuleList = 0xfffff801`2b204130
Debug session time: Wed Mar 28 09:04:03.579 2018 (UTC + 2:00)
System Uptime: 0 days 8:24:18.202
Loading Kernel Symbols
...............................................................
................................................................
...............................................
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
 
Use !analyze -v to get detailed debugging information.
 
BugCheck 116, {ffff8181930e34a0, fffff8075f89f7e8, ffffffffc0000001, 3}
 
Unable to load image \SystemRoot\System32\DriverStore\FileRepository\c0324524.inf_amd64_0d186b68c5ea1772\atikmpag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : atikmpag.sys ( atikmpag+f7e8 )
 
Followup:     MachineOwner
---------
 
2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
 
VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: ffff8181930e34a0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8075f89f7e8, The pointer into responsible device driver module (e.g. owner tag).
Arg3: ffffffffc0000001, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000003, Optional internal context dependent data.
 
Debugging Details:
------------------
 
 
DUMP_CLASS: 1
 
DUMP_QUALIFIER: 400
 
BUILD_VERSION_STRING:  10.0.16299.309 (WinBuild.160101.0800)
 
SYSTEM_MANUFACTURER:  MSI
 
SYSTEM_PRODUCT_NAME:  MS-7A62
 
SYSTEM_SKU:  Default string
 
SYSTEM_VERSION:  1.0
 
BIOS_VENDOR:  American Megatrends Inc.
 
BIOS_VERSION:  2.60
 
BIOS_DATE:  01/25/2018
 
BASEBOARD_MANUFACTURER:  MSI
 
BASEBOARD_PRODUCT:  H270 GAMING M3 (MS-7A62)
 
BASEBOARD_VERSION:  1.0
 
DUMP_TYPE:  2
 
BUGCHECK_P1: ffff8181930e34a0
 
BUGCHECK_P2: fffff8075f89f7e8
 
BUGCHECK_P3: ffffffffc0000001
 
BUGCHECK_P4: 3
 
FAULTING_IP: 
atikmpag+f7e8
fffff807`5f89f7e8 48895c2408      mov     qword ptr [rsp+8],rbx
 
DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
 
CPU_COUNT: 4
 
CPU_MHZ: d50
 
CPU_VENDOR:  GenuineIntel
 
CPU_FAMILY: 6
 
CPU_MODEL: 9e
 
CPU_STEPPING: 9
 
CPU_MICROCODE: 6,9e,9,0 (F,M,S,R)  SIG: 70'00000000 (cache) 70'00000000 (init)
 
CUSTOMER_CRASH_COUNT:  1
 
BUGCHECK_STR:  0x116
 
PROCESS_NAME:  System
 
CURRENT_IRQL:  0
 
ANALYSIS_SESSION_HOST:  DESKTOP-2EVV72P
 
ANALYSIS_SESSION_TIME:  03-28-2018 09:10:25.0227
 
ANALYSIS_VERSION: 10.0.16299.15 amd64fre
 
STACK_TEXT:  
ffffa10e`77827918 fffff807`5f32ce10 : 00000000`00000116 ffff8181`930e34a0 fffff807`5f89f7e8 ffffffff`c0000001 : nt!KeBugCheckEx
ffffa10e`77827920 fffff807`5f2f7059 : fffff807`5f89f7e8 ffff8181`935cc0a0 ffff8181`935cc170 00000000`00000000 : dxgkrnl!TdrBugcheckOnTimeout+0xec
ffffa10e`77827960 fffff807`5f2f7b75 : ffff8181`930e01a0 00000000`10000000 ffff8181`935cc0a0 00000000`10000000 : dxgkrnl!DXGADAPTER::PrepareToReset+0x159
ffffa10e`778279b0 fffff807`5f32c5a5 : 00000002`00000100 00000000`00000000 00000000`00000000 ffff8181`945bc040 : dxgkrnl!DXGADAPTER::Reset+0x229
ffffa10e`77827a20 fffff807`5f32c6f7 : 00000000`00000300 ffff8181`955f6e38 ffff8181`8e32fd20 fffff807`5eba2330 : dxgkrnl!TdrResetFromTimeout+0x15
ffffa10e`77827a50 fffff801`2aed84d5 : ffff8181`945bc040 fffff807`5f32c6d0 ffff8181`8e32fd20 00000000`000004c8 : dxgkrnl!TdrResetFromTimeoutWorkItem+0x27
ffffa10e`77827a80 fffff801`2afb3c07 : ffff8181`945bc040 00000000`00000080 ffff8181`8e2d3040 ffff8181`945bc040 : nt!ExpWorkerThread+0xf5
ffffa10e`77827b10 fffff801`2b019cc6 : ffffba00`126a0180 ffff8181`945bc040 fffff801`2afb3bc0 00000000`00000246 : nt!PspSystemThreadStartup+0x47
ffffa10e`77827b60 00000000`00000000 : ffffa10e`77828000 ffffa10e`77821000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
 
 
THREAD_SHA1_HASH_MOD_FUNC:  3aa6aac2005fb728aff349df2b5f504893184b97
 
THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  1ab971779083cc77f0ce40ee82015486869b0d0f
 
THREAD_SHA1_HASH_MOD:  3225689ea8bf23dca00cdfd517975e0703e07271
 
FOLLOWUP_IP: 
atikmpag+f7e8
fffff807`5f89f7e8 48895c2408      mov     qword ptr [rsp+8],rbx
 
FAULT_INSTR_CODE:  245c8948
 
SYMBOL_NAME:  atikmpag+f7e8
 
FOLLOWUP_NAME:  MachineOwner
 
MODULE_NAME: atikmpag
 
IMAGE_NAME:  atikmpag.sys
 
DEBUG_FLR_IMAGE_TIMESTAMP:  5a8b7461
 
STACK_COMMAND:  .thread ; .cxr ; kb
 
FAILURE_BUCKET_ID:  0x116_IMAGE_atikmpag.sys
 
BUCKET_ID:  0x116_IMAGE_atikmpag.sys
 
PRIMARY_PROBLEM_CLASS:  0x116_IMAGE_atikmpag.sys
 
TARGET_TIME:  2018-03-28T07:04:03.000Z
 
OSBUILD:  16299
 
OSSERVICEPACK:  309
 
SERVICEPACK_NUMBER: 0
 
OS_REVISION: 0
 
SUITE_MASK:  272
 
PRODUCT_TYPE:  1
 
OSPLATFORM_TYPE:  x64
 
OSNAME:  Windows 10
 
OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS
 
OS_LOCALE:  
 
USER_LCID:  0
 
OSBUILD_TIMESTAMP:  2018-03-01 06:36:55
 
BUILDDATESTAMP_STR:  160101.0800
 
BUILDLAB_STR:  WinBuild
 
BUILDOSVER_STR:  10.0.16299.309
 
ANALYSIS_SESSION_ELAPSED_TIME:  1d97
 
ANALYSIS_SOURCE:  KM
 
FAILURE_ID_HASH_STRING:  km:0x116_image_atikmpag.sys
 
FAILURE_ID_HASH:  {e300aa8c-6915-3f37-7957-d2e4fc30a6fd}
 
Followup:     MachineOwner
---------

 

 

The VIDEO_TDR_ ERROR bug check has a value of 0x00000116. This indicates that an attempt to reset the display driver and recover from a timeout failed. Which could be the case since the computer just hangs and display doesn't respond.

 

Possible causes (with comments):

 

  • Over-clocked components, such as the motherboard 
    (Doesn't have any overclocks)
  • Incorrect component compatibility and settings (especially memory configuration and timings)
    (Have to double check that but I doubt it, Have to run some diagnostics like Memtest86)
  • Insufficient system cooling
    (CPU, GPU etc. have nominal readings. Under stress CPU doesn't go above 30-35C, GPU not higher then 50-55C)
  • Insufficient system power
    This I can agree with but i want to verify this before I spend 120EUR on a new PSU, was thinking of a Corsair RM750x, unless someone can suggest me a cheaper one)
  • Defective parts (memory modules, motherboards, etc.)
    This is the last thing I want to think about since the system is only a year old, luckily I got warranty on all hardware parts, the downside is that I have to warrant this directly to the manufacturer since my retailer got bankrupt, no re-launch or rescue from bankruptcy

Couple of things I did as well is :
 

Driver Verifier :
Left it running for at least 24 hours, no BSODs. So i'm thinking, its not the drivers then, can it?

 

Chkdsk :

Had a couple of errors while scanning, ran through it last night on boot with chkdsk /f /r

Booted fine the next morning, didn't touch the power button

 

 

Suggestions and/or feedback are very welcome!

 

Is there anything else i can do to fix this problem?

Or is there some1 who could walk me through it?


Edited by Tsarkyyy, 28 March 2018 - 04:44 AM.


#3 Tsarkyyy

Tsarkyyy
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  

Posted 28 March 2018 - 03:52 PM

Another thing i noticed with OCCT http://www.ocbase.com/

My CPU should NOT be able to get overclocked. But according to this https://imgur.com/erFmoPH, i got up to 3,8 ghz instead of 3,4 ghz
Also if you look at voltages (VIN8) fluctuate heavily between 0,7V - 1.08V
Found somewhere that it controles CPU voltage, correct me if i am wrong.

What can I do?



#4 bwv848

bwv848

    Bleepin' Owl


  • BSOD Kernel Dump Expert
  • 3,011 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:92.96 million miles away from the sun
  • Local time:03:21 AM

Posted 05 April 2018 - 09:34 AM

Hi,

 

Sorry for the late response — we've been inundated with logs and it's hard to keep track of them. If you still need help, can you run the Sysnative App again for fresh log files?


If I do not reply in three days, please message me.
 
BC BSOD Posting Instructions | Carrona BSOD Index | Driver Reference Table (DRT)


#5 Tsarkyyy

Tsarkyyy
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  

Posted 05 April 2018 - 12:30 PM

Hi there,

No worries, wasnt keeping myself waiting for response so i posted these issues on a different forum as well,
but i could always use a second opinion :)

In the attachment u'll find the latest Synatives App files

Also, i am still getting the same memdump report.

 

 

On Thu 5-4-2018 18:51:38 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: atikmpag.sys (0xFFFFF805653EF7E8)
Bugcheck code: 0x116 (0xFFFFD28BA58B7010, 0xFFFFF805653EF7E8, 0xFFFFFFFFC0000001, 0x3)
Error: VIDEO_TDR_ERROR
file path: C:\WINDOWS\System32\DriverStore\FileRepository\c0323831.inf_amd64_1212be4b9fe2386c\atikmpag.sys
product: AMD driver
company: Advanced Micro Devices, Inc.
description: AMD multi-vendor Miniport Driver
Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: atikmpag.sys (AMD multi-vendor Miniport Driver, Advanced Micro Devices, Inc.).
Google query: atikmpag.sys Advanced Micro Devices, Inc. VIDEO_TDR_ERROR

 

Attached Files



#6 Tsarkyyy

Tsarkyyy
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  

Posted 08 April 2018 - 03:21 PM

I know you guys are busy browsing through all these logs that others are posting, but u can exclude this one off the list.

I got it fixed!! Can't be more happier! :D

The issue was the GPU somehow not properly seated so I removed and put it back in.
Merits of my first custom PC.

I also secured some loose cable with some zip-tips, just to make sure.

Been playing Warframe for at least 2 hours, no more crash or hangs.
Also been playing 7 Days to Die for 6 hours or so through out the weekend, no problems there.

If new or same problems occur again ill post a new thread

Thank you for replying @bwv848, but it is all sorted.... for now! :)

 



#7 bwv848

bwv848

    Bleepin' Owl


  • BSOD Kernel Dump Expert
  • 3,011 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:92.96 million miles away from the sun
  • Local time:03:21 AM

Posted 08 April 2018 - 06:32 PM

Glad it is! Happy computing!


If I do not reply in three days, please message me.
 
BC BSOD Posting Instructions | Carrona BSOD Index | Driver Reference Table (DRT)





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users