Crash

Coldplayer · 02-20-2009, 05:11 PM

Problem signature:
Problem Event Name: APPCRASH
Application Name: hl2.exe
Application Version: 0.0.0.0
Application Timestamp: 470c11ae
Fault Module Name: vstdlib.dll
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 4877a5bc
Exception Code: c0000005
Exception Offset: 00001432
OS Version: 6.0.6001.2.1.0.256.1
Locale ID: 3081
Additional Information 1: fd00
Additional Information 2: ea6f5fe8924aaa756324d57f87834160
Additional Information 3: fd00
Additional Information 4: ea6f5fe8924aaa756324d57f87834160

I get that when i start portal and it closes..Also my tf2 stopped working as well. Anyone know whats going on i think its probably because of the recent updates. Im on vista 64bit as well if it matters.

Coldplayer · 02-21-2009, 02:59 AM

buump.....

Mvwill · 02-22-2009, 12:33 PM

Bumping is against the law, contact Gabe Newell and whine.

kgarlow · 04-02-2009, 09:31 AM

I'm getting a similar result with Portal - I see the Valve logo, then the loading screen. After 30 seconds or so of messy display changes (change in resolution, black window with Portal in upper left, desktop, back to black window, back to desktop, etc.), I am notified that HL2.EXE has crashed. Full text appears at bottom.

Here is a summary of my system:
* Windows Vista Home Premium (32-bit)
* 2 GB RAM
* CPU: AMD Turion 64 X2 Mobile TL-60 2 GHz
* video card is ATI X1200

So far, no luck resolving. I've tried the following:
* verified video driver is up-to-date
* verified DirectX, using DXDIAG (have version 10)
* verified CPU supports SSE, using cputext.exe
* added HL2.EXE to Data Execution Prevention
* disabled AVG 8.0 antivirus
* disabled Windows firewall

Grrrr... pretty frustrating.

=====

Problem signature:
Problem Event Name: APPCRASH
Application Name: hl2.exe
Application Version: 0.0.0.0
Application Timestamp: 470c11ae
Fault Module Name: vstdlib.dll
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 4877a5bc
Exception Code: c0000005
Exception Offset: 00001432
OS Version: 6.0.6000.2.0.0.768.3
Locale ID: 1033
Additional Information 1: 8d13
Additional Information 2: cdca9b1d21d12b77d84f02df48e34311
Additional Information 3: 8d13
Additional Information 4: cdca9b1d21d12b77d84f02df48e34311

kgarlow · 04-04-2009, 07:36 AM

I found a resolution to my problem was setting launch properties for Portal. In Steam: My Games, select Portal, click Properties, General, Set launch options.

Here are the two settings that worked for me.

-dxlevel 81 +mat_forcehardwaresync 0

I found that both were required to successfully run the game. Using "-dxlevel 90" didn't work, so I'm sticking with DirectX 8.1.

If you want to try this approach, see the article "Troubleshooting Game Crashes", specifically the section SET GAME LAUNCH OPTIONS AND DISABLE PROBLEMATIC HARDWARE.

"For The Orange Box games (Episode Two, Team Fortress 2 and Portal), please use the following launch option:

-nosound -window -dxlevel 81 +mat_forcehardwaresync 0"

!! Note that the -nosound switch is strictly a troubleshooting step; running the game without sound won't be a fulfilling experience. !! But it might be helpful in determining if sound issues are causing your problem.

Norse_Player · 10-22-2009, 01:59 AM

I found out that by using -window in the start-up settings allows Portal to start up (in windowed mode).
However, if I try to run it 'clean' (after a -autoconfig run), the game crashes ("hl2.exe has stopped working"). If I use -no sound, I can start up and run in full screen mode.

So the culprit is probably the sound drivers in the Nvidia-card on my laptop crashing with the RealTek-sound on the MB when trying to run in full screen mode.

The solution? It's annoying, but livable; start up in window mode (-window), go to Options and choose full screen mode, each time you start up the game. At least it'll work properly.

gorpie · 10-22-2009, 01:55 PM

Quote:

Originally Posted by Mvwill

Bumping is against the law, contact Gabe Newell and whine.

Kinda late, but bumping is not disallowed. The forum rules say "Do not - Bump old threads unless you have a good reason."

gorpie · 10-22-2009, 01:59 PM

Quote:

Originally Posted by Norse_Player

I found out that by using -window in the start-up settings allows Portal to start up (in windowed mode).
However, if I try to run it 'clean' (after a -autoconfig run), the game crashes ("hl2.exe has stopped working"). If I use -no sound, I can start up and run in full screen mode.

So the culprit is probably the sound drivers in the Nvidia-card on my laptop crashing with the RealTek-sound on the MB when trying to run in full screen mode.

The solution? It's annoying, but livable; start up in window mode (-window), go to Options and choose full screen mode, each time you start up the game. At least it'll work properly.

