All games crash within 10 minutes of opening

[Abzilla]

So I have finally gotten my pc to fully boot and I have checked the CPU temps beforehand. The CPU wouldn't go below 60C in anyway and would generally stay in the 70s. After updating the bios, my CPU temps idle at 35-45C!! It occasionally spikes to 50C ish when browsing pages, but now it isn't sticking at 70-80C! Although, I need to keep the liquid temp in consideration. In my previous pics, the liquid temp was at 50C whereas now it is at 30C (likely as I have just booted up). I will test this out and see if games play like normal.

 

I have also currently left XMP off and will turn it back on after stability has been confirmed.

 

 

[Abzilla]

Ok so now I have tried loading into a save of ETS2 and once my save loads, the game crashes instantly.

I verified the integrity of the game beforehand.

 

 

[Bjoolz]

Program crashes are a bit of a pain in the ass to debug, but I can give it a go.

 

First check C:\Windwos\LiveKernelReports if you have any dump files. If you do, copy the folder itself to the desktop (Use the Downloads folder if you have OneDrive syncing the desktop) and zip it. Attach it to a post here.

 

Do the same with \Appdata\Local\CrashDumps. Windows key + R and entering "%localappdata%\CrashDump" should get you there directly. Same procedure as the previous folder. 

[Damocles Ti]

Well... at least we solved the CPU temps, is there anything in event viewer?

[Abzilla]

17 hours ago, Bjoolz said:

Program crashes are a bit of a pain in the ass to debug, but I can give it a go.

 

First check C:\Windwos\LiveKernelReports if you have any dump files. If you do, copy the folder itself to the desktop (Use the Downloads folder if you have OneDrive syncing the desktop) and zip it. Attach it to a post here.

 

Do the same with \Appdata\Local\CrashDumps. Windows key + R and entering "%localappdata%\CrashDump" should get you there directly. Same procedure as the previous folder. 

I tried doing the crashdumps too, however the zip file is 64mb, it's too big to upload.

 

13 hours ago, Damocles Ti said:

Well... at least we solved the CPU temps, is there anything in event viewer?

Yes:

Copy of Livekernelreports.zip

[Damocles Ti]

9 minutes ago, Abzilla said:

I tried doing the crashdumps too, however the zip file is 64mb, it's too big to upload.

 

Yes:

Copy of Livekernelreports.zip 2.44 MB · 0 downloads

Can we get a glimpse of what's inside the windows logs>system (on the left pane) then on the right pane: filter current log>*select critical, and error* then screen shot or copy paste any unique entries you see that occur around the time of the crashes? In particular, we're looking for WHEA-Logger if there are any, but we also want to see what errors windows sees before it crashes

[Abzilla]

8 minutes ago, Damocles Ti said:

Can we get a glimpse of what's inside the windows logs>system (on the left pane) then on the right pane: filter current log>*select critical, and error* then screen shot or copy paste any unique entries you see that occur around the time of the crashes? In particular, we're looking for WHEA-Logger if there are any, but we also want to see what errors windows sees before it crashes

 

I tried playing at approx 4-5pm to test the system but found the error timestamped at 9pm

[Damocles Ti]

7 minutes ago, Abzilla said:

