BSOD error 0x000000124

crashed again

This crash is quite different from the others and was caused by Driver Verifier being turned on (why did you do this?). Driver verifier has determined that a driver is misbehaving and reported it. The stack shows the driver.

Code:

STACK_TEXT:  
ffff8a80`852271e8 fffff802`ee6ce443 : 00000000`000000c4 00000000`00002000 fffff808`43be38c4 00000000`00000000 : nt!KeBugCheckEx
ffff8a80`852271f0 fffff802`ee15849b : fffff802`ee24d170 00000000`00002000 fffff808`43be38c4 00000000`00000000 : nt!VerifierBugCheckIfAppropriate+0xdf
ffff8a80`85227230 fffff802`ee6c63fc : 00000000`53694558 fffff802`ee24d170 fffff808`43be38c4 00000000`00000000 : nt!VfReportIssueWithOptions+0x103
ffff8a80`85227280 fffff802`ee6c44a3 : 00000000`00000000 00000000`00000004 00000000`00000026 00000000`00000000 : nt!VfCheckPoolType+0x90
ffff8a80`852272c0 fffff808`43be38c4 : 00000000`00000220 00000000`00000000 00000000`00000000 fffff802`ee1a3040 : nt!VerifierExAllocatePoolWithTag+0x53
ffff8a80`85227310 00000000`00000220 : 00000000`00000000 00000000`00000000 fffff802`ee1a3040 ffff8a80`00000080 : SiUSBXp+0x38c4
ffff8a80`85227318 00000000`00000000 : 00000000`00000000 fffff802`ee1a3040 ffff8a80`00000080 ffffe182`20a61100 : 0x220

This driver is from Silicone Labs USBXpress Development Kit - if you no longer use it then you should uninstall it or remove it.

Do not use Driver Verifier for more than 48 hours and if it does not cause any other BSOD you should turn it off and then continue to operate your system without overclocking as I suggested earlier.

I run Driver Verifier but just kept rebooting and went to safe mode to close it so didn't think it worked sorry about that I do have o/c off cpu and ram and cleared cmos on jumper.
the only USBXpress I found on device manager was Corsair USBXp Driver its for my H100i cooler and I did open hidden drivers and cant find Silicone Labs USBXpress Development Kit on device manager but did find in drivers file with silicon labs 1-25-2018 SiLib.sys and SiUSBXp.sys same date 1-25-2018 it also has sisraid2.sys an sisraid4.sys 4-15-2018 should I just delete all these drivers? (I put this PC together in Febuary 2018 plus reinstalled clean windows at least 3 times trying stop bsod)

sorry for being pain but do appreciate all the help

crashed earlier checked blue screen app same as before

It's possible that driver names can be reused by other manufacturers, if you have found the Corsair device and it specifies the driver as SiUSBXp then that is the only one you need to update.

The new crash is back to the hardware 0x124 bugcheck with the internal timer error.

Your RAM clock speeds are lower now:

Code:

BankLabel            : BANK 1
DeviceLocator        : ChannelA-DIMM1
Manufacturer         : 029E
Capacity             : 8589934592
ConfiguredClockspeed : 2133
ConfiguredVoltage    : 1200
SerialNumber         : 00000000
PartNumber           : CMK16GX4M2B3000C15  

BankLabel            : BANK 3
DeviceLocator        : ChannelB-DIMM1
Manufacturer         : 029E
Capacity             : 8589934592
ConfiguredClockspeed : 2133
ConfiguredVoltage    : 1200
SerialNumber         : 00000000
PartNumber           : CMK16GX4M2B3000C15

If you continue to get problems then I suggest you start to look at CPU hardware tests:

 CPU TEST

Run Prime95 to stress test your CPU. Prime95 - Stress Test Your CPU - Windows 10 Forums

   Warning

Your CPU temperatures will rise quickly while under this stress test. Keep a keen eye on them and abort the test if overheating occurs.

I ran Prime95 3:08 FFTs maximum heat
played a game virtual pool 4 and run video show while running

Howiewowie said:

I ran Prime95 3:08 FFTs maximum heat
played a game virtual pool 4 and run video show while running

sorry thought picture was to big made it smaller

seems to crash more now could it be the motherboard?

Howiewowie said:

seems to crash more now could it be the motherboard?

I can't rule the motherboard out but it is too soon to condemn the hardware yet. One good test is to leave the system running in safe mode for a day or two and see if you still get a crash - this is good confirmation that it is hardware.

ran 2 1/2 days safe mode no crash

Howiewowie said:

ran 2 1/2 days safe mode no crash

In that case I do wonder if there might be a software or driver problem. The usual way to track this down is to use a clean boot (turns off the non-Microsoft programs or services) and verify that the crash does not occur. Then you can start to add back in programs and services a few at a time until you once again start getting the crashes. By a process of elimination you can work out which program or service it is that triggers the crash. The full tutorial for doing this type of investigation is shown below:
Perform a Clean Boot in Windows 10 to Troubleshoot Software Conflicts