Question Random BSODs/Windows 10 Freezing for months - Can't get to the bottom of it


May 2, 2009
Since building my PC back in February, I have been getting random BSODs which for the life of me I can't figure out why are they happening nor when. They seem totally random and I can't reproduce them on demand. They can occur daily, weekly, or even bi-weekly. Sometimes they produce a mini/full dump, sometimes (quite often) they do not. Driver Verifier seems to not make any difference nor did it help with my diagnostics.

Some of the BSODs I've seen are:
I've tried all the usual stuff (upgrade firmware, drivers, memtests, fresh Windows installs, you name it) but still can't get to the bottom of it. I even had my RAM replaced (as I thought that was the issue) but BSODs still happen with my new RAM. Some drivers at this point in time might not be up-to-date (as indicated in the mini/full dumps), but no changelog indicated fixes for BSODs, so I doubt that'll help. Nevertheless, I'm in the process of updating everything (again) and will update with new BSOD dumps. Also, please note this is a custom waterloop build, so it's quite hard removing/replacing components.

I will include a number of diagnostic files, mini-dumps and dumps below (Google Drive Links) but if you need any more information, please let me know and I will provide them ASAP. You might notice a few 'big' gaps between the dates - that's because I was away and PC was turned off completely.

Full System Specification
System Information \(.nfo\)

Date | V2 Collector File | Mini-Dump | Full Memory Dump | Comments
28-Apr-2019 | N/A | link| N/A|
01-May-2019 | N/A| link| N/A|
02-May-2019 | N/A| link| N/A|
03-May-2019 | N/A| link| N/A|
04-May-2019| N/A | link| N/A|
06-May-2019| N/A | link| N/A|
27-May-2019| N/A | link| N/A|
30-May-2019| N/A | link| N/A|
18-Jun-2019| N/A | link| N/A|
20-Jun-2019|link|N/A|N/A| No dump was generated
24-Jun-2019|link|N/A|N/A|No dump was generated
30-Jun-2019|link|N/A|N/A|No dump was generated
01-Jul-2019|link|N/A|N/A|No dump was generated
01-Jul-2019|link|N/A|N/A|No dump was generated
01-Jul-2019|link|N/A|N/A|No dump was generated
02-Jul-2019| link | link| N/A|
03-Jul-2019| link| N/A| N/A|
03-Jul-2019| link| N/A| N/A|
03-Jul-2019| link| N/A| N/A|
16-Jul-2019| N/A | link| N/A|
21-Jul-2019| link| N/A| link and link|
04-Aug-2019| link | link| link|
11-Aug-2019| link | link| link|
03-Sep-2019| link | N/A | N/A|
16-Sep-2019| link | link| N/A|
20-Sep-2019| N/A | link| N/A|
06-Oct-2019| link | N/A | N/A| No dump generated. Got stuck at 0% on BSOD Screen at "Collecting Further Information"
06-Oct-2019 NEW | link | link | link | Driver Verifier ON - BSOD on Windows start-up screen

A folder with every diagnostic data I have accumulated can be found here

All help is appreciated. I'm clutching at straws here and getting really frustrated with the whole ordeal
Last edited:


Win 10 Master
Bug Check 0x1CA: SYNTHETIC_WATCHDOG_TIMEOUT - I seen a lot of BSOD and not seen this one before.

I will get a friend to convert dumps.

was system info.nfo meant to be a sound file? seems google is confused
Last edited:


Hi, I ran the dump files through the debugger and got the following information:
File information:100619-5093-01.dmp (Oct 6 2019 - 05:17:18)
Driver warnings:*** WARNING: Unable to verify timestamp for ctxusbm.sys
Probably caused by:ntkrnlmp.exe (Process: System)
Uptime:0 Day(s), 0 Hour(s), 00 Min(s), and 08 Sec(s)

File information:092019-7703-01.dmp (Sep 19 2019 - 19:40:04)
Probably caused by:memory_corruption (Process: dwm.exe)
Uptime:3 Day(s), 6 Hour(s), 18 Min(s), and 58 Sec(s)

File information:091619-6500-01.dmp (Sep 16 2019 - 06:37:21)
Probably caused by:memory_corruption (Process: Receiver.exe)
Uptime:5 Day(s), 4 Hour(s), 10 Min(s), and 42 Sec(s)

File information:081119-6187-01.dmp (Aug 9 2019 - 14:32:55)
Probably caused by:memory_corruption (Process: bplus.wtk2.exe)
Uptime:5 Day(s), 6 Hour(s), 08 Min(s), and 29 Sec(s)

File information:080419-6062-01.dmp (Aug 4 2019 - 08:22:32)
Probably caused by:ntkrnlmp.exe (Process: firefox.exe)
Uptime:0 Day(s), 0 Hour(s), 38 Min(s), and 09 Sec(s)

File information:071619-6140-01.dmp (Jul 14 2019 - 15:21:31)
Probably caused by:memory_corruption (Process: bplus.wtk2.exe)
Uptime:0 Day(s), 20 Hour(s), 24 Min(s), and 36 Sec(s)

File information:070219-7687-01.dmp (Jul 2 2019 - 14:56:50)
Driver warnings:*** WARNING: Unable to verify timestamp for nvlddmkm.sys
Probably caused by:memory_corruption (Process: csrss.exe)
Uptime:0 Day(s), 0 Hour(s), 08 Min(s), and 05 Sec(s)
The nvlddmkm.sys file is a NVIDIA graphics card driver. There are a few things you can do to fix this problem. First off, try a full uninstall using DDU in Safe Mode then re-install the driver (more information). Or try getting the latest version of the driver. Or try one of the 3 most recent drivers released by NVIDIA. Drivers can be found here: or you can allow Windows Update to download the driver for you, which might be a older/better version.

Possible Motherboard page:
You've recently updated to the latest BIOS.

This information can be used by others to help you. I can't help you with this. Someone else will post with more information. Please wait for additional answers. Good luck.

PC Tailor

@gardenman the 2 drivers that are blank on that list are both Google Drive File Stream/Sync Drivers - which I'm certain you already guessed :) !

- One of your dumps shows ctxusbm immediately before a crash and also fails to load symbols correctly so I'd be looking at that initially:
Jan 26 2018ctxusbm.sysCitrix USB Filter Driver

  • As GM has stated, nvlddmkm+0x123170 appears also in another. So probably best follow his advice and clean install those GPU drivers or roll back to the previous version, latest NV drivers have caused some issues.
  • I'd also be tempted to run HD Sentinel just to see if there is anything obvious with storage drives.
  • Did you buy 2 packs of 16GB RAM modules? So your 32GB were not from the same pack? (Same model is irrelevant). If so this could cause an issue. What RAM exactly did you replace?
Reactions: gardenman


Win 10 Master
Gardenman in middle of reconstructing his room , he might explain that to you... As such he running off a laptop and can't update ADA or he would add those drivers. The driver names are a bit of a give away

I hate the new Nvidia drivers. Almost at stage that if I see the Sept drivers I should auto suggest DDU

I have never seen a motherboard remember the last 3 BIOS versions its had installed before
  • VENDOR: American Megatrends Inc.
  • VERSION: 1302
  • DATE: 09/02/2019
  • VERSION: 1105
  • DATE: 06/06/2019
  • VERSION: 1005
  • DATE: 04/10/2019
and yet yours does.

Nvidia drivers probably caused the Unexpected Kernel Mode Trap as well, given it crashed dwm.exe which is the Windows Desktop Manager, and often a victim of GPU drivers.
Reactions: PC Tailor