![]() ![]() Something (presumably a software and not a hardware change) has caused this issue but, since I am only blessed in the ability to program Python and some C++, these stack traces are rather meaningless to me. I'm running windows 8 (not 8.1) and have been able to play Minecraft for around 4 and a half months before this error appeared. ![]() My PC quite often suffers from BSOD's relating to PAGE_FAULT_IN_NONPAGED_AREA and also several INTERNAL_POWER_ERROR(see my question on superuser for more detailed info about the Blue screens.The full error log regarding the more common issue can be found here as the whole thing was too large to put into the question.# If you would like to submit a bug report, please visit: Minidumps are not enabled by default on client versions of Windows # j .(Ljava/lang/String Ljava/lang/String [B)[B+289 # Java VM: Java HotSpot(TM) 64-Bit Server VM (24.55-b03 mixed mode windows-amd64 compressed oops) # A fatal error has been detected by the Java Runtime Environment: Spinpoint M8 ST500LM012 HN-M500MBB (Looking to replace).My PC is less that 5 months old so I see this is not a problem. Using several driver update programs, I find none with updates. I have upgraded to Java 8, downgraded back to 7. My error is, as mentioned in the title, an EXCEPTION_ACCESS_VIOLATION that is thrown whenever I start up any form of Minecraft (Vanilla, modded, multiplayer.). I understand that there are questions related to this subject already on the site but I feel mine is different as I have a different problematic frame etc. So if you too have this error and cannot find any solution, its probably hardware. Either way, I replaced my RAM and now it works. I ran Memtest, and I can't remember the number of errors but it was worryingly high. Sadly I was trying to avoid this as my PC was only 4 months old, but there was nothing I could do. I have just realised that this question has become somewhat well viewed (+10,000 views), so I thought I better update it again and say that I have solved the issue. ![]()
0 Comments
Leave a Reply. |