techsupport Motherboard failure?

[sharpblve1]

So i think i have done everything.

I have updated my BIOS,Gpu driver.

Checked CHKDSK , Temps,Ram

 

Bluescreen Stope Codes I have gotten: SYSTEM_SERVICE_EXPETION, IRQL_NOT_LESS_OR_EQUAL, KMODE_EXPETION_NOT_HANDLED, DPC_Watchdog_Violation

 

Specs:

CPU: AMD Fx6300

MotherBoard: MSI 970A-G46

GPU: NVIDIA GeForce GTX 1050 Ti

Storage: KINGSTON SSD 120gb, Western Digital WDC HDD 600gb

RAM: Corsair Vengence 16gb

GPU SSD RAM and PSU is new.

 

I think it is caused by the motherboard because before my ownership of this pc its motherboard had reach a little bit over 100 °C .

[Applefreak]

7 minutes ago, sharpblve1 said:

So i think i have done everything.

I have updated my BIOS,Gpu driver.

Checked CHKDSK , Temps,Ram

 

Bluescreen Stope Codes I have gotten: SYSTEM_SERVICE_EXPETION, IRQL_NOT_LESS_OR_EQUAL, KMODE_EXPETION_NOT_HANDLED, DPC_Watchdog_Violation

 

Specs:

CPU: AMD Fx6300

MotherBoard: MSI 970A-G46

GPU: NVIDIA GeForce GTX 1050 Ti

Storage: KINGSTON SSD 120gb, Western Digital WDC HDD 600gb

RAM: Corsair Vengence 16gb

GPU SSD RAM and PSU is new.

 

I think it is caused by the motherboard because before my ownership of this pc its motherboard had reach a little bit over 100 °C .

That's extreme but should not cause the board to fail. I'd tipp on driver issues. Best to format and install a fresh copy of the os in question and then get the latest drivers.Also check if the bios can still save settings and shows the proper time you have set. If not, replace the CMOS battery, it should be a CR2032 round cell.

[sharpblve1]

Did all that and still freezes, it also makes a buzzing sound if that helps.

[sharpblve1]

4 hours ago, sharpblve1 said:

Did all that and still freezes, it also makes a buzzing sound if that helps.

Found also in Event viewer application: taskhostw (4956,D,0) WebCacheLocal: A request to write to the file "C:\Users\Sharp\AppData\Local\Microsoft\Windows\WebCache\WebCacheV01.jfm" at offset 0 (0x0000000000000000) for 8192 (0x00002000) bytes succeeded, but took an abnormally long time (36 seconds) to be serviced by the OS. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.

[sharpblve1]

@Applefreak