On Sun, 7 Aug 2022 20:40:43 -0400, Paul <nospam@needed.invalid> wrote:

>On 8/7/2022 12:09 AM, Paul wrote:
>> On 8/6/2022 9:46 PM, pyotr filipivich wrote:
>>> "Mayayana" <mayayana@invalid.nospam> on Sat, 6 Aug 2022 08:23:30 -0400
>>> typed in alt.windows7.general  the following:
>>>> "pyotr filipivich" <phamp@mindspring.com> wrote
>>>>
>>>> | I don't recall a code on the popup.  There may be a code in the
>>>> | "dump" but first I'll have to be able to search the data dump.
>>>> |
>>>>    Popup?
>>>
>>>     Okay, the pop-up shows up after the reboot.
>>>
>
>You can point a camcorder or a digital point and shoot camera with
>video capability, at a (temporary) BSOD screen. The BSOD will stay
>on the screen for several frame times, and even with a camcorder,
>you might capture the frame with the BSOD on it, before the
>automatic reboot occurs.

The BSOD screen is not temporary. You can see it at any time, so the
automatic reboot isn't really a problem.

I previously linked to BlueScreenView from Nirsoft, if they need a
viewer.

On 8/7/2022 11:38 PM, pyotr filipivich wrote:

>> You can point a camcorder or a digital point and shoot camera with
>> video capability, at a (temporary) BSOD screen. The BSOD will stay
>> on the screen for several frame times, and even with a camcorder,
>> you might capture the frame with the BSOD on it, before the
>> automatic reboot occurs.
>
> Now all I have to do is have a camera ready to go when I'm reading
> email.

That instruction is only for cases where the symptoms are reproducible
on demand. If I can crash a computer within 30 seconds, it's worth
setting up a video camera to catch it.

I thought that's what you were telling us, was a certain activity
virtually guaranteed a crash.

Turn off room lights and work via screen light only. My P&S camera
seems to get the exposure better by staring at the screen and not
being distracted. It has autofocus.

If you have non-reproducible crashes, then disabling automatic
restart is better for that. Because you'd run out of film/battery/storage
if having to wait until it happens.

My P&S would run out of battery first and it has no wall adapter option.
Next it would run out of SD (because the SD limit is 32GB and it won't
take a 1TB one).

But my P&S also has the resolution, so the capture, the tiny text
of the BSOD declaration would be readable. My webcam isn't fine enough
for this work.

Paul

On 08/08/2022 01:40, Paul wrote:
>
> You can point a camcorder or a digital point and shoot camera with
> video capability, at a (temporary) BSOD screen. The BSOD will stay
> on the screen for several frame times, and even with a camcorder,
> you might capture the frame with the BSOD on it, before the
> automatic reboot occurs.

Yes, I once encountered this on a laptop which was endlessly rebooting,
used by the public in a cafe. I filmed it with just my mobile phone and
thereby showed the cafe owner that the hard disk was apparently failing.

However, as I think you said upthread, the best cure for this is not to
allow it to happen in the first place, and set the PC's startup option
*NOT* to reboot when it encounters a BSOD.

--

Fake news kills!

I may be contacted via the contact address given on my website:
www.macfh.co.uk

On 8/8/2022 2:00 AM, Char Jackson wrote:
> On Sun, 7 Aug 2022 20:40:43 -0400, Paul <nospam@needed.invalid> wrote:
>
>> On 8/7/2022 12:09 AM, Paul wrote:
>>> On 8/6/2022 9:46 PM, pyotr filipivich wrote:
>>>> "Mayayana" <mayayana@invalid.nospam> on Sat, 6 Aug 2022 08:23:30 -0400
>>>> typed in alt.windows7.general  the following:
>>>>> "pyotr filipivich" <phamp@mindspring.com> wrote
>>>>>
>>>>> | I don't recall a code on the popup.  There may be a code in the
>>>>> | "dump" but first I'll have to be able to search the data dump.
>>>>> |
>>>>>    Popup?
>>>>
>>>>     Okay, the pop-up shows up after the reboot.
>>>>
>>
>> You can point a camcorder or a digital point and shoot camera with
>> video capability, at a (temporary) BSOD screen. The BSOD will stay
>> on the screen for several frame times, and even with a camcorder,
>> you might capture the frame with the BSOD on it, before the
>> automatic reboot occurs.
>
> The BSOD screen is not temporary. You can see it at any time, so the
> automatic reboot isn't really a problem.
>
> I previously linked to BlueScreenView from Nirsoft, if they need a
> viewer.
>

