Windows 10: APC_INDEX_MISMATCH and others. All caused by ntoskrnl.exe

This all started happening randomly while playing Dark Souls 3 when it just froze. Now nothing has helped. I tried using a beta driver and that seemed to make it worse. I rolled back the driver and it doesn't crash immediately, but if I try to run any 3d game I know a BSoD is not far away. This is a fairly fresh install. I ran sfc already and it fixed the errors. Somebody please advise me on what to do, the blue screens are just infuriating, and I had to get my professor to let me take a test over because of the crashes.


BSoD logs:

Attachment 79471

:)

 

BSOD APC_INDEX_MISMATCH ntoskrnl.exe+142940

I had a BSOD. Bug Check String APC_INDEX_MISMATCH , cause by driver ntoskrnl.exe caused by address ntoskrnl.exe+142940. Adive on the fix for this. XPS 15 9950 RUNNING Windows 10 Pro.

 

Blue Screen; apc_index_mismatch; ntoskrnl.exe; ntoskrnl.exe+49671e

I have spent hundreds of dollars on technician fees trying to get this problem resolved.

I upgraded to Windows 10 hoping that it would solve the problem.

I do however have a sledgehammer ready to fix the problem using the neanderthal method.

==================================================

Dump File : 090915-18812-01.dmp

Crash Time : 9/9/2015 2:03:51 PM

Bug Check String : APC_INDEX_MISMATCH

Bug Check Code : 0x00000001

Parameter 1 : 00007ffd`217a3aaa

Parameter 2 : 00000000`00000000

Parameter 3 : 00000000`20000000

Parameter 4 : ffffd000`20b02b80

Caused By Driver : ntoskrnl.exe

Caused By Address : ntoskrnl.exe+14e240

File Description : NT Kernel & System

Product Name : Microsoft® Windows® Operating System

Company : Microsoft Corporation

File Version : 10.0.10240.16463 (th1.150819-1946)

Processor : x64

Crash Address : ntoskrnl.exe+14e240

Stack Address 1 :

Stack Address 2 :

Stack Address 3 :

Computer Name :

Full Path : C:\WINDOWS\Minidump\090915-18812-01.dmp

Processors Count : 2

Major Version : 15

Minor Version : 10240

Dump File Size : 281,384

Dump File Time : 9/9/2015 2:05:00 PM

==================================================

==================================================

Dump File : 090815-18812-01.dmp

Crash Time : 9/8/2015 12:35:11 AM

Bug Check String : APC_INDEX_MISMATCH

Bug Check Code : 0x00000001

Parameter 1 : 00007ffa`eacdfcba

Parameter 2 : 00000000`00000000

Parameter 3 : 00000000`20000000

Parameter 4 : ffffd000`21ba8b80

Caused By Driver : ntoskrnl.exe

Caused By Address : ntoskrnl.exe+14e240

File Description : NT Kernel & System

Product Name : Microsoft® Windows® Operating System

Company : Microsoft Corporation

File Version : 10.0.10240.16463 (th1.150819-1946)

Processor : x64

Crash Address : ntoskrnl.exe+14e240

Stack Address 1 :

Stack Address 2 :

Stack Address 3 :

Computer Name :

Full Path : C:\WINDOWS\Minidump\090815-18812-01.dmp

Processors Count : 2

Major Version : 15

Minor Version : 10240

Dump File Size : 281,328

Dump File Time : 9/8/2015 12:36:27 AM

==================================================

==================================================

Dump File : 090615-22687-01.dmp

Crash Time : 9/6/2015 11:39:57 PM

Bug Check String : APC_INDEX_MISMATCH

Bug Check Code : 0x00000001

Parameter 1 : 00000000`702c1e52

Parameter 2 : 00000000`00000000

Parameter 3 : 00000000`20000000

Parameter 4 : ffffd000`2666eb80

Caused By Driver : ntoskrnl.exe

Caused By Address : ntoskrnl.exe+14e240

File Description : NT Kernel & System

Product Name : Microsoft® Windows® Operating System

Company : Microsoft Corporation

File Version : 10.0.10240.16463 (th1.150819-1946)

Processor : x64

Crash Address : ntoskrnl.exe+14e240

Stack Address 1 :

Stack Address 2 :

Stack Address 3 :

Computer Name :

Full Path : C:\WINDOWS\Minidump\090615-22687-01.dmp

Processors Count : 2

Major Version : 15

Minor Version : 10240

Dump File Size : 281,328

Dump File Time : 9/6/2015 11:41:05 PM

==================================================

==================================================

Dump File : 090615-21656-01.dmp

Crash Time : 9/6/2015 2:44:39 PM

Bug Check String : APC_INDEX_MISMATCH

Bug Check Code : 0x00000001

Parameter 1 : 00007ffa`af39505a

Parameter 2 : 00000000`00000000

Parameter 3 : 00000000`20000000

Parameter 4 : ffffd000`23f87b80

