so .. i tested now the game under windows vista cause i thought it could be a problem in xp.. so u can play under vista but the crasch will be there too. so we must wait for a patch to play the game...

Just thought I'd chime in and say that I have the same issue. The crazy thing is, the demo worked flawlessly, but the retail game won't even get through the opening bar scene without crashing. After spending 63.89$ on the DVD version of this game and not being able to play it at all, I can say I won't buy anything from 3D Realms again. Please release a patch as soon as possible so that those of us who wish to play the game are able to.

So, after trying pretty much everything else, I finally found a solution to this problem. Buy a new motherboard and CPU. I ditched my old Gigabyte GA-7VAX and picked up an ASUS A8V, and replaced my XP 2100+ with an XP64 3500. Prey now runs like a charm.

Of course, this solution is obviously not the best one. If I hadn't been needing an upgrade, I would not have done it just to play a buggy game. So, good luck waiting for a patch to come out. Hopefully one is out soon.

So, after trying pretty much everything else, I finally found a solution to this problem. Buy a new motherboard and CPU. I ditched my old Gigabyte GA-7VAX and picked up an ASUS A8V, and replaced my XP 2100+ with an XP64 3500. Prey now runs like a charm.

Of course, this solution is obviously not the best one. If I hadn't been needing an upgrade, I would not have done it just to play a buggy game. So, good luck waiting for a patch to come out. Hopefully one is out soon.

Indeed that is not the recomended solution. But it proves that the game disc, and your other hardware wasn't the problem. You even had reloaded XP to rule out bad vxd files. I wonder what was on the mobo or CPU that could have caused the problem? Perhaps a wonky BIOS setting or chipset driver?

__________________
"The world is full of complainers, and from time to time they permit themselves to post." - Nessus

I can't say that I have the same problem. I have a AMD XP2200+ and I've had problems, but after changing my video drivers to Nvidia 81.98 I haven't had problems as frequently. That isn't to say it has been a complete solution. I randomly will crash with the sound looping. It doesn't happen till after a certain amout of time though, which leads me to believe its Heat causing the crash

Initially it the sound loop crash was happening quicker with older drivers. The game was also very sluggish compared to the demo. I somehow noticed a huge increase in performance though when switching drivers. I currently have a Geforce 6600GT.

Not sure if this will work for everyone. After some indepth searchs online, I found out that some freeze issues are related to bad ram slots. so, I tried it out. turns out they were right. I moved my ram from slot 1 to slot 4. there was mention of moving from orange to yellow slots... but on my board it's actually a move from blue to orange.
The only down side to this is that potentially I do not have the capability of using my full ram capabilities if I ever get to a point where I want all four ram slots in use.
I now took it off the shitty settings it was on earlier, which was the absolute minimal, and switched it to the highest of the high. no crashes... and the game actually looks great. I have not tested this a whole lot, but it has yet to crash on me. I will keep you posted if it starts to crash again.
Cheers, and good luck

I'm having the same problem, but it didn't start until I got to the "Follow the guiding fires" or whatever that mission was. Up to that point, the game worked perfectly. Now, I can't play the game for more than maybe 30 seconds before it locks up. I do get the Windows XP box asking if I want to report the error. I do and then the system drops me back to the desktop.

I'm having the same problem, but it didn't start until I got to the "Follow the guiding fires" or whatever that mission was. Up to that point, the game worked perfectly. Now, I can't play the game for more than maybe 30 seconds before it locks up. I do get the Windows XP box asking if I want to report the error. I do and then the system drops me back to the desktop.

This is very similar to my experience. I played the game for some time with no problems. I can't say exactly at which point the problems started, but it was about the same time, i.e. the 'Guiding Fires' level. At first, I had just an occasional hard lockup with short looped sound (which eventually stops) and my only choice was to physically power off. Now, I'm on 'Center of Gravity' and I can't play for more than 60-90 seconds before it happens.

I have tried killing all processes except essentials, re-applying XP SP2, uninstall/re-installing the nvidia drivers and changing soundcards - even no soundcard at all. I've applied AMD dual-core drivers and optimizers, turning off hardware acceleration on the soundcards, windowed/fullscreen and none of it has made any difference at all.

