Microsoft used to release a "checked" build for each version of Windows on MSDN/Visual Studio Subscription downloads. [1] This was a build with the same compiler optimization settings as the release build, but with debug-build-only assertions and checks included. In the checked build kernel, the system uptime had 49 days artificially added to it [2], precisely to help developers find out problems like this.

At one point when I was on the Windows team at Microsoft, there was an internal push for us to selfhost (dogfood) checked builds of Windows, since they theoretically provided better bug telemetry than "free" builds (release builds, which are free of debug-only code). "Slows your dev box down by just half!" was the basic pitch of that campaign in a nutshell.

[1] I don't know if this was ever done for Windows 95. It was done for Windows XP up to Windows 10 version 1511, but it appears to have stopped since then, at least according to my quick search.

[2] https://docs.microsoft.com/windows/win32/api/sysinfoapi/nf-s...