Mobile and Desktop Processors
Intel® Core™ processors, Intel Atom® processors, tools, and utilities
公告
FPGA community forums and blogs on community.intel.com are migrating to the new Altera Community and are read-only. For urgent support needs during this transition, please visit the FPGA Design Resources page or contact an Altera Authorized Distributor.
16837 讨论

BSOD from Turbo Boost Max

CMees
初学者
27,506 次查看

I've been getting the occasional BSOD recently: IRQL_NOT_LESS_OR_EQUAL

 

Using WhoCrashed by Resplendence has suggested it may have something to do with the Intel(R) Turbo Boost Max Technology 3.0 Driver

 

I have disabled the service from starting for now, to see if that fixes it, but I'm wondering if anyone else have any experience with this, or can give insight into what may be going on?

Operating System Windows 10 Pro 1703 15063.296

 

Processor (CPU) Intel® Core™i7 Six Core Processor i7-6850K (3.6GHz) 15MB Cache

 

Motherboard ASUS® X99-E: ATX, Broadwell-E CPU, USB 3.0, SATA 6 GB/s

 

Memory (RAM) 32GB Corsair Vengeance DDR4 3000 MHz X.M.P (4 x 8GB)

Intel - Turbo Boost Max Technology 3.0 version 1.0.2.1

 

Intel - Turbo Boost Max Technology 3.0 Service version 1.0.0.1031

This is what WhoCrashed said for the last crash:

On Fri 12/05/2017 03:51:04 your computer crashed

 

crash dump file: C:\Windows\Minidump\051217-17406-01.dmp

 

This was probably caused by the following module: http://www.google.com/search?q=ntoskrnl.exe ntoskrnl.exe (nt+0x16C310)

 

Bugcheck code: 0xA (0xFFFFD401003160C0, 0x2, 0x1, 0xFFFFF801847D7E7E)

 

Error: http://www.google.com/search?q=MSDN+bugcheck+IRQL_NOT_LESS_OR_EQUAL IRQL_NOT_LESS_OR_EQUAL

 

file path: C:\Windows\system32\ntoskrnl.exe

 

product: http://www.google.com/search?q=Microsoft%C2%AE%20Windows%C2%AE%20Operating%20System Microsoft® Windows® Operating System

 

company: http://www.google.com/search?q=Microsoft%20Corporation Microsoft Corporation

 

description: NT Kernel & System

 

Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.

 

This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.

 

The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

 

 

On Fri 12/05/2017 03:51:04 your computer crashed

 

crash dump file: C:\Windows\memory.dmp

 

This was probably caused by the following module: http://www.google.com/search?q=intelnit.sys intelnit.sys (IntelNit+0x660A)

 

Bugcheck code: 0xA (0xFFFFD401003160C0, 0x2, 0x1, 0xFFFFF801847D7E7E)

 

Error: http://www.google.com/search?q=MSDN+bugcheck+IRQL_NOT_LESS_OR_EQUAL IRQL_NOT_LESS_OR_EQUAL

 

file path: C:\Windows\system32\drivers\intelnit.sys

 

product: http://www.google.com/search?q=Intel(R)%20Turbo%20Boost%20Max%20Technology%203.0%20Driver Intel(R) Turbo Boost Max Technology 3.0 Driver

 

company: http://www.google.com/search?q=Intel%20Corporation Intel Corporation

 

description: Intel(R) Turbo Boost Max Technology 3.0 Driver

 

Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.

 

This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.

 

A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: intelnit.sys (Intel(R) Turbo Boost Max Technology 3.0 Driver, Intel Corporation).

 

Google query: http://www.google.com/search?q=intelnit.sys+Intel%20Corporation+IRQL_NOT_LESS_OR_EQUAL Intel Corporation IRQL_NOT_LESS_OR_EQUAL

 

The minidump can be downloaded here: https://www.dropbox.com/s/hnsymjz9i7gkk0p/051217-17406-01.dmp?dl=0 Dropbox - 051217-17406-01.dmp

The full memory dump:https://www.dropbox.com/s/sk2fqxr3x146eaw/MEMORY.DMP?dl=0 Dropbox - MEMORY.DMP

Thanks for any help anyone can give!

0 项奖励
49 回复数
idata
员工
5,203 次查看

In this case, you will need to attach it to the post; no personal information is collected. Intel is committed to protecting your privacy. See http://www.intel.com/privacy Intel's Privacy Notice.

 

 

 

Ivan U.

 

0 项奖励
PHida
初学者
5,203 次查看

I tried submitting a ticket with no avail, same issue I've got. freeze on Turbo boost

0 项奖励
JKrie
初学者
5,203 次查看

How do i attach the systeminfo.txt file? Or should i just paste it in?

0 项奖励
idata
员工
5,203 次查看

You can attach it, please see how at the pictures below:

 

Click reply and see the red arrow from the pictures.

 

Regards,

Ivan U.

