BSOD playing Sim City

Your most recent bugcheck is BCCode 0x9c which much in the same way
as 0x124 it's fundamentally different from other bugchecks.

This is a hardware issue: an unrecoverable hardware error has occurred. The parameters have different meanings depending on what type of CPU you have but, while diagnostic, rarely lead to a clear solution.

Most commonly it results from overheating, from failed hardware (RAM, CPU, hardware bus, power supply, etc.), or from pushing hardware beyond its capabilities (e.g., overclocking a CPU).

   Note

If any component is overclocked, STOP, reset it back to stock speeds!

Going through your logs I see a lot of entries which reports overheating.

Code:

  Log Name: System
  Source: Microsoft-Windows-Kernel-Power
  Date: 2013-05-13T21:56:51.058
  Event ID: 89
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: Philmos-PC
  Description: 
ACPI thermal zone ACPI\ThermalZone\TZ01 has been enumerated.             
_PSV = 379K             
_TC1 = 1             
_TC2 = 5             
_TSP = 1000ms             
_AC0 = 0K             
_AC1 = 0K             
_AC2 = 0K             
_AC3 = 0K             
_AC4 = 0K             
_AC5 = 0K             
_AC6 = 0K             
_AC7 = 0K             
_AC8 = 0K             
_AC9 = 0K             
_CRT = 379K             
_HOT = 0K             
_PSL - see event data.

Code:

  Log Name: System
  Source: Microsoft-Windows-Kernel-Power
  Date: 2013-05-13T21:56:51.058
  Event ID: 89
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: Philmos-PC
  Description: 
ACPI thermal zone ACPI\ThermalZone\TZ00 has been enumerated.             
_PSV = 0K             
_TC1 = 0             
_TC2 = 0             
_TSP = 0ms             
_AC0 = 358K             
_AC1 = 328K             
_AC2 = 273K             
_AC3 = 273K             
_AC4 = 273K             
_AC5 = 0K             
_AC6 = 0K             
_AC7 = 0K             
_AC8 = 0K             
_AC9 = 0K             
_CRT = 379K             
_HOT = 0K             
_PSL - see event data.

Download Speccy and post a Screenshot of the summary window,
one at idle and another while putting load on the PC using Prime95 for the CPU
and Furmark for the GPU.

   Warning

Keep a watchful eye in the temperatures and don't let them exceed 82°C!

The older bugchecks in the file all point to the GPU.

Fill out this form and post back the result.

• Power Supply Calculator

Even if the GPU is is failing due to overheating or other hardware failure I recommend
rolling back the driver to a more stable release.

You're using driver version 320.49 which is known to be buggy.

Code:

Adapter Description    NVIDIA GeForce GTX 670
Driver Version    9.18.13.2049

Arc said:

Lately we have experienced some issues with the latest driver. Install the 314.22 WHQL only.

• Uninstall All nvidia items in Control Panel > Programs and features
  
  • 3D Vision Control Driver
  • 3D Vision Driver
  • Graphics Driver
  • HD Audio Driver
  • PhysX
  • nvidia Update
  
  (Are you using nvidia chipset drivers? If so, dont uninstall anything other than those are listed).
• Now follow Drivers - Clean Left over Files after Uninstalling
• Boot normally now. Go to Drivers - Download NVIDIA Drivers, Download 314.22 WHQL. While installing, Select Custom (Advanced) install. In the next page, follow this settings:
  
  

Good places to read more:

• Stop 0x124 - what it means and what to try
• Stop 0x124 Troubleshooting - 'New Method'

Let us know the results :) !

philmo said:

Thanks for your quick reply, I would be surprised if it was over heating - as I have lots of cooling and heat check monitors I use now and again show fine. But of course your knowledge is far greater than mine so will check all listed.

Do you think I should also run Memtest, or is this later.

Finally GPU rollback, so I understand Arcs comments as I DO have Nvidea chipsets listed so clear should not remove them (Nvidea chipset)?.

I will update you soon.

Thanks again.

Please do check for overheating as it very important to establish that this is not the cause.
You can use memtest86+ to test the RAM :: RAM - Test with Memtest86+
No, you should not remove the chipset drivers as they have nothing to do with the GPU drivers
they will install themselves automatically anyway if you do uninstall them.
What is the make and model of your PSU?

Keep updating :)

Thanks, let us know.

Thank you for updating on the state of things :) .

73°C is considered hot but this kind of GPU and take it so it's ok,
but the real problem is the CPU.

I scanned your logs and found many WHEA entries. Those are calculation errors, otherwise know as
an internal parity, that the CPU is correcting "on the go" typically those are the none fatal errors
hence the instability of certain apps, but sometimes they are which is the
one of the main causes of the hardware related bugcheck.

These errors are more commonly found on an overclocked machine due to the user
tampering with the voltage delivery to the CPU / RAM.

Code:

Event[34949]:
  Log Name: System
  Source: Microsoft-Windows-WHEA-Logger
  Date: 2013-05-14T00:09:06.172
  Event ID: 19
  Task: N/A
  Level: Warning
  Opcode: Info
  Keyword: N/A
  User: S-1-5-19
  User Name: NT AUTHORITY\LOCAL SERVICE
  Computer: Philmos-PC
  Description: 
A corrected hardware error has occurred.

Reported by component: Processor Core
Error Source: Corrected Machine Check
Error Type: Internal parity error
Processor ID: 0

• WHEA - MSDN Microsoft.com

Since your PSU appears to be of a high enough standard
I suspect the BIOS at this point.

• Clear CMOS

   Note

Write down the current value of the SATA Mode!
Its either AHCI or IDE.
After resetting the CMOS go back and verify the value for SATA Mode is what it was
when the OS was installed.

Your BIOS is not listed anymore on your motherboard's webpage.

Code:

BiosVersion = F14
BiosReleaseDate = 05/31/2012

I recommenced flashing the BIOS, only if clearing the CMOS didn't help.

   Warning

Flashing the BIOS is a risky procedure, any interruption will render the PC useless!
Continue at your own risk.

BIOS F18 - 20/08/2012




Update with the results :) .