Bugcheckcode 239 ошибка

Windows 10: BSOD Kernel-Power 41, BugcheckCode 239

Discus and support BSOD Kernel-Power 41, BugcheckCode 239 in Windows 10 BSOD Crashes and Debugging to solve the problem; Hi everyone,

Had a few months back quite a bit of BSOD’s while multitasking (watching videos while gaming), or when my main monitor’s power brick died…
Discussion in ‘Windows 10 BSOD Crashes and Debugging’ started by LeLedg, Mar 7, 2020.

  1. BSOD Kernel-Power 41, BugcheckCode 239

    Hi everyone,

    Had a few months back quite a bit of BSOD’s while multitasking (watching videos while gaming), or when my main monitor’s power brick died and had to rely on my second monitor until the replacement unit arrived. Had an open forum thread which I closed today. Basically I back then I was recommended to memtest my RAM, which I did on both XMP profiles, and then without XMP. All tests passed. Vid card is not OC’d, as well as CPU. All stock. Only thing «OC’d» currently is the RAM via XMP. Tonight I was just playing Escape From Tarkov while doing nothing else on my second monitor, only had a browser open to a map of the area I was playing in, and I got a new BSOD. I’m not too sure what’s the cause. Here’s the diagnostic files!

    I’m on Win 10 Pro ver. 1909 (18363.693 build)

    Many thanks!

    :)

  2. Kernel-Power event id 41. BugcheckCode 0

    Hello,

    Thank you for writing to Microsoft Community Forums.

    In-order to get more clarity on this issue and to assist you with appropriate troubleshooting steps, reply with answers to the below questions:

    1. Are you aware of any changes made on your PC, prior to this issue?
    2. Is this issue specific while playing a particular game?
    3. Which edition of Windows are you currently using?

    A Kernel Power Event 41 can occur in the following scenarios.

    Scenario 1: The computer restarts, and there is a Stop error BugcheckCode in the event data.

    Scenario 2: The computer is shut down by pressing and holding the power button.

    Scenario 3: The system randomly restarts and no Stop error BugcheckCode is listed, or the computer is completely unresponsive (hard hang).

    I suggest you refer the article on Kernel
    Power Event ID 41 and follow the steps for the scenario that is causing this error on your PC.

    Additionally, you can refer the article on Windows
    Kernel event ID 41 error «The system has rebooted without cleanly shutting down first» in Windows
    and check if that helps.

    Regards,

    Sandeep Kumar M

    Microsoft Community – Moderator

  3. BSOD Kernel-Power 41, BugcheckCode 10

    Hi LeLedg,

    Welcome to 10Forums.

    This will explain the lack of dumps.

    BSOD Kernel-Power 41, BugcheckCode 239 [​IMG]

    There do not seem to be any other records about any crashes. For now, we have to wait until another crash occurs hoping it will save a dump file.

    If you want to do something meanwhile, I would suggest to temporarily revert the overclock. Even though you have stress-tested the overclock to ensure stability, there’s no way those tests guarantee stability in every possible situation.
    Whenever we suspect a hardware issue with the GPU or CPU, for example, we suggest the same (or similar) tests to test the stability but we are aware of the limits of those tests. To be sure the overclock is not causing any problems, regardless of the tests it’s been put through, I suggest reverting the overclock while troubleshooting.

  4. BSOD Kernel-Power 41, BugcheckCode 239

    Kernel-Power event id 41. BugcheckCode 0

    Hello,

    Thank you for replying with the required information.

    What is the make and model of your PC?

    As you have mentioned that the system randomly restarts and no Stop error BugcheckCode is listed, or the computer is completely unresponsive,
    this scenario usually indicates a problem with the hardware. To help isolate the problem, I suggest you to refer the section
    Scenario 3: The system randomly restarts and no Stop error BugcheckCode is listed, or the computer is completely unresponsive (hard hang)
    from the following article on Windows Kernel event
    ID 41 error «The system has rebooted without cleanly shutting down first» in Windows
    and follow the steps mentioned in the section to isolate the cause of the issue.

    If you see that the computer generates a Stop error that contains a BugcheckCode value that is not reported in an event ID 41, change the restart behavior for the computer. To do this, follow these steps:

    1.
    Right-click My Computer, and then click
    Properties.

    2.
    Click Advanced system settings.

    3.
    Click the Advanced tab.

    4.
    In the Startup and Recovery
    section, click Settings.

    5.
    Click to clear the Automatically restart
    check box.

    If the issue persists, I suggest you to follow the methods mentioned below:

    Method 1: Perform clean boot.

    Check if any third party application is causing this issue. Refer the article on
    How to perform a clean boot in Windows
    for steps to perform clean boot.

    Note:
    A “clean boot” starts Windows with a minimal set of drivers and startup programs, so that you can determine whether a background program is interfering with your game or program.

    Your computer may temporarily lose some functionality while in a clean boot environment, however that functionality will return when you
    reset the computer to start normally after you have finished your troubleshooting.

    Method 2: Adjust PC to best performance.

    To do that,

    1.
    In the search box on the taskbar, type
    performance    , then select Adjust the appearance and performance of Windows.

    2.
    On the Visual Effects tab, select
    Adjust for best performance > Apply.

    3.
    Restart your PC and see if that speeds up your PC.

    Method 3: Check your hard disk for errors.

    To do that,

    1. Double click on This PC icon.
    2. Right-click the hard disk drive that may be damaged.
    3. Click Properties, and then click the Tools tab.
    4. Click on the Check option.
    5. Now click on the Scan Drive option.

    Regards,

    Sandeep Kumar M

    Microsoft Community – Moderator

