Yep, but i am having this really bad problem with the game, that just wont go away. I have patched the game to 2.1, read all the solutions that google gave me, and still, the game will randomly crash my computer when i hit to load a save file. This is the only game/program that crashes on my computer, so i think it is safe to say there is a solution to this.
My pc should be able to handle this game, i have played Bioshock, COD 4, and other games with everything set to max, and no crashes at all.
If anyone has any solutions, post here.
------------------------------"Be nice to nerds. Chances are you'll end up working for one. " - Bill Gates
I think that might be the solution, but where do i type it exactly? Command Promt? Or the Run command? Because both are giving me a "cant find" error. And also, my card has 512 megs of ram on it, should i set it to a lower value or wont windows run out of addressing space?
Message edited by thegatekeeper on 01-27-2008 at 05:59:55 PM
I think it's a console command in the game, hit the ~ key ingame or in the options menu, that should bring down the console, i think you may have to enable console in one of the game settings for the ~ to bring down the console thouh.
The memory is system memory not graphics memory and you have 3 gig's of memory so hopefully this should help.
Please begin by making a full backup of your computer.
Step 2 -- Become familiar with the Windows XP Recovery Console
Before making this change to your Windows XP configuration, be sure you are familiar with running the Windows XP Recovery Console. Anytime you make changes to the configuration of your computer, there is a possibility of making a mistake that could cause problems booting your computer. The Windows Recovery Console can be used to repair these mistakes. I recommend you practice using the Windows Recovery Console before beginning this procedure.
For more information about the Windows Recovery Console, refer to:
Description of the Windows 2000 Recovery Console, Microsoft Knowledge Base Article 314058.
Using Recovery Console, Microsoft TechNet.
Recovery Console, The Elder Geek.
Windows 2000 / XP Recovery Console, World of Windows Networking.
Step 3 -- Make a copy of boot.ini
In the step 4, you will edit the boot.ini file, normally located in C:\. I recommend you make a backup copy to c:\boot.ini_2gb before editing the file. If necessary, you can restore boot.ini to its previous state using this backup file.
Step 4 -- Edit boot.ini to enable 3 GB addressing
To enable the 3 GB addressing, edit the boot.ini file, which is normally in C:\. You may need to enable display of hidden files and folder in order to see this file in the Windows file Explorer:
1. In Windows file Explorer, choose the Folder Options command from the Tools menu.
2. Choose the View tab.
3. Select the Show hidden files and folders radio button under Hidden files and folders.
4. Click OK.
To enable the 3 GB addressing, you must add the /3GB option to the appropriate line in the boot.ini file:
You should also increase the size of your paging file to at least 4096 MB (4 GB). It is necessary to increase the size of the your paging file beyond 3 GB because it is shared by all processes on your computer, not just The Panorama Factory.
For instructions on how to increase the size of your paging file, see the January 13, 2003 entry on the page Increase swap file size for Windows NT, 2000, XP and Vista.
Step 6 -- Restart your computer
Please double-check your changes to boot.ini before restarting your computer!"
How safe is this exactly? I don't want to mess up my computer just to play one game .
Message edited by thegatekeeper on 01-27-2008 at 09:03:23 PM
Hmm, the computer game me a blue screen referring to the nvidia driver. I may know what happened, the computer ran out of addressing space and address the memory on the graphic card.
For the latest problem i don't think it'd start addressing to the graphics card if it ran out of system memory, it may have been a non related graphics driver problem.
Funny thing is I played the witcher for like a week solid and had 1 crash, maybe i just got lucky. I've been working in the middle of nowhere for the last 3 weeks, and i'll be building a Vista64 rig with 4 gig ram when i get back so i'll now probably not even have to use the fix now that you've figured it out fully, the irony of it al (;
Hi
If you are running The Witcher on High settings or custom settings that go above the equivalent of Medium setting then you will almost undoubtedly have these problems with crashing as it is a problem with the game. I have read a couple of times in the forums, that people can only over come those problems by setting the game to medium. It really is unfortunate for this to be the case for such a good game.
I hope that I am referring to the same problem and that this helps.
I am stuck on the killing the beast in the first part of the game and the walkthrough says to drink a swallow, where do you get a swallow, or what is it talking about?
For the latest problem i don't think it'd start addressing to the graphics card if it ran out of system memory, it may have been a non related graphics driver problem.
Funny thing is I played the witcher for like a week solid and had 1 crash, maybe i just got lucky. I've been working in the middle of nowhere for the last 3 weeks, and i'll be building a Vista64 rig with 4 gig ram when i get back so i'll now probably not even have to use the fix now that you've figured it out fully, the irony of it al (;
What i mean is, with the /3GB switch, windows addressed 3 gigs of physical ram, and since 32 bit systems can only address a little over 3 gigs, it may have ran out of addressing space for the graphic card memory. So i can either go down to 2 gigs, or get a 64 bit OS.
At least, thats how i see it.
------------------------------"Be nice to nerds. Chances are you'll end up working for one. " - Bill Gates
Reply to thegatekeeper
I'm not sure that's it. I think the fix only affects system ram, not graphics ram, it'll only try address as much graphics ram as you have, say 512 or like a max of 1 gig, but than again this fix is out of my depth as far as knowhow so you may well be right.
You are about to answer a thread that has been inactive for more than 6 months. If you still wish to proceed, please ensure that your posting is original and does not duplicate or overlap any prior responses to this thread.