[SOLVED] Programs suddenly crashing.

D

doveman

Well-known member
Joined
Sep 22, 2012
Posts
58
Everything was fine a couple of days ago. I've been playing with new builds of FreeTrackNoIR, which I just unzipped into a folder so it won't have installed any files anywhere else. I got to one build and was no longer able to launch it, seeing a WerFault.exe popup from my firewall and no window for the program, although it was left running in Task Manager.

I went to play Arma2OA tonight and that crashes during loading as well now. I was playing it fine on Friday and I don't think I've changed anything since then. I upgraded from Catalyst 12.6 to 13.2beta3 recently but that was before Friday.

The original crashes of FTNoIR don't show anything very useful:

Code: 
Faulting application name: ftnoir.exe, version: 0.0.0.0, time stamp: 0x510c9a62
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc000041d
Fault offset: 0x74134d62
Faulting process id: 0x1b0c
Faulting application start time: 0x01ce01315851cfae
Faulting application path: C:\Program Files (x86)\Abbequerque Inc\FTNoIR1.8pA\ftnoir.exe
Faulting module path: unknown
Report Id: bd8280a6-6d24-11e2-b61f-8c89a563ffda

but then I got this:

Code: 
Faulting application name: ftnoir.exe, version: 0.0.0.0, time stamp: 0x510d03a8
Faulting module name: ntdll.dll, version: 6.1.7601.17725, time stamp: 0x4ec49b8f
Exception code: 0xc0000005
Fault offset: 0x000343d0
Faulting process id: 0x4b0
Faulting application start time: 0x01ce0149f9b3ee30
Faulting application path: C:\Program Files (x86)\Abbequerque Inc\FTNoIR1.8pA\ftnoir.exe
Faulting module path: C:\Windows\SysWOW64\ntdll.dll
Report Id: 95f50745-6d3f-11e2-910f-8c89a563ffda

I had one crash with Opera but I think that was just after I updated it and it's been OK since:

Code: 
Faulting application name: opera.exe, version: 12.13.1734.0, time stamp: 0x510685d3
Faulting module name: ole32.dll, version: 6.1.7601.17514, time stamp: 0x4ce7b96f
Exception code: 0xc0000005
Fault offset: 0x0003bc21
Faulting process id: 0x590
Faulting application start time: 0x01ce0182104bc95a
Faulting application path: E:\Portable Apps\Opera12\opera.exe
Faulting module path: C:\Windows\syswow64\ole32.dll
Report Id: 055709c3-6d90-11e2-bf03-8c89a563ffda

then Dyndns crashed once:

Code: 
Faulting application name: DynUpSvc.exe, version: 4.1.10.0, time stamp: 0x4ec29f59
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x006ec7a6
Faulting process id: 0x4d8
Faulting application start time: 0x01ce018066b4c2bd
Faulting application path: C:\Program Files (x86)\Dyn Updater\DynUpSvc.exe
Faulting module path: unknown
Report Id: 73dfb5ab-6e32-11e2-bf03-8c89a563ffda

and now it's Arma2OA's turn:

Code: 
Faulting application name: arma2oa.exe, version: 1.62.100.697, time stamp: 0x50efead5
Faulting module name: arma2oa.exe, version: 1.62.100.697, time stamp: 0x50efead5
Exception code: 0xc0000005
Fault offset: 0x00634d9e
Faulting process id: 0x2650
Faulting application start time: 0x01ce02411c6bb5c5
Faulting application path: D:\Games\ArmA 2 Operation Arrowhead\Expansion\beta\arma2oa.exe
Faulting module path: D:\Games\ArmA 2 Operation Arrowhead\Expansion\beta\arma2oa.exe
Report Id: 7173cfec-6e34-11e2-bf03-8c89a563ffda

then MPExtended:

Code: 
Faulting application name: MPExtended.Applications.ServiceConfigurator.exe, version: 0.5.1.0, time stamp: 0x50bcf6e5
Faulting module name: KERNELBASE.dll, version: 6.1.7601.18015, time stamp: 0x50b83c8a
Exception code: 0xe0434352
Fault offset: 0x0000c41f
Faulting process id: 0xfd4
Faulting application start time: 0x01ce0253ab43c345
Faulting application path: C:\Program Files (x86)\MPExtended\Service\MPExtended.Applications.ServiceConfigurator.exe
Faulting module path: C:\Windows\syswow64\KERNELBASE.dll
Report Id: 29cc04a5-6e47-11e2-8fe7-8c89a563ffda

