Ali Dec 29, 2012 @ 5:13pm
Win8 64bit crash on start: Unhandled Exception c0000005
Hey there, so I was just gifted this and it crashes on start with the error:

Unhandled Exception: c0000005 at address 006f5330

Anyone had any experience of this or even found a solution?

(I've tried compat. mode for XPSP3 as well as a DEP exception, no luck for either)
Showing 1-15 of 16 comments
< >
moparownsyou Dec 29, 2012 @ 6:46pm 
I'm having the same problem. No clue why.
Dib's UK ™ Dec 29, 2012 @ 9:59pm 
iMatrix7 Dec 30, 2012 @ 12:50am 
Same problem here! :(
Ali Dec 30, 2012 @ 5:57am 
Originally posted by Dilbert UK:
Have a look here this may help http://forums.steampowered.com/forums/showthread.php?t=1311695

Yeah, thanks Dilbert, but I already tried the DEP exception :(
AbstractRealist Dec 30, 2012 @ 6:55am 
I have Win8 64 and the only issues I'm experiencing are the mouse ones...so I don't think it's inherently Win8 that's the issue. Might be a graphics card issue or something else.
Ali Dec 30, 2012 @ 7:00am 
Well I'm on an nVidia GTX560Ti anyone else with the issue on nVidia?
Sinical Dec 30, 2012 @ 8:13am 
I'm getting the same error on windows 7.

I get no sound from my character, only background/music. When I try and go to audio setup I get the crash.

As to the person above me, I'm using NVIDIA GeForce 315M. So might possibly be a cause. Idk.
Dib's UK ™ Dec 30, 2012 @ 8:36am 
Have you all verfiy files and google the issue and you may get more answers, hope you get it working.
timeimp Jan 1, 2013 @ 9:57pm 
All the Google discussions point to:
1) Update Drivers
2) Delete .set file in Documents\GTA-VC folder
3) Uninstall and Reinstall game
4) Set Compat mode to XP or earlier
5) Add gta-vc.exe to DEP Exemptions List.

Hopefully Rockstar will take a look at this issue soon, I as I am having troubles with this error message too (Win 7, 64-bit)
emulpc May 3, 2013 @ 11:43am 
Same problem here...
Xava Aug 24, 2013 @ 10:15am 
Same Problem.
Keine Lust Dec 24, 2013 @ 10:51am 
Same Problem.
GalacticPond Jan 15 @ 1:21pm 
This is what an unhandled exception is=

Microsoft "This event provides notification of uncaught exceptions. It allows the application to log information about the exception before the system default handler reports the exception to the user and terminates the application. If sufficient information about the state of the application is available, other actions may be undertaken — such as saving program data for later recovery. Caution is advised, because program data can become corrupted when exceptions are not handled.



NoteNote


In the .NET Framework versions 1.0 and 1.1, application termination and debugging options are reported to the user before this event is raised, rather than after.


This event can be handled in any application domain. However, the event is not necessarily raised in the application domain where the exception occurred. An exception is unhandled only if the entire stack for the thread has been unwound without finding an applicable exception handler, so the first place the event can be raised is in the application domain where the thread originated.



NoteNote


In the .NET Framework versions 1.0 and 1.1, this event occurs only for the default application domain that is created by the system when an application is started. If an application creates additional application domains, specifying a delegate for this event in those applications domains has no effect.


If the UnhandledException event is handled in the default application domain, it is raised there for any unhandled exception in any thread, no matter what application domain the thread started in. If the thread started in an application domain that has an event handler for UnhandledException, the event is raised in that application domain. If that application domain is not the default application domain, and there is also an event handler in the default application domain, the event is raised in both application domains.

For example, suppose a thread starts in application domain "AD1", calls a method in application domain "AD2", and from there calls a method in application domain "AD3", where it throws an exception. The first application domain in which the UnhandledException event can be raised is "AD1". If that application domain is not the default application domain, the event can also be raised in the default application domain.



NoteNote


The common language runtime suspends thread aborts while event handlers for the UnhandledException event are executing.


If the event handler has a ReliabilityContractAttribute attribute with the appropriate flags, the event handler is treated as a constrained execution region.

Starting with the .NET Framework 4, this event is not raised for exceptions that corrupt the state of the process, such as stack overflows or access violations, unless the event handler is security-critical and has the HandleProcessCorruptedStateExceptionsAttribute attribute.

In the .NET Framework versions 1.0 and 1.1, an unhandled exception that occurs in a thread other than the main application thread is caught by the runtime and therefore does not cause the application to terminate. Thus, it is possible for the UnhandledException event to be raised without the application terminating. Starting with the .NET Framework version 2.0, this backstop for unhandled exceptions in child threads was removed, because the cumulative effect of such silent failures included performance degradation, corrupted data, and lockups, all of which were difficult to debug. For more information, including a list of cases in which the runtime does not terminate, see Exceptions in Managed Threads.

To register an event handler for this event, you must have the required permissions, or a SecurityException is thrown.

For more information about handling events, see Consuming Events.

Other Events for Unhandled Exceptions"


For certain application models, the UnhandledException event can be preempted by other events if the unhandled exception occurs in the main application thread.

In applications that use Windows Forms, unhandled exceptions in the main application thread cause the Application.ThreadException event to be raised. If this event is handled, the default behavior is that the unhandled exception does not terminate the application, although the application is left in an unknown state. In that case, the UnhandledException event is not raised. This behavior can be changed by using the application configuration file, or by using the Application.SetUnhandledExceptionMode method to change the mode to UnhandledExceptionMode.ThrowException before the ThreadException event handler is hooked up. This applies only to the main application thread. The UnhandledException event is raised for unhandled exceptions thrown in other threads.

Starting with Microsoft Visual Studio 2005, the Visual Basic application framework provides another event for unhandled exceptions in the main application thread. See the WindowsFormsApplicationBase.UnhandledException event. This event has an event arguments object with the same name as the event arguments object used by AppDomain.UnhandledException, but with different properties. In particular, this event arguments object has an ExitApplication property that allows the application to continue running, ignoring the unhandled exception (and leaving the application in an unknown state). In that case, the AppDomain.UnhandledException event is not raised.








This is how to fix it.
GalacticPond

-Go to Control Panel
-Go to Programs and Features
-Go to the sidebar where it says "Turn Windows Features On or Off" (Or something to that
effect)
-Wait for the list to load
...
-Like a folder, next to each folder is a box. Each folder contains a subfolder.
If no subfolder is checked, the box should be empty
If some subfolders are checked, the box should have a black square.
If all subfolders are checked, the box should have a check.

-Go through all the folders and check them until all boxes are checked.
-Restart your computer as features required are applied.

-Shoot and Rob away at Gta VC
Ali Jan 16 @ 11:43am 
That's not a real fix and I doubt it will work at all, most of the disabled features are server programs or media additions. Also, we didn't really need the full definition of unhandled exceptions...

I'm sorry to say that I have had VC working on my PC (win8) but I can't remember the fix, it may have been disabling DEP across the entire system but I can't quite remember.
:::... FulV@l ...::: [LMHT] Jan 21 @ 2:31pm 
try windows 98 compatibility mode (if you are using windows vista or 7 disable visual themes and aero composition)
Showing 1-15 of 16 comments
< >
Per page: 15 30 50