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: WinDBG symbols

18 Aug 2015   #11
z3r010

 

Post a link to one of these dumps you are getting the error on so I can make sure they open fine for me.
My System SpecsSystem Spec
18 Aug 2015   #12
Laith

Windows 10 Professional x64
 
 

Okay, there are many but i'll send one of them. This dump is made in 7-zip if you have trouble extracting the archive, i moved over to 7-zip from WinRAR when i installed Windows 10 because i was getting sick of seeing that i need to activate and stuff.


Attached Files
File Type: zip 081715-7082-01.zip (32.7 KB, 27 views)
My System SpecsSystem Spec
18 Aug 2015   #13
z3r010

 

That doesn't work for me either, but I've not had an issue opening any on the forums
My System SpecsSystem Spec
.

18 Aug 2015   #14
Laith

Windows 10 Professional x64
 
 

It all started when i upgraded to Windows 10, i should have stayed at Windows 7...
My System SpecsSystem Spec
18 Aug 2015   #15
Anak

Microsoft Community Contributor Award Recipient

Win 7 Home Premium 64bit Ver 6.1.7600 Build 7601 - SP1
 
 

Hi Laith,

Has this been happening on all of the .dmp's you've tried to open since your "upgrade" or is it just certain ones like your example?

I'm thinking in the same vein as John, and if you can open "other .dmp's" I wouldn't be so quick to blame it on win10:
Quote   Quote: Originally Posted by z3r010 View Post
That doesn't work for me either, but I've not had an issue opening any on the forums
When I open your example I get:
Code:
*************************************************************************
***                                                                   ***
***                                                                   ***
***    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                                     ***
***                                                                   ***
*************************************************************************
, but all the others open normally.


The clue here is the .pdb files, .pdb files are created when a developer writes his or her own code for a program and if you don't have access to that code; You are up a creek without the proverbial paddle.

Quote:
The most important thing all developers need to know: PDB files are as important as source code! Yes, thatís red and bold on purpose. Iíve been to countless companies to help them debug those bugs costing hundreds of thousands of dollars and nobody can find the PDB files for the build running on a production server. Without the matching PDB files you just made your debugging challenge nearly impossible. With a huge amount of effort, my fellow Wintellectuals and I can find the problems without the right PDB files, but it will save you a lot of money if you have the right PDB files in the first place.

Source: PDB Files: What Every Developer Must Know
My interpretation of your and Hacb's problem is the both of you are trying to help members that have installed open source/freelanced, call it what you want programs that are causing the BSOD's and I would guide these members to uninstall, particularly, any recent programs that have been developed by lesser known entities.
My System SpecsSystem Spec
18 Aug 2015   #16
Hacb

Windows 7 Enterprise x64
 
 

yep, that mesage looks like what i'm seeing sometimes.
My System SpecsSystem Spec
18 Aug 2015   #17
derekimo

Microsoft Community Contributor Award Recipient

 
 

I've gotten that a couple times recently, over at TF and here.

Googling these,

Code:
nt!_MMPTE
Code:
nt!_KPRCB
Will get a lot of similar results, like this,

Solved Unable to make WinDBG analyze the Dump files
My System SpecsSystem Spec
19 Aug 2015   #18
Anak

Microsoft Community Contributor Award Recipient

Win 7 Home Premium 64bit Ver 6.1.7600 Build 7601 - SP1
 
 

Good ol' Mr. Cranky Pants! That's the tack I saw:
Quote:
IMO - start by assuming it's a 3rd party driver (non-Windows)
Once you rule that out, then start in on hardware problems/diagnostics
The last thing to check (assuming Windows is fully updated) is Windows.
But I am going to have to rethink this.

From Derek's link and searching myself, not only on the web but into my own HDD I found that I do have pdb files at C:\symbols, but are they the right ones to decipher Laith's sample file?

I tested using various cmds in the debugger cmd line that I found in the kernel_debugging_tutorial.doc (copy that .doc name into your search box) that accompanies the debugger when you install it, with no luck.

I did some testing in the symbols folder following this: Windbg Symbols for ntoskrnl.exe even creating a ntoskml.pdb folder and coping files to it:
Quote:
to fix this, you need to go into
the SYMBOLS\EXE folder and copy file 'ntkrnlmp.pdb'
to 'ntoskrnl.pdb'.
with no success.

I'm going to do more reading and testing and see if I can come up with an answer. Like why don't I have ntoskml.pdb to begin with?
My System SpecsSystem Spec
19 Aug 2015   #19
Laith

Windows 10 Professional x64
 
 

Exactly, why don't we have one?

On Windows 7 WinDBG worked like a charm with no errors, but with upgrading it gave me errors and all kinds o' stuff.
My System SpecsSystem Spec
21 Aug 2015   #20
derekimo

Microsoft Community Contributor Award Recipient

 
 

Quote   Quote: Originally Posted by Laith View Post
On Windows 7 WinDBG worked like a charm with no errors, but with upgrading it gave me errors and all kinds o' stuff.
It had nothing to do with windows 10, we have three different OS's all getting the same thing.

This is still happening in quite a few dumps, I'm starting to think some update has altered something.

WinDBG symbols-2015-08-20_22h56_15.png

As soon as Microsoft gets enough complaints about this they will probably fix it.


My System SpecsSystem Spec
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search


Similar help and support threads
Thread Forum
Formatting symbols
I just dislike editing another authors word document. Unknown formatting is such a problem, furthermore the symbols displayed have little meaning to me. Is there a document showing all formatting symbols and what they mean? One that is bothering me currently, is scattered thru out the document...
Microsoft Office
How to create symbols
Use your keyboard - no program to download. List of codes: Alt Codes (symbols and character computer keyboard codes)
Customization
Subtitle symbols
hello forum,i will be quick...im trying one week now to understand why my subtitles (.srt and every sub on greek language) seems like Symbols.....i use VLC and i fix the symbol showing icons into greek language...but still if i open the sub with notepad or whatever prog they are again...
Music, Pictures & Video
bsod need correct symbols
I have got multiple bsod and mini dumps, using windbg but gives incorrect symbols message, I have installed both 64 bit and 32 bit . get same.
BSOD Help and Support
Appropriate symbols for debugging 7137
Sorry i seem to be posting a few questions i hope its not too annoying and i hope it benefits others as well im trying to sort a crash problem i have with debugging tools but i cant seem to find the right symbols if anyone was curious a guide for how to use the tools can be found here BSOD ~...
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 23:17.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App