[Picture]

https://i.postimg.cc/sX16ZcV5/bsod-video-results.jpg

In fact, in automatic reboot mode, the "BSOD" screen only appears
long enough for the dump stage to complete. If the dump was set
to minidump, it would not have taken 0.5 seconds as the video captured.

You can see in the frames at the top of the picture, that the screen
switches back to the non-BSOD view, until finally the screen goes black
as the reboot begins. It does not go from BSOD to reboot directly.
And the BSOD screen is there so that the crash dump progress can be
displayed.

Then it all depends on how the crash dump is set up. Normally,
the defaults for the OS are not to create 64GB crash dumps, when
a smaller dump will suffice. With a suitable setting, your video
might well only have three frames of BSOD on it.

I should have elevated the camera higher, since it's a TN screen,
to get a better view. It also did not seem to be in focus. I did not
have a large enough item handy, to elevate the camera for the
required camera angle. I was shooting with the camera on a mount.

Paul

"pyotr filipivich" <phamp@mindspring.com> wrote

| Now all I have to do is have a camera ready to go when I'm reading
| email.

Look at it on the bright side. There was a time when you
would have had to have written down all that gobbledygook
with a piece of charcoal on stone. :)

On Mon, 8 Aug 2022 06:25:37 -0400, Paul <nospam@needed.invalid> wrote:

>On 8/8/2022 2:00 AM, Char Jackson wrote:
>> On Sun, 7 Aug 2022 20:40:43 -0400, Paul <nospam@needed.invalid> wrote:
>>
>>> On 8/7/2022 12:09 AM, Paul wrote:
>>>> On 8/6/2022 9:46 PM, pyotr filipivich wrote:
>>>>> "Mayayana" <mayayana@invalid.nospam> on Sat, 6 Aug 2022 08:23:30 -0400
>>>>> typed in alt.windows7.general  the following:
>>>>>> "pyotr filipivich" <phamp@mindspring.com> wrote
>>>>>>
>>>>>> | I don't recall a code on the popup.  There may be a code in the
>>>>>> | "dump" but first I'll have to be able to search the data dump.
>>>>>> |
>>>>>>    Popup?
>>>>>
>>>>>     Okay, the pop-up shows up after the reboot.
>>>>>
>>>
>>> You can point a camcorder or a digital point and shoot camera with
>>> video capability, at a (temporary) BSOD screen. The BSOD will stay
>>> on the screen for several frame times, and even with a camcorder,
>>> you might capture the frame with the BSOD on it, before the
>>> automatic reboot occurs.
>>
>> The BSOD screen is not temporary. You can see it at any time, so the
>> automatic reboot isn't really a problem.
>>
>> I previously linked to BlueScreenView from Nirsoft, if they need a
>> viewer.
>>
>
> [Picture]
>
> https://i.postimg.cc/sX16ZcV5/bsod-video-results.jpg
>
>In fact, in automatic reboot mode, the "BSOD" screen only appears
>long enough for the dump stage to complete. If the dump was set
>to minidump, it would not have taken 0.5 seconds as the video captured.

That's what I don't understand. I agree that the BSOD screen only
displays for a short time if you have automatic reboot configured, but
there's nothing stopping you from rebooting and then displaying the BSOD
screen again after the reboot is complete. It's not as if it goes away
or anything if the PC is allowed to reboot.

>I should have elevated the camera higher, since it's a TN screen,
>to get a better view. It also did not seem to be in focus. I did not
>have a large enough item handy, to elevate the camera for the
>required camera angle. I was shooting with the camera on a mount.

Trying to capture a BSOD with a camera seems silly. Just reboot, then
display the BSOD screen for as long as you like. Bring it up, study it,
then task-switch to your browser to do some research, task-switch back
to the BSOD screen to get additional info, etc. The point is that BSOD
screens don't go away just because a system reboots.

"Mayayana" <mayayana@invalid.nospam> on Mon, 8 Aug 2022 07:48:49 -0400
typed in alt.windows7.general the following:
>"pyotr filipivich" <phamp@mindspring.com> wrote
>
>| Now all I have to do is have a camera ready to go when I'm reading
>| email.
>
> Look at it on the bright side. There was a time when you
>would have had to have written down all that gobbledygook
>with a piece of charcoal on stone. :)

