New Build, all games CTD?

KingKenny04 · Apr 13, 2013

Hello! Just built a new rig today, first one in many years. Here are the guts:

Mainboard: MSI Z77A G45
CPU: Core i5 3570K (CM Hyper 212 cooler)
GPU: EVGA GTX 650 Ti 1GB
RAM: Corsair XMS 8GB (2x4GB) 1600 Mhz
PSU: Antec 650W

4x 120mm case fans, 3 intake and 1 exhaust (directed out the rear of the case away from any components)

Have Windows 8 installed. Everything seemed to be running smoothly. Updated all the drivers. Now it seems every game I try playing crashes to desktop after a period of play. By crash to desktop I mean "Blabla.exe has encountered a problem and needs to close". Planetside 2 seems to do it after about 5-10 minutes of play, EVE Online after 45 minutes to an hour, and the Arma III Alpha does it around 2 hours of play. I tried clean reinstalls of my graphics and chipset drivers, and after reading some other threads on here, I got SpeedFan and EVGA Precision to check temps. At idle my CPU sits around 32C and my GPU around 36. During gaming the CPU climbs to around 45C and the GPU to around 65C, up to and including the point of crash. As I've read, it seems those temps are more than acceptable during gaming? I'm lost at this point.

aramisathei · Apr 13, 2013

Your issue doesn't sound like it's with temps.
Usually you'll either get a full system crash or down-throttled if that was the case.
It sounds more like faulty drivers.

You can check what's causing the crash in Windows' Event Viewer.
In Windows 8, Press Win + X, and select Event Viewer.
Then click the arrow next to "Windows Logs" and look under "Application".
You're looking for an error for your specific application (i.e. ps2.exe or whatever it is) and what caused it. If multiple games are crashing, it's probably related to the same driver, but there could be other causes, so check the errors for each crashing game, and then post back if you don't have any luck resolving it.

KingKenny04 · Apr 13, 2013

aramisathei :

Thanks so much! Found the applicable logs, but I can't make heads or tails of them. They may as well be written in martian to me :S I hate to drop walls of text out there like this, but I wouldn't even know where to begin with reading these:

Log Name: Application
Source: Application Error
Date: 4/12/2013 8:31:45 PM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: WarCenter
Description:
Faulting application name: arma3.exe, version: 0.52.103.507, time stamp: 0x5151a2b6
Faulting module name: arma3.exe, version: 0.52.103.507, time stamp: 0x5151a2b6
Exception code: 0xc0000096
Fault offset: 0x0000d04a
Faulting process id: 0xad0
Faulting application start time: 0x01ce37f76b54ce7a
Faulting application path: C:\Program Files (x86)\Steam\steamapps\common\Arma 3\arma3.exe
Faulting module path: C:\Program Files (x86)\Steam\steamapps\common\Arma 3\arma3.exe
Report Id: aa432a86-a3ea-11e2-be69-d43d7e98a8fd
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2013-04-13T03:31:45.000000000Z" />
<EventRecordID>232</EventRecordID>
<Channel>Application</Channel>
<Computer>WarCenter</Computer>
<Security />
</System>
<EventData>
<Data>arma3.exe</Data>
<Data>0.52.103.507</Data>
<Data>5151a2b6</Data>
<Data>arma3.exe</Data>
<Data>0.52.103.507</Data>
<Data>5151a2b6</Data>
<Data>c0000096</Data>
<Data>0000d04a</Data>
<Data>ad0</Data>
<Data>01ce37f76b54ce7a</Data>
<Data>C:\Program Files (x86)\Steam\steamapps\common\Arma 3\arma3.exe</Data>
<Data>C:\Program Files (x86)\Steam\steamapps\common\Arma 3\arma3.exe</Data>
<Data>aa432a86-a3ea-11e2-be69-d43d7e98a8fd</Data>
<Data>
</Data>
<Data>
</Data>
</EventData>
</Event>

Log Name: Application
Source: Application Error
Date: 4/12/2013 8:31:45 PM
Event ID: 1005
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: WarCenter
Description:
Windows cannot access the file for one of the following reasons: there is a problem with the network connection, the disk that the file is stored on, or the storage drivers installed on this computer; or the disk is missing. Windows closed the program Arma 3 Alpha because of this error.

Program: Arma 3 Alpha
File:

