Processors
Intel® Processors, Tools, and Utilities
14536 Discussions

Intel 7820x Core CPU BSOD's

PKrza
Beginner
12,938 Views

Configuration

Intel i7 7820x + MSI SLI PLUS x299. Last BIOS and drivers.

My problem

When Intel Turbo Bost is activated in BIOS, Photoshop CC 2017, Bridge CC 2017, After Effects CC 2017 crashes imidietly with BSOD.

When I disable Turbo Boost Max 3.0 nothing changes. It is impossible to deinstall Turbo Boost Max 3.0.

But when i deactivate Turbo Boost in BIOS Adobe program works perfect.

Other programs works normal in Turbo Boost.

Any solution for this problem ?

0 Kudos
43 Replies
sshat
Beginner
2,906 Views

Thats awesome! Thanks for the update @Klevunin! So I assume you can run your turbo boost intel software now?

0 Kudos
KLevu
Beginner
2,529 Views

Yes, absolutely right. I have BIOS settings standard. Turboost works and works photoshop.

BIOS 0802 ASUS X299-PRIME-A Update Intel X-series CPU (6-core and above) microcode.

0 Kudos
BCham3
Beginner
2,529 Views

Can confirm. I have updated my Asus x299 Strix E Gaming Mobo and I can use Turbo Boost with Adobe CC with no crashes!

0 Kudos
sshat
Beginner
2,529 Views

wow, thank you Intel and Asus. I can now rock my dual brushes and mixer brushes at obsecenely fast speeds. No lag. This is kinda wild. I've never experienced this before. this is amazing!

0 Kudos
idata
Employee
2,529 Views

Hi fauntailjabuti,

 

 

Thank you for confirming this issue is solved by updating the motherboard BIOS, I am glad this is working for you now.

 

 

Allan J.
0 Kudos
KLevu
Beginner
2,529 Views

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

...

0 Kudos
KLevu
Beginner
2,529 Views

https://yadi.sk/d/uJKuWG2u3NZnch https://yadi.sk/d/uJKuWG2u3NZnch

I again received the BSOD

This happens when watching a video on YouTube

The system is cold and unloaded

When will it be fixed or is it a problem of the processor and it needs to be changed?

0 Kudos
idata
Employee
2,528 Views

Hi klevunin,

 

 

Thank you for the updates however, I do not think this is a processor issue. You are getting BSOD with Chrome and YouTube, this means the Internet browser. You may have an issue with the operating system.

 

 

Allan J.
0 Kudos
idata
Employee
2,529 Views

Hi klevunin,

 

 

I was wondering if you were able to test or run system restore or even reload operating system for registry problems?

 

 

Regards,

 

Allan J.
0 Kudos
KLevu
Beginner
2,529 Views

I have a suspicion about virtual machine virtualbox I created a machine with a working environment, for which I allocated 2 cores. Due to the fact that the 7820x is quite powerful, it does not prevent me from disconnecting it when I do not even work with it. I also do not turn off the computer. He falls asleep himself, and I wake him up. When he wakes up, the virtual machine also wakes up. And I had a few BSOD at that moment. Now I'm disconnecting the virtualbox when I stop working with it, after that there was no problem.

0 Kudos
Mvand4
Novice
2,529 Views

There is no need for AVX offset or disable turbo boost.

the truth here is that motherboard vendors are standard overclocking these cpu's. (don't know if they all do it, but MSI for example does) For the 7820x it should standard overclock all cores to 4GHZ. with a turbo of 4.5GHZ

The problem is that a fair amount of 7820x cpu's cant run stable on these clockspeeds because most mainboards set the auto vcore setting too low. So not enough juice to feed the cpu resulting in BSOD such as WHEA uncorrectable.

So until mainboard vendors come up with a better bios version. You have to manually set a Vcore value to make it stable.

You can start of setting the Vcore at a basic 1.2V and look if it runs stable. (it should be stable at 1.2V)

If it does you can lower the vcore with small steps (0.005V) until it becomes unstable. Recommended is setting it to adaptive mode so it does not run 1.2v trough the CPU all the time.

You can choose the CPU frequencies to your need but keep in mind that higher freqs needs higher vcore voltages and raising temps.

sshat
Beginner
2,528 Views

Hey thanks @Mark81!

This was tremendously helpful and an immense insight. I have a system I put a lot of money into with what I thought were top grade parts, but was feeling like something was not right. After all, I updated to latest bios, combed forums and pretty much everything else I could read about. Then your valuable post came through and I can't thank you enough. The system is really purring now.

