League crash:
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This indicates that a system thread generated an exception which the error handler did not catch.
Code:
BugCheck 1000007E, {[COLOR=#4b0082]ffffffffc0000005[/COLOR], fffff800f6e7fcef, [COLOR=#ff0000]ffffd001ce66c6f8[/COLOR], ffffd001ce66bf00}
An access violation occurred.
Code:
1: kd> .exr 0xffffd001ce66c6f8
ExceptionAddress: fffff800f6e7fcef ([COLOR=#ff0000]dxgmms1!VIDMM_SEGMENT::MarkResourcesForEviction+0x0000000000000067[/COLOR])
ExceptionCode: [COLOR=#4b0082]c0000005 (Access violation)[/COLOR]
It occurred in
dxgmms1!VIDMM_SEGMENT::MarkResourcesForEviction+0x0000000000000067. The DirectX MMS was marking resources for eviction, but accessed invalid memory. It specifically tried to read from
ffffffffffffffff (-1).
Desktop crash:
IRQL_NOT_LESS_OR_EQUAL (a)
This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This bug check is issued if paged memory (or invalid memory) is accessed when the IRQL is too high. The error that generates this bug check usually occurs after the installation of a faulty device driver, system service, or BIOS.
Code:
BugCheck A, {[COLOR=#ff0000]fffff6e800ed02e0[/COLOR], 2, 0, fffff800e5d11414}
Code:
1: kd> .trap 0xffffd000d8f5fd40
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffc000f1254048 rbx=0000000000000000 rcx=ffffc000f1254530
rdx=0000380091167ad0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800e5dd5820 rsp=ffffd000d8f5fed8 rbp=ffffd000d8f60119
r8=0000000000000014 r9=0000000000000068 r10=0000000000000000
r11=ffffc000f1254530 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
nt!memcpy+0xa0:
fffff800`e5dd5820 f30f6f040a [COLOR=#ff0000]movdqu [/COLOR]xmm0,xmmword [COLOR=#4b0082]ptr [/COLOR][[COLOR=#000080]rdx+rcx[/COLOR]] ds:fffff801`823bc000=????????????????????????????????
On the instruction we faulted on, we failed moving (more specifically, moving double quadword from the source operand) a pointer that was stored in
rdx+rcx.
Code:
1: kd> !pte 0000380091167ad0
VA 0000380091167ad0
PXE at FFFFF6FB7DBED380 PPE at FFFFF6FB7DA70010 PDE at FFFFF6FB4E002440 PTE at FFFFF69C00488B38
Unable to get PXE FFFFF6FB7DBED380
1: kd> !pte ffffc000f1254530
VA ffffc000f1254530
PXE at FFFFF6FB7DBEDC00 PPE at FFFFF6FB7DB80018 PDE at FFFFF6FB70003C48 PTE at FFFFF6E0007892A0
Unable to get PXE FFFFF6FB7DBEDC00
I'd need a kernel-dump to check whether or not these were valid.
Okay, here's the rundown:
1. Your RAM is faulty. In order to rule this out, run Memtest for NO LESS than ~8 passes. If no errors, your RAM should be just fine:
Memtest86+:
Download Memtest86+ here:
Memtest86+ - Advanced Memory Diagnostic Tool
Which should I download?
You can either download the pre-compiled .ISO that you would burn to a CD and then boot from the CD, or you can download the auto-installer for the USB key. What this will do is format your USB drive, make it a bootable device, and then install the necessary files. Both do the same job, it's just up to you which you choose, or which you have available (whether it's CD or USB).
Do note that some older generation motherboards do not support USB-based booting, therefore your only option is CD (or Floppy if you really wanted to).
How Memtest works (you don't need to read, it's only for those interested in the specifics):
Memtest uses algorithms (specifically two), namely moving inversion & what is deemed Modulo-X. Essentially, the first algorithm fills the memory with a pattern. Starting at the low address, it checks to see if the pattern was changed (it should not have been), writes the patterns complement, increments the address, and repeats. Starting at the highest address (as opposed to the lowest), it follows the same checklist.
The reason for the second algorithm is due to a few limitations, with the first being that not all adjacent cells are being tested for interaction due to modern chips being 4 to 16 bits wide regarding data storage. With that said, patterns are used to go ahead and ensure that all adjacent cells have at least been written with all possible one and zero combinations.
The second is that caching, buffering and out of order execution will interfere with the moving inversions algorithm. However, the second algorithm used is not affected by this. For starting offsets of 0-20, the algorithm will write every 20th location with a pattern, write all other locations with the patterns complement, repeat the previous one (or more) times, and then check every 20th location for the previously mentioned pattern.
Now that you know how Memtest actually works, it's important to know that the tests it goes through all mean something different. It goes from Test 0 through Test 12, many of which use either one or the other algorithm discussed above, among many other things.
Any other questions, they can most likely be answered by reading this great guide here:
FAQ : please read before posting
2. Your GPU is faulty. In order to rule this out, refer to:
If the above BIOS update fails, do you have a secondary video card to test, or perhaps integrated video on that board? If so, uninstall your current video card drivers, shut down, physically remove your video card, install your secondary video card (or enable integrated video), and then install the latest drivers for whichever. See if the crashes stop, and if they do, your GPU is faulty.
3. Your replacement motherboard is faulty. This would be sad news...
Regards,
Patrick
