BSOD from Turbo Boost Max

[CMees]

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 DriverI 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.dmpThis 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_EQUALfile path: C:\Windows\system32\ntoskrnl.exeproduct: http://www.google.com/search?q=Microsoft%C2%AE%20Windows%C2%AE%20Operating%20System Microsoft® Windows® Operating Systemcompany: http://www.google.com/search?q=Microsoft%20Corporation Microsoft Corporationdescription: NT Kernel & SystemBug 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 crashedcrash dump file: C:\Windows\memory.dmpThis 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_EQUALfile path: C:\Windows\system32\drivers\intelnit.sysproduct: http://www.google.com/search?q=Intel(R)%20Turbo%20Boost%20Max%20Technology%203.0%20Driver Intel(R) Turbo Boost Max Technology 3.0 Drivercompany: http://www.google.com/search?q=Intel%20Corporation Intel Corporationdescription: Intel(R) Turbo Boost Max Technology 3.0 DriverBug 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!

[BWint6]

Hi Bahgoogen,

Sorry you are also having the same issue. It sucks. Especially as Intel are now ignoring this thread and not fixing their product.

Anyway, the only way to stop it from happening is to completely disable Intel Turbo Boost.

There isn't another workaround.

Until Intel get their arse in gear thats all we can do.

It fixed the issue on my build and I haven't had any BSOD since.

[CVigu]

thanks for the prompt reply.

I may start my own thread and see if it gets me anywhere. i'll let you know!

[KvanU]

Had to also disable Intel Turbo Boost in the BIOS and kill the software, because those Intelnit.sys bluescreens are fatal crashes, leaving browsers, virtual disks etc etc with corrupted databases and such.

Haven't had these types of 100% power-kill crashes for ages. This can't even be mitigated using UPS or auto-save. It just ruins every app that you had running, including the OS and storage integrity.

Like with all others, my hardware tests all 100% OK, runs stable, on a fairly new Gigabyte GA-X99-designare EX board with the latest BIOS version. RAM is fine, nothing overclocked. The OS is Windows 7 x64, all up to date, stable and secure.

Look, Intel, if you're asking us to pay extra for our chips because they support some weird bonus software speed-boost, of which I find it strange it's not just default (who does NOT want to max out their speed under normal use? Why do we even *need* to have extra ITBM software installed? Can't you just incorporate this stuff with the OS and intel platform drivers?), why don't you first make sure it runs stable?

So, just adding to the (likely) thousands of users that suffer from bad coding on the part of Intel. Not like they don't have enough budget to fix this, I guess they're just lazy, sloppy and frankly rather short-sighted. Trust me, I know. I'm a licensed Certified Information Systems Security Professional, Computer Hacking Forensic Investigator, Digital Forensic Investigator and Certified Ethical Hacker. Intel products have price-tags as if they're top-notch, but they're just as bad, if not worse, than cheap China so-called fake CPUs these days. Worse, because they pretend to be this all-knowing bunch of hardware monopolists, you claim all kinds of authority, but you never really show to deserve any respect in this area.

This all reminds me of the IME debacle we see taking over lots of systems. I luckily never fell for it, because I never understood the use of it, but it turns out even if a corporation is as loaded as Intel, it can't even get their security right. Which also shows during registration of this forum by the way, with its ridiculous password rules and limitations. How unintelligent of you, intel, to ask us to limit our passwords to 15 characters maximum. Who creates these insecure policies? Why do you even get paid so much?

Let us know by email when you've fixed your ITBM drivers.

[KLevu]

I have a BSOD on the last bios i7-7820x

on the old version of the BIOS, I received the BSD only in Photoshop

after the BIOS update, I stopped receiving the BSOD in Photoshop

But today I got the BSD only in the Chrome browser

https://yadi.sk/d/IK2fo2UN3NM3fF https://yadi.sk/d/IK2fo2UN3NM3fF - 093017-12203-01.dmp

0: kd> !analyze -v

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)

An attempt was made to access a pageable (or completely invalid) address at an

interrupt request level (IRQL) that is too high. This is usually

caused by drivers using improper addresses.

If a kernel debugger is available get the stack backtrace.

Arguments:

Arg1: ffff8b09c13a2800, memory referenced

Arg2: 0000000000000002, IRQL

Arg3: 0000000000000001, bitfield :

bit 0 : value 0 = read operation, 1 = write operation

bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)

Arg4: fffff8029c3d387a, address which referenced memory

