BSOD [APC_INDEX_MISMATCH] after some changes on the pc

Sorry, I did the screenshots but totally forgot to upload them haha

Attachment 174325Attachment 174326Attachment 174327Attachment 174328

Unfortunately, most of the times there are just freezes and not BSOD and therefore is much more difficult for me to find the cause. I remember reading in the reliability history failures like "LiveKernelEvent 144" or something like that.

I'm starting to suspect from the GPU, may an app be triggering an exception? Most of the time the PC is running but there's no display...

EDIT

About the virtual memory, I also have a B and C (obviously) drive, both also configured to none. I have an SSD so I don't want to take that much space and writing operations.

1) Under system failure:
a) un-check automatically restart
b) change write debugging information to automatic
2) For virtual memory:
a) check automatically manage paging file size for all drives

The reason that there were no dumps was the "No paging file"

Once the above changes are made please re-post the new images.

Download and install: Whocrashed
http://www.resplendence.com/whocrashed
Above analyze click on tools > crash dump test > type: ACCEPT
Click analyze > post an image of the results into the thread.
Run this log collector and post a zip into this thread after all of the above steps:
log collector v2-beta08.zip

Disk enumeration is the numbering of the drives.
Most of the time Disk 0 is used for drive C:
Drive B: is currently Disk 0
Drive C: is currently Disk 3
Was this deliberate or by accident?

1) Under system failure:
a) un-check automatically restart

Done, but my PC is NOT restarting, it is freezing and losing display.

b) change write debugging information to automatic

Can't find that setting.

2) For virtual memory:

a) check automatically manage paging file size for all drives

I have had dumps with the current config before (I have pagefile enabled on H drive), only they delete or not stored much time. I really don't want to have that file on an SSD making writing operations. I will activate this if I start having BSOD and no dumps. But is not the case right now.

Once the above changes are made please re-post the new images.

Why the images again?? Can I just make those operations and wait for the outcome??

Download and install: Whocrashed

I'm not gonna crash my PC right now, maybe tomorrow. I had enough of that when I tried verifier. Again, please check the event log, the graphic card may be the cause because 90% of the time the pc is up and running (I can ping it) but no display.

Disk enumeration is the numbering of the drives.
Most of the time Disk 0 is used for drive C:
Drive B: is currently Disk 0
Drive C: is currently Disk 3
Was this deliberate or by accident?

I guess deliberated as long as C drive is not on the SATA1 but the SATA5 pin of the motherboard. Is this related to a driver/GPU failure?

I can't post right now a full dump, but again, nothing in my configuration has changed to upload a new one, in my opinion as a computer technician.

1) During the troubleshooting process please perform the above steps so that the freezing, and display problems can be troubleshooted.
2) On the Startup and Recovery windows > under system failure > under write debugging information click the down arrow > change to automatic memory dump
3) For un-unchecking automatically restart this setting will allow you to view the BSOD window where it will display the bugcheck and may display the misbehaving driver. Without checking this box the computer does not appear to have a BSOD unless you are seeing it live as the computer has rebooted.
4) There is a driver that is used to create dumps. When the page file is on another drive this driver can malfunction. The driver may function but there may be other problems prevent the dump formation. See this report in the event viewer:

Code:

Event[796]:  Log Name: System  Source: volmgr  Date: 2018-01-25T20:32:26.281  Event ID: 46  Task: N/A  Level: Error  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: SOBREMESA1  Description: Crash dump initialization failed!

This indicates that there was a BSOD crash yesterday. This BSOD crash you did not know about due to the computer settings.

In order to troubleshoot the computer problems we need your cooperation.

Please re-post the images after the changes are made and please post a new zip:
log collector v2-beta08.zip

Ztruker said:

There was a dump in the original zip file you uploaded. I'll upload it here for zbook to look at. I don't see much of use in it but he's seen things I've missed before: Attachment 174337

I knew it was somewhere haha. Thanks for that!

zbook said:

2) On the Startup and Recovery windows > under system failure > under write debugging information click the down arrow > change to automatic memory dump.

Done, here's the shot and also the proof that I have enable swapfile on C:

Attachment 174398Attachment 174399

Although I really don't know why the need of screenshots, if I say I've done it, it means I've done it...

zbook said:

See this report in the event viewer:

Code:

Event[796]:  Log Name: System  Source: volmgr  Date: 2018-01-25T20:32:26.281  Event ID: 46  Task: N/A  Level: Error  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: SOBREMESA1  Description: Crash dump initialization failed!

This indicates that there was a BSOD crash yesterday. This BSOD crash you did not know about due to the computer settings.

I would have swear that thursday at 8:30PM I was working on my PC solving a problem with a client of mine... Maybe I was trying verifier?

And here's a new log. I have performed the above changes and then I have reboot. Also, I've set nVidia 3D settings to maximum performance instead of power save. And I have close some apps that have overlays, in order to prevent a possible exception with the GPU. This night there hasn't been any trouble. Let's see how this goes.

I hope I don't miss anything at this point.

C:\WINDOWS\Minidump contains no dump files.
C:\WINDOWS\MEMORY.DMP was not found
The last bugcheck was c9 (Driver Verifier I/O Verification violation) on 01/25
Before that was bugcheck 1 (mismatch in the APC (asynchronous procedure calls) state index) also on 1/25

1)Download and install: Whocrashed
http://www.resplendence.com/whocrashed

2) On the virtual memory window please check the box in the left corner automatically manage paging file size for all drives

3) Open Whocrashed > above analyze click on tools > crash dump test > type: ACCEPT

4) Click analyze > post a report of the whocrashed crash dump test into the thread using a one drive or drop box share link

5) run this version of the log collector and post a zip into this thread:
log collector v2-beta08.zip

I told you before, I'm NOT gonna crash my PC on purpose, not now anyway. If I get another BSOD, I will upload the dump to you. I'm tired of uploading mega dumps with all my pc info only because of a minor configuration change.

As long as WhoCrashed has no other effect that check is my PC generates dumps, I won't run it by now. Sorry, is not that I don't want to collaborate, it is just that I'm sure it can generate dumps and after my experience with verifier I don't wanna crash anymore, at least not by now.

If you wanna make sure my PC is prepared to create dumps on crashes, believe me, IT IS now.

Let's wait for the next one, or let's hope there are no more.

zbook said:

The last bugcheck was c9 (Driver Verifier I/O Verification violation) on 01/25
Before that was bugcheck 1 (mismatch in the APC (asynchronous procedure calls) state index) also on 1/25

First one was done by me, second one I remember, and I don't know why or how. Do you have a clue?

zbook said:

2) On the virtual memory window please check the box in the left corner automatically manage paging file size for all drives

Done.

There was an unexpected reboot or crash on 1/26 that did not have a dump.
That could have been a manual power off.
The activity prior to that was: Crash dump initialization failed!

zbook said:

There was an unexpected reboot or crash on 1/26 that did not have a dump.
That could have been a manual power off.
The activity prior to that was: Crash dump initialization failed!

By then probably I didn't have swapfile enabled on all drives. Also, I only remember one, maybe two BSOD, all the other crashed are no display ones, and what I did when I found those was a forced reboot. That action probably triggered lots or more errors and crashed, but those would be deliberated.

Tell me if I can give you any other info :)