daily BSOD during normal windows use (not gameplay)

Yesterday, I installed a newer version of Citrix. (Need it for work.)
I started with verifier last evening. No BSOD during this period (2 hours) with these tests active:
Attachment 226476

Today, I was at work. The computer was used by a family member at home with verifier turned off.
A BSOD appeared. When I got home, I ran BETA collector en uploaded the DMP file https://drive.google.com/open?id=11m...KfHU2lTK_dugqM

But, during running of BETA collector, again a BSOD.
I did not see a new DMP file, but I ran BETA collector again.
I am not sure if it helps, but I uploaded both sets of logfiles. I manually zipped the first batch of log files.

The latest bugcheck was 7E.
There were no misbehaving drivers seen in the mini dump.
In the memory dump the Nvidia GPU drivers were seen after the crash occurred.

If there are more misbehaving drivers in the memory dumps they can be troubleshooted.
If there are no misbehaving drivers identified in the next few BSOD then the hardware can be tested.

This evening, I continued with driver verifier, adding additional tests.

Only when activating the final 4 tests, I got repeating BSOD during boot.
Driver "atksgt.sys" was mentioned in de BSOD

Test settings were:
Attachment 226508

I ran collector and uploaded DMP: MEMORY_03-06b.DMP - Google Drive

and the BETA collector logs: Attachment 226509

For the Microsoft Windows driver verifier link it displayed to check all tests except DDI compliance checking and randomized low resource simulation.
For the latest crash DDI compliance checking (additional) was checked.
Please uncheck this test for the driver testing.
When all tests are checked there should be approximately nineteen simultaneous tests.

Ztruker said:

Do you use this? If so consider looking for an updated version. If it's unimportant than uninstall it.
It's old: 17-5-2009 15:36:34 C:\WINDOWS\system32\DRIVERS\atksgt.sys

Thanks for your reply.
I have never heard of it, and I have no idea which program on my computer uses this driver.

I uninstalled the driver by running "TagesSetup_x64 -nouninst" in an administrator command prompt.
Attachment 226576

Nothing seemed to happen.

When I run verifier, I can still select "atksgt.sys" in the list
Attachment 226575

I am puzzled now what to do and how to remove this driver.

Today, before I started with driver verifier again, I got a BSOD twice.
Attached is de BETA ZIP (run at 16:16 hours) and the DMP file: MEMORY_03-09.DMP - Google Drive

Then, I turned verifier on, according to the instructions.
- I always enable the three tests as shown in:
Enable and Disable Driver Verifier in Windows 10 | Tutorials

- Then I add 3 to 4 additional tests. If it runs OK for an hour, I deselect them and I select 3-4 other tests. I always let the 3 "first" test enabled. (If that all went well, I will increase the number of simultaneous tests.)

So, today, I started with this selection:

Attachment 226775

(NB: including I/O verification enabled)

I got a BSOD during booting.
I started up (through recovery) in safe mode, and I turned verifier off . Rebooted in normal mode, and I ran BETA collector (at 16:48 hours) and attached the ZIP. No new DMP file present.

The stopcode on the BSOD is "DRIVER VERIFIER DETECTED VIOLATION" with"atksgt.sys"

I already tried to reinstall and uninstall astkgst.sys with tagessetup_64 earlier today, but it seems unsuccesfull.

The mini dump files in the attached files were bugcheck 50: page_fault_in_nonpaged_area
Debugging with windbg displayed no misbehaving drivers.

Debugging the memory dump file also displayed no misbehaving drivers during the crash.
Then Nvidia GPU drivers were displayed after the crash.

Use Everything to identify the location of atksgt.sys.

See if there are methods in this link that had not already being used to uninstall the software:
TAGES, the AAA Copy Protection System

For Windows driver verifier uncheck atksgt.sys.
Run the tool to see if there are other misbehaving drivers.
Once the tool is run for 36 to 48 hours with no BSOD then recheck all drivers.
For the methods to turn off or recover from using windows driver verifier whenever possible use verifier /reset or the bootmode command. The dump files may be lost using system restore.
Driver Verifier-- tracking down a mis-behaving driver. - Microsoft Community

OK, thanks.

1) I succesfully removed TAGES from my computer with the instructions on TAGES, the AAA Copy Protection System

atksgt.sys is not present anymore. (And I discovered that the game Settlers6.exe uses this driver. This game needs TAGES to run.)

2) Then, I ran a new macrium backup and new restore point.
3) Then I turned verfier on. I began with a few tests, and in a couple of steps, I added new tests and let it run for an hour, before adding the next few tests.

4) Today, I turned on all tests (except DDI compliance, addidional DDI compliance and randomised low resource simulation). I got a BSOD during booting. stopcode INVALID KERNEL HANDLE. No driver was mentioned.
5) I pressed the reset button. Then, the second boot went OK and I got into windows (with verifier still turned on).
6) I turned verifier off through windows verifier, and rebooted.

7) Then I ran BETA collector and uploaded the DMP file:https://drive.google.com/open?id=1UG...29moRnIRRAZD2t