Fixing LiveKernelEvent crashing Fallout 4

This post describes how I fixed crashes with Fallout 4 with the event name “LiveKernelEvent” when playing with an AMD GPU.

The Crash details

I found that after playing Fallout for a couple minutes it would crash. This would typically either crash to desktop (CTD) or the entire graphics driver would kill the computer. This would require a reboot to fix it.

This meant I was unable to play Fallout on my PC which was annoying. I have captured two of the errors logs below.

First Event log

Fault bucket , type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 0

Problem signature:
P1: 141
P2: ffffc405f5bfa4a0
P3: fffff80ca8f4f99c
P4: 0
P5: 3258
P6: 10_0_16299
P7: 0_0
P8: 256_1
P9: 
P10:

Attached files:
\\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20180113-0147.dmp
\\?\C:\WINDOWS\TEMP\WER-17535781-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERBAC1.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERBAC1.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERBAF1.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_141_815b15af774621b1484d7d331793e37ea5b4c173_00000000_cab_171bbb00

Analysis symbol: 
Rechecking for solution: 0
Report ID: 3a728af9-7992-499b-b430-9b0d0699c8f7
Report Status: 4
Hashed bucket:

Second Error Log

Log Name: Application
Source: Windows Error Reporting
Date: 28/03/2018 4:30:20 PM
Event ID: 1001
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: endor
Description:
Fault bucket LKD_0x141_Tdr:6_IMAGE_atikmpag.sys, type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 10f103ee-0526-44bd-9f36-f268f6e84744

Problem signature:
P1: 141
P2: ffffe70d6ec0b4a0
P3: fffff80a10adf99c
P4: 0
P5: 2904
P6: 10_0_16299
P7: 0_0
P8: 256_1
P9: 
P10:

Attached files:
\\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20180328-1629.dmp
\\?\C:\WINDOWS\TEMP\WER-106523562-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER77A1.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER77B0.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER77D0.tmp.txt
\\?\C:\Windows\Temp\WERADE4.tmp.WERDataCollectionStatus.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_e89f54f2c9766c892c637b9fe7361b83f24b16_00000000_cab_2151b6dc

Analysis symbol: 
Rechecking for solution: 0
Report ID: d42b919c-908d-4deb-861d-5090107512b0
Report Status: 268435456
Hashed bucket: 
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
 <System>
 <Provider Name="Windows Error Reporting" />
 <EventID Qualifiers="0">1001</EventID>
 <Level>4</Level>
 <Task>0</Task>
 <Keywords>0x80000000000000</Keywords>
 <TimeCreated SystemTime="2018-03-28T15:30:20.544192100Z" />
 <EventRecordID>1417</EventRecordID>
 <Channel>Application</Channel>
 <Computer>endor</Computer>
 <Security />
 </System>
 <EventData>
 <Data>LKD_0x141_Tdr:6_IMAGE_atikmpag.sys</Data>
 <Data>0</Data>
 <Data>LiveKernelEvent</Data>
 <Data>Not available</Data>
 <Data>10f103ee-0526-44bd-9f36-f268f6e84744</Data>
 <Data>141</Data>
 <Data>ffffe70d6ec0b4a0</Data>
 <Data>fffff80a10adf99c</Data>
 <Data>0</Data>
 <Data>2904</Data>
 <Data>10_0_16299</Data>
 <Data>0_0</Data>
 <Data>256_1</Data>
 <Data>
 </Data>
 <Data>
 </Data>
 <Data>
\\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20180328-1629.dmp
\\?\C:\WINDOWS\TEMP\WER-106523562-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER77A1.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER77B0.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER77D0.tmp.txt
\\?\C:\Windows\Temp\WERADE4.tmp.WERDataCollectionStatus.txt</Data>
 <Data>C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_e89f54f2c9766c892c637b9fe7361b83f24b16_00000000_cab_2151b6dc</Data>
 <Data>
 </Data>
 <Data>0</Data>
 <Data>d42b919c-908d-4deb-861d-5090107512b0</Data>
 <Data>268435456</Data>
 <Data>
 </Data>
 </EventData>
</Event>

Fixing the issue

To fix the issue you can modify the settings file located at C:\Users\[username]\Documents\My Games\Fallout4\Fallout4.ini.

In this file make sure these settings are set as below. Search for the string before the equals to find them.

bSAOEnable=0
sAntiAliasing=

These settings turn off Anti Aliasing and Ambient Occlusion, after these were disabled I was able to start and run Fallout 4 as expected.

If this worked for you or you have any questions please leave a comment. Enjoy!

Add a Comment

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.