Kernel thread priority floor violation windows 10 что это

На компьютере или ноутбуке под управлением Windows появился синий экран смерти? После появления сообщения KERNEL_THREAD_PRIORITY_FLOOR_VIOLATION (0x00000157) система перезагружается? Ищите как исправить 0x00000157: KERNEL_THREAD_PRIORITY_FLOOR_VIOLATION?

Skip to content

Как убрать KERNEL_THREAD_PRIORITY_FLOOR_VIOLATION (0x00000157)?


Как убрать KERNEL_THREAD_PRIORITY_FLOOR_VIOLATION (0x00000157)?

Как убрать « KERNEL_THREAD_PRIORITY_FLOOR_VIOLATION» ( 0x00000157)?

На компьютере или ноутбуке под управлением Windows появился «синий экран смерти»? После появления сообщения «
KERNEL_THREAD_PRIORITY_FLOOR_VIOLATION» (
0x00000157)
система перезагружается? Ищите как исправить
0x00000157: «
KERNEL_THREAD_PRIORITY_FLOOR_VIOLATION»?

Как просмотреть информацию об ошибках, исправить ошибки в Windows 10, 8 или 7

Журнал событий: Как просмотреть информацию об ошибках, исправить ошибки в Windows 10, 8 или 7

Причины появления ошибки

  • На жестком диске компьютера или ноутбука не достаточно места. Для правильной работы ОС Windows 10 на системном диске должно быть свободно 2 — 10 ГБ.
  • На компьютер был установлен не совместимый BIOS или прошивка была повреждена.
  • Установлены не совместимые с ОС драйвера устройств.
  • Реестр Windows был поврежден или удален. Возможно в результате очистки были удалены системные ключи реестра.
  • Ативирусное программное обеспечение или компьютерные вирусы могут заблокировать системные файлы или удалить важные ключи реестра.
  • В результате ошибок в работе программы для резервного копирования.
  • В результате обновления ОС Windows.

Актуально для ОС: Windows 10, Windows 8.1, Windows Server 2012, Windows 8, Windows Home Server 2011, Windows 7 (Seven), Windows Small Business Server, Windows Server 2008, Windows Home Server, Windows Vista, Windows XP, Windows 2000, Windows NT.

Вот несколько способов исправления ошибки «
KERNEL_THREAD_PRIORITY_FLOOR_VIOLATION»
:

Восстановите удаленные файлы

Часто появление BSoD ошибок приводит к утери важных файлов. Блокировка файлов компьютерными вирусами, ошибки в работе программ для резервного копирования, повреждение или перезапись системных файлов, ошибки файловой системы или наличие битых секторов диска – это не далеко полный список причин удаления данных.

Исправление соответствующих ошибок восстановит работоспособность устройства, но не всегда восстановит повреждённые или утерянные файлы. Не всегда имеется возможность устранить ту или иную ошибку без форматирования диска или чистой установки операционной системы, что также может повлечь за собой утерю файлов.

Загрузите бесплатно и просканируйте ваше устройство с помощью Hetman Partition Recovery. Ознакомьтесь с возможностями программы и пошаговой инструкцией.

Восстановление файлов после ошибки - «KERNEL_THREAD_PRIORITY_FLOOR_VIOLATION»


Программа для восстановления данных

Запустите компьютер в «безопасном режиме»

Если ошибка «KERNEL_THREAD_PRIORITY_FLOOR_VIOLATION» (0x00000157) возникает в момент загрузки Windows и блокирует любую возможность работы с системой, попробуйте включить компьютер в «безопасном режиме». Этот режим предназначен для диагностики операционной системы (далее ОС), но функционал Windows при этом сильно ограничен. «Безопасный режим» следует использовать только если работа с системой заблокирована.

«KERNEL_THREAD_PRIORITY_FLOOR_VIOLATION» 0x00000157: Загрузка компьютера в Безопасном режиме

Чтобы запустить безопасный режим сделайте следующее:

  1. Перейдите в меню Пуск и выберите Параметры.
  2. В открывшемся окне параметров перейдите в меню Обновление и Безопасность и выберите раздел Восстановление.
  3. В разделе Восстановление найдите Особые варианты загрузки и нажмите кнопку Перезагрузить сейчас.
  4. После этого Windows перезагрузится и предложит выбрать следующее действие. Выберите Поиск и устранение неисправностей.
  5. В меню Поиск и устранение неисправностей кликните на Дополнительные параметры, далее — Параметры загрузки.
  6. Далее Windows уведомит вас о том, что компьютер можно перезагрузить с использованием дополнительных параметров загрузки. Укажите — Включить безопасный режим. Нажмите Перезагрузить.
  7. После перезагрузки выберите Включить безопасный режим нажав клавишу F4.

Как загрузить Windows в безопасном режиме

Как загрузить Windows в безопасном режиме Youtube видео

Обновите драйвер через Диспетчер устройств

Вы установили новое аппаратное обеспечение на компьютере? Возможно вы начали использовать новое USB-устройство с вашим компьютером. Это могло привести к ошибке «KERNEL_THREAD_PRIORITY_FLOOR_VIOLATION». Если вы установили драйвер устройства используя диск, который поставляется вместе с ним, или использовали драйвер не c официального сайта Microsoft, то причина в нем. Вам придется обновить драйвер устройства, чтобы устранить эту проблему.

«KERNEL_THREAD_PRIORITY_FLOOR_VIOLATION» 0x00000157: Обновите драйвер через Диспетчер устройств

Вы можете сделать это вручную в диспетчере устройств Windows, для того выполните следующие инструкции:

  1. Нажмите кнопку Windows, затем введите диспетчер устройств с клавиатуры.
  2. Выберите Диспетчер устройств из списка.
  3. Просмотрите список категорий устройств, нажмите на стрелочку рядом с категорией вашего нового устройства. Драйвер может быть отмечен желтым треугольником.
  4. Кликните правой кнопкой мыши на имя устройства и нажмите Обновить драйвер.
  5. Далее откроется окно Мастера обновления драйверов с двумя опциями:
    • Автоматический поиск обновленных драйверов. Windows проверит наличие наиболее подходящего драйвера для этого устройства в автоматическом режиме.
    • Выполнить поиск драйверов на этом компьютере. Используйте эту опцию, что бы самостоятельно указать ОС файлы драйвера.

Перезагрузите компьютер после установки драйвера.

Используйте sfc /scannow для проверки всех файлов системы

Повреждение или перезапись системных файлов может привести к ошибке «KERNEL_THREAD_PRIORITY_FLOOR_VIOLATION». Команда sfc находит поврежденные системные файлы Windows и заменяет их.

«KERNEL_THREAD_PRIORITY_FLOOR_VIOLATION» 0x00000157: Восстановите системные файлы
  1. Нажмите кнопку Windows, затем введите cmd с клавиатуры.
  2. Правой кнопкой мышки кликните на CMD и запустите от имени администратора.
  3. В окне командной строки введите sfc /scannow и нажмите Enter.

Этот процесс может занять несколько минут.

Как восстановить системные файлы Windows 10

Youtube видео как восстановить системные файлы Windows 10

Проверьте диск с Windows на наличие ошибок командой chkdsk c: /f

Возможно к синему экрану с «KERNEL_THREAD_PRIORITY_FLOOR_VIOLATION» привела ошибка файловой системы или наличие битых секторов диска. Команда CHKDSK проверяет диск на наличие ошибок файловой системы и битых секторов. Использование параметра /f заставит программу автоматически исправлять найденные на диске ошибки, а параметр /r позволяет найти и «исправить» проблемные сектора диска. Для запуска следуйте инструкциям:

«KERNEL_THREAD_PRIORITY_FLOOR_VIOLATION» 0x00000157: Проверьте диск на наличие ошибок
  1. Нажмите кнопку Windows, затем введите CMD с клавиатуры.
  2. Правой кнопкой мышки кликните на CMD и запустите от имени администратора.
  3. В окне командной строки введите chkdsk c: /f и нажмите Enter (используйте ту букву диска, на котором установлена ОС).

Дождитесь окончания процесса и перезагрузите компьютер.

Используйте режим совместимости со старой версией Windows

Отключите лишние программы из автозагрузки Windows

Программное обеспечение, вызывающее «KERNEL_THREAD_PRIORITY_FLOOR_VIOLATION» (0x00000157), может быть прописано в автозагрузку Windows и ошибка будет появляться сразу после запуска системы без вашего участия. Удалить программы из автозагрузки можно с помощью Диспетчера задач.

«KERNEL_THREAD_PRIORITY_FLOOR_VIOLATION» 0x00000157: Отключите программы из автозагрузки Windows
  1. Загрузитесь в Безопасном режиме.
  2. Кликните правой кнопкой мышки на Панели задач, затем на пункте Диспетчер задач.
  3. Перейдите на вкладку Автозагрузка.
  4. Чтобы убрать ту или иную программу из автозагрузки выберите её из списка и отключите, нажав кнопку Отключить в правом нижнем углу окна.

Обратитесь в поддержку Microsoft

Microsoft предлагает несколько решений удаления ошибки «голубого экрана». «KERNEL_THREAD_PRIORITY_FLOOR_VIOLATION» (0x00000157) можно убрать с помощью Центра обновления или обратившись в поддержку Windows.

«KERNEL_THREAD_PRIORITY_FLOOR_VIOLATION» 0x00000157: Обратитесь в поддержку в Microsoft
  1. Перейдите на сайт технической поддержки Microsoft.
  2. Введите код и сообщение об ошибке в поисковую строку и следуйте найденным рекомендациям.
  3. Если вы не найдете готового решения, то задайте вопрос в сообществе — возможно вам ответит сертифицированный системный администратор.

Установите последние обновления системы

С обновлениями Windows дополняет базу драйверов, исправляет ошибки и уязвимости в системе безопасности. Загрузите последние обновления, что бы избавиться от ошибки «KERNEL_THREAD_PRIORITY_FLOOR_VIOLATION» (0x00000157).

«KERNEL_THREAD_PRIORITY_FLOOR_VIOLATION» 0x00000157: Центр обновления системы

Запустить Центр обновления Windows можно следующим образом:

  1. Перейдите в меню Пуск и выберите Параметры.
  2. В окне Параметров перейдите в меню Обновление и Безопасность.
  3. Для установки последних обновлений Windows нажмите кнопку Проверка наличия обновлений и дождитесь окончания процесса их поиска и установки.
«KERNEL_THREAD_PRIORITY_FLOOR_VIOLATION» 0x00000157: Настройка автоматического обновления системы

Рекомендуется настроить автоматическую загрузку и установку обновлений операционной системы с помощью меню Дополнительные параметры.

Чтобы включить автоматическое обновление системы необходимо запустить Центр обновления Windows:

  1. Перейдите в меню Пуск и выберите Параметры.
  2. В окне Параметров перейдите в меню Обновление и Безопасность и выберите подменю Центр обновления Windows. Для установки последних обновлений Windows нажмите кнопку Проверка наличия обновлений и дождитесь окончания процесса их поиска и установки.
  3. Перейдите в Дополнительные параметры и выберите, как устанавливать обновления — Автоматически.

