how do i open dmp file

firestrike · 30 Mar 2006 at 19:33

right ive got a number of mini dump files i could do with having a look at just wondering how i could have a look at them.thanks for any help u can give

G-MAN2004 · 30 Mar 2006 at 19:38

Don't know if this will help.

NathanE · 30 Mar 2006 at 19:47

firestrike said:
right ive got a number of mini dump files i could do with having a look at just wondering how i could have a look at them.thanks for any help u can give

You need a debugger. Just e-mail them to me as before and I'll post the results here

firestrike · 30 Mar 2006 at 21:04

ok just sent you a couple. hope fully one should be different form last time. thanks fot the help it is much appreciated.

NathanE · 30 Mar 2006 at 21:09

Yep you're right. Two were the same as before, however the third was this:

Code:

kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 9d086240, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 8051ec1c, address which referenced memory

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


READ_ADDRESS:  9d086240 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!MiDeletePte+198
8051ec1c 8b420c           mov     eax,[edx+0xc]

CUSTOMER_CRASH_COUNT:  2

DEFAULT_BUCKET_ID:  DRIVER_FAULT

BUGCHECK_STR:  0xA

LAST_CONTROL_TRANSFER:  from 8051f090 to 8051ec1c

STACK_TEXT:  
f6ceabc4 8051f090 c007fb08 0ff61000 00000000 nt!MiDeletePte+0x198
f6ceac88 80516641 00000008 0ff6efff 00000000 nt!MiDeleteVirtualAddresses+0x164
f6ceaca4 805a72ec 0ff60000 0ff6efff f6cead64 nt!MiDeleteFreeVm+0x1d
f6cead4c 8053c808 ffffffff 00124bf0 00124bf4 nt!NtFreeVirtualMemory+0x42e
f6cead4c 7c90eb94 ffffffff 00124bf0 00124bf4 nt!KiFastCallEntry+0xf8
WARNING: Frame IP not in any known module. Following frames may be wrong.
00124bc0 00000000 00000000 00000000 00000000 0x7c90eb94


FOLLOWUP_IP: 
nt!MiDeletePte+198
8051ec1c 8b420c           mov     eax,[edx+0xc]

SYMBOL_STACK_INDEX:  0

FOLLOWUP_NAME:  MachineOwner

SYMBOL_NAME:  nt!MiDeletePte+198

MODULE_NAME:  nt

DEBUG_FLR_IMAGE_TIMESTAMP:  42250a1d

STACK_COMMAND:  kb

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  0xA_nt!MiDeletePte+198

BUCKET_ID:  0xA_nt!MiDeletePte+198

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

Now although this points to "memory_corruption", it doesn't necessarily mean anything is wrong with your memory sticks (although it could be

). IRQL_NOT_LESS_OR_EQUAL is a very common bug in device drivers and 95% of the time it does not point to memory corruption.

I still firmly lay the blame at your Nvidia drivers.

firestrike · 30 Mar 2006 at 21:34

mmm it does seem to be driver orientated. 1 was using omega drivers when that occured. unfortunatly ive now tryed abou 8 differnt drivers and all seem to have pritty much the same problem :rolleyes:

im startin to think ill never solve this

will never buy nvidia again