"Failed to start stack walk: 80004005", "Following frames may be wrong" and other errors you may see in windbg

re: "Failed to start stack walk: 80004005", "Following frames may be wrong" and other errors you may see in windbg

Madhur — Tue, 13 May 2008 20:16:33 GMT

Thanks, that was helpful information....

re: "Failed to start stack walk: 80004005", "Following frames may be wrong" and other errors you may see in windbg

Narasimha Vedala — Fri, 23 May 2008 17:17:59 GMT

Dear Tess,

Please could you reduce the width of lines in your posts? It is difficult to skim your posts in RSSBandit because of that short horizontal bar taking a mile or so :( I cannot simply roll my mouse down to skim.

http://blogs.msdn.com/tess/rss.xml is too wide to fit in the normal outlook standard-width reading pane.

Cheers.

re: "Failed to start stack walk: 80004005", "Following frames may be wrong" and other errors you may see in windbg

Tess — Fri, 23 May 2008 17:29:01 GMT

I will do my best... is it the debug output or everything? Does the text not wrap?

re: "Failed to start stack walk: 80004005", "Following frames may be wrong" and other errors you may see in windbg

Narasimha Vedala — Mon, 26 May 2008 12:14:54 GMT

everything. the text too doesn't wrap.

re: "Failed to start stack walk: 80004005", "Following frames may be wrong" and other errors you may see in windbg

Tess — Mon, 26 May 2008 12:44:19 GMT

Hi Narasimha,

I just downloaded RSS Bandit and subscribed to my feed.

In my copy of RSS bandit it seems to be word wrapping properly. I have resized the viewer and the word wrap seems to follow, so I am not sure what the difference is there. I tried it on 3 different machines here and got the same results. Are you just seeing this issue with my feed?

I have compared HTML with other blogs and they don't seem to put extra at the end of lines which is what i would have to do to manually word wrap. I would prefer not to do so as it will make things look weird in other readers.

re: "Failed to start stack walk: 80004005", "Following frames may be wrong" and other errors you may see in windbg

Narasimha Vedala — Mon, 26 May 2008 16:21:08 GMT

Tess,

In RSS bandit, I've configured it to show list of your posts on top and view on bottom. I hope you have similar way.

If I see individual post of yours it is ok. What I'm talking about is seeing list of posts' view. Click on the link in "My Feeds" on the left pane. Right side top view shows list of all your posts. Bottom view shows these posts which I can scroll down one by one. In this view is what I face this problem. Btw, other authors on MSDN seems ok. Though some of them have horz. bar.

For best result benchmark see Vista Team blog: http://windowsvistablog.com/blogs/default.aspx

Their posts appear nicely wrapped.

re: "Failed to start stack walk: 80004005", "Following frames may be wrong" and other errors you may see in windbg

narasimha vedala — Mon, 26 May 2008 16:25:07 GMT

hey Tess, also see Roberto Farah's http://blogs.msdn.com/debuggingtoolbox/default.aspx

they too appear without horz. bar. :) Btw, in this view RSSBandit only shows those posts which are still unread.

re: "Failed to start stack walk: 80004005", "Following frames may be wrong" and other errors you may see in windbg

Narasimha Vedala — Mon, 26 May 2008 16:49:48 GMT

I did some comparison with other authors: I think they explicitly enter a new line (\r\n) in the html code wrapped in , while your text is one single long line inside

re: "Failed to start stack walk: 80004005", "Following frames may be wrong" and other errors you may see in windbg

Tess — Mon, 26 May 2008 21:07:16 GMT

I had a look at home with some different feeds in RSSBandit and it looks like half of them have one behavior and half have the other behavior.

When I view mine it doesnt word wrap if I resize the window to be smaller than the screen width, if i maximize it it works fine. So it seems like some feeds just have a smaller width than others and I can't say why that is, but im guessing it has something to do with the theme used.

Based on the feeds that have wordwrap even when resized I can say that the source reveals that they do not do anything special as far as breaking lines etc. so I am not really sure what to do to make it show up properly in RSS bandit when resized. I'm sorry:(

re: "Failed to start stack walk: 80004005", "Following frames may be wrong" and other errors you may see in windbg

Narasimha Vedala — Tue, 27 May 2008 06:41:55 GMT

Hi Tess,

taking your cue, I changed my xsl format to "kuro5hin" template for your posts and voila! your text fits. :)

Thanks anyway. Cheers.

re: "Failed to start stack walk: 80004005", "Following frames may be wrong" and other errors you may see in windbg

Tess — Tue, 27 May 2008 14:37:12 GMT

awesome, thanks for the tip. I'll add that too to my RSS Bandit.

I use on-line RSS readers because I want it to be portable so i can keep read/unread posts anywhere i go, but after seeing this reader I am almost thinking about converting.

re: "Failed to start stack walk: 80004005", "Following frames may be wrong" and other errors you may see in windbg

narasimha vedala — Tue, 27 May 2008 17:06:47 GMT

Tess, it is my due to give you a big thanks for this very useful blog. I learned a lot from here.

Allow me to buy you cup of coffee, 'heap' of chips and a sandwich with few megabytes of free stack trace, thinly cut ham and topped with mayonnaise SOS.

re: "Failed to start stack walk: 80004005", "Following frames may be wrong" and other errors you may see in windbg

Tess — Wed, 28 May 2008 09:24:27 GMT

:) funny, thanks Narashima

“Failed to load data access DLL, 0x80004005” – OR – What is mscordacwks.dll?

Notes from a dark corner — Wed, 18 Feb 2009 20:34:42 GMT

Ever seen this error in a WinDBG/CDB debug session? Failed to load data access DLL, 0x80004005 Verify

re: "Failed to start stack walk: 80004005", "Following frames may be wrong" and other errors you may see in windbg

Thomas — Wed, 04 Nov 2009 16:22:27 GMT

Thanks Tess for all your posts.

Failed to load data access DLL, 0x80004005

This can also happen in !VerifyHeap.

My solution:

1. unload SOS (.unload SOS), because wrong version is loaded

2. load modules (ld *)

3. load SOS (.loadby sos mscorwks), should load the correct version now

4. !VerifyHeap