Random(ish) freeze then reboot

twiggy · 2014-06-25 16:06:35

Hello there, thanks in advance and apologies for missing any obvious information.

I recently got myself a new machine, consisting of:

* ASRock FM2A88X Extreme4+ Motherboard
* AMD A4 5300 CPU
* Crucial Ballistix BLS8G3D169DS3CEU Sport XT 8GB 240 Pin DIMM DDR3 PC3-12800 Memory Module

and other probably not relevant parts

and recently,
* Sapphire 11202-13-20G AMD Radeon HD 7750 Graphics Card ( HDMI, 2GB DDR3, DVI-D, VGA, PCI Express 3.0, 128-Bit, AMD HD3D Technology)

After anywhere between 30 minutes and about 6 hours (usually around 6 hours) the whole system will freeze for about 5 seconds or so, the keyboard and mouse being completely unresponsive, then it will reboot.

I haven't seen anything obvious in X logs or anything suspicious found in /var/log, but I'm not 100% sure what I'm looking for. I've done a memtest with no problems, I even switched the RAM with somebody else's and it still happened. There is nothing to suggest overheating either.

I've tried changing from the open source drivers to the fglrx with no luck, as well as the addition of the new graphics card (which did cause a few errors when switching to it, but seems ok now), also with no luck.

I'm pretty sure this will only happen in Arch Linux, I tested with Puppy Linux for about 6 hours with no problems and I'm about to install Windows 7 as a temporary measure/test. Obviously I'd rather use Arch.

Any suggestions?

Many thanks,

Twig.

Edit: Thanks, I'll get onto the output of that when I get a moment to sort my bootloader out!

Last edited by twiggy (2014-06-27 14:57:07)

loqs · 2014-06-25 19:25:20

Journalctl

journalctl -b-1 -r

journal for the last boot with order reversed so the messages from the end of that boot where the error occurred should appear first change -1 to -2 etc to go through older boot logs

twiggy · 2014-06-28 19:36:36

