BSOD while computer was idle

[vincentdb82]

These BSODs just started happening in the last day or so. First one I was playing Minecraft when it happened, then second one was today while I was out and the computer was idling. I have not taken any corrective steps at this time, other than to download Blue Screen Viewer. Included is the SF diagnostic Tool report. Any help is greatly appreciated.

 

[Arc]

Hi vincentdb82.

Can you update the intel HD Graphics driver? Use the Intel Driver Update Utility and see if it suggests anything.

Also test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

Let us know the results.
____________________________________

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

Use !analyze -v to get detailed debugging information.

BugCheck A, {0, 2, 0, fffff800030d7e52}

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

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

0: 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: fffff800030d7e52, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003309100
GetUlongFromAddress: unable to read from fffff800033091c0
 0000000000000000 Nonpaged pool

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KiSignalSynchronizationObject+42
fffff800`030d7e52 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:  fffff88005b309c0 -- (.trap 0xfffff88005b309c0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000002 rbx=0000000000000000 rcx=fffff8000324ce80
rdx=fffffa800451e540 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800030d7e52 rsp=fffff88005b30b50 rbp=0000000000000000
 r8=0000000000000000  r9=fffffa80084b1c40 r10=fffffa80084b1c40
r11=fffff88005b30be0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz ac po cy
nt!KiSignalSynchronizationObject+0x42:
fffff800`030d7e52 488b3f          mov     rdi,qword ptr [rdi] ds:00000000`00000000=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800030d1169 to fffff800030d1bc0

STACK_TEXT:  
fffff880`05b30878 fffff800`030d1169 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`05b30880 fffff800`030cfde0 : 00000000`00000000 00008000`00000000 00000000`00000000 fffffa80`0451e548 : nt!KiBugCheckDispatch+0x69
fffff880`05b309c0 fffff800`030d7e52 : 00000000`00000000 00000000`00000000 00000000`00000002 fffff800`030d7e12 : nt!KiPageFault+0x260
fffff880`05b30b50 fffff800`030d6256 : 00000000`00000000 fffff880`04c0b1d8 00000000`00000000 fffffa80`08490010 : nt!KiSignalSynchronizationObject+0x42
fffff880`05b30ba0 fffff880`04c1b47f : fffffa80`00000000 00000000`00000000 fffffa80`08d9b000 fffff880`05b30c60 : nt!KeSetEvent+0x106
fffff880`05b30c10 fffff880`04c392e9 : fffffa80`00000000 fffffa80`08490010 00000000`0000000f fffff880`04c3b085 : dxgmms1!VidMmiProcessTerminationCommand+0x5f
fffff880`05b30c60 fffff880`04c38574 : fffff800`00b96080 fffffa80`046b1010 00000000`00000000 fffffa80`08490010 : dxgmms1!VidSchiSubmitDeviceCommand+0x39
fffff880`05b30c90 fffff880`04c38012 : 00000000`00018634 fffffa80`0427d4c0 00000000`00000080 fffffa80`08490010 : dxgmms1!VidSchiSubmitQueueCommand+0xb0
fffff880`05b30cc0 fffff800`0336d73a : 00000000`02a1aabe fffffa80`08121a00 fffffa80`03fc1b30 fffffa80`08121a00 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`05b30d00 fffff800`030c28e6 : fffff800`0324ce80 fffffa80`08121a00 fffff800`0325acc0 fffff880`016c2885 : nt!PspSystemThreadStartup+0x5a
fffff880`05b30d40 00000000`00000000 : fffff880`05b31000 fffff880`05b2b000 fffff880`05b30640 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dxgmms1!VidMmiProcessTerminationCommand+5f
fffff880`04c1b47f 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
---------

 

[vincentdb82]

First off, love the avatar. Second, the update utility did suggest an update for my graphics card. I'll try the memtest before I go bed tonight.

 

[Arc]

Lol, thanks. I also love the avatar!

Let us know the results, and about any further issue.

 

[vincentdb82]

Installed new graphics driver and did a reboot. So far no BSODs -knock on wood-

 

[vincentdb82]

And right in the middle of Minecraft got the BSOD again. Gonna try the memtest step next later tonight.