Thema:

BSOD Kernel-Power 41, BugcheckCode 239

  1. BSOD Kernel-Power 41, BugcheckCode 239 — Similar Threads — BSOD Kernel Power

  2. BSOD Kernel-Power 41 task 63 BugcheckCode 239 / 0x000000EF

    in Windows 10 Gaming

    BSOD Kernel-Power 41 task 63 BugcheckCode 239 / 0x000000EF: Hi recently had bsod.could you check my dump pls.https://1drv.ms/u/s!Aq0c6RHX5Jy8mTKi6YOCx_AEoob8?e=YuX5mK

    https://answers.microsoft.com/en-us/windows/forum/all/bsod-kernel-power-41-task-63-bugcheckcode-239/6caa8a2a-7966-40b4-ba0b-f9ad042495de

  3. BSOD Kernel-Power 41 task 63 BugcheckCode 239 / 0x000000EF

    in Windows 10 Software and Apps

    BSOD Kernel-Power 41 task 63 BugcheckCode 239 / 0x000000EF: Hi recently had bsod.could you check my dump pls.https://1drv.ms/u/s!Aq0c6RHX5Jy8mTKi6YOCx_AEoob8?e=YuX5mK

    https://answers.microsoft.com/en-us/windows/forum/all/bsod-kernel-power-41-task-63-bugcheckcode-239/6caa8a2a-7966-40b4-ba0b-f9ad042495de

  4. BSOD Kernel-Power 41 task 63 BugcheckCode 239 / 0x000000EF

    in Windows 10 BSOD Crashes and Debugging

    BSOD Kernel-Power 41 task 63 BugcheckCode 239 / 0x000000EF: Hi recently had bsod.could you check my dump pls.https://1drv.ms/u/s!Aq0c6RHX5Jy8mTKi6YOCx_AEoob8?e=YuX5mK

    https://answers.microsoft.com/en-us/windows/forum/all/bsod-kernel-power-41-task-63-bugcheckcode-239/6caa8a2a-7966-40b4-ba0b-f9ad042495de

  5. Kernel Power 41 BugCheckCode 292

    in Windows 10 BSOD Crashes and Debugging

    Kernel Power 41 BugCheckCode 292: Recently my pc has been BSOD-ing constantly from either bootup or randomly when playing games.I need help Log Name: System Source: Microsoft-Windows-Kernel-Power Date: 7/27/2022 5:06:26 PM Event ID: 41 Task Category: 63 Level: Critical Keywords: 70368744177664,2 User: SYSTEM…

  6. BSOD Kernel-Power 4163 BugcheckCode 239

    in Windows 10 Gaming

    BSOD Kernel-Power 4163 BugcheckCode 239: About 2 weeks ago my PC started to BSOD randomly, sometimes while I was playing a game P.S. this game doesn’t take up a lot of my PC’s resources, but sometimes I wasn’t doing anything, the longest time I didn’t shut down my PC, it didn’t BSOD for about a week, but after a…

  7. BSOD Kernel-Power 4163 BugcheckCode 239

    in Windows 10 Software and Apps

    BSOD Kernel-Power 4163 BugcheckCode 239: About 2 weeks ago my PC started to BSOD randomly, sometimes while I was playing a game P.S. this game doesn’t take up a lot of my PC’s resources, but sometimes I wasn’t doing anything, the longest time I didn’t shut down my PC, it didn’t BSOD for about a week, but after a…

  8. BSOD BugcheckCode 122,360 and 239

    in Windows 10 Software and Apps

    BSOD BugcheckCode 122,360 and 239: Hey there, months ago I started to get BSOD it was kind of random and rare like every two weeks.But now the BSOD is common thing , this week only event viewer reported 15, 3 of them was the last 24 hour.I can’t find any memory dump in C/Windows/Minidump although I’ve the the…

  9. BSOD Kernel-Power Event 41 BugcheckCode 292

    in Windows 10 BSOD Crashes and Debugging

    BSOD Kernel-Power Event 41 BugcheckCode 292: Hi,

    I have been getting BSOD errors for the last 2 weeks and they have started getting more frequent by the day. 14 in the last 4 days.

    I have a laptop which I have started using with an external monitor, keyboard and a mouse Without issues for more than 2 months now. The…

  10. Critical error Kernel-power 41 (63) bugcheckcode 239 in hex(0x000000EF)

    in Windows 10 BSOD Crashes and Debugging

    Critical error Kernel-power 41 (63) bugcheckcode 239 in hex(0x000000EF): Just as it says for some reason my windows just crashes and goes into blue screen after hard reset the pc fails to do anything after it loads windows it fails to open programs and needs to be restarted again.

    I checked all over the internet for this problem and i cant even…