You had charcoal?
>
--
pyotr filipivich
This Week's Panel: Us & Them - Eliminating Them.
Next Month's Panel: Having eliminated the old Them(tm)
Selecting who insufficiently Woke(tm) as to serve as the new Them(tm)

Paul <nospam@needed.invalid> on Sun, 7 Aug 2022 00:09:37 -0400 typed
in alt.windows7.general the following:
>On 8/6/2022 9:46 PM, pyotr filipivich wrote:
>> "Mayayana" <mayayana@invalid.nospam> on Sat, 6 Aug 2022 08:23:30 -0400
>> typed in alt.windows7.general the following:
>>> "pyotr filipivich" <phamp@mindspring.com> wrote
>>>
>>> | I don't recall a code on the popup. There may be a code in the
>>> | "dump" but first I'll have to be able to search the data dump.
>>> |
>>> Popup?
>>
>> Okay, the pop-up shows up after the reboot.
>>
>
>There are a ton of pages on finding crash dumps, finding
>Event Viewer entries, and so on. Did you get a MEMORY.DMP ?
>Get to work, dammit :-)
>
>It could be bad RAM.
>
>It could be an "IRQL less or equals".
>
>There are many possibilities, and your mission
>is to gather the evidence.
>
>If it's a BSOD, stopping the automatic reboot is for the
>satisfaction of making the message stand still on the
>screen.
{quote}
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033

Additional information about the problem:
BCCode: 1000007e
BCP1: FFFFFFFFC0000005
BCP2: FFFFF80003A3534F
BCP3: FFFFF88002EE1888
BCP4: FFFFF88002EE10F0
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\080722-14944-01.dmp
....\AppData\Local\Temp\WER-52416-0.sysdata.xml

{endquote}

This time I saved it.

Still do not know what it means, but ... I'll add that to the list
of things to resolve.
--
pyotr filipivich
This Week's Panel: Us & Them - Eliminating Them.
Next Month's Panel: Having eliminated the old Them(tm)
Selecting who insufficiently Woke(tm) as to serve as the new Them(tm)

"pyotr filipivich" <phamp@mindspring.com> wrote

|
| Still do not know what it means, but ... I'll add that to the list
| of things to resolve.

With that you can do a search. This returns results:

