Hi guy,
I got the BSOD when playing BFBC2.
I need someone with the knowledge to anaysis this file for me and let me know if it's the system ram or the video ram that is being dumped.
RapidShare: 1-CLICK Web hosting - Easy Filehosting
Thanks in advance and really apperciated your helps!
This crash was caused by your atipmdag.sys part of your video driver. You should un install all traces of your current driver and download an install a fresh copy
Let us know if you need help
Ken
Code:Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\K\Desktop\030810-12511-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*d:\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7600 MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Machine Name: Kernel base = 0xfffff800`02c0d000 PsLoadedModuleList = 0xfffff800`02e4ae50 Debug session time: Mon Mar 8 22:39:49.301 2010 (GMT-5) System Uptime: 0 days 0:44:44.581 Loading Kernel Symbols ............................................................... ................................................................ ..................... Loading User Symbols Loading unloaded module list .... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 50, {fffff8e009e84d88, 0, fffff88004da7c66, 5} Unable to load image \SystemRoot\system32\DRIVERS\atipmdag.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for atipmdag.sys *** ERROR: Module load completed but symbols could not be loaded for atipmdag.sys Could not read faulting driver name Probably caused by : atipmdag.sys ( atipmdag+2b3c66 ) Followup: MachineOwner --------- 2: 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: fffff8e009e84d88, memory referenced. Arg2: 0000000000000000, value 0 = read operation, 1 = write operation. Arg3: fffff88004da7c66, If non-zero, the instruction address which referenced the bad memory address. Arg4: 0000000000000005, (reserved) Debugging Details: ------------------ Could not read faulting driver name READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002eb50e0 fffff8e009e84d88 FAULTING_IP: atipmdag+2b3c66 fffff880`04da7c66 817a083100bebe cmp dword ptr [rdx+8],0BEBE0031h MM_INTERNAL_CODE: 5 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x50 PROCESS_NAME: System CURRENT_IRQL: 0 TRAP_FRAME: fffff880075d7490 -- (.trap 0xfffff880075d7490) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000f1cc40000 rbx=0000000000000000 rcx=0000000000000000 rdx=fffff8e009e84d80 rsi=0000000000000000 rdi=0000000000000000 rip=fffff88004da7c66 rsp=fffff880075d7620 rbp=fffffa8007b2df20 r8=0000000000000002 r9=0000000000000002 r10=0000000000000002 r11=fffff880075d77d0 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl zr na po nc atipmdag+0x2b3c66: fffff880`04da7c66 817a083100bebe cmp dword ptr [rdx+8],0BEBE0031h ds:fffff8e0`09e84d88=???????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff80002cfcb91 to fffff80002c7ef00 STACK_TEXT: fffff880`075d7328 fffff800`02cfcb91 : 00000000`00000050 fffff8e0`09e84d88 00000000`00000000 fffff880`075d7490 : nt!KeBugCheckEx fffff880`075d7330 fffff800`02c7cfee : 00000000`00000000 00000000`00000001 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x40f5b fffff880`075d7490 fffff880`04da7c66 : 00000000`00000000 fffff880`0b8d7f00 0000000f`1c588000 00000001`00000002 : nt!KiPageFault+0x16e fffff880`075d7620 00000000`00000000 : fffff880`0b8d7f00 0000000f`1c588000 00000001`00000002 fffff880`075d7830 : atipmdag+0x2b3c66 STACK_COMMAND: kb FOLLOWUP_IP: atipmdag+2b3c66 fffff880`04da7c66 817a083100bebe cmp dword ptr [rdx+8],0BEBE0031h SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: atipmdag+2b3c66 FOLLOWUP_NAME: MachineOwner MODULE_NAME: atipmdag IMAGE_NAME: atipmdag.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4b68f9c4 FAILURE_BUCKET_ID: X64_0x50_atipmdag+2b3c66 BUCKET_ID: X64_0x50_atipmdag+2b3c66 Followup: MachineOwner ---------
Quote