View Single Post
18 Apr 2010  
zigzag3143

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by Hollywood2 View Post
i hope this helps and thank you for the help, really thank you
dale

HW

this one was caused by your video driver ( nvlddmkm.sys). I would scrape this off and 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 [D:\Users\K\Desktop\041810-22464-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: F:\Symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`03054000 PsLoadedModuleList = 0xfffff800`03291e50
Debug session time: Sun Apr 18 13:45:52.426 2010 (GMT-4)
System Uptime: 0 days 0:00:37.705
Loading Kernel Symbols
...............................................................
................................................................
............
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff88030050464, 0, fffff880049bf686, 2}

Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys

Could not read faulting driver name
Probably caused by : nvlddmkm.sys ( nvlddmkm+172686 )

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

1: 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: fffff88030050464, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff880049bf686, 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 fffff800032fc0e0
 fffff88030050464 

FAULTING_IP: 
nvlddmkm+172686
fffff880`049bf686 8b0488          mov     eax,dword ptr [rax+rcx*4]

MM_INTERNAL_CODE:  2

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  csrss.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff88002e717d0 -- (.trap 0xfffff88002e717d0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff88010000000 rbx=0000000000000000 rcx=0000000008014119
rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880049bf686 rsp=fffff88002e71960 rbp=fffffa80051531b0
 r8=0000000000005c00  r9=0000000020050464 r10=fffffa80051531b0
r11=fffffa8002f11010 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
nvlddmkm+0x172686:
fffff880`049bf686 8b0488          mov     eax,dword ptr [rax+rcx*4] ds:0001:fffff880`30050464=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80003143832 to fffff800030c4600

STACK_TEXT:  
fffff880`02e71668 fffff800`03143832 : 00000000`00000050 fffff880`30050464 00000000`00000000 fffff880`02e717d0 : nt!KeBugCheckEx
fffff880`02e71670 fffff800`030c26ee : 00000000`00000000 fffffa80`051531b0 00000000`00000000 fffff800`03253888 : nt! ?? ::FNODOBFM::`string'+0x40f00
fffff880`02e717d0 fffff880`049bf686 : 00000000`00000000 fffff880`049eae70 fffffa80`018ecb00 fffffa80`02e96560 : nt!KiPageFault+0x16e
fffff880`02e71960 00000000`00000000 : fffff880`049eae70 fffffa80`018ecb00 fffffa80`02e96560 fffffa80`018ecb00 : nvlddmkm+0x172686


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nvlddmkm+172686
fffff880`049bf686 8b0488          mov     eax,dword ptr [rax+rcx*4]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nvlddmkm+172686

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  49b1201f

FAILURE_BUCKET_ID:  X64_0x50_nvlddmkm+172686

BUCKET_ID:  X64_0x50_nvlddmkm+172686

Followup: MachineOwner
---------
My System SpecsSystem Spec