-
Home
-
News
- Beginners Guide: How to Fix Genuineintel.sys BSOD Win 10/11
Beginners Guide: How to Fix Genuineintel.sys BSOD Win 10/11
By Aurelie | Follow |
Last Updated
Blue Screen of Death (BSOD), also known as Windows stop code or fatal error, is designed to protect your computer from further complications when it detects a critical error. This post from MiniTool will delve into how to cope with Genuineintel.sys BSOD with several feasible solutions.
Recently, some users claimed on Microsoft Answers Forum that they have encountered Genuineintel.sys BSOD randomly. Like other .sys files, the Genuineintel.sys file also contains device drivers and hardware configuration for the system.
Genuineintel.sys BSOD indicates the Genuineintel.sys file is checking if Wi-Fi is working correctly or some programs are trying to access this file to see if Wi-Fi is available. Here, we come up with some common factors for Genuineintel.sys blue screen error:
- Overheating – Computers might display a blue screen when it’s overheating due to accumulated dust or long working hours.
- Hardware issues – Corrupted or faulty hardware like RAM, HDD, SSD, motherboard, PSU, processor can also contribute to Genuineintel.sys BSOD.
- Driver issues – Most blue screen errors are related to third-party device drivers.
Most of the time, a simple restart can fix blue screen errors. If Genuineintel.sys Blue Screen of Death persists after that, scroll down to find more effective solutions now.
Tips:
To prevent indirect data loss caused by Genuineintel.sys BSOD, it’s essential to give your data an extra layer of protection. To do so, it’s a good option to back up crucial files with MiniTool ShadowMaker. This free Windows backup software is tailored for offering disaster recovery and data protection for both individuals and companies. Don’t hesitate to give it a try now.
MiniTool ShadowMaker TrialClick to Download100%Clean & Safe
Fix 1: Download Intel Driver & Support Assistant
Intel Driver & Support Assistant is designed to detect and offer updates for most drivers and software. Therefore, another solution for Genuineintel.sys BSOD is to update your intel driver via this program. To do so:
Tips:
If you can’t boot into the desktop, consider entering Safe Mode or Windows Recovery Environment to troubleshoot the issue.
Step 1. Search for Intel Driver & Support Assistant on Google Chrome and select the first option.
Step 2. Click on Download now to download this program on your computer.
Step 3. After installation, launch it and update your Intel graphics driver.
Fix 2: Reset Internet Connection
To solve Genuineintel.sys BSOD, another way is to reset your internet connection. To do so:
Step 1. Press Win + I to open Windows Settings.
Step 2. In the settings window, select Network & Internet.
Step 3. In the Status section, scroll down to select Network reset.
Step 4. Confirm this action and wait for the process to complete.
Fix 3: Reinstall Your Intel Network Driver
Genuineintel.sys Blue Screen of Death indicates that there is a problem with your Intel chipset device driver, so reinstalling the driver from the ground up might be helpful. Follow these steps:
Step 1. Type device manager in the search bar and hit Enter.
Step 2. Expand Network adapters and right-click on your Intel network driver to select Properties.
Step 3. In the Drivers tab, click on Uninstall device and confirm this operation.
Step 4. Then, reboot your system to see if Genuineintel.sys BSOD appears once more.
Fix 4: Check for Windows Update
Since Windows Update can automatically download and install driver updates, keeping your system up-to-date can also potentially fix issues related to outdated drivers like UNCORRECTABLE ERROR Genuineintel.sys blue screen. To do so:
Step 1. Open Windows Settings and move to Update & Security.
Step 2. In the Windows Update section, click on Check for updates.
Final Words
By now, you must be free from Genuineintel.sys BSOD and engage in your work again. Appreciate your time and support!
About The Author
Position: Columnist
Aurelie is a passionate soul who always enjoys researching & writing articles and solutions to help others. Her posts mainly cover topics related to games, data backup & recovery, file sync and so on. Apart from writing, her primary interests include reading novels and poems, travelling and listening to country music.
Device: hp pavilion gaming 15 dk0132tx laptop
CPU: Intel Core i5 9300H @ 2.40GHz [Coffee Lake 14nm Technology]
Chipset: Intel® HM370
Graphics: Intel UHD Graphics 630
Wireless Adapter: Intel® Wireless-AC 9560 802.11a/b/g/n/ac (2×2) Wi-Fi® and Bluetooth® 5 Combo
The Problem:
1. Random Blue Screen Error when I use the laptop connected to the WIFI
2. The Blue Screen says NMI_HARDWARE_FAILOUR
2. The Error appears both in the working state and in the Idle state (Very randomly, 3-4 times a day)
3. No BSOD when using Ethernet / not connected to wifi
4. BSOD appear ONLY when I use wifi
Here are the Dump file Analysis Report of the last appeared BSOD Failure
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
NMI_HARDWARE_FAILURE (80)
This is typically due to a hardware malfunction. The hardware supplier should
be called.
Arguments:
Arg1: 00000000004f4454, ‘TDO’
Arg2: 0000000000000000, Status Byte
Arg3: 0000000000000000
Arg4: 0000000000000000
Debugging Details:
——————
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 2015
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on HP-PAVILION-G15
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.mSec
Value: 2039
Key : Analysis.Memory.CommitPeak.Mb
Value: 77
Key : Analysis.System
Value: CreateObject
ADDITIONAL_XML: 1
OS_BUILD_LAYERS: 1
DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump
BUGCHECK_CODE: 80
BUGCHECK_P1: 4f4454
BUGCHECK_P2: 0
BUGCHECK_P3: 0
BUGCHECK_P4: 0
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
STACK_TEXT:
ffffba01`638a2b58 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
MODULE_NAME: GenuineIntel
IMAGE_NAME: GenuineIntel.sys
STACK_COMMAND: .thread ; .cxr ; kb
FAILURE_BUCKET_ID: 0x80_4F4454_GenuineIntel_NOERRREC_IMAGE_GenuineIntel.sys
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {d5ef3836-2107-b7ec-b4d4-4d2ae9fc0e02}
Followup: MachineOwner
———————————————————————————
Crash Dump Analysis with WhoCrashed
———————————————————————————
On Sat 1/16/2021 8:07:19 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\011621-16546-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5780)
Bugcheck code: 0x80 (0x4F4454, 0x0, 0x0, 0x0)
Error: NMI_HARDWARE_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a hardware malfunction has occurred.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
What can be the possible reason and solution for this problem?
I’d really appreciate your help regarding this problem. Thanks!
|
0 / 0 / 0 Регистрация: 31.01.2021 Сообщений: 4 |
|
31.01.2021, 04:09. Показов 4748. Ответов 5 Добрый день, господа. В течении последней недели стал периодически получать синий экран при разной активности: просмотр онлайн видео в Хроме, в играх (в основном после +- получаса игры), даже сейчас при генерации отчёта в AIDA64. Иногда после BSOD перезагрузки через несколько секунд после появления рабочего стола опять вылетает BSOD. Дебагером показывает, что вызваны бсоды GenuineIntel. Что было сделано: Макс температуры видеокарты — 83 градуса, процессора — до 80. Тест Intel Processor Diagnostic Tool проходит Прошу вашей помощи. Спасибо!
0 |
Programming Эксперт 39485 / 9562 / 3019 Регистрация: 12.04.2006 Сообщений: 41,671 Блог |
31.01.2021, 04:09 |
Ответы с готовыми решениями: 124 bsod BSOD 124 BSOD 124 5 |
7957 / 3204 / 616 Регистрация: 09.09.2017 Сообщений: 11,611 |
|
31.01.2021, 16:36 |
|
Сообщение было отмечено Biowaste как решение РешениеСообщение от Biowaste Дебагером показывает, что вызваны бсоды GenuineIntel В дампах нет ничего конкретного, Кликните здесь для просмотра всего текста
WHEA_UNCORRECTABLE_ERROR (124) но ошибка WHEA_UNCORRECTABLE_ERROR (124) указывает на проблему с железом. Вроде как имеется фирменный десктоп от ASUS, но комплектация удивляет (по крайней мере на оф. сайте таких комплектаций нет): Драйверы для фирменного девайса публикует производитель: https://rog.asus.com/ru/deskto… _download/
1 |
0 / 0 / 0 Регистрация: 31.01.2021 Сообщений: 4 |
|
31.01.2021, 16:56 [ТС] |
|
ibarg, это сборка где-то 2х годичной давности, на оф. сайте уже таких нет. Память ставил сам, также добавил один SSD и один SATA со старого компа. Попробую удалить драйверы и поставить заново с официалки, хотя до обновления винды они и стояли и всё-равно был синий экран периодически. ArmoryCrate и прочие свистоперделки от Asus в этот раз не устанавливал принципиально.
0 |
7957 / 3204 / 616 Регистрация: 09.09.2017 Сообщений: 11,611 |
|
31.01.2021, 17:04 |
|
Сообщение от Biowaste это сборка где-то 2х годичной давности Возможно. Сообщение от Biowaste на оф. сайте уже таких нет. Там даже есть с процом i 8-го поколения. Сообщение от Biowaste Память ставил сам Давно? BIOS может не рассчитан на 32 Гб.
0 |
0 / 0 / 0 Регистрация: 31.01.2021 Сообщений: 4 |
|
31.01.2021, 22:39 [ТС] |
|
ibarg, да, именно эта модель (i9400 + 1660 Ti) снята с производства, нашёл парочку в продаже б/у и на зарубежных интернет-площадках. Память ставил сам, проработала месяцев 10, проблем не было.
0 |
0 / 0 / 0 Регистрация: 31.01.2021 Сообщений: 4 |
|
03.02.2021, 16:17 [ТС] |
|
3 дня — полёт нормальный. Думаю, проблема решена, спасибо за помощь!
0 |
inter-admin Эксперт 29715 / 6470 / 2152 Регистрация: 06.03.2009 Сообщений: 28,500 Блог |
03.02.2021, 16:17 |
Помогаю со студенческими работами здесь BSOD 124 BSOD 124 BSOD 124 Периодический BsOD 124 bsod BCCode: 124 Дополнительные… Искать еще темы с ответами Или воспользуйтесь поиском по форуму: 6 |
Новые блоги и статьи
Все статьи Все блоги / |
||||
Распределенное обучение с TensorFlow и Python
AI_Generated 05.05.2025 В машинном обучении размер имеет значение. С ростом сложности моделей и объема данных одиночный процессор или даже мощная видеокарта уже не справляются с задачей обучения за разумное время. Когда. . . |
CRUD API на C# и GraphQL
stackOverflow 05.05.2025 В бэкенд-разработке постоянно возникают новые технологии, призванные решить актуальные проблемы и упростить жизнь программистам. Одной из таких технологий стал GraphQL — язык запросов для API,. . . |
Распознавание голоса и речи на C#
UnmanagedCoder 05.05.2025 Интеграция голосового управления в приложения на C# стала намного доступнее благодаря развитию специализированных библиотек и API. При этом многие разработчики до сих пор считают голосовое управление. . . |
Реализация своих итераторов в C++
NullReferenced 05.05.2025 Итераторы в C++ — это абстракция, которая связывает весь экосистему Стандартной Библиотеки Шаблонов (STL) в единое целое, позволяя алгоритмам работать с разнородными структурами данных без знания их. . . |
Разработка собственного фреймворка для тестирования в C#
UnmanagedCoder 04.05.2025 C# довольно богат готовыми решениями – NUnit, xUnit, MSTest уже давно стали своеобразными динозаврами индустрии. Однако, как и любой динозавр, они не всегда могут протиснуться в узкие коридоры. . . |
Распределенная трассировка в Java с помощью OpenTelemetry
Javaican 04.05.2025 Микросервисная архитектура стала краеугольным камнем современной разработки, но вместе с ней пришла и головная боль, знакомая многим — отслеживание прохождения запросов через лабиринт взаимосвязанных. . . |
Шаблоны обнаружения сервисов в Kubernetes
Mr. Docker 04.05.2025 Современные Kubernetes-инфраструктуры сталкиваются с серьёзными вызовами. Развертывание в нескольких регионах и облаках одновременно, необходимость обеспечения низкой задержки для глобально. . . |
Создаем SPA на C# и Blazor
stackOverflow 04.05.2025 Мир веб-разработки за последние десять лет претерпел коллосальные изменения. Переход от традиционных многостраничных сайтов к одностраничным приложениям (Single Page Applications, SPA) — это. . . |
Реализация шаблонов проектирования GoF на C++
NullReferenced 04.05.2025 «Банда четырёх» (Gang of Four или GoF) — Эрих Гамма, Ричард Хелм, Ральф Джонсон и Джон Влиссидес — в 1994 году сформировали канон шаблонов, который выдержал проверку временем. И хотя C++ претерпел. . . |
C# и сети: Сокеты, gRPC и SignalR
UnmanagedCoder 04.05.2025 Сетевые технологии не стоят на месте, а вместе с ними эволюционируют и инструменты разработки. В . NET появилось множество решений — от низкоуровневых сокетов, позволяющих управлять каждым байтом. . . |
Наверх
Заметил, что мой ноут стал тянуть с запуском после загрузки логотипа. Произошло это неделю назад. Появляется только один раз в день. Вот что выдала WinDbg:
************* Preparing the environment for Debugger Extensions Gallery repositories **************
ExtensionRepository : Implicit
UseExperimentalFeatureForNugetShare : false
AllowNugetExeUpdate : false
AllowNugetMSCredentialProviderInstall : false
AllowParallelInitializationOfLocalRepositories : true
-- Configuring repositories
----> Repository : LocalInstalled, Enabled: true
----> Repository : UserExtensions, Enabled: true
>>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds
************* Waiting for Debugger Extensions Gallery to Initialize **************
>>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.046 seconds
----> Repository : UserExtensions, Enabled: true, Packages count: 0
----> Repository : LocalInstalled, Enabled: true, Packages count: 36
Microsoft (R) Windows Debugger Version 10.0.25877.1004 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\012324-11203-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Kernel base = 0xfffff801`44c00000 PsLoadedModuleList = 0xfffff801`4582a790
Debug session time: Tue Jan 23 16:21:24.957 2024 (UTC + 3:00)
System Uptime: 2 days 2:44:46.702
Loading Kernel Symbols
...............................................................
................................................................
................................................................
....................................................
Loading User Symbols
Loading unloaded module list
..................................................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff801`44ffd6f0 48894c2408 mov qword ptr [rsp+8],rcx ss:ffff8600`956d48f0=????????????????
1: 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
nt!_WHEA_ERROR_RECORD structure that describes the error condition. Try !errrec Address of the nt!_WHEA_ERROR_RECORD structure to get more details.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffffc809b8007028, Address of the nt!_WHEA_ERROR_RECORD structure.
Arg3: 00000000fe000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000800400, Low order 32-bits of the MCi_STATUS value.
Debugging Details:
------------------
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: hal!_WHEA_PROCESSOR_GENERIC_ERROR_SECTION ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: hal!_WHEA_PROCESSOR_GENERIC_ERROR_SECTION ***
*** ***
*************************************************************************
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 3124
Key : Analysis.Elapsed.mSec
Value: 3875
Key : Analysis.IO.Other.Mb
Value: 0
Key : Analysis.IO.Read.Mb
Value: 0
Key : Analysis.IO.Write.Mb
Value: 0
Key : Analysis.Init.CPU.mSec
Value: 405
Key : Analysis.Init.Elapsed.mSec
Value: 6209
Key : Analysis.Memory.CommitPeak.Mb
Value: 87
Key : Bugcheck.Code.LegacyAPI
Value: 0x124
Key : Dump.Attributes.AsUlong
Value: 8
Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1
Key : Failure.Bucket
Value: 0x124_0_GenuineIntel_PROCESSOR__UNKNOWN_IMAGE_GenuineIntel.sys
Key : Failure.Hash
Value: {5371cb52-c3d9-558e-47d4-d31c09567ca2}
BUGCHECK_CODE: 124
BUGCHECK_P1: 0
BUGCHECK_P2: ffffc809b8007028
BUGCHECK_P3: fe000000
BUGCHECK_P4: 800400
FILE_IN_CAB: 012324-11203-01.dmp
DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
STACK_TEXT:
ffff8600`956d48e8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
MODULE_NAME: GenuineIntel
IMAGE_NAME: GenuineIntel.sys
STACK_COMMAND: .cxr; .ecxr ; kb
FAILURE_BUCKET_ID: 0x124_0_GenuineIntel_PROCESSOR__UNKNOWN_IMAGE_GenuineIntel.sys
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {5371cb52-c3d9-558e-47d4-d31c09567ca2}
Followup: MachineOwner
---------
Файл дампа
Ноут HP Pavilion Gaming Laptop 15-cx0098ur (4 года)
Windows 10 Home SL 64bit 22h2
Intel Core i5-8300h
Intel UHD Graphics 630 (драйвер 31.0.101.2125)
NVIDIA GeForce 1060 MaxQ (драйвер 546.65)
238GB SAMSUNG MZVLW256HEHP-000H1 (Unknown (SSD))
931GB Hitachi HGST HTS721010A9E630 (SATA )
12 гб озу (4+8 Samsung M471A5244CB0-CTD)
Задавал аналогичный вопрос на других форумах, но везде молчание. Поэтому надеюсь на вашу помощь.
Что нужно исправить?
-
Microsoft Support & Malware Removal
-
BSOD Crashes, Kernel Debugging
You should upgrade or use an alternative browser.
[SOLVED] 0x124 caused by GenuineIntel. WORKAROUNDS: Don’t let CPU MHz drop (disable intelppm;disable speedstep;change power plan settings;remove under-clock)
-
Thread starter
Thread starterUpbeatFiddle
-
Start date
Start date
- Joined
- Jan 6, 2021
- Posts
- 6
-
-
#1
PC specs :
BIOS : Latest Version.
OS: Windows10.
Gtx 1070ti
CPU — I7 6700k
Motherboard — ASUS PRIME Z270-A
RAM — 2x | G.Skill ddr4 8gb.
PSU — CX600M
Attachments
-
SysnativeFileCollectionApp.zip
SysnativeFileCollectionApp.zip
SQx
BSOD Kernel Dump Analyst
-
-
#2
Welcome to Sysnative Forum!
1) Please tell me what is the reason, why you didn’t activate the Windows?
License Activation (slui.exe) failed with the following error code:
hr=0x8007232B
Command-line arguments:
RuleId=eeba1977-569e-4571-b639-7623d8bfecc0;Action=AutoActivate;AppId=55c92734-d682-4d71-983e-d6ec3f16059f;SkuId=2de67392-b7a7-462a-b1ca-108dd189f588;NotificationInterval=1440;Trigger=NetworkAvailable
2) These three dumps have the same error code indicating a CPU issue. Also I see that the processor has been overclocked.
Debug session time: Wed Jan 6 15:38:29.373 2021 (UTC - 5:00)
Loading Dump File [C:\Users\SQ\SysnativeBSODApps\010621-3468-01.dmp]
Built by: 19041.1.amd64fre.vb_release.191206-1406
System Uptime: 0 days 0:01:32.997
BugCheck Info: WHEA_UNCORRECTABLE_ERROR (124)
Bugcheck code 00000124
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffff8889b0158028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000f2000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000020005, Low order 32-bits of the MCi_STATUS value.
*** WARNING: Unable to verify timestamp for cpuz150_x64.sys
PROCESS_NAME: cpuz.exe
Probably caused by: GenuineIntel.sys
FAILURE_BUCKET_ID: 0x124_GenuineIntel_PROCESSOR__UNKNOWN
MaxSpeed: 4000
CurrentSpeed: 4008
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Wed Jan 6 15:36:32.278 2021 (UTC - 5:00)
Loading Dump File [C:\Users\SQ\SysnativeBSODApps\010621-3515-01.dmp]
Built by: 19041.1.amd64fre.vb_release.191206-1406
System Uptime: 0 days 0:07:19.903
BugCheck Info: WHEA_UNCORRECTABLE_ERROR (124)
Bugcheck code 00000124
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffffab06878ac028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000f2000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000020005, Low order 32-bits of the MCi_STATUS value.
*** WARNING: Unable to verify timestamp for win32k.sys
PROCESS_NAME: System
Probably caused by: GenuineIntel.sys
FAILURE_BUCKET_ID: 0x124_GenuineIntel_PROCESSOR__UNKNOWN
MaxSpeed: 4000
CurrentSpeed: 4008
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Wed Jan 6 15:28:47.439 2021 (UTC - 5:00)
Loading Dump File [C:\Users\SQ\SysnativeBSODApps\010621-3921-01.dmp]
Built by: 19041.1.amd64fre.vb_release.191206-1406
System Uptime: 0 days 0:04:01.064
BugCheck Info: WHEA_UNCORRECTABLE_ERROR (124)
Bugcheck code 00000124
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffffb48fbe759028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000f2000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000020005, Low order 32-bits of the MCi_STATUS value.
*** WARNING: Unable to verify timestamp for win32k.sys
PROCESS_NAME: System
Probably caused by: GenuineIntel.sys
FAILURE_BUCKET_ID: 0x124_GenuineIntel_PROCESSOR__UNKNOWN
MaxSpeed: 4000
CurrentSpeed: 4008
Could you please clarify if your BIOS has default values?
3) Did you try to reproduce this issue in Safe Mode?
- Joined
- Jan 6, 2021
- Posts
- 6
-
-
#3
And no, I hadn’t tried to reproduce the issue in Safe Mode till now ,when I tried to open Cpu-Z it gave me somekind of an error and it just didn’t work but maybe it isn’t supposed to,idk. I’ll attach the error file below. And to wait for a bsod to happen on its own in SafeMode would take time and maybe it wouldn’t at all.
And what do you mean by BIOS default values,like have I changed anything? The only thing that I’ve changed is Intel Virtualization to enabled.
Attachments
-
New Text Document.txt
SQx
BSOD Kernel Dump Analyst
-
-
#4
UpbeatFiddle said:
And what do you mean by BIOS default values,like have I changed anything?
I mean if you changed any parameter in BIOS that was the default? if so, could you please reset all parameters to Default or Factory settings.
5: kd> !sysinfo machineid
Machine ID Information [From Smbios 3.0, DMIVersion 0, Size=4288]
BiosMajorRelease = 5
BiosMinorRelease = 12
BiosVendor = American Megatrends Inc.
BiosVersion = 1302
BiosReleaseDate = 03/15/2018
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
SystemFamily = To be filled by O.E.M.
SystemVersion = System Version
SystemSKU = SKU
BaseBoardManufacturer = ASUSTeK COMPUTER INC.
BaseBoardProduct = PRIME Z270-A
BaseBoardVersion = Rev 1.xx
5: kd> .trap ffffe401`f1feae50
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff8042741dc90 rbx=0000000000000000 rcx=ffffab0687d6fe70
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff804274144a2 rsp=fffffc8759e6f5b8 rbp=0000000000000000
r8=0000000000000000 r9=ffffab0687d6fe10 r10=fffff80427411400
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
intelppm!C1Halt+0x2:
fffff804`274144a2 c3 ret
1) Please install the chipset drivers and report if the problem is still reproducible: — Asus PRIME Z270-A (Win10 x64)
— Intel_Chipset_10.1.1.45
— Intel ME V11.7.0.1045
2) Please do a test with «Download Intel® Processor Diagnostic Tool» and report if the problem is still reproducible.
- Joined
- Jan 6, 2021
- Posts
- 6
-
-
#5
Okay, I installed both of the drivers,set BIOS to default and did the test ,here are the results — Screenshot ,it still bsods when I open Cpu-Z. ( If intelppm.sys / power service is enabled ) I know I already mentioned it but just so ya know.
- Joined
- Jan 6, 2021
- Posts
- 6
-
-
#6
Here you can see what I mean — High Performance — Screenshot
Balanced — Screenshot
And as far as I know,the blue screens are because of the core speed management.
Last edited:
- Joined
- Jan 6, 2021
- Posts
- 6
SQx
BSOD Kernel Dump Analyst
-
-
#8
As we can see you have already found a solution (workaround).
Please let us know if you prefer to use this software (with your workaround) or uninstall/remove it?
P.S. If there is a bug in the program, then only the developers of the specified program can fix it.
Also on Intel website you can try to download and install the following Intel® Z270 Chipset drivers for windows 10 x64:
Download Chipset INF Utility
Download Intel® Management Engine Driver for Windows 8.1* and Windows® 10
After that check and report if the problem is still reproducible.
Please note, if updating the chipset drivers does not solve the problem, then most likely you should contact Asus technical support for help.
- Joined
- Jan 6, 2021
- Posts
- 6
-
-
#9
SQx
BSOD Kernel Dump Analyst
-
-
#10
Let us know if there are any changes.
- Joined
- Jun 1, 2021
- Posts
- 1
-
-
#11
Workaround to enable full performance power option works for me so far. I had BSOD’s every few minutes and now I am stable for 2 hours.
- Joined
- Jun 16, 2021
- Posts
- 2
-
-
#12
I also have the I7 6700k and an Asus Motherboard (Maximus VIII Hero). These BSOD’s started in January 2021 and have only gotten worse since then.
Just like the video linked above, I can consistently reproduce by simply switching from Windows’ High Performance Power Option to Balanced. It immediately Blue Screens.
I’m also sometimes able to reproduce by running OCCT CPU tests, but not reliably.
Unfortunately, I set it to High Performance about two months ago and still have them (every few days), so I’d be curious if that’s still actually working for others?
-
-
#13
Did you try the other workarounds?
Is Windows updated with the latest Windows update patches?
- Joined
- Jun 16, 2021
- Posts
- 2
-
-
#14
Yes, I did. And I am on the latest version of Windows.
In fact, for the past few months I’ve tried what seems like everything just short of changing hardware (because I couldn’t figure out which hardware was the problem).
This thread was the first pointer towards the CPU. Because of that, I just, today, replaced the I7 6700k with an I7 7700k and the problem appears to be resolved.
I can switch to ‘Balanced’ power mode without blue screening and I can run OCCT CPU Tests without an issue. We’ll see if it lasts, but this is further than I’ve gotten since January (when it appears others started seeing the same problem as well).
Hopefully if others come across this thread with the same situation, this all helps!
- Joined
- Aug 31, 2021
- Posts
- 1
-
-
#15
I’m new here but I solved a problem similar to this one at the end of last year on my new rig from september. What fixed my problem was the Intel C-STATE option in the bios. From what I’ve red, Intel C-STATE makes the cpu use only what he needs in terms of MHz. Bluescreen often appeared when the CPU was dropping to 1MHz and then when trying to get up, I was getting a BSOD.
I would say I had one or two per week, wasn’t that bad. But After disabling the Intel C-STATE in the bios, my CPU stayed at 4MHz permanently and never BSOD’d again. Hope this helps
-
-
#16
I’m new here but I solved a problem similar to this one at the end of last year on my new rig from september.
Hi!
Given that the problem seems to be the processor i7 6700k: are you using the same one? Or what?
- Joined
- Oct 17, 2023
- Posts
- 2
-
-
#17
Latest debug attached, before I disabled C-State.
Attachments
-
latest_debug.txt
ubuysa
Sysnative Staff
BSOD Kernel Dump Senior Analyst
Contributor
-
-
#18
- Joined
- Oct 17, 2023
- Posts
- 2
-
-
#19
Has Sysnative Forums helped you? Please consider donating to help us support the site!
-
Microsoft Support & Malware Removal
-
BSOD Crashes, Kernel Debugging