0 项奖励
JKrie
初学者
5,203 次查看

File attached

0 项奖励
idata
员工
5,203 次查看

Thank you!

 

 

 

Ivan U.
0 项奖励
idata
员工
5,203 次查看

Hello all,

 

 

Just one question, if you have the TB 3.0 enabled in the bios, is this failing on Safe Mode?

 

If the TB 3.0 is enabled and you disable Hyper Threading the issue persists.

 

 

 

Regards,

 

 

 

Ivan U
0 项奖励
JKrie
初学者
5,203 次查看

I haven't tried either of these, and unfortunately with TB 3.0 enabled it happens once or twice a week. I can't really work for a week either in safe-mode or with hyperthreading disabled.

FWIW, I haven't had any BSOD since disabling TB 3.0 in the BIOS. However, the machine performance seems lower.

0 项奖励
idata
员工
5,203 次查看

Thank you for that information.

 

 

Best regards,

 

 

 

Ivan U.

 

0 项奖励
idata
员工
5,203 次查看

Hello Claire_Monkey,

 

 

I sent you a private message about a warranty request.

 

 

 

Ivan U.
0 项奖励
JKrie
初学者
5,203 次查看

IntelCorporation Ivan any update on this? We have another person in the office also experiencing this BSOD now. All evidence we're seeing points to the driver. I will (privately) share my MEMORY.DMP file if it will help your engineers find the problem.

0 项奖励
idata
员工
5,203 次查看

I am having the exact same problems as stated in this thread. I have a new i7-7820x, with an ASUS Prime-x299-A Motherboard. Any help would be appreciated.

Here is what I got from WhoCrashed:

On Sun 9/17/2017 2:26:04 PM your computer crashed

 

crash dump file: C:\Windows\Minidump\091717-8671-01.dmp

 

This was probably caused by the following module: http://www.google.com/search?q=intelnit.sys intelnit.sys (IntelNit+0x5325)

 

Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8004A895325, 0xFFFF9C00C02CEEB8, 0xFFFF9C00C02CE700)

 

Error: http://www.google.com/search?q=MSDN+bugcheck+SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M

 

file path: C:\Windows\system32\drivers\intelnit.sys

 

product: http://www.google.com/search?q=Intel(R)%20Turbo%20Boost%20Max%20Technology%203.0%20Driver Intel(R) Turbo Boost Max Technology 3.0 Driver

 

company: http://www.google.com/search?q=Intel%20Corporation Intel Corporation

 

description: Intel(R) Turbo Boost Max Technology 3.0 Driver

 

Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.

 

This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.

 

A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: intelnit.sys (Intel(R) Turbo Boost Max Technology 3.0 Driver, Intel Corporation).

I had updated to driver 1.0.0.1033 and did have the latest driver. I went back to driver 1.0.0.1032 to see if it does better because my problem started with driver 1033, which is the latest.

Any suggestions how I can prevent more BSOD ?

Thanks for any help.

0 项奖励
CMees
初学者
5,203 次查看

The only way to prevent the BSOD is to go in to BIOS and turn off the Turbo Boost feature from ever running.

Intel have admitted to me there is a fault with my processor and if I had bought it less than a year ago they would've replaced it free of charge. As it happens they took 3 months to tell me this, and therefore I'm apparently not entitled to one.

Raise a support ticket directly with them, and they should offer you a replacement.

As far as anyone has told me, there is no way of fixing Turbo Boost with software.

0 项奖励
BWint6
初学者
5,203 次查看

So is this actually a fault with the processor itself and not the software?

0 项奖励
CMees
初学者
5,203 次查看

That's what they told me. They certainly haven't released a software fix of any kind.

0 项奖励
idata
员工
5,203 次查看

Thanks for the information. I started having problems once I upgraded the driver to 1.0.0.1033. I went back to 1032 and hope this helps. I would hate to disable Turbo Max.

0 项奖励
BWint6
初学者
5,203 次查看

Oh right.

I don't think they will either.

I have managed to resolve the issue by just setting it to 'disabled' but still keeping the software installed.

It reinstalls itself automatically on restart if you uninstall it from the PC

It is rather annoying that I can't benefit from the boosted processor, but I would rather have stable performance and not a BSOD every few hours.

0 项奖励
CMees
初学者
5,203 次查看

Yeah I couldn't get it to actually disable anywhere other than in BIOS. Windows likes to automatically have it on.

 

It's been fine since it was disabled. I'd rather have it on of course, but I tried everything, my choice was turn it off or constant BSOD.

 

And then Intel confirmed that I'd be entitled to a replacement if I was in warranty as it was a hardware fault.

 

Obviously you might not have the same problem as me, but this is my experience.
0 项奖励
BWint6
初学者
5,234 次查看

Thanks claire_monkey. I know what you mean about the constant BSOD - so frustrating.

I will speak to Intel regarding a replacement as I think mine is still in Warranty