Users found this page by searching for:

  1. BugcheckCode 239

    ,

  2. bugcheck code 239

    ,

  3. bugcheck code 239 windows 10

    ,

  4. bugcheck 239,
  5. BugcheckCode 239


Windows 10 Forums

Источник

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and
privacy statement. We’ll occasionally send you account related emails.

Already on GitHub?
Sign in
to your account

Assignees

@DOMARS

Comments

@LuigiBruno

docs.microsoft.com

I’m troubleshooting a CRITICAL_PROCESS_DIED bugcheck (no dump file available), only a Kernel-Power event (ID 41) on a Windows Server machine: the detailed information for the event report a «BugcheckCode 239» event data.
Is that a new bugcheck not documented yet?

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

  • ID: ddc632b2-f4e1-b784-dd1e-878feac077f9
  • Version Independent ID: 7a6866f4-3333-f2d1-86d7-dbb3d00925e0
  • Content: Bug Check Code Reference — Windows drivers
  • Content Source: windows-driver-docs-pr/debugger/bug-check-code-reference2.md
  • Product: windows-hardware
  • Technology: windows-devices
  • GitHub Login: @DOMARS
  • Microsoft Alias: domars

@DOMARS

@LuigiBruno — Can you provide the first part of the !analyze output that shows the four parameters? Also can you verify the hex value of this stop code? Also we should check if this is VMWare related.

@LuigiBruno

Copy link


Contributor


Author

@LuigiBruno — Can you provide the first part of the !analyze output that shows the four parameters? Also can you verify the hex value of this stop code? Also we should check if this is VMWare related.

Hi @DOMARS.
There was no dump file, therefore I couldn’t use WinDbg.
Here’s the information from the «System» log in the Windows Event Viewer

BugcheckCode 239
BugcheckParameter1 0xffff930e74673340
BugcheckParameter2 0x0
BugcheckParameter3 0x0
BugcheckParameter4 0x0

@RAJU2529

@RAJU2529

@wdkbot. Sir, can I add some reference links to this article by creating new PR?

@LuigiBruno

docs.microsoft.com

Copy link


Contributor


Author

@DOMARS and @RAJU2529, it should be 0x000000EF (239 in decimal), definitively a CRITICAL_PROCESS_DIED bug check.

@DOMARS

  • Remove From My Forums

none

