Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Windows 10 - LiveKernelEvent Code 141


  • Please log in to reply
32 replies to this topic

#1 The_Brophy

The_Brophy

  • Members
  • 16 posts
  • OFFLINE
  •  
  • Local time:04:09 PM

Posted 30 August 2017 - 09:04 PM

Hey everyone,

 

I've been experiencing certain issues for quite a while now. More specifically, I consistently have black/green flashes every once in a while, even during normal use. I have had certain games crash in the past but those issues seem to ceased for the time being. I thought initially it was an issue with my cards memory, but I RMA'd my graphics card and still experience issues with the new card. Each time I notice this "flash", a LiveKernelEvent gets recorded (always Code 141).

 

Speccy Linkspeccy.piriform.com/results/auAabFxWYUtNLb54O75PxPC

 

Here is an example:

Problem Event Name: LiveKernelEvent

Code: 141

Parameter 1: ffff840d93330180

Parameter 2: fffff800b388cfec

Parameter 3: 0

Parameter 4: 948

OS version: 10_0_15063

Service Pack: 0_0

Product: 768_1

OS Version: 10.0.15063.2.0.0.768.101

Locale ID: 1033

 

System Specs:

Computer Type: Custom Built Desktop

GPU: Asus - GeForce GTX 1070 8GB STRIX Video Card

CPU: AMD - Ryzen 5 1600 3.2GHz 6-Core Processor

Motherboard: Gigabyte - GA-AB350-GAMING 3 ATX AM4

RAM: Corsair - Vengeance LPX 16GB (2 x 8GB) DDR4-3000

PSU: PEVGA - 650W 80+ Gold Certified Semi-Modular ATX

Operating System & Version: Windows 10

GPU Drivers: 385.28, clean install

 

I've tried certain troubleshooting techniques including reinstalling windows, using DDU in safemode and manual DL of latest Nvidia Driver, BIOS update, etc. I've managed to resolve game crashes for the most part through a BIOS update, but I still appear to get these "flashes" and Code 141 errors.

 

Any suggestions would be appreciated! Thanks


Edited by The_Brophy, 30 August 2017 - 10:08 PM.


BC AdBot (Login to Remove)

 


m

#2 bwv848

bwv848

    Bleepin' Owl


  • BSOD Kernel Dump Expert
  • 2,473 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:92.96 million miles away from the sun
  • Local time:07:09 PM

Posted 30 August 2017 - 09:16 PM

Please follow these BSOD posting instructions and attach the requested files by replying to this topic so we can provide a FULL analysis. You may skip the part of step three where it instructs you to create a new topic, since you already have a topic here. There's no need to create another topic. :wink:

 

In the meanwhile, try driver version 372.70 from ASUS's website:

 

http://dlcdnet.asus.com/pub/ASUS/vga/nVidia/NVDriver_Win10_64_VER372_70WHQL.zip

 

and version 368.39:

 

http://dlcdnet.asus.com/pub/ASUS/vga/nVidia/NVDriver_Win10_64_VER368_39.zip

 

BOTH are specifically approved for your model.

 

