DoD don't work at all.

Duckthis · 01-25-2009, 07:22 PM

When I start DoD, it opens, run for like 2 seconds, and close. No error message.

I made a video so you can see whats happening

http://ca.youtube.com/watch?v=7P6CklDAYrc

Counter Strike 1.6 works fine, but Half-Life and DoD 1.3 don't.

Things tried:
-Reboot
-Restart Steam
-Clear cache
-Uninstall/reinstall the game
-Uninstall/reinstall Steam
-Set priority to High
-Allow on firewall

Other things I should try?

I am desesperate...

Limes!! · 01-26-2009, 03:01 PM

I'm having the exact same problem, and I've tried all of the above. Please, help!

Limes!! · 01-26-2009, 03:49 PM

Also, whenever I boot my computer, I get 2 errors from Steam, which is odd because Steam isn't even on Startup: Both of them say Unable to perform action or something because the game is already running. I believe this is causing the problem.

Drag0nZorD! · 02-12-2009, 11:26 AM

i have the same issue, its very annoying.

i just want to play

Amaterasu · 02-17-2009, 02:28 PM

I quite recently encountered someone who was having the same problem as you. He even posted a link to the exact same youtube video as you.

He was running Windows Vista and the problem turned out to be data execution prevention (DEP). If you are running Vista (I assume this could also arise for those using the Windows 7 Beta) it could well be that DEP is enabled on your system, and that if you change your settings DoD will rune fine.

Go into advanced system properties --> performance options --> DEP tab as shown below.
http://www.self-preservation-society.../vista-dep.jpg

I'm guessing yours is set to "Turn on DEP for all programs". If it is then changing it to "Windows programs and services only" as shown and rebooting will enable DoD to run properly (DoD crashes in EXACTLY the manner shown in the youtube when DEP is enabled).

If that works for you then you know DEP was the problem. I should then point out that the solution I gave you was a really lazy, quick-fix. DEP is a good thing, and the smart thing to do is to set it back to "Turn on DEP for all programs" and add "C:\Program Files\Steam\steamapps\account\Day of Defeat\hl.exe" to the list of DEP-exempt programs.

However, if that isn't the cause of the problem then I'd suggest looking at the dump file DoD creates when it crashes as you may be able to glean some information from there about the cause of the crash.

The dump file will be in your "c:\Program Files\Steam\steamapps\accountname\Day of Defeat" folder, with the extension .mdmp. You can use the app WinDbg from the Windows Debugging Tools (32bit version, 64bit version) to help make sense of the dump files. It might also be worth checking your system event logs to see if anything is written there.

01-25-2009, 07:22 PM	#1
Duckthis Join Date: Jul 2008 Reputation: 0 Posts: 27	DoD don't work at all. When I start DoD, it opens, run for like 2 seconds, and close. No error message. I made a video so you can see whats happening http://ca.youtube.com/watch?v=7P6CklDAYrc Counter Strike 1.6 works fine, but Half-Life and DoD 1.3 don't. Things tried: -Reboot -Restart Steam -Clear cache -Uninstall/reinstall the game -Uninstall/reinstall Steam -Set priority to High -Allow on firewall Other things I should try? I am desesperate... Last edited by Duckthis : 01-25-2009 at 07:28 PM.

Thread Tools
Show Printable Version Email this Page
Display Modes	Rate This Thread
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode	Rate This Thread:

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
DoD and Gmod Crashing HELP!!	Wally77	Help and Tips	2	12-22-2008 05:22 PM
DOD wont work	pernopalie	Help and Tips	2	03-31-2008 06:58 AM
DOD Server Startup Failure	ChandlerZ	Half-Life DS (Linux)	5	01-29-2005 06:05 AM

01-26-2009, 03:01 PM	#2
Limes!! Join Date: Jan 2009 Reputation: 0 Posts: 2	I'm having the exact same problem, and I've tried all of the above. Please, help!

01-26-2009, 03:49 PM	#3
Limes!! Join Date: Jan 2009 Reputation: 0 Posts: 2	Also, whenever I boot my computer, I get 2 errors from Steam, which is odd because Steam isn't even on Startup: Both of them say Unable to perform action or something because the game is already running. I believe this is causing the problem.

02-12-2009, 11:26 AM	#4
Drag0nZorD! Join Date: Aug 2008 Reputation: 26 Posts: 394	i have the same issue, its very annoying. i just want to play

02-17-2009, 02:28 PM	#5
Amaterasu Join Date: Feb 2009 Reputation: 2 Posts: 9	I quite recently encountered someone who was having the same problem as you. He even posted a link to the exact same youtube video as you. He was running Windows Vista and the problem turned out to be data execution prevention (DEP). If you are running Vista (I assume this could also arise for those using the Windows 7 Beta) it could well be that DEP is enabled on your system, and that if you change your settings DoD will rune fine. Go into advanced system properties --> performance options --> DEP tab as shown below. http://www.self-preservation-society.../vista-dep.jpg I'm guessing yours is set to "Turn on DEP for all programs". If it is then changing it to "Windows programs and services only" as shown and rebooting will enable DoD to run properly (DoD crashes in EXACTLY the manner shown in the youtube when DEP is enabled). If that works for you then you know DEP was the problem. I should then point out that the solution I gave you was a really lazy, quick-fix. DEP is a good thing, and the smart thing to do is to set it back to "Turn on DEP for all programs" and add "C:\Program Files\Steam\steamapps\account\Day of Defeat\hl.exe" to the list of DEP-exempt programs. However, if that isn't the cause of the problem then I'd suggest looking at the dump file DoD creates when it crashes as you may be able to glean some information from there about the cause of the crash. The dump file will be in your "c:\Program Files\Steam\steamapps\accountname\Day of Defeat" folder, with the extension .mdmp. You can use the app WinDbg from the Windows Debugging Tools (32bit version, 64bit version) to help make sense of the dump files. It might also be worth checking your system event logs to see if anything is written there.