Система перезагрузилась, завершив работу с ошибками. Возможные причины ошибки: система перестала отвечать на запросы, произошел критический сбой или неожиданно отключилось питание.

  • Вопрос

  • Вообщем уже месяц мучаюсь с проблемой. И никак не могу решить.
    Система Windows Server 2012 R2

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

    1.Система перезагрузилась, завершив работу с ошибками. Возможные причины ошибки: система перестала отвечать на
    запросы, произошел критический сбой или неожиданно отключилось питание.
    Режим XLM
    — <Event xmlns=»http://schemas.microsoft.com/win/2004/08/events/event»>
    — <System>
    <Provider Name=»Microsoft-Windows-Kernel-Power» Guid=»{331C3B3A-2005-44C2-AC5E-77220C37D6B4}» /> 
    <EventID>41</EventID> 
    <Version>3</Version> 
    <Level>1</Level> 
    <Task>63</Task> 
    <Opcode>0</Opcode> 
    <Keywords>0x8000000000000002</Keywords> 
    <TimeCreated SystemTime=»2018-12-16T01:15:37.439198500Z» /> 
    <EventRecordID>669734</EventRecordID> 
    <Correlation /> 
    <Execution ProcessID=»4″ ThreadID=»8″ /> 
    <Channel>System</Channel> 
    <Computer>Central-HP</Computer> 
    <Security UserID=»S-1-5-18″ /> 
    </System>
    — <EventData>
    <Data Name=»BugcheckCode»>0</Data> 
    <Data Name=»BugcheckParameter1″>0x0</Data> 
    <Data Name=»BugcheckParameter2″>0x0</Data> 
    <Data Name=»BugcheckParameter3″>0x0</Data> 
    <Data Name=»BugcheckParameter4″>0x0</Data> 
    <Data Name=»SleepInProgress»>0</Data> 
    <Data Name=»PowerButtonTimestamp»>0</Data> 
    <Data Name=»BootAppStatus»>0</Data> 
    </EventData>
    </Event>

    2.Система перезагрузилась, завершив работу с ошибками. Возможные причины ошибки: система перестала отвечать на
    запросы, произошел критический сбой или неожиданно отключилось питание.
    Режим XLM
    — <Event xmlns=»http://schemas.microsoft.com/win/2004/08/events/event»>
    — <System>
    <Provider Name=»Microsoft-Windows-Kernel-Power» Guid=»{331C3B3A-2005-44C2-AC5E-77220C37D6B4}» /> 
    <EventID>41</EventID> 
    <Version>3</Version> 
    <Level>1</Level> 
    <Task>63</Task> 
    <Opcode>0</Opcode> 
    <Keywords>0x8000000000000002</Keywords> 
    <TimeCreated SystemTime=»2018-12-16T22:32:22.283405400Z» /> 
    <EventRecordID>670077</EventRecordID> 
    <Correlation /> 
    <Execution ProcessID=»4″ ThreadID=»8″ /> 
    <Channel>System</Channel> 
    <Computer>Central-HP</Computer> 
    <Security UserID=»S-1-5-18″ /> 
    </System>
    — <EventData>
    <Data Name=»BugcheckCode»>122</Data> 
    <Data Name=»BugcheckParameter1″>0xfffff6e000f725d8</Data> 
    <Data Name=»BugcheckParameter2″>0xffffffffc000000e</Data> 
    <Data Name=»BugcheckParameter3″>0x26f417880</Data> 
    <Data Name=»BugcheckParameter4″>0xffffc001ee4bb000</Data> 
    <Data Name=»SleepInProgress»>0</Data> 
    <Data Name=»PowerButtonTimestamp»>0</Data> 
    <Data Name=»BootAppStatus»>0</Data> 
    </EventData>
    </Event>

    3.Система перезагрузилась, завершив работу с ошибками. Возможные причины ошибки: система перестала отвечать на
    запросы, произошел критический сбой или неожиданно отключилось питание.
    Режим XLM
    — <Event xmlns=»http://schemas.microsoft.com/win/2004/08/events/event»>
    — <System>
    <Provider Name=»Microsoft-Windows-Kernel-Power» Guid=»{331C3B3A-2005-44C2-AC5E-77220C37D6B4}» /> 
    <EventID>41</EventID> 
    <Version>3</Version> 
    <Level>1</Level> 
    <Task>63</Task> 
    <Opcode>0</Opcode> 
    <Keywords>0x8000000000000002</Keywords> 
    <TimeCreated SystemTime=»2018-12-16T23:35:15.283435500Z» /> 
    <EventRecordID>670251</EventRecordID> 
    <Correlation /> 
    <Execution ProcessID=»4″ ThreadID=»8″ /> 
    <Channel>System</Channel> 
    <Computer>Central-HP</Computer> 
    <Security UserID=»S-1-5-18″ /> 
    </System>
    — <EventData>
    <Data Name=»BugcheckCode»>0</Data> 
    <Data Name=»BugcheckParameter1″>0x0</Data> 
    <Data Name=»BugcheckParameter2″>0x0</Data> 
    <Data Name=»BugcheckParameter3″>0x0</Data> 
    <Data Name=»BugcheckParameter4″>0x0</Data> 
    <Data Name=»SleepInProgress»>0</Data> 
    <Data Name=»PowerButtonTimestamp»>0</Data> 
    <Data Name=»BootAppStatus»>0</Data> 
    </EventData>
    </Event>

    4.Система перезагрузилась, завершив работу с ошибками. Возможные причины ошибки: система перестала отвечать на
    запросы, произошел критический сбой или неожиданно отключилось питание.
    Режим XLM
    — <Event xmlns=»http://schemas.microsoft.com/win/2004/08/events/event»>
    — <System>
    <Provider Name=»Microsoft-Windows-Kernel-Power» Guid=»{331C3B3A-2005-44C2-AC5E-77220C37D6B4}» /> 
    <EventID>41</EventID> 
    <Version>3</Version> 
    <Level>1</Level> 
    <Task>63</Task> 
    <Opcode>0</Opcode> 
    <Keywords>0x8000000000000002</Keywords> 
    <TimeCreated SystemTime=»2018-12-17T01:00:31.189544500Z» /> 
    <EventRecordID>670422</EventRecordID> 
    <Correlation /> 
    <Execution ProcessID=»4″ ThreadID=»8″ /> 
    <Channel>System</Channel> 
    <Computer>Central-HP</Computer> 
    <Security UserID=»S-1-5-18″ /> 
    </System>
    — <EventData>
    <Data Name=»BugcheckCode»>239</Data> 
    <Data Name=»BugcheckParameter1″>0xffffe00038a9c900</Data> 
    <Data Name=»BugcheckParameter2″>0x0</Data> 
    <Data Name=»BugcheckParameter3″>0x0</Data> 
    <Data Name=»BugcheckParameter4″>0x0</Data> 
    <Data Name=»SleepInProgress»>0</Data> 
    <Data Name=»PowerButtonTimestamp»>0</Data> 
    <Data Name=»BootAppStatus»>0</Data> 
    </EventData>
    </Event>