Запустите проверку системы на вирусы

«Синий экран смерти» с ошибкой «KERNEL_THREAD_PRIORITY_FLOOR_VIOLATION» 0x00000157 может вызывать компьютерный вирус, заразивший систему Windows.

Для проверки системы на наличие вирусов запустите установленную на компьютере антивирусную программу.

«KERNEL_THREAD_PRIORITY_FLOOR_VIOLATION» 0x00000157: Проверка системы на вирусы

Современные антивирусы позволяют проверить как жесткие диски, так и оперативную память. Выполните полную проверку системы.

Выполните проверку оперативной памяти

Неполадки с памятью могут привести к ошибкам, потере информации или прекращению работы компьютера.

Прежде чем проверять оперативную память, отключите её из разъёма на материнской плате компьютера и повторно вставьте в него. Иногда ошибка KERNEL_THREAD_PRIORITY_FLOOR_VIOLATION» вызвана неправильно или не плотно вставленной в разъём планкой оперативной памяти, или засорением контактов разъёма.

Если предложенные действия не привели к положительному результату, исправность оперативной памяти можно проверить средствами операционной системы, с помощью средства проверки памяти Windows.

Запустить средство проверки памяти Windows можно двумя способами:

  1. С помощью Панели управления:
    «KERNEL_THREAD_PRIORITY_FLOOR_VIOLATION» 0x00000157: Запуск проверки памяти через Панель управления

    Перейдите в Панель управления / Система и безопасность / Администрирование. Запустите приложение Средство проверки памяти Windows.

  2. С помощью средства Выполнить:
    «KERNEL_THREAD_PRIORITY_FLOOR_VIOLATION» 0x00000157: Запуск проверки памяти c помощью комманды выполнить

    Запустите средство Выполнить с помощью комбинации клавиш Windows + R. Наберите mdsched и нажмите Enter. После чего откроется средство проверки Windows.

Для начала проверки выберите один из предлагаемых вариантов, проверка оперативной памяти в соответствии с которым будет запущена после перезагрузки компьютера.

Если в результате проверки будут определены ошибки, исправить которые не представляется возможным, то такую память необходимо заменить (замене подлежит модуль памяти с неполадками).

Выполните «чистую» установку Windows

Если не один из перечисленных методов не помог избавиться от KERNEL_THREAD_PRIORITY_FLOOR_VIOLATION», попробуйте переустановить Windows. Для того чтобы выполнить чистую установку Windows необходимо создать установочный диск или другой носитель с которого планируется осуществление установки операционной системы.

Загрузите компьютер из установочного диска. Для этого может понадобиться изменить устройство загрузки в BIOS или UEFI для более современных компьютеров.

Следуя пунктам меню установщика укажите диск, на который вы хотите установить Windows. Для этого понадобится отформатировать его. Если вас не устраивает количество или размер локальных дисков, их можно полностью удалить и заново перераспределить.

Помните, что форматирование, удаление или перераспределения дисков удалит все файлы с жесткого диска.

После указания диска для установки Windows запуститься процесс копирования системных файлов и установки операционной системы. Во время установки от вас не потребуется дополнительных действий. В течении установки экран компьютера будет несколько раз гаснуть на непродолжительное время, и для завершения некоторых этапов установки компьютер будет самостоятельно перезагружаться.

В зависимости от версии Windows на одном из этапов от вас может понадобиться выбрать или внести базовые параметры персонализации, режим работы компьютера в сети, а также параметры учётной записи или создать новую.

После загрузки рабочего стола чистую установку Windows можно считать законченной.

Примечание. Прежде чем приступить к выполнению чистой установки Windows заранее побеспокойтесь о наличии драйверов ко всем установленным устройствам и сохранности ваших файлов. Загрузите и сохраните драйвера на отдельный носитель информации, а для важных данных создайте резервную копию.

Как сбросить Windows 10 к исходному состоянию

Как сбросить Windows 10 к исходному состоянию Youtube видео

Как сбросить Windows 10, 8, 7 если компьютер не загружается

Youtube видео Как сбросить Windows 10, 8, 7 если компьютер не загружается

Blue Screen error KERNEL_THREAD_PRIORITY_FLOOR_VIOLATION in the Windows 10 compels the system to restart time and again without prior noticing. This BSOD issue refers to an illegal operation that was attempted on the priority floor of a particular thread. The problem has a bug check value 0x00000157 and always ends to reboot the affected device automatically.

Once you experience KERNEL_THREAD_PRIORITY_FLOOR_VIOLATION, you might come across error messages while starting an application or closing followed with desktop freezing. Managing the complexities of such a Windows 10 error is for high-level users. This type of error is basically the result of inconsistent and outdated faulty device drivers which causes to crash and restart your machine constantly. When the malicious software or trojans deletes the system resources, you can easily be prey of this error. This mainly happens because of the conflict between similar applications. Along with the memory issues, bad areas in Hard Disk can also be the possible causes of this mess up. Before going beyond the control of the consequences of this issue, let’s dismiss it using the workarounds as following. First of all, have a brief look at the list of the solutions –

This is how to fix KERNEL_THREAD_PRIORITY_FLOOR_VIOLATION BSOD Error in Windows 10 –

1] Disable Automatic Device Reboot

Once a device is fully affected by KERNEL_THREAD_PRIORITY_FLOOR_VIOLATION Error, you will experience automatic restarting at a quite regular interval. This is one of the most disturbing parts of the Blue screen error. Having this issue, you cannot have enough time to understand what’s happening actually. To implement a resolution will be tougher as well. Therefore, we are considering this problem in the first place and trying to disable the feature. Proceed with the following steps to accomplish the task –

Step-1: First of all, press Win+D simultaneously and head to the desktop area.

Step-2: Do a right-click on This PC icon and select Properties option from the context menu.

Step-3: On the following screen, select Advanced system settings from the left pane.

Step-4: Inside the System Properties wizard, you need to shift to locate the Advanced tab.

Step-5: Get access to Startup and Recovery region and click on the Settings option here.

Step-6: Move to the System failure section and uncheck the box adjacent to ‘Automatically restart‘.

Step-7: Finally, click on the OK button to save the changes.

KERNEL_THREAD_PRIORITY_FLOOR_VIOLATION

After these changes are put into effect, you will not experience the automatic restarting anymore. Therefore, you can have enough room to use other workarounds smoothly.

2] Kill Malware to Fix KERNEL_THREAD_PRIORITY_FLOOR_VIOLATION BSOD Error

You all might be well aware of the damage done by the malicious software still incapable to escape from them. These bugs exist throughout on the web and anytime we can be the easiest kill. A regular scanning for viruses in full system is necessary and you can get the best deal from Windows Security app only. This is the built-in anti-malware program powered by Microsoft especially for Windows 10. Here is the process to kill the malware using the default app –

  • Press the Windows key from your keyboard.
  • Type Virus & threat protection and hit the Enter.
  • When the Windows Security page opens, select Scan options to reveal all the available processes.
  • On the succeeding page, check the radio button for Full scan and hit the Scan now button.
  • After completion of the scanning, select Clean threats option if any malware present and dismiss them.
  • Thereafter, on moving to the succeeding page, you will see three options available.
  • Select Remove and later on Start actions button to start the removal.

KERNEL_THREAD_PRIORITY_FLOOR_VIOLATION error

3] Use Windows Blue Screen Troubleshooter for BSOD issues

This tool is able to remove the BSOD problem from the devices. If you are using any version equal or above that then you can easily resolve KERNEL_THREAD_PRIORITY_FLOOR_VIOLATION BSOD Error using this utility. Here are the following instructions to run the troubleshooter –

  • Press Win+I and let Windows Settings app appear.
  • Choose Update & Security.
  • On the subsequent page, choose Troubleshoot subsection from the left layout.
  • In the right side of the appearing screen, find out the Blue Screen option.
  • Once you located it, select and hit Run the Troubleshooter button.

Once it detects the Blue Screen Troubleshooter error, this will resolve them by itself. In due course, you can get rid of KERNEL_THREAD_PRIORITY_FLOOR_VIOLATION BSOD Error in Windows 10.

4] Take Help from Windows Device Manager and Update Drivers

Among all the problems behind KERNEL_THREAD_PRIORITY_FLOOR_VIOLATION BSOD Error, a defective, outdated and incompatible driver is the most potential reason to cause this. Therefore, here we need to take an immediate step to update them and in that case, Device Manager can be suitable. Outdated drivers are represented with recognizing indication and that makes the task a lot easier. Here is how to update the drivers using the default app –

  • Press Win+S hotkey and invoke Taskbar search on display.
  • Type Device Manager in the empty field and press the Enter key.
  • Take a bit of while and have a proper glance on the devices having an exclamation mark in them.
  • If there is any, do a click on that specific device to expand and split the driver list.
  • Do a right-click on the drivers and choose Update driver option from the appeared menu.
  • Now, follow the on-screen guidance to update the drivers.
  • Similarly, do the same with all devices having the mark of exclamation.

KERNEL_THREAD_PRIORITY_FLOOR_VIOLATION error windows 10

Once all the drivers are well up to date, restart the computer normally and after the starting up, check for the error. Hopefully, it will resolve the KERNEL_THREAD_PRIORITY_FLOOR_VIOLATION BSOD Error in Windows 10.

5] Resolve the Memory Problems immediately

If Windows suffers from memory issues, KERNEL_THREAD_PRIORITY_FLOOR_VIOLATION BSOD Error may occur. The same consequence is a must if the Computer’s RAM also suffers from bad areas in it. To solve all these components, Windows Memory Diagnostic come out as rescuer. Here is how to proceed for the tool –

  • Press Win and I keys and let the system launch the Settings app.
  • Type memory in the search box located on the app UI.
  • As you see “Diagnose your computer’s memory problems” in the result, select it immediately.
  • Select ‘Restart now and check for problems (recommended)’ option.
  • At this time, Windows will undergo restarting with this action. After signing back in, a Blue screen will appear in the display and start detecting RAM issues. Once the process reaches 100%, the system will reboot once again by itself.
  • When it Startup again, check the outcomes of the System Tray – Notification area.

KERNEL_THREAD_PRIORITY_FLOOR_VIOLATION bsod

Once all these memory issues will sort out, KERNEL_THREAD_PRIORITY_FLOOR_VIOLATION BSOD Error in Windows 10 will fix as well.

6] Install the available Update files and make OS up to date

All the cumulative updates, patches, and major releases hold addressing of existing bugs and problems accompanied with all new features. Once Windows is outdated, it can be easy kill to KERNEL_THREAD_PRIORITY_FLOOR_VIOLATION BSOD Error. We can simply install all the available patches in order to update OS as well as make it stronger. Follow the below instruction to do the task –

Important – Try using speedy internet connection via wireless or Ethernet cable. In the case of using Mobile Hotspot, disable the Metered Connection first or else, the downloading process will not start.

Step-1: Click on the Start button.

Step-2: Select the Settings icon to open it.

Step-3: Click on Update & Security.

Step-4: On the following page, choose Windows Update from the left flank.

Step-5: Move to the right, click on Check for updates button under it.

Step-6: When the entire patches available here, select the Download button.

