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

Hello *Smile

I have just been reading through this thread and thought I would add a comment or two.

I would suggest this is not a BSOD problem and there is no point in looking for the cause of a one-off BSOD event back on 25/Jan if that event is not being repeated.


The most recent logfiles have shown some evidence of hardware related problems as previously noted by @zbook. The watchdog error (these are not BSODs they are only there to catch errors and report them to Microsoft) that occurred on Feb 7th is related to the graphics hardware, basically it froze and reverted to using the basic display driver. See the following from the watchdog dump file you uploaded for us:

Code: VIDEO_DWMINIT_TIMEOUT_FALLBACK_BDD (187) Video fell back to BDD rather than using the IHV driver. This always generates a live dump. (This code can never be used for a real bugcheck.)[/quote] The log of the recent scan you did picked up some corrupted files that were corrected:
Code: 2018-02-09 08:56:57, Info CSI 00005bfe [SR] Repairing corrupted file \??\C:\WINDOWS\SysWOW64\es-ES\shell32.dll.mui from store 2018-02-09 08:54:36, Info CSI 0000355b [SR] Repairing corrupted file \??\C:\WINDOWS\System32\UXInit.dll from store 2018-02-09 08:54:29, Info CSI 000033be [SR] Repairing corrupted file \??\C:\WINDOWS\System32\themeui.dll from store 2018-02-09 08:54:15, Info CSI 000030f1 [SR] Repairing corrupted file \??\C:\WINDOWS\System32\es-ES\shell32.dll.mui from store[/quote]
I would be inclined to check the graphics card for all connections and clean the fans etc. If you have not run a hardware test on the graphics you should do this - we usually suggest furmark.






Diagnostic test

GPU TEST


Run Furmark tutorial



Note Run Furmark for around 30 minutes



Warning Your GPU temperatures will rise quickly while Furmark is running. Keep a keen eye on them and abort the test if temperatures rise too high

 

I will try that, thanks! May the graphic problem be related to those dll? They are patched or 'corrupted' in "purpose" in order to apply a custom theme.

Should I try reverting them?

Thanks!

EDIT:

Other thing I noticed when this happens is that my PC is not always accesible through TeamViewer, like it's not connected. Can a graphic error 'disconnect' my PC this way?

 

I would not have thought the custom theme changes would have caused problems but I don't know enough about the theme changes to be sure. If it is simple to remove then it is worth ruling that out and you can add it back in later.


TeamViewer relies on transmitting the display from your remote device so if the device display fails then I can believe the TeamViewer connection will be disrupted and might not come back until you restart it. Sorry I can't be more precise but I have not experienced this myself so I can only speculate. When running TeamViewer it usually changes the background to a black screen so having a custom theme on the device you are connecting to could be problematic.

 

I understand, is OK. It makes sense because sometimes TV showed my PC as connected but it couldn't open my display. But yesterday for example it showed as disconnected. That's weird.

 

Seems like there's been no crash so I guess the problem was the patched dlls. Let's keep this post here in case it happens again, but for now let's think about it as solved.

Thanks all!