Windows7 64-bit crashing in anygame 2

[Von do]

Hi, i'm expecting zigzag something I forgot the user name, sorry.
This is my secound thread. The problem is the exact same thing, Johnathan_King fixed it, but now its a even more badder after i got a new soundcard.....Thought it would help. But i got the graphics card(video) that Johnathan_King told me to get.
Then its perfectly fine until i got the soundcard......
Now Fix this please.

 

[Von do]

I'll get the dumps later.

 

[Von do]

Darn can't zip the dumps says i need permission but i'm the only user and the administrator and i'm using winrar

 

[Jonathan_King]

Be sure to copy the dmps to another location first, such as your desktop.

 

[Von do]

Be sure to copy the dmps to another location first, such as your desktop.

OOO awesome thanks i really want you 2 to help me
You guys rock

 

[Von do]

Minidumps for you!

Minidumps for you 2:

 

[Jonathan_King]

I still see your graphics driver as a cause, but I am now seeing meory corruption.

Download a copy of Memtest86 and burn the ISO to a CD using ImgBurn. Boot from the CD, and run at least 5 passes.

Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Jonathan\AppData\Local\Temp\Temp2_dumps.zip\040610-22640-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02c60000 PsLoadedModuleList = 0xfffff800`02e9de50
Debug session time: Tue Apr  6 17:34:08.278 2010 (GMT-4)
System Uptime: 0 days 2:52:25.247
Loading Kernel Symbols
...............................................................
................................................................
.............................
Loading User Symbols
Loading unloaded module list
.................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {ffffcb00187a7ac8, 0, fffff80002ceda7e, 7}


Could not read faulting driver name
Probably caused by : memory_corruption ( nt!MiUpdateWsle+19e )

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        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: ffffcb00187a7ac8, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff80002ceda7e, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000007, (reserved)

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


Could not read faulting driver name

OVERLAPPED_MODULE: Address regions for 'udfs' and 'usbaapl64.sy' overlap

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002f080e0
 ffffcb00187a7ac8 

FAULTING_IP: 
nt!MiUpdateWsle+19e
fffff800`02ceda7e 4b330cc7        xor     rcx,qword ptr [r15+r8*8]

MM_INTERNAL_CODE:  7

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  GTAIV.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff880061b9600 -- (.trap 0xfffff880061b9600)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff70001080488 rbx=0000000000000000 rcx=0000000000045368
rdx=0000000016da0000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002ceda7e rsp=fffff880061b9790 rbp=fffff70001080000
 r8=fffffa8002ee4ec8  r9=fffffa8001adf1e0 r10=fffff70001080488
r11=000000000004536e r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
nt!MiUpdateWsle+0x19e:
fffff800`02ceda7e 4b330cc7        xor     rcx,qword ptr [r15+r8*8] ds:97c0:ffffd400`17727640=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002d4fb19 to fffff80002cd1f00