When reinstalling your graphics driver, please perform a Custom Installation, as demonstrated below:
3SKjXsp.jpg
Also, when you click Next, make sure you only install the Graphics Driver (and the PhysX System Software if you're a gamer). Also, check Perform a clean installation (see below):

Warning! Please read this first.
PLEASE DO NOT INSTALL ANY 3D DRIVERS!!! I've seen them cause odd issues before.


1bTMUDx.jpg

 

While waiting for a response, I suggest you run these free hardware diagnostics. Run ALL the tests (especially the video ones) and let us know the results.
 


Edited by bwv848, 30 August 2017 - 09:16 PM.


#3 The_Brophy

The_Brophy
  • Topic Starter

  • Members
  • 16 posts
  • OFFLINE
  •  
  • Local time:04:09 PM

Posted 30 August 2017 - 09:42 PM

Thanks for the reply! I have linked Speccy and have also attached the zip file to this message. I will attempt those troubleshooting items in the meantime.



#4 bwv848

bwv848

    Bleepin' Owl


  • BSOD Kernel Dump Expert
  • 2,473 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:92.96 million miles away from the sun
  • Local time:07:09 PM

Posted 30 August 2017 - 09:46 PM

Hi,

 

Sorry the file and URL didn't make the trip. Will you please try again?

 

Regards,

bwv848



#5 The_Brophy

The_Brophy
  • Topic Starter

  • Members
  • 16 posts
  • OFFLINE
  •  
  • Local time:04:09 PM

Posted 30 August 2017 - 10:15 PM

My apologies, I've attached the file to this reply. For some reason when I run the Speccy, I am able to open it when I select "Open in Browser", but when I "Copy to Clipboard" and post in URL it doesn't find the page.

Attached Files



#6 bwv848

bwv848

    Bleepin' Owl


  • BSOD Kernel Dump Expert
  • 2,473 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:92.96 million miles away from the sun
  • Local time:07:09 PM

Posted 30 August 2017 - 10:28 PM

No problem, the link still works for me after editing the URL. Your graphics card was at 66°C while you were running Speccy. That is somewhat high. Were you gaming when you ran Speccy?

Please continue to check whether if there are any BIOS updates or Windows updates for your system. I'll wait and see what the outcome of using ASUS's approved graphics drivers is.



#7 The_Brophy

The_Brophy
  • Topic Starter

  • Members
  • 16 posts
  • OFFLINE
  •  
  • Local time:04:09 PM

Posted 30 August 2017 - 10:36 PM

Yes, I was running a pretty intensive game while Speccy ran (PUBG). I should mention that the issue primarily persists while playing games, yet does tend to occur during normal use from time to time.

 

I checked and there are no new BIOS or Windows updates for my system. I will try the ASUS drivers and report back.



#8 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 24,685 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:07:09 PM

Posted 31 August 2017 - 07:54 AM

Are you overclocking (lot's of PrecisionX errors in the WER section of MSINFO32)?

If so, please remove the overclock while we're troubleshooting.


- John  (my website: http://www.carrona.org/ )
**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message.

 

My eye problems have lessened and I'm able to post/respond without too much difficulty. (05 Sep 2017)
FYI - I am completely blind in the right eye and ~30% blind in the left eye.

If the eye problems come on suddenly, I may not be able to respond.
If that's the case and help is needed, please PM a staff member for assistance.


#9 bwv848

bwv848

    Bleepin' Owl


  • BSOD Kernel Dump Expert
  • 2,473 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:92.96 million miles away from the sun
  • Local time:07:09 PM

Posted 31 August 2017 - 09:41 PM

Are you overclocking (lot's of PrecisionX errors in the WER section of MSINFO32)?

If so, please remove the overclock while we're troubleshooting.

Thank you for pointing this out, John! :) Totally missed that!



#10 The_Brophy

The_Brophy
  • Topic Starter

  • Members
  • 16 posts
  • OFFLINE
  •  
  • Local time:04:09 PM

Posted 31 August 2017 - 09:51 PM

So I haven't done any overclocking on the card apart from how it was from the factory (I believe they come pre-overclocked?). A recommendation was to download PrecisionX and attempt to lower the GPU Core clock on the card (Operates around 1890 MHz in game) to see if that would fix my issue. Unfortunately, it didn't seem to do the trick. This was performed on the original card btw, and not the new card (received from RMA).

 

I downloaded 372.70 and will try it out now and report back!


Edited by The_Brophy, 31 August 2017 - 10:11 PM.


#11 The_Brophy

The_Brophy
  • Topic Starter

  • Members
  • 16 posts
  • OFFLINE
  •  
  • Local time:04:09 PM

Posted 31 August 2017 - 11:47 PM

Update: So far, so good on that driver after 2 hours or so! No issues to report and no Code 141 errors. Only thing I noticed was while loading a game it suggested to update to 372.90 as 372.70 had known errors, but I haven't had any issues.


Edited by The_Brophy, 31 August 2017 - 11:47 PM.


#12 bwv848

bwv848

    Bleepin' Owl


  • BSOD Kernel Dump Expert
  • 2,473 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:92.96 million miles away from the sun
  • Local time:07:09 PM

Posted 01 September 2017 - 08:18 AM

Glad to know that. Let's see how everything turns out after a week or so. 



#13 The_Brophy

The_Brophy
  • Topic Starter

  • Members
  • 16 posts
  • OFFLINE
  •  
  • Local time:04:09 PM

Posted 04 September 2017 - 05:22 PM

Update: Hope everyone had a great long weekend! I tested out the drivers some more today and still appear to be having issues unfortunately (Code 141 LiveKernelEvent, Black/Green flashes intermiddently, etc.).

Not sure if this will help, but got the following crash logs from one of my games:

<?xml version="1.0" encoding="UTF-8"?>
<FGenericCrashContext>
<RuntimeProperties>
<CrashVersion>3</CrashVersion>
<CrashGUID>UE4CC-Windows-47C5F35A489F66C11E0572A77C568FC3_0000</CrashGUID>
<ProcessId>8116</ProcessId>
<IsInternalBuild>false</IsInternalBuild>
<IsPerforceBuild>false</IsPerforceBuild>
<IsSourceDistribution>false</IsSourceDistribution>
<IsEnsure>false</IsEnsure>
<IsAssert>true</IsAssert>
<CrashType>Assert</CrashType>
<SecondsSinceStart>45</SecondsSinceStart>
<GameName>UE4-TslGame</GameName>
<ExecutableName>TslGame</ExecutableName>
<BuildConfiguration>Shipping</BuildConfiguration>
<GameSessionID></GameSessionID>
<PlatformName>WindowsNoEditor</PlatformName>
<PlatformNameIni>Windows</PlatformNameIni>
<EngineMode>Game</EngineMode>
<EngineModeEx>Unset</EngineModeEx>
<DeploymentName></DeploymentName>
<EngineVersion>4.14.3-0+++UE4+Release-4.14</EngineVersion>
<CommandLine>-LobbyUrl=front.battlegroundsgame.com/index.html</CommandLine>
<LanguageLCID>1033</LanguageLCID>
<AppDefaultLocale>en_US</AppDefaultLocale>
<BuildVersion>++UE4+Release-4.14-CL-0</BuildVersion>
<IsUE4Release>true</IsUE4Release>
<UserName></UserName>
<BaseDir>C:/Program Files (x86)/Steam/steamapps/common/PUBG/TslGame/Binaries/Win64/</BaseDir>
<RootDir>C:/Program Files (x86)/Steam/steamapps/common/PUBG/</RootDir>
<MachineId>F467BF3348C8E35577EF17B1F2D2F247</MachineId>
<EpicAccountId></EpicAccountId>
<CallStack></CallStack>
<SourceContext></SourceContext>
<UserDescription></UserDescription>
<UserActivityHint></UserActivityHint>
<ErrorMessage>LowLevelFatalError [File:D:\tsl\tsl-client-branch\build\UnrealEngine\Engine\Source\Runtime\Windows\D3D11RHI\Private\D3D11Util.cpp] [Line: 176] &nl;Unreal Engine is exiting due to D3D device being lost. (Error: 0x887A0006 - &apos;HUNG&apos;)&nl;</ErrorMessage>
<CrashDumpMode>0</CrashDumpMode>
<CrashReporterMessage></CrashReporterMessage>
<Misc.NumberOfCores>6</Misc.NumberOfCores>
<Misc.NumberOfCoresIncludingHyperthreads>12</Misc.NumberOfCoresIncludingHyperthreads>
<Misc.Is64bitOperatingSystem>1</Misc.Is64bitOperatingSystem>
<Misc.CPUVendor>AuthenticAMD</Misc.CPUVendor>
<Misc.CPUBrand>AMD Ryzen 5 1600 Six-Core Processor            </Misc.CPUBrand>
<Misc.PrimaryGPUBrand>NVIDIA GeForce GTX 1070</Misc.PrimaryGPUBrand>
<Misc.OSVersionMajor>Windows 10</Misc.OSVersionMajor>
<Misc.OSVersionMinor></Misc.OSVersionMinor>
<MemoryStats.TotalPhysical>17128894464</MemoryStats.TotalPhysical>
<MemoryStats.TotalVirtual>140737488224256</MemoryStats.TotalVirtual>
<MemoryStats.PageSize>65536</MemoryStats.PageSize>
<MemoryStats.TotalPhysicalGB>16</MemoryStats.TotalPhysicalGB>
<MemoryStats.AvailablePhysical>13079871488</MemoryStats.AvailablePhysical>
<MemoryStats.AvailableVirtual>140734314840064</MemoryStats.AvailableVirtual>
<MemoryStats.UsedPhysical>1205678080</MemoryStats.UsedPhysical>
<MemoryStats.PeakUsedPhysical>1349062656</MemoryStats.PeakUsedPhysical>
<MemoryStats.UsedVirtual>1966915584</MemoryStats.UsedVirtual>
<MemoryStats.PeakUsedVirtual>2750181376</MemoryStats.PeakUsedVirtual>
<MemoryStats.bIsOOM>0</MemoryStats.bIsOOM>
<MemoryStats.OOMAllocationSize>0</MemoryStats.OOMAllocationSize>
<MemoryStats.OOMAllocationAlignment>0</MemoryStats.OOMAllocationAlignment>
</RuntimeProperties>
<PlatformProperties>
<PlatformIsRunningWindows>1</PlatformIsRunningWindows>
<PlatformCallbackResult>0</PlatformCallbackResult>
</PlatformProperties>
</FGenericCrashContext>


#14 bwv848

bwv848

    Bleepin' Owl


  • BSOD Kernel Dump Expert
  • 2,473 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:92.96 million miles away from the sun
  • Local time:07:09 PM

Posted 04 September 2017 - 09:19 PM

Have you tried 368.39 as asked before?



#15 The_Brophy

The_Brophy
  • Topic Starter

  • Members
  • 16 posts
  • OFFLINE
  •  
  • Local time:04:09 PM

Posted 05 September 2017 - 08:36 PM

Yes, I have tried both 368.39 and 372.70. Unfortunately, issue appears to persist with both.

 

Update: Got a blue screen crash while on 368.39:

 

Problem Event Name: BlueScreen
Code: 119
Parameter 1: 5
Parameter 2: ffff9e8234957000
Parameter 3: ffff9e82373f7010
Parameter 4: 9fb3
OS version: 10_0_15063
Service Pack: 0_0
Product: 768_1
OS Version: 10.0.15063.2.0.0.768.101
Locale ID: 1033

Edited by The_Brophy, 05 September 2017 - 08:46 PM.





1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users