07-29-2016 03:09 AM
We've got Lenovo Products for a long time now. We have about 500 lenovo Pc's.
We changed the line of Pc, we went from L540 and x250 to L560 ans x260.
Since this change, we have several problems on those machines.
Random BSOD, mostly APC_INDEX_MISMATCH 0x00000001
We installed latest BIOS, latest drivers.
Sometimes pc's with 2 RAM, sometimes with just 1 RAM
We did not have those problems with x250 and l540
Asking for Help, Thanks
Solved! Go to Solution.
08-01-2016 08:25 AM
Think Engineering reviewed your experience and found Microsoft supporting documentation of this issue here: http://answers.microsoft.com/en-us/windows/forum/windows_7-hardware/apcindexmismatch-blue-screen-on-...
Information on returning to the last known good configuration can be found here: http://www.faultwire.com/solutions-fatal_error/APC-INDEX-MISMATCH-0x00000001-*1016.html
Troubleshooting in Safe Mode may allow you to determine root cause: http://computer.howstuffworks.com/question575.htm
Please let us know what you find.
08-04-2016 01:12 AM
Thanks for your answer.
This is a random BSOD, returning to the last known good configuration won't do anything..
How can i pinpoint which driver is causing this BSOD ?
The drivers were updated using Lenovo System Update software.
08-09-2016 01:24 PM
Can confirm, I'm seeing this on a pair of brand-new T460s units. They've been imaged using SCCM, with all relevant drivers subsequently installed using Lenovo System Update. They're both crashing in exactly the same way with the APC_INDEX_MISMATCH BSOD.
This issue does not present itself with the five brand-new X1 Carbon units which were imaged a few weeks ago.
That's now three different models in three different product lines (L, X and T series). Sounds like a driver issue to me. The units here are running Samsung 128GB SSDs.
08-13-2016 12:29 PM
Let's add another model and another product line: ThinkPad 11e Gen 3, type 20GB.
We image using WDS/MDT and the SCCM driver pack. No issues with that process, but all 4 of the machines I've imaged so far blue screen with APC_INDEX_MISMATCH at random points.
PaulCW - you mentioned you are running Samsung 128GB SSDs in your models. That's also what we're running in the machines experiencing the problem.
Has anyone been in direct contact with Lenovo about this? Didn't get a chance to open a case with them before I left on Friday, but planning to do so when I get in on Monday.
08-15-2016 06:10 AM
My thanks to the customers who have joined this discussion to add their models and share their experiences.
If anyone is willing to share their minidump files, please private message me. I would like to provide these files to Think Engineering to review.
08-15-2016 07:03 AM
Thanks, Amy! I just sent you a PM with a link to minidump files.
For others experiencing this - I came across this thread on Reddit:
Author claims that the Realtek audio drivers are the culprit, and this issue is resolved in driver version 126.96.36.19955. Lenovo doesn't have version 188.8.131.5255 available as far as I can tell, but I am testing with Microsoft's generic HD Audio driver as a work-around. Will post more as I know more. . .
08-15-2016 08:09 AM
After reviewing the models of systems reported impacted, I found one of these models, the T460s, has a Realtek audio driver version .7855 or higher available on support.lenovo.com. Unfortunately, the audio drivers for X260, L460, L560, T460, T460p, and ThinkPad 11e 20GB ThinkPads are lower versions.
PaulCW, would you mind upgrading one of your T460s to the driver listed below and report back?
Version 184.108.40.20691 for T460s: http://support.lenovo.com/us/en/products/Laptops-and-netbooks/ThinkPad-T-Series-laptops/ThinkPad-T46...
08-16-2016 01:27 PM
Just wanted to let everyone know where this is at. We started imaging today, but with the Realtek Audio driver for 20GB disabled in MDT. The laptops still have audio when the task sequence is complete, they're just using Microsoft's generic HD Audio Device driver. Have not seen any blue screens since we started.
Amy - I PM'd you the Lenovo case number for this issue. Any news from Think Engineering or the Critical Situation team?