BSOD clock_watchdog_timeout

Do you still need help with this?

If so, the first thing to do is uninstall the software and see if that makes a difference. If not then remove the new ram and see if that helps. If it does then swap in one of the new ram modules in place of one of the old ones and see what happens. Continue testing till you find the one causing the problem.

I can't see testing all the ram as it would take a couple days to test 32GB. Swapping and testing the ram is a better method in your case I think.

THe last dump only shows 16GB of ram, when did you add the additional 16GB, before or after the BSODs occurred?

Run dm_log_collector again and upload the zip file. Let's see if any new dump was saved.

One new dump:

Code:

BugCheck 7F, {8, ffff8280938b7b30, ffff8280938ddb20, fffff800cd0602f7}

*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption

Followup:     memory_corruption
---------

Code:

UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault).  The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
        use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
        use .trap on that value
Else
        .trap on the appropriate frame will show where the trap was taken
        (on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: ffff8280938b7b30
Arg3: ffff8280938ddb20
Arg4: fffff800cd0602f7

Almost surely defective RAM. Try the RAM swap and test process I mentioned in my earlier post to identify the one (or two but probably one) module causing the problem.

We recommend running memtest86+ but with 32GB of ram as I said, it would take several days to run a 8 passes which is the minimum recommended for a thorough test. If you want, you can remove the old ram and install the new ram then run memtest86+ overnight and see what it shows:
===================================================
Follow this tutorial: MemTest86+ - Test RAM - Windows 10 Forums

MemTest86+ is a diagnostic tool designed to test Random Access Memory (RAM) for faults. MemTest86+ will verify that:

• RAM will accept and keep random patterns of data sent to it
• There are no errors when different parts of memory try to interact
• There are no conflicts between memory addresses

Memtest86+ runs from bootable media to isolate the RAM from the system, no other components are taken into account during the test.

   Warning

MemTest86+ needs to run for at least 8 passes to be anywhere near conclusive, anything less will not give a complete analysis of the RAM.

If you are asked to run MemTest86+ by a Ten Forums member make sure you run the full 8 passes for conclusive results. If you run less than 8 passes you will be asked to run it again.

   Note

MemTest86+ has been known to discover errors in RAM in later passes than the eighth pass. This is for information only; if you feel there is a definite problem with the RAM and 8 passes have shown no errors feel free to continue for longer.

Running 8 passes of MemTest86+ is a long and drawn out exercise and the more RAM you have the longer it will take. It's recommended to run MemTest86+ just before you go to bed and leave it overnight.

Take a picture when done and post in the forum please.