hal.dll bsod windows 8.1

Nikoro

Reputable
Jun 12, 2015
8
0
4,510
Hey guys I need your help,

I've been having trouble with BSODs
(This was probably caused by the following module: hal.dll (hal+0x37213)
Bugcheck code: 0x124 (0x0, 0xFFFFE001B0CF7028, 0xBF800000, 0x124)
Error: WHEA_UNCORRECTABLE_ERROR) on my almost new PC

Here's my list of components:
ASUS Maximus VII Ranger
Intel Core i7 -4790K CPU 4.00GHz
corsair vengeance pro 16gb DDR3 (2x8gb)
Nvidia GeForce GTX 680
700W Cooler Master
240 SSD, 1Tb HDD
cooler master hyper 212 evo
Win 8.1 Pro with Media Center
Hope to hear from you soon
here are my dump files
https://drive.google.com/folderview?id=0B_kv7eronKtseE1VQ0hUb2xSaDA&usp=sharing
 
I would remove old/suspect asus driver and update the BIOS
https://www.asus.com/Motherboards/MAXIMUS_VII_RANGER/HelpDesk_Download/


I would suspect that your current BIOS is not correctly programmed for your low voltage CPU and is apply too much voltage to the CPU.
same goes with your asus driver IOMap64.sys from 2013.

guessing from two hints listed in the BIOS:
Max Speed 3800MHz
Current Speed 4003MHz
the max speed is the max speed for a older higher voltage CPU, updated BIOS would show 4000Mhz, your current speed showing 3Mhz overclock means your tweaking driver thinks it is overclocking when it is really not.
I think your BIOS just applied too high a voltage, one intended for a 3.8 GHz CPU running at 4 GHz, this caused your newer CPU to get a cache error on core 1 cache bank 1 so the CPU shut the system down.

Error : DCACHEL0_WR_ERR (Proc 1 Bank 1)

(could also be a power issue but the BIOS would be my first guess, your CPU came out around the same time as your BIOS, the BIOS might not have picked up the required microcode changes to support your CPU)

-------
first bugcheck 0x124 WHEA_UNCORRECTABLE_ERROR called by CPU


note: suspect drivers remove:
C:\Windows\system32\drivers\IOMap64.sys Tue Jul 02 01:27:47 2013
\SystemRoot\SysWow64\drivers\AsIO.sys Wed Aug 22 02:54:47 2012
\SystemRoot\SysWow64\drivers\AsUpIO.sys Mon Aug 02 19:47:59 2010
\SystemRoot\SysWow64\drivers\ASUSFILTER.sys Tue Sep 20 08:46:33 2011

machine info:
BIOS Release Date 07/16/2014
Manufacturer ASUSTeK COMPUTER INC.
Product MAXIMUS VII RANGER


Processor Version Intel(R) Core(TM) i7-4790K CPU @ 4.00GHz
Processor Voltage 8ch - 1.2V
External Clock 100MHz
Max Speed 3800MHz
Current Speed 4003MHz
 
Thank you very much for your response johnbl, I have updated whatever I could from asus site, and first of all I updated BIOS, hope this will solve my problem thank you.
 
BIOS list the max speed as 3800MHz, You might want to check your BIOS voltages for your CPU and confirm they are set correctly.

--------
first bugcheck 0x124 was a cache memory error reported by the CPU 1 memory bank 1
most likely caused because of overclock software running.

remove:
C:\Windows\system32\drivers\IOMap64.sys Tue Jul 02 01:27:47 2013
remove: Asus Ai Booster software
\C:\Windows\SysWow64\drivers\AsInsHelp64.sys Thu Jan 03 21:36:10 2008

I would consider removing the other asus software drivers:
\SystemRoot\SysWow64\drivers\AsIO.sys Wed Aug 22 02:54:47 2012
\SystemRoot\SysWow64\drivers\AsUpIO.sys Mon Aug 02 19:47:59 2010
\SystemRoot\SysWow64\drivers\ASUSFILTER.sys Tue Sep 20 08:46:33 2011



boot into bios and reset BIOS to defaults and reboot.

second bugcheck looks like overclocking related also, either directly related to overclocking or the overclocking caused your CPU to overheat.
(you might check your CPU fans and blow out any dust)
uptime of the system was 15 hours.
Error Type : Cache error
Operation : Generic
Severity : Fatal
Error : DCACHEL0_WR_ERR (Proc 1 Bank 1)


