Question Intel(R) Turbo boost crashing/bsod-ing PC

[Austenofaustens]

Hi guys, I am currently running an i7-8700 at 3.2gHz - recently it came with an upgrade to my pc, but it keeps on causing my PC to bsod with multiple different stopcodes and other times freezing under normal load. After fiddling online as well as the BIOS I found that disabling the Intel Turbo Boost under the frequency settings solved this, but I just want to know, since it’s turned on by default, is this supposed to happen? What can I do for it to stop crashing under Turbo Boost?

Currently using 750W power for it.

Examples of stopcodes:
APC INDEX MISMATCH
DPC WATCHDOG VIOLATION
MACHINE CHECK EXCEPTION
WHEA UNCORRECTABLE ERROR

 

[helpstar]

No, it´s definitely not supposed to happen

Which motherboard are you using? Which BIOS version is on currently it?

Which windows version is it?

Did you install a new motherboard as well?

How hot is the CPU getting? Use coretemp (without installing the extra bloatware) for this

get into windows device manager and uninstall all processors manually, after that, restart windows
similar to this, but only unsinatll the :
https://www.drivethelife.com/uploadfiles/20180227/device-manager-uninstall-device.png

 

[Austenofaustens]

No, it´s definitely not supposed to happen

Which motherboard are you using? Which BIOS version is on currently it?

Which windows version is it?

Did you install a new motherboard as well?

How hot is the CPU getting? Use coretemp (without installing the extra bloatware) for this

get into windows device manager and uninstall all processors manually, after that, restart windows
similar to this, but only unsinatll the :
https://www.drivethelife.com/uploadfiles/20180227/device-manager-uninstall-device.png