Debugging Details:

------------------

DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 10.0.15063.608 (WinBuild.160101.0800)

SYSTEM_MANUFACTURER: System manufacturer

SYSTEM_PRODUCT_NAME: System Product Name

SYSTEM_SKU: SKU

SYSTEM_VERSION: System Version

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: 0802

BIOS_DATE: 09/06/2017

BASEBOARD_MANUFACTURER: ASUSTeK COMPUTER INC.

BASEBOARD_PRODUCT: PRIME X299-A

BASEBOARD_VERSION: Rev 1.xx

DUMP_TYPE: 2

DUMP_FILE_ATTRIBUTES: 0x8

Kernel Generated Triage Dump

BUGCHECK_P1: ffff8b09c13a2800

BUGCHECK_P2: 2

BUGCHECK_P3: 1

BUGCHECK_P4: fffff8029c3d387a

WRITE_ADDRESS: fffff8029c5ec358: Unable to get MiVisibleState

Unable to get NonPagedPoolStart

Unable to get NonPagedPoolEnd

Unable to get PagedPoolStart

Unable to get PagedPoolEnd

ffff8b09c13a2800

CURRENT_IRQL: 2

FAULTING_IP:

nt!KeQueryTotalCycleTimeThread+ae49a

fffff802`9c3d387a f0480fba6b4000 lock bts qword ptr [rbx+40h],0

CPU_COUNT: 10

CPU_MHZ: e10

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 55

CPU_STEPPING: 4

CPU_MICROCODE: 6,55,4,0 (F,M,S,R) SIG: 200002B'00000000 (cache) 200002B'00000000 (init)

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: AV

PROCESS_NAME: System

ANALYSIS_SESSION_HOST: SPY

ANALYSIS_SESSION_TIME: 09-30-2017 10:45:13.0684

ANALYSIS_VERSION: 10.0.15063.468 amd64fre

TRAP_FRAME: ffffa201ad8fbea0 -- (.trap 0xffffa201ad8fbea0)

NOTE: The trap frame does not contain all registers.

Some register values may be zeroed or incorrect.

rax=ffff8b09b535b040 rbx=0000000000000000 rcx=ffff8b09c13a27c0

rdx=ffffa201ad8fc220 rsi=0000000000000000 rdi=0000000000000000

rip=fffff8029c3d387a rsp=ffffa201ad8fc030 rbp=ffffa201ad8fc130

r8=ffff8b09b9c42860 r9=0000000000000001 r10=ffffa201ad8fbb70

r11=ffffa201ad8fc140 r12=0000000000000000 r13=0000000000000000

r14=0000000000000000 r15=0000000000000000

iopl=0 nv up ei pl zr na po nc

nt!KeQueryTotalCycleTimeThread+0xae49a:

fffff802`9c3d387a f0480fba6b4000 lock bts qword ptr [rbx+40h],0 ds:00000000`00000040=????????????????

Resetting default scope

LAST_CONTROL_TRANSFER: from fffff8029c3828a9 to fffff8029c377580

STACK_TEXT:

ffffa201`ad8fbd58 fffff802`9c3828a9 : 00000000`0000000a ffff8b09`c13a2800 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx

ffffa201`ad8fbd60 fffff802`9c380e7d : ffffcb0b`d3c91e00 ffffcb0b`c9815040 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69

ffffa201`ad8fbea0 fffff802`9c3d387a : 00000000`00000000 00000000`000000f2 00000000`00000000 00000000`000000f2 : nt!KiPageFault+0x23d

ffffa201`ad8fc030 fffff805`f3546612 : 00200045`00520052 ffffcb0b`daccbad4 ffff8b09`b535b040 fffff805`f3550330 : nt!KeQueryTotalCycleTimeThread+0xae49a

ffffa201`ad8fc160 00200045`00520052 : ffffcb0b`daccbad4 ffff8b09`b535b040 fffff805`f3550330 00000000`00000000 : IntelNit+0x6612

ffffa201`ad8fc168 ffffcb0b`daccbad4 : ffff8b09`b535b040 fffff805`f3550330 00000000`00000000 00000000`00000000 : 0x00200045`00520052

ffffa201`ad8fc170 ffff8b09`b535b040 : fffff805`f3550330 00000000`00000000 00000000`00000000 80000000`c000000d : 0xffffcb0b`daccbad4

ffffa201`ad8fc178 fffff805`f3550330 : 00000000`00000000 00000000`00000000 80000000`c000000d 00000000`00000000 : 0xffff8b09`b535b040