The error value is listed in the Additional Data section.
User Action
1. Open the file again. This situation might be a temporary problem that corrects itself when the program runs again.
2. If the file still cannot be accessed and
- It is on the network, your network administrator should verify that there is not a problem with the network and that the server can be contacted.
- It is on a removable disk, for example, a floppy disk or CD-ROM, verify that the disk is fully inserted into the computer.
3. Check and repair the file system by running CHKDSK. To run CHKDSK, click Start, click Run, type CMD, and then click OK. At the command prompt, type CHKDSK /F, and then press ENTER.
4. If the problem persists, restore the file from a backup copy.
5. Determine whether other files on the same disk can be opened. If not, the disk might be damaged. If it is a hard disk, contact your administrator or computer hardware vendor for further assistance.

Additional Data
Error value: 00000000
Disk type: 0
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="49152">1005</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2013-04-13T03:31:45.000000000Z" />
<EventRecordID>233</EventRecordID>
<Channel>Application</Channel>
<Computer>WarCenter</Computer>
<Security />
</System>
<EventData>
<Data>
</Data>
<Data>Arma 3 Alpha</Data>
<Data>00000000</Data>
<Data>0</Data>
</EventData>
</Event>

Log Name: Application
Source: Application Error
Date: 4/12/2013 9:39:54 PM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: WarCenter
Description:
Faulting application name: PlanetSide2.exe, version: 0.0.0.0, time stamp: 0x51671537
Faulting module name: PlanetSide2.exe, version: 0.0.0.0, time stamp: 0x51671537
Exception code: 0xc0000005
Fault offset: 0x01a5f827
Faulting process id: 0xbcc
Faulting application start time: 0x01ce37fce8051931
Faulting application path: C:\Program Files (x86)\Steam\steamapps\common\PlanetSide 2\PlanetSide2.exe
Faulting module path: C:\Program Files (x86)\Steam\steamapps\common\PlanetSide 2\PlanetSide2.exe
Report Id: 2f3b6dfe-a3f4-11e2-be69-d43d7e98a8fd
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2013-04-13T04:39:54.000000000Z" />
<EventRecordID>314</EventRecordID>
<Channel>Application</Channel>
<Computer>WarCenter</Computer>
<Security />
</System>
<EventData>
<Data>PlanetSide2.exe</Data>
<Data>0.0.0.0</Data>
<Data>51671537</Data>
<Data>PlanetSide2.exe</Data>
<Data>0.0.0.0</Data>
<Data>51671537</Data>
<Data>c0000005</Data>
<Data>01a5f827</Data>
<Data>bcc</Data>
<Data>01ce37fce8051931</Data>
<Data>C:\Program Files (x86)\Steam\steamapps\common\PlanetSide 2\PlanetSide2.exe</Data>
<Data>C:\Program Files (x86)\Steam\steamapps\common\PlanetSide 2\PlanetSide2.exe</Data>
<Data>2f3b6dfe-a3f4-11e2-be69-d43d7e98a8fd</Data>
<Data>
</Data>
<Data>
</Data>
</EventData>
</Event>

Log Name: Application
Source: Application Error
Date: 4/12/2013 9:49:43 PM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: WarCenter
Description:
Faulting application name: ExeFile.exe, version: 2013.2.48.3842, time stamp: 0x511b6a0c
Faulting module name: nvd3dum.dll, version: 9.18.13.1422, time stamp: 0x51427c76
Exception code: 0xc0000005
Fault offset: 0x001e27ad
Faulting process id: 0x748
Faulting application start time: 0x01ce3801742ebbb3
Faulting application path: C:\Program Files (x86)\CCP\EVE\bin\ExeFile.exe
Faulting module path: C:\Windows\SYSTEM32\nvd3dum.dll
Report Id: 8e84fa3e-a3f5-11e2-be69-d43d7e98a8fd
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2013-04-13T04:49:43.000000000Z" />
<EventRecordID>317</EventRecordID>
<Channel>Application</Channel>
<Computer>WarCenter</Computer>
<Security />
</System>
<EventData>
<Data>ExeFile.exe</Data>
<Data>2013.2.48.3842</Data>
<Data>511b6a0c</Data>
<Data>nvd3dum.dll</Data>
<Data>9.18.13.1422</Data>
<Data>51427c76</Data>
<Data>c0000005</Data>
<Data>001e27ad</Data>
<Data>748</Data>
<Data>01ce3801742ebbb3</Data>
<Data>C:\Program Files (x86)\CCP\EVE\bin\ExeFile.exe</Data>
<Data>C:\Windows\SYSTEM32\nvd3dum.dll</Data>
<Data>8e84fa3e-a3f5-11e2-be69-d43d7e98a8fd</Data>
<Data>
</Data>
<Data>
</Data>
</EventData>
</Event>