Caused By Driver : ntoskrnl.exe

Caused By Address : ntoskrnl.exe+14e240

File Description : NT Kernel & System

Product Name : Microsoft® Windows® Operating System

Company : Microsoft Corporation

File Version : 10.0.10240.16463 (th1.150819-1946)

Processor : x64

Crash Address : ntoskrnl.exe+14e240

Stack Address 1 :

Stack Address 2 :

Stack Address 3 :

Computer Name :

Full Path : C:\WINDOWS\Minidump\090615-21656-01.dmp

Processors Count : 2

Major Version : 15

Minor Version : 10240

Dump File Size : 281,328

Dump File Time : 9/6/2015 2:45:39 PM

==================================================

==================================================

Dump File : 090415-21109-01.dmp

Crash Time : 9/4/2015 7:22:45 PM

Bug Check String : APC_INDEX_MISMATCH

Bug Check Code : 0x00000001

Parameter 1 : 00007ffb`f2ba353a

Parameter 2 : 00000000`00000000

Parameter 3 : 00000000`20000000

Parameter 4 : ffffd001`2b83db80

Caused By Driver : ntoskrnl.exe

Caused By Address : ntoskrnl.exe+14e240

File Description : NT Kernel & System

Product Name : Microsoft® Windows® Operating System

Company : Microsoft Corporation

File Version : 10.0.10240.16463 (th1.150819-1946)

Processor : x64

Crash Address : ntoskrnl.exe+14e240

Stack Address 1 :

Stack Address 2 :

Stack Address 3 :

Computer Name :

Full Path : C:\WINDOWS\Minidump\090415-21109-01.dmp

Processors Count : 2

Major Version : 15

Minor Version : 10240

Dump File Size : 281,328

Dump File Time : 9/4/2015 7:23:40 PM

==================================================

 

Pretty sure it's not the RAM either. I let memtest run overnight recently, and no errors were found.

 

Can anyone proficient in bsod dumps help me please? Sorry about bumping my own thread, I just want to finish dark souls 3 so badly, and I keep crashing ;_;

 

Will anyone help me? It's been like two days now *Sad

 

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 *Smile

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[/quote] 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 ![/quote]

 

didn't help

Attachment 80590

 

The dump didn't mention any driver, but the first parameter is ffffffffc0000005 which means a memory access violation has occured what is due to drivers.
Please update the drivers of your World of Warcraft MMO Gaming Mouse: Legendary Edition, it is the oldest driver on your system.
Code: 7/14/2011 11:06:02 PM C:\Windows\system32\drivers\MO4Driver.sys[/quote] Do you have a keyboard that you can use instead of Razer? Razer products, hardware & software, can be problematic sometimes. My suggestion with Razer would be to replace the hardware & remove the software for testing purpose.

If above suggestions don't help improve stability then we'll need to use driver verifier to catch them.





Diagnostic Test

DRIVER VERIFIER


Warning Please make a backup of your important files and get your rescue media or create one.
Please create a restore point.
Please follow this tutorial to run driver verifier.

Some windows drivers are blamed in a few crashes, but that usually means that a 3rd party driver is actually the cause.
Driver verifier stresses your drivers and will crash your pc if any driver fails due to a violation.

Driver verifier should be performed for a max of 48 hours, or when you have a bluescreen, whatever comes first.

If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.



Note Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.

 

I cannot replace either, and there hasn't been an update to that driver in a long time. I will run verifier when I can soon.

 

I"m only getting System_service_exception crashes now, and my computer isn't crashing from running driver verifier.

Attachment 81295

 

Please free up space in your D partition to at least 15% free space, Windows needs to have about 10-15% free space on each partition to not annoy the user about the background stuff that happens.

You have had quite some different crashes in the few days, though only 1 dumps is present in the uploaded zip file.
Driver verifier did cause crashes, but you don't see it because it isn't a 0xC4, 0xC9 or 0xE6

The 0x3B single dump was caused by driver verifier, but no drivers have been flagged. This is is an indication of something else and as the DirectX drivers are being blamed we may have to focus on the GPU.
Please try to reseat the GPU and/or seat the GPU into a different slot.
Code: ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 3B, {c0000005, fffff80149cbffe2, ffffd0003c845ca0, 0} *** WARNING: Unable to verify checksum for win32k.sys Probably caused by : dxgkrnl.sys ( dxgkrnl!DXGSYNCOBJECTLOCK::Release+27 ) Followup: MachineOwner DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP[/quote] Please fill in your system specsPlease follow this tutorial and download the tool. The tool will give you detailed information about your system specs, please fill in your system specs more completely.How to fill in your system specs:

 

It seemed like changing the pci port helped for a little while, but I tried to run MSI afterburner and it gave me a black screen, then started giving me system_service_exception errors again.

I deleted the logs in question, because I wasn't running verifier when the crashes happened.

Is there an updated version of that tool for windows 10 forums?

Attachment 81403