BSOD - ntkrnlmp.exe

Associate
Joined
18 Jun 2009
Posts
19
Hi all

I have been enjoying my rig since I built it in the summer but lately I have been getting the dreaded BSOD. I was playing Arma 2 today and it occurred the 4 times I played the game, about 15 mins in. I had received one a couple months ago, updated the ATI driver and it disappeared. That did not work this time.

SYSTEM:

http://forums.overclockers.co.uk/showthread.php?p=14374946#post14374946

OS:

Windows 7 Home Premium



I debugged the latest mini dump file and got this:

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) 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
---------

It says:

Probably caused by : ntkrnlmp.exe


Also, the BCCode was 50.

I Googled and saw conflicting reports. One said to update drivers, others say it is a sign of a hardware issue.

I was wondering if anyone could shed some light on this.
 
Back
Top Bottom