Go Back   Tech Support Forum > Microsoft Support > BSOD, App Crashes And Hangs

User Tag List

My computer reboot/crash while playing certain games 2

This is a discussion on My computer reboot/crash while playing certain games 2 within the BSOD, App Crashes And Hangs forums, part of the Tech Support Forum category. This thread is about a problem with my computer. (more details in the link below) I have attached everything that


Closed Thread
 
Thread Tools Search this Thread
Old 02-10-2016, 02:08 PM   #1
Registered Member
 
Join Date: Feb 2016
Posts: 6
OS: win 7 64-bit


Pin

This thread is about a problem with my computer. (more details in the link below)
I have attached everything that is required by the BSOD post rules.
In the ForTechSupport rar you will find the PC Health report and a txt file with details about my computer. Thanks for the support ^^

Details about the problem with my computer :)
Attached Files
File Type: rar ForTechSupport.rar (83.5 KB, 13 views)
File Type: zip SysnativeFileCollectionApp.zip (637.4 KB, 69 views)
Dreadfal is offline  
Sponsored Links
Advertisement
 
Old 02-15-2016, 01:21 AM   #2
Hardware Team
Games Team
 
Aus_Karlos's Avatar
 
Join Date: Mar 2007
Location: Western Australia, Perth
Posts: 4,651
OS: Windows 10 64-bit Pro

My System


Hi Dreadfal,

Looking at your Dump files it seems your ATI drivers are getting stuck in an infinite loop. This can be caused by the GPU not responding. A couple of things can cause the GPU not to respond.
1) GPU Hardware failure
2) Overheating
3)Overclocked
4)Corrupt Drivers
5) Insufficient PSU

You can start by downloading Speccy from my sig to monitor the temperature of the GPU (Maximum operating temp for the ATI Radeon HD 4670 is about ~80c)
If its not a temperature issue then download your latest ATI drivers and also Display Driver Uninstaller. Run this tool to completely remove the current drivers then install the latest ones. This will ensure if the current drivers are corrupt then nothing of them will be left when using this tool.

Could you please post your PSU specs and the age of your PC.

Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

THREAD_STUCK_IN_DEVICE_DRIVER_M (100000ea)
The device driver is spinning in an infinite loop, most likely waiting for
hardware to become idle. This usually indicates problem with the hardware
itself or with the device driver programming the hardware incorrectly.
If the kernel debugger is connected and running when watchdog detects a
timeout condition then DbgBreakPoint() will be called instead of KeBugCheckEx()
and detailed message including bugcheck arguments will be printed to the
debugger. This way we can identify an offending thread, set breakpoints in it,
and hit go to return to the spinning code to debug it further. Because
KeBugCheckEx() is not called the .bugcheck directive will not return bugcheck
information in this case. The arguments are already printed out to the kernel
debugger. You can also retrieve them from a global variable via
"dd watchdog!g_WdBugCheckData l5" (use dq on NT64).
On MP machines it is possible to hit a timeout when the spinning thread is
interrupted by hardware interrupt and ISR or DPC routine is running at the time
of the bugcheck (this is because the timeout's work item can be delivered and
handled on the second CPU and the same time). If this is the case you will have
to look deeper at the offending thread's stack (e.g. using dds) to determine
spinning code which caused the timeout to occur.
Arguments:
Arg1: fffffa80084e68b0, Pointer to a stuck thread object.  Do .thread then kb on it to find
	the hung location.
Arg2: 0000000000000000, Pointer to a DEFERRED_WATCHDOG object.
Arg3: 0000000000000000, Pointer to offending driver name.
Arg4: 0000000000000000, Number of times "intercepted" bugcheck 0xEA was hit (see notes).

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


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  7601.19110.amd64fre.win7sp1_gdr.151230-0600

SYSTEM_MANUFACTURER:  Gigabyte Technology Co., Ltd.

