undiagnosed driver issues [solved]

Forum rules
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
linuxshark
Level 1
Level 1
Posts: 19
Joined: Sun Mar 17, 2024 11:48 am

Re: undiagnosed driver issues

Post by linuxshark »

SMG wrote: Sat Mar 23, 2024 8:54 pm
linuxshark wrote: Sat Mar 23, 2024 8:48 pmah sorry- i just posted what seemed relevant
c tags are for short snippets of code which are less than one line long. When you are posting multi-line output (such as something with 100 lines) please use code tags. Code tags retain the formatting from the terminal. c tags do not.
ah sorry! i edited it for you
User avatar
SMG
Level 25
Level 25
Posts: 32007
Joined: Sun Jul 26, 2020 6:15 pm
Location: USA

Re: undiagnosed driver issues

Post by SMG »

linuxshark wrote: Sat Mar 23, 2024 8:56 pmah sorry! i edited it for you
Thank you.

We're going to need to go back further. The following command prints the journal log information of the prior boot cycle and sends it to termbin.

Code: Select all

journalctl -b -1 | nc termbin.com 9999
It will return with a url address that you should post in your next reply.
Image
A woman typing on a laptop with LM20.3 Cinnamon.
linuxshark
Level 1
Level 1
Posts: 19
Joined: Sun Mar 17, 2024 11:48 am

Re: undiagnosed driver issues

Post by linuxshark »

SMG wrote: Sat Mar 23, 2024 9:03 pm
linuxshark wrote: Sat Mar 23, 2024 8:56 pmah sorry! i edited it for you
Thank you.

We're going to need to go back further. The following command prints the journal log information of the prior boot cycle and sends it to termbin.

Code: Select all

journalctl -b -1 | nc termbin.com 9999
It will return with a url address that you should post in your next reply.
https://termbin.com/e5yd

i hope this gives some answers
User avatar
SMG
Level 25
Level 25
Posts: 32007
Joined: Sun Jul 26, 2020 6:15 pm
Location: USA

Re: undiagnosed driver issues

Post by SMG »

linuxshark wrote: Sat Mar 23, 2024 9:05 pmi hope this gives some answers
The Nvidia driver loads just fine... (the last message in this set is common and is not a problem)

Code: Select all

Mar 20 09:25:17 oceanicshark-GA-78LMT-S2 kernel: nvidia: loading out-of-tree module taints kernel.
Mar 20 09:25:17 oceanicshark-GA-78LMT-S2 kernel: nvidia: module license 'NVIDIA' taints kernel.
Mar 20 09:25:17 oceanicshark-GA-78LMT-S2 kernel: Disabling lock debugging due to kernel taint
Mar 20 09:25:17 oceanicshark-GA-78LMT-S2 kernel: nvidia: module verification failed: signature and/or required key missing - tainting kernel
Mar 20 09:25:17 oceanicshark-GA-78LMT-S2 kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 236
Mar 20 09:25:17 oceanicshark-GA-78LMT-S2 kernel: 
Mar 20 09:25:17 oceanicshark-GA-78LMT-S2 kernel: nvidia 0000:01:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=none:owns=io+mem
Mar 20 09:25:17 oceanicshark-GA-78LMT-S2 kernel: NVRM: loading NVIDIA UNIX x86_64 Kernel Module  535.161.07  Sat Feb 17 22:55:48 UTC 2024
Mar 20 09:25:17 oceanicshark-GA-78LMT-S2 kernel: nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX platforms  535.161.07  Sat Feb 17 23:07:24 UTC 2024
Mar 20 09:25:17 oceanicshark-GA-78LMT-S2 kernel: [drm] [nvidia-drm] [GPU ID 0x00000100] Loading driver
Mar 20 09:25:17 oceanicshark-GA-78LMT-S2 kernel: [drm] Initialized nvidia-drm 0.0.0 20160202 for 0000:01:00.0 on minor 0

