WHEA error on new build[solved]

[sam_816]

I build my system few hours ago. now i am getting WHEA error very frequently. It never appeared while system is idle or browsing files or internet. but almost everytime i have tried to install anything(even while i was updating database of kaspersky)
My build config:
Asus maximus VI gene(updated to latest Bios)
I7 4790k (not overclocked)+ hydro H90 cpucooler
corsair vengeance 2*4GB(1600hz)(x.m.p. activated to read correct mem speed)
evga gtx980(acx2.0 SC) not even detected by the system yet)
PSU: Silverstone strider GOLD evolution 750w
storage:
Toshiba SSD(Primary with win8.1 installed)
(has bad health according to ssdlife(free) (this is the culprit IMO and i am going to fresh install windows on my hdd)
But i wish to ask for opinions and suggestions regarding other setting/components i should check/tweak while the system is open again.

Only thing i have installed(in this order) so far:
kespersky internt security (WHEA errors - 2 times)
ssdlife free(no whea error)
intel driver update utility (WHEA error - 1)
tried installing nvidia 340.52 drivers (WHEA error -1)
on second try it ran properly but prompted no compatible GPU found :'(
the evga logo on GPU is glowing but its fans are not spinning.
I have connected my tv with HDMI through GPU only.
steps i have taken already :

First try System File Checker
Winkey plus 'X'
Choose Command Prompt (Admin)
Type sfc /scannow then Enter

No error/anomaly found after the scan :/
any help is welcome.
thanks in advance.

@Mods, if i m not at the right forum/sub-forum please guide me or move the thread. thanks.

 

[Ketchup]

It will be interesting to see how a good drive performs. Don't forget to rule out the cable too.

 

[sam_816]

It will be interesting to see how a good drive performs. Don't forget to rule out the cable too.

i am copying win 8.1 iso on the bootable flash drive as i write here.
what do you mean by cable? sata cable? do you really think that can cause WHEA errors like these?


what about hardware issues? i read somewhere that psu can cause these too.
i have silverstone strider 750w psu.(will update the opening post as well.)

 

[Ketchup]

Goota rule out the SSD first since it is showing definitive errors.Include the cable and the controller it is on (aka not the Admedia controller.) Once we rule those out, we can proceed if the problem persists. I don't like taking shots in the dark unless I have to.

 

[sam_816]

Goota rule out the SSD first since it is showing definitive errors.Include the cable and the controller it is on (aka not the Admedia controller.) Once we rule those out, we can proceed if the problem persists. I don't like taking shots in the dark unless I have to.

ok. i have PMed about my fresh install. pls find some time to look at it and if possible reply.
thanks in advance.
if you don't want me to PM you lemme know. i will post here.

 

[Ketchup]

YGPM. Good luck!

 

[sam_816]

UPdate: installed windows on one of my Hdds and removed the SSD.
it installed MEI(management Engine Drivers) without an issue but gave CLOCK_WATCHDOG_TIMEOUT error while installing realtek audio drivers.

 

[Rvenger]

WHEA error is normally the CPU vcore being too low.

 

[Ketchup]

UPdate: installed windows on one of my Hdds and removed the SSD.
it installed MEI(management Engine Drivers) without an issue but gave CLOCK_WATCHDOG_TIMEOUT error while installing realtek audio drivers.

That's not a good one. Are you running stock CPU speed? Are you running you memory at a conservative speed? I mentioned it before, but you are staying on the Intel SATA ports?

Although a great brand, I am almost wondering if you have a faulty PSU, if all of the above checks out.

 

[sam_816]

Didn't encounter WHEA durng my 1-1:30hour stint after switching to hdd so, I guess ssd was the issue.

Only had one clock watchdog error while installing realtek audio drivers.

Still cant find my gpuin the device manager :'(

 

[Ketchup]

Where did you get the audio drivers? Off the Asus CD?

Edit: so are you running on the Intel video now? What happens when you just plug on the Nvidia card and boot on that? If you try the other pci-express slot, does anything change?

 

[sam_816]

That's not a good one. Are you running stock CPU speed? Are you running you memory at a conservative speed? I mentioned it before, but you are staying on the Intel SATA ports?
i am running everything on stock(afaik) only advanced setting i changed was to enable X.M.P. (profile 1) which set memory clock to 1600hz and rest at automatic.
I don't understand the "you are staying on the intel sata port" part. i am using the sata cables that came with the motherboard and 1st,3rd and 4th port on the mobo(if that you are referring to) I have not installed any Sata drivers by myself though i have seen sata drivers on asus support page.

Although a great brand, I am almost wondering if you have a faulty PSU, if all of the above checks out.

even i am doubtful if my PSU is faulty. it is brand new. but my mobo is used may be that is the reason.

Where did you get the audio drivers? Off the Asus CD?
No. i downloaded all the drivers from support page of my mobo. it gave clock_watchdog error once after that PC ran smoothly..
Edit: so are you running on the Intel video now? What happens when you just plug on the Nvidia card and boot on that? If you try the other pci-express slot, does anything change?

haven't tried installing it on the 2nd pci slot will try that and update BTW 2nd port is x8. will that affect card's performance?
what do you mean by 'boot on that?' does that mean to get the output to tv from the card? i am already using HDMI port of the card to get the output and its working fine.
sorry for all the noobish questions and remarks. i am seeing the interiors of a PC for the 1st time after 1998.

 

[Ketchup]

OK, no worries about the Asmedia ports then. They are the bottom two. They are ok for storage drives, but not for boot drives.

 

[sam_816]

Update: almost everything sorted out.
for WHEA errors: turned out ssd was the culprit and caused problems during write process. so far not even a single WHEA error since i switched to hdd.
For 980 not detected: I downloaded and installed generic intel display drivers and then ran latest drivers from evga's support page. the drivers installed fine and card is showing in the device manager too.

 

[Ketchup]

Update: almost everything sorted out.
for WHEA errors: turned out ssd was the culprit and caused problems during write process. so far not even a single WHEA error since i switched to hdd.
For 980 not detected: I downloaded and installed generic intel display drivers and then ran latest drivers from evga's support page. the drivers installed fine and card is showing in the device manager too.

Great news. Hope things start settling down for you now.

 

[sam_816]

Yea. I hope so too. Now that I have properly working OS install on my 650gb hdd, i want to set up a raid0 with my 2 320gb hdd now and install a fresh win 8 OS.

Somehow both the drives are showing as non RAiD disks in Intel rapid storage application(I enter by pressing ctrl +I) when 650gb hdd is there. But when I remove the 650 one, pressing ctrl+I does nothing though both drives still appear as non RAID. I have no partitions on the drives. They don't appear in windows when I boot from 650 hdd. Should I try formatting them in a particular system format and create partitions?

 

[Ketchup]

Chapter 5 of the manual should cover this. I wonder if you are setting RAID mode in the BIOS before going into the Intel ROM Utility.

 

[sam_816]

I have set sata config(under advanced settings) as raid. But for individual sata ports only option I see is enable or disable hot switch.

I will go through the mobo manual again with focus on chapter 5.

I thought college days were over

 

[sam_816]

WHEA error is back!!
i have had 4 WHEA in the past hour or so. twice when i tried to download logitech G430 headset's software from logitech website. once when i tried to download DS4windows installer. everytime installer would start downloading and then lue screen would appear with Whea error.
the last one occurred when i tried to open .DMP file in minidump folder. i right clicked on latest dump file and clicked on open with -> wordpad and it showed blue screen again.
the last WHEA was different because after reboot there was a 'scanning and repairing drive (c) process. and it got stuck at 69% for a long time.(still stuck as i am writing)
any suggestions any one?

 

[Ketchup]

How old are the drives you are using? You need to run sfc.exe fom a command prompt. It will probably tell you to reboot.

But your file system is being corrupted on what I understand to be a second drive now. If you haven't swapped a cable /port from when this started, I would recommend you do so. If you have, you may want to run memtest for a couple hours. It that doesn't show anything. I might be inclined to suspect the hard drive controller (which is in the Z87 chipset if you are sure you are using the correct ports) on that board.

 

[sam_816]

All my hdds are old. Pulled from my old (2yr & a 4.5 yr old) laptops and ps3s. :/

I will run the said tests and buy a small ssd+ hdd tomorrow morning. I have spend over 1200 bux on all the hardware & it was soo stupid of me to buy a used ssd and relying on old hdds.

Last night I played bound by flame for about 20-30 mnutes. It gave whea error 1st time I launched but after reboot everything worked fine. I installed 'whocrashed'(by resplendence software) it showed Hal hal(something) error 0x124 .

I will post screenshot in some time.

 

[Ketchup]

All my hdds are old. Pulled from my old (2yr & a 4.5 yr old) laptops and ps3s. :/

I will run the said tests and buy a small ssd+ hdd tomorrow morning. I have spend over 1200 bux on all the hardware & it was soo stupid of me to buy a used ssd and relying on old hdds.

Last night I played bound by flame for about 20-30 mnutes. It gave whea error 1st time I launched but after reboot everything worked fine. I installed 'whocrashed'(by resplendence software) it showed Hal hal(something) error 0x124 .

I will post screenshot in some time.

Hmm, hopefully you nailed it. I just find it odd that you have more than one drive giving the same error. But we will find out with the new drive.

 

[sam_816]

I am thinking the same thing. How can two different storage devices(from different sources) can have same errors :/

Shall I try to reinsert the RAM dimms?

I just firmly pressed all connection to n from the psu.

 

[sam_816]

Update:I ran stress test on cpu, memory and video module individually and then all together for 1min and 5minutes(together) and no crashes. Is this utility any good? Or should I try some other similar program /utility?

 

[Ketchup]

I was thinking about memtest86 for the RAM:
http://www.memtest86.com/

Another thing to try would be to try one stick of RAM at a time.

One thing you might want to try is to get your dumps on a sharing sight, so that others can look at them. You should also be able to just copy the dump files to another computer (assuming you have one) and looking at them from there.