Windows 7 Various BSOD's - CPU-Z & Minidumps - Please Help!!

[RoaRk88]

I have experienced several different BSOD's over the past month, so I have attached the most recent 6 minidumps. I ran antivirus, antispy, swept the graphics drivers and reinstalled according to manufacturer's site, ran a memtest (pass), and cleaned the registry after suspecting a missing or corrupt entry. I'm starting to think it's faulty hardware (graphics or memory).

This usually occurs when I'm watching videos online, or more recently playing Minecraft. My laptop (see specs) ran Counter-Strike Source (or Half Life 2) perfectly fine without incidence, but something is amiss now. I can not for the life of me figure the cause of this out, so I'm really hoping for help here!

Please take a look and let me know what you see. Any help is greatly appreciated!

HP Pavilion dv6-2043us
ATI Mobility Radeon HD 4200 Series
Windows 7 64-bit

Let me know what others specs, screenshots, questions you might have.

Thanks all!

View attachment Dumps.zip

 

[Captain Jack]

Hello there,

Seems like it could be some Hardware that's causing the system to crash. I would recommend a full Hardware Diagnostic (MemTest 8 passes) (RAM, Hard drive and Graphic card) Hardware Diagnostic | Captain Debugger

Reinstall you display drivers follow this guide nVidia Driver Cleanup Guide | Captain Debugger even it's for nVidia it works for ATI as well.

If your Overclocking please revert to default settings. Also check your motherboard manual for RAM voltage and set it correctly.

Update these drivers :

iirsp.sys    Wed Dec 14 03:17:54 2005
nfrd960.sys  Wed Jun 07 02:41:48 2006
arc.sys      Fri May 25 02:57:55 2007
adpu320.sys  Wed Feb 28 05:34:15 2007
adpahci.sys  Tue May 01 23:00:09 2007 
adp94xx.sys  Sat Dec 06 05:24:42 2008
lsi_fc.sys   Wed Dec 10 04:16:09 2008
SiSRaid2.sys Wed Sep 24 23:58:20 2008

Check this guide: How to Update Drivers on Windows 7 | Captain Debugger

Bugcheck:

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: fffff880053e1fc5, The address that the exception occurred at
Arg3: fffff880029f06c8, Exception Record Address
Arg4: fffff880029eff20, 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+376fc5
fffff880`053e1fc5 488b4118        mov     rax,qword ptr [rcx+18h]

EXCEPTION_RECORD:  fffff880029f06c8 -- (.exr 0xfffff880029f06c8)
ExceptionAddress: fffff880053e1fc5 (atikmdag+0x0000000000376fc5)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  fffff880029eff20 -- (.cxr 0xfffff880029eff20)
rax=fffff8a00a4f7700 rbx=fffff8a000111558 rcx=00fff8a00ad85988
rdx=fffff880029f09f0 rsi=fffff8a000111000 rdi=0000000000000091
rip=fffff880053e1fc5 rsp=fffff880029f0908 rbp=0000000000000039
 r8=fffffa8004205010  r9=fffff880055ae6a0 r10=00000000c511a00c
r11=0000000000000000 r12=fffff8a008b71a80 r13=0000000000000091
r14=fffffa8004205010 r15=fffffa8003ca7300
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+0x376fc5:
fffff880`053e1fc5 488b4118        mov     rax,qword ptr [rcx+18h] ds:002b:00fff8a0`0ad859a0=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_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:  ffffffffffffffff

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ebb100
 ffffffffffffffff 

FOLLOWUP_IP: 
atikmdag+376fc5
fffff880`053e1fc5 488b4118        mov     rax,qword ptr [rcx+18h]

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from fffff8800542807f to fffff880053e1fc5

STACK_TEXT:  
fffff880`029f0908 fffff880`0542807f : 00000000`00000000 00000000`00000001 00000000`00000091 fffffa80`04876d88 : atikmdag+0x376fc5
fffff880`029f0910 00000000`00000000 : 00000000`00000001 00000000`00000091 fffffa80`04876d88 fffffa80`03ca7300 : atikmdag+0x3bd07f


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  atikmdag+376fc5

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmdag

IMAGE_NAME:  atikmdag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ddc6c20

STACK_COMMAND:  .cxr 0xfffff880029eff20 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_atikmdag+376fc5

BUCKET_ID:  X64_0x7E_atikmdag+376fc5

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