STACK_TEXT:  
fffff880`061b9498 fffff800`02d4fb19 : 00000000`00000050 ffffcb00`187a7ac8 00000000`00000000 fffff880`061b9600 : nt!KeBugCheckEx
fffff880`061b94a0 fffff800`02ccffee : 00000000`00000000 00000000`16da0001 00000000`00002600 fffffa80`01adf1e0 : nt! ?? ::FNODOBFM::`string'+0x40edb
fffff880`061b9600 fffff800`02ceda7e : 00000000`00000001 00000000`00040004 00000000`00000002 00000000`00000000 : nt!KiPageFault+0x16e
fffff880`061b9790 fffff800`02cf89cd : 00000000`00045369 00000000`00000000 00000000`00000010 fffff800`02e4ae80 : nt!MiUpdateWsle+0x19e
fffff880`061b97f0 fffff800`02d03f2b : 36900000`8f50a025 00000000`8f50a921 fffffa80`01adf1e0 0000000f`ffffffff : nt!MiCompleteProtoPteFault+0x2cd
fffff880`061b9880 fffff800`02cf8599 : 00000000`00000000 00000000`8f50a880 fffffa80`041ac260 fffffa80`02ee4ec8 : nt!MiResolveTransitionFault+0x33b
fffff880`061b9910 fffff800`02cedd9e : 00000000`00000000 00000000`16da0000 fffff680`000b6d00 fffffa80`02ee4ec8 : nt!MiResolveProtoPteFault+0x419
fffff880`061b99b0 fffff800`02cebf23 : ffffffff`ffffff00 00000000`16da0000 00000000`00001000 fffff800`00000000 : nt!MiDispatchFault+0x1de
fffff880`061b9ac0 fffff800`02ccffee : 00000000`00000000 00000000`75981a75 fffffa80`00000001 fffffa80`0213f9b0 : nt!MmAccessFault+0x343
fffff880`061b9c20 00000000`74472c85 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
00000000`19e1f9a4 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x74472c85


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiUpdateWsle+19e
fffff800`02ceda7e 4b330cc7        xor     rcx,qword ptr [r15+r8*8]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!MiUpdateWsle+19e

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc600

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x50_nt!MiUpdateWsle+19e

BUCKET_ID:  X64_0x50_nt!MiUpdateWsle+19e

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

 

[Von do]

I still see your graphics driver as a cause, but I am now seeing meory corruption.

Download a copy of Memtest86 and burn the ISO to a CD using ImgBurn. Boot from the CD, and run at least 5 passes.

Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
 
 
Loading Dump File [C:\Users\Jonathan\AppData\Local\Temp\Temp2_dumps.zip\040610-22640-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
 
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02c60000 PsLoadedModuleList = 0xfffff800`02e9de50
Debug session time: Tue Apr  6 17:34:08.278 2010 (GMT-4)
System Uptime: 0 days 2:52:25.247
Loading Kernel Symbols
...............................................................
................................................................
.............................
Loading User Symbols
Loading unloaded module list
.................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
 
Use !analyze -v to get detailed debugging information.
 
BugCheck 50, {ffffcb00187a7ac8, 0, fffff80002ceda7e, 7}
 
 
Could not read faulting driver name
Probably caused by : memory_corruption ( nt!MiUpdateWsle+19e )
 
Followup: MachineOwner
---------
 
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        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: ffffcb00187a7ac8, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff80002ceda7e, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000007, (reserved)
 
Debugging Details:
------------------
 
 
Could not read faulting driver name
 
OVERLAPPED_MODULE: Address regions for 'udfs' and 'usbaapl64.sy' overlap
 
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002f080e0
 ffffcb00187a7ac8 
 
