This things driving me crazy.. i cant play any games.. i formet and reinstall everything again and it still crashes. I get a BSOD when playing games and its getting very aggrivating... heres my crash dump analysis.
My system is a 4200+x2
ati x1800xt
2gigs memory
500+ gb hd space
and i installed all the newest drivers for everything after i reformatted.
THANKS FOR YOUR HELP
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c0000005, bfb90900, abbfca2c, 0}
Probably caused by : ati3duag.dll ( ati3duag+d2900 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
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: c0000005, The exception code that was not handled
Arg2: bfb90900, The address that the exception occurred at
Arg3: abbfca2c, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".
FAULTING_IP:
ati3duag+d2900
bfb90900 f3a5 rep movs dword ptr es:[edi],dword ptr [esi]
TRAP_FRAME: abbfca2c -- (.trap 0xffffffffabbfca2c)
ErrCode = 00000000
eax=00017480 ebx=00000150 ecx=00000054 edx=00000150 esi=00133a28 edi=ac8b5bd8
eip=bfb90900 esp=abbfcaa0 ebp=e25dd10c iopl=0 nv up ei pl nz ac po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010212
ati3duag+0xd2900:
bfb90900 f3a5 rep movs dword ptr es:[edi],dword ptr [esi] es:0023:ac8b5bd8=ff000000 ds:0023:00133a28=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 2
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: RFx.exe
LAST_CONTROL_TRANSFER: from 8054ad24 to bfb90900
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
abbfcb84 8054ad24 892480c0 00144fff 892480e4 ati3duag+0xd2900
abbfcbe0 805af796 00000000 ffdff120 805af827 nt!ExAllocatePoolWithTag+0x3bc
abbfcc48 00000000 abbfcc38 abbfc524 abbfcd30 nt!MiSecureVirtualMemory+0x42a
STACK_COMMAND: kb
FOLLOWUP_IP:
ati3duag+d2900
bfb90900 f3a5 rep movs dword ptr es:[edi],dword ptr [esi]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: ati3duag+d2900
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: ati3duag
IMAGE_NAME: ati3duag.dll
DEBUG_FLR_IMAGE_TIMESTAMP: 45f8a3f9
FAILURE_BUCKET_ID: 0x8E_ati3duag+d2900
BUCKET_ID: 0x8E_ati3duag+d2900
Followup: MachineOwner
---------
0: kd> !analyze -v
My system is a 4200+x2
ati x1800xt
2gigs memory
500+ gb hd space
and i installed all the newest drivers for everything after i reformatted.
THANKS FOR YOUR HELP
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c0000005, bfb90900, abbfca2c, 0}
Probably caused by : ati3duag.dll ( ati3duag+d2900 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
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: c0000005, The exception code that was not handled
Arg2: bfb90900, The address that the exception occurred at
Arg3: abbfca2c, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".
FAULTING_IP:
ati3duag+d2900
bfb90900 f3a5 rep movs dword ptr es:[edi],dword ptr [esi]
TRAP_FRAME: abbfca2c -- (.trap 0xffffffffabbfca2c)
ErrCode = 00000000
eax=00017480 ebx=00000150 ecx=00000054 edx=00000150 esi=00133a28 edi=ac8b5bd8
eip=bfb90900 esp=abbfcaa0 ebp=e25dd10c iopl=0 nv up ei pl nz ac po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010212
ati3duag+0xd2900:
bfb90900 f3a5 rep movs dword ptr es:[edi],dword ptr [esi] es:0023:ac8b5bd8=ff000000 ds:0023:00133a28=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 2
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: RFx.exe
LAST_CONTROL_TRANSFER: from 8054ad24 to bfb90900
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
abbfcb84 8054ad24 892480c0 00144fff 892480e4 ati3duag+0xd2900
abbfcbe0 805af796 00000000 ffdff120 805af827 nt!ExAllocatePoolWithTag+0x3bc
abbfcc48 00000000 abbfcc38 abbfc524 abbfcd30 nt!MiSecureVirtualMemory+0x42a
STACK_COMMAND: kb
FOLLOWUP_IP:
ati3duag+d2900
bfb90900 f3a5 rep movs dword ptr es:[edi],dword ptr [esi]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: ati3duag+d2900
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: ati3duag
IMAGE_NAME: ati3duag.dll
DEBUG_FLR_IMAGE_TIMESTAMP: 45f8a3f9
FAILURE_BUCKET_ID: 0x8E_ati3duag+d2900
BUCKET_ID: 0x8E_ati3duag+d2900
Followup: MachineOwner
---------
0: kd> !analyze -v
Facebook
Twitter