Random Reboots - Cannot reproduce issue on command

[freelancer91]

I've been dealing with a bit of an issue with my rig for the past few weeks. The computer will randomly reboot with absolutely no warning and seemingly no trace left on the computer (no dumps, etc).

At first I thought it was a bad power supply. I happen to have redundant power supplies so I tried both of them by themselves. It seems unlikely that both PSU's would have exactly the same problem.

It's possible that folding proteins on my CPU and GPU are stressing something out and causing it to happen, but it's too random for me to tell for sure.

Basic system specs:

Windows 8.1 Pro x64
Motherboard: Asus Rampage IV Extreme
CPU: Intel i7-3970x at standard clock speed (3.5GHz, 4.0Ghz turbo, cooled with XSPC Watercooling block)
GPU: EVGA GTX 690 with XSPC Watercooling block installed (standard clock)
Memory: 32GB Corsair Dominator Platinum (4*8GB)
PSU: 1000W EVGA Supernova 1000G2 (I have two of these, originally, I split the load between them)
Storage: Samsung 840 EVO 1 Terabyte SSD
Samsung HD103UJ 7200rpm 1 Terabyte HDD
And a hodgepodge of watercooling parts and a crapload of fans (like 21 of them in total)

And, of course, I have attached the diagnostic file

EDIT: Minidump added, Storage solution added to specs

 

[MasterChief]

Hey,

Force a bsod on purpose from the keyboard, and then re-run the log collection tool and post the results.

We will have a much more accurate look at the system that way.

In addition, please post a screenshot of CPU-Z 1st tab, one of memory tab, then one screenshot each for each stick of RAM of the SPD tab.

Monitor temps with GPU-Z and Speedfan to ensure they stay within specification range, especially while folding. Nice setup though. Thumbs up.

A guess of the top of my head is that we need to install some good ASUS stuff from proper hidden places lol. We will see about it all.

I can already see for sure that you need to install latest Asmedia USB 3.0 driver and Intel INF Update.

Also, Intel storage driver from Intel.com or ASUS.com needs to be installed:

Name    Standard SATA AHCI Controller
Manufacturer    Standard SATA AHCI Controller
Status    OK
PNP Device ID    PCI\VEN_1B21&DEV_0612&SUBSYS_84B71043&REV_01\4&100173A9&0&00E7
I/O Port    0x0000D050-0x0000D057
I/O Port    0x0000D040-0x0000D043
I/O Port    0x0000D030-0x0000D037
I/O Port    0x0000D020-0x0000D023
I/O Port    0x0000D000-0x0000D01F
Memory Address    0xFB200000-0xFB2001FF
IRQ Channel    IRQ 19
Driver    c:\windows\system32\drivers\storahci.sys (6.3.9600.16384, 105.34 KB (107,872 bytes), 8/22/2013 6:40 AM)
    
Name    Standard SATA AHCI Controller
Manufacturer    Standard SATA AHCI Controller
Status    OK
PNP Device ID    PCI\VEN_1B21&DEV_0612&SUBSYS_84B71043&REV_01\4&1DFF6D82&0&00E5
I/O Port    0x0000E050-0x0000E057
I/O Port    0x0000E040-0x0000E043
I/O Port    0x0000E030-0x0000E037
I/O Port    0x0000E020-0x0000E023
I/O Port    0x0000E000-0x0000EFFF
Memory Address    0xFB300000-0xFB3FFFFF
IRQ Channel    IRQ 17
Driver    c:\windows\system32\drivers\storahci.sys (6.3.9600.16384, 105.34 KB (107,872 bytes), 8/22/2013 6:40 AM)
    
Name    Standard SATA AHCI Controller
Manufacturer    Standard SATA AHCI Controller
Status    OK
PNP Device ID    PCI\VEN_8086&DEV_1D02&SUBSYS_84EF1043&REV_06\3&11583659&0&FA
I/O Port    0x0000F090-0x0000F097
I/O Port    0x0000F080-0x0000F083
I/O Port    0x0000F070-0x0000F077
I/O Port    0x0000F060-0x0000F063
I/O Port    0x0000F020-0x0000F03F
Memory Address    0xFB825000-0xFB8257FF
IRQ Channel    IRQ 20
Driver    c:\windows\system32\drivers\storahci.sys (6.3.9600.16384, 105.34 KB (107,872 bytes), 8/22/2013 6:40 AM)

 

[freelancer91]

Hee hee, you have to respect an operating system that will give you detailed instructions on how to make it explode.

I have added the minidump file from the manually initiated crash. Also, I realized I forgot to add the storage specs, so I did.

As for the fixes provided, I'll let you know how those go once I've gotten some sleep. It's 6:49am here and I just got off work.

 

[MasterChief]

Haha, yes about explosion.

As I assumed, an ASUS driver needs to be updated:

AsUpIO   AsUpIO.sys   Mon Aug 02 22:47:59 2010 (4C57835F)

To update the driver, go to your motherboard model's page. It will be in Downloads/Utilities section. You will probably have to look at Windows 7 for the newest update to it. (It will likely belong to whatever you see there that you have already installed. AI Suite or similar.)

All other drivers look ok - but should definitely deal with storage as per above, too.

 

