Crashing with Windows 8.1 Pro

KaptainKrazy

Honorable
Aug 16, 2012
9
0
10,510
Hi, I'm having some problems with Windows. I recently did a clean install of Windows 8.1 Pro, along with replacing the CPU and motherboard in my system. Suddenly, however, a few a days afterwards, I opened Coretemp to look at the CPU temps and Windows stopped working, and this it what it said in the the event viewer right before the crash:
LiveComm (4008) C:\Users\Seth\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\LocalState\LiveComm\5639c096a4349a30\120712-0049\: A request to read from the file "C:\Users\Seth\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\LocalState\LiveComm\5639c096a4349a30\120712-0049\DBStore\livecomm.edb" at offset 3325952 (0x000000000032c000) for 8192 (0x00002000) bytes succeeded, but took an abnormally long time (16 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.

could someone point me in the right direction as to what part in my system might be faulty? Thanks in advance.
 
Solution
The Machine Check Exception error is an error that the CPU finds. It doesn't mean that the CPU is bad, but most times it means that there's either a low-level driver or a hardware problem (which includes compatibility).

The LiveComm error points at hardware (could be compatibility) also.
The registry error may or may not be significant here. I don't think that we'll gain anything by hunting down the faulting program(s) - and even that could be due to problems with compatibility.

Unfortunately, diagnosing compatibility issues is (IME) a matter of frustration level. By this I mean the random-seeming errors keep increasing your frustration level as does your repeated attempts to fix each and every one of the problems. Finally, after a...

Astroninjaben

Honorable
Jun 24, 2014
35
0
10,560
The Machine Check Exception error is an error that the CPU finds. It doesn't mean that the CPU is bad, but most times it means that there's either a low-level driver or a hardware problem (which includes compatibility).

The LiveComm error points at hardware (could be compatibility) also.
The registry error may or may not be significant here. I don't think that we'll gain anything by hunting down the faulting program(s) - and even that could be due to problems with compatibility.

Unfortunately, diagnosing compatibility issues is (IME) a matter of frustration level. By this I mean the random-seeming errors keep increasing your frustration level as does your repeated attempts to fix each and every one of the problems. Finally, after a lot of hard work and sweat you end up replacing the suspect parts out of desperation - and then, miraculously, your problems go away (not always - but that's been my experience)! It's probably a function of both your tolerance for frustration, and your troubleshooting of the assorted problems.

Good luck!
 
Solution