Multiple "Powershell has stopped working" events

A friend is getting many Powershell errors

Often 20 or more interruptions per session.

The Application Event log shows many sets of 4 events
Error 22/03/2018 13:05:08 Application Error 1000 (100)
Error 22/03/2018 13:05:08 Application Error 1000 (100)
Error 22/03/2018 13:05:08 .NET Runtime 1026 None
Error 22/03/2018 13:05:08 .NET Runtime 1026 None
We simply close the window and carry on until next annoying interruption...
Everything else works OK

Diagnosis actions to date:
I have run CHKDSK C: /F /R with no errors. I have NOT (yet) run SFC

I've attached a text file with the event log text.
The base event always seems to be a .NET Runtime error
Faulting module name: ntdll.dll
Exception code: 0xc0000005

The problems occur on a friend's system - spec as follows

Win 10 v1709 64bit latest build
1 x 120 GB SSD as system disk
1 x 1TB HDD for data
Intel core i5-3210M @ 2.5GHz 6GB RAM
Dell Inspiron 17 motherboard

Any suggestions to fix this problem will be very welcome.
I hope I don't have to rebuild the system from scratch.

PShell error log.txt

Thanks Dimitri.
I'd like to make two small points

• The MS article on SFC here says under Win 10 users should run DISM before SFC, not after.

• The error message says "PowerShell has stopped working". When I browsed the DISM options, all the options are in verb-noun style, very like PowerShell. I'm worried DISM itself may need a reliable, working, PowerShell, and PS is the problem I need to fix.

For this reason, I think I'll follow your recommended SFC first, then DISM + SFC if problem remains. SFC is a much older utility, and may not need a fully functional PS service.

Spilly

This is an update on the problem, with some sample event log details

PowerShell started crashing on 14th Feb, and ever since crashes many times daily.
(2,800 ERROR log entries so far, on the filtered log)

Each time, the user gets this error window

which he closes and tries to carry on using the system. When left idle for a while, there can be 20 error windows to close

Actions taken:
As recommmended by Ddelo, I have run chkdsk C: /f /r, and DISM /Online /Cleanup-Image /RestoreHealth and SFC.exe /scannow No problems found; PS still fails frequently

What I now need...
...is advice on what to do next.
As a last resort, I could restore a Feb 1st backup of C: , and then recover the current set of user data files (all in D: ). As an absolute last ditch I could re-burn the entire system I suppose.

Sample Event log entries
Here are some relevant event log entries ("PowerShell_Crash.DOCX" attached)
- each error instance creates up to three pairs of error log entries.

The pairs are 98% identical, so I've pasted a single sample of each

I looked in

Code:

C:\ProgramData\Microsoft\Windows\WER\ReportArchive

, and found 500 folders there, all named AppCrash_powershell.exe..., each of which contains a

Code:

Report.WER

file - sample attached
The WER\tmp folder contains a couple of .tmp.dmp files - size under 500KB if useful


Any practical suggestions gratefully received

spilly
Attached: Report.WER.txt + PowerShell_Crash.DOCX containing error log text

Hardware of error system
Dell Inspiron 17R 6GB RAM, 1x120GB mSATA SSD for system, 1x1TB HDD for user data
Intel Core i5-3210M @ 2.50 GHz

I did as you suggested, but it found nothing and the bug is still there

I have since established this is caused by the Feb Windows Update package.
If I uninstall all Cum Patches back to Build 192, the fault goes away.
When WU installs any higher build, the fault recurs immediately after installing the new build

I'm using Win 10 Home x64, so updates are forced on me sooner or later

Googling did not find many others with my symptoms, so I'm fearful the bug will remain unfixed for a while (because the bug does not appear on My other laptop already at the latest build).
I will await my fate...

spilly
NB Since I've discovered this is a WU bug, I've posted my problem in a new thread in the Windows Update forum