Temporary fix for my CTD, is ~e5.0001 the cause?

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • eastcoasthandle

    #1

    Temporary fix for my CTD, is ~e5.0001 the cause?


    Explanation of the problems I am having


    Here is what I have found so far. I know for a fact that the file named ~e5.0001 will load up with BF2 loads up. It will stop BF2 from running if !e5.0001 fails to operate. This ~e5.001 file is only seen in processes of window manger during BF2 and is found C:\...\Local Settings\Temp. However, when you use programs that affect virtual memory such as memory tweaking program like MemSet (what I use) and A64 Tweaker and other XP tweaks that affect this ~e5.0001 file you have problems. It appears that this ~e5.0001 file is some sort of cd-copy protection program…of sorts??

    I was able to replicate CTD at will by tweaking my memory until it was no longer stable. I have made 7 successful trials of replicating the CTD when I push the join button of a server with unstable memory tweaks. When memory is stable (tweaked or otherwise) I am able to enter the server with no problems (NO CTDs using patch 1.30). This in no way suggests that you have a memory problem. I am only stating this to imply that I have been able to replicate the problem through other means (unstable memory through mem tweaker program) that appear similar to what I experience every time I hit the join button (1 out of every 3 tries w/o tweaking my memeory) This only suggests that something in virtual memory is missing up BF2 or something preventing this ~e5.0001 from functioning properly. (~e5.0001 file is damage??) This only appears to happen when it's resident in memory. And, even though other games have problems with unstable memory I am not kicked to desktop.

    This to me is the key difference when having computer problems with and without this ~e5.0001 file in virtual memory. I may have stumbled upon why we are having problems with freezing (maybe more memory related then ~e5.0001 related) and CTD. However, I have only verified this problem with my system. This by no means, a solution for all so please don’t interrupt this that way. Also note that the patch may or may not have corrupted pagefile somehow.

    Solution that work from my system

    It was suggested to me to update my version of SafeDisc here. <---place your mouse here (over the words "SafeDisc here"

    I also set my pagefile to delete on shutdown. This is an extreme measure as this "may" only need to be done once. However, so far after 12+ rounds and 4+ startups of BF2 I have yet to have a single CTD. I have on 2 occasions been kicked from servers do to crashes (in which you are kicked back to BF2’s browser, upon return to the server you see “Need X amount of people…)

    Here is what I did to clear the pagefile:

    -Click on start
    -Click on run
    -Type is regedit then hit the enter key
    -You are now inside your registry you want to go to: HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management
    -Then you want to look for:
    clearpagefileatshutdown 0
    -Right click on the word, select modify then enter 1 in place of 0 then hit enter.
    -Clearpagefileatshutdown 1 <--it should now look like this.
    -Reboot
    -Play BF2 <-or you can change it back to 0 something I haven't done yet

    Is it possible that enable or disabling this copy protection reduces CTD? I don't know as I can only speak for my system at the moment.

    Does the pagefile have anything to do with BF2? I cannot say for certain all I know is by doing the above I no longer CTD (it's been roughly 32 hours so far vs. CTD every 3 server I join). I am sure people can debate the functionality between the ~e5.0001 file and pagefile but truth be told for me, its working so what can I say?
  • scrogathon

    #2
    Re: Temporary fix for my CTD, is ~e5.0001 the cause?

    same file loads when i play bf2 too.

    Comment

    • Talus
      Member
      • Oct 2006
      • 6854

      #3
      Re: Temporary fix for my CTD, is ~e5.0001 the cause?

      It's the copy protection.

      Running BF2 using a mini-image or full image completely removes all problems with the copy protection.

      Akses VIRUS88 sebagai agen Slot88 resmi dan terpercaya 2026 dengan game gacor terbaru, proses praktis, promo harian menarik, serta layanan online 24 jam.

      Comment

      • eastcoasthandle

        #4
        Re: Temporary fix for my CTD, is ~e5.0001 the cause?

        Originally posted by Talus
        It's the copy protection.

        Running BF2 using a mini-image or full image completely removes all problems with the copy protection.

        http://www.totalbf2.com/forums/showthread.php?t=54305
        Thanks for the heads up. Is it plausible that the mini image is simply tricking the ~e5.0001 to reading the HD vs. cd/dvd rom thus still a needed program? Is this ~e5.0001 still loaded into mem when BF2 starts (ctrl-alt-dlt) in the windows task manager's processes? If it does that would be a strong indicator.

        Comment

        • BadToad

          #5
          Re: Temporary fix for my CTD, is ~e5.0001 the cause?

          Interesting theory. I do know that when I end-task that program, it crashes BF2 completely, so I wonder, like you, is that program present when using a mini-image...

          Comment

          • eastcoasthandle

            #6
            Re: Temporary fix for my CTD, is ~e5.0001 the cause?

            If you want BF2 to CTD on command all you need to do is start BF2 enter a server, spawn then hit CTRL-ALT-DEL then end process for ~e5.0001 and you will officially end BF2 or CTD. However you will already be back at desktop therefore the icon on your taskbar should disappear.

            What's causing the CTD when you push the Join button or when you already playing and suddent CTD is still unknown to me. However, I believe for whatever reason there is a break down in communication through virtual memory between BF2 and this ~e5.0001 file.

            I have played a couple more servers and no problems. I lost count on total servers because I haven't had a single CTD in the last (nearly) 36 hour or so. Has anyone tried this??

            Comment

            • lynxlyran

              #7
              Re: Temporary fix for my CTD, is ~e5.0001 the cause?

              I tried it and it seems to work. Thanks!

              Comment

              • eastcoasthandle

                #8
                Re: Temporary fix for my CTD, is ~e5.0001 the cause?

                Originally posted by lynxlyran
                I tried it and it seems to work. Thanks!
                Thanks for the confirmation, at least I know it's not just my computer

                Can someone else please try this and see if it works for you. Please?

                Comment

                • Sir. MatDef
                  Member
                  • Sep 2005
                  • 2899

                  #9
                  Re: Temporary fix for my CTD, is ~e5.0001 the cause?

                  I tried, didn't work.

                  Comment

                  • Talus
                    Member
                    • Oct 2006
                    • 6854

                    #10
                    Re: Temporary fix for my CTD, is ~e5.0001 the cause?

                    Originally posted by lynxlyran
                    I tried it and it seems to work. Thanks!
                    What I'D like to know..is what it is exactly that you tried.

                    Comment

                    • lynxlyran

                      #11
                      Re: Temporary fix for my CTD, is ~e5.0001 the cause?

                      -Click on start
                      -Click on run
                      -Type is regedit then hit the enter key
                      -You are now inside your registry you want to go to: HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management
                      -Then you want to look for:
                      clearpagefileatshutdown 0
                      -Right click on the word, select modify then enter 1 in place of 0 then hit enter.
                      -Clearpagefileatshutdown 1 <--it should now look like this.
                      -Reboot
                      -Play BF2 <-or you can change it back to 0 something I haven't done yet


                      I have not crashed joining a server since I did this. I also set it back to 0 after I rebooted.

                      Comment

                      • Sheik Yerbouti

                        #12
                        Re: Temporary fix for my CTD, is ~e5.0001 the cause?

                        Originally posted by lynxlyran
                        -Click on start
                        -Click on run
                        -Type is regedit then hit the enter key
                        -You are now inside your registry you want to go to: HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management
                        -Then you want to look for:
                        clearpagefileatshutdown 0
                        -Right click on the word, select modify then enter 1 in place of 0 then hit enter.
                        -Clearpagefileatshutdown 1 <--it should now look like this.
                        -Reboot
                        -Play BF2 <-or you can change it back to 0 something I haven't done yet


                        I have not crashed joining a server since I did this. I also set it back to 0 after I rebooted.
                        Didn't help at all, thanks though. This has ****ed me off so much. I haven't played 1 minute of Armoured fury and EA has be zero help. I've uninstalled and reinstalled. Every other aspect of BF2 works fine.

                        Comment

                        Working...