BSOD playing minecraft (problem come from ntoskrnl.exe)

[biggs223]

Hello, i recently started to play minecraft again (ftb monster to be precise) but i get BSOD after playing for an extended period of time (often 1 or 2 hour). I attached the 2 dump file to this post.
I would also like to know if java can be the cause of this because i recently updated it and i think it began to bug the same day.
Thank you.
Have a good day.

EDIT : if it has an importance i use japanese language for non unicode programs because i play many touhou game

 

[Arc]

Hi biggs223.

Install Intel® Iris™ and HD graphics Driver for Windows* 7.

Also, Is the computer hot while it is crashing? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy. Alternatively, you can publish a Speccy snapshot too: http://www.sevenforums.com/tutorials/311593-speccy-publish-snapshot-your-system-specs.html .

Let us know the results.
________________________________

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {0, 2, 0, fffff800030e1e52}

Probably caused by : dxgmms1.sys ( dxgmms1!VidMmiProcessTerminationCommand+5f )

Followup: MachineOwner
---------

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff800030e1e52, address which referenced memory

Debugging Details:
------------------


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003313100
GetUlongFromAddress: unable to read from fffff800033131c0
 0000000000000000 Nonpaged pool

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KiSignalSynchronizationObject+42
fffff800`030e1e52 488b3f          mov     rdi,qword ptr [rdi]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

TRAP_FRAME:  fffff8800853a8c0 -- (.trap 0xfffff8800853a8c0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000002 rbx=0000000000000000 rcx=fffff880009c0180
rdx=fffffa800ac13b40 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800030e1e52 rsp=fffff8800853aa50 rbp=0000000000000000
 r8=0000000000000000  r9=fffffa800a428c40 r10=fffffa800a428c40
r11=fffff8800853aae0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz ac po cy
nt!KiSignalSynchronizationObject+0x42:
fffff800`030e1e52 488b3f          mov     rdi,qword ptr [rdi] ds:00000000`00000000=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800030db169 to fffff800030dbbc0

STACK_TEXT:  
fffff880`0853a778 fffff800`030db169 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`0853a780 fffff800`030d9de0 : 00000000`00000000 00000000`00000000 fffff8a0`06f728f8 fffffa80`0ac13b48 : nt!KiBugCheckDispatch+0x69
fffff880`0853a8c0 fffff800`030e1e52 : fffffa80`0ac13ad0 fffffa80`0a3f8010 00000000`00000000 fffffa80`0aa12570 : nt!KiPageFault+0x260
fffff880`0853aa50 fffff800`030e0256 : 00000000`00000000 fffff880`101921d8 00000000`00000000 fffffa80`0a3f8010 : nt!KiSignalSynchronizationObject+0x42
fffff880`0853aaa0 fffff880`101a247f : fffffa80`00000000 00000000`00000000 fffffa80`0b569a00 fffff880`0853ab60 : nt!KeSetEvent+0x106
fffff880`0853ab10 fffff880`101c02e9 : fffffa80`00000000 fffffa80`0a3f8010 00000000`6d4d6956 fffff880`00000174 : dxgmms1!VidMmiProcessTerminationCommand+0x5f
fffff880`0853ab60 fffff880`101bf574 : fffff880`033b8f40 fffffa80`0b805c00 00000000`00000000 fffffa80`0a3f8010 : dxgmms1!VidSchiSubmitDeviceCommand+0x39
fffff880`0853ab90 fffff880`101bf012 : 00000000`00000000 fffffa80`0b805c00 00000000`00000080 fffffa80`0a3f8010 : dxgmms1!VidSchiSubmitQueueCommand+0xb0
fffff880`0853abc0 fffff800`0337773a : 00000000`023db5d3 fffffa80`0a427610 fffffa80`0516b740 fffffa80`0a427610 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`0853ac00 fffff800`030cc8e6 : fffff880`033b4180 fffffa80`0a427610 fffff880`033befc0 00000000`00000040 : nt!PspSystemThreadStartup+0x5a
fffff880`0853ac40 00000000`00000000 : fffff880`0853b000 fffff880`08535000 fffff880`0853a580 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dxgmms1!VidMmiProcessTerminationCommand+5f
fffff880`101a247f 33d2            xor     edx,edx

SYMBOL_STACK_INDEX:  5

SYMBOL_NAME:  dxgmms1!VidMmiProcessTerminationCommand+5f

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5164dc13

IMAGE_VERSION:  6.1.7601.18126

FAILURE_BUCKET_ID:  X64_0xA_dxgmms1!VidMmiProcessTerminationCommand+5f

BUCKET_ID:  X64_0xA_dxgmms1!VidMmiProcessTerminationCommand+5f

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0xa_dxgmms1!vidmmiprocessterminationcommand+5f

FAILURE_ID_HASH:  {24a5b05f-0da8-ee02-b6e4-43c87a433b59}

Followup: MachineOwner
---------

 

[biggs223]

I also updated my graphic card driver, and i removed Java (it had a problem and 2 version of Java were installed) then used CCleaner and reinstalled the latest version.

Speccy : http://speccy.piriform.com/results/EHzzV3b5tXagKJ0ehTyFmwE (for your information i use a cooling board with 3 fan, always at max speed, and i clean it often).

EDIT : I have an error with the intel driver, it say "The driver being installed is not validated for this computer. Please obtain the appropriate driver from the computer manufacturer".

 

[Arc]

In this case you should run the Intel Driver Update Utility.

 

[biggs223]

It suggest the same driver that you suggested. Still not working. But yesterday i was able to play for a relatively long time.
Maybe it was Java after all. I will inform you if it crashes again.

http://speccy.piriform.com/results/PH1h6xr7Fz21FfUvAZKJOCi : temperature after playing a bit of minecraft.