This is why it points to HAL, it is the first driver before the last NT call which goes to the bugcheck.
It is a very basic explanation, something didn't respond to a call for some reason causing the hardware crash,
Code:
# Child-SP RetAddr Call Site
00 fffff880`009f5b38 fffff800`02820818 nt!KeBugCheckEx
01 fffff880`009f5b40 fffff800`0281ff57 hal!HalpMcaReportError+0x164
02 fffff880`009f5c90 fffff800`02813e88 hal!HalpMceHandlerWithRendezvous+0x9f
03 fffff880`009f5cc0 fffff800`028c4cec hal!HalHandleMcheck+0x40
04 fffff880`009f5cf0 fffff800`028c4b53 nt!KxMcheckAbort+0x6c
05 fffff880`009f5e30 fffff880`04002c61 nt!KiMcheckAbort+0x153
06 fffff880`02d1bb58 fffff800`028cfbe9 intelppm!MWaitIdle+0x19
07 fffff880`02d1bb60 fffff800`028be0dc nt!PoIdle+0x52a
08 fffff880`02d1bc40 00000000`00000000 nt!KiIdleLoop+0x2c
That Bluescreen Viewer or WhoCrashed, or any other similar program, points to HAL with hardware crashes isn't really useful and they can't say anything more which is what makes them useless.
Please update the LAN driver & BIOS Gigabyte provides.
GIGABYTE - Moederbord - Socket 1150 - GA-Z97X-Gaming 3 (rev. 1.1)
Code:
1: kd> lmvm e22w7x64
Browse full module list
start end module name
fffff880`041ab000 fffff880`041d2000 e22w7x64 T (no symbols)
Loaded symbol image file: e22w7x64.sys
Image path: e22w7x64.sys
Image name: e22w7x64.sys
Browse all global symbols functions data
Timestamp: Wed Mar 20 22:35:41 2013 (514A2BAD)
CheckSum: 00031967
ImageSize: 00027000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Please fill in your system specsPlease follow
this tutorial and download the tool. The tool will give you detailed information about your system specs, please fill in your system specs more completely including PSU, cooling and other used stuff like mouse, keyboard, monitor, case, etc.
The PSU, cooling and other stuff are NOT mentioned in the tool.
How to fill in your system specs: