Dmp analysis by PC Tailor on: 21/08/2019 using Microsoft (R) Windows Debugger Version 10.0.18914.1001 AMD64  and PCT Analyser V2   If you see any errors or possible improvements to definitions, please inform PC Tailor.
 
This section details the summary of the dump file, relevant parameters and system information.    
Bugcheck Summary Dump file analysed: 081219-11015-01.dmp]   Generic BSOD Troubleshooting Steps:
 
BugCheck 3B SYSTEM_SERVICE_EXCEPTION   - Check the System Log in Event Viewer for additional error messages that might help identify the device or driver that is causing this bug check.
- If a driver is identified on the left side of the report,
disable the driver or check with the manufacturer for driver updates.
- Ensure all
motherboard/chipset drivers are up to date, as well as any other software drivers (GPU etc.)
- You can try running the
hardware diagnostics supplied by the system manufacturer. To test memory, memtest can be used for at least 4 passes.
- Ensure your
BIOS is up to date.
- Confirm that
any new hardware that is installed is compatible with the installed version of Windows.
- If you have recently changed hardware, try removing it to see if the problem persists.
Probably caused by : partmgr.sys ( partmgr!PmPassThrough+67 )  
 
Arg1: 00000000c0000005, Exception code that caused the bugcheck  
Arg2: fffff80158c558d0, Address of the instruction which caused the bugcheck  
Arg3: ffffa48428060bd0, Address of the context record for the exception that caused the bugcheck  
Arg4: 0000000000000000, zero.  
PROCESS_NAME:  svchost.exe  
MODULE_NAME: partmgr  
IMAGE_NAME:  partmgr.sys  
  This section lists all third party modules / drivers loaded at the time of the crash.
Bugcheck Description:   Third Party Modules Loaded
SYSTEM_SERVICE_EXCEPTION  
This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.

The stop code indicates that executing code had an exception and the thread that was  it, is a system thread.

The exception information returned in parameter one is listed in NTSTATUS Values and is also available in the ntstatus.h file located in the inc directory of the Windows Driver Kit.
  ModuleName Time Stamp Company Description
  amdide64.sys 04/12/2012 09:49 AMD AMD SATA Controller Driver
  HWiNFO64A.SYS 31/03/2015 09:51 HWInfo HWInfo 64 Driver
  asstor64.sys 17/06/2015 03:40 ASMedia Asmedia ASM-106x Sata 6G controller
  asmtxhci.sys 16/08/2017 07:30 ASMedia ASMedia Usb 3.0 Driver
  nvlddmkm.sys 27/10/2017 15:49 NVIDIA NVIDIA Video Drivers
  RTKVHD64.sys 27/11/2018 11:24 Realtek Realtek HD Audio Driver
  nvhda64v.sys 19/03/2019 04:47 NVIDIA NVIDIA Audio HDMI Driver (nForce Chip)
About your bugcheck / typical cause:   Rt64win7.sys 10/05/2019 09:01 Realtek Realtek RTL Ethernet Drivers
This is typically driver based and therefore you should reference the third party modules loaded  to check which ones may be misbehaving.

Look at the STACK TEXT for clues on what was running when the failure occurred. If multiple dump files are available, compare information to look for common code that is in the stack
  aswArDisk.sys 20/06/2019 04:05 Avast Avast Antirootkit Disk Filter
  aswRvrt.sys 20/06/2019 04:05 Avast Avast Revert Driver
  aswRdr2.sys 20/06/2019 04:05 Avast Avast TDI Redirect Driver
  aswArPot.sys 20/06/2019 04:05 Avast Avast Antirootkit Driver
  aswKbd.sys 20/06/2019 04:05 Avast Avast Keyboard Filter Driver
  aswbuniv.sys 20/06/2019 04:06 Avast Universal Avast Driver
  aswbidsh.sys 20/06/2019 04:06 Avast Avast AV Driver
  aswSP.sys 20/06/2019 04:06 Avast Avast Self Protection Driver
          aswbidsdriver.sys 20/06/2019 04:06 Avast Avast IDS Activity Monitor Driver
System Information Including BIOS, Motherboard, Processor, and Memory   aswHdsKe.sys 20/06/2019 04:07 Avast Avast  Home Network Driver
  aswStm.sys 20/06/2019 04:07 Avast Avast AV Stream Filter Driver
[BIOS Information (Type 0) - Length 24 - Handle 0000h]   aswMonFlt.sys 29/07/2019 06:42 Avast Avast File System Monitor Filter Driver
  BIOS Version                  2103   aswSnx.sys 29/07/2019 06:42 Avast Avast Virtualisation Driver
  BIOS Release Date             11/06/2013   aswVmm.sys 02/08/2019 08:19 Avast Avast VM Monitor Driver
 
[BaseBoard Information (Type 2) - Length 15 - Handle 0002h]  
  Manufacturer                  To be filled by O.E.M.  
  Product Name                  To be filled by O.E.M.  
 
[Processor Information (Type 4) - Length 42 - Handle 0004h]  
  Processor Version             AMD FX(tm)-6300 Six-Core Processor               
  Processor Voltage             8dh - 1.3V  
  Current Speed                 3500MHz  
  Max Speed                     3500MHz  
 
[Memory Modules] Size Speed Part Number  
Memory Slot 1 No Data No Data No Data  
Memory Slot 2  4096MB 1600MHz   Part Number                   HU564404EP0200      
Memory Slot 3 No Data No Data No Data  
Memory Slot 4  4096MB 1600MHz   Part Number                   HU564404EP0200      
         
Memory Stack This is the chain of commands that have lead up to the crash  
 
[0x0]   nt!KeBugCheckEx    [0xf]   partmgr!PmGlobalDispatch + 0x1f     
[0x1]   nt!KiBugCheckDispatch + 0x69    [0x10]   nt!IofCallDriver + 0x59     
[0x2]   nt!KiSystemServiceHandler + 0x7c    [0x11]   nt!IofCallDriver + 0x59     
[0x3]   nt!RtlpExecuteHandlerForException + 0x12    [0x12]   nt!IopDeleteFile + 0x12d     
[0x4]   nt!RtlDispatchException + 0x4a5    [0x13]   nt!ObpRemoveObjectRoutine + 0x80     
[0x5]   nt!KiDispatchException + 0x16e    [0x14]   nt!ObfDereferenceObjectWithTag + 0xc9     
[0x6]   nt!KiExceptionDispatch + 0x11d    [0x15]   nt!ObCloseHandleTableEntry + 0x2c7     
[0x7]   nt!KiSegmentNotPresentFault + 0x337    [0x16]   nt!NtClose + 0xde     
[0x8]   ataport!PortWdmAlwaysStatusSuccessIrp    [0x17]   nt!KiSystemServiceCopyEnd + 0x28     
[0x9]   nt!IofCallDriver + 0x59    [0x18]   0x7ffecfc7c247     
[0xa]   CLASSPNP!ClasspCreateClose + 0x258     
[0xb]   CLASSPNP!ClassCreateClose + 0x3f     
[0xc]   CLASSPNP!ClassGlobalDispatch + 0x23     
[0xd]   nt!IofCallDriver + 0x59     
[0xe]   partmgr!PmPassThrough + 0x67     
Additional Info    
 
Microsoft Hyper-V also running.