and even Werfault:

Code: 
Faulting application name: WerFault.exe, version: 6.1.7600.16385, time stamp: 0x4a5bc2d9
Faulting module name: ntdll.dll, version: 6.1.7601.17725, time stamp: 0x4ec49b8f
Exception code: 0xc0000374
Fault offset: 0x000ce6c3
Faulting process id: 0x1140
Faulting application start time: 0x01ce0254ad426da7
Faulting application path: C:\Windows\SysWOW64\WerFault.exe
Faulting module path: C:\Windows\SysWOW64\ntdll.dll
Report Id: eaf87e08-6e47-11e2-8fe7-8c89a563ffda

I booted to my other Windows 7 install and both FTNoIR and Arma2OA work fine in that. It's still running Cat 12.6, so I rebooted into the problem install, uninstalled Cat 13.2beta3, rebooted and reinstalled Cat 12.6. That hasn't helped though and I can't even open CCC now.

Code: 
Faulting application name: Kdbsync.exe, version: 0.0.0.0, time stamp: 0x4f67a718
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00000000
Faulting process id: 0x1754
Faulting application start time: 0x01ce025661253757
Faulting application path: C:\Program Files (x86)\AMD AVT\bin\Kdbsync.exe
Faulting module path: unknown
Report Id: a0e3e927-6e49-11e2-8c82-8c89a563ffda

Code: 
Faulting application name: MMLoadDrv.exe, version: 2.0.0.0, time stamp: 0x4fd61ef5
Faulting module name: ntdll.dll, version: 6.1.7601.17725, time stamp: 0x4ec49b8f
Exception code: 0xc0000374
Fault offset: 0x000ce6c3
Faulting process id: 0x1404
Faulting application start time: 0x01ce0256676149a8
Faulting application path: C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static\MMLoadDrv.exe
Faulting module path: C:\Windows\SysWOW64\ntdll.dll
Report Id: a5626ccf-6e49-11e2-8c82-8c89a563ffda

Code: 
Faulting application name: CCC.exe, version: 3.5.0.0, time stamp: 0x4f8350ef
Faulting module name: ntdll.dll, version: 6.1.7601.17725, time stamp: 0x4ec4aa8e
Exception code: 0xc0000374
Fault offset: 0x00000000000c40f2
Faulting process id: 0x1470
Faulting application start time: 0x01ce0256646c7363
Faulting application path: C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static\CCC.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: aa3f8b40-6e49-11e2-8c82-8c89a563ffda

I've done a SFC /scannow and that hasn't reported any problems.
 
Hmm, seems I spoke too soon. I thought I'd use my working Windows 7 in the meantime but now Arma2OA crashes on loading in that too:

Code: 
Faulting application name: arma2oa.exe, version: 1.62.95.248, time stamp: 0x500d59cb
Faulting module name: arma2oa.exe, version: 1.62.95.248, time stamp: 0x500d59cb
Exception code: 0xc0000005
Fault offset: 0x005c4313
Faulting process id: 0x5a0
Faulting application start time: 0x01ce025bc97fb9bc
Faulting application path: D:\Games\ArmA 2 Operation Arrowhead\arma2oa.exe
Faulting module path: D:\Games\ArmA 2 Operation Arrowhead\arma2oa.exe
Report Id: 164a9b37-6e4f-11e2-b5c3-8c89a563ffda

FTNoIR launches OK still though. I'll do a full Memtest overnight.
 
Have you yet run any hardware diagnostics? Sorry, I am losing track of all of these threads :p

Your Windows Update issue was bitshift related, which could certainly be hardware related. And all of these crashes somehow seem to be very hard to explain without hardware being a root cause.

Richard
 
Hi again,

Yeah sorry it's getting a bit confusing. I haven't had any problems with Opera crashing recently and bringing down Explorer, so I haven't needed to restart it with the resulting missing icons. So I can't really say the problem of the missing icons when restarting Explorer is fixed but the trigger that was leading to it hasn't been happening thankfully.

