0x0000003b bug code, and 0x000000c4 on driver verifier

Hello Shafmk1.

From the single crash dump you have uploaded, it appears that the BSOD is caused by ATI display driver.

Code:

fffff880`086ab4e8  fffff880`04815000 atikmdag
fffff880`086ab4f0  fffff880`04edbdf8 atikmdag+0x6c6df8
fffff880`086ab4f8  fffff880`04815000 atikmdag
fffff880`086ab500  fffff880`04ee9c88 atikmdag+0x6d4c88
fffff880`086ab508  fffff880`04815000 atikmdag
fffff880`086ab510  fffff880`04ee9be0 atikmdag+0x6d4be0
fffff880`086ab518  fffff880`04815000 atikmdag
fffff880`086ab520  fffff880`04ef27a8 atikmdag+0x6dd7a8
fffff880`086ab528  fffff880`04815000 atikmdag
fffff880`086ab530  fffff880`04ef2580 atikmdag+0x6dd580
fffff880`086ab538  fffff880`03f19000Unable to load image atikmpag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
 atikmpag
fffff880`086ab540  fffff880`03fa8324 atikmpag+0x8f324

And you are using a Beta display driver.

Code:

fffff880`03f19000 fffff880`03fb4000   atikmpag T (no symbols)           
    Loaded symbol image file: atikmpag.sys
    Image path: atikmpag.sys
    Image name: atikmpag.sys
    Timestamp:        Wed Jun 05 03:05:05 2013 (51AE5D89)
    CheckSum:         00099156
    ImageSize:        0009B000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Uninstall all the elements of the display driver using AMD Catalyst Un-install Utility . Then get the latest WHQL only from the link Latest AMD Catalyst Video Driver for Windows 7

   Information

WHQL
Release Date: April 24th 2013
Version: 13.4
In Device Manager: 12.104

If it BSODs even after doing it, next time post it following the Blue Screen of Death (BSOD) Posting Instructions.
________________________________________________________________________________
BSOD ANALYSIS:

Code:

..........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff8800483e125, fffff880086ab630, 0}

Probably caused by : Unknown_Image ( atikmdag+29125 )

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

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        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: fffff8800483e125, Address of the instruction which caused the bugcheck
Arg3: fffff880086ab630, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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+29125
fffff880`0483e125 488b4130        mov     rax,qword ptr [rcx+30h]

CONTEXT:  fffff880086ab630 -- (.cxr 0xfffff880086ab630)
rax=0100bdad9d18f188 rbx=000000f41069a010 rcx=0100bdad9d18f188
rdx=0000000000010000 rsi=0000000000000002 rdi=0100bdad9d18f188
rip=fffff8800483e125 rsp=fffff880086ac010 rbp=fffff880086ac010
 r8=0000000000000062  r9=0000000000400000 r10=0000000000000001
r11=0000000000000000 r12=fffff8a008d38158 r13=0000000000000004
r14=fffff8a008d38160 r15=fffff8a00a1d1930
iopl=0         nv up ei pl nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010206
atikmdag+0x29125:
fffff880`0483e125 488b4130        mov     rax,qword ptr [rcx+30h] ds:002b:0100bdad`9d18f1b8=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  WorldOfTanks.e

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff880086ac090 to fffff8800483e125

STACK_TEXT:  
fffff880`086ac010 fffff880`086ac090 : fffff880`048cc88e fffffa80`0ccd7a80 00000000`0000c000 fffff880`086ac140 : atikmdag+0x29125
fffff880`086ac018 fffff880`048cc88e : fffffa80`0ccd7a80 00000000`0000c000 fffff880`086ac140 fffff880`049277cc : 0xfffff880`086ac090
fffff880`086ac020 fffffa80`0ccd7a80 : 00000000`0000c000 fffff880`086ac140 fffff880`049277cc 00000000`00011fe0 : atikmdag+0xb788e
fffff880`086ac028 00000000`0000c000 : fffff880`086ac140 fffff880`049277cc 00000000`00011fe0 000000fd`fecd2000 : 0xfffffa80`0ccd7a80
fffff880`086ac030 fffff880`086ac140 : fffff880`049277cc 00000000`00011fe0 000000fd`fecd2000 fffff8a0`00bf7a40 : 0xc000
fffff880`086ac038 fffff880`049277cc : 00000000`00011fe0 000000fd`fecd2000 fffff8a0`00bf7a40 00000000`00000000 : 0xfffff880`086ac140
fffff880`086ac040 00000000`00011fe0 : 000000fd`fecd2000 fffff8a0`00bf7a40 00000000`00000000 fffffa80`0ca0ee01 : atikmdag+0x1127cc
fffff880`086ac048 000000fd`fecd2000 : fffff8a0`00bf7a40 00000000`00000000 fffffa80`0ca0ee01 fffffa80`0cace350 : 0x11fe0
fffff880`086ac050 fffff8a0`00bf7a40 : 00000000`00000000 fffffa80`0ca0ee01 fffffa80`0cace350 fffffa80`0f905000 : 0x000000fd`fecd2000
fffff880`086ac058 00000000`00000000 : fffffa80`0ca0ee01 fffffa80`0cace350 fffffa80`0f905000 00000000`00000000 : 0xfffff8a0`00bf7a40


