Windows Error Reporting?
wtf is Windows Error Reporting? Oh yes, that annoying dialog that comes up whenever an app crashed. The one with the "Don't Send" button that I always click. Well, that'll be a reliable source of statistics, then
Microsoft on Thursday rolled out a stop crashing so goddamn much "reliability" update for Internet Explorer 8 users running the Windows 7 Beta. The patch plugs a variety of ills on the browser, including crashes, hangs, and memory leaks according to Microsoft. Windows 7 Beta users can snag the software via Windows update. …
Surely this is the point of a beta? When it breaks, let the manufacturer know? I broke IE8 on W7 on the first day of use and sent the report in so that when the time comes that I am forced to support it hopefully the issue I found will be fixed.
When there is an issue with a production OS or software why do people not send the error reports either? It could be a simple fix for the developers who are only human after all.
For the record, this post was written on FF3 running on Fedora9 - no windows fan boy here, just someone who wants IT to work.
yes but then you sit there saying that Redmond are rubbish and there software crashes all the time.
Maybe, just maybe, if people sent of the info, they could fix the issues.
You are a IT departments worst f**king nightmare. the sort of person that says.
"Well it's been playing up for months coming up with some error message 5 times a day and now it's totally dead. I need it fixed urgently because (insert bosses name) needs me to get (insert item) to him by end of today, or I get sacked.
<BOFH> Woohaw haa ha haaaaaa
"Instruction at x09ae45f70 attempted to address memory at x7ef32a996 and will be terminated. OK"
They can dress windows 7 up in all sorts of goppy plastic graphics, but underneath it all, it's still the same drab old world, where users press grey paving slabs with "OK" written on them... even when it's really NOT okay. You can argue all you want about it being beta software, but users (even, or, perhaps especially, beta users) should never have to look at error messages that amount to little more than debug output containing hexadecimal numbers.
The thing is, we all know that this software will eventually go to market in state where it is still outputing stack dumps, at its users... and users will still be asked to send the raw output back to some bit-bucket at redmond... and the bit bucket will daily fill up, and there will never be enough engineers to look at them all, and work out what the hell went wrong. And the problem will remain what the problem always was: the error message tells you exactly what just happened, while conveying no useful informatioon whatsoever. They might as well say things like "Fandango on stack" or "Warning: mallocs. Rlwrwlrlwrlwrlw!".
sending Windows error reports at every opportunity. Have another one ya bastads. For a moment, I get a little vision of just how many of these make their way to Microsoft every second of every minute of every hour of every day. Little chickens coming home to roost. And I wonder what they do with them. Read them, investigate them, count them, ignore them? Online crash analysis is really wonderful though, sorts me out every time. This problem seems to have been caused by an operating system made by Microsoft.... Please contact them for more information on how to resolve it...I laugh, ha ha ha ha. And reboot
Win 7 has been very, very good in general compared to the Vista that came pre-installed on this laptop. In particular network performance has been improved beyond recognition. I have to have a couple of windows machines here and after the usual "crud removal" process you always have to go through on a new windows box, this is pretty much the best performing of the lot. A few issues with mysterious hanging file handles and file permissions, especially in the installer and visual studio, but nary a blue screen and otherwise acceptable.
Yet again, it is MS code causing crashes, it is Adobe. Seriously, all the outsourced programmers at Adobe couldn't program their way out of a wet paper bag, or indeed a C:\ prompt.
Simple fix - remove Flash, problems go away, THEREFORE problem is with FLASH, not IE8.
Biting the hand that feeds IT © 1998–2020