SYSTEM_PRODUCT_NAME:  GA-78LMT-S2

BIOS_VENDOR:  Award Software International, Inc.

BIOS_VERSION:  F2

BIOS_DATE:  05/08/2012

BASEBOARD_MANUFACTURER:  Gigabyte Technology Co., Ltd.

BASEBOARD_PRODUCT:  GA-78LMT-S2

BASEBOARD_VERSION:  x.x

DUMP_TYPE:  2

BUGCHECK_P1: fffffa80084e68b0

BUGCHECK_P2: 0

BUGCHECK_P3: 0

BUGCHECK_P4: 0

FAULTING_THREAD:  084e68b0

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_FAULT

CPU_COUNT: 4

CPU_MHZ: e20

CPU_VENDOR:  AuthenticAMD

CPU_FAMILY: 15

CPU_MODEL: 1

CPU_STEPPING: 2

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0xEA

PROCESS_NAME:  System

CURRENT_IRQL:  0

ANALYSIS_SESSION_HOST:  DESKTOP-LOQNCIA

ANALYSIS_SESSION_TIME:  02-15-2016 17:10:03.0343

ANALYSIS_VERSION: 10.0.10586.567 amd64fre

LAST_CONTROL_TRANSFER:  from fffff88004846f63 to fffff80002abfc00

STACK_TEXT:  
fffff880`02eff4c8 fffff880`04846f63 : 00000000`000000ea fffffa80`084e68b0 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
fffff880`02eff4d0 fffff880`04847112 : fffff880`02eff5a0 fffff880`042c7a2b fffff880`02eff5a0 00000000`00003f00 : dxgkrnl!TdrTimedOperationBugcheckOnTimeout+0x37
fffff880`02eff540 fffff880`040def72 : 00000000`00000000 fffff880`042c7a10 fffff880`02eff6c0 00000000`01c9c380 : dxgkrnl!TdrTimedOperationDelay+0xbe
fffff880`02eff580 00000000`00000000 : fffff880`042c7a10 fffff880`02eff6c0 00000000`01c9c380 fffff880`02ef0028 : atikmdag+0x2bf72


STACK_COMMAND:  .thread 0xfffffa80084e68b0 ; kb

THREAD_SHA1_HASH_MOD_FUNC:  260988b723f057138fe45b239c381c934e8a7f90

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  56c67e7e6ec8a2a5ff689d3b1b7fd05135caeeef

THREAD_SHA1_HASH_MOD:  b9a6b0a1888ce93becee46671d601e0839dd0b94

