General Comments

[Dinesh]

Thank you for the detailed explanation.

 

[H2SO4]

Thank you for the detailed explanation.

Oh, that's OK. It didn't take long. I copied it from the tutorial over on vistax64.com and did a find/replace for the word "Vista"

EDIT: I'll aim to expand it a bit over time, especially if people are interested in specifics.

 

[zigzag3143]

H2SO4

thanks for a great intro to debugging

 

[Bare Foot Kid]

Hello H2SO4.


It would be best if the other posts were removed from this and the thread locked so that it won't get filled up with extraneous posts like this one, that way the info won't be hard to find in all the extra posts.

 

[Tews]

Why not just have John move it to the tutorial section ... Its that good!

 

[chuckr]

I copied it from the tutorial over on vistax64.com and did a find/replace for the word "Vista"

Which software ?

Missed one:

Even More Debugger Trickery For The Really InterestedMinidumps can also easily reveal basic information about the Windows version, service pack level, time of the crash, and system uptime:1: kd> vertarget
Windows Server 2008/Windows Vista Kernel Version 6001 (Service Pack 1) MP (4 procs) Free x64

 

[H2SO4]

I copied it from the tutorial over on vistax64.com and did a find/replace for the word "Vista"

Which software ?

Missed one:

Even More Debugger Trickery For The Really InterestedMinidumps can also easily reveal basic information about the Windows version, service pack level, time of the crash, and system uptime:1: kd> vertarget
Windows Server 2008/Windows Vista Kernel Version 6001 (Service Pack 1) MP (4 procs) Free x64

Yeah, I left that one on purpose - I didn't think it would detract from the validity of the example.

Also, it's considered extremely bad form to mess with debugger spew before presenting it as supposedly just-copied-and-pasted

 

[H2SO4]

It would be best if the other posts were removed from this and the thread locked so that it won't get filled up with extraneous posts like this one, that way the info won't be hard to find in all the extra posts.

Why not just have John move it to the tutorial section ... Its that good!

Thanks guys. I don't mind what the moderators and admins choose to do with it, though in some ways I'd rather keep it here rather than see it go to "tutorials". It may be more visible to those who come to this section because they've got a problem, rather than because they're looking for a tutorial on debugging.

As far as extraneous posts (like this one) and locking are concerned, I imagine that would have to be handled by a moderator? It would be nice if the thread could remain at least partially interactive, so that questions could be asked (and maybe even answered), and others may contribute. Perhaps the non-core posts could simply be culled every so often?

 

[chuckr]

Roger that!

Its just that being w7, noobs might have difficulty following,

and become confused with dinosaur terminology.

Nobody's gonna check 'symbol references',

APIs in .h, or anything like that...

 

[H2SO4]

Roger that!

Its just that being w7, noobs might have difficulty following,

and become confused with dinosaur terminology.

Nobody's gonna check 'symbol references',

APIs in .h, or anything like that...

I see your point. Done. I have angered the gods of debugging by editing that first post to show Win7 as the name of the OS being debugged.

To punish me, some 7th-Dan Pedant is now going to come out of the woodwork to point out that the information is inconsistent because the modules list doesn't match the preferred load addresses for Win 7

 

[Bare Foot Kid]

Good ideas mate, it would be more help here than buried in the tutorial section, it is that good though.


Thanks.

 

[HammerHead]

Debugger

Ok, I got it installed. For the symbol path I copied what you had in the tutorial.

c) Set the path to be the following:

SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols

The splats are included correct? Or do I need to remove them?

There must be more to setting this up. For instance source file path, Image file path, etc.

What I want to accomplish here is when my machine goes into S3 (unattended) it will on its own try to reboot. It then goes into a loop and windows cannot boot. When I set down to the monitor it is hung at "delete Hib file and reboot win" but it still cannnot boot (continues to loop) Then I have discovered that if I enter the bios and do an F10, ok, (make no changes) it will reboot into windows.
​

 

[H2SO4]

SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
The splats are included correct? Or do I need to remove them?

All of that is included, except the colouring

Literally, S...R...V... asterisk... C... colon... back_slash... SymCache... asterisk... H... T... T... P... colon... forward_slash... forward_slash...m... s... .... and so on.

There must be more to setting this up. For instance source file path, Image file path, etc.

Unless you work for MS, I presume you don't have access to Windows source code. Therefore, the source path is irrelevant. Image file path is only used for relatively advanced things - not what we're dealing with here.

What I want to accomplish here is when my machine goes into S3 (unattended) it will on its own try to reboot. It then goes into a loop and windows cannot boot. When I set down to the monitor it is hung at "delete Hib file and reboot win" but it still cannnot boot (continues to loop) Then I have discovered that if I enter the bios and do an F10, ok, (make no changes) it will reboot into windows.

The procedures I've described here are used for analysis of "minidumps", such as those created by Windows during BSODs. (They're stored in \Windows\minidump). I get the feeling that you're describing a reboot loop which happens without BSODs ("bugchecks" in official terminology). If that's the case, this stuff won't help you directly, mostly because there's no minidump for the debugger to analyse, and you may wish to start a thread describing the entire situation so that your issue gets wide attention.

 

[jcgriff2]

Professor H2SO4's Night Class

Hi H2SO4 . . .

Excellent !!

Glad to see you back.

JC
jcgriff2

`

​

 

[H2SO4]

Hi H2SO4 . . .

Excellent !!

Glad to see you back.

JC
jcgriff2

`

​

Thank you very much JC!

I certainly wouldn't want all BSODs to go away though - people like you and I enjoy the troubleshooting way too much

 

[shuster]

Hi H2SO4,
Thank goodness for high level compilers.

 

[H2SO4]

Hi H2SO4,
Thank goodness for high level compilers.

Intel and Microsoft have been called many things over the years. "Goodness" is probably a first

 

[InfalliblexOne]

I must say, excellent work with the post about registers! I had no idea what they meant before. I'll definitely be looking into reading that, right after I learn how to start WinDbg

Seriously, thanks for your time.

 

[H2SO4]

I must say, excellent work with the post about registers! I had no idea what they meant before. I'll definitely be looking into reading that, right after I learn how to start WinDbg

Seriously, thanks for your time.

Thank you InfalliblexOne. You come highly recommended by somebody we both know, and I look forward to your forum contributions

 

[torrentg]

Was reading this earlier today. I have a feeling what Windows does "behind the scenes" will become even more interesting to me once I start to understand it better.

H2SO4, are you self taught or do you have done formal studies?