Welp, that's unlucky, I'm guessing you're still running stock, no overclock (I think if you're running PBO at stock it should be acceptable as well) what we have here is an issue where the CPU cache is faulty. This detection could be a false alarm: memory could have fed it bad data or the IO die could have failed to transfer data from disk/memory to CPU cache. Either way, if you see this a lot, that means the core (APIC ID 8 is core 4, I assume that's one of your faster cores) is unstable or defective in the cache. If you don't have anything aside from PBO, then I would consider the CPU defective and RMA it. I know that PBO is technically overclocking, but I was able to RMA my CPU after expressly noting that PBO (at stock) is a baseline feature I'm buying the CPUs for with an expectation of the feature to work.

[Bjoolz]

9 hours ago, Abzilla said:

I tried doing the crashdumps too, however the zip file is 64mb, it's too big to upload.

 

Yes:

Copy of Livekernelreports.zip 2.44 MB · 1 download

Use a file host and link here. I also saw your WHEA events, have you had any BSODs? Check C:\Windows\Minidump just in case as the screen can go black/freeze making you not see it. If you have any dump files then go back and copy the folder itself somewhere else because Windows hates you messing with files here, then zip the copied folder and upload here.

 

The WHEA events suggest a CPU issue, but in the program crashes you had 8 crashes yesterday that were because of the video engine timing out which suggests GPU driver/the GPU itself. 

[Abzilla]

12 hours ago, Bjoolz said:

Use a file host and link here. I also saw your WHEA events, have you had any BSODs? Check C:\Windows\Minidump just in case as the screen can go black/freeze making you not see it. If you have any dump files then go back and copy the folder itself somewhere else because Windows hates you messing with files here, then zip the copied folder and upload here.

 

The WHEA events suggest a CPU issue, but in the program crashes you had 8 crashes yesterday that were because of the video engine timing out which suggests GPU driver/the GPU itself. 

I checked the minidump folder which says it's empty.

 

Here is a link for the crashdumps copy

 

https://uploadnow.io/f/8kDQskw

[Abzilla]

I have booted up ets2 again and refined the eventviewer to show the most recent errors.

I entered ETS2 escape menu where you are already loaded into the save, but not driving around. Once I click "drive" the game starts loading the world, which it seems to do successfully. Although once loaded within a few seconds the game freezes, then goes black screen and closes the application.

 

Here are the errors from eventviewer after such:

 

 

 

Below I have created a new filter to include information which seems to bring some relevant information:

 

 

 

 

In addition, my disk management could be to blame? 

 

[Bjoolz]

9 hours ago, Abzilla said:

I checked the minidump folder which says it's empty.

 

Here is a link for the crashdumps copy

 

https://uploadnow.io/f/8kDQskw

All of the Euro Truck crashes are GPU/GPU driver related, Nvidia .dll directly or Direct3D files. If you have not tried DDU I would do so. Link to guide and download links.

 

One crash had the ASUS GPU fan tool you got installed involved so perhaps that's doing something stupid? Worth trying to uninstall. I also looked through your new screenshots and some mentioned corruption. It's possible you got a storage drive on the way out corrupting random stuff and being the root cause of this.

 

Modern SSDs have terrible self diagnostics which basically all storage tools rely on for checking health, but we can look anyway and we can check other drives. Guide here on CrystalDiskInfo and paste the output to pastebin.com and link here.

[BlackManINC]

On 7/4/2023 at 8:27 AM, Abzilla said:

 

I tried playing at approx 4-5pm to test the system but found the error timestamped at 9pm

Does it give you an actual bug check code in the "details" tab? 

[Abzilla]

On 7/6/2023 at 1:38 AM, BlackManINC said:

Does it give you an actual bug check code in the "details" tab? 

I found the event, this is the detail tab of both WHEA events:

On 7/5/2023 at 8:28 PM, Bjoolz said:

All of the Euro Truck crashes are GPU/GPU driver related, Nvidia .dll directly or Direct3D files. If you have not tried DDU I would do so. Link to guide and download links.

 

One crash had the ASUS GPU fan tool you got installed involved so perhaps that's doing something stupid? Worth trying to uninstall. I also looked through your new screenshots and some mentioned corruption. It's possible you got a storage drive on the way out corrupting random stuff and being the root cause of this.

 

Modern SSDs have terrible self diagnostics which basically all storage tools rely on for checking health, but we can look anyway and we can check other drives. Guide here on CrystalDiskInfo and paste the output to pastebin.com and link here.

I will try wiping my current GPU drivers with DDU

 

I assume the Asus GPU fan thing is this? Is there a possibility any OC profiles could be engaging while playing?

[Bjoolz]

40 minutes ago, Abzilla said:

I assume the Asus GPU fan thing is this?

Sorry, no idea, that's all the info it gave me. 

[Abzilla]

1 hour ago, Bjoolz said:

Sorry, no idea, that's all the info it gave me. 

No worries! I appreciate all of the help i'm getting here.

 

I used DDU and reinstalled the Nvidia driver, but when I tried loading ETS2, when trying to load into the world, the loading screen had artefacts and the game crashed while loading. Beforehand, the game would at least enter the world and crash straight after, after DDU the world doesn't load.

 

 

This is what I am seeing in GPU-Z's sensor page. I have also attached logs

 

In the pics above, I noticed power consumption reached as high as 103% of TDP, could this be of issue?

GPU-Z Sensor Log1.txt

[BlackManINC]

12 hours ago, Abzilla said:

I found the event, this is the detail tab of both WHEA events:

 

 

What about the system tab? If its a "critical error" message, there should be a "bugcheck" code somewhere. 

[Bjoolz]

3 hours ago, BlackManINC said:

What about the system tab? If its a "critical error" message, there should be a "bugcheck" code somewhere. 

It's an event, it didn't crash from this so no bugcheck.

 

@Abzilla The mix of CPU WHEA events and GPU driver crashes is confusing. The only logical thing I can draw from this is that it's something the two have in common. In my mind that would be power or motherboard. 

[BlackManINC]

8 hours ago, Bjoolz said:

It's an event, it didn't crash from this so no bugcheck.

 

@Abzilla The mix of CPU WHEA events and GPU driver crashes is confusing. The only logical thing I can draw from this is that it's something the two have in common. In my mind that would be power or motherboard. 

I hope not. Because you'd have to replace the motherboard.