0 项奖励
BWint6
初学者
5,203 次查看

Ivan, the only solution I found was to set Turbo Boost to 'disabled'

Now I haven't had any other BSOD's

Until Intel sort out their phony turbo boost driver it is the only way to stop it crashing the entire system.

It is a shame that I can't get the performance benefits of turbo boost, but I am not sure what else to do at this stage and I am sick of it crashing my pc when i'm in the middle of working or worse on the phone with a client!

0 项奖励
CVigu
初学者
5,234 次查看

Hi guys,

Let me start by saying i feel all of your pain.

I've been getting BSOD's daily since i built my new X299 system.

initially thought it was the memory, so at the point where i'm about the RMA the memory. But then i came across this post.

Learnt how to analyze my crashes, and seemingly (the recent ones anyway) IRQL_NOT_LESS_OR_EQUAL are pointing to intelNit.sys.

So what do i need to do here? I get at least 4 BSOD's a day, driving me crazy.

here's my WhoCrashed analysis of the last 5:

Computer name: CASEYV-PC

 

Windows version: Windows 10 , 10.0, build: 15063

 

Windows dir: C:\Windows

 

Hardware: ASRock, X299 Taichi

 

CPU: GenuineIntel Intel(R) Core(TM) i9-7900X CPU @ 3.30GHz Intel586, level: 6

 

20 logical processors, active mask: 1048575

 

RAM: 16867180544 bytes total

 

 

 

Crash Dump Analysis

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

 

On Tue 9/26/2017 2:16:50 PM your computer crashed

 

crash dump file: C:\Windows\Minidump\092617-10296-01.dmp

 

This was probably caused by the following module: http://www.google.com/search?q=ntoskrnl.exe ntoskrnl.exe (nt+0x16C580)

 

Bugcheck code: 0xA (0xFFFFA6025D85F0C0, 0x2, 0x1, 0xFFFFF803949DD87A)

 

Error: http://www.google.com/search?q=MSDN+bugcheck+IRQL_NOT_LESS_OR_EQUAL IRQL_NOT_LESS_OR_EQUAL

 

file path: C:\Windows\system32\ntoskrnl.exe

 

product: http://www.google.com/search?q=Microsoft%C2%AE%20Windows%C2%AE%20Operating%20System Microsoft® Windows® Operating System

 

company: http://www.google.com/search?q=Microsoft%20Corporation Microsoft Corporation

 

description: NT Kernel & System

 

Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.

 

This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.

 

The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

 

 

 

On Tue 9/26/2017 2:16:50 PM your computer crashed

 

crash dump file: C:\Windows\memory.dmp

 

This was probably caused by the following module: http://www.google.com/search?q=intelnit.sys intelnit.sys (IntelNit+0x6612)

 

Bugcheck code: 0xA (0xFFFFA6025D85F0C0, 0x2, 0x1, 0xFFFFF803949DD87A)

 

Error: http://www.google.com/search?q=MSDN+bugcheck+IRQL_NOT_LESS_OR_EQUAL IRQL_NOT_LESS_OR_EQUAL

 

file path: C:\Windows\system32\drivers\intelnit.sys

 

product: http://www.google.com/search?q=Intel(R)%20Turbo%20Boost%20Max%20Technology%203.0%20Driver Intel(R) Turbo Boost Max Technology 3.0 Driver

 

company: http://www.google.com/search?q=Intel%20Corporation Intel Corporation

 

description: Intel(R) Turbo Boost Max Technology 3.0 Driver

 

Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.

 

This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.

 

A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: intelnit.sys (Intel(R) Turbo Boost Max Technology 3.0 Driver, Intel Corporation).

 

Google query: http://www.google.com/search?q=intelnit.sys+Intel%20Corporation+IRQL_NOT_LESS_OR_EQUAL Intel Corporation IRQL_NOT_LESS_OR_EQUAL

 

 

 

On Mon 9/25/2017 10:27:37 AM your computer crashed

 

crash dump file: C:\Windows\Minidump\092517-10125-01.dmp

 

This was probably caused by the following module: http://www.google.com/search?q=ntoskrnl.exe ntoskrnl.exe (nt+0x16C580)

 

Bugcheck code: 0xA (0xFFFF868AF9B71800, 0x2, 0x1, 0xFFFFF8016F5D087A)

 

Error: http://www.google.com/search?q=MSDN+bugcheck+IRQL_NOT_LESS_OR_EQUAL IRQL_NOT_LESS_OR_EQUAL

 

file path: C:\Windows\system32\ntoskrnl.exe

 

product: http://www.google.com/search?q=Microsoft%C2%AE%20Windows%C2%AE%20Operating%20System Microsoft® Windows® Operating System

 

company: http://www.google.com/search?q=Microsoft%20Corporation Microsoft Corporation

 

description: NT Kernel & System

 

Bug check description: This indicates that Micr...
0 项奖励
回复