I have HL2, Farcry, Brother In Arms, F.E.A.R, BF2, Oblivion, Battle For Middle Earth II, The Movies, Call Of Duty 2 and CIV 4 installed and they all run fine.

Come on tech guys from 3DR and HH, we need some help! This game will have to go back to the retailer on friday if there isn't any progress by then (7 day return policy), which will be a great shame as it's so f***ing good! The fresh approach to the the gameplay puzzles and the fantastic enviroment and level design really make this game stand out - I'd love to finish it.

i find it **** now the game is in store, many people have problems, they postet in official board and "pray maker" dont bring out a patch... so there was it for tomb raider legend better at eidos.. first pazch after 2 days since release

Try as was mentioned, moving your ram to another slot. If you have 2 sticks try removing one. This looks to be a hardware issue. Try putting memory timings to less aggressive numbers in the bios. If you haven't tried removing a sound card give that a try. Please don't just wait for a patch to fix this problem. There most likely will not be a fix to this problem in a patch. Errors from bugs in the code almost always manifest as a crash to desktop with a popup saying which instruction in memory is the problem. Freezing or bluescreening is very likely to be a hardware problem. Bad or old drivers, hardware problems or conflicts, etc.

We will continue to try and help you guys out with these problems. It's a bit hard with this one to give you suggestions because the only info on the problem we have is that it freezes randomly. You can see why that would be hard to pin point. Be patiant and hopefully we will be able to get a solution for you.

Try as was mentioned, moving your ram to another slot. If you have 2 sticks try removing one. This looks to be a hardware issue. Try putting memory timings to less aggressive numbers in the bios. If you haven't tried removing a sound card give that a try. Please don't just wait for a patch to fix this problem. There most likely will not be a fix to this problem in a patch. Errors from bugs in the code almost always manifest as a crash to desktop with a popup saying which instruction in memory is the problem. Freezing or bluescreening is very likely to be a hardware problem. Bad or old drivers, hardware problems or conflicts, etc.

We will continue to try and help you guys out with these problems. It's a bit hard with this one to give you suggestions because the only info on the problem we have is that it freezes randomly. You can see why that would be hard to pin point. Be patiant and hopefully we will be able to get a solution for you.

You understand, of course, that we're just so darned anxious to play this HIGHLY rated game that we're a bit disappointed when it crashes. That said, many of the people on this thread do seem to be getting the crash notice from Windows XP, myself included. I've even seen someone post screen shots of the crash message.

If there's anything we can do to help debug this issue other than complain on this forum and hit the little button that reports the crash to Microsoft, please let us know. I would be very willing to help if it means getting to continue playing the rest of the game. Right now I get kicked out of the game within 30 seconds of loading my last saved game.

Try as was mentioned, moving your ram to another slot. If you have 2 sticks try removing one. This looks to be a hardware issue. Try putting memory timings to less aggressive numbers in the bios. If you haven't tried removing a sound card give that a try.

Brian, thanks for the reply, it is nice to know you are reading these threads.
I don't agree that this is a hardware issue in the trad sense - i.e. a hardware compatability problem. The reason I say this is because the first third of the game played flawlessly - this problem starts during (or there abouts) the guiding flame level. Is there anything the level designers do that's different from that point? I have noticed I get more frequent crashes in the levels where you have to fly the shuttle.

I have already checked my BIOS settings at it's all at the least aggressive level. I even did a BIOS upgrade.

Quote:

Originally Posted by Brian Karis

Please don't just wait for a patch to fix this problem. There most likely will not be a fix to this problem in a patch. Errors from bugs in the code almost always manifest as a crash to desktop with a popup saying which instruction in memory is the problem. Freezing or bluescreening is very likely to be a hardware problem. Bad or old drivers, hardware problems or conflicts, etc.

We will continue to try and help you guys out with these problems. It's a bit hard with this one to give you suggestions because the only info on the problem we have is that it freezes randomly. You can see why that would be hard to pin point. Be patiant and hopefully we will be able to get a solution for you.

Well, it isn't really random - I can guarantee that if I have to reboot and go back to a save due to a crash, it will crash again after playing on for a couple of minutes from that spot - the only way I can make progress is to QS every 20-30 seconds. Eventually I will get to a point where it seems a bit more stable.

