You are not logged in.
Pages: 1
Hello. I've been using Arch for a few years now, but recently, after I switched to a new build, the screen would often blank without notice, and any interaction would be impossible. To clarify, there would be no signal to the screen, and the only way to continue operation would be to restart the computer. Occasionally, the screen would be relit, and there would be a possibility of either operability or inoperability.
This was especially problematic when initially installing Arch to the machine.
Most processes would keep running normally, evident from music playing through the audio jack. Sometimes, I would be able to reboot the computer through ssh.
If, during this period, I press the hard reset button on the case, there would be the possibility that, instead of normally restarting, the box would make one long beep, followed by three short beeps.
I have achieved uptimes of more than one week before, but sometimes this occurs multiple times in a day. I have cleaned out the inside of the case and refitted all of the parts, as well.
The crash logs, as seen in the provided screenshots below, report a "Parity error in prediction queue." I have searched for documentation of this error, but have not found any.
I have no definitive process for the reproduction of this crash. However, I have observed that running IntelliJ, Chromium, or other memory intensive processes make this more likely to occur. I would also say that Arch is most likely not the source of these errors.
Here are the relevant specifications:
AMD FX-8350 Black Edition Vishera 8-Core 4.0GHz (4.2GHz Turbo) Socket AM3+ 125W Desktop Processor
CORSAIR XMS 8GB 240-Pin DDR3 SDRAM DDR3 1600 (PC3 12800) Desktop Memory
ASUS M5A97 LE R2.0 AM3+ AMD 970 + SB950 SATA 6Gb/s USB 3.0 ATX AMD Motherboard with UEFI BIOS
PowerColor AX7870 2GBD5-2DHV2 Radeon HD 7870 GHz Edition 2GB 256-Bit GDDR5 PCI Express 3.0 x16 HDCP Ready CrossFireX Support Video Card
Here are two pictures of recent crashes.
http://i.j2.io/PSA2.jpg
http://i.j2.io/NYG0.jpg
Here is one from several weeks prior.
http://i.j2.io/U4Z5.jpg
Please help me find a solution. Thank you.
Offline
Looks like some sort of hardware issue. If you have overclocked your CPU or memory, I'd go back to stock for a while. If you have a couple of spare memory modules that you know are fine, I'd switch to them for a while too. The error mentions the L1 cache, so if you have any way of testing that CPU, I'd do it (put the CPU in another similar system, a spare CPU compatible with that motherboard, etc.)
Last edited by Pse (2014-08-20 20:29:42)
Offline
Pages: 1
