BSOD, all attempt to resolve failed

Toggle sidebar Toggle sidebar
A

Alex Keng Siang

Reputable
Aug 29, 2014
4
0
4,510
Hi guys, I'm new to this forum and I've been having this issue with BSOD in Windows 7. I've searched all over the web for solutions but so far nothing has worked. Please help as I've been having this problem for about a week now. The BSOD happens everytime I clicked on a video in Chrome and when it loads about 1-2 seconds it will enter BSOD. Attached here are some info about the BSOD.

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: 100000ea
BCP1: FFFFFA8002B98AC0
BCP2: 0000000000000000
BCP3: 0000000000000000
BCP4: 0000000000000000
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\083014-80761-01.dmp
C:\Users\Alex\AppData\Local\Temp\WER-151383-0.sysdata.xml

I need help and am willing to provide any information regarding the said problem.

Things I've tried:
Updating all softwares using Securnia
Updating all Windows Update ( However 2007 Office updates failed to install )
Reinstalling Google Chrome

Any help is welcomed. Thanks.
 
Sort by date Sort by votes
smorizio

smorizio

Titan
Jan 22, 2010
30,984
9
125,315
scan p[c with malware and hitman pro and another free online scanner to rule out a virus. if it not a virus is may be a spot of bad ram. if you have two stick of ram pull one see if the error stops or changes. if it does not swap the ram. another spot that can cause issues is a failing hard drive or a bad network card or bad cpu cache or core. if the ram tests does noting try turning of the cpu cache or cores see if it changes.
 
Upvote 0 Downvote
A

Alex Keng Siang

Reputable
Aug 29, 2014
4
0
4,510
Ok guys, thanks for the replies, really appreciated it. I was able to learn how to use the Windows Debugger yesterday and seems to me I was able to fix the said problem. I saw the problem was with ATI graphic driver, so I went and downloaded a driver from ATI website and installed and then everything was fine. Hopefully this is the end to this problem.

However guys please do correct me if I'm wrong. Below is the debugger results from my MEMORY dump dated 30/8/2014.


*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck EA, {fffffa8002b98ac0, 0, 0, 0}

*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Page 20695 not present in the dump file. Type ".hh dbgerr004" for details
Page 20695 not present in the dump file. Type ".hh dbgerr004" for details
Page 20695 not present in the dump file. Type ".hh dbgerr004" for details
Page 20695 not present in the dump file. Type ".hh dbgerr004" for details
Page 20695 not present in the dump file. Type ".hh dbgerr004" for details
Page 20695 not present in the dump file. Type ".hh dbgerr004" for details
Page 20695 not present in the dump file. Type ".hh dbgerr004" for details
Page 20695 not present in the dump file. Type ".hh dbgerr004" for details
Page 20695 not present in the dump file. Type ".hh dbgerr004" for details
Page 20695 not present in the dump file. Type ".hh dbgerr004" for details
Page 20695 not present in the dump file. Type ".hh dbgerr004" for details
Page 20695 not present in the dump file. Type ".hh dbgerr004" for details
Page 20695 not present in the dump file. Type ".hh dbgerr004" for details
Page 20695 not present in the dump file. Type ".hh dbgerr004" for details
Page 20695 not present in the dump file. Type ".hh dbgerr004" for details
Page 20695 not present in the dump file. Type ".hh dbgerr004" for details
Page 20695 not present in the dump file. Type ".hh dbgerr004" for details
Page 20695 not present in the dump file. Type ".hh dbgerr004" for details
Page 20695 not present in the dump file. Type ".hh dbgerr004" for details
Page 20695 not present in the dump file. Type ".hh dbgerr004" for details
Page 20695 not present in the dump file. Type ".hh dbgerr004" for details
Probably caused by : dxgkrnl.sys ( dxgkrnl!TdrTimedOperationBugcheckOnTimeout+37 )

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

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

THREAD_STUCK_IN_DEVICE_DRIVER (ea)
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 (OS builds <= 3790) 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: fffffa8002b98ac0, 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 this error occurred. If a debugger is attached,
this error is not always fatal -- see DESCRIPTION below. On the
blue screen, this will always equal 1.

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

Page 20695 not present in the dump file. Type ".hh dbgerr004" for details
Page 20695 not present in the dump file. Type ".hh dbgerr004" for details
Page 20695 not present in the dump file. Type ".hh dbgerr004" for details
Page 20695 not present in the dump file. Type ".hh dbgerr004" for details
Page 20695 not present in the dump file. Type ".hh dbgerr004" for details
Page 20695 not present in the dump file. Type ".hh dbgerr004" for details
Page 20695 not present in the dump file. Type ".hh dbgerr004" for details
Page 20695 not present in the dump file. Type ".hh dbgerr004" for details
Page 20695 not present in the dump file. Type ".hh dbgerr004" for details
Page 20695 not present in the dump file. Type ".hh dbgerr004" for details
Page 20695 not present in the dump file. Type ".hh dbgerr004" for details
Page 20695 not present in the dump file. Type ".hh dbgerr004" for details
Page 20695 not present in the dump file. Type ".hh dbgerr004" for details
Page 20695 not present in the dump file. Type ".hh dbgerr004" for details
Page 20695 not present in the dump file. Type ".hh dbgerr004" for details
Page 20695 not present in the dump file. Type ".hh dbgerr004" for details
Page 20695 not present in the dump file. Type ".hh dbgerr004" for details
Page 20695 not present in the dump file. Type ".hh dbgerr004" for details
Page 20695 not present in the dump file. Type ".hh dbgerr004" for details

FAULTING_THREAD: fffffa8002b98ac0

DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_FAULT

BUGCHECK_STR: 0xEA

PROCESS_NAME: chrome.exe

CURRENT_IRQL: 0

ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre

LAST_CONTROL_TRANSFER: from fffff880050fcf63 to fffff8000588abc0

STACK_TEXT:
Page 20695 not present in the dump file. Type ".hh dbgerr004" for details
Page 20695 not present in the dump file. Type ".hh dbgerr004" for details
Page 20695 not present in the dump file. Type ".hh dbgerr004" for details
Page 20695 not present in the dump file. Type ".hh dbgerr004" for details
Page 20695 not present in the dump file. Type ".hh dbgerr004" for details
Page 20695 not present in the dump file. Type ".hh dbgerr004" for details
fffff880`08531248 fffff880`050fcf63 : 00000000`000000ea fffffa80`02b98ac0 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
fffff880`08531250 fffff880`050fd112 : fffff880`08531320 fffff880`04dcd523 fffff880`08531320 00000000`00000246 : dxgkrnl!TdrTimedOperationBugcheckOnTimeout+0x37
fffff880`085312c0 fffff880`04b1005a : 00000000`00000000 fffff880`04dcd508 fffff880`08531488 00000000`01c9c380 : dxgkrnl!TdrTimedOperationDelay+0xbe
fffff880`08531300 fffff880`04b07cca : 00000000`01c9c380 fffffa80`03c8d000 00000000`00000000 00000000`00000001 : atikmdag+0x3105a
fffff880`08531370 fffff880`04dd5333 : 00000000`00000001 00000000`00000bb8 fffffa80`03c8d010 fffff880`04dcd508 : atikmdag+0x28cca
fffff880`085313b0 fffff880`04de167f : 00000000`2001000c 00000000`00007530 fffffa80`02502010 00000000`00000000 : atikmdag+0x2f6333
fffff880`08531440 fffff880`04de193b : 00000000`00007530 00000000`00000398 00000000`00000000 fffff880`085315e0 : atikmdag+0x30267f
fffff880`085314d0 fffff880`04de1c04 : fffffa80`02502010 00000000`00000398 00000000`00000398 00000000`000f4400 : atikmdag+0x30293b
fffff880`08531500 fffff880`04de21b6 : fffffa80`02502010 fffffa80`02502010 fffff880`085315e0 00000000`00000000 : atikmdag+0x302c04
fffff880`08531550 fffff880`04dcac1a : 00000000`00000001 fffff880`04b058df ffff0800`00000000 00000000`00000000 : atikmdag+0x3031b6
fffff880`08531580 fffff880`04ae58d5 : fffffa80`04a542d0 fffff880`08531960 00000000`00000000 00000000`00000000 : atikmdag+0x2ebc1a
fffff880`085315c0 fffff880`04d8d940 : fffffa80`04a542d0 00000000`00000000 00000000`00000100 00000000`00000000 : atikmdag+0x68d5
fffff880`08531700 fffff880`04d8d6ff : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000001 : atikmdag+0x2ae940
fffff880`08531730 fffff880`04d8d79f : fffffa80`0269c2c0 00000000`00000000 00000000`00000000 fffffa80`04e1a000 : atikmdag+0x2ae6ff
fffff880`08531760 fffff880`04d790c2 : fffff880`00000000 00000000`00000000 00000000`00000002 fffffa80`026cd000 : atikmdag+0x2ae79f
fffff880`08531790 fffff880`04d6213c : 00000000`00000000 fffff800`05895fb8 fffffa80`03532000 fffff880`08531850 : atikmdag+0x29a0c2
fffff880`085317c0 fffff880`04af31ea : fffff880`08531960 00000000`00000000 fffff8a0`04a23620 00000000`00000000 : atikmdag+0x28313c
fffff880`08531840 fffff880`0512c74d : 00000000`00000000 fffffa80`04e60000 fffff8a0`0420b8b0 00000000`00000000 : atikmdag+0x141ea
fffff880`08531870 fffff880`0513e989 : 00000000`00000040 fffff8a0`118a8000 fffff8a0`118a8000 fffffa80`003c0ba0 : dxgkrnl!DXGADAPTER::DdiCreateContext+0x4d
fffff880`085318b0 fffff880`051413c8 : fffff8a0`0420b8b0 fffff8a0`0420b8b0 fffff880`08531a88 00000000`000007f7 : dxgkrnl!DXGCONTEXT::Initialize+0x111
fffff880`085319d0 fffff880`0513e15f : 00000000`00000000 fffff880`08531c60 00000000`000007f7 00000000`000007ff : dxgkrnl!DXGDEVICE::CreateContext+0x1c4
fffff880`08531a10 fffff960`00221cbe : 00000000`0c9ee0e0 00000000`fff9b000 00000000`00000040 00000000`000007f7 : dxgkrnl!DxgkCreateContext+0x6a3
fffff880`08531bb0 fffff800`05889e53 : 00000000`00000008 00000000`6865e5f0 00000000`07c7a301 00000000`07c68360 : win32k!NtGdiDdDDICreateContext+0x12
fffff880`08531be0 00000000`750613ba : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0c9ee0b8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x750613ba


STACK_COMMAND: .thread 0xfffffa8002b98ac0 ; kb

FOLLOWUP_IP:
dxgkrnl!TdrTimedOperationBugcheckOnTimeout+37
fffff880`050fcf63 cc int 3

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: dxgkrnl!TdrTimedOperationBugcheckOnTimeout+37

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: dxgkrnl

IMAGE_NAME: dxgkrnl.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 539e411c

FAILURE_BUCKET_ID: X64_0xEA_IMAGE_dxgkrnl.sys

BUCKET_ID: X64_0xEA_IMAGE_dxgkrnl.sys

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:x64_0xea_image_dxgkrnl.sys

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

Followup: MachineOwner
 
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