LiveKernelEvent Games Crashing

[Khalexios]

Description
A problem with your hardware caused Windows to stop working correctly.

Problem signature
Problem Event Name: LiveKernelEvent
Code: 141
Parameter 1: ffffce8e12e9a010
Parameter 2: fffff8010e966b2c
Parameter 3: 0
Parameter 4: a98
OS version: 10_0_16299
Service Pack: 0_0
Product: 768_1
OS Version: 10.0.16299.2.0.0.768.101
Locale ID: 1033

Extra information about the problem
Bucket ID: LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys_Pascal_3D
Server information: 4bc3202d-c475-4c90-b834-50ac89423262

Seems to be shooting this error code any time i'm playing anything sorta new. I'm getting the same code playing destiny 2 or wildlands. But if i play stuff like WoW,Starcraft 2 then its fine.If i'm playing subnatica it might crash but its very rare.

I crash in random places.In game,loading screen, it doesnt seem to matter. Whatever game just stops responding and sends me back to desktop.

Specs are

CPU:AMD fx 8350

16 gigs ram

not sure about motherboard.I know its asus.

GPU:gtx 1080

windows 10

550 watt psu

I've done a reinstall of windows and updated it.Made sure the correct drivers are downloaded.I'm not sure what to do next.

I also ran a GPU Stress test,got up to 76c but other than that it never shot any error codes.

[SimicEngineer]

Could be flaky RAM, with the crash frequency correlating to memory usage/throughput causing you to hit the bad bit of RAM sooner (newer games => bigger assets). A GPU stress test wouldn't catch that.

[Khalexios]

I ran a memory test and used malware bytes to do a scan and still haven't come up with anything.

[x_wing]

The source of the problem seems to be in the gpu driver by the error output... If you've the drivers up to date and you really tested your system mem (used memtest86+?), the next suspect would be the PSU (You have a CPU of high power consuption + a high power consuption GPU).

So, What is your PSU brand? Does it have 80plus certificate?

[Big Boom Boom]

PSU crash doesnt show bsod. It would just reboot your PC or turn it off. DDU and reinstall driver to see if it fixes it.

[x_wing]

Początkowo opublikowane przez Big Boom Boom:

PSU crash doesnt show bsod. It would just reboot your PC or turn it off. DDU and reinstall driver to see if it fixes it.

Not necessary, it could be that it can't give the enough current for the VGA. With the current information, the problem could be anything.

[Khalexios]

I used DDU and then reinstalled the driver directly from the site.I booted up Wildlands and made it about halfway through the first mission and it crashed.

I also reinstalled wildlands to see if that would help.

The PSU is a 550 cooler master.Just looked it up heres the link to the specs
http://www.coolermaster.com/powersupply/extreme/extreme-power-plus-550w/

[x_wing]

Do you OC your cpu/gpu?

[Khalexios]

I have my gpu set to gaming mode...Which is suppose to be normal and i've never tried to OC my cpu

[rotNdude]

It's probably a game issue. I would ask in the appropriate game forums and post your complete computer specs.

[x_wing]

Początkowo opublikowane przez rotNdude:

It's probably a game issue. I would ask in the appropriate game forums and post your complete computer specs.

He has mention two games and seems to be an error at kernel level. Don't think that the devs will address his problem. Anyeay, maybe he's lucky and the report is forwarded to nvidia.

OP can you run cpu & gpu stress test at the same time? Maybe that gives us another clue.

[Khalexios]

While doing a furmark test and a prime 95 test at the same time. my gpu didnt get over 2 frames a sec.

Update:
Yea I started the gpu test first and i was at about 120 frames at 98 gpu load,when i started the cpu test next while the gpu test was going i went back to the gpu screen and the load was jumping between 20 and 35 percent and the frames stayed around 45 to 50.

I used Furmarks CPU burner and gpu stress test at the same time.

[Khalexios]

I got an upgraded cpu and a better power supply today.Went to my local shop.We switched gpu's,cpu's all sorts of stuff.Nothing fixed the issue.