WHEA error on new build[solved]

[sam_816]

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.

Will try this too.

Continuing from my last post, after stress tests I went onto 'test item' tab and started doing other tests. These were divided into 2 parts. (assuming you are familiar with it) when I clicked 'finish' button after performing all tests, I got another bsod- critical process died :/

I am sad n annoyed now!

 

[Ketchup]

Will try this too.

Continuing from my last post, after stress tests I went onto 'test item' tab and started doing other tests. These were divided into 2 parts. (assuming you are familiar with it) when I clicked 'finish' button after performing all tests, I got another bsod- critical process died :/

I am sad n annoyed now!

Not familiar with the program. But if we can get to the minidump we can hopefully get closer to finding a cause.

 

[phasseshifter]

try this test set it to high....http://www.majorgeeks.com/files/details/intelburntest.html................................and this will give you results on your hardware......http://www.cpuid.com/softwares/cpu-z/versions-history.html.............there both programs you have to dowload and install them for them to run...

 

[sam_816]

Just finished running sfc /scannow in safe mode with command prompt. All well there.

I am unable to install windows'updates as well.

And I have installed driverreviver which has scanned 13 drivers being out of date.here is the list:

Intel management engine interface

Pci standard host cpu bridge

Pci standard pci-to-pci bridge

High precision event timer

Intel 82802 firmware hub device

Pci standard pci-to-pci bridge(came again)

Intel Ethernet connection 1217-V

Pci express root complex

Pci standard isa bridge

Standard sata achi controller

Pci standard pci-to-pci bridge(appeared again)

Motherboard resources

Realtek high definition audio.

I have installed all my drvers from asus's support page for my mobo.

Intel driver update utility is scanning no drivers at all. Wtf is happening.

I am sending minidump file link in pm

 

[sam_816]

try this test set it to high....http://www.majorgeeks.com/files/details/intelburntest.html................................and this will give you results on your hardware......http://www.cpuid.com/softwares/cpu-z/versions-history.html.............there both programs you have to dowload and install them for them to run...

I tried downloading required .net files for intelburntest.exe and widows gave error 0x800F0906.

Update: .net files installed fine after retry.

I already have cpu-z free version. But don't know how to use it. All I do is see the system components'details etc.

 

[phasseshifter]

windows up date can be quite a pain..some and in many cases you just have to leave it .. eventually it will ...leave it set to auto update and install...try getting it to go into its udate search more regualy..set it to look more often that is..there are also manual download pages but i have not got the url`s..Mr k may have them...i think a lot of your problems may be fixed after you can get windows update to run...have you ran viral check`s..

 

[phasseshifter]

open a command prompt as admin and type this ...chkdsk c: ....it hay say it wants to run it after a reboot..if you have done this then ignore..............also another factor is your hdd`s tey may well be at best sata 2 but given the size and age i suspect they may be sata one mode drives ..this is ok but your system is much advanced over your peripheral hdd`s ..this may be a contributing factor...given what you have been through..it would be wise to spend 100 dollars..get a 2tb drive sata 3 interface and start over..if your mobo only supports sata 2 get a sata card pcie 1 slot will be fine..this may get you out of the jungle ..then a fresh install..of windows..on it..if cost is in fact an issue sometimes you just have to spend the money..or go with a 500gb...it will cost less..a 2 port sata 3 card pcie 1 slot will set you back 20 odd dollars give or take 5 dollars.. you will need to make a driver disk for it when you setup windows from scratch....

 

[sam_816]

I tried intelburntest on high and it gave clock_watchdog_timout error after about 5 seconds



And the pc hung at 5% of data collection . Had to hardware restart :'(

 

[phasseshifter]

oh that is not good news um set it to its low setting try again..just do a 10 times test..it means that your cpu ..is not good or your ram or your mobo is not good i sus the cpu is it over clocked..did you buy it second hand... if you have two sticks try one at a time and also set in the bios for single channel....

 

[phasseshifter]

bsod`s are usually the result of hardware failure...along with the dumps...if you have a spare cpu that will run in that mobo try it even if it is a lower speed device...

 

[sam_816]

oh that is not good news um set it to its low setting try again..just do a 10 times test..it means that your cpu ..is not good or your ram is not good i sus the cpu is it over clocked..did you buy it second hand... if you have two sticks try one at a time and also set in the bios for single channel....

both the CPU and RAM are brand new. so is the CPU cooler.
my mobo on the other hand is second hand/used. nothing is overclocked.
i just got another WHEA error while downloading updates for windows. i am selecting one update at a time and installing it. it installed an 18 mb one and got WHEA on 800+mb one.
i just remember that there was a slight depression on the cpu block of my cpu cooler. not in the middle though. can it be that there is no proper contact between cpu and cooler block?? and this is causing the problem?
i have RAM Dimms in my 2nd and 4th slot. i will try taking them out and inserting one by one.

 

[sam_816]

bsod`s are usually the result of hardware failure...along with the dumps...if you have a spare cpu that will run in that mobo try it even if it is a lower speed device...

