ArmA 2 BSOD

[-Snafu- 77]

A week or two ago I had a number of BSODs with ArmA 2 and followed some instructions on finding and reading the dump files.

I asked about it on another forum but did not get any help and forgot about it.

It happened again today so located the new file and did the same.

Here is the older one:

Microsoft ® Windows Debugger Version 6.11.0001.404 X86

Copyright © Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Windows\Minidump\122209-16723-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 (8 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS Personal

Built by: 7600.16385.amd64fre.win7_rtm.090713-1255

Machine Name:

Kernel base = 0xfffff800`02e00000 PsLoadedModuleList = 0xfffff800`0303de50

Debug session time: Tue Dec 22 22:27:13.288 2009 (GMT+0)

System Uptime: 0 days 0:22:32.536

Loading Kernel Symbols

...............................................................

................................................................

......................

Loading User Symbols

Loading unloaded module list

.......

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff80022e7554b, 8, fffff80022e7554b, 2}

Could not read faulting driver name

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+40f90 )

Followup: MachineOwner

---------

7: 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: fffff80022e7554b, memory referenced.

Arg2: 0000000000000008, value 0 = read operation, 1 = write operation.

Arg3: fffff80022e7554b, If non-zero, the instruction address which referenced the bad memory

address.

Arg4: 0000000000000002, (reserved)

Debugging Details:

------------------

Could not read faulting driver name

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800030a80e0

fffff80022e7554b

FAULTING_IP:

+717d952f0488df9c

fffff800`22e7554b ?? ???

MM_INTERNAL_CODE: 2

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x50

PROCESS_NAME: audiodg.exe

CURRENT_IRQL: 0

TRAP_FRAME: fffff88003eda050 -- (.trap 0xfffff88003eda050)

NOTE: The trap frame does not contain all registers.

Some register values may be zeroed or incorrect.

rax=0000000000000002 rbx=0000000000000000 rcx=0000000000000000

rdx=00000000000007ff rsi=0000000000000000 rdi=0000000000000000

rip=fffff80022e7554b rsp=fffff88003eda1e0 rbp=fffffa80062c7210

r8=fffffa800554c0e8 r9=0000000000000000 r10=ffffffffffffff7f

r11=fffffa80073c6c00 r12=0000000000000000 r13=0000000000000000

r14=0000000000000000 r15=0000000000000000

iopl=0 nv up ei ng nz na pe nc

fffff800`22e7554b ?? ???

Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80002eefbc2 to fffff80002e71f00

STACK_TEXT:

fffff880`03ed9ee8 fffff800`02eefbc2 : 00000000`00000050 fffff800`22e7554b 00000000`00000008 fffff880`03eda050 : nt!KeBugCheckEx

fffff880`03ed9ef0 fffff800`02e6ffee : 00000000`00000008 fffffa80`062c7168 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x40f90

fffff880`03eda050 fffff800`22e7554b : 00000000`00000000 00000000`00000000 fffffa80`00000000 00000000`00000000 : nt!KiPageFault+0x16e

fffff880`03eda1e0 00000000`00000000 : 00000000`00000000 fffffa80`00000000 00000000`00000000 00000000`063a5d00 : 0xfffff800`22e7554b

STACK_COMMAND: kb

FOLLOWUP_IP:

nt! ?? ::FNODOBFM::`string'+40f90

fffff800`02eefbc2 cc int 3

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+40f90

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc600

FAILURE_BUCKET_ID: X64_0x50_nt!_??_::FNODOBFM::_string_+40f90

BUCKET_ID: X64_0x50_nt!_??_::FNODOBFM::_string_+40f90

Followup: MachineOwner

The latest one:

Microsoft ® Windows Debugger Version 6.11.0001.404 X86

Copyright © Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Windows\Minidump\010410-21652-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 (8 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS Personal

Built by: 7600.16385.amd64fre.win7_rtm.090713-1255

Machine Name:

Kernel base = 0xfffff800`02e0d000 PsLoadedModuleList = 0xfffff800`0304ae50

Debug session time: Mon Jan 4 19:10:06.829 2010 (GMT+0)

System Uptime: 0 days 7:40:08.077

Loading Kernel Symbols

...............................................................

................................................................

......................

Loading User Symbols

Loading unloaded module list

.....

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffffa80279705f0, 0, fffff80002fb241d, 2}

Unable to load image \SystemRoot\System32\win32k.sys, Win32 error 0n2

*** WARNING: Unable to verify timestamp for win32k.sys

*** ERROR: Module load completed but symbols could not be loaded for win32k.sys

Could not read faulting driver name

Probably caused by : win32k.sys ( win32k+c8c3a )

Followup: MachineOwner

---------

3: 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: fffffa80279705f0, memory referenced.

Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.

Arg3: fffff80002fb241d, If non-zero, the instruction address which referenced the bad memory

address.

Arg4: 0000000000000002, (reserved)

Debugging Details:

------------------

Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030b50e0

fffffa80279705f0

FAULTING_IP:

nt!ExFreePoolWithTag+36d

fffff800`02fb241d 0fb606 movzx eax,byte ptr [rsi]

