Random Crashes - Usually during long run times [SOLVED]
Forum rules
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
Re: Random Crashes - Usually during long run times
Did you buy a 6 gig or 3 gig 1060?
Re: Random Crashes - Usually during long run times
6GB. 4GB on my 980 wasn't enough.
Managed to install XFCE, but an app is complaining that the system tray is missing..I didn't click "Default" on the panel popup, now left with something very empty.
Managed to install XFCE, but an app is complaining that the system tray is missing..I didn't click "Default" on the panel popup, now left with something very empty.
Nvidia GTX 1060
Re: Random Crashes - Usually during long run times
Did you install XFCE alongside Cinnamon? Or did you do a fresh install of mint XFCE?
Re: Random Crashes - Usually during long run times
Along side.
Would it be safe to uninstall the Cinnamon?
Would it be safe to uninstall the Cinnamon?
Nvidia GTX 1060
Re: Random Crashes - Usually during long run times
The best and most stable method to move from Cinnamon to XFCE, is to DL mint XFCE and do a fresh install. Dual DEs rarely ever works out.
Re: Random Crashes - Usually during long run times
A little late to the party here, but your second htop output shows opera using more than 1 core, and something gobbling your memory. (can't see what it is) I use cinnamon and find it quite solid, the only time I have issues with it is when editing/testing conky which is easily solved with an 'ALT-F2 - r' to reset.
I would suggest running 'System Monitor', a gui from Menu > System and click on the Memory column header to bring the culprit to the top.
I would suggest running 'System Monitor', a gui from Menu > System and click on the Memory column header to bring the culprit to the top.
Re: Random Crashes - Usually during long run times
I'll try a fresh install of cinnamon, without applying any updates, and have the Nvidia driver installed. See how stable it is.
Edit:
KSysGuard is much more realistic than the default system monitor, and htop in terms of displaying the memory use.
Edit:
KSysGuard is much more realistic than the default system monitor, and htop in terms of displaying the memory use.
Nvidia GTX 1060
Re: Random Crashes - Usually during long run times
Lots of opera's in there, have you tried using something else to see what happens? I've installed opera before and didn't like what it did to my system, it seems to be almost invasive.
Re: Random Crashes - Usually during long run times
Opera opens up new processes upon the creation of new tabs.. Some crashes I've had did happen when Opera wasn't running.
Nvidia GTX 1060
Re: Random Crashes - Usually during long run times
Reinstalled Cinnamon, updated only the tested (Code 1 and 2) updates and the recommended Nvidia driver (375).
Left my PC for a while, came back to a blank screen, and my PC that seems to have been shut down.
Sys log of the assumed time of shut down. I came back at 23:22.
Left my PC for a while, came back to a blank screen, and my PC that seems to have been shut down.
Sys log of the assumed time of shut down. I came back at 23:22.
Code: Select all
May 17 22:17:01 user-MS-7851 CRON[6084]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
May 17 22:17:46 user-MS-7851 wpa_supplicant[1309]: wlp4s0: Failed to initiate sched scan
May 17 22:18:39 user-MS-7851 systemd[1]: Starting Cleanup of Temporary Directories...
May 17 22:18:39 user-MS-7851 systemd-tmpfiles[6138]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring.
May 17 22:18:39 user-MS-7851 systemd[1]: Started Cleanup of Temporary Directories.
May 17 22:18:49 user-MS-7851 wpa_supplicant[1309]: wlp4s0: Failed to initiate sched scan
May 17 22:50:13 user-MS-7851 kernel: [ 2807.566605] usb 3-5.1: reset full-speed USB device number 5 using xhci_hcd
May 17 22:50:13 user-MS-7851 kernel: [ 2807.655039] usb 3-5.1: device firmware changed
May 17 22:50:13 user-MS-7851 kernel: [ 2807.655839] usb 3-5.1: USB disconnect, device number 5
May 17 22:49:16 user-MS-7851 wpa_supplicant[1309]: message repeated 29 times: [ wlp4s0: Failed to initiate sched scan]
May 17 22:50:13 user-MS-7851 acpid: input device has been disconnected, fd 19
May 17 22:50:13 user-MS-7851 acpid: input device has been disconnected, fd 20
May 17 22:50:13 user-MS-7851 kernel: [ 2807.854461] usb 3-5.1: new full-speed USB device number 14 using xhci_hcd
May 17 22:50:13 user-MS-7851 kernel: [ 2807.943540] usb 3-5.1: unable to read config index 0 descriptor/all
May 17 22:50:13 user-MS-7851 kernel: [ 2807.943542] usb 3-5.1: can't read configurations, error -32
May 17 22:50:13 user-MS-7851 kernel: [ 2808.014467] usb 3-5.1: new full-speed USB device number 15 using xhci_hcd
May 17 22:50:13 user-MS-7851 kernel: [ 2808.103025] usb 3-5.1: unable to read config index 0 descriptor/start: -32
May 17 22:50:13 user-MS-7851 kernel: [ 2808.103028] usb 3-5.1: chopping to 0 config(s)
May 17 22:50:13 user-MS-7851 kernel: [ 2808.103491] usb 3-5.1: string descriptor 0 read error: -32
May 17 22:50:13 user-MS-7851 kernel: [ 2808.103494] usb 3-5.1: New USB device found, idVendor=2516, idProduct=0002
May 17 22:50:13 user-MS-7851 kernel: [ 2808.103495] usb 3-5.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
May 17 22:50:13 user-MS-7851 kernel: [ 2808.103569] usb 3-5.1: no configuration chosen from 0 choices
May 17 22:50:13 user-MS-7851 mtp-probe: checking bus 3, device 15: "/sys/devices/pci0000:00/0000:00:14.0/usb3/3-5/3-5.1"
May 17 22:50:13 user-MS-7851 mtp-probe: bus: 3, device: 15 was not an MTP device
May 17 22:50:19 user-MS-7851 wpa_supplicant[1309]: wlp4s0: Failed to initiate sched scan
May 17 22:54:38 user-MS-7851 kernel: [ 3073.272107] ata2: exception Emask 0x50 SAct 0x0 SErr 0x4090800 action 0xe frozen
May 17 22:54:38 user-MS-7851 kernel: [ 3073.272110] ata2: irq_stat 0x00400040, connection status changed
May 17 22:54:38 user-MS-7851 kernel: [ 3073.272111] ata2: SError: { HostInt PHYRdyChg 10B8B DevExch }
May 17 22:54:38 user-MS-7851 kernel: [ 3073.272113] ata2: hard resetting link
May 17 22:54:39 user-MS-7851 kernel: [ 3073.993868] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
May 17 22:54:39 user-MS-7851 kernel: [ 3074.015714] ata2.00: configured for UDMA/133
May 17 22:54:39 user-MS-7851 kernel: [ 3074.015716] ata2: EH complete
May 17 22:54:50 user-MS-7851 kernel: [ 3085.050916] ata2: exception Emask 0x50 SAct 0x0 SErr 0x4090800 action 0xe frozen
May 17 22:54:50 user-MS-7851 kernel: [ 3085.050918] ata2: irq_stat 0x00400040, connection status changed
May 17 22:54:50 user-MS-7851 kernel: [ 3085.050919] ata2: SError: { HostInt PHYRdyChg 10B8B DevExch }
May 17 22:54:50 user-MS-7851 kernel: [ 3085.050921] ata2: hard resetting link
May 17 22:54:51 user-MS-7851 kernel: [ 3085.774039] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
May 17 22:54:51 user-MS-7851 kernel: [ 3085.795767] ata2.00: configured for UDMA/133
May 17 22:54:51 user-MS-7851 kernel: [ 3085.795770] ata2: EH complete
May 17 22:55:17 user-MS-7851 kernel: [ 3111.989397] ata2: exception Emask 0x50 SAct 0x0 SErr 0x4090800 action 0xe frozen
May 17 22:55:17 user-MS-7851 kernel: [ 3111.989400] ata2: irq_stat 0x00400040, connection status changed
May 17 22:55:17 user-MS-7851 kernel: [ 3111.989401] ata2: SError: { HostInt PHYRdyChg 10B8B DevExch }
May 17 22:55:17 user-MS-7851 kernel: [ 3111.989403] ata2: hard resetting link
May 17 22:55:18 user-MS-7851 kernel: [ 3112.710434] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
May 17 22:55:18 user-MS-7851 kernel: [ 3112.732378] ata2.00: configured for UDMA/133
May 17 22:55:18 user-MS-7851 kernel: [ 3112.732380] ata2: EH complete
May 17 22:55:46 user-MS-7851 kernel: [ 3140.638720] ata2: limiting SATA link speed to 3.0 Gbps
May 17 22:55:46 user-MS-7851 kernel: [ 3140.638722] ata2: exception Emask 0x50 SAct 0x0 SErr 0x4090800 action 0xe frozen
May 17 22:55:46 user-MS-7851 kernel: [ 3140.638724] ata2: irq_stat 0x00400040, connection status changed
May 17 22:55:46 user-MS-7851 kernel: [ 3140.638725] ata2: SError: { HostInt PHYRdyChg 10B8B DevExch }
May 17 22:55:46 user-MS-7851 kernel: [ 3140.638727] ata2: hard resetting link
May 17 22:55:46 user-MS-7851 kernel: [ 3141.358858] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
May 17 22:55:46 user-MS-7851 kernel: [ 3141.380809] ata2.00: configured for UDMA/133
May 17 22:55:46 user-MS-7851 kernel: [ 3141.380811] ata2: EH complete
May 17 22:55:53 user-MS-7851 kernel: [ 3147.761640] ata2: exception Emask 0x50 SAct 0x0 SErr 0x4090800 action 0xe frozen
May 17 22:55:53 user-MS-7851 kernel: [ 3147.761643] ata2: irq_stat 0x00400040, connection status changed
May 17 22:55:53 user-MS-7851 kernel: [ 3147.761644] ata2: SError: { HostInt PHYRdyChg 10B8B DevExch }
May 17 22:55:53 user-MS-7851 kernel: [ 3147.761646] ata2: hard resetting link
May 17 22:55:53 user-MS-7851 kernel: [ 3148.482964] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
May 17 22:55:53 user-MS-7851 kernel: [ 3148.504919] ata2.00: configured for UDMA/133
May 17 22:55:53 user-MS-7851 kernel: [ 3148.504922] ata2: EH complete
May 17 22:55:58 user-MS-7851 kernel: [ 3153.224229] ata2: exception Emask 0x50 SAct 0x0 SErr 0x4090800 action 0xe frozen
May 17 22:55:58 user-MS-7851 kernel: [ 3153.224231] ata2: irq_stat 0x00400040, connection status changed
May 17 22:55:58 user-MS-7851 kernel: [ 3153.224233] ata2: SError: { HostInt PHYRdyChg 10B8B DevExch }
May 17 22:55:58 user-MS-7851 kernel: [ 3153.224235] ata2: hard resetting link
May 17 22:55:59 user-MS-7851 kernel: [ 3153.947043] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
May 17 22:55:59 user-MS-7851 kernel: [ 3153.969053] ata2.00: configured for UDMA/133
May 17 22:55:59 user-MS-7851 kernel: [ 3153.969055] ata2: EH complete
May 17 22:56:01 user-MS-7851 kernel: [ 3156.082694] ata2: exception Emask 0x50 SAct 0x0 SErr 0x4090800 action 0xe frozen
May 17 22:56:01 user-MS-7851 kernel: [ 3156.082697] ata2: irq_stat 0x00400040, connection status changed
May 17 22:56:01 user-MS-7851 kernel: [ 3156.082698] ata2: SError: { HostInt PHYRdyChg 10B8B DevExch }
May 17 22:56:01 user-MS-7851 kernel: [ 3156.082700] ata2: hard resetting link
May 17 22:56:02 user-MS-7851 kernel: [ 3156.803089] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
May 17 22:56:02 user-MS-7851 kernel: [ 3156.824890] ata2.00: configured for UDMA/133
May 17 22:56:02 user-MS-7851 kernel: [ 3156.824892] ata2: EH complete
May 17 22:58:13 user-MS-7851 kernel: [ 3287.647752] ata2: limiting SATA link speed to 1.5 Gbps
May 17 22:58:13 user-MS-7851 kernel: [ 3287.647755] ata2: exception Emask 0x50 SAct 0x0 SErr 0x4090800 action 0xe frozen
May 17 22:58:13 user-MS-7851 kernel: [ 3287.647756] ata2: irq_stat 0x00400040, connection status changed
May 17 22:58:13 user-MS-7851 kernel: [ 3287.647757] ata2: SError: { HostInt PHYRdyChg 10B8B DevExch }
May 17 22:58:13 user-MS-7851 kernel: [ 3287.647759] ata2: hard resetting link
May 17 22:58:13 user-MS-7851 kernel: [ 3288.369080] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
May 17 22:58:13 user-MS-7851 kernel: [ 3288.390853] ata2.00: configured for UDMA/133
May 17 22:58:13 user-MS-7851 kernel: [ 3288.390855] ata2: EH complete
May 17 22:58:15 user-MS-7851 kernel: [ 3290.254870] ata2: exception Emask 0x50 SAct 0x0 SErr 0x4090800 action 0xe frozen
May 17 22:58:15 user-MS-7851 kernel: [ 3290.254873] ata2: irq_stat 0x00400040, connection status changed
May 17 22:58:15 user-MS-7851 kernel: [ 3290.254874] ata2: SError: { HostInt PHYRdyChg 10B8B DevExch }
May 17 22:58:15 user-MS-7851 kernel: [ 3290.254876] ata2: hard resetting link
May 17 22:58:16 user-MS-7851 kernel: [ 3291.289118] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
May 17 22:58:16 user-MS-7851 kernel: [ 3291.320907] ata2.00: configured for UDMA/133
May 17 22:58:16 user-MS-7851 kernel: [ 3291.320909] ata2: EH complete
May 17 22:58:19 user-MS-7851 kernel: [ 3294.379203] ata2: exception Emask 0x50 SAct 0x0 SErr 0x4090800 action 0xe frozen
May 17 22:58:19 user-MS-7851 kernel: [ 3294.379206] ata2: irq_stat 0x00400040, connection status changed
May 17 22:58:19 user-MS-7851 kernel: [ 3294.379207] ata2: SError: { HostInt PHYRdyChg 10B8B DevExch }
May 17 22:58:19 user-MS-7851 kernel: [ 3294.379209] ata2: hard resetting link
May 17 22:58:21 user-MS-7851 kernel: [ 3295.573188] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
May 17 22:58:21 user-MS-7851 kernel: [ 3295.595134] ata2.00: configured for UDMA/133
May 17 22:58:21 user-MS-7851 kernel: [ 3295.595137] ata2: EH complete
May 17 22:58:21 user-MS-7851 kernel: [ 3295.689086] ata2: exception Emask 0x50 SAct 0x0 SErr 0x4090800 action 0xe frozen
May 17 22:58:21 user-MS-7851 kernel: [ 3295.689089] ata2: irq_stat 0x00400040, connection status changed
May 17 22:58:21 user-MS-7851 kernel: [ 3295.689090] ata2: SError: { HostInt PHYRdyChg 10B8B DevExch }
May 17 22:58:21 user-MS-7851 kernel: [ 3295.689092] ata2: hard resetting link
May 17 22:58:21 user-MS-7851 kernel: [ 3296.465194] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
May 17 22:58:21 user-MS-7851 kernel: [ 3296.486877] ata2.00: configured for UDMA/133
May 17 22:58:21 user-MS-7851 kernel: [ 3296.486880] ata2: EH complete
May 17 22:58:22 user-MS-7851 kernel: [ 3296.623271] ata2.00: limiting speed to UDMA/100:PIO4
May 17 22:58:22 user-MS-7851 kernel: [ 3296.623273] ata2: exception Emask 0x50 SAct 0x0 SErr 0x4090800 action 0xe frozen
May 17 22:58:22 user-MS-7851 kernel: [ 3296.623274] ata2: irq_stat 0x00400040, connection status changed
May 17 22:58:22 user-MS-7851 kernel: [ 3296.623276] ata2: SError: { HostInt PHYRdyChg 10B8B DevExch }
May 17 22:58:22 user-MS-7851 kernel: [ 3296.623278] ata2: hard resetting link
May 17 22:58:22 user-MS-7851 kernel: [ 3297.345215] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
May 17 22:58:22 user-MS-7851 kernel: [ 3297.367226] ata2.00: configured for UDMA/100
May 17 22:58:22 user-MS-7851 kernel: [ 3297.367229] ata2: EH complete
May 17 22:58:25 user-MS-7851 kernel: [ 3299.950119] ata2: exception Emask 0x50 SAct 0x0 SErr 0x4090800 action 0xe frozen
May 17 22:58:25 user-MS-7851 kernel: [ 3299.950122] ata2: irq_stat 0x00400040, connection status changed
May 17 22:58:25 user-MS-7851 kernel: [ 3299.950123] ata2: SError: { HostInt PHYRdyChg 10B8B DevExch }
May 17 22:58:25 user-MS-7851 kernel: [ 3299.950126] ata2: hard resetting link
May 17 22:58:26 user-MS-7851 kernel: [ 3300.673267] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
May 17 22:58:26 user-MS-7851 kernel: [ 3300.695125] ata2.00: configured for UDMA/100
May 17 22:58:26 user-MS-7851 kernel: [ 3300.695127] ata2: EH complete
May 17 22:58:26 user-MS-7851 kernel: [ 3301.121453] ata2: exception Emask 0x50 SAct 0x0 SErr 0x4090800 action 0xe frozen
May 17 22:58:26 user-MS-7851 kernel: [ 3301.121455] ata2: irq_stat 0x00400040, connection status changed
May 17 22:58:26 user-MS-7851 kernel: [ 3301.121456] ata2: SError: { HostInt PHYRdyChg 10B8B DevExch }
May 17 22:58:26 user-MS-7851 kernel: [ 3301.121458] ata2: hard resetting link
May 17 22:58:27 user-MS-7851 kernel: [ 3301.845281] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
May 17 22:58:27 user-MS-7851 kernel: [ 3301.867236] ata2.00: configured for UDMA/100
May 17 22:58:27 user-MS-7851 kernel: [ 3301.867239] ata2: EH complete
May 17 22:58:27 user-MS-7851 kernel: [ 3302.000080] ata2: exception Emask 0x50 SAct 0x0 SErr 0x4090800 action 0xe frozen
May 17 22:58:27 user-MS-7851 kernel: [ 3302.000083] ata2: irq_stat 0x00400040, connection status changed
May 17 22:58:27 user-MS-7851 kernel: [ 3302.000084] ata2: SError: { HostInt PHYRdyChg 10B8B DevExch }
May 17 22:58:27 user-MS-7851 kernel: [ 3302.000086] ata2: hard resetting link
May 17 22:58:28 user-MS-7851 kernel: [ 3302.721298] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
May 17 22:58:28 user-MS-7851 kernel: [ 3302.742967] ata2.00: configured for UDMA/100
May 17 22:58:28 user-MS-7851 kernel: [ 3302.742970] ata2: EH complete
May 17 22:58:28 user-MS-7851 kernel: [ 3302.787510] ata2.00: limiting speed to UDMA/33:PIO4
May 17 22:58:28 user-MS-7851 kernel: [ 3302.787512] ata2: exception Emask 0x50 SAct 0x0 SErr 0x4090800 action 0xe frozen
May 17 22:58:28 user-MS-7851 kernel: [ 3302.787513] ata2: irq_stat 0x00400040, connection status changed
May 17 22:58:28 user-MS-7851 kernel: [ 3302.787514] ata2: SError: { HostInt PHYRdyChg 10B8B DevExch }
May 17 22:58:28 user-MS-7851 kernel: [ 3302.787516] ata2: hard resetting link
May 17 22:58:29 user-MS-7851 kernel: [ 3304.397329] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
May 17 22:58:29 user-MS-7851 kernel: [ 3304.419169] ata2.00: configured for UDMA/33
May 17 22:58:29 user-MS-7851 kernel: [ 3304.419171] ata2: EH complete
May 17 22:58:33 user-MS-7851 kernel: [ 3307.835117] ata2: exception Emask 0x50 SAct 0x0 SErr 0x4090800 action 0xe frozen
May 17 22:58:33 user-MS-7851 kernel: [ 3307.835119] ata2: irq_stat 0x00400040, connection status changed
May 17 22:58:33 user-MS-7851 kernel: [ 3307.835120] ata2: SError: { HostInt PHYRdyChg 10B8B DevExch }
May 17 22:58:33 user-MS-7851 kernel: [ 3307.835122] ata2: hard resetting link
May 17 22:58:34 user-MS-7851 kernel: [ 3308.613385] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
May 17 22:58:34 user-MS-7851 kernel: [ 3308.635169] ata2.00: configured for UDMA/33
May 17 22:58:34 user-MS-7851 kernel: [ 3308.635172] ata2: EH complete
May 17 22:58:40 user-MS-7851 kernel: [ 3315.291886] ata2: exception Emask 0x50 SAct 0x0 SErr 0x4090800 action 0xe frozen
May 17 22:58:40 user-MS-7851 kernel: [ 3315.291889] ata2: irq_stat 0x00400040, connection status changed
May 17 22:58:40 user-MS-7851 kernel: [ 3315.291890] ata2: SError: { HostInt PHYRdyChg 10B8B DevExch }
May 17 22:58:40 user-MS-7851 kernel: [ 3315.291892] ata2: hard resetting link
May 17 22:58:41 user-MS-7851 kernel: [ 3316.069503] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
May 17 22:58:41 user-MS-7851 kernel: [ 3316.091367] ata2.00: configured for UDMA/33
May 17 22:58:41 user-MS-7851 kernel: [ 3316.091370] ata2: EH complete
May 17 22:58:42 user-MS-7851 kernel: [ 3316.883078] ata2: exception Emask 0x50 SAct 0x0 SErr 0x4090800 action 0xe frozen
May 17 22:58:42 user-MS-7851 kernel: [ 3316.883081] ata2: irq_stat 0x00400040, connection status changed
May 17 22:58:42 user-MS-7851 kernel: [ 3316.883082] ata2: SError: { HostInt PHYRdyChg 10B8B DevExch }
May 17 22:58:42 user-MS-7851 kernel: [ 3316.883084] ata2: hard resetting link
May 17 23:22:18 user-MS-7851 rsyslogd-2222: command 'KLogPermitNonKernelFacility' is currently not permitted - did you already set it via a RainerScript command (v6+ config)? [v8.16.0 try http://www.rsyslog.com/e/2222 ]
Nvidia GTX 1060
Re: Random Crashes - Usually during long run times
To my untrained eye, it looks like one of your sata devices isn't working or is intermittent, maybe a bad connection?
Re: Random Crashes - Usually during long run times
Woke up this morning, to my BIOS stating an overclock failure, which my pc wasn't overclocked. Reset bios, lead to a reboot loop. Turns out my DDR3 RAM socket 1 has failed.. Not the RAM itself, but the socket on the motherboard.
With the missing RAM module, I'll report back if I get another random shut down / crash.
I checked the Sata cable going to my SSD, looks all good. Plugged that into another port.
With the missing RAM module, I'll report back if I get another random shut down / crash.
I checked the Sata cable going to my SSD, looks all good. Plugged that into another port.
Nvidia GTX 1060
Re: Random Crashes - Usually during long run times
Quick update.
I've replaced my motherboard. My audio is now working as normal (Jacks were not been detected) as well as my RAM.
I' currently playing cities skyline and have F@H running on medium. Will do another update soon.
I've replaced my motherboard. My audio is now working as normal (Jacks were not been detected) as well as my RAM.
I' currently playing cities skyline and have F@H running on medium. Will do another update soon.
Nvidia GTX 1060
Re: Random Crashes - Usually during long run times
That just seem weird. If the actual Dimm slot 1 fails. I would think it would not even have booted, or given serious issue from the start. 1 and 3 are the primary channels for dual channel. Now if the actual ram stick was bad itself, it should have booted and not given errors until the 2 sticks filled to the point where the bad module on the RAM was present. I am not saying you are wrong. I am saying that is a behavior of a dimm failure I have not witnessed before.
To replicate your previous usage, dont forget a few Opera windows to suck up some resources.
To replicate your previous usage, dont forget a few Opera windows to suck up some resources.
Re: Random Crashes - Usually during long run times
System going well.
A couple of months ago, I did have an Antec fan self destruct in my PC for absolutely no reason.
Nvidia GTX 1060
Re: Random Crashes - Usually during long run times
Another update.
It seems Windows is very well coded to mask motherboard / PSU faults. Since changing my motherboard and PSU, my system has not crashed or rebooted, once. Bare in mind, my last system ran W10 perfectly for weeks at a time.
To note:
Using only the updates marked as "Safe and Tested" E.G. levels 1 and 2.
Nvida driver 375.39
It seems Windows is very well coded to mask motherboard / PSU faults. Since changing my motherboard and PSU, my system has not crashed or rebooted, once. Bare in mind, my last system ran W10 perfectly for weeks at a time.
To note:
Using only the updates marked as "Safe and Tested" E.G. levels 1 and 2.
Nvida driver 375.39
Nvidia GTX 1060
Re: Random Crashes - Usually during long run times
Nvidia GTX 1060