Log Name: Application
Source: Application Error
Date: 4/12/2013 10:35:22 PM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: WarCenter
Description:
Faulting application name: ExeFile.exe, version: 2013.2.48.3842, time stamp: 0x511b6a0c
Faulting module name: nvd3dum.dll, version: 9.18.13.1422, time stamp: 0x51427c76
Exception code: 0xc0000005
Fault offset: 0x002465a3
Faulting process id: 0xb54
Faulting application start time: 0x01ce3802568bb033
Faulting application path: C:\Program Files (x86)\CCP\EVE\bin\ExeFile.exe
Faulting module path: C:\Windows\SYSTEM32\nvd3dum.dll
Report Id: eeb14b39-a3fb-11e2-be69-d43d7e98a8fd
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2013-04-13T05:35:22.000000000Z" />
<EventRecordID>330</EventRecordID>
<Channel>Application</Channel>
<Computer>WarCenter</Computer>
<Security />
</System>
<EventData>
<Data>ExeFile.exe</Data>
<Data>2013.2.48.3842</Data>
<Data>511b6a0c</Data>
<Data>nvd3dum.dll</Data>
<Data>9.18.13.1422</Data>
<Data>51427c76</Data>
<Data>c0000005</Data>
<Data>002465a3</Data>
<Data>b54</Data>
<Data>01ce3802568bb033</Data>
<Data>C:\Program Files (x86)\CCP\EVE\bin\ExeFile.exe</Data>
<Data>C:\Windows\SYSTEM32\nvd3dum.dll</Data>
<Data>eeb14b39-a3fb-11e2-be69-d43d7e98a8fd</Data>
<Data>
</Data>
<Data>
</Data>
</EventData>
</Event>

Log Name: Application
Source: Application Error
Date: 4/12/2013 11:13:45 PM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: WarCenter
Description:
Faulting application name: PlanetSide2.exe, version: 0.0.0.0, time stamp: 0x5168a1d8
Faulting module name: PlanetSide2.exe, version: 0.0.0.0, time stamp: 0x5168a1d8
Exception code: 0xc00000fd
Fault offset: 0x00ffad27
Faulting process id: 0xe54
Faulting application start time: 0x01ce380cb9bdb88b
Faulting application path: C:\Program Files (x86)\Steam\steamapps\common\PlanetSide 2\PlanetSide2.exe
Faulting module path: C:\Program Files (x86)\Steam\steamapps\common\PlanetSide 2\PlanetSide2.exe
Report Id: 4bb1b5ea-a401-11e2-be69-d43d7e98a8fd
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2013-04-13T06:13:45.000000000Z" />
<EventRecordID>339</EventRecordID>
<Channel>Application</Channel>
<Computer>WarCenter</Computer>
<Security />
</System>
<EventData>
<Data>PlanetSide2.exe</Data>
<Data>0.0.0.0</Data>
<Data>5168a1d8</Data>
<Data>PlanetSide2.exe</Data>
<Data>0.0.0.0</Data>
<Data>5168a1d8</Data>
<Data>c00000fd</Data>
<Data>00ffad27</Data>
<Data>e54</Data>
<Data>01ce380cb9bdb88b</Data>
<Data>C:\Program Files (x86)\Steam\steamapps\common\PlanetSide 2\PlanetSide2.exe</Data>
<Data>C:\Program Files (x86)\Steam\steamapps\common\PlanetSide 2\PlanetSide2.exe</Data>
<Data>4bb1b5ea-a401-11e2-be69-d43d7e98a8fd</Data>
<Data>
</Data>
<Data>
</Data>
</EventData>
</Event>

