S
Stan Brown
WOW -- you posted upside down *and* you used WLM 15 to screw up the
quotes. It's two for one.
Please, please use a real newsreader, and quote and post in the
standard way.
quotes. It's two for one.
Please, please use a real newsreader, and quote and post in the
standard way.
G
Gene E. Bloch
It's the favorite trick of academics: "left as an exercise for the
reader"
B
Bob I
No, the reader is supposed to post back,It's the favorite trick of academics: "left as an exercise for the
reader"
"You have our sympathies."
G
Gene E. Bloch
But maybe he *doesn't* have our sympathies
Just sayin'...
C
charlie
Some of those error messages flash, and are gone in less than the blinkBut maybe he *doesn't* have our sympathies
Just sayin'...
of an eye. One I see occasionally (benign) has to do with a slow to
shutdown windows driver module. About the time you get halfway through
the useless verbiage, and just start to comprehend the real error
message, it's gone!
R
Roy Smith
Because we're supposedly computer experts and so we should know exactly
what error message they're talking about! ;-) Sorry but I failed at
ESP miserably, my ex-wife can verify that.
--
Roy Smith
Windows 7 Professional 64-bit
Thunderbird 3.1.9
Friday, March 25, 2011 7:29:42 PM
G
Gene E. Bloch
I recall that when I had that problem a few years ago I set up a
camcorder in front of the screen and ran it while I did what was needed
to trigger the problem.
The main thing wrong with this approach was that the captured video was
pretty much unreadable
I know that there is (or was in an older version) a configuration
setting to prevent Windows from rebooting on certain errors, which has
the benefit of leaving the message on screen. This is something I didn't
know about when I set up the camcorder...and it doesn't sound like that
would help you.
R
R. C. White
Hi, Gene.
Failure? The is the default setting in every Windows since at least Win2K.
Whenever the system encounters a fatal problem, it puts up the BSOD (Blue
Screen of Death) with text and codes that tell an expert user what triggered
the problem, and then reboots. As we all know, simply rebooting fixes many
kinds of computer glitches, so Microsoft figures this setting is best for
most users, who wouldn't understand the codes anyhow.
But sometimes the restart does not fix the problem. And, since the
automatic restart is so fast, the BSOD flashes on and off the screen so
quickly that there's no hope to read what it says. So even experts are left
with no clue as to what the problem is - unless they can read the technical
log and memory dump that are written to disk in the split second before the
reboot.
Hidden a half-dozen or more mouse-clicks deep is a page to change this
default setting, and I heartily recommend it to everybody. The click-path:
Start | Control Panel | System | Advanced System Settings | (you'll need
Administrator credentials to get past here) | on the Advanced tab under
Startup and recovery , click Settings - and we are finally at the page we
need. In the middle of this page, under System failure, clear the check box
for Automatically restart, then OK your way out. It's a very easy fix at
the end of a very long click-path.
Next time the error happens you'll still need to reboot, but it won't happen
instantly and automatically. The system will halt with the BSOD onscreen
and won't restart until you press the hardware Reset button. This will give
you all the time you need to read the BSOD, take notes, take a photo if you
like - and even go have a cup of coffee.
Most of us don't understand the Stop Codes, but we can look them up on the
web or in books or ask techie friends, who can tell a lot from those cryptic
codes. Post the codes here - verbatim! - and there's a good chance that
someone will point you in the right direction. The top half or so of the
BSOD screen is "boilerplate" language which usually doesn't help at all.
But the bottom half holds the clues that we need.
If that's NOT what you meant, Gene, maybe you or others can still salvage
something useful from my ramblings. ;^}
RC
--
R. C. White, CPA
San Marcos, TX
(e-mail address removed)
Microsoft Windows MVP (2002-9/30/10)
Windows Live Mail Version 2011 (Build 15.4.3508.1109) in Win7 Ultimate x64
SP1
"Gene E. Bloch" wrote in message
camcorder in front of the screen and ran it while I did what was needed
to trigger the problem.
The main thing wrong with this approach was that the captured video was
pretty much unreadable
I know that there is (or was in an older version) a configuration
setting to prevent Windows from rebooting on certain errors, which has
the benefit of leaving the message on screen. This is something I didn't
know about when I set up the camcorder...and it doesn't sound like that
would help you.
Are you talking about the setting to Automatically restart on System
Failure? The is the default setting in every Windows since at least Win2K.
Whenever the system encounters a fatal problem, it puts up the BSOD (Blue
Screen of Death) with text and codes that tell an expert user what triggered
the problem, and then reboots. As we all know, simply rebooting fixes many
kinds of computer glitches, so Microsoft figures this setting is best for
most users, who wouldn't understand the codes anyhow.
But sometimes the restart does not fix the problem. And, since the
automatic restart is so fast, the BSOD flashes on and off the screen so
quickly that there's no hope to read what it says. So even experts are left
with no clue as to what the problem is - unless they can read the technical
log and memory dump that are written to disk in the split second before the
reboot.
Hidden a half-dozen or more mouse-clicks deep is a page to change this
default setting, and I heartily recommend it to everybody. The click-path:
Start | Control Panel | System | Advanced System Settings | (you'll need
Administrator credentials to get past here) | on the Advanced tab under
Startup and recovery , click Settings - and we are finally at the page we
need. In the middle of this page, under System failure, clear the check box
for Automatically restart, then OK your way out. It's a very easy fix at
the end of a very long click-path.
Next time the error happens you'll still need to reboot, but it won't happen
instantly and automatically. The system will halt with the BSOD onscreen
and won't restart until you press the hardware Reset button. This will give
you all the time you need to read the BSOD, take notes, take a photo if you
like - and even go have a cup of coffee.
Most of us don't understand the Stop Codes, but we can look them up on the
web or in books or ask techie friends, who can tell a lot from those cryptic
codes. Post the codes here - verbatim! - and there's a good chance that
someone will point you in the right direction. The top half or so of the
BSOD screen is "boilerplate" language which usually doesn't help at all.
But the bottom half holds the clues that we need.
If that's NOT what you meant, Gene, maybe you or others can still salvage
something useful from my ramblings. ;^}
RC
--
R. C. White, CPA
San Marcos, TX
(e-mail address removed)
Microsoft Windows MVP (2002-9/30/10)
Windows Live Mail Version 2011 (Build 15.4.3508.1109) in Win7 Ultimate x64
SP1
"Gene E. Bloch" wrote in message
I recall that when I had that problem a few years ago I set up a
camcorder in front of the screen and ran it while I did what was needed
to trigger the problem.
The main thing wrong with this approach was that the captured video was
pretty much unreadable
I know that there is (or was in an older version) a configuration
setting to prevent Windows from rebooting on certain errors, which has
the benefit of leaving the message on screen. This is something I didn't
know about when I set up the camcorder...and it doesn't sound like that
would help you.
C
Char Jackson
I have used BlueScreenView from Nirsoft
<http://www.nirsoft.net/utils/blue_screen_view.html>
to read the crash dump files after the fact. I get a lot of systems
into the shop with the vague complaint that it crashed or it keeps
rebooting, etc, so being able to view the BSOD details is a real
blessing.
On the systems that permanently live here at the house or in my shop,
I always disable the 'automatically restart' option. If there's going
to be a BSOD I'd rather know about it for sure, rather than wondering
why the computer is sitting there with that 'freshly rebooted' look.
G
Gene E. Bloch
That is indeed what I meant. Your detailed explication should help me,
and maybe even the OP, if that's why he can't see the message.
I'll also look into Char's suggestion about the NirSoft program.
Never mind - it's here and installed (it is high time to start taking
memory pills).
C
Char Jackson
Oh, good! I'm not the only person who downloads and tries to install
software that I already have.