Tech Support Forum banner
Not open for further replies.
1 - 6 of 6 Posts

· Enthusiast
2,875 Posts
Discussion Starter · #1 ·
I have been reading this forum for a while but this is my first post.
I have a decent amount of knowledge and see that many of the responses here deal with mini dump diagnosis.
I am looking to be able to read the dumps and hope that you can help with a clarification that I need.

On this page I see this description
"When to Use 32-bit Debugging Tools
The 32-bit version of Debugging Tools for Windows is the best choice, unless you are debugging an application on a 64-bit processor. In that case, you should use a 64-bit package."

I am fairly sure of the answer but I just want to be certain.
I have XP and Vista both 32 bit.
AMD 5600X2 2.8G dual core @3.2G
Now I know that it is 64 bit processor, but as per the above sentence I had to stop and question. Which Version?

· Enthusiast
2,875 Posts
Discussion Starter · #3 ·
That is what I thought but the wording of the sentence seemd odd.

I have a pretty good knowledge of computers, operations and stop: errors in genaral.
Im trying to take it to the next level and this seems to be some thing that would be helpful to know about.
Is there anything else that you or anyone else could say to help me to learn this ability.

Possibly any mistakes not to make other than the obvious dont make changes that Im not sure about.

Please remember I am trying to learn, not brick my computer so be kind.

· Banned
3,574 Posts
Think of it this way -

When you open a 32-bit .exe on your 64-bit processor/OS, it says "not a valid 64-bit string" or something of that sort, I forget at the moment. The same goes vice-versa.

If that's the case, you have to run A 32-bit debugger on your 32-bit OS since OS takes the priority away from the processor.

Now, I may be wrong, but if any can prove me wrong, go ahead I'd actually like to know the answer to this. Thanks.

· Administrator, Manager, Microsoft Support, MVP
34,634 Posts
Hi -

Install the x86 dbugger -

That comes from this MS WHDC site -

No need to d/l any symbol packages.
Go to \program files\debugging tools for windows\windbg.exe
Right-click on it, select Run as Admin
Paste this in for symbol path -
Download a minidump - there are 1000's of them in this Vista Forum alone
CTRL-D - select dump
When the screen scrolling stops, paste this into kd> command line -
!analyze -v;r;kv;lmtn
You must have active Internet connection - symbols will d/l to c:\symbols as they are needed. The windbg app must run at elevated admin level or it will encounter permission settings issues with symbol directory.

Any other questions - just ask.

Sorry, but I have to go - am in CA on business; be back later.

Regards. . .



· Enthusiast
2,875 Posts
Discussion Starter · #6 · (Edited)
Ok guys great.
It is the way I thought 32 for 32 os etc.
Its just the way the sentence reads, it contradicts itself.
Thanks for the answers.

As for the second half of my post.
Is there anywhere you may be able to point me towards in as far as link or a lesson to help to read some of the finer details contained in the logs.

The main reason I am trying to learn, mainly out of curiosity, while trying to overclock I
encounterd various BSOD errors when I reached a certain limit.
Im not asking for OC help.
I am just interested in if it boils down to the same reasons.

Yeah I know that sounds dumb.

Ill give this a try and see what happens

Thank You
1 - 6 of 6 Posts
Not open for further replies.