BSOD Hal.DLL HELP!??! 0x15

Sraggetty

Honorable
Aug 9, 2013
19
0
10,510
-------------------------------------------------
On Wed 27/01/2016 17:36:34 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\012716-21609-01.dmp
This was probably caused by the following module: hal.dll (hal!HalpTimerClockIpiRoutine+0x15)
Bugcheck code: 0x3D (0xFFFFD001842F8BA8, 0xFFFFD001842F83C0, 0x0, 0x0)
Error: INTERRUPT_EXCEPTION_NOT_HANDLED
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 appears very infrequently.
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.

----------------------------
AMD FX 8350 Not Overclocked
Asus Pro3 R2.0 AM3+ Mobo up to date UEFI
HyperX Fury 1866mhz (Memtest passed)
600W CX Corsair PSU
NVIDIA GTX 970
Crucial 500GB SSD
Appropriate cooling, no overheating

Notes:
I'm not certain of any of this, as I am new to the system, but the specs are what they are.
This happens every time I close a intensive game (Especially if I have a video running on another screen)
Could this be a clash of Drivers? I recently moved from AMD to NVIDIA graphics cards, even though I removed the drivers some stuff could still be there?
This sometimes happens browsing the web
I can return whatever before the 31st of Jan 2016 so please reply fast<3
I read that 0x124 meant hardware failure, but mine is 0x15? I don't understand

-Please tell me if I missed anything,
Thanks
 
Solution
hal is the windows hardware abstraction layer, it is a interface for windows to talk to your hardware.
The BIOS configures your hardware.
the routine that was having a problem was a timer routine, most likely some hardware did not respond in a timely manner. This happens when you overclock,overheating, have bad BIOS settings, sometimes you get this when you plug in USB devices and the windows plug and play tries to install a driver but the driver install fails. (mostly on windows 7 with certain USB wireless devices)

you update or reset the BIOS to defaults and the BIOS will reassign hardware resources and will pass a database of settings to hal.dll so windows knows what BIOS resources the BIOS has assigned and will know which ones...
you will want to update the BIOS of your machine or reset it to defaults as a first attempt as a fix, then boot windows and install the current motherboard drivers for your machine and windows version. Get the drivers from the motherboard vendors website.

 

Sraggetty

Honorable
Aug 9, 2013
19
0
10,510


So you think its an software issue? thank god - will have a look
 
hal is the windows hardware abstraction layer, it is a interface for windows to talk to your hardware.
The BIOS configures your hardware.
the routine that was having a problem was a timer routine, most likely some hardware did not respond in a timely manner. This happens when you overclock,overheating, have bad BIOS settings, sometimes you get this when you plug in USB devices and the windows plug and play tries to install a driver but the driver install fails. (mostly on windows 7 with certain USB wireless devices)

you update or reset the BIOS to defaults and the BIOS will reassign hardware resources and will pass a database of settings to hal.dll so windows knows what BIOS resources the BIOS has assigned and will know which ones are free for it to assign.




 
Solution

Sraggetty

Honorable
Aug 9, 2013
19
0
10,510


Thank you so much! will take this in account <3