Hello, Jonesey007,
there are commands "k", "kb" and etc in the windbg to view the stack of the current thread. It's important that only registers and stack trace are available in the minidump.
Main Topics
Browse All TopicsHi,
I have a mini dump and am trying to find out whats causing my BSOD
When i press 'u' i get unassembed code, if i press 'u' again the output changes and so on and so on
Can someone tell me what im doing, am i moving down some sort of stack?
Thanks
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Business Accounts
Answer for Membership
by: t0t0Posted on 2009-09-07 at 12:40:31ID: 25276941
You're unassembling code. Look at your pair of hex addresses, notice they get bigger everytime you press 'u'? That's because it's advancing further along in memory. The hex pairs are your memory address and offset address.
Normally, you start at ????.0100. On my machine it's 0F00.0100.
If you want debug to return to the start again, enter 'u 100'.
Check out debug's commands by entering just a question mark (?)....
Below: example output from debug. Notice how I return to the start by entering 'u 100'?
Select allOpen in new window