don't have any additional hardware. only stock cpu cooler.
shall i remove the cpu cooler and put on the stock cooler and test?
imo cpu cooler was an overkill for my system. i am running games at 720p only. i bought top of the line(as per my understanding) hardware just to ensure that they don't work under heavy load and without a need to overclocking

 

[Ketchup]

Well here is what the dumps look like. I suppose we can see what are dumps look like once a new drive is in place. It would probably be worth it to check your cpu temperatures under load.

crash dump file: C\WINDOWS\Minidump\122814-25500-01.dmp
This was probably caused by the following module: hal.dll (hal+0x35C9F)
Bugcheck code: 0x124 (0x0, 0xFFFFE00002B08028, 0xBF800000, 0x124)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C\WINDOWS\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

crash dump file: C\WINDOWS\Minidump\122814-24640-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DCA0)
Bugcheck code: 0xEF (0xFFFFE000035FC4C0, 0x0, 0x0, 0x0)
Error: CRITICAL_PROCESS_DIED
file path: C\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a critical system process died.
There is a possibility this problem was caused by a virus or other malware.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

crash dump file: C\WINDOWS\Minidump\122814-29906-01.dmp
This was probably caused by the following module: hal.dll (hal+0x35C9F)
Bugcheck code: 0x124 (0x0, 0xFFFFE00002B3C028, 0xBF800000, 0x124)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C\WINDOWS\system32\hal.dll
product: Microsoft Windows Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

crash dump file: C\WINDOWS\Minidump\122814-41281-01.dmp
This was probably caused by the following module: hal.dll (hal+0x35C9F)
Bugcheck code: 0x124 (0x0, 0xFFFFE00002E32028, 0xBF800000, 0x124)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C\WINDOWS\system32\hal.dll
product: Microsoft Windows Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

crash dump file: C\WINDOWS\Minidump\122814-31140-01.dmp
This was probably caused by the following module: hal.dll (hal+0x35CDF)
Bugcheck code: 0x124 (0x0, 0xFFFFE00002A36028, 0xBF800000, 0x124)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C\WINDOWS\system32\hal.dll
product: Microsoft Windows Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

crash dump file: C\WINDOWS\Minidump\122814-19234-01.dmp
This was probably caused by the following module: hal.dll (hal+0x35CDF)
Bugcheck code: 0x124 (0x0, 0xFFFFE00002B6E028, 0xBF800000, 0x124)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C\WINDOWS\system32\hal.dll
product: Microsoft Windows Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.


crash dump file: C\WINDOWS\Minidump\122814-25062-01.dmp
This was probably caused by the following module: hal.dll (hal+0x35CDF)
Bugcheck code: 0x124 (0x0, 0xFFFFE00002E2B028, 0xBF800000, 0x124)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C\WINDOWS\system32\hal.dll
product: Microsoft Windows Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

crash dump file: C\WINDOWS\Minidump\122814-25312-01.dmp
This was probably caused by the following module: hal.dll (hal+0x35CDF)
Bugcheck code: 0x124 (0x0, 0xFFFFE000054CE028, 0xBF800000, 0x124)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C\WINDOWS\system32\hal.dll
product: Microsoft Windows Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.


crash dump file: C\WINDOWS\Minidump\122714-26093-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DCA0)
Bugcheck code: 0x101 (0x18, 0x0, 0xFFFFD00020657180, 0x2)
Error: CLOCK_WATCHDOG_TIMEOUT
file path: C\WINDOWS\system32\ntoskrnl.exe
product: Microsoft Windows Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

 

[phasseshifter]

did you remove the plastic on the bottom of the cooler when u put it on..it may be in fact if ram and cpu are good ..the mobo may not be up to the job ..

 

[phasseshifter]

down load this pls.................http://www.alcpu.com/CoreTemp/

 

[sam_816]

did you remove the plastic on the bottom of the cooler when u put it on..it may be in fact if ram and cpu are good ..the mobo may not be up to the job ..

plastic??????
there was just this plastic cap on it. under it there was a mesh kind of surface.
there was no mention of removing any plastic in the installation guide too. :'(

 

[phasseshifter]

hmm well core temp will tell you what is going on...you should be getting at idle around 15- 20 degrees approx with an after market cooler i might also add that the two surfaces have to mate flush and true ..did u use compound.. u cannot just pull a cooler out of the box and put it on without compound if no compound..this is prolly your problem..get some .....apply to processor in a X PATTERN ..IT SHOULD HAVE COME WITH SOME IN A SYRINGE A SMALL ONE...soz caps ..on a different note with the machine off grab the cooler can you rotate it a little..in other words is it on tight enough....

 