I did a couple of clean runs of memtest overnight so that seems to rule that out. I also removed PhenomMSRTweaker from both installs and removed the overclock in the BIOS, so now it's running at the default 3.2Ghz, NB at 2000Mhz. I left the Vcore at 1.375v which is the default for my CPU anyway and my motherboard undervolts it slightly if I leave it set to Default. I think I left the NB at 1.3v as well but I'll have to check that.

My second Windows install seems OK and FTNoIR runs fine. Arma2OA still crashes on loading though, so I'll try restoring the files from backup in case they've got corrupted somehow.

The original Windows install throws up errors on boot, the first I see is kdbsync.exe which is something to do with ATI:

Code: 
Faulting application name: kdbsync.exe, version: 0.0.0.0, time stamp: 0x4f67a718
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00000000
Faulting process id: 0xf88
Faulting application start time: 0x01ce026b018fac3b
Faulting application path: C:\Program Files (x86)\AMD AVT\bin\kdbsync.exe
Faulting module path: unknown
Report Id: 51c45f5e-6e5e-11e2-bc07-8c89a563ffda

then 20s later MPExtended/.NET Runtime:

Code: 
Application: MPExtended.Applications.ServiceConfigurator.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.Windows.Markup.XamlParseException
Stack:
   at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
   at System.Windows.Threading.DispatcherOperation.InvokeImpl()
   at System.Windows.Threading.DispatcherOperation.InvokeInSecurityContext(System.Object)
   at System.Threading.ExecutionContext.runTryCode(System.Object)
   at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode, CleanupCode, System.Object)
   at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
   at System.Windows.Threading.DispatcherOperation.Invoke()
   at System.Windows.Threading.Dispatcher.ProcessQueue()
   at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
   at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
   at MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object)
   at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
   at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
   at System.Windows.Threading.Dispatcher.InvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32)
   at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)
   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.Application.RunDispatcher(System.Object)
   at System.Windows.Application.RunInternal(System.Windows.Window)
   at System.Windows.Application.Run(System.Windows.Window)
   at MPExtended.Applications.ServiceConfigurator.App.Main()

then another MPExtended 25s later:

Code: 
Faulting application name: MPExtended.Applications.ServiceConfigurator.exe, version: 0.5.1.0, time stamp: 0x50bcf6e5
Faulting module name: KERNELBASE.dll, version: 6.1.7601.18015, time stamp: 0x50b83c8a
Exception code: 0xe0434352
Fault offset: 0x0000c41f
Faulting process id: 0xca8
Faulting application start time: 0x01ce026afca9370c
Faulting application path: C:\Program Files (x86)\MPExtended\Service\MPExtended.Applications.ServiceConfigurator.exe
Faulting module path: C:\Windows\syswow64\KERNELBASE.dll
Report Id: 6c8bda6e-6e5e-11e2-bc07-8c89a563ffda

and 1m30s later CCC:

Code: 
Faulting application name: CCC.exe, version: 3.5.0.0, time stamp: 0x4f8350ef
Faulting module name: ntdll.dll, version: 6.1.7601.17725, time stamp: 0x4ec4aa8e
Exception code: 0xc0000374
Fault offset: 0x00000000000c40f2
Faulting process id: 0x10c4
Faulting application start time: 0x01ce026b06dbbf59
Faulting application path: C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static\CCC.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: a257b453-6e5e-11e2-bc07-8c89a563ffda

and 45s later FUEL:

Code: 
Faulting application name: Fuel.Service.exe, version: 1.0.0.0, time stamp: 0x4fd626ed
Faulting module name: Device.dll, version: 4.1.0.0, time stamp: 0x4f55e10b
Exception code: 0xc0000005
Fault offset: 0x00000000000033c1
Faulting process id: 0x698
Faulting application start time: 0x01ce026aebf16011
Faulting application path: C:\Program Files\ATI Technologies\ATI.ACE\Fuel\Fuel.Service.exe
Faulting module path: C:\Program Files\ATI Technologies\ATI.ACE\Fuel\Device.dll
Report Id: bd718501-6e5e-11e2-bc07-8c89a563ffda