0x1000007e (0xFFFFFFFFC0000005

If I add in the 3rd number I get nothing. But this much could
help to narrow it down. Sometimes you'll come across a
discussion where someone figured out the same problem that
you have.

On 8/11/2022 8:42 PM, Mayayana wrote:
> "pyotr filipivich" <phamp@mindspring.com> wrote
>
> |
> | Still do not know what it means, but ... I'll add that to the list
> | of things to resolve.
>
>
> With that you can do a search. This returns results:
>
> 0x1000007e (0xFFFFFFFFC0000005
>
> If I add in the 3rd number I get nothing. But this much could
> help to narrow it down. Sometimes you'll come across a
> discussion where someone figured out the same problem that
> you have.
>
>

http://www.aumha.org/a/stop.php

0x0000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

0x1000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
Essentially the same error as 0x7E above.

https://web.archive.org/web/20080412030823/http://msdn2.microsoft.com/en-gb/library/ms795746.aspx

0xC0000005: STATUS_ACCESS_VIOLATION indicates a memory access violation occurred

Faulty device driver or system service. A faulty device driver or system service might be
responsible for this error. Hardware issues, such as BIOS incompatibilities, memory conflicts,
and IRQ conflicts can also generate this error.

If the problem is associated with Win32k.sys, the source of the error might be a third-party
remote control program. If such software is installed, you can remove the service by starting
the computer by using the Recovery Console and then deleting the offending system service file.

More or less same advice here.

https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0x7e--system-thread-exception-not-handled

Getting the name of an associated file, helps a bit.
For example, if it was an NVidia driver, you would
suspect a video driver issue. But just getting the
kernel file name as the faulty one, it could be
some unknown driver (like the "remote control program" unnamed
in their example).

The access violation is what happened. Something low level tried
to access memory not mapped for such access.

Paul

"Paul" <nospam@needed.invalid> wrote

| The access violation is what happened. Something low level tried
| to access memory not mapped for such access.
|

So it says, but how does that happen through Eudora?
Maybe something like older code that's running afoul of DEP?
But that's not a system process violation.
It seems that often these errors are red herrings. But then
in many cases they've been discussed online and people have
found one or more specific issues.

On 8/12/2022 9:39 AM, Mayayana wrote:
> "Paul" <nospam@needed.invalid> wrote
>
> | The access violation is what happened. Something low level tried
> | to access memory not mapped for such access.
> |
>
> So it says, but how does that happen through Eudora?
> Maybe something like older code that's running afoul of DEP?
> But that's not a system process violation.
> It seems that often these errors are red herrings. But then
> in many cases they've been discussed online and people have
> found one or more specific issues.

They can be due to RAM issues in kernel physical areas.

Then, it's "anything which is constantly doing I/O"
which may seem to be correlating with the problem.

Paul

"Mayayana" <mayayana@invalid.nospam> on Thu, 11 Aug 2022 20:42:35
-0400 typed in alt.windows7.general the following:
>"pyotr filipivich" <phamp@mindspring.com> wrote
>
>|
>| Still do not know what it means, but ... I'll add that to the list
>| of things to resolve.
>
>
>With that you can do a search. This returns results:
>
>0x1000007e (0xFFFFFFFFC0000005
>
> If I add in the 3rd number I get nothing. But this much could
>help to narrow it down. Sometimes you'll come across a
>discussion where someone figured out the same problem that
>you have.
>
Thanks, I'll try to follow up on that. (Being 'retired' I seem to
have no spare time ...)
--
pyotr filipivich
This Week's Panel: Us & Them - Eliminating Them.
Next Month's Panel: Having eliminated the old Them(tm)
Selecting who insufficiently Woke(tm) as to serve as the new Them(tm)

On 8/17/2022 9:50 PM, pyotr filipivich wrote:
> "Mayayana" <mayayana@invalid.nospam> on Thu, 11 Aug 2022 20:42:35
> -0400 typed in alt.windows7.general the following:
>> "pyotr filipivich" <phamp@mindspring.com> wrote
>>
>> |
>> | Still do not know what it means, but ... I'll add that to the list
>> | of things to resolve.
>>
>>
>> With that you can do a search. This returns results:
>>
>> 0x1000007e (0xFFFFFFFFC0000005
>>
>> If I add in the 3rd number I get nothing. But this much could
>> help to narrow it down. Sometimes you'll come across a
>> discussion where someone figured out the same problem that
>> you have.
>>
> Thanks, I'll try to follow up on that. (Being 'retired' I seem to
> have no spare time ...)

It's not just any ole number. It's a STOP code.

When the summary is displayed on the screen in
Win10 or Win11, the stop code remains the same,
but is generally shortened up to make it easier
for people to write down. Like

0x7e SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

You would look that up in Google as "STOP 0x7e".

Paul

"Paul" <nospam@needed.invalid> wrote

|
| You would look that up in Google as "STOP 0x7e".
| Or maybe look up both. I found lots of results in the
format I looked up because that's the traditional format
on blue screens. I'm guessing that what you posted is
Win10?

"pyotr filipivich" <phamp@mindspring.com> wrote

| Thanks, I'll try to follow up on that. (Being 'retired' I seem to
| have no spare time ...)

I know what you mean. The trick to stretching out time seems
to be to keep working part-time. If you stop altogether then it's
not long before there's not enough time to read the morning
paper before dinner.

If you can't work then you can substitute critical errands. For
example, decide that you simply must restock paper towels by
Friday. Then make a plan to get that done. When the task is
finished you'll be able to rest on your laurels, sit back, and enjoy
the luxury of reading the paper. :)

"Mayayana" <mayayana@invalid.nospam> on Thu, 18 Aug 2022 08:01:55
-0400 typed in alt.windows7.general the following:
>"pyotr filipivich" <phamp@mindspring.com> wrote
>
>| Thanks, I'll try to follow up on that. (Being 'retired' I seem to
>| have no spare time ...)
>
> I know what you mean. The trick to stretching out time seems
>to be to keep working part-time. If you stop altogether then it's
>not long before there's not enough time to read the morning
>paper before dinner.

"When the big paper hits the porch, I know it is time to put on my
clean clothes and go to church."
>
> If you can't work then you can substitute critical errands. For
>example, decide that you simply must restock paper towels by
>Friday. Then make a plan to get that done. When the task is
>finished you'll be able to rest on your laurels, sit back, and enjoy
>the luxury of reading the paper. :)

LOL.
I'm working on doing just that. It's anti-social media which is
the time vampire.
>
>
--
pyotr filipivich
This Week's Panel: Us & Them - Eliminating Them.
Next Month's Panel: Having eliminated the old Them(tm)
Selecting who insufficiently Woke(tm) as to serve as the new Them(tm)