BSOD Windows 7 64-bit : Happening Frequently (again)

Last year, I was having frequent BSOD moments on my Windows 7 system. Following advise from koolkat77, I did remove Norton Antivirus and went with Avast as my virus provider. All was going well for quite some time. Until recently. I've added no new programs, but I've begun crashing to the BSOD on a frighteningly frequent basis (even several times a day)

Guidance would be keenly appreciated. I am considering a hammer and mallet to solve the problems.

Thanks,
moffett71 (Stephanie)

Hello Stephanie and welcome back to Seven Forums. Sorry it's under these circumstances. Hopefully koolkat will pop in shortly to offer her awesome expertise. In looking though the latest dump file bug check analysis, I noticed that the atikmdag.sys driver was being flagged. This is the ATI Video driver from AMD. It's recommended that you remove the Catalyst Control Center and only install the Display Driver. So I'd go to the AMD support site, make sure you have the latest driver, remove the catalyst control center, and see what happens.

Driver Reference Table - atikmdag.sys

http://support.amd.com/us/Pages/AMDSupportHub.aspx

Code:

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff6f880000038, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff80002edc501, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 0000000000000005, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030f8100
 fffff6f880000038 

FAULTING_IP: 
nt!MiDispatchFault+d1
fffff800`02edc501 4b8b1c1c        mov     rbx,qword ptr [r12+r11]

MM_INTERNAL_CODE:  5

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  OUTLOOK.EXE

CURRENT_IRQL:  0

TRAP_FRAME:  fffff8800ad1b820 -- (.trap 0xfffff8800ad1b820)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=f100000071182d1c rbx=0000000000000000 rcx=00000000f1000000
rdx=00000000ffffffff rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002edc501 rsp=fffff8800ad1b9b0 rbp=fffff68000057748
 r8=fffff10000007118  r9=0000000000000000 r10=0000000fffffffff
r11=fffff68000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
nt!MiDispatchFault+0xd1:
fffff800`02edc501 4b8b1c1c        mov     rbx,qword ptr [r12+r11] ds:fffff680`00000000=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002f3c673 to fffff80002ebfc40

STACK_TEXT:  
fffff880`0ad1b6b8 fffff800`02f3c673 : 00000000`00000050 fffff6f8`80000038 00000000`00000000 fffff880`0ad1b820 : nt!KeBugCheckEx
fffff880`0ad1b6c0 fffff800`02ebdd6e : 00000000`00000000 fffff6f8`80000038 fffffa80`0a5a8400 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x43801
fffff880`0ad1b820 fffff800`02edc501 : 00000000`00000570 00000000`000005f8 00000000`000001e0 00000000`000009a0 : nt!KiPageFault+0x16e
fffff880`0ad1b9b0 fffff800`02ecc269 : 00000000`00002358 00000000`0aee9970 00000000`00000250 fffff880`00000000 : nt!MiDispatchFault+0xd1
fffff880`0ad1bac0 fffff800`02ebdd6e : 00000000`00000000 00000000`0aee9970 00000000`00000001 00000000`0af81e60 : nt!MmAccessFault+0x359
fffff880`0ad1bc20 00000000`77c60608 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
00000000`03d8fb70 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77c60608


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiDispatchFault+d1
fffff800`02edc501 4b8b1c1c        mov     rbx,qword ptr [r12+r11]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!MiDispatchFault+d1

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  50e79935

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x50_nt!MiDispatchFault+d1

BUCKET_ID:  X64_0x50_nt!MiDispatchFault+d1

Followup: MachineOwner
-------------------------------------------------------
fffff880`0ad1b6f8  fffff880`04b7af15Unable to load image \SystemRoot\system32\DRIVERS\atikmdag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
 atikmdag+0x378f15
fffff880`0ad1b700  fffffa80`0843a000
fffff880`0ad1b708  fffff880`0484be48 atikmdag+0x49e48
--------------------------------------------------------

One other caution and a suggestion. When adding/deleting drivers it's a good idea to have a current restore point just in case something breaks. You would be able to return your computer to it's current condition and be no worse off than you are now.

System Restore Point - Create

System Restore

And the suggestion is to run a system file checker scan from an elevated command prompt (option two.) If problems are found, run the scan 3 times and immediately reboot the computer after each scan.

SFC /SCANNOW Command - System File Checker

And my apologies for jumping in. It's not my intent to interfere with the working relationship you've established with koolkat.

Marsmimar, thanks for the jump in. I've tried the changes and we'll see if this works.

Koolkat: The systems diagnostic version I have doesn't appear to collect the system info. Is there a newer version of the tool? I've looked around on the site and can't find one newer than the 2010 from Captn Jack.

Thanks!