Manufacturer ASUSTeK COMPUTER INC.
Product MAXIMUS VII RANGER
Version Rev 1.xx

BIOS Version 2702
BIOS Starting Address Segment f000
BIOS Release Date 04/27/2015

Socket Designation SOCKET 1150
Processor Version Intel(R) Core(TM) i7-4790K CPU @ 4.00GHz
Processor Voltage 8ch - 1.2V
External Clock 100MHz
Max Speed 3800MHz
Current Speed 4007MHz

 
I have checked in bios cpu max speed was 4000, but why does softwares for asus motherboards can be cause of dump?
and it dumped when I was working and my working temperature is about 62 C isn't it normal temperature?
 
also the ASUS overclocking software you are running is applying clock speeds and voltages based on CPUs that were release in 2013. These are higher voltages than what would be used for your new low voltage CPU. Most likely the software is just applying too high a voltage and thinks it is overclocking a 3.8 GHz processor to 4.007GHZ with too high a voltage(because of your new CPU).

--------------
62C is 144 F, I think the thermal shutdown point is 72C
So it kind of depends on how the 62C was read. You can actually hit thermal shutdown on a CPU but still show a lower temp.
Or a single CPU on the processor can overheat and get errors before the system tries to throttle your CPU.
(guess you should check your BIOS settings for your CPU to make sure your CPU throttles on overheating)
----------
the asus software has bugs that overwrite data in memory that it does not own. The data tends to belong to the driver that is in memory next to the ASUS drivers memory. Windows tries to load the drivers in different orders on each boot, so you tend to get "random" corruptions of windows code. You can run cmd.exe as an admin, then run
verifier.exe /standard /all
and reboot, this will tell windows to check each driver for common errors and you can catch the bad drivers.
(use verifier.exe /reset to turn off verifier functions when done)

for most people, they don't actually use the various asus programs so it is best to remove them. Otherwise, update them and run verifier.exe to confirm that they work as expected. (then turn off verifier)



 
no my shutdown point is above 72 because I did some renders and at that moment temp was 80-82 C and it worked well without any restart

I did what you said activated verifier.exe /standard /all and my pc started looping bsod right before starting windows )). I canceled it from safe mode, so now I have many dump files and whocrashed says that

This was probably caused by the following module: ntoskrnl.exe (nt+0x153CA0)
Bugcheck code: 0xC4 (0x0, 0x0, 0x1, 0x0)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION

This was probably caused by the following module: asramdisk.sys (asramdisk+0x2DC8)
Bugcheck code: 0xC4 (0x0, 0x0, 0x1, 0x0)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION

here are some of that dump files

https://drive.google.com/folderview?id=0B_kv7eronKtsUDhWU1pQenRwRXM&usp=sharing
 
and I use this soft ASUS AI Suite 3 V1.00.83 that is up to date and in asus website there is no newer version so I guess it has to know my new CPU and my current CPU Frequency 4409.8 MHz.
 
I have installed new windows (I disabled windows update) downloaded from asus site drivers(Chipset,AUDIO,LAN,SATA). I did not install any other asus utilities, and today when I was copying my files it dumped again, and yesterday I left verifier.exe on.
and here is the link

https://drive.google.com/folderview?id=0B_kv7eronKtsfjdpeHBMTnktOVlsa1hsNXFRUGd1N1BTUElNUEI3T1VTWGtyQWoxZTBsY3c&usp=sharing

On Sat 04.07.2015 07:08:28 GMT your computer crashed
crash dump file: C:\Windows\Minidump\070415-15859-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x153CA0)
Bugcheck code: 0xC9 (0x242, 0xFFFFF8001F8FDE30, 0xFFFFCF82181B6D30, 0xFFFFE001AE2F1AB0)
Error: DRIVER_VERIFIER_IOMANAGER_VIOLATION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This is the bug check code for all Driver Verifier
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 04.07.2015 07:08:28 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: verifierext.sys (VerifierExt!XdvHibernationNotification+0x5971)
Bugcheck code: 0xC9 (0x242, 0xFFFFF8001F8FDE30, 0xFFFFCF82181B6D30, 0xFFFFE001AE2F1AB0)
Error: DRIVER_VERIFIER_IOMANAGER_VIOLATION
file path: C:\Windows\system32\drivers\verifierext.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Driver Verifier Extension
Bug check description: This is the bug check code for all Driver Verifier
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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.