Marcel Bruch had a great idea: A wiki for stack traces.
If you get a stack trace in your IDE, you click on it and pages from this wiki are offered (or a new page is created).
On the wiki pages, solutions for the problem could be posted.
So what we would need is a API to turn stack traces into "questions", upload them and SO would return a list of relevant links that the IDE could display. For browser users, there would be a text area where visitors can paste stack traces.
Would it be possible to create something like this on SO?
[EDIT] I feel that downvoters haven't even started to understand what this question is about. So some explanations:
What's a beginner? A beginner is someone who doesn't even know where to begin.
So the beginner has an error on his computer. What should he do? What can he do? He doesn't even understand half of the words on the screen. He can't tell which information we would need to help.
Furthermore, if you look at the questions, they are always the same. Theoretically, there is an infinite numbers of paths through a program but in reality, only a small number is executed. Beginners are humans. All human brains are similar. So the errors are similar. There might be 100 of them but not millions.
If beginners had a tool that would a) collect all useful information, b) submit that automatically to a search engine, and c) display similar problems, this would reduce a lot of confused questions on SO (and comments like "please provide additional information").
Now, a couple of people will argue "they should search" but that's the key problem: They don't know what's wrong. If you google for the error message, that might return something useful but not always. Try to google for "java.lang.NullPointerException: null".
For an expert, it's obvious how to solve this but a beginner (by definition) doesn't even know what a null pointer is.
Again, there are billions of places in a program where the code can throw NPEs but 99% of the places never do. And the small rest always throws it for the same reason (missing parameter on the command line, broken config file, broken database).
So my suggestion is to extend SO with a stacktrace wiki/search engine which allows to aggregate, search and quantify automatic error reports.
Tooling should include things like: Submit a stack trace (incl. program name, programming language and possibly class path) automatically, find similar reports, post answers/comments to those stack traces and merge them.
From my limited point of view, we already have almost everything at SO except for the stack trace search engine.