So as you can see, there's three ATI related errors there. It's hard to believe that upgrading from Cat 12.6 to 13.2beta3 caused the problem as it didn't start happening until several days later. It's possible that some files have been left over when uninstalling 13.2beta3 (apparently this is a common problem, or at least used to be, perhaps they've improved things recently) so maybe I need to find out how to uninstall 12.6, clean out all ATI files and reinstall 12.6.

I can certainly do a Prime95 test on the working Windows install to check the processor is OK and I've just done a quick check of the GPU with the MSI Kombuster stress test and that seems OK (I only thought it might be worth checking because of the ATI related errors and the fact that ArmA2OA crashes on loading, when it might be loading the GPU, but Kombuster loads it far more than ArmA2OA's menu would).
 
It seems that other games are crashing on loading under the "working" Windows install as well. As well as Arma2OA, I've tried Arma2 and DCS World.

I'm running Prime95 Blend at the moment and it's only been going for 17mins but it hasn't thrown up any errors yet. I can't really think what other hardware apart from the RAM, CPU or GPU could be causing games to crash like this. I've still got an XP install, so I'll see if they work under that (except DCS World which is 64-bit).
 
Well Prime95 for 45mins didn't throw up any errors.

I tried loading Far Cry 3, which is installed on my secondary drive and that loaded OK, so I tried copying Arma2OA to that drive and running it from there but it still crashed. Black Mirror 2 which is on the first drive loads OK though.

Things seem to be taking longer to load than the should though.

I tried taking out two sticks of RAM, leaving 2*4GB but Arma2OA still crashes.

I've got a problem on my "working" Windows with Avira Antirvir as well, as it can't start or be installed. Nor can I install the new version on top of it. This is the error in the logs:

Code: 
Unable to load file QueryInterface(57).  Returned error code: 0x1

but the popup error says:

"Setup could not determine the feature control file or was not able to read it correctly [Errorcode: 7]"

EDIT: OK, I've found some manual uninstall instructions for Avira. My CPU is stuck at 800Mhz now though! I had to select "Reset to Defaults" when booting after I removed the RAM but I thought that would just reset the RAM settings. Anyway, even if it's re-enabled Cool'N'Quiet, it should still be upclocking.

EDIT2: OK, "Reset Defaults" did reset everything, including enabling CoolNQuiet and changing from AHCI to IDE mode. Doesn't explain why it was stuck at 800Mhz but I've disabled CnQ now and set everything else back to how it should be. Games are still crashing on load though in the "Working" Windows. The fact that both Windows installs are having this problem (although the first one is having far more problems and may be beyond saving) does suggest a hardware rather than software fault but I can't for the life of me think what.
 
OK, I restored from a True Image and Arma2OA and DCS World both load OK now.

I'd like to blame Cat 13.2beta3 but I can't really, seeing as it's never been installed in the 2nd Windows, so not really sure what could have been causing the games to crash in both.

I did notice this strange purple box on booting, which I've seen a couple of times recently (perhaps since these problems started) but I don't think it appears on every boot.


No other errors on boot or otherwise so far though thankfully. Opera has crashed once but it didn't register in the logs, nor did it bring down Explorer.

So I guess I'll just keep an eye on it and report back if I see any more problems.
 
Hi -

The Opera crash shows it running from e: -
Code: 
E:\Portable Apps\Opera12\opera.exe
Is that usually where you run it from?

You may want to install ATI driver only (no CCC).

Follow instructions by usasma - https://www.sysnative.com/forums/wi...cards-driver-only-installation-procedure.html

When you see that purple box on the screen again, use SysInternals Process Explorer and find out what app it belongs to.

Process Explorer

Leave the purple box on screen; run Process Explorer. Click on this icon, hold left mouse key down, drag it to the purple box. Release the mouse button; Process Explorer screen will reappear.

02-04-2013_procexp1.png
​

The app will be on the highlighted blue line.

Regards. . .

jcgriff2
 
Hi jcgriff2

Yep, I installed Opera using the USB option and put it in my Portable Apps folder so that I can share it between Windows installations.

I should probably leave the ATI stuff alone at the moment whilst it's working ;) I actually need CCC anyway to set the video options (deinterlace, pulldown, etc).

I'll try and catch what the purple box belongs to with Process Explorer but it might be tricky as I think it only appears for maybe 5-10s and as it's near the start of Windows booting it's not very responsive at that point so it'll be tricky to launch Process Explorer quickly.
 
