Re: Blue Screen Error HELP!
I'm not disageeing, if there really is a 'why', perhaps we should consider
the language problem? Right now, there are three uses of 'default' that
comes to mind - you have the Legal use; the Sporting use; the Computer use.
In the Legal use, if you don't pay your bill, no court will ever process the
claim, it is simply forwarded to you and filed as evidence as a command to
pay.
In the Sporting use, if you don't show up for a match, or have put
unregistered players on the team - without any hearing for explanations
(asside from the press) you'll have lost the match.
A computer expects a command to do it's thing. If you don't enter a
command - in order for the process not to crash, 'some' reserve command is
executed in order for you to at least have the ability to stop it if you
should so wish, or a way for the process itself to automatically stop
executing gracefully, in the instance when further execution and/or
interaction has become pointless.
Often when Computerese is attempted being translated, 'default' comes out
the other end as 'standard'. Indeed, many conscientious programmers are
bending over backwards to keep their processes running in the most sensible
manner adapted to the functioning of the human brain and do invent and/or
follow a sort of 'standardized' semi-meaningfull sequence of defaults to
mimic 'intelligence'.
I don't assume much effort is spent if you've defaulted the machine to
re-boot - there are configuration options in place to logging and
streamlining the booting process to your own liking, so I think we shall
probably have to be content with being on our own - except for the lucky
instance when we can help each other out!
Tony. . .
"R. C. White" <rc@grandecom.net> wrote in message
news:16E15605-38D9-4084-B7C0-C7891DF37203@microsoft.com...
> Hi, Dan_Bee.
>
>> Why do M.S use the default "Not to show error message?"
>
> Well, it DOES show - but then restarts instantly before we can see more
> than a blue flash on the screen. And this is most definitely NOT a "BUG".
> Microsoft does this intentionally. It has been brought to their attention
> innumerable times. They still think this is the right default.
>
> The only reason I can think of for this behavior as the default is what we
> all probably learned in our first week of computing: MANY computing
> glitches are momentary things that can be cured by simply rebooting the
> computer. So, MOST of the time, the automatic restart will get the show
> back on the road - without any call to Tech Support or other hassle.
>
> But there are the times when the automatic restart does NOT fix the
> problem. THAT's when we need to be able to read the Stop code.
>
> RC
> --
> R. C. White, CPA
> San Marcos, TX
> rc@grandecom.net
> Microsoft Windows MVP
> (Running Windows Live Mail beta 2 in Vista Ultimate x64 SP1 beta v.275)
>
> "Dan_Bee" <DanBee@discussions.microsoft.com> wrote in message
> news:0173760C-54CC-4D95-AD2A-EBA028B9DF60@microsoft.com...
>> Again thanks' I took your advice and changed the default from Automatic
>> restart
>> as this makes sence if it happens again, or for any other blue screen
>> error
>> problem.
>>
>> I knew i t could be done from "F8"key exstended menu while booting, as i
>> have done so on other systems in the past , "thats fine if you are
>> getting
>> blue screens from boot" before you enter windows.
>> Why do M.S use the default "Not to show error message?"
>> It would be a lot easyer for users to find the help they need with this
>> info
>> in hand?.
>>
>> Tank's Again
>> Dan
>>
>> "R. C. White" wrote:
>>
>>> Hi, Dan_Bee.
>>>
>>> Thanks for the report back. Good detective work! ;<)
>>>
>>> But you might want to change that default setting from Automatically
>>> restart, anyhow, for the time when another of Vista' rare BSODs appears.
>>>
>>> RC
>>> --
>>> R. C. White, CPA
>>> San Marcos, TX
>>> rc@grandecom.net
>>> Microsoft Windows MVP
>>> (Running Windows Live Mail beta 2 in Vista Ultimate x64 SP1 beta v.275)
>>>
>>> "Dan_Bee" <DanBee@discussions.microsoft.com> wrote in message
>>> news:20BC9530-8F4E-4F5B-A0DB-63B9B3A09BBD@microsoft.com...
>>> > Thanks' for advice, I have now found the problem, It was one of the
>>> > sticks
>>> > of
>>> > Ram
>>> > I noticed the active led's on one of the 4 mod's was out of sync' with
>>> > the
>>> > other 3
>>> > So i swaped the 4 mod's with Kingston HyperX of the same spec' and all
>>> > was
>>> > fine again.
>>> > Thanks
>>> >
>>> > "R. C. White" wrote:
>>> >
>>> >> Hi, Dan_Bee.
>>> >>
>>> >> The log file is helpful, but the best clue to your problem is
>>> >> probably
>>> >> the
>>> >> Stop code on the BSOD (Blue Screen of Death). Unfortunately,
>>> >> Microsoft
>>> >> sets
>>> >> the default for "what to do on system failure" to "automatically
>>> >> restart" -
>>> >> and the restart happens so quickly that we never get a chance to read
>>> >> the
>>> >> BSOD. So one of the first things that I always do after installing
>>> >> Windows
>>> >> is change that default!
>>> >>
>>> >> Go to Control Panel | System and click Advanced System Settings
>>> >> (you'll
>>> >> need
>>> >> your Administrator password to get past here). On the next Advanced
>>> >> tab,
>>> >> click Settings under Startup and Recovery. This gets you finally to
>>> >> the
>>> >> page where you can remove the check from that Automatically restart
>>> >> line,
>>> >> then OK your way out.
>>> >>
>>> >> The next time, your computer will still abort, but it will halt with
>>> >> that
>>> >> BSOD onscreen, giving you all the time you need before you press the
>>> >> hardware Restart button. Copy down that Stop code - verbatim - along
>>> >> with
>>> >> the line of hex codes and any other text that might be there. It
>>> >> might
>>> >> be
>>> >> gibberish to you (and to me), but it will mean a lot to the gurus
>>> >> here
>>> >> who
>>> >> know how to read it. They can point you in the right direction.
>>> >>
>>> >> RC
>>>