Step-7: On finishing the process, the installation will start by itself.

Step-8: Be careful about the further instructions coming here.

KERNEL_THREAD_PRIORITY_FLOOR_VIOLATION blue screen

7] Offer the Additional Hard Drive little rest to Fix KERNEL_THREAD_PRIORITY_FLOOR_VIOLATION BSOD Error

Some people have gone through the worst consequences of KERNEL_THREAD_PRIORITY_FLOOR_VIOLATION BSOD Error just after connecting an additional HDD with PC. Nowadays, we need an extra hard disk for serving vibrant purposes. Fortunately, the fix is simpler than we could ever think. Only disconnecting will do the trick. Follow the below instructions and offer them an instantly break –

  • First of all, disconnect the additional hard drive and place it in a safe place with care.
  • Now, click on the Start button and Restart Windows 10 PC.
  • When Windows completes the cycle of rebooting, perform checking in the system for the existence of the error.
  • If nothing comes up, plug in all the separated accessory one by one.
  • When the connecting procedure ends, open the web browser from the computer and make a visit to the manufacturer website for the device.
  • Download and install again the latest drivers.

8] Rectify Windows System Components issue and Recover missing DLL files

KERNEL_THREAD_PRIORITY_FLOOR_VIOLATION BSOD Error is developed in a system when DLL files go missing and system resources are corrupted. A handy tool named System File Checker can resolve all these issues. To launch the utility, instructions are as follows –

  • Open the Taskbar search by pressing Win+S hotkey together.
  • In the void, type cmd, and press Ctrl+Shift+Enter together.
  • This will launch Elevated Command Prompt.
  • Click on the Yes button to give consent once User account control dialog prompts.
  • In the following window, type the following command line –

Sfc /scannow

  • Press Enter key to activate the System File Checker in it.
  • This will recover all the missing DLL files and fix corrupted resources in the system.
  • It might take a long time, so wait patiently until finished off.

SFC /SCannow in elevated command prompt

Finally, restart the device and check if KERNEL_THREAD_PRIORITY_FLOOR_VIOLATION BSOD Error in Windows 10 has resolved.

9] Remove all Similar kinds of Programs staying together in the system

Similar types of programs when staying together in the system, engage in collision with each other. In the end, they delete necessary OS files and KERNEL_THREAD_PRIORITY_FLOOR_VIOLATION BSOD Error rises up. To stop this, uninstalling is the key only. Here is how to uninstall an app from the system –

  • Launch Settings app using any handy method as we explained above.
  • Click Apps.
  • Select Apps & features lying on the left side.
  • Jump to the alternate pane and reach to programs colliding with each other once they are available in the list.
  • Select the app and hit the Uninstall button.
  • If UAC dialog prompts for permission, hit Yes to continue.
  • Once the uninstalling finishes following additional guidelines coming to display, restart Windows.
  • Prior to signing back, if the error is resolved successfully, download and install these apps if necessary.

uninstall unnecessary program

10] Fix-up the Poor Hard Disc Sections using Disk Checking Tool

If Hard Disk has bad areas present in it, will definitely suffer from KERNEL_THREAD_PRIORITY_FLOOR_VIOLATION BSOD Error. Disk Checking is a much recommendable tool for fixing these areas in a smooth way. To power up the tool, first, you have to run command in Elevated Command Prompt. The guidelines for that is as follows –

  • First of all, press Ctrl+Alt+Del.
  • Select Task Manager from the appearing window.
  • Once it opens, select File option located at the top left end.
  • Choose Run new task from visible options.
  • When a dialog appears, type cmd in the blank text area.
  • Thereafter, tick the box leading to the option “Create this task with administrative privileges”.
  • Select the OK button and let Elevated Command Prompt appear.
  • Type the following command and press the Enter key – chkdsk [Drive:] [parameters]
  • Disk Checking tool will start showing disk status only.
  • Now, arrange the command in following way –

/f /r /x

In the above command line, we have used f for fixing the detected problems in volume.

r for bringing out the bad areas in the Hard disk.

x for making the total volume dismounted before the operation begins.

Accordingly, the final command seems like- chkdsk C: /f /r /x

check disk in command prompt as administrator

Here, C: is added as we have installed the OS in this drive. For your case, use any like D:, E: or any based on where you have installed Windows 10.

  • Now, hit the Enter button after typing the whole command.
  • This process will take a while for finishing up, hold the patience till it gets over completely.
  • Once finished, you can reboot the PC and afterward, check whether the workaround has resolved KERNEL_THREAD_PRIORITY_FLOOR_VIOLATION BSOD Error in Windows 10.

11] Clear junk files to have extra space in Disk

Junk files are automatically created by the system for the execution of tasks and they are useful for a temporary period of time. However, they are useless but still stored in Disk space. In due course, they keep piling up and at a time occupy huge space. As a result, the normal functionality of device deteriorates and also cause the KERNEL_THREAD_PRIORITY_FLOOR_VIOLATION BSOD Error. Disk Cleanup tool easily delete them all together once activated. Here is how to free up space using the tool –

  • Do a right-click on the Start menu and select the Run option.
  • Type cleanmgr in the text box and hit the Enter key.
  • From the dialog, select C: from the dropdown menu and press the Enter key.
  • This will calculate the recoverable space on Drive C:
  • Scroll and click on the Clean up system files option.
  • You will see the small popup dialog coming up once again and asking for the desired drive.
  • Choose C: again from the menu and also select the OK button.
  • At this time, Disk Cleanup for (C:) will disappear after running the calculation.
  • Subsequently, check all the items available except Downloads.
  • Hit OK from the bottom to initiate the cleanup process.

disk cleanup ok button

Note – Prior to commencing the process, carry out a check-in Recycle Bin for necessary files in it. Restore to respective location if you find any.

12] Uninstall Problematic Windows Update Files to Resolve KERNEL_THREAD_PRIORITY_FLOOR_VIOLATION BSOD Error

If the Windows updating process stops at midway, the files become corrupted. It would be the main cause of KERNEL_THREAD_PRIORITY_FLOOR_VIOLATION. Usually, this case is very rare but might happen in case of you. The resolution is to delete them ASAP using below steps –

  • Press Win+I together and let Windows Settings appear.
  • Click on the Update & Security icon.
  • On the subsequent page, choose Windows Update from the left pane.
  • Navigating ahead to the corresponding pane, click on the link View update history.
  • After that, do a click on the Uninstall updates link.
  • This act will open up the Installed Updates window by default. Reach to the last received patch.
  • Select it and hit Uninstall option from the top ribbon.
  • Follow the upcoming guidelines on display to complete the deleting process.

uninstall faulty updates

13] Perform System Restore to take Windows 10 to previous point

You can get KERNEL_THREAD_PRIORITY_FLOOR_VIOLATION BSOD Error after making abnormal changes by installing or uninstalling a program. Performing System Restore will guide you back in the earlier state if you have previously created Restore points. You can use this workaround and probably, can skip the BSOD error. To use the method, the instructions are –

Note – If you have not ever created restore points, bypass this workaround and pass to the next resolution. You cannot accomplish the task without having points created before.

  • Open Run dialog using a suitable way as we explained above.
  • Type ‘rstrui‘ and press the Enter key.
  • Hit Next from the bottom of this appearing wizard.
  • On the succeeding window, make a click on Show more restore points if want to see all the previous ones.
  • Choose the recent one in the list and hit the Next button again.
  • From the window appearing next, select Finish to start the Restoring process.

show more restore points

14] Solve the Windows Image Files to fix KERNEL_THREAD_PRIORITY_FLOOR_VIOLATION BSOD Error

For so many reasons, Windows image files fall into corruption. Unless we fix them, can cause KERNEL_THREAD_PRIORITY_FLOOR_VIOLATION BSOD Error any time. DISM tool very handy application that can easily solve this task. To access the utility, proceed with the following –

  • Open Command Prompt as administrator using the above guidelines.
  • Once it opens, type following command-line tool –

DISM.exe /Online /Cleanup-image /Restorehealth

  • Press Enter.
  • The tool will instantly start working and will fix all the defective Windows image files by itself.
  • Once the task is finished, reboot the device to make this resolution effective.

dism tool in command prompt

Upon returning back to the desktop, check if there is KERNEL_THREAD_PRIORITY_FLOOR_VIOLATION BSOD Error in Windows 10.

15] Remove the Third Party anti-virus Applications

Anti-virus applications are necessary to deal with malware and you cannot really feel safe without one. With time, Windows Security has become the best ever utility in this case. Other Third-party anti-malware programs become unnecessary and can cause KERNEL_THREAD_PRIORITY_FLOOR_VIOLATION BSOD Error also. Thus, you can prevent BSOD issue by deleting these programs. To complete the task, instructions are as following –

  • Invoke Run dialog by making a combined press of Win+R.
  • Type appwiz.cpl in the text box and click on the OK button.
  • When the Programs and Features window appears, move out for Third Party anti-virus Application in the appearing list.
  • Do a right-click on it and choose Uninstall option.
  • Hit Yes if UAC prompts.
  • Follow the guidelines coming afterwards until this app uninstall successfully.

16] Enter Safe Boot Mode

From the very primitive period, during all Windows issues, Booting in Safe Mode came out victorious. In this mode, the OS starts with loading only the basic programs and most of the critical issue disappears with this only. As a well-known workaround, let’s follow the below instructions –

Step#1: Click on the Start button and select the Power icon.

Step#2: Continuously press the Shift key then click on the restart via start menu.

Step#3: Windows will prepare for rebooting initially and then you notice view a blue screen having few options at the Startup.

Step#4: Click on the Troubleshoot.

Step#5: Select Advanced options and click on Startup Settings.

Step#6: Now, restart Windows 10 once more.

Step#7: The startup screen will have options Boot in Safe Mode.

Step#8: Finally, click on the F8 key and head to the Safe Mode next.

So far, we have elaborated all the effective workarounds resolving KERNEL_THREAD_PRIORITY_FLOOR_VIOLATION BSOD Error. As you have come to this point, probably, the issue is no more prevalent in your system. If you still have the same situation like before, we can suggest only last resort – Reinstalling Windows 10. This will be the ultimate solution for all problems if done with perfection.

However, if you have made your mind to go with the workaround, make sure you have saved the backup for all the essential data to avoid loss. Furthermore, to avoid any issue, you can also take help from professional for performing the task.

Methods:
1] Disable Automatic Device Reboot
2] Kill Malware
3] Use Windows Blue Screen Troubleshooter
4] Take Help from Windows Device Manager and Update Drivers
5] Resolve the Memory Problems
6] Install the available Update files
7] Offer the Additional Hard Drive little rest
8] Rectify Windows System Components issue
9] Remove all Similar kinds of Programs
10] Fix-up the Poor Hard Disc Sections
11] Clear junk files
12] Uninstall Problematic Windows Update Files
13] Perform System Restore
14] Solve the Windows Image
15] Remove the Third Party anti-virus Applications
16] Enter Safe Boot Mode

That’s all!!

Repair any Windows problems such as Blue/Black Screen, DLL, Exe, application, Regisrty error and quickly recover system from issues using Reimage.

22.01.2020