Log Name: Application
Source: Application Error
Date: 4/12/2013 11:24:51 PM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: WarCenter
Description:
Faulting application name: PlanetSide2.exe, version: 0.0.0.0, time stamp: 0x5168a1d8
Faulting module name: PlanetSide2.exe, version: 0.0.0.0, time stamp: 0x5168a1d8
Exception code: 0xc0000005
Fault offset: 0x01a5e4a5
Faulting process id: 0xeb8
Faulting application start time: 0x01ce380e56076720
Faulting application path: C:\Program Files (x86)\Steam\steamapps\common\PlanetSide 2\PlanetSide2.exe
Faulting module path: C:\Program Files (x86)\Steam\steamapps\common\PlanetSide 2\PlanetSide2.exe
Report Id: d8869ce5-a402-11e2-be69-d43d7e98a8fd
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2013-04-13T06:24:51.000000000Z" />
<EventRecordID>341</EventRecordID>
<Channel>Application</Channel>
<Computer>WarCenter</Computer>
<Security />
</System>
<EventData>
<Data>PlanetSide2.exe</Data>
<Data>0.0.0.0</Data>
<Data>5168a1d8</Data>
<Data>PlanetSide2.exe</Data>
<Data>0.0.0.0</Data>
<Data>5168a1d8</Data>
<Data>c0000005</Data>
<Data>01a5e4a5</Data>
<Data>eb8</Data>
<Data>01ce380e56076720</Data>
<Data>C:\Program Files (x86)\Steam\steamapps\common\PlanetSide 2\PlanetSide2.exe</Data>
<Data>C:\Program Files (x86)\Steam\steamapps\common\PlanetSide 2\PlanetSide2.exe</Data>
<Data>d8869ce5-a402-11e2-be69-d43d7e98a8fd</Data>
<Data>
</Data>
<Data>
</Data>
</EventData>
</Event>

Log Name: Application
Source: Application Error
Date: 4/13/2013 1:45:34 AM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: WarCenter
Description:
Faulting application name: arma3.exe, version: 0.52.103.507, time stamp: 0x5151a2b6
Faulting module name: arma3.exe, version: 0.52.103.507, time stamp: 0x5151a2b6
Exception code: 0xc0000096
Fault offset: 0x0000d04a
Faulting process id: 0x1704
Faulting application start time: 0x01ce38234288d828
Faulting application path: C:\Program Files (x86)\Steam\steamapps\common\Arma 3\arma3.exe
Faulting module path: C:\Program Files (x86)\Steam\steamapps\common\Arma 3\arma3.exe
Report Id: 811ca253-a416-11e2-be6c-d43d7e98a8fd
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2013-04-13T08:45:34.000000000Z" />
<EventRecordID>545</EventRecordID>
<Channel>Application</Channel>
<Computer>WarCenter</Computer>
<Security />
</System>
<EventData>
<Data>arma3.exe</Data>
<Data>0.52.103.507</Data>
<Data>5151a2b6</Data>
<Data>arma3.exe</Data>
<Data>0.52.103.507</Data>
<Data>5151a2b6</Data>
<Data>c0000096</Data>
<Data>0000d04a</Data>
<Data>1704</Data>
<Data>01ce38234288d828</Data>
<Data>C:\Program Files (x86)\Steam\steamapps\common\Arma 3\arma3.exe</Data>
<Data>C:\Program Files (x86)\Steam\steamapps\common\Arma 3\arma3.exe</Data>
<Data>811ca253-a416-11e2-be6c-d43d7e98a8fd</Data>
<Data>
</Data>
<Data>
</Data>
</EventData>
</Event>

Log Name: Application
Source: Application Error
Date: 4/13/2013 1:45:34 AM
Event ID: 1005
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: WarCenter
Description:
Windows cannot access the file for one of the following reasons: there is a problem with the network connection, the disk that the file is stored on, or the storage drivers installed on this computer; or the disk is missing. Windows closed the program Arma 3 Alpha because of this error.

Program: Arma 3 Alpha
File:

The error value is listed in the Additional Data section.
User Action
1. Open the file again. This situation might be a temporary problem that corrects itself when the program runs again.
2. If the file still cannot be accessed and
- It is on the network, your network administrator should verify that there is not a problem with the network and that the server can be contacted.
- It is on a removable disk, for example, a floppy disk or CD-ROM, verify that the disk is fully inserted into the computer.
3. Check and repair the file system by running CHKDSK. To run CHKDSK, click Start, click Run, type CMD, and then click OK. At the command prompt, type CHKDSK /F, and then press ENTER.
4. If the problem persists, restore the file from a backup copy.
5. Determine whether other files on the same disk can be opened. If not, the disk might be damaged. If it is a hard disk, contact your administrator or computer hardware vendor for further assistance.

