Windows 10: BSOD - ntoskernel, hal.dll

Info attached. Anyone know what caused this?

I was playing Mass Effect 3 at the time.

Attachment 74600

:)

 

BSOD ntoskrnl.exe+16c3f0. Five times in the last week.

I'm interested in what your BSOD is telling you. Just from what I see, you seem to be having a problem with the ntoskernel, but here are other ways to examine the minidump. Microsoft provides a very efficient method without the need of external chants
and vapors.

What does your BSOD say to you? What is the exception error message there?

 

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!

 

RAM Clock incompatibility, most probably.
Your RAM runs at ......
Code: Speed 2933MHz Manufacturer G-Skill Serial Number Asset Tag Number Part Number F4-3000C15-8GTZB[/quote] Which your motherboard does not support. It supports: Attachment 74649In those latest systems like Skylake, the RAM is controlled by the CPU, your CPU supports: Attachment 74653IMHO it would be safe to use a 2133 MHz RAM module.

 

So is that literally the only thing it could be? No other possibilities?

 

Other possibilities are there, but as this one is prima facie, it should be taken care of. A hardware incompatibility is not desirable, and it alone can cause the BSODs.

 

Okay, so a bit of background on the RAM. I deliberately bought DDR4-3000 memory because I wanted fast RAM. I enabled the XMP profile but found that @ 3000Mhz, sometimes the PC wouldn't POST. However, at 2933 it always POSTs.

I would be willing to drop it to 2800 if you think that would be worthwhile.

 

Can you drop it to 2133? Will your Rapjaws support it?

 

Yeah, 2133 is stock (XMP disabled). If that's what it'll take for stability then, fine, but I would like faster memory if poss.

 

2133 is way faster.

Get back to it. See how it goes. If it still BSODs, let us see another log.