Linux Mint 19.3 XFCE Shuts Down Suddenly SOLVED

Alexzee

Alexzee

Well-Known Member
Joined
Jun 1, 2019
Messages
4,183
Reaction score
2,291
Credits
25,718
I've got Linux Mint 19.3 XFCE running on this custome built 64-bit desktop and all was running fine.

All of the sudden the desktop shutdown while I was online reading a news article.

Anyone have any ideas what may have cause the not so graceful shut down?

Here's the end of the dmesg log:


(Note that use of the override may cause unknown side effects.)
[ 11.134974] EDAC amd64: Node 0: DRAM ECC disabled.
[ 11.134975] EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load.
Either enable ECC checking or force module loading by setting 'ecc_enable_override'.
(Note that use of the override may cause unknown side effects.)
[ 11.179013] EDAC amd64: Node 0: DRAM ECC disabled.
[ 11.179014] EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load.
Either enable ECC checking or force module loading by setting 'ecc_enable_override'.
(Note that use of the override may cause unknown side effects.)
[ 11.227354] EDAC amd64: Node 0: DRAM ECC disabled.
[ 11.227355] EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load.
Either enable ECC checking or force module loading by setting 'ecc_enable_override'.
(Note that use of the override may cause unknown side effects.)
[ 11.259343] EDAC amd64: Node 0: DRAM ECC disabled.
[ 11.259344] EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load.
Either enable ECC checking or force module loading by setting 'ecc_enable_override'.
(Note that use of the override may cause unknown side effects.)
[ 11.303347] EDAC amd64: Node 0: DRAM ECC disabled.
[ 11.303349] EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load.
Either enable ECC checking or force module loading by setting 'ecc_enable_override'.
(Note that use of the override may cause unknown side effects.)
[ 96.003213] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 96.003214] Bluetooth: BNEP filters: protocol multicast
[ 96.003216] Bluetooth: BNEP socket layer initialized
[ 96.071651] vboxdrv: loading out-of-tree module taints kernel.
[ 96.071794] vboxdrv: module verification failed: signature and/or required key missing - tainting kernel
[ 96.076059] vboxdrv: Found 12 processor cores
[ 96.094625] vboxdrv: TSC mode is Invariant, tentative frequency 3792890285 Hz
[ 96.094626] vboxdrv: Successfully loaded version 6.1.4 (interface 0x002d0001)
[ 96.102229] Generic Realtek PHY r8169-500:00: attached PHY driver [Generic Realtek PHY] (mii_bus:phy_addr=r8169-500:00, irq=IGNORE)
[ 96.211620] r8169 0000:05:00.0 enp5s0: Link is Down
[ 96.223426] iwlwifi 0000:04:00.0: Applying debug destination EXTERNAL_DRAM
[ 96.296712] VBoxNetFlt: Successfully started.
[ 96.297307] VBoxNetAdp: Successfully started.
[ 96.337791] iwlwifi 0000:04:00.0: Applying debug destination EXTERNAL_DRAM
[ 96.400903] iwlwifi 0000:04:00.0: FW already configured (0) - re-configuring
[ 96.562487] radeon_dp_aux_transfer_native: 158 callbacks suppressed
[ 115.818662] radeon_dp_aux_transfer_native: 74 callbacks suppressed
[ 116.687160] wlp4s0: authenticate with dc:bf:e9:fd:39:ea
[ 116.688442] wlp4s0: send auth to dc:bf:e9:fd:39:ea (try 1/3)
[ 116.828391] wlp4s0: authenticated
[ 116.830666] wlp4s0: associate with dc:bf:e9:fd:39:ea (try 1/3)
[ 116.834424] wlp4s0: RX AssocResp from dc:bf:e9:fd:39:ea (capab=0x1411 status=0 aid=2)
[ 116.836970] wlp4s0: associated
[ 116.857175] Bluetooth: RFCOMM TTY layer initialized
[ 116.857181] Bluetooth: RFCOMM socket layer initialized
[ 116.857185] Bluetooth: RFCOMM ver 1.11
[ 116.882014] IPv6: ADDRCONF(NETDEV_CHANGE): wlp4s0: link becomes ready
 


notwithstanding whatever that log may mean.......

Is there any chance overheating occurred ?
 
Condobloke said:
notwithstanding whatever that log may mean.......

Is there any chance overheating occurred ?
Click to expand...
Psensors shows 37 degrees.

I just built this desktop six months ago
 
I had the same situation in one of my desktops. As soon i open the box it was clogged up, plain dust and thick. I always used air cans to clean the vents but I never open it up. I decided open all apart clean them all, even remove old thermal paste and put a new one. Put everything back in order, turn it up and never turn off again.

If continues than it may be something else is going bad like cooling fan.....or else. But try what I did, usually the system turns off to prevent burning the CPU and other components.
 
linu89waltzodi said:
I had the same situation in one of my desktops. As soon i open the box it was clogged up, plain dust and thick. I always used air cans to clean the vents but I never open it up. I decided open all apart clean them all, even remove old thermal paste and put a new one. Put everything back in order, turn it up and never turn off again.

If continues than it may be something else is going bad like cooling fan.....or else. But try what I did, usually the system turns off to prevent burning the CPU and other components.
Click to expand...
Thanks for the details.

I don't see any dust.
Than again I just built this rig 5 or 6 months ago.
Both fans are running so that's good.
 
Psensor shows 39 degrees.

Psensor.png
 
do i see CPU 0 as in nothing revolutions per minute; cos it indicates CPU fan is not running ?can you check
 
captain-sensible said:
do i see CPU 0 as in nothing revolutions per minute; cos it indicates CPU fan is not running ?can you check
Click to expand...
Yeah, I just checked.
The CPU fan is running.
 
ok had another look this time with glasses on so the CPU fan is not being monitored since all values are zero
 
well there is mention of DRAM ECC disabled in your output , but i've read things can be worse if its enabled. I've had shutdowns with out warning on PC tower, due to loose wire hitting cpu fan. lose connection of wires to front power up pannel ,and an unstable situation due to a complicated bios and bad choice of settings overclock, and such like. I also had erratic unpredicable power off due to a bad / loose sata wire connection. Did i read your PC is a self build ?
 
captain-sensible said:
well there is mention of DRAM ECC disabled in your output , but i've read things can be worse if its enabled. I've had shutdowns with out warning on PC tower, due to loose wire hitting cpu fan. lose connection of wires to front power up pannel ,and an unstable situation due to a complicated bios and bad choice of settings overclock, and such like. I also had erratic unpredicable power off due to a bad / loose sata wire connection. Did i read your PC is a self build ?
Click to expand...
Yes, my best friend and I built my gaming rig together.
 
Have you placed an x in the box beside 'cpu usage' ? (in Psensor)
 
its going to be a process of elimination ; when i was i Africa i had surge control enabled so my Desktop on a single phase electricity supply that was up and down like a Yo yo went off every 20 minutes. if its a self build check all wires , dodgy wires, lose wires, PSU ..
 
All wires and everything are all ok and connected correctly.

So far since making this thread my desktop has not shut down again.
 
There haven't been any more not so graceful shut downs and Mint is running well.
Everything seems ok now.

Thanks for the help everyone.
 
You must log in or register to reply here.

Members online

Total: 352 (members: 2, guests: 350)

Latest posts

Top