Regarding keeping away from old drivers etc, my PC was brand new just before Christmas. I am in IT support myself, and so I am diligent about ensuring my system is fully up to date.
As I said in my first post (just a couple up) I have stripped my system back to the most basic config I can (tho I haven't tried the RAM slots trick yet, I wont have time until the weekend).
I have error reporting enabled, but never get a crash dialog box - just a hard lockup with looping sound. I had a similar problem with F.E.A.R, but that was caused by a duff Geforce 6800 GT, which I replaced with my current 7800 GTX. That fixed the problem with F.E.A.R, and I have had no problems with this setup until now.

I moved my RAM to another slot. No help. I updated the BIOS, no help. I disabled the integrated audio and uninstalled drivers, no help. Only thing that made a difference was reinstallation of DirectX. Now I can play few hours without freezing, but eventually this game freezees and I have to reset the computer. If this is a hardware issue, why does my other games work perfectly without these annoying freezees? For exemple I can keep Doom3 of Oblivion almost all day running without any problems at all.

I've been crashing like a fiend and have been sending the windows dialog to microshaft every time. Earlier this morning i could play for about 5 min before it froze, now it goes for about 30 seconds after a load. Specs as follows:

I noticed something about the G15. When the game loads up the LCD says PREY, but it doesn't give ammo or health count. Could it be that the game has problems w/ my keyboard....unfortunatly i don't have an xtra to try.

I was getting quite frequent freezes and then blue screen (with nv4_disp as the driver) and freezes and then un-freeze and keep playing.
Sometime after severval seconds of freezing, it would start playing again. Other times it would go to the BSOD.

I recently updated my mobo drivers and grabbed the latest nvidia graphics driver. I deinstalled the current nvidia graphics driver and reinstalled it.

Now it freezes a lot less frequently. It hasn't went to BSOD since updating the drivers. Usually by this time it would have. Now, when it freezes, after a few seconds...it un-freezes and keeps playing. I played for an hour with only two short freezes which both unfroze and I kept playing.

It has never just locked up and I'd have to reboot...either BSOD or freeze/unfreeze.

I'm pretty sure the freezing has to do with the graphics and/or the mobo drivers.

I've checked the temperature on the mobo, processor and the video card and all are fine when playing games. So, it doesn't appear to be a heat issue. It never crashes in Windows.

After observing and reading carefully everything in this topic, i think it's time to share my two cents.
I don't get error messages, it is just freezing with sound going in choppy loop cycle. The only things that helps is hardware reset.
In one of the cases, but just one - after the game crashed i've got the Doom 3 engine console with error messages filled. Just after a seconds the machine has restarted and i couldn't obtain any usefull information at all, one the could help resolve or get a workaround for this.
Since then, the engine system console (which exists in all id Games since Quake 3), i've never managed to get it and/or analyse it at all.
The crashes are constant, and practicaly i've gave up trying to play "Prey" for the moment.
Here are the things i've tried -
- updating to the latest sound drivers (Creative Audigy 2 Value)
- updating the 6600GT drivers from nVidia to the latest one, even tried with the latest beta - 91.33, but with no any luck at all. Then i got back to the latest 91.31 revision.
- updating the nForce chipset (3) drivers to the 5.11 (i was with an obsolete old version), but this also didn't resolve anything
- lowering couple a levels the sound hardware acceleration
- removing the Audigy 2 card from the slot and switching to the cursed AC'97 integrated audio
- borrowing and replacing my own two pieces of A-Data VITESTA DDR400 RAM modules (2x512 mb) with a Kingston from a friend
- switching the A-Datas and the Kingstons through different DIMM slots, even combining both of them. Extensive memory checks on the both pairs of memory modules, showed no failures or memory checksums at all. I'm saying that, with one idea - the problem is a hardware compatibility issue, but IT'S definitely not in any individual hardware component - i assume it's a mixed effect from couple of factors, which i guess triggers some memory leak or something which causes the freezing. Also - THIS is the only game currently installed on my computer which behave like this.
- updating to the latest Dx9.0 binaries.
- unloaded all other system proceses, trying to free as much resourses as i can, to do a "clean boot" with the game.
- currently i also have, Quake 4, Doom 3 - RoE installed, which never caused such problems

After crashing and cold rebooting the mchine, i've looked at the event logs on my machines, but there were no usefull info for the crash at all. The machine even doesn't reacts like it was restarted because of the hardware problem (as we all known it does with the message "The system has recovered from serious system crash" generated by Windows XP Professional).

I have and another ideas, and i'll try them ASAP, when i have the time - to run the game, trough Sysinternals FileMon and RegMon apps, but i think it will be useless. Nevertheless i'll try that too.

Still i think, that it is a glitch in the engine or scripting code. Don't know.
Also i do not dismiss fully the idea that it could be a sound hardware/drivers/game link issue, since the thing i've noted for the last couple of days reading around the topic is that most of us has a Creative SoundBlaster cards.. Don't know if that helps.

One last things to ask the guys from Humand head - is there anyway, to make the game generating some runtime log which i could examine or send to you after all, i think it will be helpfull to examine and squash the problem

)

