Hi. . .
Thank you for the files. I did not really find anything that pointed to the nature of the problem, but I'm still going through the Event Viewer logs looking for out-of-place/odd entries. I did find quite a few surprises, which are detailed below.
One thing that I would highly recommend that you do as soon as possible and for the duration of our work here is to uninstall Kaspersky Internet Security 2019 (for now). KIS (like other similar products) is very extremely resource intensive and it's firewall has a tendency to block local NETBIOS ports, which in and of itself can cause freezing. The blocking of these ports is typical of all 3rd party firewalls, but KIS seems to have more trouble than most.
I am an ESET Beta tester and part of my job is to install competitor Internet Security Suites and to test them as well. Several years ago, it was time for me to test KIS. At that time, I had an HP dv7-1020us Core2Duo laptop and KIS brought it to its knees. I literally was unable to perform other functions (i.e., use the system normally) while KIS was installed.
However, things have changed since then. KIS has certainly changed and your system (8th gen corei7 - definitely one of the most powerful systems available) should be much better equipped to handle resource intensive apps like KIS vs. my Intel Core2Duo laptop all those years ago).
However, it is worth a try to see how your system performs without KIS.
Be sure to use the Kaspersky "kavremover tool" removal tool -
Removal tool for Kaspersky Lab applications (kavremover)
Please be sure to re-boot the system immediately after the removal tool app finishes to assure that boot drivers and kernel mode drivers get removed properly and fully. If not, the KIS drivers could still load into RAM and cause problems.
I could not help but notice that there were 2 mini dump files I the attached zip file dated 8 May and 10 May 2019. Unfortunately, both are corrupted and in fact contain very little data as if to indicate that the system came down/crashed so fast that Windows did not have time to write a complete memory dump.
Further investigation into the Event Viewer logs and the output of the Windows app
msinfo32 indicate that you have suffered a total of
8 (eight) BSODs recently - (scroll to right; look for the word
BlueScreen) -
Code:
06-May-19 6:34 PM Windows Error Reporting Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 1000007e
P2: ffffffffc0000005
P3: fffff804433cc7bf
P4: ffff8681e7d167a8
P5: ffff8681e7d15ff0
P6: 10_0_17763
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\050619-27859-01.dmp
\\?\C:\WINDOWS\TEMP\WER-453078-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2AA7.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2AB8.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2AF6.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2B06.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_1000007e_25241770d6aeb0c2b67347b444a0b153c79d971_00000000_cab_347f96c1

Analysis symbol: 
Rechecking for solution: 0
Report Id: 8cf34efd-260e-485b-8043-552fecad3c98
Report Status: 2049
Hashed bucket: 
Cab Guid: 0
06-May-19 6:16 PM Windows Error Reporting Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 1000007e
P2: ffffffffc0000005
P3: fffff804433cc7bf
P4: ffff8681e7d167a8
P5: ffff8681e7d15ff0
P6: 10_0_17763
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\050619-27859-01.dmp
\\?\C:\WINDOWS\TEMP\WER-453078-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2AA7.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2AB8.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2AF6.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2B06.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_1000007e_25241770d6aeb0c2b67347b444a0b153c79d971_00000000_03a32b05

Analysis symbol: 
Rechecking for solution: 0
Report Id: 8cf34efd-260e-485b-8043-552fecad3c98
Report Status: 4
Hashed bucket: 
Cab Guid: 0
06-May-19 3:06 PM Windows Error Reporting Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: deaddead
P2: 0
P3: 0
P4: 19fb96d1
P5: 3c2a58ed
P6: 10_0_17763
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\050619-43656-01.dmp
\\?\C:\WINDOWS\TEMP\WER-230156-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD3FB.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD41B.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD41E.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD45D.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_deaddead_69dcc0e61e897872072459d7e7784e638ec21a7_00000000_cab_111ca3dd

Analysis symbol: 
Rechecking for solution: 0
Report Id: 317de70b-35c2-4200-9a2f-1fe04bd263cc
Report Status: 2049
Hashed bucket: 
Cab Guid: 0
06-May-19 3:05 PM Windows Error Reporting Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: deaddead
P2: 0
P3: 0
P4: 19fb96d1
P5: 3c2a58ed
P6: 10_0_17763
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\050619-43656-01.dmp
\\?\C:\WINDOWS\TEMP\WER-230156-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD3FB.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD41B.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD41E.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD45D.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_deaddead_69dcc0e61e897872072459d7e7784e638ec21a7_00000000_03c3d4a6