FOLLOWUP_IP: 
dxgkrnl!TdrTimedOperationBugcheckOnTimeout+37
fffff880`04846f63 cc              int     3

FAULT_INSTR_CODE:  cccccccc

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  dxgkrnl!TdrTimedOperationBugcheckOnTimeout+37

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgkrnl

IMAGE_NAME:  dxgkrnl.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  539e411c

IMAGE_VERSION:  6.1.7601.18510

FAILURE_BUCKET_ID:  X64_0xEA_IMAGE_dxgkrnl.sys

BUCKET_ID:  X64_0xEA_IMAGE_dxgkrnl.sys

PRIMARY_PROBLEM_CLASS:  X64_0xEA_IMAGE_dxgkrnl.sys

TARGET_TIME:  2016-02-09T15:04:07.000Z

OSBUILD:  7601

OSSERVICEPACK:  1000

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  272

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 7

OSEDITION:  Windows 7 WinNt (Service Pack 1) TerminalServer SingleUserTS

OS_LOCALE:  

USER_LCID:  0

OSBUILD_TIMESTAMP:  2015-12-31 01:49:16

BUILDDATESTAMP_STR:  151230-0600

BUILDLAB_STR:  win7sp1_gdr

BUILDOSVER_STR:  6.1.7601.19110.amd64fre.win7sp1_gdr.151230-0600

ANALYSIS_SESSION_ELAPSED_TIME: 465

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0xea_image_dxgkrnl.sys

FAILURE_ID_HASH:  {b58a0dfd-90f3-63cd-1b07-7ce1b53744cb}

Followup:     MachineOwner
Aus_Karlos is offline  
Old 02-16-2016, 01:51 PM   #3
Registered Member
 
Join Date: Feb 2016
Posts: 6
OS: win 7 64-bit



Quote:
Originally Posted by Aus_Karlos View Post
Hi Dreadfal,

Looking at your Dump files it seems your ATI drivers are getting stuck in an infinite loop. This can be caused by the GPU not responding. A couple of things can cause the GPU not to respond.
1) GPU Hardware failure
2) Overheating
3)Overclocked
4)Corrupt Drivers
5) Insufficient PSU

You can start by downloading Speccy from my sig to monitor the temperature of the GPU (Maximum operating temp for the ATI Radeon HD 4670 is about ~80c)
If its not a temperature issue then download your latest ATI drivers and also Display Driver Uninstaller. Run this tool to completely remove the current drivers then install the latest ones. This will ensure if the current drivers are corrupt then nothing of them will be left when using this tool.

Could you please post your PSU specs and the age of your PC.

Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

THREAD_STUCK_IN_DEVICE_DRIVER_M (100000ea)
The device driver is spinning in an infinite loop, most likely waiting for
hardware to become idle. This usually indicates problem with the hardware
itself or with the device driver programming the hardware incorrectly.
If the kernel debugger is connected and running when watchdog detects a
timeout condition then DbgBreakPoint() will be called instead of KeBugCheckEx()
and detailed message including bugcheck arguments will be printed to the
debugger. This way we can identify an offending thread, set breakpoints in it,
and hit go to return to the spinning code to debug it further. Because
KeBugCheckEx() is not called the .bugcheck directive will not return bugcheck
information in this case. The arguments are already printed out to the kernel
debugger. You can also retrieve them from a global variable via
"dd watchdog!g_WdBugCheckData l5" (use dq on NT64).
On MP machines it is possible to hit a timeout when the spinning thread is
interrupted by hardware interrupt and ISR or DPC routine is running at the time
of the bugcheck (this is because the timeout's work item can be delivered and
handled on the second CPU and the same time). If this is the case you will have
to look deeper at the offending thread's stack (e.g. using dds) to determine
spinning code which caused the timeout to occur.
Arguments:
Arg1: fffffa80084e68b0, Pointer to a stuck thread object.  Do .thread then kb on it to find
	the hung location.
Arg2: 0000000000000000, Pointer to a DEFERRED_WATCHDOG object.
Arg3: 0000000000000000, Pointer to offending driver name.
Arg4: 0000000000000000, Number of times "intercepted" bugcheck 0xEA was hit (see notes).

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


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  7601.19110.amd64fre.win7sp1_gdr.151230-0600

SYSTEM_MANUFACTURER:  Gigabyte Technology Co., Ltd.

SYSTEM_PRODUCT_NAME:  GA-78LMT-S2

BIOS_VENDOR:  Award Software International, Inc.

BIOS_VERSION:  F2

BIOS_DATE:  05/08/2012

BASEBOARD_MANUFACTURER:  Gigabyte Technology Co., Ltd.

BASEBOARD_PRODUCT:  GA-78LMT-S2

BASEBOARD_VERSION:  x.x

DUMP_TYPE:  2

BUGCHECK_P1: fffffa80084e68b0

BUGCHECK_P2: 0

BUGCHECK_P3: 0

BUGCHECK_P4: 0

FAULTING_THREAD:  084e68b0

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_FAULT

CPU_COUNT: 4

CPU_MHZ: e20

CPU_VENDOR:  AuthenticAMD

CPU_FAMILY: 15

CPU_MODEL: 1

CPU_STEPPING: 2

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0xEA

PROCESS_NAME:  System

CURRENT_IRQL:  0

ANALYSIS_SESSION_HOST:  DESKTOP-LOQNCIA

ANALYSIS_SESSION_TIME:  02-15-2016 17:10:03.0343

ANALYSIS_VERSION: 10.0.10586.567 amd64fre

LAST_CONTROL_TRANSFER:  from fffff88004846f63 to fffff80002abfc00

STACK_TEXT:  
fffff880`02eff4c8 fffff880`04846f63 : 00000000`000000ea fffffa80`084e68b0 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
fffff880`02eff4d0 fffff880`04847112 : fffff880`02eff5a0 fffff880`042c7a2b fffff880`02eff5a0 00000000`00003f00 : dxgkrnl!TdrTimedOperationBugcheckOnTimeout+0x37
fffff880`02eff540 fffff880`040def72 : 00000000`00000000 fffff880`042c7a10 fffff880`02eff6c0 00000000`01c9c380 : dxgkrnl!TdrTimedOperationDelay+0xbe
fffff880`02eff580 00000000`00000000 : fffff880`042c7a10 fffff880`02eff6c0 00000000`01c9c380 fffff880`02ef0028 : atikmdag+0x2bf72


STACK_COMMAND:  .thread 0xfffffa80084e68b0 ; kb

THREAD_SHA1_HASH_MOD_FUNC:  260988b723f057138fe45b239c381c934e8a7f90

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  56c67e7e6ec8a2a5ff689d3b1b7fd05135caeeef

THREAD_SHA1_HASH_MOD:  b9a6b0a1888ce93becee46671d601e0839dd0b94

FOLLOWUP_IP: 
dxgkrnl!TdrTimedOperationBugcheckOnTimeout+37
fffff880`04846f63 cc              int     3

