Application Error - Cannot repair member file

oneutd

New member
Joined
Mar 24, 2014
Posts
3
While running the EXE file for an application I get the Application Error. While checking online to find a solution I found out about SFC. As per the instructions I have taken I dump of the sfc details. Please find attached.

Please help me resolve the error. I tried loading the drivers for my ATI Radeon HD 7550M/7650M Graphics but to no avail.
 

Attachments

Hello, and welcome to Sysnative!

  1. Press the Windows Key on your keyboard and X to open up the Power User Tasks Menu
  2. Click (or tap) Command Prompt (admin)
  3. When command prompt opens, copy and paste the following commands into it, press enter after each

    DISM.exe /Online /Cleanup-image /Restorehealth

    Wait for this to finish before you continue (approximately 15-20 minutes)

    sfc /scannow
    Wait for this to finish before you continue (approximately another 15 minutes)

DISM should be able to fix your particular corruption, but please check that SFC runs clear.

Next, please copy word for word the application error message you are receiving, and for what program.

Thank you.

Richard
 
hey niemiro, thanks for the suggestion. It worked and SFC runs clear now. The original error was when I run FM2014. The error I get after running the exe file for FM2014 is "Application Error: A serious error was encountered and the application will close. An error file has been generated in: C:\Users........\FM 2014 v14.2.1.454037 (2014.03.26 03.00.47).dmp"
 
Using the Windows De-bugging tool I could read the dmp file and it had:-
Microsoft (R) Windows Debugger Version 6.3.9600.16384 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.




Loading Dump File [C:\Users\VISHY\Documents\Sports Interactive\Football Manager 2014\crash dumps\FM 2014 v14.2.1.454037 (2014.03.26 04.33.53).dmp]
User Mini Dump File: Only registers, stack and portions of memory are available


Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
Windows 8 Version 9200 MP (4 procs) Free x86 compatible
Product: WinNt, suite: SingleUserTS Personal
Machine Name:
Debug session time: Wed Mar 26 04:33:53.000 2014 (UTC + 5:30)
System Uptime: not available
Process Uptime: 0 days 0:00:09.000
................................................................
............
This dump file has an exception of interest stored in it.
The stored exception information can be accessed via .ecxr.
(17e4.e50): Access violation - code c0000005 (first/second chance not available)
*** WARNING: Unable to verify timestamp for ntdll.dll
*** ERROR: Module load completed but symbols could not be loaded for ntdll.dll
eax=00000000 ebx=08d04f05 ecx=0923f110 edx=006f0064 esi=00000794 edi=0bbeed1c
eip=7799e9e4 esp=0bbee2d0 ebp=0bbee2dc iopl=0 nv up ei pl nz ac po nc
cs=0023 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00200212
ntdll+0x2e9e4:
7799e9e4 c20800 ret 8
 
Hello oneutd,

I can't offer any assistance with your problem as I am currently enrolled in the Windows Update Academy and don't yet have the required knowledge. I can, however, help you with that pesky error you have in WinDBG :smile9:

The error you are receiving means that you haven't installed the "Symbol File Path" yet, so let's do that:

  1. Please open WinDBG.
  2. Click on File and then on Symbol File Path .... this will open a new window.
  3. Enter the following under Symbol path:
    SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
  4. Click on Ok and close WinDBG.
  5. You will recieve a promp asking you if you want to save your workspace, checkmark the box next to Don't ask again and click on Accept / Yes.
    This will save the symbol file path in WinDBG so that you will never get the Symbol search path is invalid error again.

Good luck,
Nommy
 
In this particular case there should be no need to actually set the symbol path. We already have the exception code (0xc0000005), and this coupled with a couple of other facts is all we need to know in order to determine next steps:

1) the symbols for Football Manager 2014 are not available for us. We cannot do analysis on where the access violation occurred or what exactly caused it. We would need to set the Microsoft Symbol path to do this but a) we'd do it on our own computer and b) we still need those Football Manager 2014 symbols, which we don't have
2) an access violation is almost always a software bug, but can very occasionally be hardware related. If it were hardware related, we would be seeing variety and a random nature. What we actually see is a null deference (I'm assuming deference on the accumulator register (eax), which is very reasonably given a )it's data and b) faulting instruction of ret 8) on a single application. We therefore conclude software on a variety of grounds.
3) Now that we've concluded software, we think about what we can do to fix the issue. Either it's a bug in the application, or it's some fault with this computer. Without the software being open source, it's very difficult to be absolutely certain, but with a null dereference failure, I think it's pretty safe to say it's a software bug.
4) So what's the fix? We get the OP to check for an update for the game. If that doesn't fix it, we get the OP to take a full process dump (if a reasonably size, which for a game it may not be) through the correct architecture Task Manager. We then get the OP to upload it to us, we quickly confirm that there's nothing we can diagnose without symbols (i.e. there's not some obviously weird conflict going on between graphics card driver), then they open a support ticket with the game maker, uploading the full dump file so the developers can take a look at what's going on with the source code.

Fixing the symbol error should not be necessary for any of those steps. I may be a Windows Update specialist, but the forum specialises in BSOD debugging and clearly something's rubbed off :p We also like sharing methods here so that a) others can learn and b) I can be corrected by the better BSOD debuggers here, because I'm really bad compared to them! (I would like to think that it's not me who's terrible, but they who are amazing, but who am I to judge?). Anyway, I'm getting massively off topic now :)

@oneutd: please check for a game update/patch for Football Manager 2014.

Richard
 
Thanks for the great analysis Richard!
Do note that I was merely trying to help the OP with fixing the symbol file path, as this error would be present in any dump file he'd open as .symfix only lasts one session to my knowledge.


Nommy
 
Hi,

oneutd - can you please zip up and upload the dump file to your next post as well please?

Thanks,
Stephen
 
Back
Top