Ответы

  • Kernel-Power 41 (63) — это обычно проблемы с качеством питания. Самый простой способ проверки — заменить БП на заведомо исправный. Или искать вздувшиеся либо потекшие конденсаторы на системной плате и в БП.

    • Изменено

      17 декабря 2018 г. 12:27

    • Помечено в качестве ответа
      Petko KrushevMicrosoft contingent staff, Moderator
      2 января 2019 г. 9:03
  • Remove From My Forums

  • Question

  • Hello Good People.

    I have a server windows server 2016 which running on VMWare Esxi 6.5

    Since two days my windows server is crashing with event log stating as below.

    Note: VMware host has not restarted.

    Last week i did some windows update i dont know may be that has caused the VM to crashed.

    VMware event log says VM has crashed.

    • Edited by
      Mohammed Arifuddin
      Sunday, February 24, 2019 6:54 AM

All replies

  • Hi,

    Thanks for the reply !

    Please find the below details.

    This is a Virtual Machine ( Hosting a Exchange Database Copy ) this error is coming when we started seeding the mailbox database copy.

    Due to this issue, Database seeding also fails

  • Hello

    Bugcheckcode 239 is EF in Hex so this is a Bug Check OxEF (0x000000EF) 

    Here is some documentation on that stop code.

    https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0xef—critical-process-died  

    Thanks, Darrell Gorter [MSFT] This posting is provided «AS IS» with no warranties, and confers no rights.

  • Hi,

    According to the screenshot you provided,
    BugCheckCode 
    239     means CRITICAL_PROCESS_DIED.

    To fix this issue, please open the following link and do some troubleshooting:

    Troubleshoot blue screen errors

    https://support.microsoft.com/en-sg/help/14238/windows-10-troubleshoot-blue-screen-errors

    If the issue still persists, please upload dump file by OneDrive and attach the shared link in your reply.

    Hope these are helpful.

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact
    tnmff@microsoft.com.

  • Hi,

    I will upload the logs shortly.

    Thanks,

    Arif

  • Hi,

    Please find the link for the logs.

    https://1drv.ms/u/s!AmNSeoy9NimpgsIU8RMUZeiNJuaQiQ

    There was an cumulative Update for the windows server 2016, I have uninstalled and monitored the server for 3 days.

    Now its seems to be normal and running fine.

    Thanks,

    Arif

    • Edited by
      Mohammed Arifuddin
      Sunday, March 3, 2019 7:23 AM

  • Hi,

    Thanks for your updating.

    If you have any questions, please do not hesitate to contact us.

    Best

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact
    tnmff@microsoft.com.

