Random crashes on Windows 7!

Jun 3, 2018
3
0
10
0
Hi! My computer has had the habit of randomly blue screening every so often. I have reinstall multiple windows multiple times. I was originally Windows 7 and had the free update to windows 10, which I took. Then all the problems began to arise. I got a windows 8 disk from a friend and installed that to hopefully counter the problems as I thought it was due to Windows 10 being newly release and not fully developed.
However, this did not work.

I installed Windows 7 once more and for a week or so, it seemed fine... now .. the crashes are back, and I have no idea what to do!!

I can't enjoy anything! I will link the dump files below, please help!
 
Jun 3, 2018
3
0
10
0
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: fffffa800b0f6060, 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:
------------------


KEY_VALUES_STRING: 1


TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 7601.24117.amd64fre.win7sp1_ldr_escrow.180422-1430

SYSTEM_MANUFACTURER: Gigabyte Technology Co., Ltd.

SYSTEM_PRODUCT_NAME: To be filled by O.E.M.

SYSTEM_SKU: To be filled by O.E.M.

SYSTEM_VERSION: To be filled by O.E.M.

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: F4

BIOS_DATE: 05/28/2014

BASEBOARD_MANUFACTURER: Gigabyte Technology Co., Ltd.

BASEBOARD_PRODUCT: F2A78M-D3H

BASEBOARD_VERSION: x.x

DUMP_TYPE: 2

BUGCHECK_P1: fffffa800b0f6060

BUGCHECK_P2: 0

BUGCHECK_P3: 0

BUGCHECK_P4: 0

FAULTING_THREAD: 0b0f6060

DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_FAULT

CPU_COUNT: 4

CPU_MHZ: f98

CPU_VENDOR: AuthenticAMD

CPU_FAMILY: 15

CPU_MODEL: 38

CPU_STEPPING: 1

CUSTOMER_CRASH_COUNT: 1

BUGCHECK_STR: 0xEA

PROCESS_NAME: amddvr.exe

CURRENT_IRQL: 0

ANALYSIS_SESSION_HOST: NEXUS-PC

ANALYSIS_SESSION_TIME: 06-03-2018 16:31:20.0728

ANALYSIS_VERSION: 10.0.17134.12 amd64fre

LAST_CONTROL_TRANSFER: from fffff880040cbf63 to fffff80002cfe4a0

STACK_TEXT:
fffff880`080bd6c8 fffff880`040cbf63 : 00000000`000000ea fffffa80`0b0f6060 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
fffff880`080bd6d0 fffff880`040cc112 : fffff880`080bd7a8 fffff880`10f6eda4 fffff880`080bd7a8 00000000`00000000 : dxgkrnl!TdrTimedOperationBugcheckOnTimeout+0x37
fffff880`080bd740 fffff880`10eed5e0 : fffffa80`08bac000 00000000`00000000 fffff880`080bd890 fffff880`10f6ed90 : dxgkrnl!TdrTimedOperationDelay+0xbe
fffff880`080bd780 fffffa80`08bac000 : 00000000`00000000 fffff880`080bd890 fffff880`10f6ed90 00000000`00002710 : atikmdag+0x665e0
fffff880`080bd788 00000000`00000000 : fffff880`080bd890 fffff880`10f6ed90 00000000`00002710 fffffa80`092d0028 : 0xfffffa80`08bac000


STACK_COMMAND: .thread 0xfffffa800b0f6060 ; 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`040cbf63 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: 591b136f

IMAGE_VERSION: 6.1.7601.23809

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: 2018-06-03T15:14:02.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: 2018-04-23 00:25:30

BUILDDATESTAMP_STR: 180422-1430

BUILDLAB_STR: win7sp1_ldr_escrow

BUILDOSVER_STR: 6.1.7601.24117.amd64fre.win7sp1_ldr_escrow.180422-1430

ANALYSIS_SESSION_ELAPSED_TIME: 61c

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:x64_0xea_image_dxgkrnl.sys

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



Can someone make sense of this for me please?
 

Similar threads


ASK THE COMMUNITY