Problem connecting to the Windows Error Reporting service

Seems this "glitch" still hasn't been fixed. Why not just say which errors have been uploaded and those that haven't been give the reason why not.

In another thread I started which discusses this I root caused the issue using Fiddler to monitor network traffic.

http://answers.microsoft.com/en-us/windows/forum/windows_7-performance/problem-connecting-to-the-windows-error-reporting/7dd569d0-e4fa-4ae1-ba7b-99ecfdfd3ee1?page=2

When an error is trying to upload a memory dump it uses an encrypted SSLv3 network connection to oca.microsoft.com.  The connection fails.  Other problems that don't need to upload files use an unencrypted connection and those problems get reported.  SSLv3 works fine on my computer for mail.live.com so it just seems to be with oca.microsoft.com.  You can go to the link to see all the details.

So, even with free beta testers that root cause the problem for them it is not fixed.  I believe it is what I suggested in the other thread -- it is too far down the list of things to fix for it to ever be worked on.  I don't care if it is fixed anymore; >99% of the time it just tells you that no solution is found.  Of the few times it has told me a solution it was either wrong (telling me to fix a driver for another piece of hardware with a similar driver name) or told me something simple like update Flash player.

Actually, the BSOD in the chess game right before checkmate is a built in feature of the game!  :-D

Somewhere between Level III programming and system design, this problem might be resolved. As an experienced user (and I don't have the space to list databases and fiber systems I've designed here) working with PC's since 1978, I honestly don't understand this problem.

I have had the same blue screen error reporting annoyance for years. I just live with it. I suggest you give up and do the same.

It is apparent and obvious that Microsoft does not possess either the ability or skill to resolve this issue. I submit as evidence, the length of time this thread has been going on, all with no reasonable resolution.

If we, the users, think Microsoft is going to solve this common problem by accepting individual error reports, spending any kind of time analyze them, and then providing us (the general user public) a useful solution independent of the need to possess programming skills, let alone the time to effect them, all in the name of "hey public, do the work for us", well, that is just wishful thinking.

PS - I've never lost any data as a result of this problem except when it happens in the middle of constructing a research paper, on the last slide of a Power Point that's due "tomorrow", or once in a while just before I am ready to checkmate the computer during a Level 6 game...........no biggie.