ffffa201`ad8fc180 00000000`00000000 : 00000000`00000000 80000000`c000000d 00000000`00000000 00000000`00000000 : IntelNit+0x10330

STACK_COMMAND: kb

THREAD_SHA1_HASH_MOD_FUNC: a6f5d20972abe84fd01ccdfedd6ebeb3821616f5

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 8f8959082d43e4a23e4a1325e0444839358036e2

THREAD_SHA1_HASH_MOD: ca2516a6fc4100b4741d669c0e97fa276eac24b6

FOLLOWUP_IP:

IntelNit+6612

fffff805`f3546612 ?? ???

SYMBOL_STACK_INDEX: 4

SYMBOL_NAME: IntelNit+6612

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: IntelNit

IMAGE_NAME: IntelNit.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 593ba6bd

BUCKET_ID_FUNC_OFFSET: 6612

FAILURE_BUCKET_ID: AV_IntelNit!unknown_function

BUCKET_ID: AV_IntelNit!unknown_function

PRIMARY_PROBLEM_CLASS: AV_IntelNit!unknown_function

TARGET_TIME: 2017-09-30T07:39:25.000Z

OSBUILD: 15063

OSSERVICEPACK: 608

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 272

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS

<...

[DKova5]

Hello

Hardware

Motherboard: ASUS Rampage V Edition 10, BIOS 1701

CPU: 6950X

RAM: 64GB Corsair CMK64GX4M4A2400C16 (used XMP profile)

OS

Windows 10 x64 Prof (Rus)

During the compilation process (VS С++, /MT key) I got the BSOD.

Dump File (attached) says that the problem in IntelNit.sys.

I not sure that the problem in this driver. May be it is problem with my RAM.

In any case, please look to attached dump file. May be it contains some usefull information

Thanks.

[IPric1]

I feel this thread hasn't received much attention from intel lately, and probably won't therefor. So I'll just give my "me too!" and dump my WinDBG crash dump analysis. If anyone from intel actually wants memory dumps etc, well, there's usually one lurking on my C: drive as of some weeks ago so just holler.

Microsoft (R) Windows Debugger Version 10.0.16299.91 X86

Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Windows\MEMORY.DMP]

Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.

Symbol search path is: srv*

Executable search path is:

Windows 10 Kernel Version 16299 MP (12 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Built by: 16299.15.amd64fre.rs3_release.170928-1534

Machine Name:

Kernel base = 0xfffff800`53a84000 PsLoadedModuleList = 0xfffff800`53deafd0

Debug session time: Mon Feb 12 17:36:48.115 2018 (UTC + 0:00)

System Uptime: 1 days 14:15:28.637

Loading Kernel Symbols

...............................................................

................................................................

.............................................................

Loading User Symbols

Loading unloaded module list

.....................................

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {ffffb8826e5a3740, 2, 1, fffff80053c35022}

*** ERROR: Module load completed but symbols could not be loaded for IntelNit.sys

Probably caused by : IntelNit.sys ( IntelNit+6612 )

Followup: MachineOwner

---------

0: kd> !analyze -v

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)

An attempt was made to access a pageable (or completely invalid) address at an

interrupt request level (IRQL) that is too high. This is usually

caused by drivers using improper addresses.

If a kernel debugger is available get the stack backtrace.

Arguments:

Arg1: ffffb8826e5a3740, memory referenced

Arg2: 0000000000000002, IRQL

Arg3: 0000000000000001, bitfield :

bit 0 : value 0 = read operation, 1 = write operation

bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)

Arg4: fffff80053c35022, address which referenced memory

Debugging Details:

------------------

DUMP_CLASS: 1

DUMP_QUALIFIER: 401

BUILD_VERSION_STRING: 16299.15.amd64fre.rs3_release.170928-1534

DUMP_TYPE: 1

BUGCHECK_P1: ffffb8826e5a3740

BUGCHECK_P2: 2

BUGCHECK_P3: 1

BUGCHECK_P4: fffff80053c35022

WRITE_ADDRESS: ffffb8826e5a3740 Nonpaged pool

CURRENT_IRQL: 2

FAULTING_IP:

nt!KeQueryTotalCycleTimeThread+f36e2

fffff800`53c35022 f0480fba6f4000 lock bts qword ptr [rdi+40h],0

CPU_COUNT: c