Additional Data
Error value: 00000000
Disk type: 0
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="49152">1005</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2013-04-13T08:45:34.000000000Z" />
<EventRecordID>546</EventRecordID>
<Channel>Application</Channel>
<Computer>WarCenter</Computer>
<Security />
</System>
<EventData>
<Data>
</Data>
<Data>Arma 3 Alpha</Data>
<Data>00000000</Data>
<Data>0</Data>
</EventData>
</Event>

Log Name: Application
Source: Application Error
Date: 4/13/2013 3:13:13 AM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: WarCenter
Description:
Faulting application name: arma3.exe, version: 0.52.103.507, time stamp: 0x5151a2b6
Faulting module name: arma3.exe, version: 0.52.103.507, time stamp: 0x5151a2b6
Exception code: 0xc0000005
Fault offset: 0x0003d91f
Faulting process id: 0x1704
Faulting application start time: 0x01ce38234288d828
Faulting application path: C:\Program Files (x86)\Steam\steamapps\common\Arma 3\arma3.exe
Faulting module path: C:\Program Files (x86)\Steam\steamapps\common\Arma 3\arma3.exe
Report Id: bf62ded4-a422-11e2-be6c-d43d7e98a8fd
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2013-04-13T10:13:13.000000000Z" />
<EventRecordID>556</EventRecordID>
<Channel>Application</Channel>
<Computer>WarCenter</Computer>
<Security />
</System>
<EventData>
<Data>arma3.exe</Data>
<Data>0.52.103.507</Data>
<Data>5151a2b6</Data>
<Data>arma3.exe</Data>
<Data>0.52.103.507</Data>
<Data>5151a2b6</Data>
<Data>c0000005</Data>
<Data>0003d91f</Data>
<Data>1704</Data>
<Data>01ce38234288d828</Data>
<Data>C:\Program Files (x86)\Steam\steamapps\common\Arma 3\arma3.exe</Data>
<Data>C:\Program Files (x86)\Steam\steamapps\common\Arma 3\arma3.exe</Data>
<Data>bf62ded4-a422-11e2-be6c-d43d7e98a8fd</Data>
<Data>
</Data>
<Data>
</Data>
</EventData>
</Event>

Log Name: Application
Source: Application Error
Date: 4/13/2013 3:31:01 AM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: WarCenter
Description:
Faulting application name: PlanetSide2.exe, version: 0.0.0.0, time stamp: 0x5168a1d8
Faulting module name: PlanetSide2.exe, version: 0.0.0.0, time stamp: 0x5168a1d8
Exception code: 0xc00000fd
Fault offset: 0x00ffad27
Faulting process id: 0x1408
Faulting application start time: 0x01ce38313446ed80
Faulting application path: C:\Program Files (x86)\Steam\steamapps\common\PlanetSide 2\PlanetSide2.exe
Faulting module path: C:\Program Files (x86)\Steam\steamapps\common\PlanetSide 2\PlanetSide2.exe
Report Id: 3c3fc3f5-a425-11e2-be6c-d43d7e98a8fd
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2013-04-13T10:31:01.000000000Z" />
<EventRecordID>570</EventRecordID>
<Channel>Application</Channel>
<Computer>WarCenter</Computer>
<Security />
</System>
<EventData>
<Data>PlanetSide2.exe</Data>
<Data>0.0.0.0</Data>
<Data>5168a1d8</Data>
<Data>PlanetSide2.exe</Data>
<Data>0.0.0.0</Data>
<Data>5168a1d8</Data>
<Data>c00000fd</Data>
<Data>00ffad27</Data>
<Data>1408</Data>
<Data>01ce38313446ed80</Data>
<Data>C:\Program Files (x86)\Steam\steamapps\common\PlanetSide 2\PlanetSide2.exe</Data>
<Data>C:\Program Files (x86)\Steam\steamapps\common\PlanetSide 2\PlanetSide2.exe</Data>
<Data>3c3fc3f5-a425-11e2-be6c-d43d7e98a8fd</Data>
<Data>
</Data>
<Data>
</Data>
</EventData>
</Event>

KingKenny04 · Apr 13, 2013

Been googling around, and downloaded MSI live update. Ran it, and saw this:

https://dl.dropboxusercontent.com/u/75331142/Ooops.png

Apparently the chipset and mobo drivers I THOUGHT I installed were incorrect? Might this have something to do with the issue? In any case I'm updating them now.

EDIT: I'm wondering if the outdated chipset driver or lack of Intel ME driver had something to do with it. A couple of those logs mention missing or corrupted storage drivers, so maybe that's the cause? I'll update them and then run Planetside and see if I'm still having issues.

