BSOD on computer after motherboard upgrade

OK, that's fine. But now you know how to get there and how to change it if you need to. Today wasn't a total loss. You learned something.

Enable driver verifier but first create a restore point. The link of how to create one is below. Then enable driver verifier. Sort the drivers by provider and enable all drivers NOT provided by Microsoft. Then use your computer any way you want and do anything you want to. It will seem kind of slow and sluggish. If there is anything that you do that usually causes a BSOD, do that often. Driver Verifier puts extra stress on the drivers, trying to make the computer crash. Hopefully, the driver causing problems will be caught. Keep it on for 24 hours of actual use. Again, there are no restrictions on what you can do. Run it as hard as you want. But, do keep an eye on the CPU temps.

   Warning

Be sure to create a Systm Restore point before proceeding further System Restore Point - Create

Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

What is Driver Verifier:
It puts stress on the drivers, and tries to make the faulty driver crash the computer. It is designed this way, to attempt to trap the offending driver.

What you will notice:
It will tend to make the computer rather slow and sluggish because the drivers are being stressed.

   Warning

Before enabling DV, make sure you have created a system restore point before enabling Driver Verifier. make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.

The screen shots look OK. I will just wait until you find the results of the test. After that we will enable Driver Verifier, but wait for the test to finish.

The link in the post tells you how to enable or disable it Driver Verifier - Enable and Disable

Here is the first BSOD

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck C4, {e1, fffff9800149efb8, 0, 0}
*** WARNING: Unable to verify timestamp for GUBootStartup.sys
*** ERROR: Module load completed but symbols could not be loaded for GUBootStartup.sys
Probably caused by : GUBootStartup.sys ( GUBootStartup+103c )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught.  This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arguments:
Arg1: 00000000000000e1, Synchronization object address is bogus or pageable.
Arg2: fffff9800149efb8, Synchronization object address.
Arg3: 0000000000000000
Arg4: 0000000000000000

That is GlarySoft - Glary Utilities Startup Manager Tool driver