I hope you reap a lot of karma points for your help!

Faunt

0 Kudos
Mvand4
Novice
2,529 Views

Hey @Faunt

Great too hear it worked for you! Can you tell me which motherboard you have? And at what voltage and frequency are you ended up with?

Thnx, Mark

0 Kudos
sshat
Beginner
2,529 Views

Hi mark,

Increasing the voltage has seemed to be a step in the right direction for sure. I can see the whole machine runs more stably.

it seems to have worked for me and solved some issues, yet others persist. i don't understand the abnormal behavior. Seems like the cpu is working too hard to relatively simple tasks or no tasks at all. I'm going to migrate this conversation to appropriate channels.

heres what I'm running:

Voltage: 1.25 vo

CPU: I7-7820X @ 3.6ghz

M/B: Asus Prime X299 Deluxe

RAM: G.SKILL, TridentZ, Series 64GB (4x16GB sticks) DDR4, SDRAM 3600

SSD: INTEL SSD 750 Series Connected through PCIE

VGA: Asus GeForce 1080Ti

CPU Cooler: Corsair H100 V2 Extreme

PSU: Corsair RM 1000i

0 Kudos
Mvand4
Novice
2,529 Views

wow 1.25v is way overkill for only 3.6GHZ. You can at least run 4.6 or 4.7GHZ with that voltage.

That said. Can you check at which setting your energy power profile is set to?. it should been set to balanced.

0 Kudos
JSima1
Novice
2,529 Views

Hi Mark, did you found that solution on Puget System Website (https://www.pugetsystems.com/labs/support-hardware/WHEA-UNCORRECTABLE-ERROR-on-Gigabyte-x299-and-Skylake-X-SOLVED-1042/ https://www.pugetsystems.com/labs/support-hardware/WHEA-UNCORRECTABLE-ERROR-on-Gigabyte-x299-and-Skylake-X-SOLVED-1042/ _?

I see many posts here about the exact same problem and Intel doesn't seem to be aware of the problem and solution.

So I made that post and I hope Intel can send a note to all their customers about this, I lost so much time with that problem and the solution is so easy but we just need to know abou it!:

In my case I also wanted to overclock a bit more and when doing so the BSOD were back so I ended up also using the avx offset and now I have no more blue screen. Or should I try to increase the voltage from 1200mV instead of avx offset?

My system:

Alienware Area 51 R4

i9-7980XE

windows 10 1709

64GB ram 2666

water cooling

2 x 1080ti zotac mini

os on 512GB samsun evo pro on board m.2

2x samsung evo pro 1TB m.2 in raid 0 on Highpoint rocket raid pcie card

1500W psu

Mvand4
Novice
2,529 Views

yes that puget article was one of my sources , Strob.

You should only AVX offset for temperature reasons and not BSOD's. I think you should raise your vcore voltage a bit. What freqs are you on?? Mine cant get past 4.7GHZ without delidding. And i have an AVX offset only for AVX512

0 Kudos
JSima1
Novice
2,529 Views

Why did you set only avx512 (what's the difference between both avx?)

Here is what my frequencies look when I am rendering. I find weird that not all my core seems to be affected by turbo.I set those settings:

OC\Mail Box Configuration\Processor

Core Max OC ratio 80

OC\CPU Power Management Configuration

Turbo Modo Enabled

Long duration power limit: 240

Long duration power limit: 1

Short duration power limit: 250

Short duration power limit: 1

Core Ratio Limit 1: 42

Core count number: 18

OC\Overvoltage

vccin voltage: 1830

memory voltage: 1200

And both avx offset to 5

0 Kudos
sshat
Beginner
2,529 Views

Just curious, Strob, but what kind of temperatures are you seeing when rendering? I guess I'm asking because mine skyrocket to max temperatures and its doesn't seem right?

0 Kudos
JSima1
Novice
2,529 Views

It stays pretty cool (50 to 60 depending on the core)

Last night I had another blue screen during rendering. So I will try without the AVX offset and increase the voltage a bit.

0 Kudos
Mvand4
Novice
2,456 Views

Hi strob,

AVX512 is the most demanding instruction your CPU will ever face. System power draw and temps will go trough the roof. Thats why i set a avx512 offset. With my 8 core @ 4.7GHZ, temps are reaching very fast 90C

I think your cpu is heavily throttling. 4.6 GHZ on a 18 core is way to high. Especially on a non delidded CPU. What motherboard do you have??

You can check if your cpu is throttling with aida64 and choose system stability check.

0 Kudos
Reply