Windows 8 BSODS while playing games ntoskrnl.exe/hall.dll

[FridgidDreams]

currently running windows 8.1, I built my own computer so I know all internal parts work together so that's not an issue but when ever I am playing a game, I listen to music or watch a tv show as well to not get bored on my computer. sometimes the bsod occurs and sometimes I don't get it for several days/weeks so I don't really know what is causing this exactly.. I've tried looking for solutions myself but I can't seem to find a fix so here I am hoping that you fine folks can help me out..

now this is a brand new installation of the OS (just installed literally yesterday) still get the bsod - I've had this issue before on different OS's (all windows 8/8.1) but sometimes they would disappear completely and I forget about them or they just don't ever appear or they start showing up the next couple days after re-installing my OS. I'm always running the same software I do through every OS installation I do as it usually never changes for me and it's never caused me issues before it's just kinda been recently as like within the past few months or so.

anyways my diagnostics are down below.
If you need anymore information or anything just let me know and I'll get back asap with what ever is needed, just hope I can get this fixed once and for all :/


Edit: here is the dump I get from BlueScreenView as well -
==================================================
Dump File : 100414-16437-01.dmp
Crash Time : 10/4/14 8:44:40 PM
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x0000000a
Parameter 1 : 00000000`05e0fbbc
Parameter 2 : 00000000`0000000f
Parameter 3 : 00000000`00000001
Parameter 4 : fffff801`dbfadb57
Caused By Driver : hal.dll
Caused By Address : hal.dll+1bb57
File Description : Hardware Abstraction Layer DLL
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.3.9600.17196 (winblue_gdr.140601-1505)
Processor : x64
Crash Address : ntoskrnl.exe+153ca0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\100414-16437-01.dmp
Processors Count : 6
Major Version : 15
Minor Version : 9600
Dump File Size : 296,768
Dump File Time : 10/4/14 8:45:44 PM
==================================================

 

[FridgidDreams]

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {55ffba0, f, 0, fffff801265aabb0}

*** WARNING: Unable to verify timestamp for cpuz137_x64.sys
*** ERROR: Module load completed but symbols could not be loaded for cpuz137_x64.sys
Probably caused by : cpuz137_x64.sys ( cpuz137_x64+2073 )

Followup: MachineOwner

This cpuz137 x64.sys still appears to be the issue or something related. Not only does it appear above but also in your driver stack and stack text. I've been doing some research on why this keeps appearing even though it's not installed and it may have something to do with the CPU.
Try stress testing the CPU with Prime95. You only need to run it for an hour or so but just check all is ok on that end.
http://www.mersenne.org/download/
Check your GPU using this app:
Link Removed
and this app too:
http://www.ozone3d.net/benchmarks/fur/

Well I ran Prime95 for around an hour and a half, I could do better testing at a later time like when I'm asleep or something but the log is down below. it pretty much came up with zero errors.

The first GPU test with VMT didn't bring up any errors as well other than 2 saying that my card wasn't supported for 2 options and when it tried to change my resolution. Log is down below as well

Now for the second GPU test the one with FurMark, I ran it for a bit and never had any issues but I don't know where it keeps it's logs. I had logging enabled but without knowing where it stores them I can't upload it.

 

[kemical]

Furmark does contain it's own test try running the actual test.

As this error has appeared with all the operating systems you've tried let's just make sure some of the basic components are ok.
This may seem pointless but any information is invaluable at this stage if only to discount whatever it is your testing.

Go to your C drive and right click on it. Choose properties, Tools and then check now. Tick any boxes to repair sectors ect and you may need to reboot.

Windows does have it's own memory testing app but it can often miss errors and the best app for the job is Memtest86. The latest version of which can be found here:
http://www.memtest.org/
To run Memtest86 you need to either burn a copy of it to disk or use a USB stick. If you look down the page you'll eventually find the latest version and it's associated downloads. If your burning to disk choose the pre-compiled iso zip. If your using a USB method then the corresponding download is the auto installer for a USB stick.
Once you have Memtest86 on the media you selected you'll then need to enter your bios and change the boot order so that the machine will boot from either the disk or stick you have Memtest86 on.
Run for at least 12hrs unless it becomes clear that there is a issue. If there is a problem with the RAM you'll see the errors pop up in red so you can't miss them.

 

[FridgidDreams]

Furmark does contain it's own test try running the actual test.