FAULT_INSTR_CODE:  cccccccc

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  dxgkrnl!TdrTimedOperationBugcheckOnTimeout+37

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgkrnl

IMAGE_NAME:  dxgkrnl.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  539e411c

IMAGE_VERSION:  6.1.7601.18510

FAILURE_BUCKET_ID:  X64_0xEA_IMAGE_dxgkrnl.sys

BUCKET_ID:  X64_0xEA_IMAGE_dxgkrnl.sys

PRIMARY_PROBLEM_CLASS:  X64_0xEA_IMAGE_dxgkrnl.sys

TARGET_TIME:  2016-02-09T15:04:07.000Z

OSBUILD:  7601

OSSERVICEPACK:  1000

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  272

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 7

OSEDITION:  Windows 7 WinNt (Service Pack 1) TerminalServer SingleUserTS

OS_LOCALE:  

USER_LCID:  0

OSBUILD_TIMESTAMP:  2015-12-31 01:49:16

BUILDDATESTAMP_STR:  151230-0600

BUILDLAB_STR:  win7sp1_gdr

BUILDOSVER_STR:  6.1.7601.19110.amd64fre.win7sp1_gdr.151230-0600

ANALYSIS_SESSION_ELAPSED_TIME: 465

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0xea_image_dxgkrnl.sys

FAILURE_ID_HASH:  {b58a0dfd-90f3-63cd-1b07-7ce1b53744cb}

Followup:     MachineOwner
I wrote my computer's age in the txt file but i'll write it again anyways.
The age of my computer is maybe a little bit over 9 years 10 max, but i upgraded the Motherboard, CPU, RAM 3 years ago, and the GPU 5 Years ago or maybe 6 I can't remember the exact time. My PSU is delux 550 Watts don't much about it, it's cheap PSU.
Dreadfal is offline  
Sponsored Links
Advertisement
 
Old 02-18-2016, 01:15 AM   #4
Hardware Team
Games Team
 
Aus_Karlos's Avatar
 
Join Date: Mar 2007
Location: Western Australia, Perth
Posts: 4,651
OS: Windows 10 64-bit Pro