Maybe this should get its very own thread, especially if you want help (sorry, I don't have any answers). Some people will look at the "new post in the thread", but others might not...

I don't know if it will help, but have you looked at the Half-Life 2 forum? I don't know if there are any problems like yours there, but I think it's the same game engine.

nrnoble · 10-22-2009, 10:35 PM

old thread and an old problem that keeps surfacing over and over.

Don't have the task manager running or any other application that wants to be "Always on top". A high percentage of all Hl2.exe crashes can be linked to apps wanting to be "on top"

02-20-2009, 05:11 PM	#1
Coldplayer Join Date: Jan 2009 Reputation: 0 Posts: 180	Crash Problem signature: Problem Event Name: APPCRASH Application Name: hl2.exe Application Version: 0.0.0.0 Application Timestamp: 470c11ae Fault Module Name: vstdlib.dll Fault Module Version: 0.0.0.0 Fault Module Timestamp: 4877a5bc Exception Code: c0000005 Exception Offset: 00001432 OS Version: 6.0.6001.2.1.0.256.1 Locale ID: 3081 Additional Information 1: fd00 Additional Information 2: ea6f5fe8924aaa756324d57f87834160 Additional Information 3: fd00 Additional Information 4: ea6f5fe8924aaa756324d57f87834160 I get that when i start portal and it closes..Also my tf2 stopped working as well. Anyone know whats going on i think its probably because of the recent updates. Im on vista 64bit as well if it matters.

04-02-2009, 09:31 AM	#4
kgarlow Join Date: Apr 2009 Reputation: 0 Posts: 2	Appcrash as well I'm getting a similar result with Portal - I see the Valve logo, then the loading screen. After 30 seconds or so of messy display changes (change in resolution, black window with Portal in upper left, desktop, back to black window, back to desktop, etc.), I am notified that HL2.EXE has crashed. Full text appears at bottom. Here is a summary of my system: * Windows Vista Home Premium (32-bit) * 2 GB RAM * CPU: AMD Turion 64 X2 Mobile TL-60 2 GHz * video card is ATI X1200 So far, no luck resolving. I've tried the following: * verified video driver is up-to-date * verified DirectX, using DXDIAG (have version 10) * verified CPU supports SSE, using cputext.exe * added HL2.EXE to Data Execution Prevention * disabled AVG 8.0 antivirus * disabled Windows firewall Grrrr... pretty frustrating. ===== Problem signature: Problem Event Name: APPCRASH Application Name: hl2.exe Application Version: 0.0.0.0 Application Timestamp: 470c11ae Fault Module Name: vstdlib.dll Fault Module Version: 0.0.0.0 Fault Module Timestamp: 4877a5bc Exception Code: c0000005 Exception Offset: 00001432 OS Version: 6.0.6000.2.0.0.768.3 Locale ID: 1033 Additional Information 1: 8d13 Additional Information 2: cdca9b1d21d12b77d84f02df48e34311 Additional Information 3: 8d13 Additional Information 4: cdca9b1d21d12b77d84f02df48e34311

04-04-2009, 07:36 AM	#5
kgarlow Join Date: Apr 2009 Reputation: 0 Posts: 2	Resolved through "launch properties" I found a resolution to my problem was setting launch properties for Portal. In Steam: My Games, select Portal, click Properties, General, Set launch options. Here are the two settings that worked for me. -dxlevel 81 +mat_forcehardwaresync 0 I found that both were required to successfully run the game. Using "-dxlevel 90" didn't work, so I'm sticking with DirectX 8.1. If you want to try this approach, see the article "Troubleshooting Game Crashes", specifically the section SET GAME LAUNCH OPTIONS AND DISABLE PROBLEMATIC HARDWARE. "For The Orange Box games (Episode Two, Team Fortress 2 and Portal), please use the following launch option: -nosound -window -dxlevel 81 +mat_forcehardwaresync 0" !! Note that the -nosound switch is strictly a troubleshooting step; running the game without sound won't be a fulfilling experience. !! But it might be helpful in determining if sound issues are causing your problem.

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
CRASH CSS SERVERS! HELP!!!	sNeeP	Counter-Strike: Source	5	05-10-2009 08:34 AM
How to not crash (CTD) and still have Factionwar (by Havoc1234)	Draken	S.T.A.L.K.E.R. series	12	10-07-2008 08:07 AM
CSS DS Crashes	trashmasterFX	Source DS (Linux)	8	01-28-2007 08:29 PM

02-21-2009, 02:59 AM	#2
Coldplayer Join Date: Jan 2009 Reputation: 0 Posts: 180	buump.....

02-22-2009, 12:33 PM	#3
Mvwill Join Date: Feb 2008 Reputation: 10 Posts: 296	Bumping is against the law, contact Gabe Newell and whine.

10-22-2009, 01:59 AM	#6
Norse_Player Join Date: Aug 2006 Reputation: 14 Posts: 117	I found out that by using -window in the start-up settings allows Portal to start up (in windowed mode). However, if I try to run it 'clean' (after a -autoconfig run), the game crashes ("hl2.exe has stopped working"). If I use -no sound, I can start up and run in full screen mode. So the culprit is probably the sound drivers in the Nvidia-card on my laptop crashing with the RealTek-sound on the MB when trying to run in full screen mode. The solution? It's annoying, but livable; start up in window mode (-window), go to Options and choose full screen mode, each time you start up the game. At least it'll work properly.

10-22-2009, 10:35 PM	#9
nrnoble Join Date: May 2008 Reputation: 6 Posts: 364	old thread and an old problem that keeps surfacing over and over. Don't have the task manager running or any other application that wants to be "Always on top". A high percentage of all Hl2.exe crashes can be linked to apps wanting to be "on top"