Jump to content


Photo

Assertion failed - what the heck?


  • Please log in to reply
3 replies to this topic

#1 Cal Jones

Cal Jones
  • Modder
  • 1168 posts

Posted 03 February 2009 - 12:48 PM

I've had a few blue screens lately (which I've posted on in the CTD sticky thread) but game has been working OK other than that.
Now, however, I try to start it up, it loads the title screens etc but when I go to the save game menu I get:

"An assertion failed at InfoScreenLoad.cpp at line 1428". And reverts to desktop. So what's up here? Do I have to reinstall from discs?

(I've just tried IWD2 - that loads up fine, incidentally.
I'm seriously considering a new PC at this point in any case, though am slightly worried BG2 won't run at all on a new machine).

#2 Yovaneth

Yovaneth

    The newly-appointed Master Builder of Baldur's Gate

  • Modder
  • 3060 posts

Posted 03 February 2009 - 03:55 PM

Definately a corrupted BG2, I'm afraid, although I have to say that although I've seen quite a few BG2 assertion errors, I've never seen that one!

InfScreenLoad.cpp at line 1492
Corrupt portrait bitmap. Go into the directory of the save game that is giving this error and delete all the .bmp files. Load the game and then re-save.

Putting all the errors together, I'm now seriously wondering if your motherboard is looking for somewhere to lie down and die. I don't think I'd worry too much about running BG2 on a new(er) PC, although I would treat Vista to a dose of the Black Spot if you're offered it. I have BG2 running on a 2.6GHz Core Duo and apart from my own stupidity during modding, it's never given me trouble.

-Y-

Edited by Yovaneth, 03 February 2009 - 04:00 PM.


#3 Cal Jones

Cal Jones
  • Modder
  • 1168 posts

Posted 03 February 2009 - 11:08 PM

Yeah I looked over the Bioware boards and that wasn't one of the ones listed. I've been pulling mods on and off that install (using the backup method to clean it up between games) so it may just have had enough.
I'm also wondering if it could be my DVD drive that has issues. Either way, it's time for a new PC - I've had this one over 4 years now!

#4 Cal Jones

Cal Jones
  • Modder
  • 1168 posts

Posted 04 February 2009 - 01:34 PM

OK well it seemed that the last blue screen corrupted the previous save game, or at least the images therein, so I deleted it. Problem solved - previous saves were OK. The difference with the assertion error, I think, is that it happened in ToB (I tried loading the SoA saves initially and they were all fine), hence different error code.

Anyway, still going to get a new PC soon, but at least I can get this game finished first. :)