Best regards
C'est Moi

P.S: Nothing in the machine is overcloked - the RAM is in normal latency, neither the CPU has been tweaked, neither the GPU core and GPU's Memory clocks.

Well, with all stuff suggested, I had pretty much an identical experience to Kopacha, and had tried almost the exact same things (bar trying new memory). On top of that list I also did a virgin install of XP Pro, XP2'd, patched and nothing else at all. This install doesn't connect to the net, so no AV, Anti-Spyware, no extra software of any description. Didn't help.

HOWEVER I have now completed the game after making one change.

Someone suggested that changing the CAS latency in the BIOS helped - I changed mine from 2.5 to 3 (the lowest performance setting, lower even than the BIOS default 'safe' setting), and after that I could play for up to half an hour without a crash. So I got into the habit of playing for about 15mins, quitting to the desktop, restarting the game etc etc and I have now been able to finish. The last level didn't crash at all, and I was so engrossed I forgot to quit out.

Hope this helps some of you. Perhaps if the HumanHead peeps are reading this, this might help you pinpoint where the problems lies.

I had exactly the same problem as you guys...the game would run for 5 to 30minutes and then the video would lock up along with the sound. I could not control alt del to exit the game, I had to reboot each time.

Now here's the strange bit

I had a similair problem with TRD with a ti4200 256 X8 which was overheating and causing the game to lock up. I enabled AA and AF to X2 and the lockups stopped. I used the same "trick" with prey on a completely different rig and guess what? No more lock suey!

I get a random crash within about 5 minutes of playing the game. Sometimes I can play for 15, other times for only about 30 seconds. The oddest thing? Multiplayer is rock solid.

I have a BFG 6800GT and an Athlon64 3000 running on an MSI Nforce 3 mobo. I'm going to try some of the suggestions found here and post more details on my system later, just wanted to keep this thread bumped.

Oh yes, and more details on the crash: The screen goes rainbow technicolor and I am forced to reboot, ctrl-alt-del does not work. I seem to remember the sound looping, Ill confirm on that later.

Lets get this one fixed people, its probably some obscure setting, my experience with WoW (another picky game) has shown me that tech support for these types of issues falls to the community :-(. There are simply to many combinations of hardware for the developers to reallistically test.

bsouth4228 (and possibly others),
If you get a crash dialog such as the one seen here:http://img451.imageshack.us/img451/7...problem1ib.jpg
Please click that "click here" link at the bottom of the box, and take a screenshot of the screen that pops up there instead. It contains a module name and address offset, which is important in helping us track down the source of the crash.

well first off you gotta kno this EVERY OTHER GAME runs PERFECT in the highest settings like: All Source Engine Games, F.E.A.R., Tomb Raider Legend, Ghost Recon.

I ain t got no problems at all with my computer and all games!

Now I bought prey and started playin it and everythang seemed to be ok.
BUT always when I play for about 15-30 mins approximately the game screen freezes and I get sound loops. NOW THE WEIRD THING IS: after approximately 30 seconds everythang works fine again but then after another 30 seconds it freezes again for 30 seconds BUT without sound loops and after that I can play another 15 mins without problems. weird huh? Another problem is when I close the game a memory error pops up. NO NO MEMORY PROBLEM JUST FINE!!! I did not really do any experimenting with the settings in the game cuz more ppl got this problem and everythang else is just workin fine. ALL drivers are up to date like when they thinkin bout programming new ones I got em already installed lol whut.