Mar 20 09:25:21 oceanicshark-GA-78LMT-S2 kernel: nvidia_uvm: module uses symbols from proprietary module nvidia, inheriting taint.
Mar 20 09:25:21 oceanicshark-GA-78LMT-S2 kernel: nvidia-uvm: Loaded the UVM driver, major device number 234

Mar 23 08:30:02 oceanicshark-GA-78LMT-S2 nvidia-persistenced[761]: Verbose syslog connection opened
Mar 23 08:30:02 oceanicshark-GA-78LMT-S2 nvidia-persistenced[761]: Now running with user ID 127 and group ID 137
Mar 23 08:30:02 oceanicshark-GA-78LMT-S2 nvidia-persistenced[761]: Started (761)

Mar 23 08:30:02 oceanicshark-GA-78LMT-S2 systemd[1]: Starting NVIDIA Persistence Daemon...

Mar 23 08:30:02 oceanicshark-GA-78LMT-S2 nvidia-persistenced[761]: Verbose syslog connection opened
Mar 23 08:30:02 oceanicshark-GA-78LMT-S2 nvidia-persistenced[761]: Now running with user ID 127 and group ID 137
Mar 23 08:30:02 oceanicshark-GA-78LMT-S2 nvidia-persistenced[761]: Started (761)

Mar 23 08:30:03 oceanicshark-GA-78LMT-S2 nvidia-persistenced[761]: device 0000:01:00.0 - registered
Mar 23 08:30:03 oceanicshark-GA-78LMT-S2 nvidia-persistenced[761]: Local RPC services initialized
Mar 23 08:30:03 oceanicshark-GA-78LMT-S2 systemd[1]: Started NVIDIA Persistence Daemon.