Просмотров: 11051

BSOD или синий экран смерти KERNEL THREAD PRIORITY FLOOR VIOLATION с кодом 0x00000157 возникает на различных сборках Windows по причине аппаратной и программной поломки. Поскольку на официальном сайте Майкрософт нет указания на точную причину BSOD, то для её определения нужно включить малый дамп памяти и проанализировать полученный файл с помощью программы BlueScreenView.

Читайте также: Методы исправления ошибки 0x00000156: WINSOCK DETECTED HUNG CLOSESOCKET LIVEDUMP на Windows 8

Как исправить BSOD 0x00000157: KERNEL THREAD PRIORITY FLOOR VIOLATION на Windows 7?

Поскольку официальных рекомендаций по исправлению ошибки 0x00000157: KERNEL THREAD PRIORITY FLOOR VIOLATION на сайте Майкрософт нет, то, проанализировал зарубежные форумы, выделим способы, к которым прибегали пользователи Windows 7 и не только для решения проблемы.

Так, на одном из зарубежных форумов указано, что синий экран смерти KERNEL_THREAD_PRIORITY_FLOOR_VIOLATION возникала на ПК с Windows 7 при запуске онлайн игр. При этом ПК после вылета ошибки перезагружался. Виновником BSOD оказался видеодрайвер. Для решения ошибки стоит переустановить ПО для видеокарты. Сделать это можно следующим образом:

Жмем «Win+R» и вводим «devmgmt», чтобы открыть «Диспетчер устройств».

Разворачиваем ветку «Видеоадаптеры». Нажимаем на названии видеокарты правой кнопкой мыши и выбираем «Обновить драйвера».

Появится небольшое окно. Выбираем «Выполнить поиск драйверов на этом компьютере».

Указываем путь к ранее загруженному драйверу.

Позволяем Windows обновить драйвера. Перезагружаем систему, чтобы изменения вступили в силу.

ВАЖНО! В некоторых пользователей данную ошибку вызывал аудиодрайвер. Поэтому нужно проанализировать состояние всех установленных драйверов и при необходимости обновить их все.

Еще на одном форуме пользователи указывали, что ошибка 0x00000157 появлялась на их ПК по причине вирусного заражения системы и повреждения системных файлов. При этом стандартный инструмент sfc /scannow не помог исправить ошибку. В данном случае нужно воспользоваться опцией по восстановлению системы с установочного диска. Для этого нужно подключить к ПК установочный диск или флешку с той же версией и разрядностью операционной системы, что и установлена. Далее кликнуть не «Установить», а «Восстановление системы».

Появится небольшое окно. Нужно выбрать «Восстановление системы».

Запустится восстановление Windows. После завершения процесса и перезагрузки ПК нужно извлечь диск или флешку и проверить систему на наличие или отсутствие ошибки.

Если же вы занимались разгоном оперативной памяти или процессора и применяли для этой цели фирменные утилиты от производителей устройств, то нужно сбросить настройки до заводских и удалить специальные программы. Иногда, именно фирменные утилиты вызывают BSOD 0x00000157: KERNEL THREAD PRIORITY FLOOR VIOLATION.

В случае, если вы не разгоняли ни одно из установленных комплектующих системной сборки, на ПК нет вирусов и драйвера находятся в актуальном состоянии, рекомендуем провести полную диагностику всего ПК и откатить Windows 7 до более раннего состояния или вовсе выполнить чистую инсталляцию операционной системы.

Contents

  • Causes of The Error
  • Restore Deleted Files
  • Start The Computer in Safe Mode
  • Update a Driver With The Device Manager
  • Use sfc /scannow To Check All System Files
  • Check for Errors The Disk Where Windows Is Installed By Using The Command chkdsk c: /f
  • Use The Mode of Compatibility With an Old Version of Windows
  • Disable Unnecessary Programs in Windows Startup Menu
  • Consult Microsoft Support Service
  • Install Latest System Updates
  • Scan The System For Viruses
  • Test Your RAM
  • Make a Clean Installation of Windows

Causes of The Error

  • There is not enough free space in the hard disk of your computer/laptop. For Windows 10 to operate correctly you need to have from 2 to 10 Gb of free space in your system disk.

  • An incompatible version of BIOS was installed or the firmware was damaged.

  • Device drivers incompatible with the OS were installed.

  • Windows registry was damaged or deleted, or cleaning operations accidentally deleted system keys.

  • Antivirus software or viruses may block system files or delete important registry keys.

  • An error occurred in the work of backup software.

  • It can also happen as a result of a Windows update.

Read more how to fix 0x00000157: «KERNEL_THREAD_PRIORITY_FLOOR_VIOLATION» in Windows 11, Windows 10, Windows 8.1, Windows Server 2012, Windows 8, Windows Home Server 2011, Windows 7 (Seven), Windows Small Business Server, Windows Server 2008, Windows Home Server, Windows Vista, Windows XP, Windows 2000, Windows NT.

Here are some ways of eliminating the problem with «KERNEL_THREAD_PRIORITY_FLOOR_VIOLATION»:

Restore Deleted Files

Often BSoD errors cause loss of important files. Files blocked by computer viruses, backup software errors, damaged or overwritten system files, file system errors or bad hard disk sectors – these are only some of the causes that can make your data lost.

Corrections of the corresponding errors will restore the normal operation of your devices, but it does not always restore damaged or lost files. Also, it is not always possible to eliminate an error without formatting the hard disk or clean installation of the operating system, which can also involve loss of files.

The tool recovers data from any devices, regardless of the cause of data loss.

Download for free and scan your device with the help of Hetman Partition Recovery. Learn about the program features and step-by-step guide.

Hetman Partition Recovery

Start The Computer in Safe Mode

If the error «KERNEL_THREAD_PRIORITY_FLOOR_VIOLATION» (0x00000157) occurs when loading Windows and blocks any attempts to work with the system, try loading the computer in Safe Mode. This mode is meant for operating system (OS) diagnostics, but OS functions are very limited in this mode. Safe Mode should only be used if the system is blocked otherwise.

Start The Computer in Safe Mode

In order to start Safe Mode you should do the following:

  1. Go to Start menu and choose Settings.

  2. In the settings window that appears go to Update & Security menu and choose the Recovery tab.

  3. In the tab Recovery find Advanced startup and click the button Restart now.

  4. As your Windows restarts, it will ask you to choose the next step. Choose Troubleshoot.

  5. In the Troubleshoot menu click on Advanced Options and then on Startup Settings.

  6. Then Windows will inform you that the computer can be restarted with the use of additional settings one of which is Enable Safe Mode. Press Restart.

  7. After restarting choose Enable Safe Mode by pressing F4.


Go to view

How to Boot Windows 10 in Safe Mode (All Methods)


How to Boot Windows 10 in Safe Mode (All Methods)

Update a Driver With The Device Manager

Have you installed new hardware to your computer? Are you using a new USB device? These can be the causes for the error «KERNEL_THREAD_PRIORITY_FLOOR_VIOLATION». If you installed your device driver from the disk you have found in the device delivery package or if you are using a driver which was downloaded from a place other than Microsoft official website, this can be the core of the problem. You will have to update the device driver to fix it.

Update a Driver With The Device Manager

You can do it manually in the Windows device manager by taking the following steps:

  1. Press Windows button and type device manager on the keyboard.

  2. Choose Device Manager from the list.

  3. View the list of device categories and click on the arrow nest to the category in which your new device falls. The driver can be marked with a yellow triangle.

  4. Right-click on the device name and press Update Driver Software.

  5. Then a window of Update Driver Software with two options will appear:

    • Search automatically for updated driver software. Windows will automatically check availability of the best suitable driver for this device.

    • Browse my computer for driver software. Use this option to show the OS where the driver files are kept.

Restart the computer after the driver is installed.

Use sfc /scannow To Check All System Files

Damaged or rewritten system files may cause the error «KERNEL_THREAD_PRIORITY_FLOOR_VIOLATION». The command sfc finds damaged Windows system files and replaces them.

Use sfc /scannow To Check All System Files
  1. Press Windows button and enter cmd from the keyboard.

  2. Right-click on CMD and launch it as administrator.

  3. In the command prompt window, type in sfc /scannow and press Enter.

This process may take several minutes.


Go to view

How to Recover Windows 10, 8, 7 System Files (SFC, DISM)


How to Recover Windows 10, 8, 7 System Files (SFC, DISM)

Check for Errors The Disk Where Windows Is Installed By Using The Command chkdsk c: /f

The blue screen with «KERNEL_THREAD_PRIORITY_FLOOR_VIOLATION» may be caused by a file system error or by bad sectors in your disk. The command CHKDSK will check the disk for file system errors and bad sectors. Using the setting /f will make the program to automatically correct the detected errors, and the setting /r allows finding and fixing problem disk sectors. To launch it, follow these steps:

Check for Errors The Disk Where Windows Is Installed By Using The Command chkdsk c: /f
  1. Press Windows, then enter CMD from the keyboard.

  2. Right-click on CMD and launch it as administrator.

  3. In the command prompt window type chkdsk c: /f and press Enter (use the letter of the drive where your OS is installed).

Wait until the process is over and restart your computer.

Use The Mode of Compatibility With an Old Version of Windows

A error with the code «KERNEL_THREAD_PRIORITY_FLOOR_VIOLATION» may be caused by outdated software. If this error occurs after launching a program, then using Windows compatibility mode can help you get rid of the problem. To fix it, do the following:

Use The Mode of Compatibility With an Old Version of Windows
  1. Find a program executable file (it has .exe extension) and right-click on it.

  2. In the quick menu, select Troubleshoot compatibility.

  3. At the next stage, you will see the window Program Compatibility Troubleshooter. You will have two troubleshooting options to choose from:

    • Try recommended settings. Select this variant to start a test run of the program using recommended compatibility settings.

    • Troubleshoot program. Select this variant to choose compatibility settings based on what problems you have encountered.

  4. After testing the program under various versions of Windows and startup settings save the suitable settings for your program.

Setup compatibility mode
Check errors
Setup Windows version


Go to view

How to Run a Program in Compatibility Mode With Windows 10, 8 and 7


How to Run a Program in Compatibility Mode With Windows 10, 8 and 7

Disable Unnecessary Programs in Windows Startup Menu

The software causing «KERNEL_THREAD_PRIORITY_FLOOR_VIOLATION» (0x00000157) may be written to Windows Startup list so the error occurs immediately after the system starts without any user activity. You can delete programs from Startup by using Task Manager.

Disable Unnecessary Programs in Windows Startup Menu
  1. Load the computer in Safe Mode.

  2. Right-click on Task Bar and then on Task Manager.

  3. Go to Startup tab.

  4. To delete a program from the startup list select it and disable by clicking Disable in the right lower corner of the window.

Consult Microsoft Support Service

Microsoft offers several solutions to eliminate the blue screen error. «KERNEL_THREAD_PRIORITY_FLOOR_VIOLATION» (0x00000157) can be fixed with the help of Windows Update or by addressing Windows Support.

Consult Microsoft Support Service
  1. Go to Microsoft Support Service.

  2. Enter your error code and message into the search field and follow the directions.

  3. If you don’t find a ready solution as the community where your query can be answered by a certified system administrator.

