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!

[idata]

Hello Claire_Monkey,

Thank you for contacting the Intel community. I'm sorry for the issue you have experience with the Intel® Turbo Boost 3.0. By any chance, have you checked if this option is available on your motherboard BIOS? Also make sure you are running the latest BIOS version for your motherboard. If that does not work.

1. Uninstalling previous version of Driver/Application and reinstall the new version.
2. Go to Windows Control Panel > Programs > Uninstall a Program, and uninstall any previous version of Intel® Turbo Boost Max Technology 3.0 software.
3. Reboot the system.
4. To install the new version unzip the TBMT Driver/Control Panel Application package.
5. In Windows Explorer, right-click on INF file and select Install.
6. After successful installation, reboot the system.

Please let me know how it goes. Regards, Ivan U.

[CMees]

Apologies for having left this so long. I thought it was fixed and had managed to go a whole month without a crash. Then this-morning it happened again.

So since then I have updated my bios to the latest version. I went from 1504 up to 1701 from: https://www.asus.com/uk/Motherboards/X99-E/HelpDesk_Download/ https://www.asus.com/uk/Motherboards/X99-E/HelpDesk_Download/

I also uninstalled and reinstalled the Turbo Boost Max driver from: https://downloadcenter.intel.com/download/26103/Intel-Turbo-Boost-Max-Technology-3-0 Download Intel® Turbo Boost Max Technology 3.0

Although it did already list that I was on that version.

And a mere 4 hours since my last crash, I crash again.

It's always the IRQL_NOT_LESS_OR_EQUAL BSOD

The Turbo Boot Max service is running, though I had it disabled until after the earlier crash today. The driver said it was installed on 20th within programs and features when I went to uninstall it. So Windows must have done it. I did find if I tried to uninstall it, it would immediately ask me to restart, and if I did restart, it would be reinstalled when I looked again.

[idata]

Hello ,I'm following on this post to ask you if your issue has been resolved or if you need further assistance.Regards,Ivan.

[idata]

Hello Claire_Monkey,

We have tried the Intel® Turbo Boost Max Technology but haven't experience any BSOD. I don't believe this issue is caused by the Try running the system I safe mode, Intel® Turbo Boost Max Technology, I this point I suggest you to run Windows update, to reinstall all drivers. An incorrectly installed or buggy driver can lead to crashes. Download the latest drivers for your computer's hardware from your computer manufacturer's website and install them — this may fix BSODs caused by driver problems. Blue screens are generally caused by problems with your computer's hardware or issues with its hardware driver software. Sometimes, they can be caused by issues with low-level software running in the Windows kernel. Regular apps usually won't be able to cause blue screens. If an app crashes, it will do so without taking the operating system out with it. If your system was working fine before try to do a system restore to a date where the system was working fine. If that does not solve it.Check for Hardware Problems: Blue screens can be caused by faulty hardware in your computer. Try testing your computer's memory for errors and checking its temperature to ensure that it isn't overheating. If that fails, you might need to test other hardware components. If nothing works, Reinstall Windows: Resetting Windows—or performing a clean install—is the nuclear option. It will blow away your existing system software, replacing it with a fresh Windows system. If your computer continues to blue screen after this, you likely have a hardware problem.

A computer in proper working state shouldn't blue-screen at all, but no software or hardware is perfect. Even a properly functioning computer may blue screen on rare occasions for no apparent reason—possibly as the result of rare driver bugs or hardware issues. If your computer is regularly blue-screening, you have a problem. If you encounter a blue screen once every two years, don't worry about it.

I hope this can help.Regards,

Ivan U.

[CMees]

As stated in my original message, the dump's are stating that it is caused my Turbo boost.

I always keep my Windows up-to-date and my drivers are all up to date. This has been an ongoing problem, continually stating Turbo boost as the issue and has not changed no matter what I have updated.

I have been receiving these BSOD before and since the last fresh install of Windows, so System Restore is not an option for me. I have tested my memory, there were no errors. This computer is only a year old, and the boot drive was replaced 2 months ago when updating the bios for this very problem killed it.

My crash analyser says its unlikely to be hardware and pinpoints Turbo Boost as the problem, why would it say that if it had nothing to do with it?

Is there any way to actually not use Turbo Boost at all? So I can just see if it works without it?

[idata]

Hello Claire_Monkey,

Turbo boost on your processor you can disable in the BIOS but it depends on your motherboard BIOS if this option is enabled or not. To uninstall the Intel® Turbo Boost Max Technology 3.0 you can do it from the control panel, Go to Windows Control Panel > Programs > Uninstall a Program, and uninstall any version of Intel® Turbo Boost Max Technology 3.0 software.Reboot the system. Regards, Ivan U.

[CMees]

As stated in my first post, my motherboard is the ASUS® X99-E. Will I be able to disable it on that? Can you give any guidance to what setting I'm looking for?

It crashed again last night.

As stated in my previous message, when I try to uninstall the driver now, it automatically re-installs on restart. I'm not sure what I can do about that? I'm fairly certain I did get it uninstalled before and that's why I didn't have a crash for a month, but now it doesn't seem to be an option.

[idata]

To check the turbo boost in the BIOS, you will need to contact ASUS for them to guide you in the BIOS how to disable it or to enable it if it is not enabled and perhaps for that reason you are getting the BSOD.

You should be able to contact ASUS here:https://www.asus.com/support/ https://www.asus.com/support/NOTE: This link is being offered for your convenience and should not be viewed as an endorsement by Intel of the content, products, or services offered there. Please let me know how it goes. Ivan U.

[idata]

Hello ,I'm following on this post to ask you if your issue has been resolved or if you need further assistance.Regards,Ivan.

[JKrie]

I too am getting this BSOD. Twice so far this morning and generally about once or twice a week prior. The machine is only a few months old.

Here's the bugcheck info from WinDbg:

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: ffff988ef2ac1840, 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: fffff8036c31bd19, address which referenced memory Debugging Details: ------------------ *** ERROR: Module load completed but symbols could not be loaded for IntelNit.sys WRITE_ADDRESS: unable to get nt!MmSpecialPoolStart unable to get nt!MmSpecialPoolEnd unable to get nt!MmPagedPoolEnd unable to get nt!MmNonPagedPoolStart unable to get nt!MmSizeOfNonPagedPoolInBytes ffff988ef2ac1840 CURRENT_IRQL: 2 FAULTING_IP: nt!KiAcquireThreadLockRaiseToDpc+1d fffff803`6c31bd19 f0480fba6b4000 lock bts qword ptr [rbx+40h],0 DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT BUGCHECK_STR: AV PROCESS_NAME: System ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre TRAP_FRAME: ffffd8008f991530 -- (.trap 0xffffd8008f991530) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000002 rdx=ffffd8008f991720 rsi=0000000000000000 rdi=0000000000000000 rip=fffff8036c31bd19 rsp=ffffd8008f9916c0 rbp=ffffd8008f9917f0 r8=ffff988ef1d4d7b0 r9=0000000000000001 r10=ffffd8008f991230 r11=fffff8036c24e100 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl zr na po nc nt!KiAcquireThreadLockRaiseToDpc+0x1d: fffff803`6c31bd19 f0480fba6b4000 lock bts qword ptr [rbx+40h],0 ds:00000000`00000040=???????????????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff8036c3d0b29 to fffff8036c3c5960 STACK_TEXT: ffffd800`8f9913e8 fffff803`6c3d0b29 : 00000000`0000000a ffff988e`f2ac1840 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx ffffd800`8f9913f0 fffff803`6c3cf107 : ffff988e`ec791040 00000000`00000000 00000000`00001044 00000000`0008bc60 : nt!KiBugCheckDispatch+0x69 ffffd800`8f991530 fffff803`6c31bd19 : 00000000`00000000 ffff988e`fa30f080 ffffd800`8f9918e0 ffffd800`8f9917f0 : nt!KiPageFault+0x247 ffffd800`8f9916c0 fffff803`6c403ef8 : ffffd5ea`00000000 00000000`000000b7 ffff70ba`abc56d19 fffff803`6c3ca7ef : nt!KiAcquireThreadLockRaiseToDpc+0x1d ffffd800`8f9916f0 fffff805`9e6c660a : 00000000`00000000 00000000`00000000 fffff805`9e6d0328 00000000`00000000 : nt!KeQueryTotalCycleTimeThread+0xba2e4 ffffd800`8f991820 fffff805`9e6c4329 : ffff988e`ec361180 ffff988e`ec794330 ffff988e`f1d4d7b0 fffff805`9e6c60c0 : IntelNit+0x660a ffffd800`8f991920 fffff805`9e6d15af : ffff988e`ec361180 ffffd800`8f991b48 ffff988e`ec791040 00000000`00000000 : IntelNit+0x4329 ffffd800`8f9919a0 fffff803`6c32c965 : ffff988e`ec361180 fffff803`6c3cad4f 00000000`0185e380 ffff988e`ec791040 : IntelNit+0x115af ffffd800`8f991c10 fffff803`6c3cae26 : fffff803`6c5b2180 ffff988e`ec791040 fffff803`6c32c924 00000000`00000000 : nt!PspSystemThreadStartup+0x41 ffffd800`8f991c60 00000000`00000000 : ffffd800`8f992000 ffffd800`8f98c000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16 STACK_COMMAND: kb FOLLOWUP_IP: IntelNit+660a fffff805`9e6c660a 48898424b8000000 mov qword ptr [rsp+0B8h],rax SYMBOL_STACK_INDEX: 5 SYMBOL_NAME: IntelNit+660a FOLLOWUP_NAME: MachineOwner MODULE_NAME: IntelNit IMAGE_NAME: IntelNit.sys DEBUG_FLR_IMAGE_TIMESTAMP: 581212a0 FAILURE_BUCKET_ID: AV_IntelNit+660a BUCKET_ID: AV_IntelNit+660a ANALYSIS_SOURCE: KM FAILURE_ID_HASH_STRING: km:av_intelnit+660a FAILURE_ID_HASH: {490299d6-07ec-66e2-835f-a328cc511c1b} Followup: MachineOwner ---------