FAULTING_IP: 
nt!MiUpdateWsle+19e
fffff800`02ceda7e 4b330cc7        xor     rcx,qword ptr [r15+r8*8]
 
MM_INTERNAL_CODE:  7
 
CUSTOMER_CRASH_COUNT:  1
 
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
 
BUGCHECK_STR:  0x50
 
PROCESS_NAME:  GTAIV.exe
 
CURRENT_IRQL:  0
 
TRAP_FRAME:  fffff880061b9600 -- (.trap 0xfffff880061b9600)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff70001080488 rbx=0000000000000000 rcx=0000000000045368
rdx=0000000016da0000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002ceda7e rsp=fffff880061b9790 rbp=fffff70001080000
 r8=fffffa8002ee4ec8  r9=fffffa8001adf1e0 r10=fffff70001080488
r11=000000000004536e r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
nt!MiUpdateWsle+0x19e:
fffff800`02ceda7e 4b330cc7        xor     rcx,qword ptr [r15+r8*8] ds:97c0:ffffd400`17727640=????????????????
Resetting default scope
 
LAST_CONTROL_TRANSFER:  from fffff80002d4fb19 to fffff80002cd1f00
 
STACK_TEXT:  
fffff880`061b9498 fffff800`02d4fb19 : 00000000`00000050 ffffcb00`187a7ac8 00000000`00000000 fffff880`061b9600 : nt!KeBugCheckEx
fffff880`061b94a0 fffff800`02ccffee : 00000000`00000000 00000000`16da0001 00000000`00002600 fffffa80`01adf1e0 : nt! ?? ::FNODOBFM::`string'+0x40edb
fffff880`061b9600 fffff800`02ceda7e : 00000000`00000001 00000000`00040004 00000000`00000002 00000000`00000000 : nt!KiPageFault+0x16e
fffff880`061b9790 fffff800`02cf89cd : 00000000`00045369 00000000`00000000 00000000`00000010 fffff800`02e4ae80 : nt!MiUpdateWsle+0x19e
fffff880`061b97f0 fffff800`02d03f2b : 36900000`8f50a025 00000000`8f50a921 fffffa80`01adf1e0 0000000f`ffffffff : nt!MiCompleteProtoPteFault+0x2cd
fffff880`061b9880 fffff800`02cf8599 : 00000000`00000000 00000000`8f50a880 fffffa80`041ac260 fffffa80`02ee4ec8 : nt!MiResolveTransitionFault+0x33b
fffff880`061b9910 fffff800`02cedd9e : 00000000`00000000 00000000`16da0000 fffff680`000b6d00 fffffa80`02ee4ec8 : nt!MiResolveProtoPteFault+0x419
fffff880`061b99b0 fffff800`02cebf23 : ffffffff`ffffff00 00000000`16da0000 00000000`00001000 fffff800`00000000 : nt!MiDispatchFault+0x1de
fffff880`061b9ac0 fffff800`02ccffee : 00000000`00000000 00000000`75981a75 fffffa80`00000001 fffffa80`0213f9b0 : nt!MmAccessFault+0x343
fffff880`061b9c20 00000000`74472c85 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
00000000`19e1f9a4 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x74472c85
 
 
STACK_COMMAND:  kb
 
FOLLOWUP_IP: 
nt!MiUpdateWsle+19e
fffff800`02ceda7e 4b330cc7        xor     rcx,qword ptr [r15+r8*8]
 
SYMBOL_STACK_INDEX:  3
 
SYMBOL_NAME:  nt!MiUpdateWsle+19e
 
FOLLOWUP_NAME:  MachineOwner
 
MODULE_NAME: nt
 
DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc600
 
IMAGE_NAME:  memory_corruption
 
FAILURE_BUCKET_ID:  X64_0x50_nt!MiUpdateWsle+19e
 
BUCKET_ID:  X64_0x50_nt!MiUpdateWsle+19e
 
Followup: MachineOwner
---------

Soooo, can i burn it to drive D or E without a CD?

 

[Jonathan_King]

You don't have a CD drive, am I understanding right?

 

[Von do]

You don't have a CD drive, am I understanding right?

..........
...................
.................
................
...............
I do have a cd drive, but i don have a CD, so can i mount it?

 

[Tews]

You will need to burn memtest86 to a CD, then boot your computer from the CD..

 

[Jonathan_King]

I don't think so, you need to boot from it.

You can try the Windows Memory Diagnostic instead of Memtest. It's not the preferred program, but I guess it's better than nothing.

 

[Von do]

What now

If i run it about 5 times or whatever, what do i do next?
Is that it, and then do i need to update my graphics card again, coz i just checked theres another update

 

[Jonathan_King]

Update the card drivers first, then check for memory errors.

 

[Von do]

Update the card drivers first, then check for memory errors.

Affirmative

 

[Von do]

Well i tried the memory diagnosis before but when its almost done my computer overheated lol! :shock:

 

[Jonathan_King]

That might explain some problems. Open up your case, and vacuum the dust out. For the time being, leave the case open, and you may even want to blow a fan inside.

 

[Von do]

That might explain some problems. Open up your case, and vacuum the dust out. For the time being, leave the case open, and you may even want to blow a fan inside.

Awesome, that overheating problem stupid problem until u fixed it!
No more overheating!

 

[Von do]

This thread has been completed dun dun dah dah!!!

 

[Jonathan_King]

Great, be sure to let us know if you have more questions/problems.