jcgriff2 said:
What does the icon in Taskbar say?

View attachment 3236

What is it for?
Click to expand...

That's Xpadder. It just allows me to map keys to the buttons on my joystick.

Actually that purple box is roughly the same shape as the Xpadder window but seems a fair bit smaller. If I keep seeing it, I'll disable it from loading at boot though and see if that stops it.
 
jcgriff2 said:
doveman said:
Actually that purple box is roughly the same shape as the Xpadder window but seems a fair bit smaller. If I keep seeing it, I'll disable it from loading at boot though and see if that stops it.
Click to expand...

The shape of the taskbar box is likely due to your system setting -

Windows 7 Taskbar and Start Menu Properties

If you change it to "always combine, hide labels" - all will be the same size (small square box)
Click to expand...

I'm not concerned with the shape of the taskbar boxes and I don't like the "always combine" option but thanks anyway.
 
Whilst it mostly seems OK at the moment, I do sometimes get an error/crash on boot from MPExtended, although that may be a problem with that app rather than a sign of anything more general wrong.

In Event Viewer I see:

Code: 
Application: MPExtended.Applications.ServiceConfigurator.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.Windows.Markup.XamlParseException
Stack:
   at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
   at System.Windows.Threading.DispatcherOperation.InvokeImpl()
   at System.Windows.Threading.DispatcherOperation.InvokeInSecurityContext(System.Object)
   at System.Threading.ExecutionContext.runTryCode(System.Object)
   at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode, CleanupCode, System.Object)
   at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
   at System.Windows.Threading.DispatcherOperation.Invoke()
   at System.Windows.Threading.Dispatcher.ProcessQueue()
   at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
   at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
   at MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object)
   at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
   at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
   at System.Windows.Threading.Dispatcher.InvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32)
   at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)
   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.Application.RunDispatcher(System.Object)
   at System.Windows.Application.RunInternal(System.Windows.Window)
   at System.Windows.Application.Run(System.Windows.Window)
   at MPExtended.Applications.ServiceConfigurator.App.Main()

and then

Code: 
Faulting application name: MPExtended.Applications.ServiceConfigurator.exe, version: 0.5.3.0, time stamp: 0x51056c54
Faulting module name: KERNELBASE.dll, version: 6.1.7601.18015, time stamp: 0x50b83c8a
Exception code: 0xe0434352
Fault offset: 0x0000c41f
Faulting process id: 0xa68
Faulting application start time: 0x01ce0416a77069d9
Faulting application path: C:\Program Files (x86)\MPExtended\Service\MPExtended.Applications.ServiceConfigurator.exe
Faulting module path: C:\Windows\syswow64\KERNELBASE.dll
Report Id: 029b8198-700a-11e2-a858-8c89a563ffda

I'm not sure if this is connected to the above but 1min34s later there's this:

Code: 
Fault bucket 3469834093, type 5
Event Name: CLR20r3
Response: Not available
Cab Id: 0

Problem signature:
P1: 3QX3DGLKNUIBNNXRXLSOM2J0SUF3ONYR
P2: 0.5.0.0
P3: 51056c54
P4: Hardcodet.Wpf.TaskbarNotification
P5: 1.0.4.0
P6: 4e8c1cf0
P7: 3f
P8: 2b
P9: System.Windows.Markup.XamlParse
P10: 

Attached files:
c:\Temp\Del\WER9137.tmp.WERInternalMetadata.xml

These files may be available here:
C:\Users\Del\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_3QX3DGLKNUIBNNXR_e4a3759996b37416ea670682a1cac95db78cc57_0d4f007c

Analysis symbol: 
Rechecking for solution: 0
Report Id: 029b8198-700a-11e2-a858-8c89a563ffda
Report Status: 0

I have another problem after this boot though, in that my Notification Area icon for Comodo Firewall is not there, although the process cfp.exe is still running. I've had this from time to time before actually, where it's icon doesn't appear after booting and I have to run it, which doesn't create another instance of cfp.exe but opens it's window and creates the icon. I'm planning to uninstall it and use a different firewall though as I find the way it's rules list works rather strange and unmanageable but maybe I should find out why it's doing this first.
 
Which sticks of RAM did you remove? It should be the first couple, not the last, since those ones are more likely to be causing this.

