Solved Random BSOD Crashes, please help

T

tremmel

New Member
Messages
3
Location
Tampa, Florida
Getting random crashes sometimes within minutes after booting up with the actions of navigating Firefox websites. Would appreciate the help fixing the issue.
 
Loading Dump File [C:\Users\blk_d_000\Desktop\SFdebugFiles\040515-32140-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred srv*c:\symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 8 Kernel Version 9600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 9600.17668.amd64fre.winblue_r8.150127-1500
Machine Name:
Kernel base = 0xfffff802`5b60c000 PsLoadedModuleList = 0xfffff802`5b8e5250
Debug session time: Sun Apr 5 06:31:31.719 2015 (UTC - 4:00)
System Uptime: 0 days 0:18:44.539
Loading Kernel Symbols
...............................................................
................................................................
..................................................
Loading User Symbols
Loading unloaded module list
.......
Unable to load image \SystemRoot\system32\DRIVERS\atikmdag.sys, Win32 error 0n2
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff800c49aa12b, ffffd0017d75c1b8, ffffd0017d75b9c0}

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

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

3: 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: fffff800c49aa12b, The address that the exception occurred at
Arg3: ffffd0017d75c1b8, Exception Record Address
Arg4: ffffd0017d75b9c0, 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+c512b
fffff800`c49aa12b 488b83a8060000 mov rax,qword ptr [rbx+6A8h]

EXCEPTION_RECORD: ffffd0017d75c1b8 -- (.exr 0xffffd0017d75c1b8)
ExceptionAddress: fffff800c49aa12b (atikmdag+0x00000000000c512b)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 00000000000006a8
Attempt to read from address 00000000000006a8

CONTEXT: ffffd0017d75b9c0 -- (.cxr 0xffffd0017d75b9c0;r)
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000001e00 rdi=0000000000000002
rip=fffff800c49aa12b rsp=ffffd0017d75c3f0 rbp=ffffe000659fb060
r8=0000000000000002 r9=000000f41035a000 r10=0000000000000000
r11=fffff800c367d447 r12=ffffe00065dc0500 r13=ffffe000657f3480
r14=ffffe00063c79740 r15=fffff800c48e5000
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+0xc512b:
fffff800`c49aa12b 488b83a8060000 mov rax,qword ptr [rbx+6A8h] ds:002b:00000000`000006a8=????????????????
Last set context:
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000001e00 rdi=0000000000000002
rip=fffff800c49aa12b rsp=ffffd0017d75c3f0 rbp=ffffe000659fb060
r8=0000000000000002 r9=000000f41035a000 r10=0000000000000000
r11=fffff800c367d447 r12=ffffe00065dc0500 r13=ffffe000657f3480
r14=ffffe00063c79740 r15=fffff800c48e5000
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+0xc512b:
fffff800`c49aa12b 488b83a8060000 mov rax,qword ptr [rbx+6A8h] ds:002b:00000000`000006a8=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 0

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

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: 00000000000006a8

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff8025b96f138
unable to get nt!MmNonPagedPoolStart
unable to get nt!MmSizeOfNonPagedPoolInBytes
00000000000006a8

FOLLOWUP_IP:
atikmdag+c512b
fffff800`c49aa12b 488b83a8060000 mov rax,qword ptr [rbx+6A8h]

BUGCHECK_STR: AV

ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre

LAST_CONTROL_TRANSFER: from 0000000000000010 to fffff800c49aa12b

STACK_TEXT:
ffffd001`7d75c3f0 00000000`00000010 : 00000000`00000246 ffffd001`7d75c418 00000000`00000018 ffffe000`63c79740 : atikmdag+0xc512b
ffffd001`7d75c3f8 00000000`00000246 : ffffd001`7d75c418 00000000`00000018 ffffe000`63c79740 fffff800`c4a0945f : 0x10
ffffd001`7d75c400 ffffd001`7d75c418 : 00000000`00000018 ffffe000`63c79740 fffff800`c4a0945f 00000000`00000000 : 0x246
ffffd001`7d75c408 00000000`00000018 : ffffe000`63c79740 fffff800`c4a0945f 00000000`00000000 00000000`00000000 : 0xffffd001`7d75c418
ffffd001`7d75c410 ffffe000`63c79740 : fffff800`c4a0945f 00000000`00000000 00000000`00000000 00000000`00000000 : 0x18
ffffd001`7d75c418 fffff800`c4a0945f : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xffffe000`63c79740
ffffd001`7d75c420 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : atikmdag+0x12445f


SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: atikmdag+c512b

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: atikmdag

IMAGE_NAME: atikmdag.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 53572763

STACK_COMMAND: .cxr 0xffffd0017d75b9c0 ; kb

FAILURE_BUCKET_ID: AV_atikmdag+c512b

BUCKET_ID: AV_atikmdag+c512b

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:av_atikmdag+c512b

FAILURE_ID_HASH: {2fcea8d7-0bb3-85b3-1c64-7fe7ccbc474a}

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

3: 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: fffff800c49aa12b, The address that the exception occurred at
Arg3: ffffd0017d75c1b8, Exception Record Address
Arg4: ffffd0017d75b9c0, 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+c512b
fffff800`c49aa12b 488b83a8060000 mov rax,qword ptr [rbx+6A8h]

