BSOD in Windows 8 Pro 64-bit

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

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff880061260b5, Address of the instruction which caused the bugcheck
Arg3: fffff8800bf2efd0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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

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

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Instruktionen p 0x%08lx refererade till minnet p 0x%08lx. Det gick inte att utf ra en minnes tg rd. F ljande fel returnerades: The memory could not be %s.

FAULTING_IP:
atikmpag+480b5
fffff880`061260b5 488b9190000000 mov rdx,qword ptr [rcx+90h]

CONTEXT: fffff8800bf2efd0 -- (.cxr 0xfffff8800bf2efd0)
rax=fffff8a0166676d0 rbx=00000001000003c0 rcx=00000000003c0000
rdx=0000000000000030 rsi=fffffa8010620010 rdi=fffffa800e30e100
rip=fffff880061260b5 rsp=fffff8800bf2f9d0 rbp=fffff8800bf2f9d0
r8=000000000221c035 r9=00000000003c0000 r10=0000000000000801
r11=fffff8800bf30380 r12=00000000c0005f00 r13=fffff8a017a3b300
r14=fffffa800e30e180 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010206
atikmpag+0x480b5:
fffff880`061260b5 488b9190000000 mov rdx,qword ptr [rcx+90h] ds:002b:00000000`003c0090=????????????????
Resetting default scope

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0x3B

PROCESS_NAME: dwm.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff8800611e7de to fffff880061260b5

STACK_TEXT:
fffff880`0bf2f9d0 fffff880`0611e7de : 00000000`00000000 fffff880`0bf2fa00 fffffa80`10620010 fffff880`0bf30460 : atikmpag+0x480b5
fffff880`0bf2f9e0 fffff880`062fa0ab : fffffa80`0e30e180 fffffa80`0e30e180 00000000`0000001c 00000001`00000005 : atikmpag+0x407de
fffff880`0bf2fa10 fffff880`06312d10 : fffff880`0bf2fa80 fffff880`0630945a 00000000`00000000 fffff880`0bf2fa80 : atikmdag+0x9e0ab
fffff880`0bf2fa50 fffff880`0630bbab : 00000000`00000000 fffff880`062fa0b3 fffffa80`0cc25048 fffffa80`0e2e4900 : atikmdag+0xb6d10
fffff880`0bf2fa80 fffff880`06311cb5 : fffffa80`10620010 fffff880`0bf2fc00 00000000`00000001 00000000`00025bce : atikmdag+0xafbab
fffff880`0bf2fad0 fffff880`060ea6ab : fffffa80`0e30e1a0 fffff880`00000000 fffff8a0`00000000 00000000`00001ff0 : atikmdag+0xb5cb5
fffff880`0bf2fb90 fffff880`0589e24d : fffffa80`0e2e4900 fffff880`0bf30170 fffff880`0bf30400 fffff8a0`17ad7d00 : atikmpag+0xc6ab
fffff880`0bf2fe70 fffff880`058dd419 : fffff880`0bf30170 fffff880`0bf30731 fffff8a0`17a3b330 fffff880`0bf306e0 : dxgkrnl!ADAPTER_RENDER:diOpenAllocation+0x7d
fffff880`0bf2fec0 fffff880`058dc761 : fffff8a0`00125000 fffff880`0bf306e0 fffff880`0bf30420 fffff8a0`17ad7d00 : dxgkrnl!DXGDEVICE::OpenAllocations+0x259
fffff880`0bf2ff80 fffff880`058b4690 : 00000000`00000799 fffff880`0bf30731 00000000`00000000 00000000`00000701 : dxgkrnl!DXGDEVICE::CreateAllocation+0xdb1
fffff880`0bf30650 fffff880`058b3f1b : fffff8a0`00000238 fffff8a0`020556a0 fffff8a0`178116c0 00000000`00000000 : dxgkrnl!DXGDEVICE::OpenResource<_D3DKMT_OPENRESOURCEFROMNTHANDLE>+0x330
fffff880`0bf30770 fffff880`058b3b67 : fffffa80`12e0d080 00000000`00000301 fffff8a0`00000001 fffff8a0`17811600 : dxgkrnl!OpenResourceFromGlobalHandleOrNtObject<_D3DKMT_OPENRESOURCEFROMNTHANDLE>+0x36b
fffff880`0bf30950 fffff802`4dcd4453 : 0000004c`cf63de90 00000000`00000020 0000004c`cf63e2f0 00000000`00000001 : dxgkrnl!DxgkOpenResourceFromNtHandle+0x193
fffff880`0bf30a80 000007fd`c624233a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
0000004c`cf63de38 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x000007fd`c624233a


FOLLOWUP_IP:
atikmpag+480b5
fffff880`061260b5 488b9190000000 mov rdx,qword ptr [rcx+90h]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: atikmpag+480b5

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME: atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 5154e9d9

