Advertisement
Guest User

Untitled

a guest
Sep 5th, 2013
67
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 1.38 KB | None | 0 0
  1. Client> #
  2. Client> # A fatal error has been detected by the Java Runtime Environment:
  3. Client> #
  4. Client> # EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x690edb84, pid=2544, tid=2476
  5. Client> #
  6. Client> # JRE version: 7.0_25-b17
  7. Client> # Java VM: Java HotSpot(TM) Client VM (23.25-b01 mixed mode, sharing windows-x86 )
  8. Client> # Problematic frame:
  9. Client> # C [atioglxx.dll+0xedb84] atiPPHSN+0x35d54
  10. Client> #
  11. Client> # Failed to write core dump. Minidumps are not enabled by default on client versions of Windows
  12. Client> #
  13. Client> # An error report file with more information is saved as:
  14. Client> # C:\Documents and Settings\Pete\Application Data\.minecraft\hs_err_pid2544.log
  15. Client> #
  16. Client> # If you would like to submit a bug report, please visit:
  17. Client> # http://bugreport.sun.com/bugreport/crash.jsp
  18. Client> # The crash happened outside the Java Virtual Machine in native code.
  19. Client> # See problematic frame for where to report the bug.
  20. Client> #
  21. Client> AL lib: (EE) alc_cleanup: 1 device not closed
  22. Game ended with bad state (exit code 1073807364)
  23. Ignoring visibility rule and showing launcher due to a game crash
  24. Deleting C:\Documents and Settings\Pete\Application Data\.minecraft\versions\1.6.2\1.6.2-natives-335599488248
  25. Couldn't delete C:\Documents and Settings\Pete\Application Data\.minecraft\versions\1.6.2\1.6.2-natives-335599488248 - scheduling for deletion upon exit
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement