Skip to main content

windows 7 - Computer restarts randomly - all parts A/B tested

Brief Intro: Computer, one fine day, started randomly restarting. No pattern seen. Occurs anywhere between 1 to 8-9 times a day, usually 2-5. Can go 2-3 days between occurrences. Restart does not involve BSOD. Event logs offer no hints. Temps aren't high - has happened during idle load. Details below, and in my first Q.


This Q follows up Computer irregularly restarts - what should service centre look for?


As of now, the motherboard has just been replaced by Gigabyte. CPU has been replaced, RAM has been replaced, but the problem of random reboots continues.


Below is a crude graphical guide to the permutations in which restarts have occurred.



Key:


WP = Main or Wall Power source
IP = Intermediate Power Source a.k.a UPS
PSU = Computer Power Supply Unit - Corsair 550M
Cs = Computer case/cabinet
MB = Motherboard GA-H97-D3H
RAM -  RC = 2x Corsair 4GB DDR3 1333
      RK1 = 1x Kingston 8GB DDR3 1600
      RK2 = 2x Kingston 8GB DDR3 1866
CPU = i5-4440
HDDs = WD 1TB Win 7 + Seagate 2TB OpenSuSE Linux Tumbleweed
OS = within Win7 / Linux / UEFI

No add-on graphics ever (at my end), only iGPU.


These are the scenarios in which the system has been tested. FAIL at the start means restart reproduced; PASS means no restarts seen.


If there's a suffix - it indicates a changed component. Trailing ? indicates that component may not have been present.


In chronological order,


FAIL:  WP - IP - PSU - Cs - MB - RC - CPU - HDDs - Win
FAIL:  WP - IP - PSU - Cs - MB - RC - CPU - HDDs - Linux 
FAIL:  WP - IP - PSU - Cs - MB - RC - CPU - HDDs - BIOS

--- comp sent to dealer without HDDs --->

FAIL:  WP_dlr - IP_dlr? - PSU - Cs - MB - RC - CPU - HDDs_dlr - Win_dlr
PASS:  WP_dlr - IP_dlr? - PSU_dlr - Cs_dlr - MB - RC - CPU - HDDs_dlr - Win_dlr
(^ tested for less than a day)

--- comp returned to me with dealer PSU and Cs --->

FAIL:  WP - IP - PSU_dlr - Cs_dlr - MB - RC - CPU - HDDs - Win
FAIL:  WP - IP - PSU_dlr - Cs_dlr - MB - RK1 - CPU - HDDs - Win
(^ a week passed without restarts after switching to ram RK1)
FAIL:  WP - IP - PSU_dlr - Cs_dlr - MB - RK1 - CPU - HDDs - Linux

contd..


--- comp returned to dealer without HDDs --->
--- MB only forwarded to Gigabyte --->

PASS:  WP_gb - IP_gb? - PSU_gb - Cs_gb? - MB - R_gb - CPU_gb - HDDs_gb? - ?
(^ burn-in test for 2 days)
FAIL:  WP_gb - IP_gb? - PSU_gb - Cs_gb? - MB - RC - CPU - HDDs_gb? - ?
(^ sent my CPU + Corsair RAM)

--- Gigabyte return items to dealer; say one of the RC sticks to blame --->

PASS:  WP_dlr - IP_dlr? - PSU - Cs - MB - 1xRC + RK1 - CPU - HDDs_dlr - Win_dlr
(^ tested intermittently over 3-4 days)

--- comp returned to me with "faulty" RAM removed --->

FAIL:  WP - IP - PSU - Cs - MB - 1xRC + RK1 - CPU - HDDs - Win

--- MB+CPU+RAM(RC+RK1) resent to Gigabyte --->

(no testing done; CPU examined - observed some pins have blackened; say CPU to blame)

--- dealer replaces CPU with same model --->

PASS:  WP_dlr - IP_dlr? - PSU_dlr - Cs_dlr - MB - 1xRC + RK1 - CPU_new - HDDs_dlr - Win_dlr
(^ tested for 3 days)

contd..


--- comp returned to me with new CPU --->

FAIL:  WP - IP - PSU - Cs - MB - RC + RK1 - CPU_new - HDDs - Win
FAIL:  WP - IP - PSU - Cs - MB - RC + RK1 - CPU_new - HDDs - BIOS

--- MB+CPU_new+RAM(RC+RK1) sent to Gigabyte --->

PASS:  WP_gb - IP_gb? - PSU_gb - Cs_gb? - MB - RC+RK1 - CPU_new - HDDs_gb? - ?
(^ testing setup and duration unknown but reported after 3 days; say PSU to blame)

At this stage, I call Gigabyte and explain testing history to site manager,
who offers replacement MB.

--- comp returned to me with RMAed MB --->

