Solved APC Index Mismatch BSOD

[doveman007]

I've never seen this before and it's only happened this morning but I also had at least one automatic restart (clean shutdown) that happened whilst I was browsing with IE10 and I don't think there was any good reason for it (i.e. no programs had autoupdated and triggered the restart).

Unfortunately I haven't got any crash dumps as I've recently got a SSD and so disabled the pagefile to reduce writes to it. I've just tried to set the pagefile on C: to system managed but it's saying there's not enough space, even though there's 10GB free!

I checked the event log and there's several instances of

Application: RzSynapse.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.AccessViolationException
Stack:
at MS.Win32.UnsafeNativeMethods.DispatchMessage(System.Windows.Interop.MSG ByRef)
at System.Windows.Threading.Dispatcher.PushFrameImpl(System.Windows.Threading.DispatcherFrame)
at System.Windows.Threading.Dispatcher.PushFrame(System.Windows.Threading.DispatcherFrame)
at System.Windows.Threading.Dispatcher.Run()
at System.Windows.Application.RunDispatcher(System.Object)
at System.Windows.Application.RunInternal(System.Windows.Window)
at System.Windows.Application.Run(System.Windows.Window)
at Razer.Emily.UI.SynapseApp.Run()
at Razer.Emily.UI.AppEntryPoint.Main(System.String[])

and

Faulting application name: RzMaelstromVADStreamingService.exe, version: 1.1.47.1552, time stamp: 0x5232db8b
Faulting module name: RzMaelstromVADStreamingService.exe, version: 1.1.47.1552, time stamp: 0x5232db8b
Exception code: 0xc0000417
Fault offset: 0x00000000002e99c4
Faulting process id: 0xb38
Faulting application start time: 0x01cefd62e51f80b4
Faulting application path: C:\ProgramData\Razer\Synapse\Devices\Razer Surround\Driver\RzMaelstromVADStreamingService.exe
Faulting module path: C:\ProgramData\Razer\Synapse\Devices\Razer Surround\Driver\RzMaelstromVADStreamingService.exe
Report Id: 0cdfc882-6958-11e3-beea-8c89a563ffda

and

Faulting application name: RzSynapse.exe, version: 1.15.4.17412, time stamp: 0x52607323
Faulting module name: RazerConfigNative.dll, version: 2.19.17.0, time stamp: 0x526f1f0f
Exception code: 0xc0000005
Fault offset: 0x001b5942
Faulting process id: 0xf34
Faulting application start time: 0x01cefd62e6b345fe
Faulting application path: C:\Program Files (x86)\Razer\Synapse\RzSynapse.exe
Faulting module path: C:\ProgramData\Razer\Synapse\Devices\RazerConfigNative.dll
Report Id: 295dd5d8-6956-11e3-beea-8c89a563ffda

I've had Razer Surround Sound/Synapse installed for ages. I note it refers to Framework Version though, so maybe that's updated recently and they have some incompatibility problems. I've uninstalled Razer Synapse now anyway but left Razer Surround installed.

I installed Splashtop Desktop yesterday, so maybe that's the problem, although it's strange that it would only start causing problems this morning. I've disabled it's services for now anyway.

I did a sfc /scannow and the only thing that found was termsrv.dll, which I think is a modified version I used once to allow me to log in remotely without logging out the current user. It couldn't repair it automatically and I can't find the original in the Win7 ISO but I've got a backup named termsrv.dll.7601.1130.bak with a date of 21/11/2010 so if it hasn't been updated since then, I could restore that.

Any way, I'll reboot now to allow it to do a disc scan on C: I've exported the System and Application log errors for today and attached them.

 

[Arc]

Post it following the Blue Screen of Death (BSOD) Posting Instructions.

 

[doveman007]

Sorry, lost track of this.

I uninstalled Razer Surround anyway and haven't had any BSOD or crashes since. Seems quite a few people have reported the same problems with it.

I can only guess that I was using an earlier version before and it's only the recent update that introduced this critical bug.

 

[Arc]

Well done!

From our place, it is not good to suggest anything about the BSODs without seeing the dumps; but as per your original post, that was the issue actually.

Let us know for any further issue.