Posted: Wed Nov 27, 2013 9:22 pmHi all....I do hope you can help here. Fresh install of windows 7 64bit...upto date tried new and also rolled back graphics still no luck. Anyone had similar experience...overclocking rolled back too
Page 1 of 1
Posted: Wed Nov 27, 2013 9:22 pmPosted: Wed Nov 27, 2013 9:43 pmNo expert here , fresh install of OS Win7 , was the HD reformated , or was it a repair re-install?
Posted: Thu Nov 28, 2013 11:30 amHiya...full reformat. No other drives present during install.... cheers 
Posted: Thu Nov 28, 2013 7:27 pmCan you supply a bit more detail regarding the problem.
Posted: Thu Nov 28, 2013 8:25 pmwairoaboy wrote:QUOTE (wairoaboy @ Nov 27 2013,10:22 PM) <{POST_SNAPBACK}>Hi all....I do hope you can help here. Fresh install of windows 7 64bit...upto date tried new and also rolled back graphics still no luck. Anyone had similar experience...overclocking rolled back too
Know the feeling, had to roll my NVIDIA drivers back to the one I had in January to get the system stable again. Not sure why that should be but if that's what it takes then I guess that's what has to be done.
Posted: Thu Nov 28, 2013 10:03 pmrocky289 wrote:QUOTE (rocky289 @ Nov 28 2013,8:27 PM) <{POST_SNAPBACK}>Can you supply a bit more detail regarding the problem.
Hi Rocky....the head is a bit knumb but heres the gst of it
Posted: Fri Nov 29, 2013 8:44 amIs it ok if you don't use the DX10 setting?
Posted: Fri Nov 29, 2013 3:57 pmI had a similar, although less severe, issue that I fixed by completely uninstalling my AMD drivers (including Catalyst). I was expecting to have to do a reinstall in order to get anything other than very rudimentary video support. As it turned out the out of the box Windows driver worked fine and I didn't have an obvious decrease in FPS. I only mention this as your problem appears to be video card/driver related.
Upon further investigation the driver that ended up being used was a AMD video driver (albeit one that was about 12 months old). I was using the latest version from the AMD website. I have not tried to upgrade to a newer AMD driver (with or without Catalyst) as there seems little point at this stage. I suspect the answer might be different for something that uses the features of the video card (eg Prepar3d v2).
BTW: I am using an AMD 7770 video card (ie relatively recent) and the error I was getting was something called a "BEX error". It appears that a BEX error is a somewhat vague thing. Other FSX users claim they have fixed it by doing everything from turning off DEP to sacrificing a virgin. Ok I made the last one up, but you get the picture. None of those solutions worked for me.
Upon further investigation the driver that ended up being used was a AMD video driver (albeit one that was about 12 months old). I was using the latest version from the AMD website. I have not tried to upgrade to a newer AMD driver (with or without Catalyst) as there seems little point at this stage. I suspect the answer might be different for something that uses the features of the video card (eg Prepar3d v2).
BTW: I am using an AMD 7770 video card (ie relatively recent) and the error I was getting was something called a "BEX error". It appears that a BEX error is a somewhat vague thing. Other FSX users claim they have fixed it by doing everything from turning off DEP to sacrificing a virgin. Ok I made the last one up, but you get the picture. None of those solutions worked for me.
Posted: Sun Dec 01, 2013 10:55 amgdavies wrote:QUOTE (gdavies @ Nov 29 2013,4:57 PM) <{POST_SNAPBACK}>I had a similar, although less severe, issue that I fixed by completely uninstalling my AMD drivers (including Catalyst). I was expecting to have to do a reinstall in order to get anything other than very rudimentary video support. As it turned out the out of the box Windows driver worked fine and I didn't have an obvious decrease in FPS. I only mention this as your problem appears to be video card/driver related.
Upon further investigation the driver that ended up being used was a AMD video driver (albeit one that was about 12 months old). I was using the latest version from the AMD website. I have not tried to upgrade to a newer AMD driver (with or without Catalyst) as there seems little point at this stage. I suspect the answer might be different for something that uses the features of the video card (eg Prepar3d v2).
BTW: I am using an AMD 7770 video card (ie relatively recent) and the error I was getting was something called a "BEX error". It appears that a BEX error is a somewhat vague thing. Other FSX users claim they have fixed it by doing everything from turning off DEP to sacrificing a virgin. Ok I made the last one up, but you get the picture. None of those solutions worked for me.
Ahh yes, I recall something along the lines of Maybe nspector been changed or a profile deleted around the same time. Although have done driver install but not tried nspector. One thing of note, dx9 is fine...when that first plane that opos up and whirls around, in dx10 mode its pretty much missing...maybe a couple black pieces that's about it.rocky289 wrote:QUOTE (rocky289 @ Nov 29 2013,9:44 AM) <{POST_SNAPBACK}>Is it ok if you don't use the DX10 setting?
Im curious to see how these new tweaks go that are currently all the buzzalthough it could well do the head in
With your setup I wouldn't use any tweaks.
It shouldn't need any as long as you are not running other apps in the background.
I run all default settings.
Only have issues when when I tweak.
I tried the DX10 lock but it made mine unstable & things appear out of proportion.
Well you wouldn't read about it!! Was fiddling around last-night and finally got around to connecting SLI connection to Graphics cards.....and would you believe it...no more CTD in DX10 mode!!! Who can understand these gremlins that crop up from time to time....would never have thought an SLI connection would have affected it
Yip .. the amount of funky chickens .. and as funky as they are can really cook ya chook
