Random crashes in games

[PeryForTheHunter]

Hi Guys

I am stuck and confused.

I7 7700k stock
GTX 1080
Asus Strix Z270E
16 gb crucial 2133
2 tb western digital 7200 rpm
Windows 10 64 bit home
1000w EVGA super nova

Its a new build.

Drivers are all up to date

The PC turns on fine and works fine.

I have done countless stress tests for my CPU and Ram no problems.

Temps are optimal.

I have played two games on it so far and they both crash after 20-60 minutes.
GTA 5 and Crysis 3.

Temps and load are all fine during gameplay and nothing out of the ordinary.

Done some more stress tests and the CPU and ram both pass with flying colors.

I am not sure what else I can do.

 

[marko55]

Anything in your windows event logs? Check system and application logs to see if any errors are logged at the time of the crash.

Wouldn't hurt to create a bootable memtest thumb drive, boot to that & let it run overnight either to see if it spits back any RAM errors. Typically several hours of stress testing under Prime95 will bring RAM problems to light but memtest will actually tell you if its the RAM causing an issue. Many times when there's an inexplicable and random freeze/crash scenario its RAM.

 

[PeryForTheHunter]

Anything in your windows event logs? Check system and application logs to see if any errors are logged at the time of the crash.

Wouldn't hurt to create a bootable memtest thumb drive, boot to that & let it run overnight either to see if it spits back any RAM errors. Typically several hours of stress testing under Prime95 will bring RAM problems to light but memtest will actually tell you if its the RAM causing an issue. Many times when there's an inexplicable and random freeze/crash scenario its RAM.

Hi

I forgot to mention that I have done the mdsched.exe test that windows has. That came back with no errors found.

I will keep an eye on the logs and post the finding when I can.

Thanks

 

[Calvin7]

Minimum memory speed for your setup is 2400MHz. I7 7700k can use even faster, higher frequency memory.

You list yours at 16 gb crucial 2133.

 

[marko55]

2400 is not the "minimum." You can operate memory anywhere from 2133 to 3200. Just depends on the memory and the motherboard's ability to OC it.

 

[urbancamper]

You said it's a new build. Does that mean the gpu is also new? Could it be that the gpu fans are not spinning up enough? Are you maybe overclocking the gpu and that is crashing it? I see that gpu has 4 fans. Another thought would be you are using an aftermarket app with it and it is interfering with the fans operation.

 

[PeryForTheHunter]

You said it's a new build. Does that mean the gpu is also new? Could it be that the gpu fans are not spinning up enough? Are you maybe overclocking the gpu and that is crashing it? I see that gpu has 4 fans. Another thought would be you are using an aftermarket app with it and it is interfering with the fans operation.

The GPU is working fine as i can see. The GPU is from my old PC is and has been working fine.

The temps on the GPU are similar to the ones on my old PC.

 

[PeryForTheHunter]

This is the most recent crash log that I got.

Faulting application name: crysis3.exe, version: 1.3.0.0, time stamp: 0x51ee2fd1
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x8c852bc0
Faulting process id: 0x1e9c
Faulting application start time: 0x01d2c27c708afd7f
Faulting application path: C:\Program Files (x86)\Origin Games\Crysis 3\Bin32\crysis3.exe
Faulting module path: unknown
Report Id: 0d211953-b861-4ced-8e35-d9667faae2d8
Faulting package full name:
Faulting package-relative application ID:

Any ideas?

 

[PeryForTheHunter]

Anything in your windows event logs? Check system and application logs to see if any errors are logged at the time of the crash.

Wouldn't hurt to create a bootable memtest thumb drive, boot to that & let it run overnight either to see if it spits back any RAM errors. Typically several hours of stress testing under Prime95 will bring RAM problems to light but memtest will actually tell you if its the RAM causing an issue. Many times when there's an inexplicable and random freeze/crash scenario its RAM.

Most recent event log
Faulting application name: crysis3.exe, version: 1.3.0.0, time stamp: 0x51ee2fd1
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x8c852bc0
Faulting process id: 0x1e9c
Faulting application start time: 0x01d2c27c708afd7f
Faulting application path: C:\Program Files (x86)\Origin Games\Crysis 3\Bin32\crysis3.exe
Faulting module path: unknown
Report Id: 0d211953-b861-4ced-8e35-d9667faae2d8
Faulting package full name:
Faulting package-relative application ID:

 

[marko55]

Have you run malwarebytes to see if anything turns up?

 

[PeryForTheHunter]

I have run Prime95 and did the blend test. Soon as the test starts it stops and it says error. Looking at the log it says.

FATAL ERROR: Rounding was 0.5, expected less than 0.4
Hardware failure detected, consult stress.txt file.
FATAL ERROR: Rounding was 0.5, expected less than 0.4
Hardware failure detected, consult stress.txt file.
FATAL ERROR: Rounding was 0.4972167823, expected less than 0.4
Hardware failure detected, consult stress.txt file.
FATAL ERROR: Rounding was 0.4976898512, expected less than 0.4
Hardware failure detected, consult stress.txt file.
FATAL ERROR: Rounding was 0.5, expected less than 0.4
Hardware failure detected, consult stress.txt file.
FATAL ERROR: Rounding was 0.5, expected less than 0.4
Hardware failure detected, consult stress.txt file.
FATAL ERROR: Rounding was 0.5, expected less than 0.4
Hardware failure detected, consult stress.txt file.
FATAL ERROR: Rounding was 0.4971671965, expected less than 0.4
Hardware failure detected, consult stress.txt file.
FATAL ERROR: Rounding was 0.4982019377, expected less than 0.4
Hardware failure detected, consult stress.txt file.
FATAL ERROR: Rounding was 0.4992001041, expected less than 0.4
Hardware failure detected, consult stress.txt file.
FATAL ERROR: Rounding was 0.4956497362, expected less than 0.4
Hardware failure detected, consult stress.txt file.
FATAL ERROR: Rounding was 0.5, expected less than 0.4
Hardware failure detected, consult stress.txt file.
FATAL ERROR: Rounding was 0.4983882159, expected less than 0.4
Hardware failure detected, consult stress.txt file.
FATAL ERROR: Rounding was 0.4962722541, expected less than 0.4
Hardware failure detected, consult stress.txt file.
FATAL ERROR: Rounding was 0.4999815515, expected less than 0.4
Hardware failure detected, consult stress.txt file.
FATAL ERROR: Rounding was 0.4975799466, expected less than 0.4
Hardware failure detected, consult stress.txt file.
FATAL ERROR: Rounding was 0.5, expected less than 0.4
Hardware failure detected, consult stress.txt file.
FATAL ERROR: Rounding was 0.4986700007, expected less than 0.4
Hardware failure detected, consult stress.txt file.
FATAL ERROR: Rounding was 0.5, expected less than 0.4
Hardware failure detected, consult stress.txt file.
FATAL ERROR: Rounding was 0.5, expected less than 0.4
Hardware failure detected, consult stress.txt file.

Any ideas?

 

[urbancamper]

There is a new bios out that fixes the faults in prime. Of course this may not fix your problem but it is worth a try. This should fix the errors in prime.

As far as the game crash issue. Is it possible that you may just have to go to a different driver? The current one seems ok. The last one had some issues from what I understand. You may want to try not the last one(if you are using the current one but 2 drivers back. Current 381.89 \ two back 378.92.