MM_INTERNAL_CODE: 2

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x50

PROCESS_NAME: arma2.exe

CURRENT_IRQL: 0

TRAP_FRAME: fffff88006db57f0 -- (.trap 0xfffff88006db57f0)

NOTE: The trap frame does not contain all registers.

Some register values may be zeroed or incorrect.

rax=0000000000015500 rbx=0000000000000000 rcx=000000000000010e

rdx=000000000000002d rsi=0000000000000000 rdi=0000000000000000

rip=fffff80002fb241d rsp=fffff88006db5980 rbp=0000000000000000

r8=0000000000000870 r9=00000000000003e0 r10=fffff80002e0d000

r11=0000000000000036 r12=0000000000000000 r13=0000000000000000

r14=0000000000000000 r15=0000000000000000

iopl=0 nv up ei ng nz na po nc

nt!ExFreePoolWithTag+0x36d:

fffff800`02fb241d 0fb606 movzx eax,byte ptr [rsi] ds:a800:00000000`00000000=??

Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80002efcbc2 to fffff80002e7ef00

STACK_TEXT:

fffff880`06db5688 fffff800`02efcbc2 : 00000000`00000050 fffffa80`279705f0 00000000`00000000 fffff880`06db57f0 : nt!KeBugCheckEx

fffff880`06db5690 fffff800`02e7cfee : 00000000`00000000 fffff900`c2453240 fffff900`00000000 00000000`00000003 : nt! ?? ::FNODOBFM::`string'+0x40f90

fffff880`06db57f0 fffff800`02fb241d : fffffa80`05507aa0 00000000`00000070 00000000`00000001 fffffa80`07970700 : nt!KiPageFault+0x16e

fffff880`06db5980 fffff960`000c8c3a : fffffa80`079705f0 fffff900`c2453250 00000000`69747355 fffff900`c2453250 : nt!ExFreePoolWithTag+0x36d

fffff880`06db5a30 fffffa80`079705f0 : fffff900`c2453250 00000000`69747355 fffff900`c2453250 00000000`00000001 : win32k+0xc8c3a

fffff880`06db5a38 fffff900`c2453250 : 00000000`69747355 fffff900`c2453250 00000000`00000001 fffff960`000c6bd9 : 0xfffffa80`079705f0

fffff880`06db5a40 00000000`69747355 : fffff900`c2453250 00000000`00000001 fffff960`000c6bd9 fffffa80`09078b60 : 0xfffff900`c2453250

fffff880`06db5a48 fffff900`c2453250 : 00000000`00000001 fffff960`000c6bd9 fffffa80`09078b60 fffffa80`09078b60 : 0x69747355

fffff880`06db5a50 00000000`00000001 : fffff960`000c6bd9 fffffa80`09078b60 fffffa80`09078b60 fffffa80`072d4950 : 0xfffff900`c2453250

fffff880`06db5a58 fffff960`000c6bd9 : fffffa80`09078b60 fffffa80`09078b60 fffffa80`072d4950 fffff900`c2453250 : 0x1

fffff880`06db5a60 fffffa80`09078b60 : fffffa80`09078b60 fffffa80`072d4950 fffff900`c2453250 00000000`00000000 : win32k+0xc6bd9

fffff880`06db5a68 fffffa80`09078b60 : fffffa80`072d4950 fffff900`c2453250 00000000`00000000 fffff960`000c3c1c : 0xfffffa80`09078b60

fffff880`06db5a70 fffffa80`072d4950 : fffff900`c2453250 00000000`00000000 fffff960`000c3c1c fffffa80`0731be60 : 0xfffffa80`09078b60

fffff880`06db5a78 fffff900`c2453250 : 00000000`00000000 fffff960`000c3c1c fffffa80`0731be60 fffffa80`09078b60 : 0xfffffa80`072d4950

fffff880`06db5a80 00000000`00000000 : fffff960`000c3c1c fffffa80`0731be60 fffffa80`09078b60 fffffa80`09078b60 : 0xfffff900`c2453250

STACK_COMMAND: kb

FOLLOWUP_IP:

win32k+c8c3a

fffff960`000c8c3a ?? ???

SYMBOL_STACK_INDEX: 4

SYMBOL_NAME: win32k+c8c3a

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: win32k

IMAGE_NAME: win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc5e1

FAILURE_BUCKET_ID: X64_0x50_win32k+c8c3a

BUCKET_ID: X64_0x50_win32k+c8c3a

Followup: MachineOwner

I did some research on the first one but never found anything concrete. I don't know about the second report as it details something different.

I did have this once before but I updated the ATI drivers and it went away. Did not work this time.

Any help appreciated.