Kernel-Power Event 41 (random restarts)

Code:

STOP 0x0000001A: MEMORY_MANAGEMENT  http://www.carrona.org/bsodindx.html#0x0000001A

Usual causes:  Device driver, memory, kernel

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {5002, fffff70001080000, cd24, 2a009a40fffffffe}

Probably caused by : dxgkrnl.sys ( dxgkrnl!memmove+154 )

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

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

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000005002, The subtype of the bugcheck.
Arg2: fffff70001080000
Arg3: 000000000000cd24
Arg4: 2a009a40fffffffe

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


BUGCHECK_STR:  0x1a_5002

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  plugin-contain

CURRENT_IRQL:  0

TRAP_FRAME:  fffff880097a2980 -- (.trap 0xfffff880097a2980)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000001 rbx=0000000000000000 rcx=000000000401a020
rdx=fffff8a006349fe0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800463b924 rsp=fffff880097a2b18 rbp=fffff880097a2ca0
 r8=0000000000025964  r9=000003e900007530 r10=0000000200000001
r11=0000000003fa0020 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
dxgkrnl!memmove+0x154:
fffff880`0463b924 4c0fc349e0      movnti  qword ptr [rcx-20h],r9 ds:00000000`0401a000=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002e6e6e7 to fffff80002eddfc0

STACK_TEXT:  
fffff880`097a2818 fffff800`02e6e6e7 : 00000000`0000001a 00000000`00005002 fffff700`01080000 00000000`0000cd24 : nt!KeBugCheckEx
fffff880`097a2820 fffff800`02edc0ee : 00000000`00000001 00000000`0401a000 fffffa80`074cfb00 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x45f28
fffff880`097a2980 fffff880`0463b924 : fffff880`0467cee6 00000000`ffffe17e 00000000`00000000 00000000`00000002 : nt!KiPageFault+0x16e
fffff880`097a2b18 fffff880`0467cee6 : 00000000`ffffe17e 00000000`00000000 00000000`00000002 00000000`00000000 : dxgkrnl!memmove+0x154
fffff880`097a2b20 fffff960`001f057a : 00000000`0671e7c0 00000000`fff80000 00000000`00000000 00000000`00000001 : dxgkrnl!DxgkGetDisplayModeList+0x73a
fffff880`097a2bf0 fffff800`02edd253 : 00000000`00000001 00000000`03fa0018 00000000`0671e701 00000000`05130000 : win32k!NtGdiDdDDIGetDisplayModeList+0x12
fffff880`097a2c20 00000000`747214ca : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0671e798 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x747214ca


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dxgkrnl!memmove+154
fffff880`0463b924 4c0fc349e0      movnti  qword ptr [rcx-20h],r9

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  dxgkrnl!memmove+154

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgkrnl

IMAGE_NAME:  dxgkrnl.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce799fa

FAILURE_BUCKET_ID:  X64_0x1a_5002_dxgkrnl!memmove+154

BUCKET_ID:  X64_0x1a_5002_dxgkrnl!memmove+154

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

Probably you should take memtest for longer.

Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.

• RAM - Test with Memtest86+

The goal is to test all the RAM sticks and all the motherboard slots.

Check your motherboard manual to ensure the RAM sticks are in the recommended motherboard slots. Some motherboards have very specific slots required for the number of RAM sticks installed.

If you get errors, stop the test and continue with the next step.

1. Remove all but one stick of RAM from your computer (this will be RAM stick #1), and run Memtest86 again, for 7 passes.

*Be sure to note the RAM stick, use a piece of tape with a number, and note the motherboard slot.

If this stick passes the test then go to step #3.

2. If RAM stick #1 has errors, repeat the test with RAM stick #2 in the same motherboard slot.

*If RAM stick #2 passes, this indicates that RAM stick #1 may be bad. If you want to be absolutely sure, re-test RAM stick #1 in another known good slot.

*If RAM stick #2 has errors, this indicates another possible bad RAM stick, a possible motherboard slot failure or inadequate settings.

3. Test the next stick of RAM (stick #2) in the next motherboard slot.

*If this RAM stick has errors repeat step #2 using a known good stick if possible, or another stick.

*If this RAM stick has no errors and both sticks failed in slot#1, test RAM stick #1 in this slot.

4. If you find a stick that passes the test, test it in all the other motherboard slots.

If Part 2 testing shows errors, and all tests in Part 3 show errors, you will need to test the RAM sticks in another computer and/or test other RAM in your computer to identify the problem.

In this way, you can identify whether it is a bad stick of RAM, a bad motherboard, or incompatibility between the sticks.

   Information

Errors are sometimes found after 8 passes.

   Tip

Do this test overnight, before going to bed.

Good news.

Let us know if you have any other problems.