Install Latest System Updates

Windows provides updates that extend your driver database and correct errors or security vulnerabilities. Download the latest updates to get rid of the error «KERNEL_THREAD_PRIORITY_FLOOR_VIOLATION» (0x00000157).

Install Latest System Updates

You can launch Windows Update like this:

  1. Go to Start menu and select Settings.

  2. In the Settings window go to Update and Security tab.

  3. To install the latest Windows updates click on Check for updates and wait until they are found and installed.

Set up automatic download and installation of system updates

It is recommended to set up automatic download and installation of system updates with the help of Advanced Options.

To enable automatic system update you need to start Windows Update:

  1. Go to Start menu and choose Settings.

  2. In the Settings window go to the Update and Security menu and select Windows Update. To install the latest Windows updates click on Check for updates and wait until they are found and installed.

  3. Go to Advanced Options and choose the mode of update installation — Automatic.

Scan The System For Viruses

The blue screen of death with the error «KERNEL_THREAD_PRIORITY_FLOOR_VIOLATION» 0x00000157 can be caused by computer viruses that infected your system.

To check the computer for viruses launch your antivirus program.

Modern antiviruses allow checking both hard disks and RAM. Run a full system scan.

Test Your RAM

System memory problems may cause errors, loss of data or even make your computer stop working.

Before you start checking RAM, take it out of the slot on the motherboard and then stick it back again. Sometimes the error «KERNEL_THREAD_PRIORITY_FLOOR_VIOLATION» can be caused by the memory stick which was set into the slot incorrectly or not tight enough, and sometimes by the slot contacts covered with dust.

If the above actions did not make things better, you can check your RAM with the means of your operating system – Windows Memory Diagnostic.

JYou can start this tool in two ways:

  1. With the help of Control Panel:

    Start Windows Memory Diagnostic with Control Panel

    Go to Control Panel / System and Security / Administrative Tools. Launch the application Windows Memory Diagnostic.

  2. With the use of Run:

    With the use of Run

    Launch the Run tool with the combination of keys Windows + R. Type in mdsched and press Enter. The Windows Diagnostic tool will start.

To start the checking select one of the suggested variants to decide how your RAM will be tested after the computer is restarted.

If the diagnostic tool finds errors that cannot be corrected, such memory should be replaced (that is, you have to replace the memory stick where errors were found).

Make a Clean Installation of Windows

If none of the methods helped you to get rid of «KERNEL_THREAD_PRIORITY_FLOOR_VIOLATION», try reinstalling Windows. In order to make a clean installation of Windows you need to create a setup disk or another media which you are going to use to install the OS.

Start the computer with the setup disk. To do it you may need to change boot priority in BIOS or UEFI for newer computers.

Following the installer menu stages, specify the disk where you want your Windows installed. You will have to format it then. If you are not satisfied with the number or size of the local disks they can be deleted and repartitioned.

Remember that formatting, deleting or partitioning your disks will destroy all files in the hard disk.

After specifying the disk to install Windows to, the process of copying system files and installing the operating system will start. During the installation, no additional action is required. In the process, the screen will go off for a while several times, and the computer will restart on its own to complete certain stages of installation.

Depending on the version of Windows at one of the stages you may have to select or enter basic personalization settings, choose how the computer works with networks and select settings of your account or create a new one.

As the computer loads the desktop, a clean installation of Windows is finished.

Note. Before you start a clean installation of Windows make sure you have drivers for all your hardware and that your files are safe. Download and save drivers to a separate media, and create a backup copy of important data.


Go to view

How to Reset Windows 10 or 8 PC to Factory Default Settings (All Methods)


How to Reset Windows 10 or 8 PC to Factory Default Settings (All Methods)


Go to view

How to Reset Windows 10 or 8 PC If The Operating System Won't Boot


How to Reset Windows 10 or 8 PC If The Operating System Won’t Boot

title description keywords ms.date topic_type api_name api_type

Bug Check 0x157 KERNEL_THREAD_PRIORITY_FLOOR_VIOLATION

The ATTEMPTED_SWITCH_FROM_DPC bug check has a value of 0x00000157. This indicates that an illegal operation was attempted on the priority floor of a particular thread.

Bug Check 0x157 KERNEL_THREAD_PRIORITY_FLOOR_VIOLATION

KERNEL_THREAD_PRIORITY_FLOOR_VIOLATION

05/23/2017

apiref

KERNEL_THREAD_PRIORITY_FLOOR_VIOLATION

NA

Bug Check 0x157: KERNEL_THREAD_PRIORITY_FLOOR_VIOLATION

The ATTEMPTED_SWITCH_FROM_DPC bug check has a value of 0x00000157. This indicates that an illegal operation was attempted on the priority floor of a particular thread.

[!IMPORTANT]
This topic is for programmers. If you are a customer who has received a blue screen error code while using your computer, see Troubleshoot blue screen errors.

KERNEL_THREAD_PRIORITY_FLOOR_VIOLATION Parameters

Parameter Description
1 The address of the thread
2 The target priority value
3

A status code indicating the nature of the violation

0x1 : The priority counter for the target priority over-flowed
0x2 : The priority counter for the target priority under-flowed
0x3 : The target priority value was illegal

4 Reserved

Синий экран смерти 0x00000157 означает, что была предпринята попытка запрещенной операции на уровне приоритета конкретного потока.

Данная ошибка встречается крайне редко.

Параметры KERNEL_THREAD_PRIORITY_FLOOR_VIOLATION:

Img

РЕШЕНИЕ

ОБЩИЕ СВЕДЕНИЯ ОБ АВАРИЙНОМ ДАМПЕ ПАМЯТИ
Все Windows-системы при обнаружении фатальной ошибки делают аварийный дамп (снимок) содержимого оперативной памяти и сохраняет его на жесткий диск. Существуют три типа дампа памяти:

Полный дамп памяти – сохраняет все содержимое оперативной памяти. Размер снимка равен размеру оперативной памяти + 1 Мб (заголовок). Используется очень редко, так как в системах с большим объемом памяти размер дампа будет слишком большим.

Дамп памяти ядра – сохраняет информацию оперативной памяти, касающуюся только режима ядра. Информация пользовательского режима не сохраняется, так как не несет в себе информации о причине краха системы. Объем файла дампа зависит от размера оперативной памяти и варьируется от 50 Мб (для систем с 128 Мб оперативной памяти) до 800 Мб (для систем с 8 Гб оперативной памяти).

Малый дамп памяти (мини дамп) – содержит довольно небольшое количество информации: код ошибки с параметрами, список драйверов загруженных в оперативную память на момент краха системы и т.д., но этих сведений достаточно, для определения сбойного драйвера. Еще одним преимуществом данного вида дампа является маленький размер файла.

или

Для устранения ошибки воспользуйтесь одним или несколькими способами.

1. Сперва необходимо проверите наличие свободного места на системном разделе жесткого диска. Если свободного места мало, то необходимо его увеличить, удалив ненужные данные;

2. Просканируйте операционную систему антивирусными программами для удаления всевозможного нежелательного программного обеспечения, коими являются вирусы, трояны и т.д.;

3. Большое количество BSoD появляется вследствие ошибок кода самой операционной системы. Компания Microsoft постоянно работает над исправлением таких ошибок, выпуская патчи и пакеты обновления. Установленный последний пакет обновлений (Service pack) и постоянное обновление системы избавят от большого количества ошибок. Рекомендую установить радиокнопку автоматического обновления системы.

4. Если ошибка появилась после недавно установленного драйвера устройства или программы. Необходимо откатить драйвер на более раннюю версию. С программами дела обстоят проще, их удаление устранит причину сбоя. Может пригодиться опция “Запуск последней удачной конфигурации” системы.

5. Если синий экран начал появляться после того как Вы подключили новое устройство к системе, то необходимо проверить его на совместимость с Вашей операционной системой. Если устройство совместимо, то необходимо скачать свежие драйвера с официального сайта производителя и установить их. Если установлена последняя версия драйверов, то необходимо установить более раннюю версию драйверов. Если устройство несовместимо с операционной системой, то необходимо, либо поменять данное устройство, либо поменять операционную систему, поддерживающую данное устройство.

6. Установите настройки BIOS по умолчанию. Неправильные настройки BIOSа могут привести к печальным последствиям. И экран смерти это не самый худший вариант. Если Вы не уверенны в своих навыках, то в BIOSе лучше ничего не менять.

7. Очень часто причиной появления BSoD является неисправность оперативной памяти. Для её проверки можно использовать тестирующие программы, например memtest86+. В случае выявления битой линейки памяти, её необходимо заменить. При использовании в компьютере двух планок памяти и более, устранение неисправной устранит сбой.

8. Проверьте жесткий диск на наличие битых секторов и ошибок. По возможности исправьте ошибки и восстановите битые сектора стандартными средствами системы.

9. Необходимо избавиться от перегрева компонентов ПК. Почистите Ваш компьютер от пыли, смажьте специальным маслом все кулеры (процессорный, чипсетный, видеокарты, блока питания). При необходимости, установите дополнительные кулера, для организации правильного потока воздуха в системном блоке.

10. Проверьте правильность подключения кабелей и комплектующих. Посмотрите на их контакты, при необходимости смажьте их.

11. Переустановите операционную систему. Используйте только лицензионный диск операционной системы. Использование различных сборок приводит к постоянным проблемам.
———

В благодарность за информацию посмотрите рекламу, может что-то заинтересует) Отключите антибаннер в вашем браузере.



Apr 7, 2020



8



0



10

0


  • #1

I’m having constant BSOD after going back to my old GPU — here’s some background.

Specs are:
Ryzen 5 3600
MSI B450 Tomahawk
16GB DDR4 3200mhz HyperX Predator
500GB Crucial MX500 SSD
Gigabyte GTX 960 4GB Windforce
EVGA 500w PSU

I bought a new GPU last week (MSI Radeon RX 5600 XT Mech OC), I had what seems to be very common issues with AMD cards at the moment — black screen when playing games and a blue screen or two. I tried several fixes I found online including uninstalling all Nvidia drivers using display driver uninstaller and updating motherboard BIOS, none of them helped. Just before I made the decision to return the GPU I got BSOD a couple of times with different stop codes. I put my old GPU in and the blue screens continued. I removed the old AMD drivers, by uninstalling the AMD software and using DDU and I installed the Nvidia drivers but this didn’t help. After, again, trying a few fixes I decided to do a clean install of Windows 10. Unfortunately this hasn’t helped and the blue screens continue, tried lots of different fixes and nothing seems to help.

Even after resetting Windows I still get a variety of codes including:

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
PAGE_FAULT_IN_NONPAGES_AREA
KERNEL_AUTO_BOOST_LOCK_AQUISITION_WITH_RAISED_IRQL
KERNEL_SECURITY_CHECK_FAILURE
APC_INDEX_MISMATCH
KERNEL_THREAD_PRIORITY_FLOOR_VIOLATION

Blue screen doesn’t seem to happen at any specific time, just when I do anything, usually within a minute of booting. Safe mode seems to be fine.