CPU_MHZ: e10

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 4f

CPU_STEPPING: 1

CPU_MICROCODE: 6,4f,1,0 (F,M,S,R) SIG: B00001C'00000000 (cache) B00001C'00000000 (init)

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: AV

PROCESS_NAME: System

ANALYSIS_SESSION_HOST: LUNA

ANALYSIS_SESSION_TIME: 02-12-2018 18:15:06.0007

ANALYSIS_VERSION: 10.0.16299.91 x86fre

TRAP_FRAME: ffffe20e2b7a3560 -- (.trap 0xffffe20e2b7a3560)

NOTE: The trap frame does not contain all registers.

Some register values may be zeroed or incorrect.

rax=0000000000000002 rbx=0000000000000000 rcx=ffffb8826e5a3700

rdx=ffffe20e2b7a38e0 rsi=0000000000000000 rdi=0000000000000000

rip=fffff80053c35022 rsp=ffffe20e2b7a36f0 rbp=0000000000000080

r8=ffffb8826a9af220 r9=ffffe20e2b7a3380 r10=ffffe20e2b7a3230

r11=ffffe20e2b7a3800 r12=0000000000000000 r13=0000000000000000

r14=0000000000000000 r15=0000000000000000

iopl=0 nv up ei pl zr na po nc

nt!KeQueryTotalCycleTimeThread+0xf36e2:

fffff800`53c35022 f0480fba6f4000 lock bts qword ptr [rdi+40h],0 ds:00000000`00000040=????????????????

Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80053c0c729 to fffff80053bf96e0

STACK_TEXT:

ffffe20e`2b7a3418 fffff800`53c0c729 : 00000000`0000000a ffffb882`6e5a3740 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx

ffffe20e`2b7a3420 fffff800`53c08859 : ffffb882`41187700 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69

ffffe20e`2b7a3560 fffff800`53c35022 : 00000000`00000001 00000000`000000ab fffff800`52713180 ffff8003`ffffffff : nt!KiPageFault+0x519

ffffe20e`2b7a36f0 fffff80a`174b6612 : 00000000`00000000 00000000`00000000 ffffb882`41187700 00000000`00000080 : nt!KeQueryTotalCycleTimeThread+0xf36e2

ffffe20e`2b7a3820 fffff80a`174b4329 : ffffb882`421b4180 ffffb882`41113c00 ffffb882`6a9af220 fffff80a`174b60c0 : IntelNit+0x6612

ffffe20e`2b7a3920 fffff80a`174c15b7 : ffffb882`421b4180 ffffe20e`2b7a3b48 ffffb882`41187700 fffff80a`00000000 : IntelNit+0x4329

ffffe20e`2b7a39a0 fffff800`53b9b807 : ffffb882`421b4180 fffff80a`174c0330 ffff9e81`5c5ab180 00000425`bd9bbfff : IntelNit+0x115b7

ffffe20e`2b7a3c10 fffff800`53c00e96 : ffff9e81`5c5ab180 ffffb882`41187700 fffff800`53b9b7c0 00000000`00000246 : nt!PspSystemThreadStartup+0x47

ffffe20e`2b7a3c60 00000000`00000000 : ffffe20e`2b7a4000 ffffe20e`2b79e000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16

THREAD_SHA1_HASH_MOD_FUNC: 324ee403a93a7cb797ddfd6880c125be100b6fbb

THREA...

[JElmo]

I'm also getting the BSOD's from this app. Gonna disable it in the bios if it happens again. i've uninstalled the app. it's a shame, I wanted to stay stock speeds and get that nice turbo. Hopefully Intel will address this.

I am running Asus's latest R6E Bios 1401

Here is my https://1drv.ms/t/s!AmbjG5a2Eu2y1iz3O2_uw85EBkH0 Dxdiag: https://1drv.ms/t/s!AmbjG5a2Eu2y1iz3O2_uw85EBkH0 Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.

Operating System Windows 10 Pro 1803

Processor (CPU) Intel® Core™i9 10 Core Processor i9-7900x

Motherboard ASUS® Rampage VI Extreme

Memory (RAM) 32GB GSkill RGB 3200 Mhz

[llope13]

Hello,

This post seems still open...

I have an x99 Gigabyte Board with intel 6950X and have the same issue.

I believe this is happening with different board manufacturers which means the issue is with the CPU (?)

please help, none of the steps described by any Intel rep has worked for me!

Cheerio!

Luis