View Single Post
Old 07-23-2008, 01:10 PM   #8 (permalink)
K1boRG
K1boRG's Avatar
 
Newb Techie

Join Date: Jul 2008

Location: Latvija

Posts: 28

K1boRG is on a distinguished road

Send a message via ICQ to K1boRG Send a message via MSN to K1boRG Send a message via Skype™ to K1boRG
Default Re: BSOD while playing Games...

CSS is ~2004 year game

WOW is 2004 game & its expansion is 2007 16th january released...

I have AMD Radeon HD 3650 512mb ddr-3 videocard...

Got another 2 BSOD

Code:
Use !analyze -v to get detailed debugging information.

BugCheck 1000000A, {c03b2258, 2, 0, 80510d72}

Probably caused by : memory_corruption ( nt!MiDeleteValidAddress+2e )

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
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 a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: c03b2258, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, bitfield :
	bit 0 : value 0 = read operation, 1 = write operation
	bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 80510d72, address which referenced memory

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


READ_ADDRESS:  c03b2258 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!MiDeleteValidAddress+2e
80510d72 8b0f            mov     ecx,dword ptr [edi]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  regedit.exe

LAST_CONTROL_TRANSFER:  from 805aee11 to 80510d72

STACK_TEXT:  
aa5ccc2c 805aee11 7644b001 8a1e77c8 007ffff8 nt!MiDeleteValidAddress+0x2e
aa5ccc4c 8051295d 8a1e77c8 8a1e7900 8a1e77c8 nt!MiDeleteAddressesInWorkingSet+0x65
aa5ccc80 805d114b 001e77c8 899d29b0 899d2bf8 nt!MmCleanProcessAddressSpace+0x193
aa5ccd08 805d130e 00000000 899d29b0 00000000 nt!PspExitThread+0x621
aa5ccd28 805d14e9 899d29b0 00000000 aa5ccd64 nt!PspTerminateThreadByPointer+0x52
aa5ccd54 805409ac 00000000 00000000 0007fecc nt!NtTerminateProcess+0x105
aa5ccd54 7c90eb94 00000000 00000000 0007fecc nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
0007fecc 00000000 00000000 00000000 00000000 0x7c90eb94


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiDeleteValidAddress+2e
80510d72 8b0f            mov     ecx,dword ptr [edi]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!MiDeleteValidAddress+2e

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  45e5484a

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  0xA_nt!MiDeleteValidAddress+2e

BUCKET_ID:  0xA_nt!MiDeleteValidAddress+2e

Followup: MachineOwner
---------
And 2nd BSOD log
Code:
Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, bf26c6ed, a9b5aab0, 0}

Probably caused by : ati3duag.dll ( ati3duag+d86ed )

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

3: 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: bf26c6ed, The address that the exception occurred at
Arg3: a9b5aab0, 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+d86ed
bf26c6ed 395004          cmp     dword ptr [eax+4],edx

TRAP_FRAME:  a9b5aab0 -- (.trap 0xffffffffa9b5aab0)
ErrCode = 00000000
eax=01000000 ebx=00000000 ecx=e10e7018 edx=00000003 esi=000000cc edi=e1287ba8
eip=bf26c6ed esp=a9b5ab24 ebp=00000000 iopl=0         nv up ei pl nz na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010206
ati3duag+0xd86ed:
bf26c6ed 395004          cmp     dword ptr [eax+4],edx ds:0023:01000004=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  2

DEFAULT_BUCKET_ID:  DRIVER_FAULT

BUGCHECK_STR:  0x8E

PROCESS_NAME:  IEXPLORE.EXE

LAST_CONTROL_TRANSFER:  from 00000000 to bf26c6ed

STACK_TEXT:  
00000000 00000000 00000000 00000000 00000000 ati3duag+0xd86ed


STACK_COMMAND:  kb

FOLLOWUP_IP: 
ati3duag+d86ed
bf26c6ed 395004          cmp     dword ptr [eax+4],edx

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  ati3duag+d86ed

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: ati3duag

IMAGE_NAME:  ati3duag.dll

DEBUG_FLR_IMAGE_TIMESTAMP:  486d9269

FAILURE_BUCKET_ID:  0x8E_ati3duag+d86ed

BUCKET_ID:  0x8E_ati3duag+d86ed

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

K1boRG is offline