No error messages of any interest, the last error it reported was two minutes before it crashed and was nothing to do with this (related to ttyS0 not existing, which isn't relevant). The only other error messages (in red text) were earlier on to do with Rhythmbox crashing.

The last message before the ttyS0 guff was:

Jun 28 20:21:33 WID-I systemd[1]: Failed to reset devices.list on /system.slice: Invalid argument
Jun 28 20:21:13 WID-I su[10130]: pam_unix(su:session): session opened for user root by twiggy(uid=1000)

but I doubt that's relevant either.

Any other ideas?

Thanks again for your help so far.

Last edited by twiggy (2014-06-28 20:29:33)

0strodamus · 2014-06-28 23:06:11

I just built a new AMD based system and was having intermittent freezing. My system wasn't rebooting like yours - just freezing. Nothing in my logs and I had also run memtest prior to installing Arch without any issues. I lowered my memory frequency from DDR3-2133 to DDR3-1866 and haven't had another freezing incident so far. You might want to give it a try too. I may try running at 2133 in the future with a voltage bump, but I want to make sure I'm stable at the lower frequency first.

twiggy · 2014-06-29 20:39:03

So far, (9 hours), it seems to be running alright, I set the RAM speed a bit lower (1066?).

I ran dmesg just for the hell of it and got this

[   25.579393] <6>[fglrx] Firegl kernel thread PID: 258
[   25.579458] <6>[fglrx] Firegl kernel thread PID: 259
[   25.579518] <6>[fglrx] Firegl kernel thread PID: 260
[   25.579612] <6>[fglrx] IRQ 54 Enabled
[   25.587954] <6>[fglrx] Reserved FB block: Shared offset:0, size:1000000 
[   25.587957] <6>[fglrx] Reserved FB block: Unshared offset:f838000, size:4000 
[   25.587958] <6>[fglrx] Reserved FB block: Unshared offset:f83c000, size:4c4000 
[   25.587960] <6>[fglrx] Reserved FB block: Unshared offset:7ffee000, size:12000

Does this mean anything? Cheers.

Edit: Spoke too soon, it crashed again!

Last edited by twiggy (2014-06-30 09:19:18)

0strodamus · 2014-07-01 04:16:37

Sorry to hear your system crashed again. If you got more uptime with the memory change, you might want to focus some attention there. Make sure your timings and voltage are all correct according to the mfg. You could also try bumping the voltage up a little bit (just be careful; the last thing you need is to damage your hardware). Or I could be leading you down a blind alley. It's so hard to know for sure. On my new system, I'm a few full days into running without any freezes with the memory frequency change. I also changed my BIOS DDR voltage setting from AUTO to 1.51v to make sure I'm getting a full 1.5v. At AUTO the voltage reading was ~1.49.

I'm sorry that I don't have much else to offer and I don't know if the messages you posted mean anything. Good luck - I can imagine this is frustrating for you to say the least.

GSF1200S · 2014-07-01 04:37:18

Do you have a new power supply? Freezes as such are often the hallmark of a failing power supply.

Have you run memtest on the ram?

mgmartins · 2014-07-01 07:40:20

Ummm, try downgrading kernel to 3.14

twiggy · 2014-07-01 08:26:57

Yes, it is a new power supply. I need to test more thoroughly, but this hasn't happened on Windows 7 yet.

I have ran memtest with no problems

I could try downgrading, I'll give it a bash.

Cheers

Last edited by twiggy (2014-07-01 13:45:10)

jackwild · 2014-07-01 14:10:07

Sounds like the symptoms I was having, see https://bbs.archlinux.org/viewtopic.php?id=183494

You can test if it's the same issue by forcing a swap. Go to a virtual console (ctrl-alt f1-f6) and create a tmpfs the size of your ram and fill it with data o force swapping:

#mkdir /mnt/tmptest
#mount -t tmpfs -o size=8G tmpfs /mnt/tmptest
dd if=/dev/zero of=/mnt/tmptest/zero.txt bs=512M count=16

This should reveal if it is the same issue.

twiggy · 2014-07-01 15:16:54

jackwild wrote:

Sounds like the symptoms I was having, see https://bbs.archlinux.org/viewtopic.php?id=183494
You can test if it's the same issue by forcing a swap. Go to a virtual console (ctrl-alt f1-f6) and create a tmpfs the size of your ram and fill it with data o force swapping:
#mkdir /mnt/tmptest
#mount -t tmpfs -o size=8G tmpfs /mnt/tmptest
dd if=/dev/zero of=/mnt/tmptest/zero.txt bs=512M count=16
This should reveal if it is the same issue.

I did those commands and nothing of interest happened. What should happen?

Cheers.

jackwild · 2014-07-01 15:43:04

It seems like a different issue then as for me, it would provoke a freeze as soon as the memory was paged to swap. Just to be sure what is the output of

swapon -s

and after completing the commands:

free -m

Also, don't forget to free that memory again:

#umount /mnt/tmptest
#rm /mnt/tmptest -R

twiggy · 2014-07-01 17:03:45

Ah ok, here we go

[root@WID-I twiggy]# swapon -s
Filename				Type		Size	Used	Priority
/dev/sda3                              	partition	5118972	0	-1
[root@WID-I twiggy]#

[root@WID-I twiggy]# free -m
             total       used       free     shared    buffers     cached
Mem:          7844       2264       5579         36         33        398
-/+ buffers/cache:       1832       6011
Swap:         4998          0       4998

[root@WID-I twiggy]# mount -t tmpfs -o size=8G tmpfs /mnt/tmptest
[root@WID-I twiggy]# dd if=/dev/zero of=/mnt/tmptest/zero.txt bs=512M count=16
16+0 records in
16+0 records out
8589934592 bytes (8.6 GB) copied, 24.798 s, 346 MB/s

Running the dd does cause a bit of lag, but nothing major.

After the above command

[root@WID-I twiggy]# free -m
             total       used       free     shared    buffers     cached
Mem:          7844       7150        693       4947          2       5064
-/+ buffers/cache:       2084       5760
Swap:         4998       3276       1722

Last edited by twiggy (2014-07-01 17:05:42)

jackwild · 2014-07-01 18:04:02

It definitely isn't the same problem I had. Sorry to waste your time, but I can make a couple of suggestions. It seems like you have eliminated a hardware problem as best you can so maybe you can try installing the linux-lts package to see if it gives different results. It's basically an older version of the kernel with major bug fixes. You might also try a different desktop to see if it is KDE related, there are some good lightweight desktops available in the repos (it's a good idea to create a new user to do this so you don't pollute your own configuration). Beyond that, with no logs, it makes it difficult. I'd try alternatives for applications you use (firefox etc). Just try to narrow it down.

Last edited by jackwild (2014-07-01 18:05:16)

twiggy · 2014-07-01 18:06:57

No apologies necessary, thank you for helping me eliminate it as a possible answer.

I haven't got around to trying the older kernel solution yet (also mentioned by mgmartins), but I'll get on with that now.

Thanks to everyone so far!

Edit: X doesn't want to play ball with the lts-kernel. It launches to a very glitchy screen (beyond being usable in anyway). I'll see if I can sort it out.

Edit: X is now behaving with the old kernel, let's see whether it crashes again.

Last edited by twiggy (2014-07-01 19:32:52)

twiggy · 2014-07-02 08:33:59

The LTS kernel makes no difference, just a had a restart after a few hours. I guess I could try another distro and see if that makes any difference.

Could it be an application/desktop environment causing a complete freeze and reboot with nothing noticeable in the logs? There have been some instances where I've just left it on LXDE with nothing else all day and it has still reset. I may have done so already, but I could try not launching X and see if it still does it.

Just realised I put the DRAM speed back to auto before the kernel switch, now trying with the old kernel and with the RAM set to 1066 (Thanks to 0strodamus).

Last edited by twiggy (2014-07-02 09:07:02)

jackwild · 2014-07-02 11:06:50

Do you get anything interesting from

#journalctl -b -1 -p warning

twiggy · 2014-07-02 11:11:34

I'm aware of the loose USB connection causing the USB guff. I'm not sure whether the Firegl errors are anything to do with when I was switching between the open source and the closed source drivers though.

-- Logs begin at Wed 2014-06-11 01:46:54 BST, end at Wed 2014-07-02 11:11:59 BS
Jul 02 09:23:24 WID-I kernel: ACPI: RSDP 00000000000f04a0 00024 (v02 ALASKA)
Jul 02 09:23:24 WID-I kernel: ACPI: XSDT 00000000cbdf4078 00074 (v01 ALASKA    
Jul 02 09:23:24 WID-I kernel: ACPI: FACP 00000000cbdfa258 0010C (v05 ALASKA    
Jul 02 09:23:24 WID-I kernel: ACPI BIOS Bug: Warning: Optional FADT field Pm2Co
Jul 02 09:23:24 WID-I kernel: ACPI: DSDT 00000000cbdf4188 060D0 (v02 ALASKA    
Jul 02 09:23:24 WID-I kernel: ACPI: FACS 00000000cbe1e080 00040
Jul 02 09:23:24 WID-I kernel: ACPI: APIC 00000000cbdfa368 00072 (v03 ALASKA    
Jul 02 09:23:24 WID-I kernel: ACPI: FPDT 00000000cbdfa3e0 00044 (v01 ALASKA    
Jul 02 09:23:24 WID-I kernel: ACPI: MCFG 00000000cbdfa428 0003C (v01 ALASKA    
Jul 02 09:23:24 WID-I kernel: ACPI: HPET 00000000cbdfa468 00038 (v01 ALASKA    
Jul 02 09:23:24 WID-I kernel: ACPI: AAFT 00000000cbdfa4a0 002D4 (v01 ALASKA OEM
Jul 02 09:23:24 WID-I kernel: ACPI: SSDT 00000000cbdfa778 006B2 (v01    AMD BAN
Jul 02 09:23:24 WID-I kernel: ACPI: SSDT 00000000cbdfae30 004B7 (v02    AMD BAN
Jul 02 09:23:24 WID-I kernel: ACPI: CRAT 00000000cbdfb2e8 002E8 (v01    AMD BAN
Jul 02 09:23:24 WID-I kernel: ACPI: SSDT 00000000cbdfb5d0 01115 (v01    AMD   C
Jul 02 09:23:24 WID-I kernel: Zone ranges:
Jul 02 09:23:24 WID-I kernel:   DMA      [mem 0x00001000-0x00ffffff]
Jul 02 09:23:24 WID-I kernel:   DMA32    [mem 0x01000000-0xffffffff]
lines 1-19...skipping...
-- Logs begin at Wed 2014-06-11 01:46:54 BST, end at Wed 2014-07-02 11:11:59 BST. --
Jul 02 09:23:24 WID-I kernel: ACPI: RSDP 00000000000f04a0 00024 (v02 ALASKA)
Jul 02 09:23:24 WID-I kernel: ACPI: XSDT 00000000cbdf4078 00074 (v01 ALASKA    A M I 01072009 AMI  00010013)
Jul 02 09:23:24 WID-I kernel: ACPI: FACP 00000000cbdfa258 0010C (v05 ALASKA    A M I 01072009 AMI  00010013)
Jul 02 09:23:24 WID-I kernel: ACPI BIOS Bug: Warning: Optional FADT field Pm2ControlBlock has zero address or length: 0x0000000000000000/0x1 (20130328/tbfadt-603)
Jul 02 09:23:24 WID-I kernel: ACPI: DSDT 00000000cbdf4188 060D0 (v02 ALASKA    A M I 00000000 INTL 20051117)
Jul 02 09:23:24 WID-I kernel: ACPI: FACS 00000000cbe1e080 00040
Jul 02 09:23:24 WID-I kernel: ACPI: APIC 00000000cbdfa368 00072 (v03 ALASKA    A M I 01072009 AMI  00010013)
Jul 02 09:23:24 WID-I kernel: ACPI: FPDT 00000000cbdfa3e0 00044 (v01 ALASKA    A M I 01072009 AMI  00010013)
Jul 02 09:23:24 WID-I kernel: ACPI: MCFG 00000000cbdfa428 0003C (v01 ALASKA    A M I 01072009 MSFT 00010013)
Jul 02 09:23:24 WID-I kernel: ACPI: HPET 00000000cbdfa468 00038 (v01 ALASKA    A M I 01072009 AMI  00000005)
Jul 02 09:23:24 WID-I kernel: ACPI: AAFT 00000000cbdfa4a0 002D4 (v01 ALASKA OEMAAFT  01072009 MSFT 00000097)
Jul 02 09:23:24 WID-I kernel: ACPI: SSDT 00000000cbdfa778 006B2 (v01    AMD BANTRY   00000001 AMD  00000001)
Jul 02 09:23:24 WID-I kernel: ACPI: SSDT 00000000cbdfae30 004B7 (v02    AMD BANTRY   00000001 MSFT 04000000)
Jul 02 09:23:24 WID-I kernel: ACPI: CRAT 00000000cbdfb2e8 002E8 (v01    AMD BANTRY   00000001 AMD  00000001)
Jul 02 09:23:24 WID-I kernel: ACPI: SSDT 00000000cbdfb5d0 01115 (v01    AMD   CPMCMN 00000001 INTL 20051117)
Jul 02 09:23:24 WID-I kernel: Zone ranges:
Jul 02 09:23:24 WID-I kernel:   DMA      [mem 0x00001000-0x00ffffff]
Jul 02 09:23:24 WID-I kernel:   DMA32    [mem 0x01000000-0xffffffff]
Jul 02 09:23:24 WID-I kernel:   Normal   [mem 0x100000000-0x22effffff]
Jul 02 09:23:24 WID-I kernel: Movable zone start for each node
Jul 02 09:23:24 WID-I kernel: Early memory node ranges
Jul 02 09:23:24 WID-I kernel:   node   0: [mem 0x00001000-0x0009dfff]
Jul 02 09:23:24 WID-I kernel:   node   0: [mem 0x00100000-0xcba66fff]
Jul 02 09:23:24 WID-I kernel:   node   0: [mem 0xcba97000-0xcbd71fff]
Jul 02 09:23:24 WID-I kernel:   node   0: [mem 0xce137000-0xce137fff]
Jul 02 09:23:24 WID-I kernel:   node   0: [mem 0xce33e000-0xce493fff]
Jul 02 09:23:24 WID-I kernel:   node   0: [mem 0xcf031000-0xcf071fff]
Jul 02 09:23:24 WID-I kernel:   node   0: [mem 0xcf7f1000-0xcf7fffff]
Jul 02 09:23:24 WID-I kernel:   node   0: [mem 0x100000000-0x22effffff]
Jul 02 09:23:24 WID-I kernel: Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 2043829
Jul 02 09:23:24 WID-I kernel: Policy zone: Normal
Jul 02 09:23:24 WID-I kernel: ACPI: All ACPI Tables successfully acquired
Jul 02 09:23:24 WID-I kernel: AMD PMU driver.
Jul 02 09:23:24 WID-I kernel: ACPI: Executed 1 blocks of module-level executable AML code
Jul 02 09:23:24 WID-I kernel: ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20130328/hwxface-568)
Jul 02 09:23:24 WID-I kernel: ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20130328/hwxface-568)
Jul 02 09:23:24 WID-I kernel: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Jul 02 09:23:24 WID-I kernel: 0000:02:07.0: Redundant entry in serial pci_table.
                              Please send the output of lspci -vv, this
                              message (0x4348,0x3253,0x4348,0x3253), the
                              manufacturer and name of serial board or
                              modem board to rmk+serial@arm.linux.org.uk.
Jul 02 09:23:24 WID-I kernel: i8042: PNP: PS/2 appears to have AUX port disabled, if this is incorrect please boot with i8042.nopnp
Jul 02 09:23:24 WID-I kernel: usb 6-4: Device not responding to set address.
Jul 02 09:23:24 WID-I kernel: usb 6-4: Device not responding to set address.
Jul 02 09:23:24 WID-I kernel: usb 6-4: device not accepting address 3, error -71
Jul 02 09:23:24 WID-I kernel: usb 6-4: Device not responding to set address.
Jul 02 09:23:24 WID-I kernel: usb 6-4: Device not responding to set address.
Jul 02 09:23:24 WID-I kernel: usb 6-4: device not accepting address 4, error -71
Jul 02 09:23:24 WID-I kernel: usb 6-4: Device not responding to set address.
Jul 02 09:23:24 WID-I kernel: usb 6-4: Device not responding to set address.
Jul 02 09:23:24 WID-I kernel: usb 6-4: device not accepting address 5, error -71
Jul 02 09:23:24 WID-I kernel: usb 6-4: Device not responding to set address.
Jul 02 09:23:24 WID-I kernel: usb 6-4: Device not responding to set address.
Jul 02 09:23:24 WID-I kernel: usb 6-4: device not accepting address 6, error -71
Jul 02 09:23:24 WID-I kernel: hub 6-0:1.0: unable to enumerate USB device on port 4
Jul 02 09:23:24 WID-I kernel: usb 1-1.1: ep 0x81 - rounding interval to 64 microframes, ep desc says 80 microframes
Jul 02 09:23:24 WID-I systemd[1]: Cannot add dependency job for unit display-manager.service, ignoring: Unit display-manager.service failed to load: No such file or directory.
Jul 02 09:23:26 WID-I kernel: fglrx: module license 'Proprietary. (C) 2002 - ATI Technologies, Starnberg, GERMANY' taints kernel.
Jul 02 09:23:26 WID-I kernel: Disabling lock debugging due to kernel taint
Jul 02 09:23:26 WID-I kernel: <6>[fglrx] Maximum main memory to use for locked dma buffers: 7614 MBytes.
Jul 02 09:23:26 WID-I kernel: <6>[fglrx]   vendor: 1002 device: 683f count: 1
Jul 02 09:23:26 WID-I kernel: <6>[fglrx] ioport: bar 4, base 0xe000, size: 0x100
Jul 02 09:23:26 WID-I kernel: <6>[fglrx] Kernel PAT support is enabled
Jul 02 09:23:26 WID-I kernel: <6>[fglrx] module loaded - fglrx 14.20.7 [May 22 2014] with 1 minors
Jul 02 09:24:54 WID-I systemd[1]: Job sys-subsystem-net-devices-enp4s0.device/start timed out.
Jul 02 09:24:54 WID-I systemd[1]: Timed out waiting for device sys-subsystem-net-devices-enp4s0.device.
Jul 02 09:24:54 WID-I systemd[1]: Dependency failed for Network connectivity (enp4s0).
Jul 02 09:24:54 WID-I systemd[1]: Job dev-ttys0.device/start timed out.
Jul 02 09:24:54 WID-I systemd[1]: Timed out waiting for device dev-ttys0.device.
Jul 02 09:24:54 WID-I systemd[1]: Dependency failed for Serial Getty on ttys0.
Jul 02 09:31:00 WID-I kernel: <6>[fglrx] Firegl kernel thread PID: 247
Jul 02 09:31:00 WID-I kernel: <6>[fglrx] Firegl kernel thread PID: 248
Jul 02 09:31:00 WID-I kernel: <6>[fglrx] Firegl kernel thread PID: 249
Jul 02 09:31:00 WID-I kernel: <6>[fglrx] IRQ 54 Enabled
Jul 02 09:31:00 WID-I kernel: <6>[fglrx] Reserved FB block: Shared offset:0, size:1000000 
Jul 02 09:31:00 WID-I kernel: <6>[fglrx] Reserved FB block: Unshared offset:f838000, size:4000 
Jul 02 09:31:00 WID-I kernel: <6>[fglrx] Reserved FB block: Unshared offset:f83c000, size:4c4000 
Jul 02 09:31:00 WID-I kernel: <6>[fglrx] Reserved FB block: Unshared offset:7ffee000, size:12000 
Jul 02 09:31:09 WID-I pulseaudio[287]: GetManagedObjects() failed: org.freedesktop.DBus.Error.ServiceUnknown: The name org.bluez was not provided by any .service files
Jul 02 09:31:27 WID-I org.gtk.vfs.Daemon[265]: ** (process:388): WARNING **: Failed to setup SSH evironment: The name org.gnome.keyring was not provided by any .service files (g-dbus-error-quark, 2)
Jul 02 09:31:41 WID-I org.gtk.vfs.Daemon[265]: ** (process:388): WARNING **: Global default SecretService instance out of sync with the watch for its DBus name
Jul 02 09:43:15 WID-I org.a11y.Bus[265]: Activating service name='org.a11y.atspi.Registry'
Jul 02 09:43:15 WID-I org.a11y.Bus[265]: Successfully activated service 'org.a11y.atspi.Registry'
Jul 02 09:43:15 WID-I org.a11y.atspi.Registry[1084]: ** (at-spi2-registryd:1087): WARNING **: Failed to register client: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.Session
Jul 02 09:43:15 WID-I org.a11y.atspi.Registry[1084]: ** (at-spi2-registryd:1087): WARNING **: Unable to register client with session manager
Jul 02 09:56:27 WID-I pulseaudio[287]: Unable to read or parse data from client.
Jul 02 09:56:27 WID-I org.a11y.Bus[265]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.

Edit: Voltage up and frequency down, over 10 hours of uptime, so far so good!
Edit: Another session only lasted 4 hours, I've upped the voltage on the RAM again.

Last edited by twiggy (2014-07-03 09:31:10)

weirddan455 · 2014-07-02 11:47:25

I recently solved similar instability by lowering my RAM clock. I was getting the same kind of crash you describe (hard crash which made the system hard reset most of the time) It was happening in both Windows and Linux but only when I was playing a game or doing something CPU intensive.

I found running Prime95 helped me test my stability. My system was more stable than yours... crashing only once every day or two but Prime95 still crashed it within a couple minutes until I lowered my RAM frequency and then it ran nonstop just fine. That also marked the end of my system crashes. I ran the Blend test with the number of threads equal to my number of CPU cores. If you have hyperthreading you may want to set it to the number of virtual core (usually twice the number of cores.) There's no AUR package but the Linux download from the link below contains a binary you simply extract and then run from the command line. Since it's CLI, you can also use this to diagnose if the problem lies with X or not.

http://www.mersenne.org/download/

Last edited by weirddan455 (2014-07-02 11:57:22)

GSF1200S · 2014-07-03 23:15:57

If tweaking your RAM voltage doesnt fix your problem, I would very heavily consider exchanging the power supply (I hope its modular!). It isnt clear by your last choice whether the problem is fixed..

twiggy · 2014-07-04 09:41:20

RAM voltage/frequency tweaking didn't solve the problem, neither did using another Linux distribution. I have just been in contact with Corsair for a replacement. Thanks to everyone for your help.

Edit: A crash still hasn't happened on Windows, I've been using it exclusively for the last two days. I will keep you posted.

Last edited by twiggy (2014-07-05 20:59:00)

twiggy · 2014-07-18 13:27:43

Right. I ordered a new power supply (HEC Compucase G7 Modular Power Extreme 750W Power Supply) as the cost of returning my current one would cost the same price as buying a new one. Anyhow, this new power supply has caused the system to be even more unstable. The symptoms although are different, instead of a "freeze", the whole thing will just power off after about 10 minutes of use.

Any thoughts would be hugely appreciated, cheers.

Edit: Windows managed to crash with the new power supply, but has still yet to with the old. Strange behaviour...

Edit: Aha! Windows has crashed in the same way as Arch Linux originally did. While running a YouTube video of all things. For some reason Arch Linux crashes more regularly, but Windows took weeks. Interesting nonetheless.

Last edited by twiggy (2014-07-19 10:38:43)

GSF1200S · 2014-07-19 18:29:33

Swap the motherboard out? I would say RAM is the most probable cause of freezing, but for it to change with a different power supply, I dont really know- I would think motherboard.

Thats a strange and really crappy problem.

Arch Linux

#1 2014-06-25 16:06:35

Random(ish) freeze then reboot

#2 2014-06-25 19:25:20

Re: Random(ish) freeze then reboot

#3 2014-06-28 19:36:36

Re: Random(ish) freeze then reboot

#4 2014-06-28 23:06:11

Re: Random(ish) freeze then reboot

#5 2014-06-29 20:39:03

Re: Random(ish) freeze then reboot

#6 2014-07-01 04:16:37

Re: Random(ish) freeze then reboot

#7 2014-07-01 04:37:18

Re: Random(ish) freeze then reboot

#8 2014-07-01 07:40:20

Re: Random(ish) freeze then reboot

#9 2014-07-01 08:26:57

Re: Random(ish) freeze then reboot

#10 2014-07-01 14:10:07

Re: Random(ish) freeze then reboot

#11 2014-07-01 15:16:54

Re: Random(ish) freeze then reboot

#12 2014-07-01 15:43:04

Re: Random(ish) freeze then reboot

#13 2014-07-01 17:03:45

Re: Random(ish) freeze then reboot

#14 2014-07-01 18:04:02

Re: Random(ish) freeze then reboot

#15 2014-07-01 18:06:57

Re: Random(ish) freeze then reboot

#16 2014-07-02 08:33:59

Re: Random(ish) freeze then reboot

#17 2014-07-02 11:06:50

Re: Random(ish) freeze then reboot

#18 2014-07-02 11:11:34

Re: Random(ish) freeze then reboot

#19 2014-07-02 11:47:25

Re: Random(ish) freeze then reboot

#20 2014-07-03 23:15:57

Re: Random(ish) freeze then reboot

#21 2014-07-04 09:41:20

Re: Random(ish) freeze then reboot

#22 2014-07-18 13:27:43

Re: Random(ish) freeze then reboot

#23 2014-07-19 18:29:33

Re: Random(ish) freeze then reboot

Board footer