FAIL:  WP - IP - PSU - Cs - MB_rma - RC + RK1 - CPU_new - HDDs - Win
PASS:  WP - IP - PSU - Cs - MB_rma - RC + RK1 - CPU_new - HDDs - Linux
(^ a few hours)
FAIL:  WP - IP - PSU - Cs - MB_rma - RC + RK1 - CPU_new - HDDs - BIOS

--- swap RAM with another (working) comp, yesterday --->

FAIL:  WP - IP - PSU - Cs - MB_rma - RK2 - CPU_new - HDDs - Win
(PASS:  WP_oth - PSU_oth - Cs_oth - MB_oth - RC + RK1 - CPU_oth - HDD_oth - Win)

Now thinking of what my next testing step is probably upgrading this to the theological department, but will check temporal suggestions a bit longer.


If you read the initial Q, you'll notice that the original MB was sent to Gigabyte in June. It was sent back repaired and with its BIOS upgraded to version F7. Version before was F3. The new version added support for 5th gen procs, they also prevent BIOS rollbacks. Could the new BIOS be responsible? The RMAed board has F7 as well. Against this possibility is the fact that the upgrade occurred in June and the restart behaviour started in mid-Oct.


The disappearing drive issue hasn't recurred since the first return to me from Gigabyte. No crashes during any Windows or Linux use.


I'll probably swap the PSU with the working comp, though an earlier config has been unsuccessfully tested with the dealer's PSU.


Thanks for reading. Thoughts?

Comments

Post a Comment

Popular Posts

How do I transmit a single hexadecimal value serial data in PuTTY using an Alt code?

I am trying to sent a specific hexadecimal value across a serial COM port using PuTTY. Specifically, I want to send the hex codes 9C, B6, FC, and 8B. I have looked up the Alt codes for these and they are 156, 182, 252, and 139 respectively. However, whenever I input the Alt codes, a preceding hex value of C2 is sent before 9C, B6, and 8B so the values that are sent are C2 9C, C2 B6, and C2 8B. The value for FC is changed to C3 FC. Why are these values being placed before the hex value and why is FC being changed altogether? To me, it seems like there is a problem internally converting the Alt code to hex. Is there a way to directly input hex values without using Alt codes in PuTTY? Answer What you're seeing is just ordinary text character set conversion. As far as PuTTY is concerned, you are typing (and reading) text , not raw binary data, therefore it has to convert the text to bytes in whatever configured character set before sending it over the wire. In other words, when y...
Post a Comment
Read more

linux - Extract/save a mail attachment using bash

Using normal bash tools (ie, built-ins or commonly-available command-line tools), is it possible, and how to extract/save attachments on emails? For example, say I have a nightly report which arrives via email but is a zip archive of several log files. I want to save all those zips into a backup directory. How would I accomplish that? Answer If you're aiming for portability, beware that there are several different versions of mail(1) and mailx(1) . There's a POSIX mailx command, but with very few requirements. And none of the implementations I have seem to parse attachments anyway. You might have the mpack package . Its munpack command saves all parts of a MIME message into separate files, then all you have to do is save the interesting parts and clean up the rest. There's also metamail . An equivalent of munpack is metamail -wy .
Post a Comment
Read more

ubuntu - Why does my USB hdd returns SG_IO: bad/missing sense data?

I am able to boot and run commands from external USB hdd; the message in question appears for about 45 seconds then booting continues. GRUB2 is installed on internal HDD. When choosing to boot directly to /dev/sdb the message doesn't appear, however boot time is about the same as booting to internal HDD. /dev/sdb: Timing cached reads: 1018 MB in 2.00 seconds = 508.97 MB/sec Timing buffered disk reads: 80 MB in 3.03 seconds = 26.37 MB/sec pfeiffep@de:~$ sudo hdparm -i /dev/sdb /dev/sdb: SG_IO: bad/missing sense data, sb[]: 70 00 05 00 00 00 00 10 00 00 00 00 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 HDIO_GET_IDENTITY failed: Invalid argument Gparted correctly identifies the drive as SAMSUNG MP0402H. Any ideas how to remedy the HDIO & SG_IO messages?
Post a Comment
Read more

Desktop reboots itself on sleep or hibernate

I have been using an ASUS M2NPV-VM motherboard for main home desktop workstation, operating Windows Vista x64. This computer has right from day one not been able to enter hibernate or standby; after Windows performs its final actions and brings the machine down, it would automatically revive itself for a reboot. Updating to the second latest BIOS (1201)has not helped (the latest BIOS revision would induce video refresh problems rendering it unusable). I have been reading related discussions on incidents similar to mine to no avail of a true workable solution. They appear to be more speculative guesses rather than actual knowledge on the inner workings of motherboard hardware. Does anybody have any electronic engineering experience on PC energy-saving standards to provide a more informed opinion how to go about getting this to work? More stories: this motherboard could not even reboot properly the first thing i used it. It was due to refresh rate of the onboard GPU, which had no influe...
Post a Comment
Read more