I was running 13w19a on the launcher 0.8.1 a few days ago without any problems on my Surface Pro with Windows 8. Between then and now, a Windows 8 update was pushed and I now receive the following error (as seen in the launcher):
Client> 265 recipes
Client> 27 achievements
Client> 2013-05-25 18:05:55 [CLIENT] [INFO] Setting user: reigalius
Client> 2013-05-25 18:05:55 [CLIENT] [INFO] (Session ID is 9163927269001428029)
Client> 2013-05-25 18:05:55 [CLIENT] [INFO] LWJGL Version: 2.9.0
Client> #
Client> # A fatal error has been detected by the Java Runtime Environment:
Client> #
Client> # EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x6a1fb60e, pid=6732, tid=6660
Client> #
Client> # JRE version: 7.0_21-b11
Client> # Java VM: Java HotSpot™ Client VM (23.21-b01 mixed mode windows-x86 )
Client> # Problematic frame:
Client> # C [ig7icd32.dll+0x3b60e]
Client> # Client> # Failed to write core dump. Minidumps are not enabled by default on client versions of Windows
Client> #
Client> # An error report file with more information is saved as:
Client> # C:\Users\Matt\AppData\Roaming\.minecraft\hs_err_pid6732.log
Client> #
Client> # If you would like to submit a bug report, please visit:
Client> # http://bugreport.sun...eport/crash.jsp
Client> # The crash happened outside the Java Virtual Machine in native code.
Client> # See problematic frame for where to report the bug.
Client> #
Client>
Client> [error occurred during error reporting , id 0xc0000005]
Client>
Game ended with bad state (exit code -1) Deleting C:\Users\Matt\AppData\Roaming\.minecraft\versions\13w21a\13w21a-natives-54810487235819 Couldn't delete C:\Users\Matt\AppData\Roaming\.minecraft\versions\13w21a\13w21a-natives-54810487235819 - scheduling for deletion upon exit
While it says that it will delete the folder upon exit, it does not. Manually deleting it is futile, as this runs immediately before the game tries to launch:
Unpacking natives to C:\Users\Matt\AppData\Roaming\.minecraft\versions\13w21a\13w21a-natives-54810487235819
I even tried clearing out my entire .minecraft folder to find the error persisted. I also enabled minidumps for BSOD to see if that would enable it for my client version of windows.
Looking around the web leads me to believe that the minidump error can be fixed by updating one's graphics drivers. However, I am running a Surface Pro with a custom Intel HD 4000; it is advised, on Intel's website, that anyone running custom graphics cards should not try to update manually.
Hi,
This looks like a driver issue (ig7icd32.dll). Try using the Intel Driver Update Utility to update your graphics drivers: http://www.intel.com.../support/detect
Unfortunately, the utility doesn't work for custom drivers; I tried it a couple of days ago.
EDIT:
Quote from java.com »
You have the recommended Java installed (Version 7 Update 21).
Quote from intel.com »
A customized computer manufacturer driver is installed on your computer. The Intel Driver Update Utility is not able to update the driver. Installing a generic Intel driver instead of the customized computer manufacturer driver may cause technical issues. Contact your computer manufacturer for the latest driver for your computer.
I'd really rather avoid Microsoft support on this if I can.
I just purchased Minecraft for my son on my Surface Pro. Same thing. Mostly. boisseaumr said he had it working, but after a MS update it stoppe. I haven't gotten this to work at all.
I'd be happy to toy with different drivers if this was a PC, but I'm opposed to the idea of tinkering with drivers on a Surface.
Any new updates to this thread are appreciated!!!!
Client> 27 achievements
Client> 2013-05-25 18:05:55 [CLIENT] [INFO] Setting user: reigalius
Client> 2013-05-25 18:05:55 [CLIENT] [INFO] (Session ID is 9163927269001428029)
Client> 2013-05-25 18:05:55 [CLIENT] [INFO] LWJGL Version: 2.9.0
Client> #
Client> # A fatal error has been detected by the Java Runtime Environment:
Client> #
Client> # EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x6a1fb60e, pid=6732, tid=6660
Client> #
Client> # JRE version: 7.0_21-b11
Client> # Java VM: Java HotSpot™ Client VM (23.21-b01 mixed mode windows-x86 )
Client> # Problematic frame:
Client> # C [ig7icd32.dll+0x3b60e]
Client> #
Client> # Failed to write core dump. Minidumps are not enabled by default on client versions of Windows
Client> #
Client> # An error report file with more information is saved as:
Client> # C:\Users\Matt\AppData\Roaming\.minecraft\hs_err_pid6732.log
Client> #
Client> # If you would like to submit a bug report, please visit:
Client> # http://bugreport.sun...eport/crash.jsp
Client> # The crash happened outside the Java Virtual Machine in native code.
Client> # See problematic frame for where to report the bug.
Client> #
Client>
Client> [error occurred during error reporting , id 0xc0000005]
Client>
Game ended with bad state (exit code -1)
Deleting C:\Users\Matt\AppData\Roaming\.minecraft\versions\13w21a\13w21a-natives-54810487235819
Couldn't delete C:\Users\Matt\AppData\Roaming\.minecraft\versions\13w21a\13w21a-natives-54810487235819 - scheduling for deletion upon exit
While it says that it will delete the folder upon exit, it does not. Manually deleting it is futile, as this runs immediately before the game tries to launch:
I even tried clearing out my entire .minecraft folder to find the error persisted. I also enabled minidumps for BSOD to see if that would enable it for my client version of windows.
Looking around the web leads me to believe that the minidump error can be fixed by updating one's graphics drivers. However, I am running a Surface Pro with a custom Intel HD 4000; it is advised, on Intel's website, that anyone running custom graphics cards should not try to update manually.
Any advice on getting around this nonsense?
This looks like a driver issue (ig7icd32.dll). Try using the Intel Driver Update Utility to update your graphics drivers: http://www.intel.com/p/en_US/support/detect
Stu
Unfortunately, the utility doesn't work for custom drivers; I tried it a couple of days ago.
EDIT:
I'd really rather avoid Microsoft support on this if I can.
I'd be happy to toy with different drivers if this was a PC, but I'm opposed to the idea of tinkering with drivers on a Surface.
Any new updates to this thread are appreciated!!!!