Habe heute mehrfach Bluescreens sehen müssen:
System Service Exception
Memoy Management
PFN List Corrupt
Critical Process Died (2x)

BluescreenView:

==================================================
Dump File         : 101319-7125-01.dmp
Crash Time        : 13.10.2019 19:08:47
Bug Check String  : SYSTEM_SERVICE_EXCEPTION
Bug Check Code    : 0x0000003b
Parameter 1       : 00000000`c0000005
Parameter 2       : fffff800`4407e36a
Parameter 3       : ffffaf81`4afad930
Parameter 4       : 00000000`00000000
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+1c1220
File Description  : 
Product Name      : 
Company           : 
File Version      : 
Processor         : x64
Crash Address     : ntoskrnl.exe+1c1220
Stack Address 1   : 
Stack Address 2   : 
Stack Address 3   : 
Computer Name     : 
Full Path         : C:\WINDOWS\Minidump\101319-7125-01.dmp
Processors Count  : 12
Major Version     : 15
Minor Version     : 18362
Dump File Size    : 749.660
Dump File Time    : 13.10.2019 19:11:50
==================================================

==================================================
Dump File         : 101019-6968-01.dmp
Crash Time        : 10.10.2019 18:00:14
Bug Check String  : CRITICAL_PROCESS_DIED
Bug Check Code    : 0x000000ef
Parameter 1       : ffff858f`2715e080
Parameter 2       : 00000000`00000000
Parameter 3       : 00000000`00000000
Parameter 4       : 00000000`00000000
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+1c1220
File Description  : 
Product Name      : 
Company           : 
File Version      : 
Processor         : x64
Crash Address     : ntoskrnl.exe+1c1220
Stack Address 1   : 
Stack Address 2   : 
Stack Address 3   : 
Computer Name     : 
Full Path         : C:\WINDOWS\Minidump\101019-6968-01.dmp
Processors Count  : 12
Major Version     : 15
Minor Version     : 18362
Dump File Size    : 717.860
Dump File Time    : 10.10.2019 18:01:37
==================================================
         

WhoCrashed:

System Information (local)
--------------------------------------------------------------------------------

Computer name: DESKTOP-O466OPA
Windows version: Windows 10 , 10.0, version 1903, build: 18362
Windows dir: C:\WINDOWS
Hardware: ASRock, A320M-HDV R3.0
CPU: AuthenticAMD AMD Ryzen 5 2600 Six-Core Processor AMD8664, level: 23
12 logical processors, active mask: 4095
RAM: 17109430272 bytes (15,9GB)




--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dumps are enabled on your computer. 

Crash dump directories: 
C:\Windows
C:\Windows\Minidump

On Sun 13.10.2019 20:15:36 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: ntkrnlmp.exe (nt!memset+0x1515E) 
Bugcheck code: 0x4E (0x99, 0x10E20F, 0x2, 0x400011000116610)
Error: PFN_LIST_CORRUPT
Bug check description: This indicates that the page frame number (PFN) list is corrupted. 
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out. 
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 



On Sun 13.10.2019 19:08:47 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\101319-7125-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C1220) 
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8004407E36A, 0xFFFFAF814AFAD930, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code. 
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 



On Thu 10.10.2019 18:00:14 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\101019-6968-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C1220) 
Bugcheck code: 0xEF (0xFFFF858F2715E080, 0x0, 0x0, 0x0)
Error: CRITICAL_PROCESS_DIED
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a critical system process died. 
There is a possibility this problem was caused by a virus or other malware. 
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 



The following dump files were found but could not be read. These files may be corrupted:
C:\Windows\Minidump\101319-11390-01.dmp




--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

4 crash dumps have been found and analyzed. Only 3 are included in this report. If dump files are found and they could not be analuzed, it means they are corrupted. Because crash dumps are an emergency measure it is not uncommon for this to happen, however often it points to a problem in the storage stack. It is suggested that you run CHKDSK on your system drive to check your drive for errors. 
No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you. 


Read the topic general suggestions for troubleshooting system crashes for more information. 

Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
         

Habe den Rechner heute mit MBAM, Eset Onlinescanner & Emsisoft AntiMalware gescannt. Alles ohne Befund.

Mein 'Plan' ist jetzt MemTest86 v8.2 - USB über Nacht laufen lassen, weil für mich (laienhaft) so einiges auf den RAM zeigt.
Sinnvoll?
eventl. Treiberproblem? (Nvidia 436.48 zuletzt am 10. oder 11.10. installiert)
Alternativen?
weitere Infos nötig?
Danke!

Führe doch erstmal mdsched.exe aus, um den Speicher zu testen, bevor Du mit Memtest anfängst.

edit: oder schau mal hier:
http://de.pcerror-fix.com/gelost-wie-man-pfn_list_corrupt-blue-screen-fehler-0x0000004e-repariert/

mdsched.exe hat keine Fehler gefunden.

"2: Nach dem Öffnen der Eingabeaufforderung müssen Sie chkdsk / f eingeben und die Eingabetaste drücken."
funktioniert so nicht, der Befehl ist falsch; richtig ist: chkdsk /f: keine Fehler, auch bei DiskInfo ist alles 'gut'.

Microsoft OneDrive wurde von mir mit als erstes nach der letzten Neuinstallation deinstalliert.

Windows Error Repair Tool = Reimage

Die Treiber überprüft?

Ja, einzig, kürzlich aktualisiert ist der Nvidia-Treiber (#1).
MS-Update findet nichts & im Gerätemanager (incl. 'ausglebente Geräte anzeigen) ist auch nichts gelbes oder rotes.

Habe jetzt 2 Treiberupdates von Samsung (USB vom 08.10. & Modem vom 09.10.) versuchsweise deinstalliert. Beides Version 2.16.9.0.
Die hat sich w10 wohl beim angestecken S7 geholt. Habe sonst nichts, ausser einem Monitor, von Samsung.

Am Nvidia-Treiber kanns laut Microsoft Technet aber liegen, installier den doch mal neu.
Hattest Du denn noch neue Bluescreens?
Ansonsten doch mal Memtest86 über Nacht laufen lassen.

Ok, Nvidia-Treiber ist neu installiert.
Nein, kein weiterer BSoD.
Beobachte jetzt erst mal bis morgen Abend.
Besten Dank bis hierhin!