EXCEPTION_RECORD: ffffd0017d75c1b8 -- (.exr 0xffffd0017d75c1b8)
ExceptionAddress: fffff800c49aa12b (atikmdag+0x00000000000c512b)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 00000000000006a8
Attempt to read from address 00000000000006a8

CONTEXT: ffffd0017d75b9c0 -- (.cxr 0xffffd0017d75b9c0;r)
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000001e00 rdi=0000000000000002
rip=fffff800c49aa12b rsp=ffffd0017d75c3f0 rbp=ffffe000659fb060
r8=0000000000000002 r9=000000f41035a000 r10=0000000000000000
r11=fffff800c367d447 r12=ffffe00065dc0500 r13=ffffe000657f3480
r14=ffffe00063c79740 r15=fffff800c48e5000
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+0xc512b:
fffff800`c49aa12b 488b83a8060000 mov rax,qword ptr [rbx+6A8h] ds:002b:00000000`000006a8=????????????????
Last set context:
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000001e00 rdi=0000000000000002
rip=fffff800c49aa12b rsp=ffffd0017d75c3f0 rbp=ffffe000659fb060
r8=0000000000000002 r9=000000f41035a000 r10=0000000000000000
r11=fffff800c367d447 r12=ffffe00065dc0500 r13=ffffe000657f3480
r14=ffffe00063c79740 r15=fffff800c48e5000
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+0xc512b:
fffff800`c49aa12b 488b83a8060000 mov rax,qword ptr [rbx+6A8h] ds:002b:00000000`000006a8=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 0

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

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: 00000000000006a8

READ_ADDRESS: 00000000000006a8

FOLLOWUP_IP:
atikmdag+c512b
fffff800`c49aa12b 488b83a8060000 mov rax,qword ptr [rbx+6A8h]

BUGCHECK_STR: AV

ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre

LAST_CONTROL_TRANSFER: from 0000000000000010 to fffff800c49aa12b

STACK_TEXT:
ffffd001`7d75c3f0 00000000`00000010 : 00000000`00000246 ffffd001`7d75c418 00000000`00000018 ffffe000`63c79740 : atikmdag+0xc512b
ffffd001`7d75c3f8 00000000`00000246 : ffffd001`7d75c418 00000000`00000018 ffffe000`63c79740 fffff800`c4a0945f : 0x10
ffffd001`7d75c400 ffffd001`7d75c418 : 00000000`00000018 ffffe000`63c79740 fffff800`c4a0945f 00000000`00000000 : 0x246
ffffd001`7d75c408 00000000`00000018 : ffffe000`63c79740 fffff800`c4a0945f 00000000`00000000 00000000`00000000 : 0xffffd001`7d75c418
ffffd001`7d75c410 ffffe000`63c79740 : fffff800`c4a0945f 00000000`00000000 00000000`00000000 00000000`00000000 : 0x18
ffffd001`7d75c418 fffff800`c4a0945f : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xffffe000`63c79740
ffffd001`7d75c420 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : atikmdag+0x12445f


SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: atikmdag+c512b

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: atikmdag

IMAGE_NAME: atikmdag.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 53572763

STACK_COMMAND: .cxr 0xffffd0017d75b9c0 ; kb

FAILURE_BUCKET_ID: AV_atikmdag+c512b

BUCKET_ID: AV_atikmdag+c512b

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:av_atikmdag+c512b

FAILURE_ID_HASH: {2fcea8d7-0bb3-85b3-1c64-7fe7ccbc474a}

Followup: MachineOwner
---------
 
Last edited:
nevermind on the help apperently windows decided it needed help checking for updates on new hardware drivers, sorry it took me so long to respond to this thread as easter plans took place and i was still unsure if i would crash or not but i havn't had a single crash since. thanks for viewing!
 
Hi trammel & welcome to the forums ^_^,

Glad to hear that you have solved the problem on your own. In case of any further problems, do not hesitate to post back and we would take a look on it :)


-Pranav
 
You must log in or register to reply here.

Similar threads

O
BSOD Microsoft-Windows-Kernel-Power - Random Crashes
Replies
1
Views
2K
axe0
axe0
L
Solved Random Crashes (No BSOD) - Event 41, Kernel-Power
2
Replies
25
Views
47K
timgarrow
T
S
Random BSOD CRASHES Multiple Times
Replies
6
Views
3K
axe0
axe0
O
Random BSOD Crashes, thought it was Blue Stacks but mb not
Replies
4
Views
9K
otaru1921
O
H
Solved BSOD, random crashes, PSU, Memory or other cause?
Replies
7
Views
9K
usasma
U
Back
Top