Analysis symbol: 
Rechecking for solution: 0
Report Id: 317de70b-35c2-4200-9a2f-1fe04bd263cc
Report Status: 4
Hashed bucket: 
Cab Guid: 0
05-May-19 3:35 PM Windows Error Reporting Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 1000007e
P2: ffffffffc0000005
P3: fffff805623187b8
P4: ffff810b4ee3dc88
P5: ffff810b4ee3d4d0
P6: 10_0_17763
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\050519-92375-01.dmp
\\?\C:\WINDOWS\TEMP\WER-224062-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER94BF.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER95BA.tmp.xml

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_1000007e_964fb53cf318f7c7112acc3f2fe6bbb2fc8c33af_00000000_cab_13095157

Analysis symbol: 
Rechecking for solution: 0
Report Id: 5708f0af-34b0-41d7-a441-434a18fb8093
Report Status: 2049
Hashed bucket: 
Cab Guid: 0
05-May-19 3:27 PM Windows Error Reporting Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 1000007e
P2: ffffffffc0000005
P3: fffff805623187b8
P4: ffff810b4ee3dc88
P5: ffff810b4ee3d4d0
P6: 10_0_17763
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\050519-92375-01.dmp
\\?\C:\WINDOWS\TEMP\WER-224062-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER94BF.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER95BA.tmp.xml

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_1000007e_964fb53cf318f7c7112acc3f2fe6bbb2fc8c33af_00000000_032f95b9

Analysis symbol: 
Rechecking for solution: 0
Report Id: 5708f0af-34b0-41d7-a441-434a18fb8093
Report Status: 4
Hashed bucket: 
Cab Guid: 0
05-May-19 10:19 AM Windows Error Reporting Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 1000007e
P2: ffffffffc0000005
P3: fffff8004e32b7b8
P4: ffff810b7f445c88
P5: ffff810b7f4454d0
P6: 10_0_17763
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\050519-69000-01.dmp
\\?\C:\WINDOWS\TEMP\WER-342953-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6875.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6896.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6899.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER68C9.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_1000007e_1cdda4af33314038eeee7284f37c9ca52d4377b_00000000_cab_19a96a0c

Analysis symbol: 
Rechecking for solution: 0
Report Id: 00b40e23-d1e3-4602-afcc-3b44ebddd6ec
Report Status: 2049
Hashed bucket: 
Cab Guid: 0
05-May-19 10:19 AM Windows Error Reporting Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 1000007e
P2: ffffffffc0000005
P3: fffff8004e32b7b8
P4: ffff810b7f445c88
P5: ffff810b7f4454d0
P6: 10_0_17763
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\050519-69000-01.dmp
\\?\C:\WINDOWS\TEMP\WER-342953-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6875.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6896.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6899.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER68C9.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_1000007e_1cdda4af33314038eeee7284f37c9ca52d4377b_00000000_03c168e3

Analysis symbol: 
Rechecking for solution: 0
Report Id: 00b40e23-d1e3-4602-afcc-3b44ebddd6ec
Report Status: 4
Hashed bucket: 
Cab Guid: 0
I see that Windows was installed (or if a new system, the date that you initially booted the system) about 2.5 months ago -
Code:
Original Install Date: 08-Mar-19, 11:36:38 PM
Is this a new system that you purchased on or about 8 March 2019?
I have been facing this issue since past one month.
Any idea as to what happened about 1 month ago? Did you have any problems with the system before this time?
Check the Reliability Monitor.
Press the WIN key and type
reliability; select
Reliability Monitor or
View Reliability History
The Reliability Monitor will appear. You can click on the red circles to obtain additional info on what the errors are.
From my system:
If you purchased the system in March, it would still be under warranty. I would implore you to contact Acer support and tell them that you want a replacement system as there is definitely something very wrong with your system. To have at least 8 BSODs plus hundreds of app crashes (you can see these crashes in the Sysnative folder in Documents -
msinfo32.nfo file; "software environment"; "Windows Error Reporting"
There are 1,057 entries under Windows Error Reporting - the majority of which are application (app) crashes and hangs. This simply should not be for a new system. It truly is unacceptable especially given what you likely paid for this new corei7 system.
Contact Acer support and link them to this thread (this post in particular) as proof of the problems you are having -
Service & Support | Acer Official Site
That is all that I have for you at the moment.
Regards. . .
jcgriff2