once haunted BSOD pc again haunted :(

[Cambria]

hey there,

after great help from here i solved BSOD problems, sadly they are back now

Is Windows 7 . . .
- x86 (32-bit) or x64 ?
x64
- the original installed OS on the system?
win7, clean install
- an OEM or full retail version?
retail
- OEM = came pre-installed on system
- Full Retail = you purchased it from retailer

- What is the age of system (hardware)?
bought all but the SSD in august 2010, the SSD came in june 2011
- What is the age of OS installation (have you re-installed the OS?)
reinstalled when SSD came, so 2 weeks

what i already did:
memtest86, ran for 5 passes and passed
update video drivers, didnt help
put back stock clockings
monitoring heat, cpu doesnt reach 50 and gpu doesnt reach 70


EDIT: ps, things might be in dutch. i'll translate them if you want me to

 

[Maguscreed]

It looks like you are having problems with the ati driver.

Let's wipe the current installation with this tool.
Phyxion.net - Driver Sweeper

and reinstall the latest version of your driver from a fresh download.
AMD Graphics Drivers & Software

KMODE_EXCEPTION_NOT_HANDLED (1e)
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.
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

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


EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.

FAULTING_IP: 
+3837356334626561
00000000`00000000 ??              ???

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0

BUGCHECK_STR:  0x1E_0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  2

EXCEPTION_RECORD:  fffff88002ffd428 -- (.exr 0xfffff88002ffd428)
ExceptionAddress: fffff8800410cb3d (dxgmms1!VIDMM_GLOBAL::UnreferenceDmaBuffer+0x000000000000007d)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

TRAP_FRAME:  fffff88002ffd4d0 -- (.trap 0xfffff88002ffd4d0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=f7fffa8004e6a700 rbx=0000000000000000 rcx=fffffa8004bec010
rdx=fffffa8004c19480 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800410cb3d rsp=fffff88002ffd660 rbp=fffffa8004bdf540
 r8=0000000000000002  r9=fffffa8005345038 r10=fffffa8004b817d0
r11=fffff88002ffda10 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
dxgmms1!VIDMM_GLOBAL::UnreferenceDmaBuffer+0x7d:
fffff880`0410cb3d f0834018ff      lock add dword ptr [rax+18h],0FFFFFFFFh ds:9b58:f7fffa80`04e6a718=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002a946be to fffff80002a9ccd0

STACK_TEXT:  
fffff880`02ffc508 fffff800`02a946be : 00000200`00020000 00010000`01000002 fffff880`02ffcc80 fffff800`02ac8890 : nt!KeBugCheck
fffff880`02ffc510 fffff800`02ac855d : fffff800`02ca3968 fffff800`02be0cbc fffff800`02a1d000 fffff880`02ffd428 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`02ffc540 fffff800`02ac7335 : fffff800`02be40fc fffff880`02ffc5b8 fffff880`02ffd428 fffff800`02a1d000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`02ffc570 fffff800`02ad83b1 : fffff880`02ffd428 fffff880`02ffcc80 fffff880`00000000 fffffa80`00000004 : nt!RtlDispatchException+0x415
fffff880`02ffcc50 fffff800`02a9c382 : fffff880`02ffd428 fffffa80`04b859c0 fffff880`02ffd4d0 fffffa80`04c19480 : nt!KiDispatchException+0x135
fffff880`02ffd2f0 fffff800`02a9ac8a : 00000000`00000000 fffff800`02aa303a fffffa80`043c7f00 fffff880`03f690c6 : nt!KiExceptionDispatch+0xc2
fffff880`02ffd4d0 fffff880`0410cb3d : 00000000`00000000 fffffa80`04900000 fffffa80`04b81010 fffffa80`04bdf540 : nt!KiGeneralProtectionFault+0x10a
fffff880`02ffd660 fffff880`04110677 : fffffa80`04900000 fffffa80`04b81010 fffffa80`04b84000 fffff880`04905730 : dxgmms1!VIDMM_GLOBAL::UnreferenceDmaBuffer+0x7d
fffff880`02ffd690 fffff880`0410fe00 : 00000000`00000000 fffffa80`04b81010 fffffa80`04b85ab0 fffffa80`04b81010 : dxgmms1!VidSchiProcessDpcCompletedPacket+0x253
fffff880`02ffd730 fffff880`0410fc4c : 00029105`60000400 fffffa80`04b81010 00000000`00000000 fffffa80`04900000 : dxgmms1!VidSchDdiNotifyDpcWorker+0x198
fffff880`02ffd780 fffff880`040161cf : fffffa80`043c6040 00000000`00000000 00000000`00000001 fffffa80`049120d0 : dxgmms1!VidSchDdiNotifyDpc+0x94
fffff880`02ffd7d0 fffff880`048f4d31 : fffffa80`03a00000 fffffa80`03a00000 fffffa80`04900000 00000000`00000001 : dxgkrnl!DxgNotifyDpcCB+0x77
fffff880`02ffd800 fffffa80`03a00000 : fffffa80`03a00000 fffffa80`04900000 00000000`00000001 fffffa80`04922ef0 : atikmdag+0x4dd31
fffff880`02ffd808 fffffa80`03a00000 : fffffa80`04900000 00000000`00000001 fffffa80`04922ef0 fffff880`04905730 : 0xfffffa80`03a00000
fffff880`02ffd810 fffffa80`04900000 : 00000000`00000001 fffffa80`04922ef0 fffff880`04905730 00000000`00000000 : 0xfffffa80`03a00000
fffff880`02ffd818 00000000`00000001 : fffffa80`04922ef0 fffff880`04905730 00000000`00000000 00000000`00000000 : 0xfffffa80`04900000
fffff880`02ffd820 fffffa80`04922ef0 : fffff880`04905730 00000000`00000000 00000000`00000000 00000000`00000000 : 0x1
fffff880`02ffd828 fffff880`04905730 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff880`049955c7 : 0xfffffa80`04922ef0
fffff880`02ffd830 00000000`00000000 : 00000000`00000000 00000000`00000000 fffff880`049955c7 fffffa80`04922e70 : atikmdag+0x5e730


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dxgmms1!VIDMM_GLOBAL::UnreferenceDmaBuffer+7d
fffff880`0410cb3d f0834018ff      lock add dword ptr [rax+18h],0FFFFFFFFh

SYMBOL_STACK_INDEX:  7

SYMBOL_NAME:  dxgmms1!VIDMM_GLOBAL::UnreferenceDmaBuffer+7d

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce799c1

FAILURE_BUCKET_ID:  X64_0x1E_0_dxgmms1!VIDMM_GLOBAL::UnreferenceDmaBuffer+7d

BUCKET_ID:  X64_0x1E_0_dxgmms1!VIDMM_GLOBAL::UnreferenceDmaBuffer+7d

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

 

[Cambria]

wow... that was FAST

ill try that and get back to you

 

[Maguscreed]

normally it would take longer but I've seen this specific debug result quite a few times now.

 

[Cambria]

okay, i sweeped the driver in safe mode. when i reboot and check it again tho i still see amd display in the list? this is correct?

 

[Maguscreed]

Just so long as we wiped everything, the computer probably reinstalled the default driver for the device when you rebooted, just go ahead and update from the amd/ati link I gave above.

 

[Cambria]

okay, installed the driver again, any way to test if its working fine again? or is it just waiting?

 

[Maguscreed]

yeah, it's a wait and see thing now.
If it does happen again just post the newest minidump along with the update post.

 

[Cambria]

hey again,

after the driver update it worked for about 3 hours. now, when starting a movie i got the BSOD again driver blamed atikmdag.sys again

 

[Maguscreed]

You don't have anything overclocked at all do you?
Using driver sweeper should have cleaned out the problem we shouldn't still be seeing the same error here.

hmmm... here's something to test, create a new user account (possibly a temporary measure)
Boot into the new account try playing the same video and see if you experience the crash again.

...just checking that we do still in fact have a video driver issue and not a user account setting issue.

 

[Cambria]

hey,

once i restarted i could play the movie just normally. i'll try if i get any BSODs in the new account

thanks

EDIT: got the BSOD in SC II this time, on the new account
EDIT2: ohh and to answer your question, i havent overclocked anything ANYMORE. that was the first thing i put back (i had the multiplier on 17, i know its low, now its on auto again). i DO use an overclocking program which runs on the background to monitor my gpu heat, the program is called MSI afterburner but i didnt touch the clockings

 

[Cambria]

sorry for double post, but the BSOD happened again this time in SC II too

 

[Cambria]

hey again,

blue screens got worse when i get lucky i can play for about 30 minutes. when i get lucky ill try to upload the jcgriff report

i do get the message atikmdag in the bsod, which i find odd cuz i just updated the videodriver again (although, site says 15/6/2011 and the driver is 14/5/2011)

EDIT: cant get in safemode too, driver it blue screens on is CLASSPNP.SYS

 

[Maguscreed]

A device is obviously causing you problems, when you are gaming I would unplug everything from the computer but internet mouse and keyboard.
If you have any additional usb devices/external drives I would disconnect them when gaming just to trim down the number of possible causes.

It's pointing directly to the ati driver as the source of the crash in your latest dumps.
I'm starting to become concerned that there may be a problem with the card itself.

Does your system have internal graphics you can fall back on just to boot with?
Keep in mind we're unplugging everything but the absolutely required things to make the computer power on.

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: fffff88004cce0b5, The address that the exception occurred at
Arg3: fffff88003d0e9e8, Exception Record Address
Arg4: fffff88003d0e240, 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+4840b5
fffff880`04cce0b5 66413100        xor     word ptr [r8],ax

EXCEPTION_RECORD:  fffff88003d0e9e8 -- (.exr 0xfffff88003d0e9e8)
ExceptionAddress: fffff88004cce0b5 (atikmdag+0x00000000004840b5)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  fffff88003d0e240 -- (.cxr 0xfffff88003d0e240)
rax=000000000000f13c rbx=0000000000000000 rcx=0000000000000018
rdx=fffff88003d0ec70 rsi=cccccccccccccccd rdi=0000000000000000
rip=fffff88004cce0b5 rsp=fffff88003d0ec28 rbp=0000000000000400
 r8=0ec3f88004cce0cb  r9=fffff88003d0ec70 r10=0000004dbb746aca
r11=0000000000000143 r12=0000000000000000 r13=0000000000002bf0
r14=0000000000000020 r15=0000000000000000
iopl=0         nv up di pl nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010006
atikmdag+0x4840b5:
fffff880`04cce0b5 66413100        xor     word ptr [r8],ax ds:002b:0ec3f880`04cce0cb=????
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 fffff80002cb4100
 ffffffffffffffff 

FOLLOWUP_IP: 
atikmdag+4840b5
fffff880`04cce0b5 66413100        xor     word ptr [r8],ax

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from fffff88004c8f1df to fffff88004cce0b5

STACK_TEXT:  
fffff880`03d0ec28 fffff880`04c8f1df : 00000000`00000004 cccccccc`00000000 00000000`00000000 00000000`00000000 : atikmdag+0x4840b5
fffff880`03d0ec30 00000000`00000004 : cccccccc`00000000 00000000`00000000 00000000`00000000 fffff880`009e9180 : atikmdag+0x4451df
fffff880`03d0ec38 cccccccc`00000000 : 00000000`00000000 00000000`00000000 fffff880`009e9180 fffff8a0`00067335 : 0x4
fffff880`03d0ec40 00000000`00000000 : 00000000`00000000 fffff880`009e9180 fffff8a0`00067335 00000008`0000015f : 0xcccccccc`00000000


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  atikmdag+4840b5

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmdag

IMAGE_NAME:  atikmdag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ddc6c20

STACK_COMMAND:  .cxr 0xfffff88003d0e240 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_atikmdag+4840b5

BUCKET_ID:  X64_0x7E_atikmdag+4840b5

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

 

[Cambria]

hey,

i've had an external usb hard drive in it all the time, i cant really test anything now because my PSU gave up. every time i plug it in it short circuits something, it's being RMA'd at the moment

DD