FOLLOWUP_IP: 
atikmdag+29125
fffff880`0483e125 488b4130        mov     rax,qword ptr [rcx+30h]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  atikmdag+29125

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME:  Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP:  0

STACK_COMMAND:  .cxr 0xfffff880086ab630 ; kb

BUCKET_ID:  INVALID_KERNEL_CONTEXT

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

We ask all to post in BSOD threads following Blue Screen of Death (BSOD) Posting Instructions. A stray crash dump only is not enough information to debug.

But you are not required to go and do it right now. Take the suggestion of my earlier post first. Then if it is a BSOD again, then only post following Blue Screen of Death (BSOD) Posting Instructions.

It states clearly which driver you should install.

If the said driver fails to install, upload a screenshot of the failure message here following Screenshots and Files - Upload and Post in Seven Forums .

Set the overclocks back to normal, even if those are factory overclocks.

Code:

CPUID:        "Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3467

As you are getting BSODs, you should stop overclocking and run all the hardware components like CPU, GPU and RAM to their default settings. Also set the BIOS to default, too.
How To Clear CMOS (Reset BIOS)

Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

Make it sure that the OCZ-VERTEX4 SSD is running with Up-to-date firmware.
OCZ Toolbox: Firmware & BIOS Updates

Some network components are also found in the BSOD dump, and it is Realtek network driver, which is out of date..

Code:

fffff880`0433f000 fffff880`043f2000   Rt64win7 T (no symbols)           
    Loaded symbol image file: Rt64win7.sys
    Image path: Rt64win7.sys
    Image name: Rt64win7.sys
    Timestamp:        Tue Jun 12 19:30:29 2012 (4FD74B7D)
    CheckSum:         000B8CFC
    ImageSize:        000B3000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Update it, from Realtek .

Let us know the results.
____________________________________________________________________________
BSOD ANALYSIS:

Code:

.........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {e8, 2, 1, fffff88003c0a08a}

Probably caused by : memory_corruption

Followup: memory_corruption
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 00000000000000e8, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff88003c0a08a, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800030bd0e8
GetUlongFromAddress: unable to read from fffff800030bd198
 00000000000000e8 Nonpaged pool

CURRENT_IRQL:  2

FAULTING_IP: 
dxgmms1!VidSchiProcessCompletedQueuePacketInternal+162
fffff880`03c0a08a 490987e8000000  or      qword ptr [r15+0E8h],rax

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

BUGCHECK_STR:  0xD1

PROCESS_NAME:  WorldOfTanks.e

LAST_CONTROL_TRANSFER:  from 0000000000000000 to 0000000000000000

STACK_TEXT:  
00000000`00000000 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0


STACK_COMMAND:  .bugcheck ; kb

CHKIMG_EXTENSION: !chkimg -lo 50 -db !dxgmms1
6 errors : !dxgmms1 (fffff88003c0a082-fffff88003c0a0ba)
fffff88003c0a080  00  8b *4f  04  49  8b  c0  48  d3  e0 *49  09  87  e8  00  00 ..O.I..H..I.....
fffff88003c0a090  00  8b  43  44  8b  c8  c1  e9  13  41 *22  c8  74  04  a8  40 ..CD.....A".t..@
fffff88003c0a0a0  74  0a *4f  ba  e0  0f  0f  83  52  01 *40  00  0f  ba  e0  0b t.O.....R.@.....
fffff88003c0a0b0  73  0a  0f  ba  e0  0c  0f  83  42  01 *40  00  44  8b  ab  a0 s.......B.@.D...

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  STRIDE

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE

BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE

Followup: memory_corruption
---------