Crashed... -1 reply

Please wait...

Seek And Destroy

{FtD} Fighting Till Death

50 XP

21st February 2004

0 Uploads

91 Posts

0 Threads

#1 16 years ago

Whenever I go to open Far Cry all of a sudden I get a black screen, and this error..

FileVersion: 1.1.0.1230 ProductVersion: 1.1.0.1230 Exception Code: 0xC0000005 Exception Addr: 0x001B:0x3804A104 Exception Module: Exception Description: EXCEPTION_ACCESS_VIOLATION, Attempt to read from address 0x00000000 The memory could not be "read" Call Stack Trace: 2) function=0x3804A104 1) function=0x0 anyone know what this means and how I could fix it????




Seek And Destroy

{FtD} Fighting Till Death

50 XP

21st February 2004

0 Uploads

91 Posts

0 Threads

#2 16 years ago

can anyone help me so i can play some more Far Cry?... or at least direct me to some help!?:cya:




SnuFFeh

50 XP

17th March 2004

0 Uploads

3,884 Posts

0 Threads

#3 16 years ago

Try a reinstall dude, thats the sort of thing that will get fixed by a reinstall.




doomer91

GF old man

50 XP

29th December 2003

0 Uploads

686 Posts

0 Threads

#4 16 years ago

Saint right...and thread moved to tech support and help




HummerMan

The Internet ends at GF

50 XP

30th May 2003

0 Uploads

108 Posts

0 Threads

#5 16 years ago

i agree, a reinstall sounds in order... make sure you are using all the up to date drivers on your graphics card and direct x, 9.0C was just released a bit ago




Seek And Destroy

{FtD} Fighting Till Death

50 XP

21st February 2004

0 Uploads

91 Posts

0 Threads

#6 16 years ago

ok I tried a reinstall.. and guess what.. no luck. Might need to do a DirectX update. Anyone else seen this message before??




kermit14319

Slightly cooler than a n00b

50 XP

27th November 2005

0 Uploads

43 Posts

0 Threads

#7 16 years ago

That same thing happens to me! I dont know how to fix it, but I'll try direct x 9.0c (although I think I have it), and a reinstall. Please mail me if you find out whats wrong!




Big Business

GF Pwns Me!

50 XP

11th September 2007

0 Uploads

47 Posts

0 Threads

#8 16 years ago

I had the exact same proble, and what fixed it for me, was installing the patch and turning off (NONE) Antialising!