My System


For a system this old it was only a matter of time before hardware will start to fail. The first is quite possibly the PSU, as you stated its a cheap one. The PSU is one of the most important parts of a PC. It supplies stable power to all the components, if the PSU faults it can take out the rest of your system.

If im to assume your PCs PSU is also 9 years old depending on how you have been using it the PSU will not be outputting anywhere near the stated 550W. Its probably more like sitting around 300-400W or less depending on the quality of the capacitors. So it s probably not able to supply sufficient or correct voltage/amps to all the components.

I would personally replace the PSU with a decent same size one.
80 PLUS BRONZE Certified, Power Supplies, Power Supplies, Components - Newegg.com

The higher the rated 80Plus (Silver, Gold, Platinum ect) the better the quality of the PSU. Stick with Seasonic, EVGA, Corsair, they are all good brands.
Aus_Karlos is offline  
Old 02-18-2016, 01:32 PM   #5
Registered Member
 
Join Date: Feb 2016
Posts: 6
OS: win 7 64-bit



Quote:
Originally Posted by Aus_Karlos View Post
For a system this old it was only a matter of time before hardware will start to fail. The first is quite possibly the PSU, as you stated its a cheap one. The PSU is one of the most important parts of a PC. It supplies stable power to all the components, if the PSU faults it can take out the rest of your system.

If im to assume your PCs PSU is also 9 years old depending on how you have been using it the PSU will not be outputting anywhere near the stated 550W. Its probably more like sitting around 300-400W or less depending on the quality of the capacitors. So it s probably not able to supply sufficient or correct voltage/amps to all the components.

I would personally replace the PSU with a decent same size one.
80 PLUS BRONZE Certified, Power Supplies, Power Supplies, Components - Newegg.com

The higher the rated 80Plus (Silver, Gold, Platinum ect) the better the quality of the PSU. Stick with Seasonic, EVGA, Corsair, they are all good brands.
No the PSU is 1 years old because I bought new one little less then one year ago.
Dreadfal is offline  
Old 02-19-2016, 12:46 AM   #6
Hardware Team
Games Team
 
Aus_Karlos's Avatar
 
Join Date: Mar 2007
Location: Western Australia, Perth
Posts: 4,651
OS: Windows 10 64-bit Pro

My System


Then its more than likely your GPU is on its way out. Is it possible to use another GPU for the time been to test the systems stability?

But i'd advise you to not purchase the cheapest PSU you can find. Really cheap ones do not have any over-current protection, and may not be able to supply steady voltage to the components which is called voltage ripple. Voltage ripple can be deadly to the components.
Aus_Karlos is offline  
Old 02-19-2016, 02:45 PM   #7
Registered Member
 
Join Date: Feb 2016
Posts: 6
OS: win 7 64-bit



Quote:
Originally Posted by Aus_Karlos View Post
Then its more than likely your GPU is on its way out. Is it possible to use another GPU for the time been to test the systems stability?

But i'd advise you to not purchase the cheapest PSU you can find. Really cheap ones do not have any over-current protection, and may not be able to supply steady voltage to the components which is called voltage ripple. Voltage ripple can be deadly to the components.
Sadly I can't, but to bring update to the topic. My computer crashes when I start any game, my screen goes black and the GPU's cooler seems to shuts off and start again and again and again till I restart the computer. :) This should ease your decision if it's the GPU or PSU.
Dreadfal is offline  
Old 02-19-2016, 10:18 PM   #8
Hardware Team
Games Team
 
Aus_Karlos's Avatar
 
Join Date: Mar 2007
Location: Western Australia, Perth
Posts: 4,651
OS: Windows 10 64-bit Pro

My System


Still its a hard one. If your PSU isnt suppling the correct voltage/amp then your card could be shutting down to avoid damage. But on the otherside if your GPU is damaged then the GPU switching off is a fail-safe.

