| Details |
| Product: |
Windows
Operating System |
| ID: |
1000 |
| Source: |
OHN0000
Error |
| Version: |
0.000000001 |
| Symbolic
Name: |
U_R_SCRWD_BLU |
| Message: |
Fault: %100,
Unknown Module, Unknown Address, Unknown Name, Pretty Much All
Unknown, But Nice to Get a Message Anyway, Huh? |
| |
| Explanation |
|
The indicated program stopped unexpectedly. Yep. Life's Not
Fair. Get over it.
The message
contains details on which program and module stopped, but
you're way too dumb to decipher it. Don't feel bad, we made it that way. A matching event with Event ID 1001 might
also appear in the event log. So what? That just means you'll
feel twice as dumb.
|
| |
| User Action |
|
If an error report was generated for this error, you might
obtain even more confusing gobbly-gook about the error by
sending the report to Microsoft for analysis. Then, once the
sun runs out of hydrogen, you might get a reply. You may also
try spending your morning using Windows built in help to
troubleshoot the error. Once completed, and you receive the
message "Windows cannot resolve the problem", you
may decide to consider arson or a ball peen hammer as an
alternative.
What to expect
Microsoft actively analyzes all error reports and
prioritizes them based on whether the current bad press we've
been getting at the time is affecting our stock price. When a
report is submitted, Microsoft will see whether our stock is
up or down. If it is up, we discard the error, and wait until
it is down again to continue. If it is down, we do just enough
so it will rise again. Accordingly, it's not likely that
Microsoft will be able to provide a solution for your
particular error at any given time, but you may at anytime
check the status at MSFT
(NASDAQ).
|
|
You can find additional information on this topic
in the following Microsoft Knowledge Base articles:
• Glimmer of hope link
that refuses to load
This link existed once on the Microsoft website,
but it has been moved, or merged, or deleted. Too
bad, too, because it looked like exactly the
problem you were experiencing.
• How to really screw
things up further
This step-by-step article describes how to create absolute
havoc on your system, by just trying to fix a
relatively simple problem. You can create customized
problems so bizarre they actually don't exist in
nature. Eventually, you may be so jazzed, you'll be
convinced that you have major hardware failure, and
be replacing parts from Best Buy all weekend long.
Homicide may...
• How to interpret
USERENV 1000 events
This article describes how to interpret USERENV
1000 events. It's not going to get you anywhere, but
it can be useful in the way reading and memorizing
the parts assembly list for your refrigerator might be...
• Client, service, and
program incompatibilities that have no bearing on
your error, but look good on this page
This article describes incompatibilities running
Microsoft Windows 95, Microsoft Windows 98,
Microsoft Windows NT 4.0, Microsoft Windows 2000,
Microsoft Windows XP Professional, or Microsoft
Windows Home. It goes on for 10 city blocks. Go on!
Give it a try! We double dare ya!
|
|