Copied from steam in response to a user saying that a known memory leak cannot cause a crash and its all the Steam users systems:
Memory leaks can cause crashes easily in 32 bit OS depending on the type of memory leaked. For example a leak in Kernel memory like NPP, PTEs, or Pagepool it doesnt take much.
If its a handle leak it can crash as well but these are much more rare and typically show very slugish performance before it dies as the virtual memory manager doesnt seem to kick out pooltags to attempt to save the system as it will with other types of leaks so Windows tries to soldier on as it dies...
However I have a 64 bit system and i know a thing or two about resource leaks..I also crash regularly now that im in the Landsmeet area.
Without a memory dump with the correct symbols to read it i cant get very much information about what module is the problem...but its definetly the code as shown by this access violation:
Faulting application name: DAOrigins.exe, version: 1.3.11253.0, time stamp: 0x4b7057ab
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00000000
Faulting process id: 0x13b8
Faulting application start time: 0x01cacc9caab7d484
Faulting application path: c:\\program files (x86)\\steam\\steamapps\\common\\dragon age origins\\bin_ship\\DAOrigins.exe
Faulting module path: unknown
http://en.wikipedia....ccess_violationOddly i played through the entire Awakenings without a single crash....mine seems to like to crash when i play through with my Warrior and in Denerim.
System Specs:
Old Crap CPU: Intel Core 2 6400
4GB Crucial Ram cant remember the clockspeed and dont care.
NVidia GTS 250 running 197.13 read the FULL engineering release notes and no known issue at time of release with DAO and NVIDIA on my OS.
WIN 7 64 Ultimate.
If you are going to argue its my system please show me fact based data on your argument like i showed above, links to offcial documents from manufacturers would help so i can read any whitepapers they may publish...