Mar 23 08:30:27 oceanicshark-GA-78LMT-S2 kernel: [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to grab modeset ownership
but then not long after the GPU falls off the bus...

Code: Select all

Mar 23 08:31:47 oceanicshark-GA-78LMT-S2 kernel: NVRM: GPU at PCI:0000:01:00: GPU-94826f69-b8d5-f328-aa50-a516d0f5c5d6
Mar 23 08:31:47 oceanicshark-GA-78LMT-S2 kernel: NVRM: Xid (PCI:0000:01:00): 79, pid='<unknown>', name=<unknown>, GPU has fallen off the bus.
Mar 23 08:31:47 oceanicshark-GA-78LMT-S2 kernel: NVRM: GPU 0000:01:00.0: GPU has fallen off the bus.

Mar 23 08:32:05 oceanicshark-GA-78LMT-S2 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000947d:0:0:0x0000000f
Mar 23 08:32:05 oceanicshark-GA-78LMT-S2 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000927c:0:0:0x0000000f
Mar 23 08:32:05 oceanicshark-GA-78LMT-S2 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000917e:0:0:0x0000000f
Mar 23 08:32:05 oceanicshark-GA-78LMT-S2 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000927c:1:0:0x0000000f
Mar 23 08:32:05 oceanicshark-GA-78LMT-S2 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000917e:1:0:0x0000000f
Mar 23 08:32:05 oceanicshark-GA-78LMT-S2 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000927c:2:0:0x0000000f
Mar 23 08:32:05 oceanicshark-GA-78LMT-S2 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000917e:2:0:0x0000000f
Mar 23 08:32:05 oceanicshark-GA-78LMT-S2 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000927c:3:0:0x0000000f
Mar 23 08:32:05 oceanicshark-GA-78LMT-S2 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000917e:3:0:0x0000000f

Mar 23 08:32:39 oceanicshark-GA-78LMT-S2 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000927c:3:0:0x0000000f
Mar 23 08:32:39 oceanicshark-GA-78LMT-S2 kernel: nvidia-modeset: ERROR: GPU:0: Failed detecting connected display devices
Mar 23 08:32:39 oceanicshark-GA-78LMT-S2 kernel: nvidia-modeset: ERROR: GPU:0: Failed detecting connected display devices
Mar 23 08:32:39 oceanicshark-GA-78LMT-S2 kernel: nvidia-modeset: ERROR: GPU:0: Failed detecting connected display devices
Mar 23 08:32:39 oceanicshark-GA-78LMT-S2 kernel: nvidia-modeset: ERROR: GPU:0: Failure reading maximum pixel clock value for display device DVI-I-1.
Mar 23 08:32:39 oceanicshark-GA-78LMT-S2 kernel: nvidia-modeset: ERROR: GPU:0: Failed detecting connected display devices
Mar 23 08:32:39 oceanicshark-GA-78LMT-S2 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000947d:0:0:0x0000000f
You have the system adjusting the clock in the middle which is why the times do not line up.

Code: Select all

Mar 20 09:25:29 oceanicshark-GA-78LMT-S2 systemd-timesyncd[695]: System clock time unset or jumped backwards, restoring from recorded timestamp: Sat 2024-03-23 08:30:01 PDT
Mar 23 08:30:01 oceanicshark-GA-78LMT-S2 systemd-timesyncd[695]: The system is configured to read the RTC time in the local time zone. This mode cannot be fully supported. All system time to RTC updates are disabled.

Mar 23 08:30:01 oceanicshark-GA-78LMT-S2 systemd[1]: System is tainted: local-hwclock
At this point, I have no idea why rebooting would help. If the driver is the problem then it should be the problem regardless, but that does not seem to be the case based on what you have described.

I am headed to bed now, but will see if I can come up with any ideas tomorrow.
Image
A woman typing on a laptop with LM20.3 Cinnamon.
linuxshark
Level 1
Level 1
Posts: 19
Joined: Sun Mar 17, 2024 11:48 am

Re: undiagnosed driver issues

Post by linuxshark »

SMG wrote: Sat Mar 23, 2024 10:18 pmAt this point, I have no idea why rebooting would help. If the driver is the problem then it should be the problem regardless, but that does not seem to be the case based on what you have described.

I am headed to bed now, but will see if I can come up with any ideas tomorrow.
rest well! thank you for working on helping me with this. i cannot fathom what the problem is here. if its directing to a hardware issue i may just have to bite the bullet and gut my computer and replace some things or just get a whole new build.
Last edited by SMG on Sun Mar 24, 2024 11:12 am, edited 1 time in total.
Reason: Shortened quote to relevant information so response is easier to notice.
User avatar
SMG
Level 25
Level 25
Posts: 32007
Joined: Sun Jul 26, 2020 6:15 pm
Location: USA

Re: undiagnosed driver issues

Post by SMG »

linuxshark wrote: Sat Mar 23, 2024 10:31 pmi cannot fathom what the problem is here. if its directing to a hardware issue i may just have to bite the bullet and gut my computer and replace some things or just get a whole new build.
If you can reboot and it works infinitely until shut down, then you wouldn't need to get new hardware.

That is the puzzling part that all you have to do is either do a hard boot or a reboot very soon after the initial issue and it is fine. That is also making it hard to find a similar situation.

I did find this which indicates a slightly loose power cable might be an issue. (I have seen riser/power cables be issues in the past although not necessarily with this message.) It's also possible just reseating the GPU might help.

The really odd thing to me is the "unknowns".

Code: Select all

kernel: NVRM: Xid (PCI:0000:01:00): 79, pid='<unknown>', name=<unknown>, GPU has fallen off the bus.
I suppose after you reboot we can also check the output of

Code: Select all

journalctl -b | grep -i "drm\|nvidia\|NVRM\|01:00.0"
for comparison to the boot cycle with the problems. Maybe that will give us a better clue.

Do you have any other drivers besides the Nvidia-470 showing in Driver Manager?
Image
A woman typing on a laptop with LM20.3 Cinnamon.
linuxshark
Level 1
Level 1
Posts: 19
Joined: Sun Mar 17, 2024 11:48 am

Re: undiagnosed driver issues

Post by linuxshark »

SMG wrote: Sun Mar 24, 2024 4:28 pm

Code: Select all

Mar 21 08:19:22 oceanicshark-GA-78LMT-S2 kernel: pci 0000:01:00.0: [10de:1380] type 00 class 0x030000
Mar 21 08:19:22 oceanicshark-GA-78LMT-S2 kernel: pci 0000:01:00.0: reg 0x10: [mem 0xfb000000-0xfbffffff]
Mar 21 08:19:22 oceanicshark-GA-78LMT-S2 kernel: pci 0000:01:00.0: reg 0x14: [mem 0xc0000000-0xcfffffff 64bit pref]
Mar 21 08:19:22 oceanicshark-GA-78LMT-S2 kernel: pci 0000:01:00.0: reg 0x1c: [mem 0xde000000-0xdfffffff 64bit pref]
Mar 21 08:19:22 oceanicshark-GA-78LMT-S2 kernel: pci 0000:01:00.0: reg 0x24: [io  0xef00-0xef7f]
Mar 21 08:19:22 oceanicshark-GA-78LMT-S2 kernel: pci 0000:01:00.0: reg 0x30: [mem 0x00000000-0x0007ffff pref]
Mar 21 08:19:22 oceanicshark-GA-78LMT-S2 kernel: pci 0000:01:00.0: BAR 3: assigned to efifb
Mar 21 08:19:22 oceanicshark-GA-78LMT-S2 kernel: pci 0000:01:00.0: Video device with shadowed ROM at [mem 0x000c0000-0x000dffff]
Mar 21 08:19:22 oceanicshark-GA-78LMT-S2 kernel: pci 0000:01:00.0: 32.000 Gb/s available PCIe bandwidth, limited by 2.5 GT/s PCIe x16 link at 0000:00:02.0 (capable of 126.016 Gb/s with 8.0 GT/s PCIe x16 link)
Mar 21 08:19:22 oceanicshark-GA-78LMT-S2 kernel: pci 0000:01:00.0: vgaarb: setting as boot VGA device
Mar 21 08:19:22 oceanicshark-GA-78LMT-S2 kernel: pci 0000:01:00.0: vgaarb: VGA device added: decodes=io+mem,owns=io+mem,locks=none
Mar 21 08:19:22 oceanicshark-GA-78LMT-S2 kernel: pci 0000:01:00.0: vgaarb: bridge control possible
Mar 21 08:19:22 oceanicshark-GA-78LMT-S2 kernel: pnp 00:06: disabling [mem 0x000cea00-0x000cffff] because it overlaps 0000:01:00.0 BAR 6 [mem 0x000c0000-0x000dffff]
Mar 21 08:19:22 oceanicshark-GA-78LMT-S2 kernel: pci 0000:01:00.1: D0 power state depends on 0000:01:00.0
Mar 21 08:19:22 oceanicshark-GA-78LMT-S2 kernel: nvidia: loading out-of-tree module taints kernel.
Mar 21 08:19:22 oceanicshark-GA-78LMT-S2 kernel: nvidia: module license 'NVIDIA' taints kernel.
Mar 21 08:19:22 oceanicshark-GA-78LMT-S2 kernel: nvidia: module verification failed: signature and/or required key missing - tainting kernel
Mar 21 08:19:22 oceanicshark-GA-78LMT-S2 kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 236
Mar 21 08:19:22 oceanicshark-GA-78LMT-S2 kernel: nvidia 0000:01:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=none:owns=io+mem
Mar 21 08:19:22 oceanicshark-GA-78LMT-S2 kernel: NVRM: loading NVIDIA UNIX x86_64 Kernel Module  535.161.07  Sat Feb 17 22:55:48 UTC 2024
Mar 21 08:19:22 oceanicshark-GA-78LMT-S2 kernel: nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX platforms  535.161.07  Sat Feb 17 23:07:24 UTC 2024
Mar 21 08:19:22 oceanicshark-GA-78LMT-S2 kernel: [drm] [nvidia-drm] [GPU ID 0x00000100] Loading driver
Mar 21 08:19:22 oceanicshark-GA-78LMT-S2 kernel: [drm] Initialized nvidia-drm 0.0.0 20160202 for 0000:01:00.0 on minor 0
Mar 21 08:19:22 oceanicshark-GA-78LMT-S2 systemd[1]: Starting Load Kernel Module drm...
Mar 21 08:19:22 oceanicshark-GA-78LMT-S2 systemd[1]: modprobe@drm.service: Deactivated successfully.
Mar 21 08:19:22 oceanicshark-GA-78LMT-S2 systemd[1]: Finished Load Kernel Module drm.
Mar 21 08:19:26 oceanicshark-GA-78LMT-S2 kernel: nvidia_uvm: module uses symbols from proprietary module nvidia, inheriting taint.
Mar 21 08:19:26 oceanicshark-GA-78LMT-S2 kernel: nvidia-uvm: Loaded the UVM driver, major device number 234.
Mar 21 08:19:28 oceanicshark-GA-78LMT-S2 kernel: input: HDA NVidia HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:02.0/0000:01:00.1/sound/card1/input11
Mar 21 08:19:28 oceanicshark-GA-78LMT-S2 kernel: input: HDA NVidia HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:02.0/0000:01:00.1/sound/card1/input12
Mar 21 08:19:28 oceanicshark-GA-78LMT-S2 kernel: input: HDA NVidia HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:02.0/0000:01:00.1/sound/card1/input13
Mar 21 08:19:28 oceanicshark-GA-78LMT-S2 kernel: input: HDA NVidia HDMI/DP,pcm=9 as /devices/pci0000:00/0000:00:02.0/0000:01:00.1/sound/card1/input14
Mar 21 08:19:28 oceanicshark-GA-78LMT-S2 kernel: input: HDA NVidia HDMI/DP,pcm=10 as /devices/pci0000:00/0000:00:02.0/0000:01:00.1/sound/card1/input15
Mar 21 08:19:28 oceanicshark-GA-78LMT-S2 kernel: input: HDA NVidia HDMI/DP,pcm=11 as /devices/pci0000:00/0000:00:02.0/0000:01:00.1/sound/card1/input16
Mar 21 08:19:28 oceanicshark-GA-78LMT-S2 kernel: input: HDA NVidia HDMI/DP,pcm=12 as /devices/pci0000:00/0000:00:02.0/0000:01:00.1/sound/card1/input17
Mar 21 08:19:35 oceanicshark-GA-78LMT-S2 audit[689]: AVC apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe" pid=689 comm="apparmor_parser"
Mar 21 08:19:35 oceanicshark-GA-78LMT-S2 audit[689]: AVC apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe//kmod" pid=689 comm="apparmor_parser"
Mar 21 08:19:35 oceanicshark-GA-78LMT-S2 kernel: audit: type=1400 audit(1711034375.666:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe" pid=689 comm="apparmor_parser"
Mar 21 08:19:35 oceanicshark-GA-78LMT-S2 kernel: audit: type=1400 audit(1711034375.666:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe//kmod" pid=689 comm="apparmor_parser"
Mar 23 20:41:50 oceanicshark-GA-78LMT-S2 systemd[1]: Starting NVIDIA Persistence Daemon...
Mar 23 20:41:51 oceanicshark-GA-78LMT-S2 nvidia-persistenced[793]: Verbose syslog connection opened
Mar 23 20:41:51 oceanicshark-GA-78LMT-S2 nvidia-persistenced[793]: Now running with user ID 127 and group ID 137
Mar 23 20:41:51 oceanicshark-GA-78LMT-S2 nvidia-persistenced[793]: Started (793)
Mar 23 20:41:52 oceanicshark-GA-78LMT-S2 nvidia-persistenced[793]: device 0000:01:00.0 - registered
Mar 23 20:41:52 oceanicshark-GA-78LMT-S2 nvidia-persistenced[793]: Local RPC services initialized
Mar 23 20:41:52 oceanicshark-GA-78LMT-S2 systemd[1]: Started NVIDIA Persistence Daemon.
Mar 23 20:42:15 oceanicshark-GA-78LMT-S2 kernel: [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to grab modeset ownership
here ya go! also i do not have any other drivers.

odd thing though, this morning i didn't get a single freeze? im still running on my first boot of the day no problem. the only difference was last night i had shut off my computer for the night but booted it back up to look something up and quickly shut it back down before it froze.
Last edited by SMG on Sun Mar 24, 2024 5:32 pm, edited 1 time in total.
Reason: Shortened quote which is a complete duplicate of the prior post. We can scroll up if we need to see it again; no need to duplicate it and make the response harder to see.
User avatar
SMG
Level 25
Level 25
Posts: 32007
Joined: Sun Jul 26, 2020 6:15 pm
Location: USA

Re: undiagnosed driver issues

Post by SMG »

linuxshark wrote: Sun Mar 24, 2024 4:54 pmhere ya go! also i do not have any other drivers.
Nothing of note there. It's the same messages just without the driver falling off the bus messages.
linuxshark wrote: Sun Mar 24, 2024 4:54 pmodd thing though, this morning i didn't get a single freeze? im still running on my first boot of the day no problem. the only difference was last night i had shut off my computer for the night but booted it back up to look something up and quickly shut it back down before it froze.
I have no new ideas.
Image
A woman typing on a laptop with LM20.3 Cinnamon.
linuxshark
Level 1
Level 1
Posts: 19
Joined: Sun Mar 17, 2024 11:48 am

Re: undiagnosed driver issues

Post by linuxshark »

SMG wrote: Sun Mar 24, 2024 5:34 pm
linuxshark wrote: Sun Mar 24, 2024 4:54 pmhere ya go! also i do not have any other drivers.
Nothing of note there. It's the same messages just without the driver falling off the bus messages.
linuxshark wrote: Sun Mar 24, 2024 4:54 pmodd thing though, this morning i didn't get a single freeze? im still running on my first boot of the day no problem. the only difference was last night i had shut off my computer for the night but booted it back up to look something up and quickly shut it back down before it froze.
I have no new ideas.
one thing i forgot to mention was that when im not home i turn the power strip to my computer off to save money on electric bills? could it be that?

or possibly, i just need to clean in my pc? its been a hot moment since ive done that lol
User avatar
SMG
Level 25
Level 25
Posts: 32007
Joined: Sun Jul 26, 2020 6:15 pm
Location: USA

Re: undiagnosed driver issues

Post by SMG »

When one cannot reliably reproduce a problem, it's difficult to come up with a solution.
Image
A woman typing on a laptop with LM20.3 Cinnamon.
linuxshark
Level 1
Level 1
Posts: 19
Joined: Sun Mar 17, 2024 11:48 am

Re: undiagnosed driver issues

Post by linuxshark »

SMG wrote: Sun Mar 24, 2024 5:40 pm When one cannot reliably reproduce a problem, it's difficult to come up with a solution.
understandable! thank you for trying to help me anyways :) i'll get some cleaning materials when i can and try that. and ill report back when i get results. i dont know when thatll be, however
linuxshark
Level 1
Level 1
Posts: 19
Joined: Sun Mar 17, 2024 11:48 am

Re: undiagnosed driver issues

Post by linuxshark »

so its been 2 weeks and i havent had a single freeze since. which is good! i still dont quite know what the issue is or what fixed it but ill put down what i have done

1: i increased the size of my swap file to help with memory

2: i did a cold boot and shut down before a freeze would occur

i didn't do any system updates between my last freeze and what i did above, i checked, only update i did was firefox
Post Reply

Return to “Graphics Cards & Monitors”