STACK_COMMAND: .cxr 0xfffff8800bf2efd0 ; kb

FAILURE_BUCKET_ID: 0x3B_atikmpag+480b5

BUCKET_ID: 0x3B_atikmpag+480b5

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

7: kd> lmvm atikmpag
start end module name
fffff880`060de000 fffff880`06172000 atikmpag (no symbols)
Loaded symbol image file: atikmpag.sys
Image path: \SystemRoot\system32\DRIVERS\atikmpag.sys
Image name: atikmpag.sys
Timestamp: Fri Mar 29 02:09:45 2013 (5154E9D9)
CheckSum: 00091A60
ImageSize: 00094000
File version: 8.14.1.6304
Product version: 8.14.1.6304
File flags: 8 (Mask 3F) Private
File OS: 40004 NT Win32
File type: 3.4 Driver
File date: 00000000.00000000
Translations: 0409.04b0
CompanyName: Advanced Micro Devices, Inc.
ProductName: AMD driver
InternalName: atikmpag.sys
OriginalFilename: atikmpag.sys
ProductVersion: 8.14.01.6304
FileVersion: 8.14.01.6304
FileDescription: AMD multi-vendor Miniport Driver
LegalCopyright: Copyright (C) 2007 Advanced Micro Devices, Inc.

Obviously you got yourself a problem with ATI video card. First thing is to find appropriate drivers for it, then uninstall current ones, switch to safe mode and clean up the remnants with Driver Cleaner or such and then install the new ones. Barring a hardware problem that should fix it.

But the AMD video card is not the cause to all crashes (I think). Have you checked the attached files?

The first place to start with is the AMD drivers - as they are blamed in the memory dump. You ran the lmvm command on atikmpag - and that's the AMD driver.

Also:
AMD OverDrive (AODDriver2.sys) is either a stand-alone application, or a component of the AMD VISION Engine Control Center. This driver is known to cause BSOD's on some Windows systems.

Please un-install all AMD/ATI video stuff from Control Panel...Programs...Un-install a program
Then, download (but DO NOT install) a fresh copy of the ATI drivers from Global Provider of Innovative Graphics, Processors and Media Solutions | AMD (in the upper right corner of the page)
Use this procedure to install the DRIVER ONLY: ATI video cards - DRIVER ONLY installation procedure - Sysnative Forums

If the device (AODDriver or AODDriver4.01) remains a problem, open Device Manager, select the "View" item.
Then select "Show hidden devices" and scroll down to the Non-Plug and Play Drivers section.
Locate the AODDriver entry, right click on it and select "Un-install". Reboot for changes to take affect.

Click to expand...

Sometimes the driver remains and continues to cause BSOD's. If this is the case for you, post back and we'll give further instructions for safely removing it.

If overclocking, please stop. Remove the overclock and return the system to stock/standard values while we're troubleshooting. Once the system is stable again, feel free to resume the overclocking.

In addition, the Western Digital software uses a 2008 driver (wdcsam64.sys Wed Apr 16 04:39:08 2008) that is known to cause BSOD's in Windows systems. Please uninstall the Western Digital software.