[freelancer91]

It did it again. About 4 hours ago. I have attached another report. I wasn't at the computer when it happened.

 

[MasterChief]

Since I can't see any new crash dumps at all because they don't exist, nothing to say.

You should uninstall Cisco though.

Storage driver not installed.

 

[freelancer91]

I ran the Asus Update Utility that comes with the AISuite. Guess it missed that one. As for Cisco, I unfortunately need the Cisco VPN to access campus resources when off campus here at Illinois State University. I cannot do my computer science course work without it. I'll make another crash dump when I get off work at 6am.

 

[MasterChief]

It's most likely of everything to be causing issues.

 

[freelancer91]

I can't shake the horrible feeling that one of the very expensive components on this computer might be defective or damaged. Even if I did have warranties, replacing watercooled components is a massive chore.

 

[freelancer91]

I did some looking and AsUpIO.sys is at its latest version. It can be found by navigating to ASUSTeK Computer Inc. -Support- Drivers and Download Rampage IV Extreme, selecting Windows 8.1 64bit, going to Utilities, and downloading the latest AiSuite. When you extract the folder, navigate to AsusUpdate/AppSetup/AsUpIo and you will see that the driver signing date is exactly the same as the date you listed above.

 

[MasterChief]

How has the machine been behaving with Cisco removed, as test?

If there are any further crashes without it, run the tool again and attach as done before.

Also please include a screenshot of 1st tab of CPU-Z, a screenshot of Memory tab, and one screenshot each for each stick or RAM that you have. You can zip them and attach, or add to your post as pictures.

 

[freelancer91]

Sorry, I hadn't seen this post until now. I have been spending the past few days booted into Linux Mint while I do some programming for a class. Booted back into Windows today and just a few minutes ago, the computer rebooted while I was across the room. When it came to, it was apparently installing an update. However, it seems to be stuck in a reboot loop.

Interesting, while in Linux Mint, I never once had an issue with a random reboot. I find this encouraging, but it seems to indicate a software problem rather than a hardware problem. Hardware problems are expensive.

I guess I'm gonna reinstall Windows and go from there since it won't snap out of this boot loop.

 

[MasterChief]

Hopefully you didn't install Cisco to recreate the problem.

 

[freelancer91]

I don't want to get ahead of myself, but I have been running in Windows for a couple days now (after doing a fresh reinstall) and the issue hasn't come up again. I'm going to mark this as solved unless something comes up. No idea exactly what did it.

I haven't reinstalled Cisco, but I may need to at some point because it is required to log in to campus resources when I am not on a campus network connection (which is pretty much always, since this is a desktop in my apartment). There is a webVPN option, but it's a pain to use.

 

[freelancer91]

Ahh, think I spoke too soon. Had a random reboot while I was at work at about 12:52am last night CST. Then, just now, when I noticed my graphics drivers were updateable, I updated them and had a good old-fashioned BSOD (complaining about nvldmkm.sys).

BTW, if I wanted to learn how to read dmp files myself, where would you recommend I start? I know I need the debugging tools installed, but last time I tried this, I had trouble doing that. Now that I have gotten almost all of my computer science degree finished, I think its time I learn how to do this so that I don't have to come here every time I have an issue.

EDIT: Did some more searching, got the debugging symbols right, and looked at the problem. I think I probably just made the mistake of not turning off the Folding@Home program before updating the drivers. Oops.

This still doesn't explain the random reboot last night.

I haven't reinstalled the Cisco program so we can rule that out. This Windows install is fairly young (less than a week, I think). It was a completely fresh reinstall.

 

[MasterChief]

Don't run FAH and it will be alright.

Update:

AiChargerPlus AiChargerPlus.sys Wed Apr 18 21:17:35 2012 (4F8F67AF)
AsIO AsIO.sys Wed Aug 22 05:54:47 2012 (5034AC67)
AsUpIO AsUpIO.sys Mon Aug 02 22:47:59 2010 (4C57835F)
ASUSFILTER ASUSFILTER.sys Tue Sep 20 11:46:33 2011 (4E78B559)
nvlddmkm nvlddmkm.sys Wed Oct 23 02:21:50 2013 (52676AFE)
ICCWDT ICCWDT.sys Wed Aug 18 04:27:45 2010 (4C6B9981)

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  FahCore_17.exe

 

[freelancer91]

Whenever you post these drivers, how do you know they are out of date and that there are newer versions available? Some of these are pretty hard to track down.

Sorry for these slow responses. Between 40-hour-a-week night shifts, Computer Science midterms, research projects, the post-graduation job hunt, exhaustion from walking a work every day in the freezing weather, and my failing health, I've got quite a lot on my plate right now. I'm doing good if I get a thousand calories and 6 hours of sleep in a day.

 

[MasterChief]

I have a mental index of all drivers. They're easy to find. 2 of them are ATK and/or Probe II in Utilities sections at ASUS. Other is AI USB Charger.

 

[freelancer91]

I have a mental index of all drivers. They're easy to find. 2 of them are ATK and/or Probe II in Utilities sections at ASUS. Other is AI USB Charger.

I went to the Asus drivers website and downloaded the AI Suite and it said everything was up to date.