Windows 10: BSOD [APC_INDEX_MISMATCH] after some changes on the pc

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

 

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: 012518-385859-01.zip

 

I knew it was somewhere haha. Thanks for that!

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







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

This indicates that there was a BSOD crash yesterday. This BSOD crash you did not know about due to the computer settings.[/quote] 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
Resplendence Software - WhoCrashed, automatic crash dump analyzer

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.

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

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!

 

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

 

So far so good, maybe the nVidia config change I made did it? I'll keep you guys posted...

 

I'm going on a trip, so I'll keep testing when I get back. Thanks to all!

 

OK, so today it happen again. No inet visibility from outside, monitors off, but PC running. No BSOD crash on BlueScreenView, and yes, pagefile is on, automatically managed by windows for all drives. Here's a new dump of my PC. I think it may happen after I play around with nVidia 3D vision, but I'm not 100% sure about that.

Thanks.

 

Search for live kernal reports > post links into the thread
live-kernal-reports
WATCHDOG-20180207-2102.dmp

 

File explorer > this PC > C: > right upper corner search

 

1) backup all files to another drive or to the cloud
2) make a backup image using Macrium:
Macrium Software | Macrium Reflect Free
3) save the backup image to another drive or to the cloud
4) make a brand new restore point

Windows driver verifier is a tool that tests drivers.
It will repetitively produce BSOD until misbehaving drivers are fixed or until the tool is turned off.

In order to turn off the tool there are 3 methods using the windows advanced troubleshooting menu:
Enable and Disable Driver Verifier in Windows 10 Performance Maintenance Tutorials

Use the settings in this link for the customized tests:
Driver Verifier-- tracking down a mis-behaving driver. - Microsoft Community

During the use of windows driver verifier the computer may become sluggish. Sometimes there is difficulty booting. If you experience either of these problems the customized test settings can be modified.

The tool will be used for 48 hours. After the last BSOD it will be used for an additional 36 hours of typical computer use.

After each BSOD > turn off windows driver verifier > uninstall the misbehaving driver > post a new zip for troubleshooting:
log collector v2-beta08.zip

 

Founded on C:\Windows\LiveKernelReports\WATCHDOG *Smile

 

The msinfo32 was corrupt.
Please find it manually and post it into the thread:
In the left lower corner type: msinfo32 > save as NFO > save to desktop > zip > post into the thread