I wanna learn...

How to open minidump files and read them, anyone willing to help me???

Crash and lockup debug 'How To' - Windows 7 Forums

sotorious said:

How to open minidump files and read them, anyone willing to help me???

Sure

Pm Me


ken J+

when i tryed installing the program i got this

testing

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

PROCESS_NAME: wmplayer.exe

Nvidia driver problem and something about wmplayer.

That's a memory management error.

Either it's your antivirus or you should have brought the pc to a shop like I said about a month ago for them to set up the pc and/or do testing for faulty hardware.

In any case, I'd update this asap and also uninstall av:

Code:

ASACPI   ASACPI.sys   Sun Mar 27 22:30:36 2005

Also, visit Marvell.com or here to get the latest networking driver because what you have is old.

Code:

yk62x64  yk62x64.sys  Mon Feb 23 10:02:27 2009

i was doing a test on something, what caused the bluescreen really was a ram stick, i just happened to be opening windows media player at the time. Yea i also havent gotten around to updated the Ethernet driver.

sotorious said:

testing

OK. Blue screen view, and to some extent Windbg say it was probably caused by ntkrnlmp.exe. It also shows that WMP was in memory at the time.

The two drivers below are ancient and need to be updated.


ASACPI.sys fffff880`04431000 fffff880`04439000 0x00008000 0x42476c4c 3/27/2005 9:30:36 PM
secdrv.SYS fffff880`05d65000 fffff880`05d70000 0x0000b000 0x4508052e 9/13/2006 8:18:38 AM


PUT code tags here

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\120609-16504-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 (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255----here AMD 64bit
Machine Name:
Kernel base = 0xfffff800`02c4d000 PsLoadedModuleList = 0xfffff800`02e8ae50
Debug session time: Sun Dec  6 03:25:22.492 2009 (GMT-5)
System Uptime: 0 days 0:01:50.709---------Uptime
Loading Kernel Symbols
...............................................................
................................................................
............
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41790, fffffa8000eb0ec0, ffff, 0}

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

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

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

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041790, The subtype of the bugcheck.
Arg2: fffffa8000eb0ec0
Arg3: 000000000000ffff
Arg4: 0000000000000000

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


BUGCHECK_STR:  0x1a_41790

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  wmplayer.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002d3126e to fffff80002cbef00

STACK_TEXT:  
fffff880`03910968 fffff800`02d3126e : 00000000`0000001a 00000000`00041790 fffffa80`00eb0ec0 00000000`0000ffff : nt!KeBugCheckEx
fffff880`03910970 fffff800`02d00c4a : 00000000`00000000 00000000`0614dfff fffffa80`00000000 fffffa80`03bd6b30 : nt! ?? ::FNODOBFM::`string'+0x339d6
fffff880`03910b30 fffff800`02cbe153 : ffffffff`ffffffff 00000000`0530e3f0 00000000`0530e3e8 fffffa80`00008000 : nt!NtFreeVirtualMemory+0x5ca
fffff880`03910c20 00000000`7789009a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0530e3b8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7789009a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+339d6
fffff800`02d3126e cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+339d6

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc600

FAILURE_BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+339d6

BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+339d6

code tags

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

The secdrv.sys is alright and latest. It's not a problem-causer.