1 / 1 / 0

Регистрация: 03.10.2021

Сообщений: 3

1

03.10.2021, 18:13. Показов 2522. Ответов 3

Студворк — интернет-сервис помощи студентам

Доброго времени суток!
Недавно(недели две назад) приобрел себе бу видеокарту для игр. Видеокарта — «GeForce® GTX 1060 Mini ITX OC 3G»
Сразу же для галочки протестил систему через Furmark, AIDA64, Crystaldisk mark. По датчикам все в норме, ЦП максимум 65 градусов, видеокарта максимум 70 под стресс тестами и в играх. И тут внезапно начали вылетать синие экраны. Первые два были во время игры, последующие начали появляться в любом состоянии ПК(игра, браузер, работа, простой). Никакой закономерности их появления выявить у меня не получается, единственное что они появляются примерно раз в сутки. Код ошибки — Critical process died. В журнале событий такое значение — «Kernel-Power, код 41, категория задачи 63. Система перезагрузилась, завершив работу с ошибками. Возможные причины ошибки: система перестала отвечать на запросы, произошел критический сбой или неожиданно отключилось питание. BugcheckCode 239.» Перед бсодом обычно происходит зависание системы на 10-15 секунд, после чего ребут.
При этом у меня не пишутся дампы памяти, хотя они включены, файл подкачки выставлен автоматически.
Из проделанного мною: -тест ОЗУ с помощью memtest86(4 прохода)-ошибок не выявлено; -проверка системы с помощью команд SFC и DISM(ошибок не выявлено); -менял шлейфы Sata кабелей; -отключал доп. жесткий диск; -отключил быстрый запуск в win 10; -отключил все режими энергосбережения; -обновление биоса; -обновление прошивки SSD; -переустановка драйверов на мат. плату с сайта производителя; -переустановка драйвера на видеокарту. В конце концов переустановил виндоус. В итоге ошибка осталась.
Хочу заметить, что синие экраны появлялись и раньше(судя по логам журнала событий), просто было это намного реже и я, видимо, просто не уделил этому заначения на тот момент.
Отчет AIDA прилагается, файлы дампов не создаются.
Прошу помощи.

0

Источник

Аватар пользователя

Недели две назад комп переодически начал уходить в ребут без BSODа (Иногда выскакивает синий экран но настолько быстро что не успевает даже ошибка появится. Бывает что просто замрёт на 5-10 секунд а потом в ребут) В журнале ошибок пишет (Kernel -Power Код 41 BugcheckCode разный ( 239,340) за сегодня). 
Чтоя только не делал и в стресстестах по 1ч каждый всё в норме, переустановлял Вин с 11 на 10 и обратно, обновлял и откатывал биос (Кстати ошибка на пару дней ушла после отката с верссии F15d до F14),но и это не помогло, сбрасывал до дефолтных настроек БИОС, проверял  ССД через консоль и через Crystal disk Видеокарту тоже гонял в фулмарке температура ЦПУ И ГПУ в норме ( Не выше 65градусов) 
Хочу у вас узнать что это может быть 
Я грешу на Блок питания, потому что только он и остаётся непроверенным, либо оперативная память.
Вот сборка ПК
Процессор AMD Ryzen 5 3600X OEM
Видеокарта GIGABYTE AORUS GeForce RTX 3050 ELITE
Материнская плата GIGABYTE B550 AORUS ELITE V2
Оперативная память Kingston HyperX Predator RGB [HX432C16PB3AK2/16] 16 ГБ
Блок питания Cougar BXM 700W
1000 ГБ SSD M.2 накопитель Samsung 980

Обсуждение товара

Источник

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and
privacy statement. We’ll occasionally send you account related emails.

Already on GitHub?
Sign in
to your account

Assignees

@DOMARS

Comments

@LuigiBruno

docs.microsoft.com

