BardDoots

So, I have system that is rarely getting post. Here's the specs: MOBO: Asus M5A97 (Note: It's an AM3+ board, while the Athlon is AM3, but compatibility should be there.) CPU: Athlon II X4 640 Ram: Adata 2GB DIMM 1333MHz (Also tried some HyperX 4GB DIMMs but no difference.) GPU: I tried a GTX 1070, an RX 480 and an HD 7850, but they had zero difference PSU: Corsair VS650 (Also tried another PSU, no effect and them both run off of a UPS) So I built this system a few days ago and it posted fine. I installed Windows 7 on it and used it for a good 5 hours to install drivers and play around with it. Then after that day it has had problems booting. I updated the BIOS, tried other graphics cards. clearing CMOS now for around 40 times, nothing is helping, but around 10% of the time, it does boot and after boot it works perfectly. It once gave out a small puff of some smoke, I thought that was a last dying breath, but I've gotten it to boot 2 times after that. If I get through post and in to Windows, the system works perfectly. When the boot fails it just doesn't output anything, but fans keep spinning and nothing is else happening. Help me I'm losing my mind here.

Thanks man, but I intend to use the FX-4100 for a NAS (I know I guess kinda backwards) And I don't really want a whole new gaming system because I'll be moving to the US for a year as an exchange student and I can build a new mini-ITX PC over there with the parts being much cheaper. I just need a quick upgrade because it's just torture to use the FX-4100 daily. I can get the two Xeons and the MB for around $370

So I could get a couple of E5-2650 Xeons (Sandy Bridge) So they're on the LGA2011 socket and I was looking for a motherboard for them. I found this: Dell Precision GN6JF T5600. And the supported Graphics cards don't say anything recent, but it might just be outdated. Is it possible to know this in any way? I currently have an FX-4100 and I'm 100% sure this would be a better setup.

I forgot to say that I did run sfc /scannow, chkdsk and dxdiag but yielded no results.

So as the title says, My pc freezes for about 5-60 seconds around once per hour. The freezing problem usually occurs when I'm browsing and/or watching youtube/netflix. The PC doesn't completely freeze though, I can still scroll windows and usually the sound from netflix/youtube keeps playing but the sound of Spotify cuts off and if you try to load another browser page it can't do it. The bluescreen usually only happens when under gaming load and specifically DirectX API games. I tried playing Doom on Vulkan and OpenGL and the bluescreen wouldn't happen. I'll put some of the crash reports below. Googling only gives me responses like: Update faulty drivers, etc. How do I know what are the faulty ones though?? The troubleshooting steps that I've taken are: Done Windows Memory Diagnostic, Updated graphics drivers, ran stress tests to see that it wasn't an overheating issue. Here's the specs MB: AsRock Extreme4 970 AM3+ CPU: AMD FX-4100 (I know, I know.... I just really don't wanna upgrade since I'm going to be living in the US for a year and leaving in August so I don't wanna spend money and leave it here, I'd rather build a new one in the states.) RAM: 2x4GB GSkill 1333MHz (IIRC) and 2x4GB Kingston HyperX 1333MHz SSD: Kingston SATA3 SSDNow 480GB HDD: Seagate Barracuda 1TB 7200RPM GPU: Asus Dual OC GTX 1070 8GB PSU: LW-Power 650W (pls don't kill me) Other: I do have an optical drive to match the FX-era feel of old pc parts. Help is much appreciated, Thank you. Blue screen crash reports (from WhoCrashed): On Sat 20-May-17 01:45:36 your computer crashed crash dump file: C:\WINDOWS\memory.dmp This was probably caused by the following module: Unknown (0xFFFFB186F61B1E70) Bugcheck code: 0xFC (0xFFFFB186F61B1E70, 0x8A000004172009E3, 0xFFFFE481576D5890, 0x4) Error: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY Bug check description: This indicates that an attempt was made to execute non-executable memory. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. There is a possibility this problem was caused by a virus or other malware. A third party driver was identified as the probable root cause of this system error. Google query: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY On Thu 18-May-17 21:21:20 your computer crashed crash dump file: C:\WINDOWS\Minidump\051817-9031-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x16C310) Bugcheck code: 0xA (0x105CE, 0xFF, 0x6E, 0xFFFFF800B16474FB) Error: IRQL_NOT_LESS_OR_EQUAL file path: C:\WINDOWS\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. On Thu 18-May-17 00:11:19 your computer crashed crash dump file: C:\WINDOWS\Minidump\051817-9046-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x16C310) Bugcheck code: 0x93 (0x1C08, 0x0, 0x0, 0x0) Error: INVALID_KERNEL_HANDLE file path: C:\WINDOWS\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This bug check indicates that an invalid or protected handle was passed to The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. On Wed 17-May-17 20:18:02 your computer crashed crash dump file: C:\WINDOWS\Minidump\051717-11062-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x16C310) Bugcheck code: 0x109 (0xA39FC9621188BABA, 0xB3B6D5E8640A3819, 0x0, 0x18) Error: CRITICAL_STRUCTURE_CORRUPTION file path: C:\WINDOWS\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that the kernel has detected critical kernel code or data corruption. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.