Motherboard: GIGABYTE H310M-DS2 (it's also new)
BIOS Version/Date American Megatrends Inc. F4, 6/14/2018
Windows version: Version 10.0.17763 Build 17763
Core temps are 44~48C under 10-20% load.

Will try this later today, will reply with the result

 

[Austenofaustens]

Motherboard: GIGABYTE H310M-DS2 (it's also new)
BIOS Version/Date American Megatrends Inc. F4, 6/14/2018
Windows version: Version 10.0.17763 Build 17763
Core temps are 44~48C under 10-20% load.

Will try this later today, will reply with the result

BSOD happens again.

 

[SkyNetRising]

Please list full specs of your pc including

ram (model name),​

cpu cooler (is it stock cooler?),​

PSU (model name),​

GPU (model name).​

​

It's better to have all this info in your first post.

 

[Austenofaustens]

Please list full specs of your pc including

ram (model name),​

cpu cooler (is it stock cooler?),​

PSU (model name),​

GPU (model name).​

​

It's better to have all this info in your first post.

Windows 10 Home 64-bit
Intel Core i7-8700 CPU @ 3.20GHz
Crucial 16GB DDR4-2666 UDIMM
Stock cpu cooler (Intel)
Vector G750 CPA-0750GFV-U51
NVIDIA GeForce GTX 1060 3GB (Zotac GTX 1060 AMP! Edition 3GB)
Toshiba DT01ACA200 2TB SATA HDD
Tecware Edge Case

Apologies if i missed out anything.

 

[SkyNetRising]

You may need to update BIOS of your board.
https://www.gigabyte.com/Motherboard/H310M-DS2-rev-10#support-dl-bios

You said, you upgraded system recently. Did you reinstall windows also?

 

[gingerrankin]

What have you updated? If you have updated the CPU, you should enter in the BIOS and "load optimized values" or even perform a clear cmos.

If the error was already happening before changing the CPU, the RAM is probably the culprit. Try to pass a memory test program MEMTEST64 or similar. If you have two sticks try to start with only one of the two .

 

[Austenofaustens]

You may need to update BIOS of your board.
https://www.gigabyte.com/Motherboard/H310M-DS2-rev-10#support-dl-bios

You said, you upgraded system recently. Did you reinstall windows also?

This version of windows was kept on my C drive and I upgraded everything but that, so I didn't re-install windows.
I updated the BIOS with the above link, and the same problem occurs.

What have you updated? If you have updated the CPU, you should enter in the BIOS and "load optimized values" or even perform a clear cmos.

If the error was already happening before changing the CPU, the RAM is probably the culprit. Try to pass a memory test program MEMTEST64 or similar. If you have two sticks try to start with only one of the two .

I reset BIOS and loaded optimized values, but problem still persists. Running memtest64 for 3 hours came back with no problems. I will try memtest86 tonight and see if there's anything new

 

[SkyNetRising]

This version of windows was kept on my C drive and I upgraded everything but that, so I didn't re-install windows.

Then reinstall windows.

 

[Austenofaustens]

Then reinstall windows.

Reinstalled windows only then ran memtest86+, passed 48/48 (on one 16gb stick), and later while running games got DPC_WATCHDOG_VIOLATION.

 

[Austenofaustens]

this is the dump from one of the recent crashes.

Spoiler: crashdump

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 17763 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 17763.1.amd64fre.rs5_release.180914-1434
Machine Name:
Kernel base = 0xfffff80545caa000 PsLoadedModuleList = 0xfffff805460c59f0
Debug session time: Thu Mar 21 16:53:09.883 2019 (UTC + 8:00)
System Uptime: 0 days 19:05:28.605
Loading Kernel Symbols
...............................................................
................................................................
...................................................
Loading User Symbols

Loading unloaded module list
...............
***

• *
• Bugcheck Analysis *
• *

***

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, ffffc00ba6ed5028, b2000000, 30005}

Probably caused by : GenuineIntel

Followup: MachineOwner
---------

3: kd> !analyze -v
***

• *
• Bugcheck Analysis *
• *

***

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffffc00ba6ed5028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000b2000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000030005, Low order 32-bits of the MCi_STATUS value.

Debugging Details:
------------------


KEY_VALUES_STRING: 1


STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 401

BUILD_VERSION_STRING: 17763.1.amd64fre.rs5_release.180914-1434

SYSTEM_MANUFACTURER: Gigabyte Technology Co., Ltd.

SYSTEM_PRODUCT_NAME: H310M DS2

SYSTEM_SKU: Default string

SYSTEM_VERSION: Default string

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: F12

BIOS_DATE: 01/16/2019

BASEBOARD_MANUFACTURER: Gigabyte Technology Co., Ltd.

BASEBOARD_PRODUCT: H310M DS2

BASEBOARD_VERSION: x.x

DUMP_TYPE: 1

BUGCHECK_P1: 0

BUGCHECK_P2: ffffc00ba6ed5028

BUGCHECK_P3: b2000000

BUGCHECK_P4: 30005

BUGCHECK_STR: 0x124_GenuineIntel

CPU_COUNT: c

CPU_MHZ: c78

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 9e

CPU_STEPPING: a

CPU_MICROCODE: 6,9e,a,0 (F,M,S,R) SIG: AA'00000000 (cache) AA'00000000 (init)

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: f

ANALYSIS_SESSION_HOST: DESKTOP-LAR2VVL

ANALYSIS_SESSION_TIME: 03-21-2019 17:15:06.0854

ANALYSIS_VERSION: 10.0.17763.1 x86fre

STACK_TEXT:
ffff92814c72ec88 fffff80545c54667 : 0000000000000124 0000000000000000 ffffc00ba6ed5028 00000000b2000000 : nt!KeBugCheckEx
ffff92814c72ec90 fffff8010620146b : ffffc00ba6ed5028 ffffc00b9dedad30 ffffc00b9dedad30 ffffc00b9dedad30 : hal!HalBugCheckSystem+0xd7
ffff92814c72ecd0 fffff80545fc85ae : ffffc00ba6ed5028 0000000000000000 ffffc00b9dedad30 ffffc00b9dedad30 : PSHED!PshedBugCheckSystem+0xb
ffff92814c72ed00 fffff80545c55f59 : 0000000000000728 0000000000000003 0000000000000000 0000000000000000 : nt!WheaReportHwError+0x25e
ffff92814c72ed60 fffff80545c562de : 0000000000000010 ffffc00b9dedad80 ffff92814c72ef08 0000000000000003 : hal!HalpMcaReportError+0x5d
ffff92814c72eeb0 fffff80545c561ba : ffffc00b9d8dd260 0000000000000001 0000000000000000 0000000000000000 : hal!HalpMceHandlerCore+0xf2
ffff92814c72ef00 fffff80545c56424 : 000000000000000c 0000000000000001 0000000000000000 0000000000000000 : hal!HalpMceHandler+0xda
ffff92814c72ef40 fffff80545c5569c : 0000000000000000 ffff92814c72f1d0 0000000000000000 0000000000000000 : hal!HalpMceHandlerWithRendezvous+0xd4
ffff92814c72ef70 fffff80545c566c7 : ffffc00b9d8dd260 0000000000000000 0000000000000000 0000000000000000 : hal!HalpHandleMachineCheck+0x5c
ffff92814c72efa0 fffff80545f3616b : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : hal!HalHandleMcheck+0x37
ffff92814c72efd0 fffff80545e6bf7a : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiHandleMcheck+0xb
ffff92814c72f000 fffff80545e6bc60 : ffff928100000000 fffff80545e6bb9d ffff92814c68f180 0000000000000000 : nt!KxMcheckAbort+0x7a
ffff92814c72f140 fffff8010de0136f : fffff8010de01404 0000000000000000 ffffc00ba84c90f0 ffff92814c723180 : nt!KiMcheckAbort+0x260
ffff828575e4f6a8 fffff8010de01404 : 0000000000000000 ffffc00ba84c90f0 ffff92814c723180 ffffc00ba84c9000 : intelppm!MWaitIdle+0x1f
ffff828575e4f6b0 fffff80545dd024b : 0000000000000000 0000539300000086 0000000000000000 000000000000004e : intelppm!AcpiCStateIdleExecute+0x24
ffff828575e4f6e0 fffff80545dcf9ff : 0000000000000000 0000000000000002 0000000000000000 0000000000000008 : nt!PpmIdleExecuteTransition+0x6bb
ffff828575e4fa00 fffff80545e60fcc : 0000000000000000 ffff92814c723180 ffff92814c733300 ffffc00bacdd0080 : nt!PoIdle+0x33f
ffff828575e4fb60 0000000000000000 : ffff828575e50000 ffff828575e49000 0000000000000000 0000000000000000 : nt!KiIdleLoop+0x2c


THREAD_SHA1_HASH_MOD_FUNC: f7c0b1d09843687a307ffaac768aa7455b6fc4a8

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: ebe6601608dc2d9b467d46c5688ba140d351cbc0

THREAD_SHA1_HASH_MOD: 915542d5ee9cb0daf7a7a78c82e940b2426a2770

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: GenuineIntel

IMAGE_NAME: GenuineIntel

DEBUG_FLR_IMAGE_TIMESTAMP: 0

STACK_COMMAND: .thread ; .cxr ; kb

FAILURE_BUCKET_ID: 0x124_GenuineIntel_PROCESSOR_MAE

BUCKET_ID: 0x124_GenuineIntel_PROCESSOR_MAE

PRIMARY_PROBLEM_CLASS: 0x124_GenuineIntel_PROCESSOR_MAE

TARGET_TIME: 2019-03-21T08:53:09.000Z

OSBUILD: 17763

OSSERVICEPACK: 0

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 784

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS Personal

OS_LOCALE:

USER_LCID: 0

OSBUILD_TIMESTAMP: unknown_date

BUILDDATESTAMP_STR: 180914-1434

BUILDLAB_STR: rs5_release

BUILDOSVER_STR: 10.0.17763.1.amd64fre.rs5_release.180914-1434

ANALYSIS_SESSION_ELAPSED_TIME: 81b

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x124_genuineintel_processor_mae

FAILURE_ID_HASH: {7c95de0c-286c-8226-45c2-422b4de101d6}

Followup: MachineOwner
---------

 

[pomuso]

Hello,
I have the same issue, Windows 10 DPC_WATCHDOG_VIOLATION BSOD ,
Hangs/Freezing.
I changed procesor by i5-8400 during 3 weeks and work fine, then return to i7-8700 and crash at least twice a day.

 

[mdd1963]

Chipset drivers from mainboard manufacturer installed?

CMOS cleared between CPU changes? CPU correctly identified/detected within device manager for increased thread count, etc?

(Windows does not always take kindly to CPU swaps, as even CPU swaps involve different drivers being installed, etc...)