Would really appreciate any advice you can give me.

Colif



Jun 12, 2015



61,162



5,187



166,290

10,454


  • #2

KERNEL_AUTO_BOOST_LOCK_AQUISITION_WITH_RAISED_IRQL — i have seen this caused by LAN drivers.
KERNEL_THREAD_PRIORITY_FLOOR_VIOLATION — this is a new one… can’t say I seen this before.

Can you follow option one on the following link — here — and then do this step below: Small memory dumps — Have Windows Create a Small Memory Dump (Minidump) on BSOD — that creates a file in c windows/minidump after the next BSOD

copy that file to documents

upload the copy from documents to a file sharing web site, and share the link in your thread so we can help fix the problem

after reset? Have you updated drivers on motherboard? Have you run MSI Dragon Centre as I believe it updates drivers for you — https://www.msi.com/Motherboard/support/B450-TOMAHAWK#down-driver&Win10 64



Apr 7, 2020



8



0



10

0


  • #3

KERNEL_AUTO_BOOST_LOCK_AQUISITION_WITH_RAISED_IRQL — i have seen this caused by LAN drivers.
KERNEL_THREAD_PRIORITY_FLOOR_VIOLATION — this is a new one… can’t say I seen this before.

Can you follow option one on the following link — here — and then do this step below: Small memory dumps — Have Windows Create a Small Memory Dump (Minidump) on BSOD — that creates a file in c windows/minidump after the next BSOD

copy that file to documents

upload the copy from documents to a file sharing web site, and share the link in your thread so we can help fix the problem

after reset? Have you updated drivers on motherboard? Have you run MSI Dragon Centre as I believe it updates drivers for you — https://www.msi.com/Motherboard/support/B450-TOMAHAWK#down-driver&Win10 64

Thanks for the reply, here are the files, I included the last two from today:
https://www.dropbox.com/sh/bo1l70hsfcjcdix/AABk2Co7lzm6e3dEMVeYGrY9a?dl=0

Yes, I did update the motherboard drivers after reinstalling windows.

gardenman



Jun 16, 2016



4,116



453



18,090

641


  • #4

Hi, I ran the dump files through the debugger and got the following information: https://dreamiestleaftailedgecko.htmlpasta.com/

File information: 040820-6484-01.dmp (Apr 8 2020 — 10:28:03)
Bugcheck: CLOCK_WATCHDOG_TIMEOUT (101)
Probably caused by: memory_corruption (Process: System)
Uptime: 0 Day(s), 0 Hour(s), 02 Min(s), and 05 Sec(s)

Possible Motherboard page: https://www.msi.com/Motherboard/B450-TOMAHAWK
You have the latest BIOS already installed, version 1.D.

This information can be used by others to help you. I can’t help you with this. Someone else will post with more information. Please wait for additional answers. Good luck.



Apr 7, 2020



8



0



10

0


gardenman



Jun 16, 2016



4,116



453



18,090

641


  • #6

When did you start using Verifier? It’s turned on. It’s job is to stress drivers out until they crash.

Colif



Jun 12, 2015



61,162



5,187



166,290

10,454


  • #7

Driver Verifer — its always turned on, It just doesn’t often appear in errors.Volume shadow copy crashed? that is the process that is otherwise known as System restore…

wonder what would cause that…
motherboard website has realtek audio drivers but actual system is showing AMD HD Audio, I am not sure if thats part of the GPU drivers. Or if it was installed by windows as some of these are defaults.
Newer LAN drivers on MSI website — https://www.msi.com/Motherboard/support/B450-TOMAHAWK#down-driver&Win10 64

All but one of the drivers running are from AMD.
The chipset drivers might be latest, the ones on MSI site are 1 month newer than whats installed, that is within range of being the same.

Try running memtest86 on each of your ram sticks, one stick at a time, up to 4 passes. Only error count you want is 0, any higher could be cause of the BSOD. Remove/replace ram sticks with errors. (just to remove it as a possible cause as if i see weird errors like this, I should check ram)

gardenman



Jun 16, 2016



4,116



453



18,090

641


  • #8

The reason I asked is because Driver Verifier usually doesn’t have that many switches turned on. Compare «Extra 1» in his dumps to other dumps. There was also a VERIFIER bugcheck. Therefore I assume verifier is «on» when it’s usually «off».



Apr 7, 2020



8



0



10

0


  • #9

The reason I asked is because Driver Verifier usually doesn’t have that many switches turned on. Compare «Extra 1» in his dumps to other dumps. There was also a VERIFIER bugcheck. Therefore I assume verifier is «on» when it’s usually «off».

I had actually turned on verifier shortly before.



Apr 7, 2020



8



0



10

0


  • #10

Driver Verifer — its always turned on, It just doesn’t often appear in errors.Volume shadow copy crashed? that is the process that is otherwise known as System restore…

wonder what would cause that…
motherboard website has realtek audio drivers but actual system is showing AMD HD Audio, I am not sure if thats part of the GPU drivers. Or if it was installed by windows as some of these are defaults.
Newer LAN drivers on MSI website — https://www.msi.com/Motherboard/support/B450-TOMAHAWK#down-driver&Win10 64

All but one of the drivers running are from AMD.
The chipset drivers might be latest, the ones on MSI site are 1 month newer than whats installed, that is within range of being the same.

Try running memtest86 on each of your ram sticks, one stick at a time, up to 4 passes. Only error count you want is 0, any higher could be cause of the BSOD. Remove/replace ram sticks with errors. (just to remove it as a possible cause as if i see weird errors like this, I should check ram)

I’ve installed the newer LAN drivers and chipset drivers, no help unfortunately.

I also ran memtest86 on each stick for 4 passes with 0 errors.

Colif



Jun 12, 2015



61,162



5,187



166,290

10,454


  • #11

Please share any new dumps you get as more info the better.
Have you installed all the software for the hardware in PC? Just wondering if its a device that just doesn’t have any drivers yet.

BSOD that survive installs normally signal that its hardware, not software.

I am not sure if this includes tests for ssd — https://www.crucial.com/support/storage-executive



Apr 7, 2020



8



0



10

0


  • #12

Please share any new dumps you get as more info the better.
Have you installed all the software for the hardware in PC? Just wondering if its a device that just doesn’t have any drivers yet.

BSOD that survive installs normally signal that its hardware, not software.

I am not sure if this includes tests for ssd — https://www.crucial.com/support/storage-executive

After downloading the crucial software and getting new dumps I now can’t seem to restart into safe mode, restarting just goes to a black screen then eventually goes to the blue screen with stop code driver power state failure. Also, when I try to shut down it goes to black screen and then eventually just restarts. Not being able to boot into safe mode means it’s difficult to do anything as booting normally just leads to a blue screen after about a minute.

Managed to save the dump files from yesterday.

https://www.dropbox.com/sh/5oaaz90and76vvw/AACnKL9dH8JAsK484EJq46CXa?dl=0

Colif



Jun 12, 2015



61,162



5,187



166,290

10,454


gardenman



Jun 16, 2016



4,116



453



18,090

641


  • #14

I ran the dump files through the debugger and got the following information: https://zenithalmonth.htmlpasta.com/

This information can be used by others to help you. I can’t help you with this. Someone else will post with more information. Please wait for additional answers. Good luck.

Colif



Jun 12, 2015



61,162



5,187



166,290

10,454


  • #15

Wonders if saying GPU wasn’t problem was over reaching. It could be it just creates different errors. I assume that ryzen doesn’t have graphics cores (only as if it did we could run without a gpu).

the blank screens at startup should have been a clue.

The kernel auto boost lock acquisition with raised irq error appears to be GPU error. one of the commands run just before errors was using WIn 10 Graphics Device Interface.

Its not a normal error (even for ATI cards, I normally see another one). Its impossible to blame anyone apart from AMD for these errors though given its all you have running. And its difficult to tell which are installed by windows as it includes some by default

Mar 19 2015 amd_sata.sys AMD SATA Controller AHCI Device driver http://support.amd.com/
Mar 19 2015 amd_xata.sys AMD Stor Filter driver http://support.amd.com/
Mar 14 2016 amdgpio3.sys AMD GPIO Controller Driver from Advanced Micro Devices http://support.amd.com/
May 17 2019 amdgpio2.sys AMD GPIO Controller Driver from Advanced Micro Devices http://support.amd.com/
Jun 19 2019 amdpsp.sys Advanced Micro Devices, Inc http://support.amd.com/
Jul 24 2019 AMDPCIDev.sys Advanced Micro Devices PCI Device driver
Nov 15 2019 AtihdWT6.sys AMD High Definition Audio Function driver http://support.amd.com/
Nov 18 2019 rt640x64.sys Realtek NICDRV 8169 PCIe GBE Family Controller driver https://www.realtek.com/en/
Apr 01 2020 atikmdag.sys ATI Radeon Kernel Mode driver
Apr 01 2020 atikmpag.sys ATI video card driver

I think you need to uninstall the AMD display drivers in windows since it won’t load safe mode. See if it stops the BSOD after startup effect.

Or put the Nvidia card back in and see if that makes any difference. I know it didn’t last time.
Changing GPU shouldn’t cause BSOD, but it might have changed how the systems power draw was balanced and it might be something else is failing. When I upgraded from a 960 to a 980 (yeah, I know, massive) my screen randomly stopped loading desktop at startup. It was after troubleshooting including reinstalling win 10 , that I figured out cause was my speakers weren’t responding at startup and delaying desktop. So just little changes can set off other parts that had worked perfectly fine (for 15 years)

or get pc repaired… If it was a perfect world and we were able to travel freely to a shop and ask them to figure out whats wrong.



Apr 7, 2020



8



0



10

0


  • #16

Wonders if saying GPU wasn’t problem was over reaching. It could be it just creates different errors. I assume that ryzen doesn’t have graphics cores (only as if it did we could run without a gpu).

the blank screens at startup should have been a clue.

The kernel auto boost lock acquisition with raised irq error appears to be GPU error. one of the commands run just before errors was using WIn 10 Graphics Device Interface.

Its not a normal error (even for ATI cards, I normally see another one). Its impossible to blame anyone apart from AMD for these errors though given its all you have running. And its difficult to tell which are installed by windows as it includes some by default

Mar 19 2015 amd_sata.sys AMD SATA Controller AHCI Device driver http://support.amd.com/
Mar 19 2015 amd_xata.sys AMD Stor Filter driver http://support.amd.com/
Mar 14 2016 amdgpio3.sys AMD GPIO Controller Driver from Advanced Micro Devices http://support.amd.com/
May 17 2019 amdgpio2.sys AMD GPIO Controller Driver from Advanced Micro Devices http://support.amd.com/
Jun 19 2019 amdpsp.sys Advanced Micro Devices, Inc http://support.amd.com/
Jul 24 2019 AMDPCIDev.sys Advanced Micro Devices PCI Device driver
Nov 15 2019 AtihdWT6.sys AMD High Definition Audio Function driver http://support.amd.com/
Nov 18 2019 rt640x64.sys Realtek NICDRV 8169 PCIe GBE Family Controller driver https://www.realtek.com/en/
Apr 01 2020 atikmdag.sys ATI Radeon Kernel Mode driver
Apr 01 2020 atikmpag.sys ATI video card driver

