But still How could I tell that the memory was bad? It was a slow learning process. It was rather sporadical at first but as demo sizes for games increased steadily, it happened more and more often that I got CRC errors. I used Gamer's Hell as my main resource for demo downloads back then and due to the absence of any other issues with my system, I thought that they had screwed up the archives upon packing or uploading.
Then I got WoW when it was released and had major trouble with installing and patching the game. It was either my whole install or the patch es that got corrupted during the install or patching process. It was a nightmare. When I checked around the net, everyone and everything was always pointing out that it could be a RAM issue so I finally got new memory as it was time to upgrade to 2x MB anyway. Well, haven't had a single archive corruption error or issues with WoW quit a looong time ago but back then the prob went away with the new RAM ever since.
It's really strange since all the tests for bad RAM were negative but in the end it was that very same "flawless" memory that caused the few issues that I was having with my system. My RAM upgrade was done in order to be able to play Gothic 3 properly. I still have the 2 sticks of the "old" memory lying around so I could try to put them back to see if there is any difference.
I haven't noticed any other problems with the new sticks but I've had the old ones for almost 2 years now and I have NEVER had any problems with those, so they "ought" to be okay. I'll get back to you on that later. The real bitch about the error message I'm receiving is that is an OS level error message.
In other words: Neither the game Dark Messiah nor the engine Source is catching the exception so it passes along to the outermost layer and that is Windows XP. Unfortunately for bug fixing purposes, the reporting details at this stage is minimal at best. When trying to search for the nature of the error I ran across everything from media player crashes the genre as a whole and not necessarily the program by that name and browser crashes to crashes from games also from some that are not even remotely connected to the Source engine.
It is very unfortunate that Arcane aren't catching this error but even more so that Valve themselves have failed to make proper exception handling in their engine. When I started searching for means to fix or locate the problem I ran across a link to a FAQ on Steam where this error message is mentioned.
It basically says that if you get this error then you're screwed because they have no idea what is causing it or how to fix it well, the wording was slightly less defeatist but that meaning was clear. This is what bugs me the most: If this problem lies with the engine and not the game then why the hell am I only getting this error in Dark Messiah and not HL2 or CS: Source or Bloodlines. Basic logic, and that is what programming is all about, dictates that this can NOT be the case so therefore it MUST be something that is done in Dark Messiah, but not in the other Source based games, that is causing the game to crash I'll be back after trying with my "old" memory sticks.
Son of a Oddly enough I couldn't get it to crash right away and as I had an errand to run and was consequently pressed for time I decided to start the tutorial, turn off the sound and leave it to its own devices while I went about my business.
I did notice however that the console was filled with red lines of this or that "could not be initialize" or whatnot, So I thought: "AHA! A quick couple of yanks and pushes later and the new RAM is back in and I fire up the game. Now is your chance to conquer them Exact same error message and this time the console is also filled with lots of red lined system messages At any rate, how the heck do I explain to the place where I bought the memory that I can only detect problems in a single game and maybe in a While I'm quite pisssed that this took so damned long to figure out and that even a respectable program like memtest which has only one task: to test the memory couldn't find anything wrong, I am glad you guys didn't let me off the hook.
Otherwise I would have given up a long time ago and since I wasn't expecting to include memory when next I'm to upgrade I would still not be able to play the game. So thank you all for being so damned persistent :biggrin: Oh and I obviously have to eat every bit of criticism I have blurted out previously since neither Arcane nor Valve can be expected to handle hardware errors in their software.
That is the OS's responsibility and for once Windows does just what it is supposed to do so I can't even blame Microsoft this time there has got to be a first for everything ;. Even though I have tried to be civil I suspect I won't go to bed hungry tonight :biggrin:. Hehe, well congrats! DId you say which brand of RAM your using? If no other game is crashing then I wouldn't worry about it. Use the old sticks to play DM, then switch them.
Don't be so quick to think that something is wrong with your 1 gig sticks. Just because they're incompatible with Dark Messiah doesn't mean they're defective. You already said that none of your other games were crashing. I'm just curious.
Which Corsair RAM did you buy? Well, once you find the spot with the honey you can't help but poke around abit while your hands are dirty anyway, so I thought I ought to double check other Source based games.
Just like the DM multiplayer mode that I was able to run with only the occasional crash no more than many other games so is CounterStrike: Source fully playable even though the crashing frequency has indeed increased somewhat. Crashes left and right within the opening sequences and while the error message was different I got an ingame error message instead of an OS message the nature of the crash is identical to what I'm experiencing in Dark Messiah.
On one hand it is no longer "just" one game that is causing problems but on the other hand it is not the entire engine that is at fault but apparently only when playing singleplayer games on the Source engine that the problems emerge This is defiantly strange, it must be just a bad stick, as Corsair is reliable and high end brand.
Yeah you definatly want this fixed before you try a great game like Bloodlines. Okay, once I got Dark Messiah working, at last, I really wanted to play it so I decided to stop looking my gift horse in the mouth and just play the damned thing before I continued my testing to find out what was wrong in the first place besides, I had to wait until the end of the holidays anyway if I wanted to exchange my RAM sticks.
So I played it, finished it as a fighter and enjoyed it. Not using stealth or magic left me wanting for more so I started another run through as a mage. A simple test came to mind though and instead of playing with my old 2 sticks of Mb RAM I put in a single stick of my new memory to test each stick individually I've reached chapter 8 as my mage and that means that I've played at the very least 6 hours with no crashes on each stick and since my old memory worked fine with 2 sticks as well, I can't lay the blame on the RAM slots either.
If I had any hair left it would definitely be turning grey by now. The only thing I have left to test is the dreaded complete OS reinstall. I'm currently building up my courage for such a massive and time-consuming undertaking. Again: for the game part. The game itself would not be patched anymore since 1. And they have no business with this game anymore since To answer another question: Dark Messiah multiplayer and Dark Messiah singleplayer are two seperate games, seperately built by two different companies.
Singleplayer is built by Arkane. Multiplayer is built by Kuji. Both games have their own seperate patches. No you cannot "patch" the Steam version with the retail patch. Steam patches their version automatically. The Steam version has always had stability issues e.
Hopefully the recent game content conversion solved those issues. Zuletzt bearbeitet von Unbornchild ; Mai um Pro Seite: 15 30 Geschrieben am: However if you purchased a normal retail DVD copy of Dark Messiah, you don't have to run Steam at any time to run the Singleplayer aspect of the game.
But there is a bug in the retail version of the game such that if you install the multiplayer component along with the singleplayer component of the game, after installation Steam will launch and commence redownloading a major portion of the entire singleplayer portion of the game again.
As mentioned in the patch section above, I recommend that you do install Steam and allow it to update your singleplayer game files as these updates are necessary, however to save it from redownloading existing files, follow these steps:.
In general it is recommended that you allow the game to be updated by Steam as often as possible. You don't need to keep Steam running all the time to do this, but make sure to check this page for notification of major updates, and also regularly restart your Steam client while online to see if any updates are required - they will download and install themselves automatically if any exist.
There were some other topics open already about this strange issue, so I suggest to write there Grimm 19 Feb, am. So I've jumped through all the hoops and the game finally starts up; however now when I select 'new game' it gives me a difficulty selector - and after selecting difficulty and clicking OK, proceeds to do absolutely nothing.
I restarted with -console enabled and tried to forceload the first map up, upon which the console returns this error: [quote]Could not get IServerGameDLL interface from library server. If you've got any ideas, feel free to throw them my way. Thanks a lot! Gaming wouldnt be the same without u guys.
Share to your Steam activity feed. You need to sign in or create an account to do that.
0コメント