Windows 10 Been crashing for months cant figure out why

  • Thread starter Thread starter GagneWest
  • Start date Start date
G

GagneWest

Hi I have been having a problem since mid October now, I have been to several forums gotten into contact with AMD and noone has been able to help this far. I had recently upgrade a few components in my pc being my Motherboard, CPU and RAM. Started with a clean install of windows but soon after I started to notice crashing I don't get bluescreens my computer just dies and turns back on right away. So I tried a bunch of fixes when I noticed this was not a 1 off deal and it kept happening. People were telling me it was my ram I ran windows memtest and memtest86 no errors, still not convinced I even replaced the ram. Soon after the subject changed to it being my PSU so I swapped that to I upgraded from a 450W to a 750W, still crashing after. Temps all look fine, I stress tested my pc and the temps all hover around 80 but max thermal is around 95 so I shouldn't be having a problem there. I performed CMOS on my bios, still crashing. I reinstalled gpu drivers multiple times by wiping it with DDU and fresh installing. I am starting to get a little frustrated so I will leave some error codes I have been getting in hopes that someone who is good with computers can help me diagnose this problem.


My Current Build

GPU - GTX 1060 3GB

RAM - Corsair Vengeance 3600MHZ C18

PSU - Modular 80+ Bronze 750W

Mobo - ASUS Prime X570-P

CPU - Ryzen 5 3600x (with stock cooler)


Some of the errors and dumps I have been getting.


A fatal hardware error has occurred.



Reported by component: Processor Core

Error Source: Machine Check Exception

Error Type: Cache Hierarchy Error

Processor APIC ID: 0



The details view of this entry contains further information.


My dumps conflicting files


- ntoskrnl.exe ntoskrnl.exe+44f5ae fffff807`04e00000 fffff807`05e46000 0x01046000 0xed9dc31e 2096-04-29 7:01:34 AM

- dxgmms2.sys dxgmms2.sys+a7a05 fffff801`35b10000 fffff801`35bf1000 0x000e1000 0x81055c4e 2038-08-05 4:09:34 AM

-ntoskrnl.exe ntoskrnl.exe+2de1f7 fffff801`26c00000 fffff801`27c46000 0x01046000 0xed9dc31e 2096-04-29 7:01:34 -watchdog.sys watchdog.sys+3ad0 fffff801`351b0000 fffff801`351c8000 0x00018000 0x4493508b 2006-06-16 7:44:59 PM

Continue reading...
 
Back
Top