Apc_index_mismatch

timoto · 16 Oct 2010

Dell M4400
Windows 7 Pro x64
Is original installed OS
OEM
System Hardware = 18 months old
OS installation = 9 months old

Hello and thank you for taking the time to help with this post.

This system has regularly experienced APC_INDEX_MISMATCH BSODs

The BSOD occurs intermittently at the end of booting windows and seems to be related to the wireless networking (Dell 150 Wireless-N), though I am not certain.

I believe all the drivers and BIOS are up to date.

Logs are zipped and attached.

Any help in locating the cause is much appreciated.

Thank you

Jonathan_King · 16 Oct 2010

Looks like Stopzilla may be causing the problem, from a quick glance. Try removing it and see what happens.

Also remove Avast. Use this tool: http://files.avast.com/files/eng/aswclear5.exe

Replace it with MSE: http://www.microsoft.com/security_essentials

LogMeIn should be updated or removed.

Install these updated nVidia drivers: NVIDIA DRIVERS 258.96 WHQL

Install these Intel NIC drivers: http://downloadcenter.intel.com/Deta...=3003&lang=eng

Install these Dell NIC drivers: Drivers and Downloads

There is more to update, if that doesn't work. Post back here if you get more BSODs, after completing the above steps.

...Summary of the Dumps:

Code:


Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Oct 16 10:45:22.474 2010 (UTC - 4:00)
System Uptime: 0 days 0:01:37.456
BugCheck 1, {74bd2dd9, 0, ffff, fffff880081f9ca0}
Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExit+245 )
BUGCHECK_STR:  0x1
PROCESS_NAME:  SZServer.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Oct 16 10:26:12.659 2010 (UTC - 4:00)
System Uptime: 0 days 0:02:11.641
BugCheck 1, {75502dd9, 0, ffff, fffff8800a1d1ca0}
Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExit+245 )
BUGCHECK_STR:  0x1
PROCESS_NAME:  SZServer.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Thu Oct 14 13:25:13.295 2010 (UTC - 4:00)
System Uptime: 0 days 0:01:35.277
BugCheck 1, {74e22dd9, 0, ffff, fffff88008d85ca0}
Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExit+245 )
BUGCHECK_STR:  0x1
PROCESS_NAME:  SZServer.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Thu Oct 14 11:28:59.260 2010 (UTC - 4:00)
System Uptime: 0 days 0:03:23.242
BugCheck 1, {755f2dd9, 0, ffff, fffff880085baca0}
Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExit+245 )
BUGCHECK_STR:  0x1
PROCESS_NAME:  SZServer.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Oct 12 10:10:30.769 2010 (UTC - 4:00)
System Uptime: 0 days 0:01:50.626
BugCheck 1, {74982dd9, 0, ffff, fffff88008673ca0}
Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExit+245 )
BUGCHECK_STR:  0x1
PROCESS_NAME:  SZServer.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Oct 11 09:10:21.725 2010 (UTC - 4:00)
System Uptime: 0 days 0:01:42.707
BugCheck 1, {75632dd9, 0, ffff, fffff880076c2ca0}
Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExit+245 )
BUGCHECK_STR:  0x1
PROCESS_NAME:  SZServer.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨

timoto · 16 Oct 2010

Hi Jonathan

Thank you for your support.

I have carried out your suggestions and will report back with any further BSOD errors should they arise.

May I ask, do you have a tool for analysing system logs that generates suggested driver updates, or did you do a manual search?

Thanks again

Jonathan_King · 17 Oct 2010

We use Windbg, and run the lmnt command (or variations thereof, such as lmntsm, to sort by name).

That shows the timestamps of all drivers loaded in RAM at the time of the crash.

Alternatively, while in Windbg, go to Debug>Modules, and then sort the list by timestamp.

The timestamp of Windows drivers is July 13, 2009 (July 14 depending on what part of the world you live in). Generally speaking, drivers older than that should be updated, although many drivers do not follow that rule.

It's just a matter of recognizing which drivers are prone to causing BSODs.

timoto · 27 Oct 2010

Just reporting back to say, thank you.

After putting the system through quite a lot of heavy use and variety of jobs I have had no further issues with the apc_index_mismatch.

Jonathan_King · 27 Oct 2010

Thanks for the report!

Did you follow all of the suggestions? I'm just trying to figure out what the cause was exactly, for the sake of my Solved BSOD archive.

And I'm glad it's all sorted out now.

Let us know if you need anything else.

timoto · 27 Oct 2010

Yes I followed all of the suggestions in one fell swoop without checking each change.

I wouldn't have had the patience to make one change and test for a few days before making the next one. Sorry.

So difficult to say in the end which element was really the cause.

The networking on the system, LAN, WLAN and Bluetooth are quite finicky I find. They have finally settled down, but this was for me the one area that was always causing me problems. Still it's not a definitive answer.

I'm glad to have Stopzilla off the system. They had a bug whereby the software would download ALL antivirus updates EVERY update. So at update 45 that's roughly 45MB to download then 46MB the next update.

Jonathan_King · 27 Oct 2010

I'll take a gamble and post that Stopzilla was the cause, as it was running at the time of all the crashes. It could also be the network drivers though, or a combination of any of those things.

The most important thing is that you got it sorted out.