Weird Problems: Crit Process Died; LAN not detected; Graphical Errors in BIOS and Windows

ReaperTheMad

Reputable
Jun 10, 2014
9
0
4,510
System Configuration: Motherboard: AsRock Extreme4 CPU: Intel i5 3570k Memory: 32gb DDR3 1600 GPU: XFX R9 Fury X VBIOS: 113-C8800 100-101 Driver: Crimson 17.2.1 OS: Windows 10 Pro x64 (14393.693). No OC on anything, all factory settings.

PSU is only a few months old, 850w EVGA 80+ Gold. Ram is about 2 years old. Fury X is maybe a year old. Everything else is circa 2012-2013, including the boot drive (Samsung 840 Pro).

So I started getting Critical_Process_Error BSOD about two weeks ago. Random as best I can tell, but seemed to be common when running Microsoft Edge. (I'll include text from the CBS log at the bottom, as I'm not sure of a better way to format it).

Also, I've been noticing that it takes longer to detect my LAN (wired) when I boot. Sometimes, it doesn't detect it at all, but if I reboot, it detects it almost instantly.

Fast forward to today. I boot up, and in both the BIOS/boot screen and the welcome/login screen, the colors were all skewed and there were weird binary looking vertical lines every couple of inches or so. Rebooted, same thing. Rebooted again, color is normal, but no internet. Reboot again, everything is normal.

So what is going on? Multiple issues at once that just happened to start around the same time? Mobo? I'm lost at the moment.

CBS logs (I searched for "error"):

2017-02-23 23:41:31, Info CBS Archived backup log: C:\WINDOWS\Logs\CBS\CbsPersist_20170222214650.cab. 2017-02-23 23:41:31, Info CBS CAB compressed log file: C:\WINDOWS\Logs\CBS\CbsPersist_20170222214650.log 2017-02-23 23:41:31, Info CBS Failed compressing file C:\WINDOWS\Logs\CBS\CbsPersist_20170222214650.log [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND] 2017-02-23 23:41:31, Info CBS Failed compressing log file C:\WINDOWS\Logs\CBS\CbsPersist_20170222214650.log [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND] 2017-02-23 23:41:37, Info CBS Archived backup log: C:\WINDOWS\Logs\CBS\CbsPersist_20170223224541.cab. 2017-02-23 23:41:37, Info CBS CAB compressed log file: C:\WINDOWS\Logs\CBS\CbsPersist_20170223224541.log 2017-02-23 23:41:37, Info CBS Failed compressing file C:\WINDOWS\Logs\CBS\CbsPersist_20170223224541.log [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND] 2017-02-23 23:41:37, Info CBS Failed compressing log file C:\WINDOWS\Logs\CBS\CbsPersist_20170223224541.log [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND] 2017-02-23 23:41:37, Info CBS Failed archiving backup logs [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND] 2017-02-23 23:41:37, Info CBS Failed archiving backup logs [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2017-02-24 23:10:01, Info CBS Session: 30576413_151539475 initialized by client WindowsUpdateAgent, external staging directory: (null), external registry directory: (null 2017-02-24 23:10:01, Info CBS Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE] 2017-02-24 23:10:01, Info CBS Failed to OpenPackage using worker session [HRESULT = 0x800f0805] 2017-02-24 23:10:01, Info CBS Session: 30576413_151564497 initialized by client WindowsUpdateAgent, external staging directory: (null), external registry directory: (null 2017-02-24 23:10:01, Info CBS Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE] 2017-02-24 23:10:01, Info CBS Failed to OpenPackage using worker session [HRESULT = 0x800f0805] 2017-02-24 23:10:03, Info CBS WU creates the package, AppID:UpdateOrchestrator, UpdateID:{92EC2FD0-E6D7-4983-9685-02789AFB5C86}, revision: 201
 
Solution
You may have hardware damage or a bad capacitor somewhere on your board or something may be going on with the BIOS. In order to make sure that all those issues aren't BIOS related, try resetting the CMOS and updating the BIOS if you don't already have the latest version. That way you may fix all those issues. If you don't then I'm afraid that your board is probably bad and the situation is going to get worse by time.
You may have hardware damage or a bad capacitor somewhere on your board or something may be going on with the BIOS. In order to make sure that all those issues aren't BIOS related, try resetting the CMOS and updating the BIOS if you don't already have the latest version. That way you may fix all those issues. If you don't then I'm afraid that your board is probably bad and the situation is going to get worse by time.
 
Solution