As this error has appeared with all the operating systems you've tried let's just make sure some of the basic components are ok.
This may seem pointless but any information is invaluable at this stage if only to discount whatever it is your testing.

Go to your C drive and right click on it. Choose properties, Tools and then check now. Tick any boxes to repair sectors ect and you may need to reboot.

Windows does have it's own memory testing app but it can often miss errors and the best app for the job is Memtest86. The latest version of which can be found here:
http://www.memtest.org/
To run Memtest86 you need to either burn a copy of it to disk or use a USB stick. If you look down the page you'll eventually find the latest version and it's associated downloads. If your burning to disk choose the pre-compiled iso zip. If your using a USB method then the corresponding download is the auto installer for a USB stick.
Once you have Memtest86 on the media you selected you'll then need to enter your bios and change the boot order so that the machine will boot from either the disk or stick you have Memtest86 on.
Run for at least 12hrs unless it becomes clear that there is a issue. If there is a problem with the RAM you'll see the errors pop up in red so you can't miss them.

I did run it's test all it does it just pop up the information after a run and that's it, it doesn't seem to keep a log anywhere though or at least one I can't seem to find anyways.

I've already tried the error checking before as requested on another forum it never fixed anything.

As for memtest86 I'm unable to run it for at least 12 hours as I'm not the only one who uses this computer, plus I do a lot of my work from this computer as well and honestly I've already replaced RAM Sticks 2 times already thinking that might of been the issue a while back (few months ago) and as it still happens then obviously it's not because of the RAM.

 

[kemical]

It could be the RAM slots. Try running it for less time then. Does the other person who uses the pc have their own account?

 

[FridgidDreams]

It could be the RAM slots. Try running it for less time then. Does the other person who uses the pc have their own account?

I honestly doubt it has anything to do with either the RAM or the RAM slots, when the windows 10 tech preview came out I ran it for a couple days (still have it on a separate hard drive that's not plugged in atm) and I never had any issues, no blue screens no anything. I'd of stayed on the tech preview if it wasn't for the fact that I had sound issues because the drivers for my headsets wouldn't work on windows 10.

No the other person who uses the PC just uses my account since all they mainly do is play games or browse Facebook or various other sites or do paperwork and such for where she works.

Now here's a funny thing that seems to have happened, so I deleted the registry entry for the cpuz yesterday as someone suggested it on another forum that's helping me out as well with this problem and I know for sure it was gone as I tripple checked before restarting my computer, well just now I did a registry scan for cpuz and well it's some how back..

 

[kemical]

As I mentioned in the previous post sometimes these things are worth checking if only to discount them. It's entirely up to you if you want to take my advice or not.

Somewhere on your system is a copy of cpu-z or something like it and this is causing the issue. Have you checked for malware?
https://www.malwarebytes.org/

 

[FridgidDreams]

As I mentioned in the previous post sometimes these things are worth checking if only to discount them. It's entirely up to you if you want to take my advice or not.

Somewhere on your system is a copy of cpu-z or something like it and this is causing the issue. Have you checked for malware?
https://www.malwarebytes.org/

Well I might of finally found out my issue as to why I am getting bsods, I have been running Advanced System Care from IOBIT which ofc is a cleaner kinda like ccleaner but with a bit more options than just cleaning, anyways ; it was what was creating the cpuz137_x64 registry entry and such as it has a menu of sorts that show things like cpu temps and responsiveness and ram load and all that kinda stuff.

I never actually thought about it because I've been running Advanced System Care for years and never had an issue with the program before but a new beta came out in the past 2-3 months and that's when all the cpu/ram/gpu stuff came into play in the program.

I've uninstalled ASC and deleted the registry entry for cpuz137, so hopefully this is the end to my bsods once and for all but only time will tell I guess. I'll post sometime next week if I don't get another bsod before then to let you know if it fixed it.

 

[kemical]

Damn.... Really? Well at least you found it at last (the cpu-z mystery) and this is excellent for my own records too. As they say 'your always learning'! Best of luck Frigid and please post back with any results or new bsods.

 

[FridgidDreams]

Damn.... Really? Well at least you found it at last (the cpu-z mystery) and this is excellent for my own records too. As they say 'your always learning'! Best of luck Frigid and please post back with any results or new bsods.

Well it has been a little over a week now and I haven't had any more bsods since removal of Advanced System Care so as it stands this issue has been fixed ^^

 

[kemical]

Thanks for updating and best of luck for the future. Post back if you should ever need to..