Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Random BSOD possibly caused by at1kmdsg.sys

18 Jun 2015   #1
barrro

Windows 7 Professional sp1 64bit
 
 
Random BSOD possibly caused by at1kmdsg.sys

Hi there,

My PC, which has been fine for about 1yr, has crashed 3 times in the last 24hrs. The last time I managed to read the BSOD message which seemed to indicate that at1kmdsg.sys may be responsible.

This has not caused other users problems for nearly a year as far as I can see from your forum, but following instructions on another post I generated a log which I upload.

Please can you help me with this problem.


My System SpecsSystem Spec
.
18 Jun 2015   #2
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

It is a display failure, and the display driver that is installed there is a good stable one. Still, update the display drive to 14.12 CCC, as some R7 and R9 cards run better with that driver.

When done, stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark
Take a screenshot of the furmark window before closing it. Upload the screenshot for us. Also let us know if you have experienced any crash/BSOD and/or artifacts during the test.

We will decide the next course of action after seeing this result.
_____________________________________________________________
Code:
BugCheck 1000007E, {ffffffffc0000005, fffff8800f4cbdbb, fffff880030b8228, fffff880030b7a80}

Probably caused by : atikmdag.sys ( atikmdag+c7dbb )

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

1: 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: fffff8800f4cbdbb, The address that the exception occurred at
Arg3: fffff880030b8228, Exception Record Address
Arg4: fffff880030b7a80, Context Record Address

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

FAULTING_IP: 
atikmdag+c7dbb
fffff880`0f4cbdbb 488b83a8060000  mov     rax,qword ptr [rbx+6A8h]

EXCEPTION_RECORD:  fffff880030b8228 -- (.exr 0xfffff880030b8228)
ExceptionAddress: fffff8800f4cbdbb (atikmdag+0x00000000000c7dbb)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 00000000000006a8
Attempt to read from address 00000000000006a8

CONTEXT:  fffff880030b7a80 -- (.cxr 0xfffff880030b7a80;r)
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000050000 rdi=0000000000000002
rip=fffff8800f4cbdbb rsp=fffff880030b8460 rbp=fffffa80107ae820
 r8=0000000000000002  r9=000000f41a2f8000 r10=0000000000000000
r11=fffff880030b8690 r12=fffffa8010845240 r13=fffffa8010a56380
r14=fffffa802cbb6010 r15=fffff8800f404000
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
atikmdag+0xc7dbb:
fffff880`0f4cbdbb 488b83a8060000  mov     rax,qword ptr [rbx+6A8h] ds:002b:00000000`000006a8=????????????????
Last set context:
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000050000 rdi=0000000000000002
rip=fffff8800f4cbdbb rsp=fffff880030b8460 rbp=fffffa80107ae820
 r8=0000000000000002  r9=000000f41a2f8000 r10=0000000000000000
r11=fffff880030b8690 r12=fffffa8010845240 r13=fffffa8010a56380
r14=fffffa802cbb6010 r15=fffff8800f404000
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
atikmdag+0xc7dbb:
fffff880`0f4cbdbb 488b83a8060000  mov     rax,qword ptr [rbx+6A8h] ds:002b:00000000`000006a8=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  00000000000006a8

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800034c1100
GetUlongFromAddress: unable to read from fffff800034c11c0
 00000000000006a8 Nonpaged pool

FOLLOWUP_IP: 
atikmdag+c7dbb
fffff880`0f4cbdbb 488b83a8060000  mov     rax,qword ptr [rbx+6A8h]

BUGCHECK_STR:  0x7E

ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff8800f4cbdbb

STACK_TEXT:  
fffff880`030b8460 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`2cbb6010 : atikmdag+0xc7dbb


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  atikmdag+c7dbb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmdag

IMAGE_NAME:  atikmdag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  53508a3c

STACK_COMMAND:  .cxr 0xfffff880030b7a80 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_atikmdag+c7dbb

BUCKET_ID:  X64_0x7E_atikmdag+c7dbb

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x7e_atikmdag+c7dbb

FAILURE_ID_HASH:  {1bce3716-c561-7934-01c3-535369bb657c}

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

1: kd> lmvm atikmdag
start             end                 module name
fffff880`0f404000 fffff880`10314000   atikmdag T (no symbols)           
    Loaded symbol image file: atikmdag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmdag.sys
    Image name: atikmdag.sys
    Timestamp:        Fri Apr 18 07:43:16 2014 (53508A3C)
    CheckSum:         00EAEEE6
    ImageSize:        00F10000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
My System SpecsSystem Spec
Reply

 Random BSOD possibly caused by at1kmdsg.sys




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
BSOD seemingly at random, possibly Chrome caused
My PC keeps blue screening with seemingly no cause, every time it's a different reason as to why it crashed, so I'm thinking it's hardware, my PC is fully up to date and nothing, as far as I can think, has changed lately to cause it to happen. I hope someone can help me out, it appears so random...
BSOD Help and Support
BSOD possibly caused by new NVIDIA driver. Not sure what to do.
Last year in March, I installed the 314.22 drivers and everything seemed fine. A few months later, I installed the 320.18 drivers, but learned that it caused a lot of problems, such as the kernel mode driver stopping and restarting while simply using Firefox. I used System Restore and it seemed to...
Drivers
BSOD possibly caused by ntoskrnl.exe?
My computer, over the past months, has been constantly displaying BSODs frequently, and I can't stand it anymore :mad:! Can someone please help me to fix this? Thanks in advance
BSOD Help and Support
BSOD possibly caused by adding RAM
So I purchased new RAM with the exact same specs (DDR3 1600Mhz 9-9-9-24 1.5v) all 4 GB sticks. The ram I had in slots A1 and A2 worked fine and I had no issues. With the new ram in slots B1 and B2 the computer blue screens every couple of hours. I ran memtest86+ for 10 passes and there were no...
BSOD Help and Support
Constant BSOD caused possibly by ntoskrnl.exe
Hello all. I recently decided to fork over the money and put myself together a nice gaming computer. The problem is I'm being constantly plagued by BSOD even as I currently type this out. I've never been very computer savvy so I had to have my tech friend walk me through getting all the right...
BSOD Help and Support
BSOD possibly caused by dtsoftbus01 on new build
Hi guys, I've been getting a BSOD sometimes on start up or shortly after. I've used the debugger to check the dump file and the driver that would appear to be faulty is dtsoftbus01 which from what I read is daemon tools. I had daemon tools on this computer at one point in time but I've since...
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 01:32.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App