KingKenny04 · Apr 13, 2013

Further update. Installed that Intel ME driver and flashed the BIOS to the latest version. Seemed to do the trick. Just got done with a 2 hour session on Planetside 2, no issues whatsoever.

aramisathei · Apr 13, 2013

Glad to hear it's working better now. If issues do come up again, feel free to post and we'll work through it.

KingKenny04 · Apr 13, 2013

Games have been running fine, no more CTD's so far. However, another issue has cropped up. Just had a BSOD that suggested I should search "MEMORY_MANAGEMENT". The event viewer shows this:

Log Name: System
Source: Microsoft-Windows-WER-SystemErrorReporting
Date: 4/13/2013 8:16:55 PM
Event ID: 1001
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: WarCenter
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000001a (0x0000000000005003, 0xfffff70001080000, 0x000000000002dbf5, 0x0001953b0405b7ea). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 041313-25828-01.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-WER-SystemErrorReporting" Guid="{ABCE23E7-DE45-4366-8631-84FA6C525952}" EventSourceName="BugCheck" />
<EventID Qualifiers="16384">1001</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2013-04-14T03:16:55.000000000Z" />
<EventRecordID>771</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>System</Channel>
<Computer>WarCenter</Computer>
<Security />
</System>
<EventData>
<Data Name="param1">0x0000001a (0x0000000000005003, 0xfffff70001080000, 0x000000000002dbf5, 0x0001953b0405b7ea)</Data>
<Data Name="param2">C:\Windows\MEMORY.DMP</Data>
<Data Name="param3">041313-25828-01</Data>
</EventData>
</Event>

I'm not sure what it means. Is my memory bad? Are the slots on my mobo bad? Some googling has suggested that I run chkdsk, and I have it set to run next time I restart, but beyond that I don't really know what I'm looking for.

EDIT: Ran chkdsk. Windows also installed some updates when I restarted. Dunno if the problem is resolved or if that BSOD was just a freak occurrence. We shall see.

KingKenny04 · Apr 14, 2013

Just had another CTD, but this time the log is more specific.

Log Name: Application
Source: Application Error
Date: 4/13/2013 9:51:51 PM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: WarCenter
Description:
Faulting application name: ExeFile.exe, version: 2013.2.48.3842, time stamp: 0x511b6a0c
Faulting module name: _trinity_dx9_deploy.dll, version: 2013.2.48.5922, time stamp: 0x51225fbd
Exception code: 0xc0000005
Fault offset: 0x000d14ba
Faulting process id: 0xd0c
Faulting application start time: 0x01ce38c492cdbd75
Faulting application path: C:\Program Files (x86)\CCP\EVE\bin\ExeFile.exe
Faulting module path: C:\Program Files (x86)\CCP\EVE\bin\_trinity_dx9_deploy.dll
Report Id: 050ee72f-a4bf-11e2-be71-d43d7e98a8fd
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2013-04-14T04:51:51.000000000Z" />
<EventRecordID>1035</EventRecordID>
<Channel>Application</Channel>
<Computer>WarCenter</Computer>
<Security />
</System>
<EventData>
<Data>ExeFile.exe</Data>
<Data>2013.2.48.3842</Data>
<Data>511b6a0c</Data>
<Data>_trinity_dx9_deploy.dll</Data>
<Data>2013.2.48.5922</Data>
<Data>51225fbd</Data>
<Data>c0000005</Data>
<Data>000d14ba</Data>
<Data>d0c</Data>
<Data>01ce38c492cdbd75</Data>
<Data>C:\Program Files (x86)\CCP\EVE\bin\ExeFile.exe</Data>
<Data>C:\Program Files (x86)\CCP\EVE\bin\_trinity_dx9_deploy.dll</Data>
<Data>050ee72f-a4bf-11e2-be71-d43d7e98a8fd</Data>
<Data>
</Data>
<Data>
</Data>
</EventData>
</Event>

Something with DX9, I suppose. Although I thought EVE Online was on DX11. I'll poke around in the in-game graphics settings and google around some.

UPDATE: Just noticed something. I had been running two EVE clients (not unusual, EVE is set up to be able to run multiple instances of it at the same time). Only ONE of the clients crashed. The other is still running fine as of this moment. Not sure what that means, but it's something.

FURTHER UPDATE: Just had another "MEMORY_MANAGEMENT" BSOD. Getting really concerned now. Event log:

Log Name: System
Source: Microsoft-Windows-WER-SystemErrorReporting
Date: 4/13/2013 10:05:13 PM
Event ID: 1001
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: WARCENTER
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000001a (0x0000000000005003, 0xfffff70001080000, 0x00000000000396a0, 0x00031dd704072d40). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 041313-35515-01.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-WER-SystemErrorReporting" Guid="{ABCE23E7-DE45-4366-8631-84FA6C525952}" EventSourceName="BugCheck" />
<EventID Qualifiers="16384">1001</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2013-04-14T05:05:13.000000000Z" />
<EventRecordID>875</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>System</Channel>
<Computer>WARCENTER</Computer>
<Security />
</System>
<EventData>
<Data Name="param1">0x0000001a (0x0000000000005003, 0xfffff70001080000, 0x00000000000396a0, 0x00031dd704072d40)</Data>
<Data Name="param2">C:\Windows\MEMORY.DMP</Data>
<Data Name="param3">041313-35515-01</Data>
</EventData>
</Event>

UPDATE 3: Ran Memtest86, no errors found. I'm wondering if maybe the BSODs were due to the new BIOS, as they didn't start happening until AFTER I'd flashed it to the latest version. Now, after I flashed it, I also installed the new Intel ME driver and Audio driver. My worry is that flashing the BIOS was what solved my original CTD problem, and that flashing it back might cause the CTD's to start up again. Would it perhaps be a better option to flash to an even earlier BIOS version? Is there anyone who could possibly shed some light on this?

KingKenny04 · Apr 14, 2013

UPDATE: I've reflashed to the previous BIOS. Hopefully everything works now. If I get another CTD or BSOD, then I'll roll back one more version. If it persists, then I don't know what else to do. Hopefully someone here has some ideas for me.

UPDATE 2: Just CTD'd on me again. Fairly certain the culprit is this version of the BIOS. Will roll back to the version previous to this, if the problem persists I'm out of ideas and in desperate need of help.

UPDATE 3: Another CTD. At this point I'm inclined to believe the CTD issue exists in all BIOS versions previous to the latest one. The latest BIOS fixes that issue, but seems to have an issue with BSOD's. At this point I've run out of ideas. I'm considering doing a complete OS reinstall and redoing all of the drivers from scratch. Does ANYBODY have any other ideas?

KingKenny04 · Apr 14, 2013

OKAY! Hopefully final update. Did a complete OS reinstall. Installed all the proper and latest drivers the first time. Flashed BIOS to latest version. Redownloading Steam now, hopefully no more BSODs.

aramisathei · Apr 14, 2013

Best of luck, but odds are it wasn't the bios firmware to begin with.
If you're running into consistent memory management issues, it sounds more like a hardware issue.

If you notice these issues still cropping up, I'd look at your bios configuration (which might be why flashing your bios helped--it resets all values), and then physically inspect your mobo and connecting components themselves.

KingKenny04 · Apr 14, 2013

aramisathei :

What would I be looking for in the bios config? It's all gibberish to me.

KingKenny04 · Apr 14, 2013

UPDATE: After some further googling, apparently what I SHOULD have done was pull and test each individual stick in each slot with Memtest86. Tested the first stick in slot 2, on the second run it showed 20 errors. Let it run a few more cycles, no additional errors reported. Ran the second stick in the same slot, memtest ran almost 5 hours continuously (something like 7 or 8 cycles), no errors reported. So the culprit seems to be bad RAM. I'll be going in to Fry's tomorrow to swap it out, and this time I won't let them bring me one of their "previously opened" sets.

aramisathei · Apr 15, 2013

Yep. A proper memtest is long and boring, but it's one stick at a time, preferably per slot, to rule out any issues.
Lucky you caught it, since it only threw a couple errors throughout the entire process. Hopefully this will resolve your situation.

Search

New Build, all games CTD?

KingKenny04

Honorable

aramisathei

aramisathei

Honorable

KingKenny04

Honorable

KingKenny04

Honorable

KingKenny04

Honorable

aramisathei

Honorable

KingKenny04

Honorable

KingKenny04

Honorable

KingKenny04

Honorable

KingKenny04

Honorable

aramisathei

Honorable

KingKenny04

Honorable

KingKenny04

Honorable

aramisathei

Honorable

TRENDING THREADS

Latest posts

Moderators online

Share this page