Official eMule-Board: Emule Crashing When Starting On Windows 7 64 Bit - Official eMule-Board

Jump to content


Page 1 of 1

Emule Crashing When Starting On Windows 7 64 Bit

#1 User is offline   Skrybe 

  • Splendid Member
  • PipPipPipPip
  • Group: Members
  • Posts: 107
  • Joined: 07-February 03

Posted 09 December 2011 - 02:52 PM

I've been using Emule for quite some time on this PC running Win7 64bit with no problems. I recently reinstalled Windows 7 64 bit Home Premium on a new SSD and got everything running including Emule (I thought) fine. However it had a couple BSODs and I found out that the new SSD needed a firmware update to fix that *sigh*

Anyway, last BSOD before the firmware update Emule was running when the PC died. Now I can't start Emule. Every time I try I get the windows trouble shooter and it logs an error in the app log. It doesn't even get as far as displaying the Emule splash screen although emule.exe *32 shows up briefly in task manager (along with WER - windows error reporting). I tried running emule as administrator and that didn't help. I tried downloading a fresh version of Emule and dropping it into a new folder and running that (with just the config files from the zip). Same problem. I tried rebooting the PC in between as well. I also tried starting it from a different hard drive (the one where it was originally installed). Always the same error. I've copied the event log in below;

Copy pasted the event log:
--------------------------
Faulting application name: emule.exe, version: 0.50.0.4, time stamp: 0x4bbc81c8
Faulting module name: emule.exe, version: 0.50.0.4, time stamp: 0x4bbc81c8
Exception code: 0xc0000005
Fault offset: 0x00054924
Faulting process id: 0x718
Faulting application start time: 0x01ccb679c9dbdfb2
Faulting application path: C:\Program Files (x86)\eMule\emule.exe
Faulting module path: C:\Program Files (x86)\eMule\emule.exe
Report Id: 088e41f1-226d-11e1-b239-20cf305cb235

And event log from where I tried unzipping and starting a fresh Emule:
----------------------------------------------------------------------
Faulting application name: emule.exe, version: 0.50.0.4, time stamp: 0x4bbc81c8
Faulting module name: emule.exe, version: 0.50.0.4, time stamp: 0x4bbc81c8
Exception code: 0xc0000005
Fault offset: 0x00054924
Faulting process id: 0x188
Faulting application start time: 0x01ccb65262418ba2
Faulting application path: C:\Users\xxxxxx\Desktop\emule\emule.exe
Faulting module path: C:\Users\xxxxxx\Desktop\emule\emule.exe
Report Id: a024d629-2245-11e1-bd89-20cf305cb235

It ran ok before changing HDD to SSD, and it ran on the current SSD before the firmware update. Pretty sure I haven't installed anything besides the firmware update since the last time Emule was running. All other hardware and software was the same Avira Antivirus, Fritz Box router etc. I've also run the windows system file checker just to make sure there are no corrupt system files - everything was fine.

Googling seems to indicate Exception 0xc0000005 is a memory access violation and possibly DEP is preventing the app from running. I don't understand why this would be the case since it was running last week just fine...

Any ideas?
0

#2 User is offline   Skrybe 

  • Splendid Member
  • PipPipPipPip
  • Group: Members
  • Posts: 107
  • Joined: 07-February 03

Posted 10 December 2011 - 03:12 AM

Never mind I figured out the problem. Just in case anyone else has a similar issue and is trying to search here I'll post the solution.

Saved config, searches, known files etc all get saved to C:\Users\<your user name>\AppData\Local\eMule\config under Windows 7 (and probably other versions too). I miss the days when settings got saved in the same folder as the app, or in the registry... *sigh*

Anyway, I moved all the files out of there to a temp folder and tried restarting Emule. It fired up just fine, but with no config, no shared files, incomplete downloads etc. I shut it back down and moved the config files back a couple at a time restarting Emule after each. I started with the ini files since they were human readable and I could see that they looked ok. Turned out the known2_64.met file had been corrupted by the crash. So I left it out and let Emule re-hash the shared files (took a long time). After that it ran just fine, had all my partially complete downloads, saved searches, shared files, categories etc.

This post has been edited by Skrybe: 10 December 2011 - 03:13 AM

0

#3 User is offline   fox88 

  • Golden eMule
  • PipPipPipPipPipPipPip
  • Group: Members
  • Posts: 4974
  • Joined: 13-May 07

Posted 10 December 2011 - 02:59 PM

Congratulations. :)
And two remarks.

View PostSkrybe, on 10 December 2011 - 06:12 AM, said:

I miss the days when settings got saved in the same folder as the app, or in the registry... *sigh*

I'm quite sure you still could get binaries and unpack into something like c:\emule.

View PostSkrybe, on 10 December 2011 - 06:12 AM, said:

known2_64.met file had been corrupted by the crash.

I had a similar issue with one mod, which renamed that file, but used known2_64.met with different structure. Of course, official eMule was failing to start.
In my opinion corrupted data files should not crash applications; so here's something for devs to think about.
0

#4 User is offline   Rocknme 

  • Newbie
  • Pip
  • Group: Members
  • Posts: 7
  • Joined: 31-March 05

Posted 30 August 2016 - 11:17 PM

Skrybe, you are genius. In my case I can't tell if the Known.met file or the known2_64.met file was corrupt because when I moved only one of the two, emule rewrote both files and made them 1k big. They were in my case 1.45MB and 1.19MB respectively. Now they are 1K on my again-working copy of emule.

It is interesting that a .met file corruption will cause emule to GPF. I would think the developers could keep backup copies and run a validity check before allowing a GPF to happen. I found we (back when I was a developer leading developers) even had to do that with helper files including the infamous msvcr redistributable.

Thanks again. You're a pal.
0

  • Member Options

Page 1 of 1

1 User(s) are reading this topic
0 members, 1 guests, 0 anonymous users