i'm struggling with this problem where my ubuntu system (formerly BSODdding windows 7) is unstable.
I decided to perform several memtest runs and on 2 out of 4 I had errors. The first one happened on the first run
Then, since I've 4x4GB RAM sticks i perfomed these actions
- removed A+B and tested C+D - no errors
- replaced C+D with A+B - no errors
- moved A+B in the other 2 RAM slots in my MOBO - no errors
- replaced A+B with C+D - no errors
Hence i re-tried to test A+B+C+D (all positioned in their old slots) and memtest passed several runs across the 14hours i let the test running.
At this point I knew something was wrong but I had no time to perform other tests until a couple of days ago where I ran memtest for 12+hours without any errors.
I decided then to run it again yesterday overnight and when I woke up I found memtest showing this:
As you can see the test giving error is #10 on both failing runs. Now I really don't know what to do and I'm probably misreading memtest results too.
OTHER Infos
My PC is composed by the following components:
- CPU: Intel Core i7-3770
- MOBO: ASUSTeK MAXIMUS V FORMULA Versione Rev 1.XX
- RAM: 4x4GB Corsair Vengeance CMZ16GX3M4A1600C9
I'm experiencing several Google Chrome Crashes along as Java crashes both during compilation and software usage (Intellij IDEA). It's worth mentioning that a laptop I own with the same software installed never (ever) crashes on java (both during compile-time and IDEA regular usage).
Also, sometimes, regular ubuntu applications such as FileManager crashes showing the beautiful "Ubuntu experienced an internal error" dialog.
I, a few times, tried to look into the java crash log and google it but I never came across anything letting me validate my thinking that this might be an hardware fault.
The Java crashes becomes more frequent (with a "max" of one crash every 2 mins) when the PC is powered-on for a long time (probably cause i've several chrome -sucking ram- tabs open???). Performing a sudo echo 3 | sudo tee /proc/sys/vm/drop_caches
(clear ram cache) seems to delay next crash event.