View Single Post
  #11  
Old January 13th 19, 04:27 PM posted to alt.comp.os.windows-10
Paul[_32_]
external usenet poster
 
Posts: 11,873
Default Significant Windows 10 1809 Crash.

Keith Nuttle wrote:
On 1/12/2019 1:29 PM, Keith Nuttle wrote:
On 1/12/2019 1:18 PM, Paul wrote:
Keith Nuttle wrote:
This afternoon I was writing a summary of my research and the system
crashed big time. I was using the Word Perfect X8 and had at least
one document open in the Adobe Reader Continuous release version
2019.010.20069. I had Firefox Version 64.0.2 open. First Adobe
froze, then the Firefox, and finally WordPerfect. The system came to
a complete stop, even the recover screen that said it was collect
information on the error froze.

I normally have these programs running with equivalent documents.
Some time I have Thunderbird also opens so I was not working in an
abnormal program environment.

I am running Window 10 1809 OS build 17763.253 on an HP laptop with
Intel i7-65000 CPU, 8 GB ram, and a 1TB disk.

I have no idea of the error codes as I said every thing froze, and I
had to do a hard restart. (Hold down the power button until it shut
off)

Is this a common occurrence with this Windows 10 build and are the
causes being investigated?

I have a game that crashes out to desktop, and the
Event Viewer has some sort of power event that correlates
with the failures. Hard to say what is cause, and what is
side effect. That never used to happen with my previous
(gutless) video card.

You can try looking in the Reliability Monitor and see if
the event got logged before you had to hit the power button.

Things like this can happen if the OS runs out of a resource...
even though the Task Manager "Memory" display shows it's not
railed into trouble (down to the last 350MB). You could have
a pool leak perhaps.

If you're lucky, something (Event Viewer?) might give
you a driver name to work with. The driver itself might
not be the culprit, if some other driver ate the resources
and "a neighbor" reported a problem.

Paul

Sorry I forgot the Event Viewer. There were four errors that occurred
about the time if the failure.

I don't have any idea of what it means. I do know I have used the
same combination of program and similar files and never had this
problem before. Since there are four errors I assume that one
occurred when Adobe froze, Word Perfect Froze, and Firefox froze. I
don't remember what the fourth program I had open was.

They were identical. Each stated

Log Name: System
Source: Microsoft-Windows-DistributedCOM
Date: 1/12/2019 12:45:55 PM
Event ID: 10016
Task Category: None
Level: Error
Keywords: Classic
User: LAPTOP\Keith Nuttle2
Computer: LAPTOP
Description:
The application-specific permission settings do not grant Local
Activation permission for the COM Server application with CLSID
{2593F8B9-4EAF-457C-B68A-50F6B8EA6B54}
and APPID
{15C20B67-12E7-4BB6-92BB-7AFF07997402}
to the user LAPTOP\Keith Nuttle2 SID
(S-1-5-21-2958119282-3360191907-2581630708-1001) from address
LocalHost (Using LRPC) running in the application container
Unavailable SID (Unavailable). This security permission can be
modified using the Component Services administrative tool.
Event Xml:
Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"
System
Provider Name="Microsoft-Windows-DistributedCOM"
Guid="{1B562E86-B7AA-4131-BADC-B6F3A001407E}" EventSourceName="DCOM" /
EventID Qualifiers="0"10016/EventID
Version0/Version
Level2/Level
Task0/Task
Opcode0/Opcode
Keywords0x8080000000000000/Keywords
TimeCreated SystemTime="2019-01-12T17:45:55.280775900Z" /
EventRecordID12204/EventRecordID
Correlation /
Execution ProcessID="512" ThreadID="1492" /
ChannelSystem/Channel
ComputerLAPTOP/Computer
Security UserID="S-1-5-21-2958119282-3360191907-2581630708-1001" /
/System
EventData
Data Name="param1"application-specific/Data
Data Name="param2"Local/Data
Data Name="param3"Activation/Data
Data Name="param4"{2593F8B9-4EAF-457C-B68A-50F6B8EA6B54}/Data
Data Name="param5"{15C20B67-12E7-4BB6-92BB-7AFF07997402}/Data
Data Name="param6"LAPTOP/Data
Data Name="param7"Keith Nuttle2/Data
Data
Name="param8"S-1-5-21-2958119282-3360191907-2581630708-1001/Data
Data Name="param9"LocalHost (Using LRPC)/Data
Data Name="param10"Unavailable/Data
Data Name="param11"Unavailable/Data
/EventData
/Event

Something new, now I am getting these loud bell coming from the laptop.
It can not be turned off by the volume control. This morning when it
happened, it seemed to coincide with the time when my wife turned on her
computer which automatically connects to the LAN.

Two folders on her computer are mapped as drives on my laptop and
automatically connect when her computer is on.

Would this cause the error I experienced above or the alarms? Could it
be associated with changes in the way MS manages LAN connections and
shared information?


In the real world, tracing sounds isn't nearly this easy.

https://superuser.com/questions/3141...ds-on-my-syste

Sounds can be emitted, without using the Windows Sound Mixer,
which may alter the ability to "turn the volume down".

And the "beep" or "bell" is a "special object" uses when
a process or thread isn't allowed to do ordinary I/O. In fact,
if a computer is missing a sound driver, there may still be
some sort of fallback path making "bell". And good luck
tracing that, or figuring out where it comes from.

The BIOS (via the SMM routine), can make alarm noises on
the piezoelectric transducer (not the computer speakers).
I don't know if there is a BELL() object in say, ACPI table, that
allows the OS to get the BIOS to make the noise on its
behalf.

Based on the inability to trace the software path used,
my guess is that it's a SVCHOST or a driver or some
low level thing that isn't happy, and wants to tell
you about it. A much richer set of sound effects is
available in Ring3 User Space (play a WAV thru speakers).

I don't think I would be able to figure out the path
here, if it happened to me. I'd probably need a logic
analyzer with disassembler module or something, and "trace
execution" of everything, Ring0/Ring3 and so on. And on
modern processors, that would be hard to do (in real time),
a bit easier to do if execution on the machine was
slowed to a crawl.

*******

Go back and look in your Event Viewer, for some
sort of security issue. Maybe in addition to the sound,
there are new entries corresponding to a perceived
security breach or an audit failure.

Paul
Ads