File Server - Recode or fix bugs?

I have been trying to have a project of mine completed. It seems I have a hard time finding good coders, because I keep running into issues. I am wondering if it is better for me to start over or have my app reviewed to be fixed. My app has many features in it, but the app is flawed. The app is a File server and a client side app that can receive files and keep folders, programs or games up to date. I have a feeling the freelancer I hired to do this project might of coded this them self or used released/someone else launcher. I can be wrong, but either way I have many issues that I was able to hire another coder to fix, but was unable to fix other issues. The current issue with this app: I have the last set of files the coder gave me before he was banned from the freelancer website(Not from me). Sadly I am unable to speak to him any more and he stopped replying to me after I was trying to get an update stats about this crashing issue with the file server. So the file server was able to run for 1 day, 3 days, maybe a week and then it would crash. He added logging to it and it was showing a bad packet, but he was unable to track it down and more or less gave up. Fast forward to today, I am trying to compile his source code that he last gave me and its giving me errors at this time. One coder quoted me 700$, he proposed he would fix the compile on the source, read and debug the client/source and give a proposal of log improvement and a stress tool to try and reproduce the bug again. Would also improve the logs, and then try to fix the bug. My question is do you think it would be better to have this projected recoded or have the current bug(and future bugs) worked on. Would you be interested in this project, if so what are your thoughts and quote? Features: *Programmed in C++ MFC. *xdelta- Let's say the user has a 100mb file and we update that file, making it 101mb now. The user would only need to download the 1mb difference to update their file. Saves time and bandwidth [login to view URL] *Launcher Updater - If the launcher detects that it has an update, it will update its self without the user needing to do anything. It detects a new version number and then updates itself. *Can make the launcher run any program in the root folder after the user presses "Play" *Login - This connects to a server and confirms the users log in. And has a save option *Settings that change values client-side in a txt file *Able to change the visual pictures of the launcher with ease. This includes the Login, The *Patching and the final Play button with all the hyperlinking boxes *Server uses DNS instead of IP so the player will never need to update this information if the server needs to be moved.