Sign in with
Sign up | Sign in
Your question

New build - PC ramdomly reboots, no BSOD, no minidump. Little help please?

Last response: in Systems
Share
May 14, 2013 5:37:18 AM

Hi all,

Apologies for another 'reboot' thread; have searched forum etc + was hoping something specific to my problem might sound familiar to someone.

As title suggests, I'm having a recurring rebooting issue with a new build I've built my gf. Everything works great, except I'm getting random reboots - however, there's never a BSOD and no minidump is ever created (c:\windows\minidump). For every reboot so far (bar one, when I was on firefox) the PC has been idle, just sitting on the desktop.

- The ram passes memtest86+ for ~8hrs no problem and likewise the Win7 boot memory test.
- running Prime95, temps get very hot (high 80s), too quickly on blend (think I need to redo TIM), but system seems stable.
- HDD has been scanned, no 'bad' areas.
- PSU voltages seem stable and within norm (used HWMonitor Pro - know software voltage readings aren't necessarily accurate, but assume it would show if they were unstable or way off?).
- No gfx card inserted.
- Motherboard has no blown capacitors etc.
- All connections on motherboard secure.
- All drivers up to date (station-drivers.com)

SETUP (new build):
- Gigabyte Z77X-UP5 TH (overkill given the rest of the PC I know, but got it stupidly cheap!)
- CMZ8GX3M2A1600C9
- i5 3570k - at 3.4ghz
- Enermax NAXN ENM850EWT
- Sapphire HD 7750 Ultimate - not yet connected
- LG CH10LS28 - Blu-ray drive
- AK-HC-05BKV2 - 5.25 memory card reader
- Corsair 550D Obsidian - case
- Western Digital Caviar Green 2TB WD20EZRX
- Samsung 840 Pro 128GB
- GC-WB300D - wireless PCIe card
- Win7 Home Premium - not yet activated

PC reboots sporadically, five times so far (has reset within an hour, left idle and unattended. Equally, has survived an entire night formatting a 2TB WD HDD). It's only ever rebooted from within Win7 - have left a mini build of XP running for nearly 24hrs (from Hiren's Boot CD 15.2) without issues. Equally, I assume said mini build might not use/ activate all the 'bits' of the PC - i.e. wireless card?

Could the wireless card (rev. 1.1, plugged into PCIe4 - included with motherboard) be causing issues? First reset happened whilst I was mucking around with our router MAC address.

I bought HWMonitor Pro to try and look over logs etc when it crashes. Annoyingly, the logs in HWMonitor Pro don't save when it crashes - if I instead record the logs onto another computer, the other computer tends to crash with a BEX64 error before the new PC reboots itself!

I guess what I'm interested to know is...

...does this def. look like a hardware issue, or is there a chance it's still software (despite the lack of BSOD/ minidump)? Anything stupid/ obvious I'm overlooking? Suppose the next step is to start swapping out components - any recommendations on how to test in this way as efficiently as possible?

Thanks in advance,
Rob
May 14, 2013 5:46:56 AM

Make sure the mb and Ssd drive firmware and the mb bios been updated.
In the mb bios make sure xmp profile is turned on. Use Cpuz read memory spd info make sure the mb set the speed up right. On the ram make sure it was 1.5v ram or less. Check to see if it on the mb qal list.
m
0
l
May 14, 2013 6:01:32 AM

smorizio said:
Make sure the mb and Ssd drive firmware and the mb bios been updated.
In the mb bios make sure xmp profile is turned on. Use Cpuz read memory spd info make sure the mb set the speed up right. On the ram make sure it was 1.5v ram or less. Check to see if it on the mb qal list.


Cheers smorizio,

Yep. Motherboard is on latest beta bios F13a (stable bios by all accounts). SSD is on latest firmware, and RAM is running XMP timings correctly (and on the memory support list).

This mb is a bit notorious for refusing to play nicely with certain PSUs...
www.youtube.com/watch?v=TJjdeNblhkA
www.xbitlabs.com/articles/mainboards/display/gigabyte-g...
...but my PSU is *supposed* to be ok (xbitlabs use it in their review above).
m
0
l
Related resources
May 14, 2013 6:18:29 AM

I'd say its mostly a hardware issue. My approach would be get down to extreme basics, disconnect the the wireless card, the 2TB hard drive, the blu-ray drive, the card reader and this may sound a bit ridiculous but also disconnect all of the case connections and fans, and use the motherboard power button to boot it.

if it doesn't crash on this setup, start reconnecting one thing at a time and test each time.

Let us know how it goes
m
0
l
May 14, 2013 6:36:39 AM

_Brute_Force_ said:
I'd say its mostly a hardware issue. My approach would be get down to extreme basics, disconnect the the wireless card, the 2TB hard drive, the blu-ray drive, the card reader and this may sound a bit ridiculous but also disconnect all of the case connections and fans, and use the motherboard power button to boot it.

if it doesn't crash on this setup, start reconnecting one thing at a time and test each time.

Let us know how it goes


Thanks, sounds logical - will get on it.

Appreciate I'm probably dreaming here, but it'd be awesome if there was some easier, more definitive way to diagnose hardware glitches like these in the future... who has the time for stuff like this?! :heink: 
m
0
l
May 14, 2013 11:41:55 AM

Check on her system what plugged into the USB ports. It could be there to many devices on the ports and there pulling more power when the pc wakes up then it can Handel.
m
0
l
May 14, 2013 3:28:31 PM

smorizio said:
Check on her system what plugged into the USB ports. It could be there to many devices on the ports and there pulling more power when the pc wakes up then it can Handel.


Afraid not smorizio. As it's a new/ unfinished build I'm trying to sort out this reboot issue, so nothing's plugged in to any of the USB slots - besides, this motherboard and PSU in question should be able to deal with almost anything I could throw at it...!

Thanks anyway though.
m
0
l
!