I think you need to uninstall the AMD display drivers in windows since it won’t load safe mode. See if it stops the BSOD after startup effect.

Or put the Nvidia card back in and see if that makes any difference. I know it didn’t last time.
Changing GPU shouldn’t cause BSOD, but it might have changed how the systems power draw was balanced and it might be something else is failing. When I upgraded from a 960 to a 980 (yeah, I know, massive) my screen randomly stopped loading desktop at startup. It was after troubleshooting including reinstalling win 10 , that I figured out cause was my speakers weren’t responding at startup and delaying desktop. So just little changes can set off other parts that had worked perfectly fine (for 15 years)

or get pc repaired… If it was a perfect world and we were able to travel freely to a shop and ask them to figure out whats wrong.

In response to your last two messages.

Don’t think the crucial software fully installed before the additional problems happened (not being able to boot into safe mode etc.), it was listed in the start menu but not in the list of installed programs. Also, not convinced it can be an SSD problem as i installed windows on my HDD and was still getting BSOD.

PSU — I checked the bios and 5v is 5.050 and 12v is 12.216 — there was no 3.3v at all under the PC Health Status section.

I ran the Marsenne Prime Test v28 and was still running after 24 hours with no crashes.

Took your advice and removed the 5600XT and put the 960 back in, removed AMD drivers and reinstalled the Nvidia drivers, the PC now seems to be improved and is now running for longer. The first time I started the PC I managed to install Origin and i ran Geforce Now for a while and tried to load a game, was in the queue for a while and then it blue screened. Have just restarted and done some browsing and typed this message without a blue screen (then I opened notepad and it blue screened). I now seem to be able to boot into safe mode.

After putting back in the 960 I installed Sysnative and ran it, here is the result — https://www.dropbox.com/sh/z500dg9fowrckmk/AABqy5ygQdfH5EYGAYIdU0eGa?dl=0

Let me know if you have any more thoughts but understand I may need to take it to a shop when this is all over.



Apr 7, 2020



8



0



10

0


gardenman



Jun 16, 2016



4,116



453



18,090

641


  • #18

I ran the dump files through the debugger and got the following information: https://incorruptibis.htmlpasta.com/

File information: 041220-4156-01 — Copy.dmp (Apr 12 2020 — 11:34:21)
Bugcheck: IRQL_NOT_LESS_OR_EQUAL (A)
Probably caused by: memory_corruption (Process: System)
Uptime: 0 Day(s), 0 Hour(s), 13 Min(s), and 03 Sec(s)

File information: 041220-4187-01 — Copy.dmp (Apr 12 2020 — 12:02:51)
Bugcheck: IRQL_NOT_LESS_OR_EQUAL (A)
Probably caused by: memory_corruption (Process: System)
Uptime: 0 Day(s), 0 Hour(s), 27 Min(s), and 59 Sec(s)

File information: 041220-4640-01 — Copy.dmp (Apr 12 2020 — 12:19:27)
Bugcheck: IRQL_NOT_LESS_OR_EQUAL (A)
Probably caused by: ntkrnlmp.exe (Process: firefox.exe)
Uptime: 0 Day(s), 0 Hour(s), 10 Min(s), and 08 Sec(s)

This information can be used by others to help you. I can’t help you with this. Someone else will post with more information. Please wait for additional answers. Good luck.

Thread starter Similar threads Forum Replies Date

N

Question Constant BSOD since reinstalling Windows, please help. Windows 10 3 Jan 4, 2023

3

Question Win10 constant blue screens Windows 10 6 Dec 16, 2022

R

Question System is constantly crashing Windows 10 1 Oct 24, 2022

F

Question Constant Boot Blue Screens Windows 10 23 Oct 10, 2022

P

Question System constantly running into STATUS_ACCESS_VIOLATIONS Windows 10 11 Aug 25, 2022

V

Question Constant BSODs After Windows Reinstall Windows 10 2 Jun 2, 2022

B

[SOLVED] Constant BSOD While Gaming for Past 7 Months, Tried Hardware Swap, Troubleshooting, no Minidump, Custom Watercooling Windows 10 16 Jun 1, 2022

S

[SOLVED] Constant Blue Screening since upgrading to Windows 10, tried many online fixes with no luck Windows 10 3 Apr 11, 2022

aarock1234

[SOLVED] Constant BSOD with DIFFERENT causes. Windows 10 3 Mar 23, 2022

Caelik

Question Constant BSOD after fresh Windows 10 install ? Windows 10 1 Feb 14, 2022

  • Advertising
  • Cookies Policies
  • Privacy
  • Term & Conditions
  • Topics



Apr 7, 2020



8



0



10

0


  • #1

I’m having constant BSOD after going back to my old GPU — here’s some background.

Specs are:
Ryzen 5 3600
MSI B450 Tomahawk
16GB DDR4 3200mhz HyperX Predator
500GB Crucial MX500 SSD
Gigabyte GTX 960 4GB Windforce
EVGA 500w PSU

I bought a new GPU last week (MSI Radeon RX 5600 XT Mech OC), I had what seems to be very common issues with AMD cards at the moment — black screen when playing games and a blue screen or two. I tried several fixes I found online including uninstalling all Nvidia drivers using display driver uninstaller and updating motherboard BIOS, none of them helped. Just before I made the decision to return the GPU I got BSOD a couple of times with different stop codes. I put my old GPU in and the blue screens continued. I removed the old AMD drivers, by uninstalling the AMD software and using DDU and I installed the Nvidia drivers but this didn’t help. After, again, trying a few fixes I decided to do a clean install of Windows 10. Unfortunately this hasn’t helped and the blue screens continue, tried lots of different fixes and nothing seems to help.

Even after resetting Windows I still get a variety of codes including:

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
PAGE_FAULT_IN_NONPAGES_AREA
KERNEL_AUTO_BOOST_LOCK_AQUISITION_WITH_RAISED_IRQL
KERNEL_SECURITY_CHECK_FAILURE
APC_INDEX_MISMATCH
KERNEL_THREAD_PRIORITY_FLOOR_VIOLATION

Blue screen doesn’t seem to happen at any specific time, just when I do anything, usually within a minute of booting. Safe mode seems to be fine.

Would really appreciate any advice you can give me.

Colif



Jun 12, 2015



61,162



5,187



166,290

10,454


  • #2

KERNEL_AUTO_BOOST_LOCK_AQUISITION_WITH_RAISED_IRQL — i have seen this caused by LAN drivers.
KERNEL_THREAD_PRIORITY_FLOOR_VIOLATION — this is a new one… can’t say I seen this before.

Can you follow option one on the following link — here — and then do this step below: Small memory dumps — Have Windows Create a Small Memory Dump (Minidump) on BSOD — that creates a file in c windows/minidump after the next BSOD

copy that file to documents

upload the copy from documents to a file sharing web site, and share the link in your thread so we can help fix the problem

after reset? Have you updated drivers on motherboard? Have you run MSI Dragon Centre as I believe it updates drivers for you — https://www.msi.com/Motherboard/support/B450-TOMAHAWK#down-driver&Win10 64



Apr 7, 2020



8



0



10

0


  • #3

KERNEL_AUTO_BOOST_LOCK_AQUISITION_WITH_RAISED_IRQL — i have seen this caused by LAN drivers.
KERNEL_THREAD_PRIORITY_FLOOR_VIOLATION — this is a new one… can’t say I seen this before.

Can you follow option one on the following link — here — and then do this step below: Small memory dumps — Have Windows Create a Small Memory Dump (Minidump) on BSOD — that creates a file in c windows/minidump after the next BSOD

copy that file to documents

upload the copy from documents to a file sharing web site, and share the link in your thread so we can help fix the problem

after reset? Have you updated drivers on motherboard? Have you run MSI Dragon Centre as I believe it updates drivers for you — https://www.msi.com/Motherboard/support/B450-TOMAHAWK#down-driver&Win10 64

Thanks for the reply, here are the files, I included the last two from today:
https://www.dropbox.com/sh/bo1l70hsfcjcdix/AABk2Co7lzm6e3dEMVeYGrY9a?dl=0

Yes, I did update the motherboard drivers after reinstalling windows.

gardenman



Jun 16, 2016



4,116



453



18,090

641


  • #4

Hi, I ran the dump files through the debugger and got the following information: https://dreamiestleaftailedgecko.htmlpasta.com/

File information: 040820-6484-01.dmp (Apr 8 2020 — 10:28:03)
Bugcheck: CLOCK_WATCHDOG_TIMEOUT (101)
Probably caused by: memory_corruption (Process: System)
Uptime: 0 Day(s), 0 Hour(s), 02 Min(s), and 05 Sec(s)

Possible Motherboard page: https://www.msi.com/Motherboard/B450-TOMAHAWK
You have the latest BIOS already installed, version 1.D.

This information can be used by others to help you. I can’t help you with this. Someone else will post with more information. Please wait for additional answers. Good luck.



Apr 7, 2020



8



0



10

0


gardenman



Jun 16, 2016



4,116



453



18,090

641


  • #6

When did you start using Verifier? It’s turned on. It’s job is to stress drivers out until they crash.

Colif



Jun 12, 2015



61,162



5,187



166,290

10,454


  • #7

Driver Verifer — its always turned on, It just doesn’t often appear in errors.Volume shadow copy crashed? that is the process that is otherwise known as System restore…

wonder what would cause that…
motherboard website has realtek audio drivers but actual system is showing AMD HD Audio, I am not sure if thats part of the GPU drivers. Or if it was installed by windows as some of these are defaults.
Newer LAN drivers on MSI website — https://www.msi.com/Motherboard/support/B450-TOMAHAWK#down-driver&Win10 64

All but one of the drivers running are from AMD.
The chipset drivers might be latest, the ones on MSI site are 1 month newer than whats installed, that is within range of being the same.

Try running memtest86 on each of your ram sticks, one stick at a time, up to 4 passes. Only error count you want is 0, any higher could be cause of the BSOD. Remove/replace ram sticks with errors. (just to remove it as a possible cause as if i see weird errors like this, I should check ram)

gardenman



Jun 16, 2016



4,116



453



18,090

641


  • #8

The reason I asked is because Driver Verifier usually doesn’t have that many switches turned on. Compare «Extra 1» in his dumps to other dumps. There was also a VERIFIER bugcheck. Therefore I assume verifier is «on» when it’s usually «off».



Apr 7, 2020



8



0



10

0


  • #9

The reason I asked is because Driver Verifier usually doesn’t have that many switches turned on. Compare «Extra 1» in his dumps to other dumps. There was also a VERIFIER bugcheck. Therefore I assume verifier is «on» when it’s usually «off».

I had actually turned on verifier shortly before.



Apr 7, 2020



8



0



10

0


  • #10

Driver Verifer — its always turned on, It just doesn’t often appear in errors.Volume shadow copy crashed? that is the process that is otherwise known as System restore…

wonder what would cause that…
motherboard website has realtek audio drivers but actual system is showing AMD HD Audio, I am not sure if thats part of the GPU drivers. Or if it was installed by windows as some of these are defaults.
Newer LAN drivers on MSI website — https://www.msi.com/Motherboard/support/B450-TOMAHAWK#down-driver&Win10 64

