Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Reading a dump file

09 Mar 2010   #1
SMOKKINU

Windows 7 Ultimate 64bit
 
 
Reading a dump file

can anyone translate this for me?

Code:
 
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
 
 
Loading Dump File [C:\Users\Michae\Desktop\030910-26609-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
 
Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is: 
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
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`02c61000 PsLoadedModuleList = 0xfffff800`02e9ee50
Debug session time: Tue Mar 9 09:59:48.703 2010 (GMT-5)
System Uptime: 0 days 0:00:15.000
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
.............................................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
 
Use !analyze -v to get detailed debugging information.
 
BugCheck D1, {fffff88015c00000, e, 0, fffff8800ffb622e}
 
*** WARNING: Unable to verify timestamp for mssmbios.sys
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
 
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
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
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Probably caused by : nvlddmkm.sys ( nvlddmkm+18c22e )
 
Followup: MachineOwner
---------



My System SpecsSystem Spec
.

09 Mar 2010   #2
Tews

64-bit Windows 8.1 Pro
 
 

zip the file up first then attach it to your next post
My System SpecsSystem Spec
09 Mar 2010   #3
SMOKKINU

Windows 7 Ultimate 64bit
 
 

Quote   Quote: Originally Posted by Tews View Post
zip the file up first then attach it to your next post

done
My System SpecsSystem Spec
.


09 Mar 2010   #4
SMOKKINU

Windows 7 Ultimate 64bit
 
 

here
My System SpecsSystem Spec
09 Mar 2010   #5
SMOKKINU

Windows 7 Ultimate 64bit
 
 

Is this related to video cards?
My System SpecsSystem Spec
09 Mar 2010   #6
SMOKKINU

Windows 7 Ultimate 64bit
 
 

anyone?
My System SpecsSystem Spec
Reply

 Reading a dump file




Thread Tools





Similar help and support threads
Thread Forum
reading dump files
When reading dump files; what is the easiest way to figure out the culprit in terms of what everything in a dump file is pointing to as the reason for the dump file happening? Is it whatever the string is pointing to is the culprit or something similar? I am not a expert in reading dump files;...
BSOD Help and Support
RANDOM BSOD HELP ASAP someone with reading dump file knowledge
hey im getting this more and more often and i really need some help reading it pleased someone who is experience try to respond ASAP before my computer completely fails
BSOD Help and Support
help reading dump files
Hi all, my friends comp keeps bsoding and i was able to get him to send me the dump files (7 of them) through email. Now my problem is that i cant open it. I tried installing windows sdk on my comp to read it but it keeps failing the install. So i was wondering if i place those dump files on to my...
BSOD Help and Support
Help reading dump file
My computer crashed overnight and I have a dmp file. I cannot read it -- and I am not PC savvy enough to work it out with the SDK program, although I did try. The file is attached, zipped. Thank you for any insights!
BSOD Help and Support
Help reading memory dump
After upgrading a couple of my friends to i5 systems, the upgrade but hit me as well. However I am damn near regretting it as the new build has given me nothing but headaches for the past week. The system specs are: Intel i5-750 CPU with retail HSF Gigabyte GA-P55M-UD2 motherboard 2x2 Gigs...
BSOD Help and Support
problem reading mini dump file
I am trying to debug a minidump on Windows 7 x64 7229 but I am having a problem with the Symbols. I have downloaded and installed: Debugging Tools for Windows - Native x64 (version 6.11.1.404) Windows 7 x64 symbols
BSOD Help and Support

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 06:59.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App