A desperate man with random BSOD

RAM
16.0GB Dual-Channel DDR3 @ 799MHz (10-10-10-30)

Do you have part number or link to the memory?

System Uptime: 6 days 5:06:25.051

this problem will be hard to find. I would update the bios, see if you can update the old mouse driver.
I would change the memory dump type to kernel so it will save debug info and internal error logs.
I would run verifier.exe to set debug flags to force the system to call a bugcheck when one driver writes to areas not allocated to that driver.

do the bios update since there seems to be some sort of issue going on with your system sleeping/hibernation.

you can run crystaldiskinfo.exe to read the smart data on the drive but generally the bogus memory address is more likely to be a driver bug.
since the problem took over 6 days to bugcheck the system, you might turn on more driver checks to get it to crash faster.

best to update the bios and motherboard drivers since it is the only fix you will have even if you knew which driver was making the programming mistake.

---------------
bogus memory address(-46) passed to kernel routine.
most likely some driver overwrote another drivers data.

the window cpu microcode update seems to be corrupted.
attempting to find the cpu microcode version in the debugger resulted in a error.

you might run cmd.exe as an admin and run
dism.exe /online /cleanup-image /restorehealth
maybe it will update this file:
\SystemRoot\system32\mcupdate_AuthenticAMD.dll ***** Invalid (84956950)

or maybe run the Microsoft windows update after you do your bios update.


I would suspect this old ball mouse driver:
\SystemRoot\system32\DRIVERS\t_mouse.sys Sun Dec 2 22:19:30 2012

BIOS Version P1.20
BIOS Release Date 01/12/2016
Manufacturer ASRock
Product 970A-G/3.1
Version
Processor Version AMD FX(tm)-8350 Eight-Core Processor
Processor Voltage 8eh - 1.4V
External Clock 200MHz
Max Speed 4000MHz
Current Speed 4000MHz

if you are charging a apple device, remove the device. apple devices pull 2 times the max allowed current on the usb port. this cause the usb port to shutdown many times a second. Unless you have a PC with a apple charging usb port and you have the special usbfilter driver that overrides the spec. This is a bad idea because of the bugs in these custom drivers.

google how to set up windows to make a kernel memory dump.
kernel dumps are required to debug usb related problems, and read the internal error logs.
having verifier running on all of the drivers makes debugging easier.
ie start cmd.exe or powershell.exe as an admin and
run verifier.exe /all /standard
then reboot.

be sure to turn it off after the next memory dump.
via
verifier.exe /reset

be sure you know how to get into safe mode, in case your machine bugchecks during the boot up process.

some mice require firmware updates from the mouse vendors website. or the updated mouse might require a updated mouse driver that matches the updated mouse firmware.

only things i see that are questionable is
\SystemRoot\system32\mcupdate_AuthenticAMD.dll ***** Invalid
(this it a amd cpu microcode patch that the debugger thinks is not working)

and your old t_mouse.sys driver from 2012 is still there.

system bugchecked because of a stack pointer error related to the GPU calls made by the game you were playing.
CivilizationVI.exe the error ended up calling memory address 0

you might start
https://docs.microsoft.com/en-us/sysinternals/downloads/autoruns
and uncheck the driver to see if you are actually using it.

uncheck the old mouse driver and see if it is actually being used. IE reboot and see if your mouse still works.

then new bugcheck was in the graphics driver:
nvlddmkm.sys Wed Oct 10 15:33:24 2018
the system was up for 6 days 10 hours

some sort of problem involving writing to virtual memory.

( I kind of think it is going to be related to corruption of your pagefile by the webservice printer or scanner. not sure how to prove it though.) I think it will be triggered by many rounds of sleeping and waking the computer. (4 hours or longer of sleep would be one sleep cycle)
any shutdown/restart would likely delay the problem.
(it is speculation, only because I have seen cases that took 16 sleep cycles before a bugcheck would happen and it was related to these drivers)


generally with a bugcheck in a graphics driver you would just go to nvidia website and install the most current graphics driver.

can not tell, my guess it is going to be a driver bug. I would be looking for a small increase in virtual memory usage over time. or maybe remove the print and scan driver and see if you still hit the problem.
or reboot your machine every few days to avoid the problem.

you might run cmd.exe or powershell as an admin and run
dism.exe /online /cleanup-image /restorehealth
but I don't think it will find anything.
then apply all windows updates.
and run a Malwarebytes scan.

a full memory dump might show what is going on. (rather than a minidump)
turn on verifier flags and leave them running until the next bugcheck might find a bug in a driver.
you might even force the system to thru a bunch of sleep and wake cycles to see if you can cause a bugcheck or for verifier to find a problem.

a bunch of sleep wake cycles (maybe 20). the system will not go to a full hibernation but it might find some issue.

or see if you can force a bunch of hibernations then wake the system again. do it in cycles.

even if you find the problem, your only fixes are to update the bios, and the motherboard drivers
and sometimes update firmware (for solid state drives).

if there is a problem with your memory, when the image of your operating system is copied from disk to memory it can get modified. then 4 hours after the system sleeps the modifications are written to disk and you have the change saved until you get a bugcheck. always good to run memtest86 to confirm that there are no memory problems at all.

38 copies of powershell.exe running
13 copies of NVIDIA Share.exe running
not sure why you would have so many of these running. I would stop the nvidia share utility
if you are not using it. just a likely cause of a stack overflow in a graphics driver
https://nvidia.custhelp.com/app/answers/detail/a_id/4228/~/disabling-the-geforce-experience-share-in-game-overlay

(best to turn off all of the nvidia add on programs if you are not using them)

6 errors : nt (fffff802ab0d9788-fffff802ab0d9792)