All but one of the drivers running are from AMD.
The chipset drivers might be latest, the ones on MSI site are 1 month newer than whats installed, that is within range of being the same.

Try running memtest86 on each of your ram sticks, one stick at a time, up to 4 passes. Only error count you want is 0, any higher could be cause of the BSOD. Remove/replace ram sticks with errors. (just to remove it as a possible cause as if i see weird errors like this, I should check ram)

I’ve installed the newer LAN drivers and chipset drivers, no help unfortunately.

I also ran memtest86 on each stick for 4 passes with 0 errors.

Colif



Jun 12, 2015



61,162



5,187



166,290

10,454


  • #11

Please share any new dumps you get as more info the better.
Have you installed all the software for the hardware in PC? Just wondering if its a device that just doesn’t have any drivers yet.

BSOD that survive installs normally signal that its hardware, not software.

I am not sure if this includes tests for ssd — https://www.crucial.com/support/storage-executive



Apr 7, 2020



8



0



10

0


  • #12

Please share any new dumps you get as more info the better.
Have you installed all the software for the hardware in PC? Just wondering if its a device that just doesn’t have any drivers yet.

BSOD that survive installs normally signal that its hardware, not software.

I am not sure if this includes tests for ssd — https://www.crucial.com/support/storage-executive

After downloading the crucial software and getting new dumps I now can’t seem to restart into safe mode, restarting just goes to a black screen then eventually goes to the blue screen with stop code driver power state failure. Also, when I try to shut down it goes to black screen and then eventually just restarts. Not being able to boot into safe mode means it’s difficult to do anything as booting normally just leads to a blue screen after about a minute.

Managed to save the dump files from yesterday.

https://www.dropbox.com/sh/5oaaz90and76vvw/AACnKL9dH8JAsK484EJq46CXa?dl=0

Colif



Jun 12, 2015



61,162



5,187



166,290

10,454


gardenman



Jun 16, 2016



4,116



453



18,090

641


  • #14

I ran the dump files through the debugger and got the following information: https://zenithalmonth.htmlpasta.com/

This information can be used by others to help you. I can’t help you with this. Someone else will post with more information. Please wait for additional answers. Good luck.

Colif



Jun 12, 2015



61,162



5,187



166,290

10,454


  • #15

Wonders if saying GPU wasn’t problem was over reaching. It could be it just creates different errors. I assume that ryzen doesn’t have graphics cores (only as if it did we could run without a gpu).

the blank screens at startup should have been a clue.

The kernel auto boost lock acquisition with raised irq error appears to be GPU error. one of the commands run just before errors was using WIn 10 Graphics Device Interface.

Its not a normal error (even for ATI cards, I normally see another one). Its impossible to blame anyone apart from AMD for these errors though given its all you have running. And its difficult to tell which are installed by windows as it includes some by default

Mar 19 2015 amd_sata.sys AMD SATA Controller AHCI Device driver http://support.amd.com/
Mar 19 2015 amd_xata.sys AMD Stor Filter driver http://support.amd.com/
Mar 14 2016 amdgpio3.sys AMD GPIO Controller Driver from Advanced Micro Devices http://support.amd.com/
May 17 2019 amdgpio2.sys AMD GPIO Controller Driver from Advanced Micro Devices http://support.amd.com/
Jun 19 2019 amdpsp.sys Advanced Micro Devices, Inc http://support.amd.com/
Jul 24 2019 AMDPCIDev.sys Advanced Micro Devices PCI Device driver
Nov 15 2019 AtihdWT6.sys AMD High Definition Audio Function driver http://support.amd.com/
Nov 18 2019 rt640x64.sys Realtek NICDRV 8169 PCIe GBE Family Controller driver https://www.realtek.com/en/
Apr 01 2020 atikmdag.sys ATI Radeon Kernel Mode driver
Apr 01 2020 atikmpag.sys ATI video card driver

I think you need to uninstall the AMD display drivers in windows since it won’t load safe mode. See if it stops the BSOD after startup effect.

Or put the Nvidia card back in and see if that makes any difference. I know it didn’t last time.
Changing GPU shouldn’t cause BSOD, but it might have changed how the systems power draw was balanced and it might be something else is failing. When I upgraded from a 960 to a 980 (yeah, I know, massive) my screen randomly stopped loading desktop at startup. It was after troubleshooting including reinstalling win 10 , that I figured out cause was my speakers weren’t responding at startup and delaying desktop. So just little changes can set off other parts that had worked perfectly fine (for 15 years)

or get pc repaired… If it was a perfect world and we were able to travel freely to a shop and ask them to figure out whats wrong.



Apr 7, 2020



8



0



10

0


  • #16

Wonders if saying GPU wasn’t problem was over reaching. It could be it just creates different errors. I assume that ryzen doesn’t have graphics cores (only as if it did we could run without a gpu).

the blank screens at startup should have been a clue.

The kernel auto boost lock acquisition with raised irq error appears to be GPU error. one of the commands run just before errors was using WIn 10 Graphics Device Interface.

Its not a normal error (even for ATI cards, I normally see another one). Its impossible to blame anyone apart from AMD for these errors though given its all you have running. And its difficult to tell which are installed by windows as it includes some by default

Mar 19 2015 amd_sata.sys AMD SATA Controller AHCI Device driver http://support.amd.com/
Mar 19 2015 amd_xata.sys AMD Stor Filter driver http://support.amd.com/
Mar 14 2016 amdgpio3.sys AMD GPIO Controller Driver from Advanced Micro Devices http://support.amd.com/
May 17 2019 amdgpio2.sys AMD GPIO Controller Driver from Advanced Micro Devices http://support.amd.com/
Jun 19 2019 amdpsp.sys Advanced Micro Devices, Inc http://support.amd.com/
Jul 24 2019 AMDPCIDev.sys Advanced Micro Devices PCI Device driver
Nov 15 2019 AtihdWT6.sys AMD High Definition Audio Function driver http://support.amd.com/
Nov 18 2019 rt640x64.sys Realtek NICDRV 8169 PCIe GBE Family Controller driver https://www.realtek.com/en/
Apr 01 2020 atikmdag.sys ATI Radeon Kernel Mode driver
Apr 01 2020 atikmpag.sys ATI video card driver

I think you need to uninstall the AMD display drivers in windows since it won’t load safe mode. See if it stops the BSOD after startup effect.

Or put the Nvidia card back in and see if that makes any difference. I know it didn’t last time.
Changing GPU shouldn’t cause BSOD, but it might have changed how the systems power draw was balanced and it might be something else is failing. When I upgraded from a 960 to a 980 (yeah, I know, massive) my screen randomly stopped loading desktop at startup. It was after troubleshooting including reinstalling win 10 , that I figured out cause was my speakers weren’t responding at startup and delaying desktop. So just little changes can set off other parts that had worked perfectly fine (for 15 years)

or get pc repaired… If it was a perfect world and we were able to travel freely to a shop and ask them to figure out whats wrong.

In response to your last two messages.

Don’t think the crucial software fully installed before the additional problems happened (not being able to boot into safe mode etc.), it was listed in the start menu but not in the list of installed programs. Also, not convinced it can be an SSD problem as i installed windows on my HDD and was still getting BSOD.

PSU — I checked the bios and 5v is 5.050 and 12v is 12.216 — there was no 3.3v at all under the PC Health Status section.

I ran the Marsenne Prime Test v28 and was still running after 24 hours with no crashes.

Took your advice and removed the 5600XT and put the 960 back in, removed AMD drivers and reinstalled the Nvidia drivers, the PC now seems to be improved and is now running for longer. The first time I started the PC I managed to install Origin and i ran Geforce Now for a while and tried to load a game, was in the queue for a while and then it blue screened. Have just restarted and done some browsing and typed this message without a blue screen (then I opened notepad and it blue screened). I now seem to be able to boot into safe mode.

After putting back in the 960 I installed Sysnative and ran it, here is the result — https://www.dropbox.com/sh/z500dg9fowrckmk/AABqy5ygQdfH5EYGAYIdU0eGa?dl=0

Let me know if you have any more thoughts but understand I may need to take it to a shop when this is all over.



Apr 7, 2020



8



0



10

0


gardenman



Jun 16, 2016



4,116



453



18,090

641


  • #18

I ran the dump files through the debugger and got the following information: https://incorruptibis.htmlpasta.com/

File information: 041220-4156-01 — Copy.dmp (Apr 12 2020 — 11:34:21)
Bugcheck: IRQL_NOT_LESS_OR_EQUAL (A)
Probably caused by: memory_corruption (Process: System)
Uptime: 0 Day(s), 0 Hour(s), 13 Min(s), and 03 Sec(s)

File information: 041220-4187-01 — Copy.dmp (Apr 12 2020 — 12:02:51)
Bugcheck: IRQL_NOT_LESS_OR_EQUAL (A)
Probably caused by: memory_corruption (Process: System)
Uptime: 0 Day(s), 0 Hour(s), 27 Min(s), and 59 Sec(s)

File information: 041220-4640-01 — Copy.dmp (Apr 12 2020 — 12:19:27)
Bugcheck: IRQL_NOT_LESS_OR_EQUAL (A)
Probably caused by: ntkrnlmp.exe (Process: firefox.exe)
Uptime: 0 Day(s), 0 Hour(s), 10 Min(s), and 08 Sec(s)

This information can be used by others to help you. I can’t help you with this. Someone else will post with more information. Please wait for additional answers. Good luck.

Thread starter Similar threads Forum Replies Date

N

Question Constant BSOD since reinstalling Windows, please help. Windows 10 3 Jan 4, 2023

3

Question Win10 constant blue screens Windows 10 6 Dec 16, 2022

R

Question System is constantly crashing Windows 10 1 Oct 24, 2022

F

Question Constant Boot Blue Screens Windows 10 23 Oct 10, 2022

P

Question System constantly running into STATUS_ACCESS_VIOLATIONS Windows 10 11 Aug 25, 2022

V

Question Constant BSODs After Windows Reinstall Windows 10 2 Jun 2, 2022

B

[SOLVED] Constant BSOD While Gaming for Past 7 Months, Tried Hardware Swap, Troubleshooting, no Minidump, Custom Watercooling Windows 10 16 Jun 1, 2022

S

[SOLVED] Constant Blue Screening since upgrading to Windows 10, tried many online fixes with no luck Windows 10 3 Apr 11, 2022

aarock1234

[SOLVED] Constant BSOD with DIFFERENT causes. Windows 10 3 Mar 23, 2022

Caelik

Question Constant BSOD after fresh Windows 10 install ? Windows 10 1 Feb 14, 2022

  • Advertising
  • Cookies Policies
  • Privacy
  • Term & Conditions
  • Topics

Понравилась статья? Поделить с друзьями:
  • Kernel thread priority floor violation windows 10 как исправить
  • Kernel system check failure windows 10
  • Kernel stack locked at exit windows 10
  • Kernel security check failure при установки windows 10
  • Kernel security check failure при загрузке windows 10 как исправить