-
Bug
-
Resolution: Duplicate
-
None
-
1.16.1
-
None
-
--------------- S Y S T E M ---------------
OS: Windows 10.0 , 64 bit Build 18362 (10.0.18362.959)
CPU:total 4 (2 cores per cpu, 2 threads per core) family 6 model 142 stepping 9, cmov, cx8, fxsr, mmx, sse, sse2, sse3, ssse3, sse4.1, sse4.2, popcnt, avx, avx2, aes, clmul, erms, 3dnowpref, lzcnt, ht, tsc, tscinvbit, bmi1, bmi2, adx
Memory: 4k page, physical 4067556k(385160k free), swap 14565460k(3362080k free)
vm_info: Java HotSpot(TM) 64-Bit Server VM (25.51-b03) for windows-amd64 JRE (1.8.0_51-b16), built on Jun 8 2015 18:03:07 by "java_re" with MS VC++ 10.0 (VS2010)
time: Sat Jul 25 23:27:51 2020
elapsed time: 195 seconds (0d 0h 3m 15s)--------------- S Y S T E M --------------- OS: Windows 10.0 , 64 bit Build 18362 (10.0.18362.959) CPU:total 4 (2 cores per cpu, 2 threads per core) family 6 model 142 stepping 9, cmov, cx8, fxsr, mmx, sse, sse2, sse3, ssse3, sse4.1, sse4.2, popcnt, avx, avx2, aes, clmul, erms, 3dnowpref, lzcnt, ht, tsc, tscinvbit, bmi1, bmi2, adx Memory: 4k page, physical 4067556k(385160k free), swap 14565460k(3362080k free) vm_info: Java HotSpot(TM) 64-Bit Server VM (25.51-b03) for windows-amd64 JRE (1.8.0_51-b16), built on Jun 8 2015 18:03:07 by "java_re" with MS VC++ 10.0 (VS2010) time: Sat Jul 25 23:27:51 2020 elapsed time: 195 seconds (0d 0h 3m 15s)
-
Unconfirmed
-
(Unassigned)
when ever i tab back to minecraft after checking discord minecraft crashes
#
- A fatal error has been detected by the Java Runtime Environment:
# - EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x00007ff8b7452380, pid=11492, tid=9388
# - JRE version: Java(TM) SE Runtime Environment (8.0_51-b16) (build 1.8.0_51-b16)
- Java VM: Java HotSpot(TM) 64-Bit Server VM (25.51-b03 mixed mode windows-amd64 compressed oops)
- Problematic frame:
- C [ig9icd64.dll+0x12380]
# - Failed to write core dump. Minidumps are not enabled by default on client versions of Windows
# - If you would like to submit a bug report, please visit:
- http://bugreport.java.com/bugreport/crash.jsp
- The crash happened outside the Java Virtual Machine in native code.
- See problematic frame for where to report the bug.
- duplicates
-
- Resolved