[JKrie]

Just got it again, this time as a DPC_WATCHDOG_VIOLATION. This is on the latest version of IntelNit.sys available on your website (1.0.0.1031 dated 2 May 2017)

WinDbg reports:

Probably caused by : IntelNit.sys ( IntelNit+660a )

0: kd> !analyze -v

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

* *

* Bugcheck Analysis *

* *

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

DPC_WATCHDOG_VIOLATION (133)

The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL

or above.

Arguments:

Arg1: 0000000000000001, The system cumulatively spent an extended period of time at

DISPATCH_LEVEL or above. The offending component can usually be

identified with a stack trace.

Arg2: 0000000000001e00, The watchdog period.

Arg3: fffff800b2fbe540

Arg4: 0000000000000000

Debugging Details:

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

FAULTING_MODULE: fffff800b2c1f000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 58e34870

DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0x133

CURRENT_IRQL: 0

ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre

LAST_CONTROL_TRANSFER: from fffff800b2c41fda to fffff800b2d6e870

STACK_TEXT:

fffff800`b4824d88 fffff800`b2c41fda : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff800`b2fbe540 : nt!KeBugCheckEx

fffff800`b4824d90 fffff800`b2c3ffc9 : 00021d25`ddf4265c 00000000`00000000 00000000`00000000 fffff780`00000320 : nt!KeClockInterruptNotify+0x247a

fffff800`b4824df0 fffff800`b3438366 : ffffb000`37926500 fffff800`b34833e0 00000000`00000002 00021d25`ddf402ea : nt!KeClockInterruptNotify+0x469

fffff800`b4824f40 fffff800`b2c32c26 : fffff800`b34833e0 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalpTimerClockInterrupt+0x56

fffff800`b4824f70 fffff800`b2d6feea : ffffb000`37926580 ffffe60a`2c588600 00000000`00000145 ffffb000`364a2d40 : nt!KeSetSystemGroupAffinityThread+0x35e

fffff800`b4824fb0 fffff800`b2d70337 : ffffe11c`44d4e158 ffffe60a`2c588600 ffffe11c`44d4e168 fffff800`b2d703be : nt!KeSynchronizeExecution+0x78a

ffffb000`37926500 fffff800`b2c816c8 : ffffffff`ffffffd1 fffff800`b2cc4b72 00000000`00000010 00000000`00000286 : nt!KeSynchronizeExecution+0xbd7

ffffb000`37926690 fffff800`b2cc4b72 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff800`b2d43294 : nt!ExAcquireSpinLockExclusive+0x128

ffffb000`379266c0 fffff800`b2dacd90 : fffff800`25cfd2b2 00000000`00000145 00000000`00000000 00000000`00000000 : nt!KeUnstackDetachProcess+0x1ab6

ffffb000`379266f0 fffff802`04b6660a : 00000000`00000006 00000008`00000000 fffff802`04b70328 00000000`00000000 : nt!memset+0x32310

ffffb000`37926820 fffff802`04b64329 : ffffe60a`15e21180 ffffe60a`15e91350 ffffe60a`240b90b0 00000000`00000000 : IntelNit+0x660a

ffffb000`37926920 fffff802`04b715af : ffffe60a`15e21180 ffffb000`37926b48 ffffe60a`15e95040 00000000`00000000 : IntelNit+0x4329

ffffb000`379269a0 fffff800`b2cd57c5 : ffffe60a`15e21180 fffff800`b2d73c5f 00000000`016a323f ffffe60a`15e95040 : IntelNit+0x115af

ffffb000`37926c10 fffff800`b2d73d36 : ffffb000`3649c180 ffffe60a`15e95040 fffff800`b2cd5784 00000000`00000000 : nt!PsGetCurrentProcessId+0x55

ffffb000`37926c60 00000000`00000000 : ffffb000`37927000 ffffb000`37921000 00000000`00000000 00000000`00000000 : nt!KeSynchronizeExecution+0x45d6

STACK_COMMAND: kb

FOLLOWUP_IP:

IntelNit+660a

fffff802`04b6660a 48898424b8000000 mov qword ptr [rsp+0B8h],rax

