It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
During the prologue, everything went perfect, but as soon as chapter 1 started the crashing keeps occuring. Can't fully enjoy the game without it crashing to the desktop. Then there are times when I push the "esc" key, meditate, and talking to people, the game will crash to the desktop.
Same here. Not a single crash in the tutorial (with all the graphic intensity of the siege) and then crashes to desktop every 5 minutes in Flotsam. This happens always (?) on cell change or when exiting one of the UI windows.
Post edited May 18, 2011 by Megarelix
avatar
starocean37: During the prologue, everything went perfect, but as soon as chapter 1 started the crashing keeps occuring. Can't fully enjoy the game without it crashing to the desktop. Then there are times when I push the "esc" key, meditate, and talking to people, the game will crash to the desktop.
Yep, started happening with me when you are still in that arrow-blocking magical bubble nearing the town. I've tried different drivers for video and such, no clue. Prologue had no crashes or bugs.
If I remember right, it srarted under the shield bubble, too.

As usual, support FAQ points us towards "install newest drivers, defrag HD, disable antivirus" excuses. Well, just in case I did all of these, to no avail. My specs are OK: ATI 5800 series, Intel Q9300, Vista/32, 3 GB RAM. This rig runs Oblivion with 130 mods (including huge textures) just fine, so I don't think it is overpowered.

The last thing I'm going to check is running a game save from the tutorial. If it goes OK for 15 minutes, I'll be blaming the game (as opposed to system) software.
Post edited May 18, 2011 by Megarelix
Same problem here.

PC: GTX 460, 4GB RAM, Win 7 32, Drivers updated.
I just did an experiment: loading a save from just after waking up with Tris, I was able to run for 20 minutes w/o problems. Then reloaded the save before facing the dragon on the bridge: the same. Then I loaded my most recent save in the Flotsam tavern: lasted about 16 seconds before CTD. In the next attempt I was able to leave the tavern - only to crash outdoors after about three minutes; consistent with my average Flotsam experience of less than 5 minutes.

The total of 40 minutes of pre-Flotsam play without problems does not seem like just luck. WIth MTBF of, say, 5 minutes, the chances for a successful run of that length would be about 1/exp(8), or 1 in 2500. This is a strong argument indicating the reason as either something Flotsam-related or some problem (memory leaks, corruption) developing with game time.

If I have time and patience, I may try to keep restarting until I can get to a place far from Flotsam and see what happens. Most probably, though, I'll just kiss goodbye, for the time being at least, to the $130 spent on the CE, get myself Honest Hearts and spend a few days with Fallout 3 NV. This is becoming more work than play.
Post edited May 18, 2011 by Megarelix
avatar
Megarelix: I just did an experiment: loading a save from just after waking up with Tris, I was able to run for 20 minutes w/o problems. Then reloaded the save before facing the dragon on the brighe: the same. Then I loaded my most recent save in the Flotsam tavern: lasted about 16 seconds before CTD. In the next attempt I was able to leave the tavern only to crash outdoors after about three minutes - consistent with my average Flotsam experience.

The total of 40 minutes of pre-Flotsam play without problems does not seem like just luck. WIth MTBF of, say, 5 minutes, If crashes were just random, the chances for a successful run of that length would be about 1/exp(8), or 1 in 2500. This is a strong argument indicating the reason as either something Flotsam-related or some problem (memory leaks, corruption) developing with game time.

If I have time and patience, I may try to keep restarting until I can get to a place far from Flotsam and see what happens. Most probably, though, I'll just kiss goodbye, for the time being at least, to the $130 spent on the CE, get myself Honest Hearts and spend a few days with Fallout 3 NV. This is becoming more work than play.
Disabling the DOF effects seem to help....a tad...Just a tad
avatar
starocean37: During the prologue, everything went perfect, but as soon as chapter 1 started the crashing keeps occuring. Can't fully enjoy the game without it crashing to the desktop. Then there are times when I push the "esc" key, meditate, and talking to people, the game will crash to the desktop.
Bump for any advice/solutions. Just randomly crashes back to launcher with no warning or errors. :-(
avatar
winterforge: Bump for any advice/solutions. Just randomly crashes back to launcher with no warning or errors. :-(
Have any of you tried adjusting the screen resolution to something lower? That's the only thing I can think of. I have a rig similar to Megarelix above, slightly less powerful, even, and I've had one CTD in maybe 15 hours of gameplay. My resolution is 1440xsomethingrandom, so I suspect it has to do with people playing at resolutions their computer can't handle and the new engine not handling it well.

Of course, that's just a guess. Still might be worth a try to see if that's the issue, though.
Playing at 1680x1050, my desktop resolution and what I play every game at.
avatar
winterforge: Playing at 1680x1050, my desktop resolution and what I play every game at.
The thing is that CDPR made their engine from scratch, so other games working a certain way doesn't necessarily guarantee that the same can be said of The Witcher 2.

I might be wrong about the resolution, of course. Just thought that lowering the resolution was a good place to start, if only to see whether it still crashes/how long before it crashes.
Do you play the GOG version? If not, do you have patch 1.01 installed?


[url=]http://www.gog.com/en/forum/the_witcher_2/how_to_get_the_patch[/url]
Post edited May 19, 2011 by MihaiHornet
Start > Command prompt or Win + R -> cmd.exe

First, backup!

Type: bcdedit /export "C:\BCDBackup"

Done.

Solution:

Type: bcdedit /set IncreaseUserVa 3072

Ok, close the Command Prompt, and go Gaming! ;)

If any problem, restore!

Type: bcdedit /import "C:\BCDBackup"

That's all!
This might be sound driver problem. If you are using realtek high definition drivers, update it to the latest 3.21 aka 2.60.
I had one crash to desktop when I was on the boat at the end of the prologue I played entire prologue in about 6 hours and not one issue i hope the game does not start to crash to desktop much more often now.

The game is epic thumbs up to the witcher devs.