I’m troubleshooting a CRITICAL_PROCESS_DIED bugcheck (no dump file available), only a Kernel-Power event (ID 41) on a Windows Server machine: the detailed information for the event report a «BugcheckCode 239» event data.
Is that a new bugcheck not documented yet?

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

  • ID: ddc632b2-f4e1-b784-dd1e-878feac077f9
  • Version Independent ID: 7a6866f4-3333-f2d1-86d7-dbb3d00925e0
  • Content: Bug Check Code Reference — Windows drivers
  • Content Source: windows-driver-docs-pr/debugger/bug-check-code-reference2.md
  • Product: windows-hardware
  • Technology: windows-devices
  • GitHub Login: @DOMARS
  • Microsoft Alias: domars

@DOMARS

@LuigiBruno — Can you provide the first part of the !analyze output that shows the four parameters? Also can you verify the hex value of this stop code? Also we should check if this is VMWare related.

@LuigiBruno



Copy link


Contributor


Author

@LuigiBruno — Can you provide the first part of the !analyze output that shows the four parameters? Also can you verify the hex value of this stop code? Also we should check if this is VMWare related.

Hi @DOMARS.
There was no dump file, therefore I couldn’t use WinDbg.
Here’s the information from the «System» log in the Windows Event Viewer

BugcheckCode 239
BugcheckParameter1 0xffff930e74673340
BugcheckParameter2 0x0
BugcheckParameter3 0x0
BugcheckParameter4 0x0

@RAJU2529

@RAJU2529

@wdkbot. Sir, can I add some reference links to this article by creating new PR?

@LuigiBruno

docs.microsoft.com



Copy link


Contributor


Author

@DOMARS and @RAJU2529, it should be 0x000000EF (239 in decimal), definitively a CRITICAL_PROCESS_DIED bug check.

@DOMARS

Источник

RRS feed

  • Remove From My Forums

  • Вопрос

  • Hello Good People.

    I have a server windows server 2016 which running on VMWare Esxi 6.5

    Since two days my windows server is crashing with event log stating as below.

    Note: VMware host has not restarted.

    Last week i did some windows update i dont know may be that has caused the VM to crashed.

    VMware event log says VM has crashed.

    • Изменено
      Mohammed Arifuddin
      24 февраля 2019 г. 6:54

Все ответы

  • Hi,

    Thanks for the reply !

    Please find the below details.

    This is a Virtual Machine ( Hosting a Exchange Database Copy ) this error is coming when we started seeding the mailbox database copy.

    Due to this issue, Database seeding also fails

  • Hello

    Bugcheckcode 239 is EF in Hex so this is a Bug Check OxEF (0x000000EF) 

    Here is some documentation on that stop code.

    https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0xef—critical-process-died  

    Thanks, Darrell Gorter [MSFT] This posting is provided «AS IS» with no warranties, and confers no rights.

  • Hi,

    According to the screenshot you provided,
    BugCheckCode 
    239     means CRITICAL_PROCESS_DIED.

    To fix this issue, please open the following link and do some troubleshooting:

    Troubleshoot blue screen errors

    https://support.microsoft.com/en-sg/help/14238/windows-10-troubleshoot-blue-screen-errors

    If the issue still persists, please upload dump file by OneDrive and attach the shared link in your reply.

    Hope these are helpful.

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact
    tnmff@microsoft.com.

  • Hi,

    I will upload the logs shortly.

    Thanks,

    Arif

  • Hi,

    Please find the link for the logs.

    https://1drv.ms/u/s!AmNSeoy9NimpgsIU8RMUZeiNJuaQiQ

    There was an cumulative Update for the windows server 2016, I have uninstalled and monitored the server for 3 days.

    Now its seems to be normal and running fine.

    Thanks,

    Arif

    • Изменено
      Mohammed Arifuddin
      3 марта 2019 г. 7:23

  • Hi,

    Thanks for your updating.

    If you have any questions, please do not hesitate to contact us.

    Best

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact
    tnmff@microsoft.com.

Источник

Понравилась статья? Поделить с друзьями:
  • Bugcheck 1001 windows 10 ошибка как исправить
  • Bugcheck 1001 windows 10 ошибка 0x00000133
  • Bugcheck 1001 windows 10 ошибка 0x0000003b
  • Bugcheck 1001 windows 10 ошибка 0x00000001
  • Bug type 210 iphone ошибка