Originally posted by Mr Blue Playdoh:

Originally posted by Hardware Hero™:

What does the event viewer say? Look for hardware faults critical. Then look at errors just before. Get the stop code and look it up online. Most likely it's hardware related because that's what windows does when it detects an issue that's so bad, it has to crash dump everything right away so you don't lose data.

Here we go with the “it’s your PC” post! How is it his PC when EVERY game is ok! Wow

Actually there is a good answer for this, it's because not every game hits every piece of a driver or instruction set inside the north or south bridge. So you will occasionally run in to a game that uses an instruction that 99% of other games don't and if there is a fault it will expose it. As a developer for enterprise applications we tend to avoid "funny" stuff and use safe high level languages and API that avoids those 1% areas. Game developers cannot always do this and get what they want accomplished and sometimes have to dip in those instruction sets.

For example if you needed a custom recursion for injecting code during runtime, this is avoided as it can be messy. I can count on one finger I've ever done this in an enterprise environment and it was eventually replaced with much safer code.

As an EA application I would honestly expect that kind of code to be laying around until some tech debt cycles are done. Hell most beta's on AAA titles I've participated in had the same issues that eventually got cleaned out.

You are also going to run in to some "fudge factor" such as a compiled binary on an intel processor might not be the same compiled binary on an amd processor or sparc, etc. This can sometimes cause a mismatch in instruction sets in the binary. It's rare but lawsuits have happened over it, such as that one time intel cpu's purposely added an addition instruction to slow down running on amd cpu's. Fun times.