SYMBOL_STACK_INDEX: a

SYMBOL_NAME: IntelNit+660a

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: IntelNit

IMAGE_NAME: IntelNit.sys

BUCKET_ID: WRONG_SYMBOLS

FAILURE_BUCKET_ID: WRONG_SYMBOLS

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:wrong_symbols

FAILURE_ID_HASH: {70b057e8-2462-896f-28e7-ac72d4d365f8}

Followup: MachineOwner

[idata]

You are getting a watchdog violation problem and when this happens you will most likely get a BSOD; however, you can try disabling ITBM in the BIOS to see if you keep getting the problem or contact you system manufacturer to get a BIOS update.

If that does not work and your system worked fine before, you can try with a system restore to an earlier time when it was better working, if that does not work then this is most likely an issue with the operating system registry and you will need to reinstall the operating system. I saying it because we have tested the ITBM and it works flawless, no BSOD or anything else.

Regards,

Ivan U.

[JKrie]

Thanks for the response Ivan. This is a relatively new machine and it has always had this problem. It almost always occurs when i am building C++ code using Xoreax Incredibuild and syncing data files to my local disk with Perforce's P4V tool. I generally get a IRQL_NOT_LESS_OR_EQUAL BSOD but occasionally get the watchdog violation. It's always "probably caused by IntelNit.sys" according to WinDbg when do !analyze -v on the resulting MEMORY.DMP from the kernel.

I've tried turning off Turbo Mode in the BIOS settings (didn't find anything that specifically refers to ITBM) and have also changed my Windows power profile to max CPU at 99%. I'll let you know if it happens again. It's generally pretty terrible when it happens; I have to force re-sync the files from Perforce and do a full clean/rebuild due to corrupted file state from a non-clean shutdown.

[idata]

Thank you for the information, hopefully you will not get the BSOD if you disable the ITBM in the BIOS and if the problem persists, most likely is with something else on your system, another application that is not running properly and it needs to be reinstalled.

Regards, Ivan U.

[BWint6]

I am getting the exact same issue on my computer.

It seems to be getting worse and worse now, whereby I am getting crashes on a daily basis.

I can't uninstall Turbo Boost because each time I restart my computer it reinstalls itself automatically.

I have crash logs showing that it is Turbo Boost causing the issue

On Tue 8/1/2017 21:56:04 your computer crashed

crash dump file: C:\WINDOWS\memory.dmpThis was probably caused by the following module: http://www.google.com/search?q=intelnit.sys intelnit.sys (IntelNit+0x6612) Bugcheck code: 0xA (0xFFFFA909152E5800, 0x2, 0x1, 0xFFFFF8025804E87A)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).

I have tried to contact Intel about this and they have not been very helpful - giving generic responses, such as 'Do a system restore to when it was working' - I can't do this because it was never working

Windows update installed this turbo boost software without my consent and is now causing me these constant issues

How can I disable this software and completely remove it from my system?

[idata]

Hello bryce_w,

In this case you will need to disable it in the BIOS, if that does not work you will need to contact your motherboard manufacturer to get tips how to do it. Regards, Ivan U.

[JKrie]

Bryce, I'm kind of curious to see what kind of motherboard you have? I have the ASUS X99-A II. I've disabled the Intel Turbo Boost Max 3.0 from the BIOS and so far, so good.

IntelCorporation/Ivan U., if people are reporting this issue with multiple different motherboards, and Windows Kernel debugging tools are indicating that your IntelNit.sys driver is the likely culprit, it might be time to take these crash dumps back to the software engineers. As a software developer myself, it's likely that something is going on in the driver.

[BWint6]

Thanks Ivan - I will try this and see if it works.

Thanks for your advice jkriegshauser - I am using a MSI X99A SLI KRAIT EDITION LGA 2011-v3 Intel X99 SATA 6Gb/s USB 3.1 USB 3.0 ATX Intel Motherboard

I agree with you - it seems like a lot of people are having this BSOD issue on different MOBO's, so the driver can be resolved.

[idata]

Thank you for the information, in order to further investigate, would please attach your system information. You can use the Intel SSU (System Support Utility) to get the system information:

https://downloadcenter.intel.com/download/25293/Intel-System-Support-Utility https://downloadcenter.intel.com/download/25293/Intel-System-Support-Utility: Download Intel® System Support Utility

1. Download the utility
2. Run the exe and select 'Scan'
3. Save and include as an attachment in the Intel Community Forum

Regards, Ivan U.

[JKrie]

I've done this, but I'm not posting this information publicly to the forum. Is there a way to privately send it to you IntelCorporation