"SYSTEM THREAD EXCEPTION NOT HANDLED" How do I fix this Issue?

Status
This thread has been Locked and is not open to further replies. Please start a New Thread if you're having a similar issue. View our Welcome Guide to learn how to use this site.

drlucas1015

Thread Starter
Joined
Jan 30, 2015
Messages
1
i am having this BSOD popup so many times on my system when i am in the middle of my worK causing me to lose all my unsaved info....pls can someone help me on how to fix this issue....i tried reinstalling (clean) windows 8.1 but it still keeps showing up...i have attached a copy of the minidump file that was created the last time it did this...if that may help

this drives me crazy...pls help:(
 

Attachments

blues_harp28

Moderator
Joined
Jan 9, 2005
Messages
19,431
Hi, I am not a Win 8 user, however, the mindump file result.
.................................
Unable to load image atikmdag.sys Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Probably caused by : atikmdag.sys ( atikmdag+c4deb )
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8013db34deb, The address that the exception occurred at
Arg3: ffffd0015d596128, Exception Record Address
Arg4: ffffd0015d595930, Context Record Address

Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

FAULTING_IP:
atikmdag+c4deb
fffff801`3db34deb 488b83a8060000 mov rax,qword ptr [rbx+6A8h]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 0

FOLLOWUP_IP:
atikmdag+c4deb
fffff801`3db34deb 488b83a8060000 mov rax,qword ptr [rbx+6A8h]

BUGCHECK_STR: 0x7E

LAST_CONTROL_TRANSFER: from ffffe00169721880 to fffff8013db34deb

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: atikmdag+c4deb

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: atikmdag

IMAGE_NAME: atikmdag.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 531fc36e

STACK_COMMAND: .cxr 0xffffd0015d595930 ; kb

FAILURE_BUCKET_ID: X64_0x7E_atikmdag+c4deb

BUCKET_ID: X64_0x7E_atikmdag+c4deb

Followup: MachineOwner
======
atikmdag.sys
ATI Radeon Kernel Mode Driver.
http://www.systemlookup.com/Drivers/576-atikmdag_sys.html
http://support.amd.com/en-us/download/auto-detect-tool
 
Status
This thread has been Locked and is not open to further replies. Please start a New Thread if you're having a similar issue. View our Welcome Guide to learn how to use this site.

Users Who Are Viewing This Thread (Users: 0, Guests: 1)

As Seen On
As Seen On...

Welcome to Tech Support Guy!

Are you looking for the solution to your computer problem? Join our site today to ask your question. This site is completely free -- paid for by advertisers and donations.

If you're not already familiar with forums, watch our Welcome Guide to get started.

Join over 807,865 other people just like you!

Latest posts

Members online

Top