the debugger indicated a graphics driver fault (hardware problem)
IP_MISALIGNED
could be a stack overflow in the graphics driver, or a heat problem with the GPU or low voltage

you have a bunch of usb devices trying to wake.
you might have something that is messing up the usb
(maybe something with you UASSOFT.COM software for Keyboard And Mouse?)

no devices reported connected to usb 3
-------------
here are the modifications to the windows kernel and what was expected:
6 errors : !nt (fffff8027b2ec788-fffff8027b2ec792)
fffff8027b2ec780 00 00 00 00 00 00 00 00 *80 *3a *05 7b 02 f8 ff ff .........:.{....
fffff8027b2ec790 *d0 *3a *05 7b 02 f8 ff ff f0 af 44 00 00 00 00 00 .:.{......D.....
2: kd> u fffff8027b2ec780
nt!msrpc_NULL_THUNK_DATA:
fffff802`7b2ec780 0000 add byte ptr [rax],al
fffff802`7b2ec782 0000 add byte ptr [rax],al
fffff802`7b2ec784 0000 add byte ptr [rax],al
fffff802`7b2ec786 0000 add byte ptr [rax],al
nt!_guard_check_icall_fptr:
fffff802`7b2ec788 803a05 cmp byte ptr [rdx],5
fffff802`7b2ec78b 7b02 jnp nt!_guard_check_icall_fptr+0x7 (fffff802`7b2ec78f)
fffff802`7b2ec78d f8 clc
fffff802`7b2ec78e ff ???
2: kd> u
nt!_guard_check_icall_fptr+0x7:
fffff802`7b2ec78f ffd0 call rax
fffff802`7b2ec791 3a057b02f8ff cmp al,byte ptr [nt!PaletteBmp+0x12 (fffff802`7b26ca12)]
fffff802`7b2ec797 fff0 push rax
fffff802`7b2ec799 af scas dword ptr [rdi]
fffff802`7b2ec79a 440000 add byte ptr [rax],r8b
fffff802`7b2ec79d 0000 add byte ptr [rax],al
fffff802`7b2ec79f 0000 add byte ptr [rax],al
fffff802`7b2ec7a1 0000 add byte ptr [rax],al

2: kd> !chkimg -f !nt
Warning: Any detected errors will be fixed to what we expect!
Page 3700 not present in the dump file. Type ".hh dbgerr004" for details
Page 3700 not present in the dump file. Type ".hh dbgerr004" for details
6 errors (fixed): !nt (fffff8027b2ec788-fffff8027b2ec792)
2: kd> u fffff8027b2ec780
nt!msrpc_NULL_THUNK_DATA:
fffff802`7b2ec780 0000 add byte ptr [rax],al
fffff802`7b2ec782 0000 add byte ptr [rax],al
fffff802`7b2ec784 0000 add byte ptr [rax],al
fffff802`7b2ec786 0000 add byte ptr [rax],al
nt!_guard_check_icall_fptr:
fffff802`7b2ec788 20dd and ch,bl
fffff802`7b2ec78a 007b02 add byte ptr [rbx+2],bh
fffff802`7b2ec78d f8 clc
fffff802`7b2ec78e ff ???
2: kd> u
nt!_guard_check_icall_fptr+0x7:
fffff802`7b2ec78f ffb077047b02 push qword ptr [rax+27B0477h]
fffff802`7b2ec795 f8 clc
fffff802`7b2ec796 ff ???
fffff802`7b2ec797 fff0 push rax
fffff802`7b2ec799 af scas dword ptr [rdi]
fffff802`7b2ec79a 440000 add byte ptr [rax],r8b
fffff802`7b2ec79d 0000 add byte ptr [rax],al
fffff802`7b2ec79f 0000 add byte ptr [rax],al

AMD FX is so old that I can't remember if it has integrated graphics. I think it does. Can you take the graphics card out and see if the BSODS persist? 9 out of 10 its a graphics driver and you said you updated the drivers so let see if there's a hardware issue with your graphics card by taking it out of the build.

Can you get your hands on a temp graphics card?

user mode app tried to access a privileged instruction something that only a kernel driver can do.
system was running 17 days.
owing process was mgsvtpp.exe (looks like METAL GEAR SOLID V)
(guessing the app may have corrupted its stack)

-you have a large number of powershell commands boxes running

you might run verifier.exe to catch programs making this kind of programming mistake. most likely it will be a 3rd party service trying to talk to its device driver.

-ten physical hardware devices were trying to wake up from sleep at the time of the bugcheck. sleep state was s4
https://docs.microsoft.com/en-us/windows-hardware/drivers/kernel/system-sleeping-states

no usb 3 devices reported as connected to usb 3
3 devices seem to be running:
keyboard:Wuxi China Resources Semico Co., Ltd.
mouse: Pixart Imaging, Inc.
Wuxi China Resources Semico Co., Ltd (listed as consumer controls and desktop controls)

usb logs for these three devices could not be read. this could mean a custom usb driver is required for your machine.

no other devices were reported as connected to usb.
if you have other usb devices then one of the 3rd party drivers might not be processing wake events correctly ie not passing the usb packets to the other devices so they will wake.
old mouse driver is loaded:
\SystemRoot\system32\DRIVERS\t_mouse.sys Sun Dec 2 22:19:30 2012
usb devices that were awake:
PDO Generic Desktop Controls (0x01) | Keyboard (0x06)
Generic Desktop Controls (0x01) | Mouse



usb devices were waiting to wake: (none of these devices show up in the list of devices)
(not sure if anything is actually connected) you can download and run this tool to read status of usb ports and see what is connected: https://www.uwe-sieber.de/usbtreeview_e.html
usbpdo 0
usbpdo 4
USBPDO-5
USBPDO-3
USBPDO-1
USBPDO-7
USBPDO-8
USBPDO-6