APC_INDEX_MISMATCH and others. All caused by ntoskrnl.exe

Hi aolxhangover,

This is a quote from Multiple BSODs on new build - Windows 10 Forums for the reason why I didn't reply to your thread.

I haven't replied to your thread because of your own responses, they make it look like your getting helped by someone, because the last few days were quite busy I'm for now ignoring the threads where it looks like the OP is being helped to help others who certainly aren't being helped.

We work from oldest threads to newest threads with the 'unanswered threads' list, when you keep responding to your own thread it removes you from the list + it gives us the appearance you're already being helped. As we usually only reply to those where we already are helping or those who haven't gotten answers you would have been missed completely.
I recommend that you for the next time read this post in case the exact same happens again in the future so it can be prevented :)

Another thing to mention, at the Windows 10 Forums bumping is not allowed per the Forum Rules, I suggest that you take a bit time to read it, most of the rules are being used by many forums.

2) No useless posts, e.g., thread bumping, useless one liners, junk posting to increase post count, and identical multi-postings in different forums.

Now to the BSODs, run the DM Log Collector again and upload a new zip to provide all new data since the last crash.

axe0 said:

Hi aolxhangover,

This is a quote from Multiple BSODs on new build - Windows 10 Forums for the reason why I didn't reply to your thread.

We work from oldest threads to newest threads with the 'unanswered threads' list, when you keep responding to your own thread it removes you from the list + it gives us the appearance you're already being helped. As we usually only reply to those where we already are helping or those who haven't gotten answers you would have been missed completely.
I recommend that you for the next time read this post in case the exact same happens again in the future so it can be prevented :)

Another thing to mention, at the Windows 10 Forums bumping is not allowed per the Forum Rules, I suggest that you take a bit time to read it, most of the rules are being used by many forums.


Now to the BSODs, run the DM Log Collector again and upload a new zip to provide all new data since the last crash.

Sorry about that, and sorry about the time it took. It didn't bluescreen for a few days thankfully. I know you guys have finite resources. I was just really angsty because I really wanted to beat dark souls. 3:


Anyways, here's the newest crashes. I'm getting a system_service_exception error now, still while running dark souls 3. I do not think it is exclusive to being on dark souls 3 though. The BSoD seems to not have any consistency that I notice.



Attachment 80275


E: upon trying to launch dark souls 3 again, I got a new bluescreen "Attempted_Write_To_Readonly_Memory." Never seen that one before. anyways log file for that instance are below.

Attachment 80276

E2: Another System_Service_Exception, this time while trying diablo 3.

What fixed this before, but only very temporarily, was to uninstall all of my amd drivers, install a very old version, and manually update piece-by-piece from there. It took quite a while, and doesn't seem to work past a few days. I guess anyways, may have just been a coincidence. However I started Blue screening again after a non-bsod crash occured in dark souls 3 (computer just locked up) assuming that probably messed up the driver a little somehow.

E3: Going to run Memtest 86 all night to make sure. See you guys in the morning. Hopefully with some magic, and hopefully with no memtest errors.

You're running memory of different models & makes, this can cause lots of problems.
It is recommended that you remove either of them and use only memory of the same make & model.

Code:

[Memory Device (Type 17) - Length 34 - Handle 002ah]
  Physical Memory Array Handle  0028h
  Memory Error Info Handle      [Not Provided]
  Total Width                   64 bits
  Data Width                    64 bits
  Size                          8192MB
  Form Factor                   09h - DIMM
  Device Set                    [None]
  Device Locator                DIMM0
  Bank Locator                  BANK0
  Memory Type                   18h - Specification Reserved
  Type Detail                   4080h - Synchronous
  Speed                         1066MHz
  Manufacturer                  Kingston     
  Serial Number                        
  Asset Tag Number                          
  Part Number                   KHX1866C10D3/8G   
[Memory Device (Type 17) - Length 34 - Handle 002ch]
  Physical Memory Array Handle  0028h
  Memory Error Info Handle      [Not Provided]
  Total Width                   64 bits
  Data Width                    64 bits
  Size                          8192MB
  Form Factor                   09h - DIMM
  Device Set                    [None]
  Device Locator                DIMM1
  Bank Locator                  BANK1
  Memory Type                   18h - Specification Reserved
  Type Detail                   4080h - Synchronous
  Speed                         1066MHz
  Manufacturer                  Undefined    
  Serial Number                        
  Asset Tag Number                          
  Part Number                   8GBH2X04E99927-15 
[Memory Device (Type 17) - Length 34 - Handle 002eh]
  Physical Memory Array Handle  0028h
  Memory Error Info Handle      [Not Provided]
  Total Width                   64 bits
  Data Width                    64 bits
  Size                          8192MB
  Form Factor                   09h - DIMM
  Device Set                    [None]
  Device Locator                DIMM2
  Bank Locator                  BANK2
  Memory Type                   18h - Specification Reserved
  Type Detail                   4080h - Synchronous
  Speed                         1066MHz
  Manufacturer                  Kingston     
  Serial Number                        
  Asset Tag Number                          
  Part Number                   KHX1866C10D3/8G   
[Memory Device (Type 17) - Length 34 - Handle 0030h]
  Physical Memory Array Handle  0028h
  Memory Error Info Handle      [Not Provided]
  Total Width                   64 bits
  Data Width                    64 bits
  Size                          8192MB
  Form Factor                   09h - DIMM
  Device Set                    [None]
  Device Locator                DIMM3
  Bank Locator                  BANK3
  Memory Type                   18h - Specification Reserved
  Type Detail                   4080h - Synchronous
  Speed                         1066MHz
  Manufacturer                  Undefined    
  Serial Number                        
  Asset Tag Number                          
  Part Number                   8GBH2X04E99927-15

Seeing the PTE is also invalid it is very likely your memory causing problems.

Code:

4: kd> !pte 8000000000880121
                                           VA 8000000000880121
PXE at FFFFF6FB7DBED000    PPE at FFFFF6FB7DA00000    PDE at FFFFF6FB40000020    PTE at FFFFF68000004400
contains 0E700000B6D35867  contains 0000000000000000
pfn b6d35     ---DA--UWEV  not valid

WARNING: noncanonical VA, accesses will fault !