[sam_816]

hmm well core temp will tell you what is going on...you should be getting at idle around 15- 20 degrees approx with an after market cooler i might also add that the two surfaces have to mate flush and true ..did u use compound..

my core temp on cpu is about 35-40 degrees even when i go directly to UEFI/Bios :/
like now i booted the PC after 15-20 min of rest and the temp in UEFI monitor is 34C for CPU and 30C for Mobo. and it went to 36C without me doing anything.

I didn't apply any thermal compound as the corsair manual said it comes with pre installed.

i have installed core temp and
core 0 min-34 max-44 load 0-1%
core 1 min-33 max-40 load 0-1%
core 2 min-35 max-41 load 0-1%
core 3 min 31 max-48 load 0-1%
power .7 W

 

[phasseshifter]

take of cooler apply compound those figures are way to high..can you take a close up pic and post it of core temp..for me pls..if possible...if in fact that is a water cooler you may have the pump lead the lead that comes from the block connected to the wrong connector..asls something to check..go into bios and make shore all fans are running to there max..like disable stuff like cool and quiet go into h-ware monitor make shore all fans settings are maxed out..the core temps i would expect are around and no higher than 20 degrees..at idle..

 

[sam_816]

take of cooler apply compound those figures are way to high..can you take a close up pic and post it of core temp..for me pls..if possible...

i just did a custom test with intel burn test(custom- 512 mb) and the temps shot to 61-64 with in a second and WHEA error. i think the cpu cooler is not installed properly. let me take it off and post a PIC of the cpu block. may be there is a protective film on. oh god i feel so dumb!!

 

[phasseshifter]

i just did a custom test with intel burn test(custom- 512 mb) and the temps shot to 61-64 with in a second and WHEA error. i think the cpu cooler is not installed properly. let me take it off and post a PIC of the cpu block. may be there is a protective film on. oh god i feel so dumb!!

happens to the best of us when u re apply the block make shure it is a tight fit..the surfaces must mate ..um ok justlooked at the cooler design and specs..its a good unit but poor in it mounting of the block/pump there a bit tricky ...do you have a fan on both sides of the radiator ..i.e..um one fan to push air in and one to extract..i would look at this...the pump does it have 3 wires or four they differ..with different types of set ups generally i connect the pump to a chassis fan connector making shure it runs flat out..others may beg to differ...also look at weather it is a pwm pump or voltage driven..there may be a setting in your bios that you can change...

 

[sam_816]

looks like i installed the cpu cooler fine. i will buy new thermal paste tomorrow and re-apply.
the radiator is not in push-pull config. right now. only push(one fan) due to space limitation. i guess i will add another fan on the outside the case to complete push-pull.
the pump has 3-pin connector which i connected to cpu fan(CPU_FAN) and the fan's connector is on optional (CPU_OPT) fan connector.
I also have selected all FAN connectors to run at 'TURBO' in BIOS along with system performance is selected to ASUS Optimal mode(which is performance oriented mode)

sorry for poor quality screen this is the resolution of the pdf file.

happens to the best of us when u re apply the block make shure it is a tight fit..the surfaces must mate ..um ok justlooked at the cooler design and specs..its a good unit but poor in it mounting of the block/pump there a bit tricky ...do you have a fan on both sides of the radiator ..i.e..um one fan to push air in and one to extract..i would look at this...the pump does it have 3 wires or four they differ..with different types of set ups generally i connect the pump to a chassis fan connector making shure it runs flat out..others may beg to differ...

 

[phasseshifter]

hmmm well you can re assemble it with what compound is let there i think the problem is that it was not on tight enough..or change the pump connector to one of the chassis fan headers and see if it makes a difference..the setup on those pump blocks the fastening method i dont like..each too there own but when you put it back on make shure it is tight to the cpu.. the block it`s self..not able to move the block if you can move it at all then its not a mated fit there should be no movement by hand pressure at all..

 

[phasseshifter]

if only one thing we have narrowed it down a little..i need sleep i am on gmt+ 10:00 time here..well if the pump block has a 3 pin conn on it conn it to a 3 pin headder...peace out ..

 

[sam_816]

hmmm well you can re assemble it with what compound is let there i think the problem is that it was not on tight enough..or change the pump connector to one of the chassis fan headers and see if it makes a difference..the setup on those pump blocks the fastening method i dont like..each too there own but when you put it back on make shure it is tight to the cpu.. the block it`s self..not able to move the block if you can move it at all then its not a mated fit there should be no movement by hand pressure at all..

shouldn't i reapply the compound(fresh)? it would dry after 5-10 minutes, isn't?
i can't tighten it up after a point . the screws get free circulation after that point.
how to connect 3-pin pump controller to 4 pins on the Mo-Bo? should i put in on the 3 pins on the left or right or it doesn't matter? i have doubts about everything now