#live kernel (2) the electric troubleshoot

1 messages · Page 1 of 1 (latest)

crisp cove
#

Well...its happen again. And this time it occur by a non directx 9 game. This time its warframe.....which has occur again right now in fact. This is rare because i been playing this game and no issue even occured untill now.

Currently doing a window memory diognastic to see the issue at hand.

crisp cove
#

no issue

craggy hemlock
#

use memtest86

crisp cove
#

memtest86?

craggy hemlock
#

yes

#

windows memory test suck

crisp cove
#

do you have a link for me to use?

craggy hemlock
#

how much ram u got?

craggy hemlock
crisp cove
#

i dont haave one

craggy hemlock
#

u dont have usb?

crisp cove
#

nope

#

but something tells me its because of overheating if anything

#

cant be too sure

#

warframe havent get a crash like that since idk ever

craggy hemlock
crisp cove
craggy hemlock
#

Laptop?

crisp cove
#

yup

craggy hemlock
#

Oh well u cant test what component overheating

crisp cove
#

warframe luckliy have a side spercificly for this very issue

#
#

this show the issue about it

#

gonna try playing it again to see if this issue happen again. because that would mean directx 11 game would potentionally become unplayable

crisp cove
#

Again?

#

I need to underclock it

#

Hmmm undervoltinh

crisp cove
#

first strike

#

second strike

craggy hemlock
#

Do dxdiag in window search

crisp cove
crisp cove
#

Hello?

crisp cove
#

ok...i think i manage to "i think" fix itt

if its what i was thinking. its must be a corrupted driver

crisp cove
#

i think its really is a fix

crisp cove
#

Also. Its not a corrupted driver. More luke corrputed system file

craggy hemlock
#

with 30gb capacity

crisp cove
#

hmmm

#

i got the same that supposed to be alive kernel 190

#

but there is non

#

and i can feel this laptop being very hot

#

hmmm. even more interesting. unlike last time. this one has no corrupted file

crisp cove
#

Look like kernel 190 have been stopped.
Unfortunately kernel 141 will remain

crisp cove
#

AGAIN?

hollow horizon
#

i have the same error issues livekernelevent 141

#

this bs error can be caused for server reasons which makes it frustrating to diagnose every single one of it

#

i have been facing this since December seems like youve had this much earlier

#

I have tried switching to new ram sticks and ssds they didn't work either

fleet galleon
#

please uninstall drivers with DDU and reinstall drivers

onyx steepleBOT
#

For a utility to automate DDU as much as possible follow this guide.