Do you have another PC to test the GPU in? Even a friends PC, its the best way to test components without purchasing something.
Aus_Karlos is offline  
Old 02-23-2016, 07:18 AM   #9
Registered Member
 
Join Date: Feb 2016
Posts: 6
OS: win 7 64-bit



Quote:
Originally Posted by Aus_Karlos View Post
Still its a hard one. If your PSU isnt suppling the correct voltage/amp then your card could be shutting down to avoid damage. But on the otherside if your GPU is damaged then the GPU switching off is a fail-safe.

Do you have another PC to test the GPU in? Even a friends PC, its the best way to test components without purchasing something.
I don't have second PC otherwise I wouldn't complain about not being able to play videogames :D
But I can ask a friend to test the GPU and the PSU on his PC.
Dreadfal is offline  
Closed Thread

Thread Tools Search this Thread
Search this Thread:

Advanced Search

Similar Threads
Thread Thread Starter Forum Replies Last Post
My computer reboot/crash while playing certain games
So couple of days ago my computer started to act strange. First it crashed once, i didn't payed much attention since it worked just fine after the reboot, but yesterday my computer couldn't even turn on, it goes to windows loading screen, or even desktop screen if I'm lucky and it crashes again. I...
Dreadfal Driver Support 2 02-10-2016 02:48 AM
BSOD help Windows 7 64 bit
Over the last months I have had different BSOD's. I have little time have not been really been able to post information, but today I have some time finally (plus getting tired of it). Could you help me out identifying what the driver, hardware, problem is? Thanks so much in advance! ...
HardTrance9 BSOD, App Crashes And Hangs 24 02-18-2014 06:01 PM
Computer freezes when playing games or watching videos
Hi, Im not really sure what is wrong with my computer, but I will post it in this forum because it very likely could have something to do with the video card. My specs are: Windows 7 Ultimate 64-bit Acer Aspire M7720 i7 CPU 2.67 Ghz (8 CPUs) 6.1 GB RAM Direct x11
Kazario Motherboards, Bios & CPU 26 01-19-2013 05:59 AM
Computer Freezes mostly when playing video games, sometimes when watching videos.
Hello and good days, I'm having trouble with my pc, when i play video games it freezes sometimes a second after i started the game or maybe half an hour or an hour into it. it sometimes freezes when watching videos on full screen and also when it freezes and I reboot it when windows is loading,...
Vuddoo PC Gaming Support 5 06-09-2012 07:28 PM
Windows 7 BSOD - Memory management
Been getting BSOD. Sometimes twice a night, sometimes none. This hass been for weeks. Sometimes I get stuck in a reboot loop, sometimes it wants to run Repair, sometimes it wants me to choose safe mode/no safe mode. Pulled out two 1GB sticks of old dell memory yesterday when it was stuck in a...
dj-anakin BSOD, App Crashes And Hangs 7 02-21-2011 03:27 PM

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is on
Smilies are on
[IMG] code is on
HTML code is Off
Trackbacks are Off
Pingbacks are Off
Refbacks are Off


Post a Question


» Site Navigation
 > FAQ
  > 10.0.0.2
Powered by vBadvanced CMPS v3.2.3


All times are GMT -7. The time now is 03:45 PM.


Powered by vBulletin® Version 3.8.8
Copyright ©2000 - 2020, vBulletin Solutions, Inc.
vBulletin Security provided by vBSecurity v2.2.2 (Pro) - vBulletin Mods & Addons Copyright © 2020 DragonByte Technologies Ltd.
User Alert System provided by Advanced User Tagging v3.1.0 (Pro) - vBulletin Mods & Addons Copyright © 2020 DragonByte Technologies Ltd.
Copyright 2001 - 2018, Tech Support Forum

Windows 10 - Windows 7 - Windows XP - Windows Vista - Trojan Removal - Spyware Removal - Virus Removal - Networking - Security - Top Web Hosts