The error codes for the crashes seem to range from your typical "memory could not be read/written/executed" to some more interesting ones like the one hit by WerFault and CCC.exe which says the heap was corrupted. So either some user-mode application is going haywire and smearing heap memory, or there's RAM module issues on the ones holding the heap memory. Heap memory resides on the lower region of memory for the system while kernel and pool memory sits at the very top, so we'll want to look at the lower portion of memory to find anything unusual.

Would it be possible for you to retrieve for us a crashdump or two from these appfaults? When WerFault (the error message) appears saying the app has crashed, it will usually provide a link to the crashdump file. That crashdump file is temporary and often I've found it's deleted the moment WerFault is closed, so while the error message is still up direct yourself to that file and move it to a safe location then send to us for evaluation. Doing this for multiple crashing programs will allow us to detect any patterns between them that can help determine cause. You may also provide us with a full dump when the app crashes by keeping the error message open, then open up Task Manager (or Process Explorer, preferably) and right-click the app (not WerFault but the crashing app) and select Create Dump then Full Dump (for Process Explorer). It will be rather big so you may need to upload to 3rd-party site (make sure to zip first).

It may even be necessary to run Application Verifier on the faulting program. Set it up to point it to the application you want to test and save the settings, then open the app and let the app crash. It may end up providing more accurate details in the crashdump WerFault churns out than if done otherwise. You don't have to tweak the actual check settings, I believe, as the basic stuff seems enough for now. You can ignore the prompt it gives you for having the app run in a debugger at this time.

@niemiro:

Where are you getting the conclusion on the bitshift? I don't see Windows Update in his previous posts nor any hint to a bitshift. I may be overlooking something so please direct me. :)
 
Well after restoring from my True Image backup I was able to play Arma2OA and DCS World last night fine. Today however, ARMA2OA is crashing on loading again but I can play DCS World OK. I can't think of anything I've changed since last night so I have no idea what's going on. I booted to XP and Arma2OA loaded fine there.
 
Hi Vir

Thanks for the advice, I'll grab the crashdumps when I can as advised.

I removed the two RAM sticks furthest away from the CPU socket as I believe the two nearest sockets have to be used first on my board, although I could be wrong about that. As that didn't solve the problem I put them back and did a memtest on the 4 sticks and that didn't reveal any problems.
 
What was the date of your True Image backup image? Was it before you actually started experiencing any problematic symptoms? If so, it smells like hardware failure, in which case I point blame on either the RAM or the Motherboard.
 
It was about two weeks ago and can't say it was before I started experiencing any problems. As my other threads show I had problems with Windows Update a while ago which niemiro helped me fix and more recently, Opera crashing and bringing down Windows Explorer and notification area icons not being reloaded when it was restarted but I certainly didn't have any problems playing games until Sunday.

I was leaning towards hardware failure myself but it's hard to understand how restoring my two week old TI backup could have fixed the problems of games crashing (albeit only for a couple of days) on launch if that was the case. The fact that Arma2OA only crashes under Win7 and not XP could indicate a RAM fault I guess, as obviously XP doesn't have access to the full 16GB. I'll do another memtest overnight anyway.
 
It is possible that the disappearance of crashing was just a coincidence. If it hasn't actually resolved the problem in a somewhat permanent manner, then something is still around that's causing it, and there's a good chance it's hardware. Understand that while it may be the RAM, there are other components that can be at fault here too.

Prime95 shouldn't run for just a few minutes, btw, but a few hours if you want to determine stability. Testing it on Large FFTs also may help.

I'd like to list some elements of the symptoms here just to get my bearings straight. Correct or add wherever necessary:


  • System has been experiencing only user-mode app/service crashes, no deadlocks or BSODs.
  • Symptoms only occur on Win7 and on two separate Win7 installations.
  • Backup image of what is suspected to be prior to symptoms for Windows 7 showed up no symptoms for a couple days then symptoms resurfaced.
  • Symptoms do not occur on XP.
  • Memtest was conducted a number of times for several passes for all 4 sticks, no failures detected.
  • Top 2 RAM modules have been removed, Memtest ran again. No failures detected. Symptoms still occur in userland.
  • Prime95 on 45 minutes on Blend showed up ok.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top