Yep, you can use that one ;)
Looking at your error log, NONE of those errors have anything to do with the repack's files. Here's my suggestion.
1. Check the amount of space on your hard drive.
Code:
CRITICAL ERROR.
Couldn't initialize the symbol handler for process.
Error [Not enough storage is available to process this command.
].
2. Your memory chip may be going bad, again, has nothing to do with the repack.
Code:
Exception code: E06D7363
Fault address: 763642EB 01:000432EB C:\Windows\system32\kernel32.dll
3. Uninstall/reinstall the Visual C++ runtimes and the .NET Framework 3.5
4.
Code:
772B9A94 00000000 0001:00058A94 C:\Windows\system32\ntdll.dll
74F31FC8 00000000 0001:00000FC8 C:\Windows\system32\MSWSOCK.dll
773A1693 00000000 0001:00000693 C:\Windows\system32\WS2_32.dll
...
7637A091 00000000 0001:00059091 C:\Windows\system32\kernel32.dll
6B678ED9 00000000 0001:00067ED9 C:\Windows\WinSxS
You may have some corrupt files in your Windows Installation, which could be caused by a large of amount of fragmentation. I would suggest:
a. Run CCleaner (with CCenhancer)
b. Run Eusing Free Registry Cleaner
c. Run Defraggler
5.
Code:
This application has requested the Runtime to terminate it in an unusual way.
...
6B633433 00000000 0001:00022433 C:\Windows\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.4974_none_50940634bcb759cb\MSVCR90.dll
6B6334C7 00000000 0001:000224C7 C:\Windows\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.4974_none_50940634bcb759cb\MSVCR90.dll
This can also be caused by a corrupt installation of Visual C++ runtimes.
And the BIGGEST problem of them all...
Code:
*** Operation System ***
Windows Vista
Update Compiling:
Code:
MaNGOS updated to 10438
Acid Scripts Updated to 36