So I used the instructions in this: http://www.instructables.com/id/How-to-Analyze-a-BSOD-Crash-Dump/ article to analyze a crash dump. The results are were this:
Microsoft (R) Windows Debugger Version 6.3.9600.17298 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Only kernel address space is available
************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*C:\Windows\symbol_cache*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*C:\Windows\symbol_cache*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 = 0xfffff803`d5216000 PsLoadedModuleList = 0xfffff803`d54ef250
Debug session time: Sun Mar 22 20:30:26.090 2015 (UTC - 4:00)
System Uptime: 1 days 17:06:55.134
Loading Kernel Symbols
...............................................................
................................................................
...........................
Loading User Symbols
Loading unloaded module list
..................................................
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A0000001, {5, 0, 0, 0}
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
Probably caused by : atikmdag.sys ( atikmdag+2783e )
Followup: MachineOwner
---------
so i entered !analyze -v and I got this:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Unknown bugcheck code (a0000001)
Unknown bugcheck description
Arguments:
Arg1: 0000000000000005
Arg2: 0000000000000000
Arg3: 0000000000000000
Arg4: 0000000000000000
Debugging Details:
------------------
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: 0xA0000001
PROCESS_NAME: System
CURRENT_IRQL: 6
ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre
EXCEPTION_RECORD: fffff803d5519180 -- (.exr 0xfffff803d5519180)
ExceptionAddress: 0000000000000000
ExceptionCode: 00001f80
ExceptionFlags: 01000000
NumberParameters: -715707904
Parameter[0]: 0000000000000001
Parameter[1]: fffff803d6fa0c90
Parameter[2]: 0000000000000000
Parameter[3]: fffff803d55290d0
Parameter[4]: 0000000080050033
Parameter[5]: 0000000000000030
Parameter[6]: 00000000001aa000
Parameter[7]: 00000000001506f8
Parameter[8]: 0000000000000000
Parameter[9]: 0000000000000000
Parameter[10]: 0000000000000000
Parameter[11]: 0000000000000000
Parameter[12]: 00000000ffff0ff0
Parameter[13]: 0000000000000400
Parameter[14]: 007f000000000000
LAST_CONTROL_TRANSFER: from fffff800dc6b383e to fffff803d53669a0
STACK_TEXT:
fffff803`d6faeb58 fffff800`dc6b383e : 00000000`a0000001 00000000`00000005 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
fffff803`d6faeb60 fffff800`dc6c28e0 : 00000000`00000000 00000000`00000000 ffffe001`1a1b5030 00000000`00000078 : atikmdag+0x2783e
fffff803`d6faeba0 fffff800`dc70c9ed : ffffe001`1a241e50 00000000`00000000 00000000`00000282 fffff800`dc6c3eea : atikmdag+0x368e0
fffff803`d6faebd0 fffff800`dc70e4a0 : ffffe001`1a260f00 fffff800`dc6c1ea3 ffffe001`1a25c420 00000000`000000a0 : atikmdag+0x809ed
fffff803`d6faec50 fffff800`dc70e5dd : ffffe001`1a272580 fffff803`d6faedb1 00000000`00000000 fffff803`d6faedb1 : atikmdag+0x824a0
fffff803`d6faecd0 fffff800`dc70e69a : 00000000`00000001 fffff803`d526933e 00000000`00000000 00000000`00000000 : atikmdag+0x825dd
fffff803`d6faed10 fffff800`dc70e7b9 : ffffe001`1a241000 00000000`00000000 ffffe001`00000000 ffffe001`1a25b670 : atikmdag+0x8269a
fffff803`d6faee10 fffff800`dc716e11 : ffffe001`1a242cf0 ffffe001`1a251660 ffffe001`1a241000 fffff800`dc716c36 : atikmdag+0x827b9
fffff803`d6faee60 fffff800`dc70b30c : ffffe001`00000000 ffffe001`1a241000 00000000`00000001 00000000`00000001 : atikmdag+0x8ae11
fffff803`d6faeeb0 fffff800`dc6b067f : ffffe001`167f3a40 fffff803`d5519180 fffff803`d54d0660 ffffe001`1590a010 : atikmdag+0x7f30c
fffff803`d6faeee0 fffff800`dc46028a : fffff803`d6faefa0 fffff803`d52c9e1f ffffe001`158fc010 ffffe001`158c3000 : atikmdag+0x2467f
fffff803`d6faef10 fffff800`dc04cac1 : 00000000`00400a02 fffff803`d52c9f0c fffff800`dc04ca90 00000000`00006101 : atikmpag+0x928a
fffff803`d6faef40 fffff803`d52fbf32 : ffffd001`85abec80 00000000`00000000 ffff7be7`1a9cde8f 00000000`00000010 : dxgkrnl!DpiFdoMessageInterruptRoutine+0x31
fffff803`d6faef70 fffff803`d5367be8 : ffffd001`85abec80 ffffe001`199b6040 00000000`00000000 ffffe001`15889900 : nt!KiCallInterruptServiceRoutine+0x122
fffff803`d6faefb0 fffff803`d5367f3b : ffffe001`19c47430 00000000`00000001 ffffe001`19c47430 fffff803`d5519180 : nt!KiInterruptSubDispatch+0x108
fffff803`d6fa0ad0 fffff803`d536a4c2 : fffff803`d5519180 fffff803`d5519180 fffff803`d5572a00 00000000`00000000 : nt!KiInterruptDispatch+0xfb
fffff803`d6fa0c60 00000000`00000000 : fffff803`d6fa1000 fffff803`d6f9b000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x32
STACK_COMMAND: kb
FOLLOWUP_IP:
atikmdag+2783e
fffff800`dc6b383e cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: atikmdag+2783e
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: atikmdag
IMAGE_NAME: atikmdag.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 53b75741
FAILURE_BUCKET_ID: 0xA0000001_atikmdag+2783e
BUCKET_ID: 0xA0000001_atikmdag+2783e
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0xa0000001_atikmdag+2783e
FAILURE_ID_HASH: {58094d98-cc97-fc3c-4835-b683101627cd}
Followup: MachineOwner
I really don't know what any of this means, but I looked up atikmdag.sys and I believe it is a file related to my AMD drivers, right? So was this just a driver issue? If it doesn't happen again should I not worry about uninstalling and re-installing drivers? Thanks for your help.