Windows 10: hal.dll and ntoskrnl.exe BSOD only when gaming

Hi Jordan here.

I've recently been getting a lot of blue screens whilst gaming, this problem occurred when I was on Windows 7 too but I upgraded to 10 when I done a clean install of windows.
I'm not really sure what is causing the problem.
I've ran tests on my cpu, gpu, ram and hard drive and they all passed but I had my suspicion of it being the gpu as I tested an older card in my rig everything was fine. I contacted the store that sold me my gpu and after a lot of testing on my side they came to the conclusion it was my psu. It turns out it wasn't my psu because I've just bought a brand new one and I'm still getting BSOD.

I have noticed that before the pc blue screens that my games will stutter and the fps will drop a reasonable amount and this only happens when gaming.

It has blue screened on all of the games I play. GTA 5, CSGO, H1Z1 and a few others too.

If anyone could help me find out what is causing this problem I would really appreciate it because I don't want to end up spending more money on things that I don't need to buy.

Every thing you need to know about my system should be in the .zip I attached, if there's something missing that you need then please let me know.

Attachment 38892
Thanks,
Jordan.

:)

 

Windows 10 BSOD

HP Envy h8-1450. Updated to Build 10586. Now getting BSOD, but only on my primary admin account.

BlueScreen view seems to implicate hal.dll and/or ntoskrnl.exe

Tried rolling back with no luck. Also, nothing found with SFC scan.

Thanks in advace,

Jeremy

 

hal.dll+35f1f bsod error in Windows 10

OT- hal.dll+35f1f bsod

Hello,

There was a bsod just now, which is the first time I've experienced it - and should I be worrying about it?

This is what I got from BlueScreenView:

071816-24656-01.dmp

18/7/2016 8:23:23 PM

0x00000124

00000000`00000000

ffffe000`2db12028

00000000`b2000000

00000000`00100402

hal.dll

hal.dll+35f1f

x64

ntoskrnl.exe+142940

C:\WINDOWS\Minidump\071816-24656-01.dmp

What caused this? Thanks!

 

Hi Jordan & Welcome to the forums ^_^,

I have analysed your dump files and below has been provided an analysis of the same for informative purposes :-
Code: 7: kd> !errrec ffffe001`974e7028=============================================================================== Common Platform Error Record @ ffffe001974e7028 ------------------------------------------------------------------------------- Record Id : 01d0f55a885dc611 Severity : Fatal (1) Length : 928 Creator : Microsoft Notify Type : Machine Check Exception Timestamp : 9/22/2015 17:40:46 (UTC) Flags : 0x00000000 =============================================================================== Section 0 : Processor Generic ------------------------------------------------------------------------------- Descriptor @ ffffe001974e70a8 Section @ ffffe001974e7180 Offset : 344 Length : 192 Flags : 0x00000001 Primary Severity : Fatal Proc. Type : x86/x64 Instr. Set : x64 Error Type : Micro-Architectural Error Flags : 0x00 CPU Version : 0x00000000000306c3 Processor ID : 0x0000000000000007 =============================================================================== Section 1 : x86/x64 Processor Specific ------------------------------------------------------------------------------- Descriptor @ ffffe001974e70f0 Section @ ffffe001974e7240 Offset : 536 Length : 128 Flags : 0x00000000 Severity : Fatal Local APIC Id : 0x0000000000000007 CPU Id : c3 06 03 00 00 08 10 07 - bf fb fa 7f ff fb eb bf 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 Proc. Info 0 @ ffffe001974e7240 =============================================================================== Section 2 : x86/x64 MCA ------------------------------------------------------------------------------- Descriptor @ ffffe001974e7138 Section @ ffffe001974e72c0 Offset : 664 Length : 264 Flags : 0x00000000 Severity : Fatal Error : Internal timer (Proc 7 Bank 4) Status : 0xbe00000000800400 Address : 0x00007ffc4894d9e8 Misc. : 0x00007ffc4894d9e8[/quote] I tried analyzing the other dump files but they were severely corrupted *Sad . Only the recent most dump file gave some information. As per the dump there was an Internal Timer Error which caused the system to crash.
Below is a list of 3rd party drivers present on your system -
Code: **************************Tue Sep 22 23:10:46.576 2015 (UTC + 5:30)************************** AsIO.sys Wed Aug 22 15:24:47 2012 (5034AC67) speedfan.sys Sun Dec 30 02:29:35 2012 (50DF59B7) TeeDriverx64.sys Wed Sep 24 01:31:14 2014 (5421D18A) e1i63x64.sys Fri Mar 27 01:54:57 2015 (55146B19) nvhda64v.sys Fri Apr 17 00:33:16 2015 (55300774) RTCore64.sys Fri Apr 24 12:31:47 2015 (5539EA5B) RTKVHD64.sys Tue Jun 16 16:25:05 2015 (55800089) intelppm.sys Fri Jul 10 08:42:59 2015 (559F383B) NvStreamKms.sys Sat Jul 25 14:52:15 2015 (55B35547) nvvad64v.sys Mon Aug 10 13:21:42 2015 (55C8580E) nvlddmkm.sys Tue Aug 25 19:11:50 2015 (55DC709E) ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨`` **************************Thu Sep 3 20:20:13.510 2015 (UTC + 5:30)************************** X6va060 Thu Aug 6 12:27:21 2015 (55C30551) nvlddmkm.sys Fri Aug 7 08:49:41 2015 (55C423CD)[/quote] http://www.carrona.org/drivers/driver.php?id=AsIO.sys
http://www.carrona.org/drivers/driver.php?id=speedfan.sys
http://www.carrona.org/drivers/driver.php?id=TeeDriverx64.sys
http://www.carrona.org/drivers/driver.php?id=e1i63x64.sys
http://www.carrona.org/drivers/driver.php?id=nvhda64v.sys
http://www.carrona.org/drivers/driver.php?id=RTCore64.sys
http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys
http://www.carrona.org/drivers/driver.php?id=intelppm.sys
http://www.carrona.org/drivers/driver.php?id=NvStreamKms.sys
http://www.carrona.org/drivers/driver.php?id=nvvad64v.sys
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
X6va060 - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys




Kindly follow the below steps -

• Kindly remove the ASUS Bloatware (ASUS PCProbe Utility) since ASUS bloatware is known to cause problems.
• Make sure that you are not overclocking. In case you are overclocking, kindly reset everything to STOCK settings.
• This appears to be a hardware problem. Kindly run the Prime95 test as per the below guide and report back the results -

Let me know how it goes ^_^

-Pranav