Please update these older drivers. Links are included to assist in looking up the source of the drivers. If unable to find an update, please remove (un-install) the program responsible for that driver. DO NOT manually delete/rename the driver as it may make the system unbootable! :

ladfDHP2amd64.sys Fri Sep 24 13:06:44 2010 (4C9CDAA4)
Logitech G35 Headset driver
http://www.carrona.org/drivers/driver.php?id=ladfDHP2amd64.sys

ladfSBVMamd64.sys Fri Sep 24 15:13:10 2010 (4C9CF846)
Logitech G35 Headset driver
http://www.carrona.org/drivers/driver.php?id=ladfSBVMamd64.sys

If this doesn't solve the BSOD's, please rerun the data collection app (your upload is missing some files) and let it run for at least 15 minutes (or until the app itself says that it's finished). Then zip it up and upload it with your next post.

Then, If all of this doesn't stop the BSOD's, please run Driver Verifier according to these instructions: Driver Verifier Settings




Analysis:
The following is for informational purposes only.

3rd Party Drivers:
The following is for information purposes only.
Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.
http://www.carrona.org/drivers/driver.php?id=wdcsam64.sys
http://www.carrona.org/drivers/driver.php?id=ladfDHP2amd64.sys
http://www.carrona.org/drivers/driver.php?id=ladfSBVMamd64.sys
http://www.carrona.org/drivers/driver.php?id=e1i63x64.sys
http://www.carrona.org/drivers/driver.php?id=AODDriver2.sys
http://www.carrona.org/drivers/driver.php?id=GEARAspiWDM.sys
http://www.carrona.org/drivers/driver.php?id=cpuz135_x64.sys
http://www.carrona.org/drivers/driver.php?id=AtihdW86.sys
http://www.carrona.org/drivers/driver.php?id=dump_storahci.sys
http://www.carrona.org/drivers/driver.php?id=atikmpag.sys
http://www.carrona.org/drivers/driver.php?id=atikmdag.sys

Thanks usasma, I was waiting for your reply.

I have uploaded the complete data collection from the app now. I will check all things you have mentioned in your post. Can you see if my BSOD/crashes are hardware or software related?

It is difficult to tell if it's hardware or software. This is because the lower-level drivers behave as if they were hardware (at times).
We generally rule out the software causes first - then we work on the hardware.

You have 3 hard drives. What is the make/model/wattage and age of your Power Supply?

SSD's were temperamental when they first came out, but their reliability has improved greatly over the last year or two. There are 2 things that MUST be checked on systems with BSOD's and SSD's:

1) That the SSD firmware is the latest available for the SSD
2) That the storage controller drivers on the motherboard are the most recent. They must date from late 2012 or later. This is ALL controllers, not just the one that the SSD is attached to.

Click to expand...

If you are concerned about it being a hardware problem, you can try these free hardware diagnostics: Hardware Diagnostics

I have a Corsair 750W Gold PSU, only one year old.

I have the latest firmware to my Samsung 830 SSD according to Samsung Magician software. However, I dont have a clue about the storage controller drivers. I have the latest BIOS. I thought these drivers was updated automatically via Windows Update.
This is my motherboard: http://www.asus.com/Motherboards/CROSSHAIR_V_FORMULAZ

Windows update drivers from their database, for this one go to Asus site.

Windows Update only provides drivers that the manufacturer's upload to the Windows Update site. These are notoriously outdated and we tell people NEVER to use them when having BSOD issues.

You have the following controllers:

• StorageAMD SB950 controller :
  6 x SATA 6Gb/s port(s), red
  Support Raid 0, 1, 5, 10
  ASMedia® ASM1061 controller :
  2 x SATA 6Gb/s port(s), red
  2 x eSATA 6Gb/s port(s), red
  

Click to expand...

I don't usually check the controllers if they don't show up in the memory dumps. And in this case they aren't there (except for the dump_storahci.sys driver - and it dates from 2013). I wouldn't worry about that right now.