bsod whea_uncorrectable_error 0x124

[notebooker]

Hi everyone! I bought a msi gp 66 i 7 11800h+ 3070 almost a year ago, and since the very beginning i got death screens. I get error whea_uncorrectable_error (0x00000124). Sometimes it happens randomly without anything weird going on before this, sometimes my laptop freezes completely before the error, and a weird screeching noise begins to play if my speakers are on -- and after that i get a death screen. Sometimes my mouse is also lagging, moving really slowly. These errors occur really randomly, sometimes during gaming sessions, sometimes when it's just idle, not even browsing the net. Furthermore, when i do benchmark testing, nothing ever happens (OCCT, AIDA64, FurMark). The frequency of these errors also varies. There was a period when it happened twice a day, or when it happened once a week. But i didn't get this error for 2 months after i got windows reinstalled. But it happened again recently when i was testing gpu via OCCT, the test was just fine, but after it completed - it freezed after a few minutes, and then i got another death screen. But in general, the errors seem to have nothing to do with the test, because they occurred before I first did the test, and afterwards, too. A little later (i have it in my windows log) it just freezed while i was browsing for a few minutes (i got some of it on video attached in the comments), after which I rebooted it via button and in the log i saw that this was that whea error again. But before and after that, all the CPU, gpu and everything else' tests were just fine and i got no errors. I took it to the warranty service three times, they tested it and reinstalled windows each time, but i still got these errors the very same day i had it reinstalled (i only installed some games from steam there). I also reinstalled drivers many times, but it didn't help at all. Last time I went to service, i got no result as well. The tests were just fine again.
I got bios updated as well, i checked it, but it didn't change anything. I couldn't get a dump file before (i got a window saying 'dump file creating error'), but i managed to get those files two last times (attached in the comments). I didn't do any overclocking or undervolting. I check temperatures all the time, i make sure to keep it below 75 Celcius. I can attach windows log if it's any help. I also tested wram with memtest, tested ssd many times. Crystal disc info tells me there are no critical failure and everything is perfect. I also had my motherboard checked in the service, but they saw no issues with it.
Some additional info that might help. Firstly, when testing VRAM with OCCT my laptop gave me this low battery warning, although it was plugged in charge and my battery charge was 82% at the moment. Then it went to sleeping mode, when i turned it on i had a ACPI 13 event in my log. The battery was still 82% though. Secondly, recently I've noticed that I get kernel boot 29 and a critical failure event in my log sometimes when I turn my laptop on. Nevertheless, it doesn't affect my laptop performance at all. It seems to happen when it's booting.

Thank you for reading and thanks in advance!! I'd appreciate any advice from you.

UPD: so last three times i had this error was while testing video RAM with OCCT, but it just freezed forever (i left it for 25 minutes, still freezed), so when i reboot it - i didn't get bsod, BUT it appeared to be the same mistake as those i've described bc t appeared on my windows log by the same name. Nevertheless, it doesn't occure everytime i run this test. What's more, it doesn't occur when i play games or run other video RAM tests.
Arg 1 in win dbg also is
Arg1: 0000000000000007, BOOT Error
but I didn't find on the internet what it could mean.
if someone could help by reading my dumps, I would be grateful.

 

[notebooker]

I also saw that it is worth answering some questions for better help, I attach the answers to them

• • A brief description of your problem (but you can also include the steps you tried) Bsodes at random times, as well as complete freezes, after which the same whea error occurs in the event log
  • System Manufacturer? MSI
  • Laptop or Desktop? Laptop
  • Exact model number (if laptop, check label on bottom) MSI GP 66 11 UG 699 11800H+3070
  • OS ? (Windows 11, 10, 8.1, 8, 7, Vista) WIN 10
  • x86 (32bit) or x64 (64bit)? X64
  • (Only for Vista, Windows 7) Service pack?
  • What was original installed OS on system? Free DOS? but in the manufacturer's service reinstalled the OS several times, but it did not help
  • Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from retailer)? retail
  • Age of system? (hardware) 11 months but problem was from 10 days after bought
  • Age of OS installation? 11 months
  • Have you re-installed the OS? yes
  • CPU i7 11800h
  • RAM (brand, EXACT model, what slots are you using?) factory version, 16 GB
  • Video Card кеч 3070
  • MotherBoard - (if NOT a laptop)
  • Power Supply - brand & wattage (if laptop, skip this one)
  • Is driver verifier enabled or disabled? enabled for 48 hours twice? but it didn't caused problems
  • What security software are you using? (Firewall, antivirus, antimalware, antispyware, and so forth) win defender
  • Are you using proxy, vpn, ipfilters or similar software? no
  • Are you using Disk Image tools? (like daemon tools, alcohol 52% or 120%, virtual CloneDrive, roxio software) no
  • Are you currently under/overclocking? Are there overclocking software installed on your system? no

 

[ubuysa]

It would help a lot if you followed the BSOD posting instructions.

Something to bear in mind with laptops is that it's generally wise to stick to the laptop vendor's supplied drivers, particularly for graphics drivers (both iGPU and dGPU). This is because these drivers in particular are often customised on laptops for power-saving or operational reasons. The generic drivers (from Nvidia and Intel) often don't contain these needed customisations and do sometimes cause issues (and BSODs) on laptops. I mention this because you do seem to be (also) having issues with nvlddmkm.sys, the Nvidia graphics driver. There are many of these errors in your System log...

Log Name:      System
Source:        nvlddmkm
Date:          28/02/2024 09:10:30
Event ID:      0
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      DESKTOP-TPNUHRU
Description:
The description for Event ID 0 from source nvlddmkm cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

\Device\Video8
Error occurred on GPUID: 100

The message resource is present but the message was not found in the message table

These are a kind of 'unknown' graphics driver error, something has failed but the error handlers weren't able to isolate what that was. This is quite commonly seen when generic graphics drivers are installed on a laptop.

The four dumps you uploaded all point at a boot error, which indicates that something failed during the Windows boot process, so I'd initially be thinking about a potential RAM issue or a system drive problem. It would be wise to check that the BIOS version you have supports that upgraded CPU and that you have the latest BIOS installed.

It would be wise to run a proper RAM test initially, although no RAM tester can ever prove that your RAM is good, only that it probably is...

1. Download Memtest86 (free), use the imageUSB.exe tool extracted from the download to make a bootable USB drive containing Memtest86 (1GB is plenty big enough). Do this on a different PC if you can, because you can't fully trust yours at the moment.
2. Then boot that USB drive on your PC, Memtest86 will start running as soon as it boots.
3. If no errors have been found after the four iterations of the 13 different tests that the free version does, then restart Memtest86 and do another four iterations. Even a single bit error is a failure.

Please follow the BSOD posting instructions above and let us know how the Memtest86 tests go. We'll move on depending on what that reveals.

 

[notebooker]

Было бы очень полезно, если бы вы следили за людьми после публикации BSOD .

При работе с ноутбуком следует иметь в виду, что, как правило, разумно руководствоваться драйверами, поставляемыми производителем ноутбука, особенно графическими драйверами (как iGPU, так и dGPU). Это связано с тем, что именно эти драйверы часто настраиваются на ноутбуках в соответствии с требованиями энергосбережения или эксплуатации. Универсальные драйверы (от Nvidia и Intel) часто не содержат необходимых настроек и иногда вызывают проблемы (и BSOD) на ноутбуках. Я упоминаю об этом, потому что, похоже, у вас (также) проблемы с nvlddmkm.sys, графическим драйвером Nvidia. В вашем системном журнале много таких ошибок...
[код]
Имя журнала: Система
Источник: нвлддмкм
Дата: 28.02.2024 09:10:30
Идентификатор событий: 0
Категория задачи: Нет
Уровень: Ошибка
Ключевые слова: Классика
Пользователь: Н/Д
Компьютер: DESKTOP-TPNUHRU
Описание:
Невозможно найти описание событий с идентификатором 0 из источника nvlddmkm. Либо компонент, вызывающий это событие, не установлен на вашем локальном компьютере, либо установка повреждена. Вы можете установить или восстановить компонент на локальном компьютере.

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

К мероприятию была приложена следующая информация:

\Устройство\Видео8
Произошла ошибка по GPUID: 100.

Ресурс сообщений присутствует, но сообщение не найдено в таблице сообщений.
[/код]
Это своего рода «неизвестная» ошибка графического драйвера: что-то не удалось, но обработчики ошибок не смогли определить, что это было. Такое часто можно увидеть, когда на ноутбуке установлены универсальные графические драйверы.

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

Было бы разумно сначала провести правильный тест ОЗУ, хотя ни один тестер ОЗУ никогда не сможет доказать, что ваш ОЗУ в порядке, а только то, что, вероятно, так оно и есть...

1. Загрузите Memtest86 (бесплатно) , воспользуйтесь инструментом imageUSB.exe, извлеките из загрузки, чтобы создать загрузочный USB-накопитель, включите Memtest86 (1 ГБ вполне достаточно). Если можете, сделайте это на другом компьютере, потому что в данный момент вы не можете полностью доверять ему.
2. Затем загрузите этот USB-накопитель на свой компьютер, Memtest86 начнет работать сразу после загрузки.
3. Если после четырех итераций 13 различных тестов, которые делают бесплатную версию, ошибок не обнаружено, перезапустите Memtest86 и выполните еще четыре итерации. Даже одна битовая ошибка является нашей.

Пожалуйста, проследите за приведенными выше руководителями после публикации BSOD и сообщите нам, как проходят тесты Memtest86. Мы будем двигаться дальше в зависимости от того, что

Привет! Ошибки nvlddmkm возникали при выключении теста видеопамяти OSCT и никак не влияли на работу. пропало после отката драйверов видеокарты с сайта производителя. Остальные драйвера также устанавливались с сайта производителя. Да, как видно из журнала, ошибка обычно регистрируется после включения ноутбука. memtest 86 тестировался 3 раза с 4 итерациями, каждый раз выдавая ноль ошибок. Что касается SSD, Виктория показала, что все в порядке, Kristal Disk Info также не имеет предупреждений, состояние хорошее.

 

[notebooker]

Было бы очень полезно, если бы вы следили за людьми после публикации BSOD .

При работе с ноутбуком следует иметь в виду, что, как правило, разумно управлять драйверами, предоставляемыми производителем ноутбука, особенно графическими драйверами (как iGPU, так и dGPU). Это связано с тем, что именно эти драйверы часто настраиваются на ноутбуках в соответствии с требованиями энергосбережения или эксплуатации. Универсальные драйверы (от Nvidia и Intel) часто не содержат необходимых настроек и иногда вызывают проблемы (и BSOD) на ноутбуках. Я упоминаю об этом, потому что, похоже, у вас (также) проблемы с nvlddmkm.sys, графическим драйвером Nvidia. В вашем системном журнале много таких ошибок...
[код]
Имя журнала: Система
Источник: нвлддмкм
Дата: 28.02.2024 09:10:30
Идентификатор событий: 0
Категория задачи: Нет
Уровень: Ошибка
Ключевые слова: Классика
Пользователь: Н/Д
Компьютер: DESKTOP-TPNUHRU
Описание:
Невозможно найти описание событий с идентификатором 0 из источника nvlddmkm. Либо компонент, вызывающий это событие, не установлен на вашем локальном компьютере, либо установка повреждена. Вы можете установить или восстановить компонент на локальном компьютере.

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

К мероприятию была приложена следующая информация:

\Устройство\Видео8
Произошла ошибка по GPUID: 100.

Ресурс сообщений присутствует, но сообщение в таблице сообщений не найдено.
[/код]
Это своего рода «неизвестная» ошибка графического драйвера: что-то не удалось, но обработчики ошибок не смогли определить, что это было. Такое часто можно увидеть, когда на ноутбуке установлены универсальные графические драйверы.

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

Было бы разумно сначала провести правильный тест ОЗУ, хотя ни один тестер ОЗУ никогда не сможет найти, что ваш ОЗУ в порядке, а только то, что, вероятно, так оно и есть...

1. Загрузите Memtest86 (бесплатно) , используйте imageUSB.exe, извлеките из загрузки, чтобы создать загрузочный USB-накопитель, Memtest86 (1 ГБ вполне достаточно). Если можете, сделайте это на другом компьютере, потому что в данный момент вы не можете ему полностью доверять.
2. Затем загрузите этот USB-накопитель на свой компьютер, Memtest86 начнет работать сразу после загрузки.
3. Если после четырех итераций 13 различных тестов, которые делает бесплатная версия, ошибки не выявлены, перезапустите Memtest86 и выполните еще четыре итерации. Даже одна битовая ошибка — наша.

Пожалуйста, проследите за приведенными выше руководителями после публикации BSOD и сообщите нам, как проходят тесты Memtest86. Мы будем двигаться дальше в зависимости от того, что эт

The BIOS is also the latest version, it was installed at the factory, the new version is not a release and I have the latest version, I checked. Sorry, I didn’t understand a little what, besides answers to questions and dumps, as well as a description of the problem, can be done according to the bsod instructions

 

[notebooker]

It would help a lot if you followed the BSOD posting instructions.

Something to bear in mind with laptops is that it's generally wise to stick to the laptop vendor's supplied drivers, particularly for graphics drivers (both iGPU and dGPU). This is because these drivers in particular are often customised on laptops for power-saving or operational reasons. The generic drivers (from Nvidia and Intel) often don't contain these needed customisations and do sometimes cause issues (and BSODs) on laptops. I mention this because you do seem to be (also) having issues with nvlddmkm.sys, the Nvidia graphics driver. There are many of these errors in your System log...

Log Name:      System
Source:        nvlddmkm
Date:          28/02/2024 09:10:30
Event ID:      0
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      DESKTOP-TPNUHRU
Description:
The description for Event ID 0 from source nvlddmkm cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

\Device\Video8
Error occurred on GPUID: 100

The message resource is present but the message was not found in the message table

These are a kind of 'unknown' graphics driver error, something has failed but the error handlers weren't able to isolate what that was. This is quite commonly seen when generic graphics drivers are installed on a laptop.

The four dumps you uploaded all point at a boot error, which indicates that something failed during the Windows boot process, so I'd initially be thinking about a potential RAM issue or a system drive problem. It would be wise to check that the BIOS version you have supports that upgraded CPU and that you have the latest BIOS installed.

It would be wise to run a proper RAM test initially, although no RAM tester can ever prove that your RAM is good, only that it probably is...

1. Download Memtest86 (free), use the imageUSB.exe tool extracted from the download to make a bootable USB drive containing Memtest86 (1GB is plenty big enough). Do this on a different PC if you can, because you can't fully trust yours at the moment.
2. Then boot that USB drive on your PC, Memtest86 will start running as soon as it boots.
3. If no errors have been found after the four iterations of the 13 different tests that the free version does, then restart Memtest86 and do another four iterations. Even a single bit error is a failure.

Please follow the BSOD posting instructions above and let us know how the Memtest86 tests go. We'll move on depending on what that reveals.

Hello! nvlddmkm errors occurred when the OSCT video memory test was turned off and did not affect operation in any way. disappeared after rolling back the video card drivers from the manufacturer's website. The remaining drivers were also installed from the manufacturer's website. Yes, as you can see from the log, the error is usually registered after turning on the laptop. memtest 86 was tested 3 times with 4 iterations, producing zero errors each time. As for the SSD, Victoria showed that everything is in order, Kristal Disk Info also has no warnings, the condition is good

 

[notebooker]

It would help a lot if you followed the BSOD posting instructions.

Something to bear in mind with laptops is that it's generally wise to stick to the laptop vendor's supplied drivers, particularly for graphics drivers (both iGPU and dGPU). This is because these drivers in particular are often customised on laptops for power-saving or operational reasons. The generic drivers (from Nvidia and Intel) often don't contain these needed customisations and do sometimes cause issues (and BSODs) on laptops. I mention this because you do seem to be (also) having issues with nvlddmkm.sys, the Nvidia graphics driver. There are many of these errors in your System log...

Log Name:      System
Source:        nvlddmkm
Date:          28/02/2024 09:10:30
Event ID:      0
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      DESKTOP-TPNUHRU
Description:
The description for Event ID 0 from source nvlddmkm cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

\Device\Video8
Error occurred on GPUID: 100

The message resource is present but the message was not found in the message table

These are a kind of 'unknown' graphics driver error, something has failed but the error handlers weren't able to isolate what that was. This is quite commonly seen when generic graphics drivers are installed on a laptop.

The four dumps you uploaded all point at a boot error, which indicates that something failed during the Windows boot process, so I'd initially be thinking about a potential RAM issue or a system drive problem. It would be wise to check that the BIOS version you have supports that upgraded CPU and that you have the latest BIOS installed.

It would be wise to run a proper RAM test initially, although no RAM tester can ever prove that your RAM is good, only that it probably is...

1. Download Memtest86 (free), use the imageUSB.exe tool extracted from the download to make a bootable USB drive containing Memtest86 (1GB is plenty big enough). Do this on a different PC if you can, because you can't fully trust yours at the moment.
2. Then boot that USB drive on your PC, Memtest86 will start running as soon as it boots.
3. If no errors have been found after the four iterations of the 13 different tests that the free version does, then restart Memtest86 and do another four iterations. Even a single bit error is a failure.

Please follow the BSOD posting instructions above and let us know how the Memtest86 tests go. We'll move on depending on what that reveals.

here's another sysnative file

 

[ubuysa]

Thanks for reposting in English, I think that everyone one here speaks English. It would also help (although I know it's a pain) if you could change your system language to English before running the SysnativeBSODCollectionApp. Most of the data uploaded is not in English and so I'm unable to read most of it.

It is possible for the 0x124 BSOD to be caused by a bad third-party driver, and especially since this is a boot error. The first thing you need to do is to enable boot logging so that we get a list of the drivers that are loaded at boot time. To do that search for the msconfig command and run that to bring up the System Configuration window. Click the Boot tab and click (select) the Boot Log checkbox. Each time you boot Windows now a boot log will be saved as C:\Windows\ntbtlog.txt, upload that file to the cloud so we can see it. You might also want to copy the text file and save it somewhere else for reference later (it gets overwritten at each boot).

Then try a clean boot of Windows. Initially boot Windows with all third-party drivers deselected (ie. not loaded). The laptop will be fairly unusable in that state because many devices won't work properly (or at all) because their drivers are not loaded. Your display will be low resolution for example, because the third-party display driver will not be loaded. The objective here is to see whether it BSODs on boot with no third-party drivers loaded. You may want to boot it multiple times in this configuration to be certain whether or not it will BSOD.

If it BSODs with only Microsoft drivers loaded at boot time then it's almost certainly a hardware problem. In that case, as a final confirmation, boot Windows into Safe Mode without networking. This loads a stripped-down copy of Windows with only critical drivers and services loaded, typically no third-party drivers will be loaded. If it BSODs in Safe Mode without networking then you can be pretty certain that you have a hardware problem.

If it will not BSOD in that clean boot state then you can be confident that the problem is a third-party driver that's being loaded at boot time. Now you can use a common boolean-search technique to quickly isolate the problem driver...

1. In a clean boot, enable half of the third-party drivers. If it BSODs on boot the problem driver is in the half you enabled. If it doesn't BSOD on boot the problem driver is in the half you didn't enable.
2. Pick the problem half and do another clean boot with only half of the problem half drivers enabled. By repeating this process, picking the problem half each time, you can quickly home in on the one driver causing the boot BSOD.
3. It's possible of course that there may be more than one driver causing problems, that will require enabling third-party drivers in much smaller groups to locate the bad ones.

 

[notebooker]

Thanks for reposting in English, I think that everyone one here speaks English. It would also help (although I know it's a pain) if you could change your system language to English before running the SysnativeBSODCollectionApp. Most of the data uploaded is not in English and so I'm unable to read most of it.

It is possible for the 0x124 BSOD to be caused by a bad third-party driver, and especially since this is a boot error. The first thing you need to do is to enable boot logging so that we get a list of the drivers that are loaded at boot time. To do that search for the msconfig command and run that to bring up the System Configuration window. Click the Boot tab and click (select) the Boot Log checkbox. Each time you boot Windows now a boot log will be saved as C:\Windows\ntbtlog.txt, upload that file to the cloud so we can see it. You might also want to copy the text file and save it somewhere else for reference later (it gets overwritten at each boot).

Then try a clean boot of Windows. Initially boot Windows with all third-party drivers deselected (ie. not loaded). The laptop will be fairly unusable in that state because many devices won't work properly (or at all) because their drivers are not loaded. Your display will be low resolution for example, because the third-party display driver will not be loaded. The objective here is to see whether it BSODs on boot with no third-party drivers loaded. You may want to boot it multiple times in this configuration to be certain whether or not it will BSOD.

If it BSODs with only Microsoft drivers loaded at boot time then it's almost certainly a hardware problem. In that case, as a final confirmation, boot Windows into Safe Mode without networking. This loads a stripped-down copy of Windows with only critical drivers and services loaded, typically no third-party drivers will be loaded. If it BSODs in Safe Mode without networking then you can be pretty certain that you have a hardware problem.

If it will not BSOD in that clean boot state then you can be confident that the problem is a third-party driver that's being loaded at boot time. Now you can use a common boolean-search technique to quickly isolate the problem driver...

1. In a clean boot, enable half of the third-party drivers. If it BSODs on boot the problem driver is in the half you enabled. If it doesn't BSOD on boot the problem driver is in the half you didn't enable.
2. Pick the problem half and do another clean boot with only half of the problem half drivers enabled. By repeating this process, picking the problem half each time, you can quickly home in on the one driver causing the boot BSOD.
3. It's possible of course that there may be more than one driver causing problems, that will require enabling third-party drivers in much smaller groups to locate the bad ones.

yes, sorry, I wanted to write in English, but my auto translator of the page was wrong. Please tell me how to change the language in the sysnative application. As soon as I get to the laptop, I'll turn on the boot log. Regarding the clean boot of Windows, you say that the laptop will be almost unusable, but as I said, the problem is intermittent and may not appear even for several weeks, so it will be problematic to use this, but if there is no other option, I will try. And the fact that there were no problems in Windows verifier for two days does not allow us to exclude drivers as the cause of the problem? In general, is the Boot error usually associated with them, or is it difficult to determine? Thank you for your help.

 

[notebooker]

Спасибо за репост на английском, думаю, здесь все говорят по-английски. Также было бы полезно (хотя я знаю, что это неприятно), если бы вы могли изменить язык системы на английский перед запуском SysnativeBSODCollectionApp. Большая часть загруженных данных не на английском языке, поэтому я не могу их прочитать.

BSOD 0x124 может быть вызван плохим сторонним драйвером, тем более что это ошибка загрузки. Первое, что вам нужно сделать, это включить ведение журнала загрузки, чтобы мы получили список драйверов, загружаемых во время загрузки. Для этого найдите команду msconfig и запустите ее, чтобы открыть окно конфигурации системы. Перейдите на вкладку «Загрузка» и установите флажок «Журнал загрузки». Теперь каждый раз, когда вы загружаете Windows, журнал загрузки будет сохраняться как C:\Windows\ntbtlog.txt. Загрузите этот файл в облако, чтобы мы могли его увидеть. Вы также можете скопировать текстовый файл и сохранить его в другом месте для дальнейшего использования (он перезаписывается при каждой загрузке).

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

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

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

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

another interesting thing. Previously, errors consisted of either a spontaneous blue screen, or a short-term (about 30 seconds) freeze, then a blue screen. After I took the laptop to the service center, where it was completely disassembled, the errors stopped for 1.5 months (previously they were at least once every 2 weeks), and reappeared after the OSCT video memory test. However, these errors after a break already cause very long freezes, lasting indefinitely, until the laptop is rebooted from the button, and the blue screen does not crash, but in the event log there is the same whea error, which is why I am sure that this is the same thing , but for some reason it changed a little. Maybe this will help somehow

 

[notebooker]

sysnative in english

 

[notebooker]

Each time you boot Windows now a boot log will be saved as C:\Windows\ntbtlog.txt, upload that file to the cloud so we can see it. You might also want to copy the text file and save it somewhere else for reference later (it gets overwritten at each boot).

boot log

 

[ubuysa]

Ah, I got the impression from your first post that the BSODs happened on most boots? Is that not the case then? If this happens rarely then it's almost certainly a hardware rather than a driver problem.

 

[notebooker]

Ah, I got the impression from your first post that the BSODs happened on most boots? Is that not the case then? If this happens rarely then it's almost certainly a hardware rather than a driver problem.

No, it's absolutely randomly, it can be once or twice a day, and can once a month, as it was after service

 

[notebooker]

Ах, из вашего первого поста у меня сложилось впечатление, что BSODы случаются на большинстве ботинок? Разве это не так? Если это происходит редко, то почти наверняка это проблема оборудования, а не драйвера.

Dumps can't say anything new? If this happens rarely and randomly, it turns out there is something wrong with the equipment? It's strange then why this doesn't happen in tests

 

[notebooker]

Ah, I got the impression from your first post that the BSODs happened on most boots? Is that not the case then? If this happens rarely then it's almost certainly a hardware rather than a driver problem.

And if, in your opinion, this is probably a hardware problem, then could you tell me how to determine which one? The manufacturer cannot catch the problem and therefore says that it is working, although obviously it is not. Maybe if I pointed him to a specific piece of equipment it would be easier

 

[ubuysa]

I wish I could point you at a specific component, but the 0x124 dumps aren't very helpful with hardware.

I have seen several niggly problems resolved by removing and re-seating an M.2 SSD drive, so I'd suggest you try that. Ensure the SSD pins and the M.2 contacts are clean - but don't blow on them with your mouth - and then fully re-insert the SSD. The dumps do show a Read_File operation in the lead-up to the BSODs, so this is well worth trying.

If the RAM is removable (sometimes it's soldered in on laptops, then pop the RAM cards out, ensure that the pins and sockets are clean, and then re-insert the RAM cards firmly. There isn't much else on a laptop that you can remove and re-insert, except the networking card and that's not likely to be at fault here.

I did spend some time yesterday looking through your list of boot loaded drivers, because there is still a sm,all chance that it's one of these fouling up on the odd boot. I did spot a few things that might be worth looking more closely at...

• You are using a Killer WiFi card and the driver for this (KfeCo10X64.sys) is loaded at boot time. However, the Intel WiFi adapter driver (Nwtwtw10.sys) is also loaded at boot time, yet I don't see anywhere that you have an Intel WiFi adapter installed? I'm wondering why that driver is being loaded at all? I would disable the Intel Wireless Driver in a clean boot.
  
  
• There are also a bunch of drivers loaded at boot time for the Intel Dynamic Platform and Thermal Management system. This is essentially a hardware level version of the Windows power options. I am quite sure that you can do without this, at least temporarily, and manage the system using the Windows power options. I would disable this feature in a clean boot.
  
  
• There is a driver loaded at boot time for the Intel Watchdog Timer Facility (ICCWDT.sys). This is designed to monitor for hung applications and to terminate and restart them if they do hang. You can certainly do without this feature, so I would disable it in a clean boot.
  
  
• You have a number of HD audio drivers loading at boot time, I know from experience that sometimes these can clash and cause BSODs. These are; RTKVHD64.sys - the Realtek audio driver for the on-board audio components, nvhda64v.sys - the Nvidia HD audio driver for sending audio over HDMI (this driver has been known to clash with rtkvhd64.sys on other systems), and two Nahimic drivers (Nahimic_Mirroring.sys and NahimicBTLink.sys), this audio drivers for the Nahimic system which may be included in your laptop. These audio drivers may not be playing nicely when the initialise on boot, so I would suggest you decide which drivers you can do without for a while and disable those in a clean boot. Note that the only way to disable the nvhda64v.sys driver is to reinstall the Nvidia graphics driver and deselect the audio driver. You don't need this driver if you're not sending audio over an HDMI connection.
  
  
• There is a Samsung Magician driver (magdrvamd64.sys) loading at boot time, unless you actively use Magician I would disable this in a clean boot (or uninstall Magician).
  
  
• There is an HWInfo driver (HWiNFO64A_187.SYS) loading at boot time. This may be harmless but I would disable it in a clean boot since you don't need it.
  
  
• The Intel graphics driver (igdkmdn64.sys) is quite old, dating from Aug 2021. See whether there is an update on the laptop vendor's website.
  
  
• The Nvidia graphics driver (nvlddmkm.sys) dates from April 2022, look for an updated driver from the laptop vendor's website.

It is well worth disabling all the features in a clean boot that you know you can live without, even temporarily, such as those mentioned above. With an intermittent problem such as this you have to take some pain in order to be able to identify the cause, there is no quick fix.

 

[notebooker]

I wish I could point you at a specific component, but the 0x124 dumps aren't very helpful with hardware.

I have seen several niggly problems resolved by removing and re-seating an M.2 SSD drive, so I'd suggest you try that. Ensure the SSD pins and the M.2 contacts are clean - but don't blow on them with your mouth - and then fully re-insert the SSD. The dumps do show a Read_File operation in the lead-up to the BSODs, so this is well worth trying.

If the RAM is removable (sometimes it's soldered in on laptops, then pop the RAM cards out, ensure that the pins and sockets are clean, and then re-insert the RAM cards firmly. There isn't much else on a laptop that you can remove and re-insert, except the networking card and that's not likely to be at fault here.

I did spend some time yesterday looking through your list of boot loaded drivers, because there is still a sm,all chance that it's one of these fouling up on the odd boot. I did spot a few things that might be worth looking more closely at...

• You are using a Killer WiFi card and the driver for this (KfeCo10X64.sys) is loaded at boot time. However, the Intel WiFi adapter driver (Nwtwtw10.sys) is also loaded at boot time, yet I don't see anywhere that you have an Intel WiFi adapter installed? I'm wondering why that driver is being loaded at all? I would disable the Intel Wireless Driver in a clean boot.
  
  
• There are also a bunch of drivers loaded at boot time for the Intel Dynamic Platform and Thermal Management system. This is essentially a hardware level version of the Windows power options. I am quite sure that you can do without this, at least temporarily, and manage the system using the Windows power options. I would disable this feature in a clean boot.
  
  
• There is a driver loaded at boot time for the Intel Watchdog Timer Facility (ICCWDT.sys). This is designed to monitor for hung applications and to terminate and restart them if they do hang. You can certainly do without this feature, so I would disable it in a clean boot.
  
  
• You have a number of HD audio drivers loading at boot time, I know from experience that sometimes these can clash and cause BSODs. These are; RTKVHD64.sys - the Realtek audio driver for the on-board audio components, nvhda64v.sys - the Nvidia HD audio driver for sending audio over HDMI (this driver has been known to clash with rtkvhd64.sys on other systems), and two Nahimic drivers (Nahimic_Mirroring.sys and NahimicBTLink.sys), this audio drivers for the Nahimic system which may be included in your laptop. These audio drivers may not be playing nicely when the initialise on boot, so I would suggest you decide which drivers you can do without for a while and disable those in a clean boot. Note that the only way to disable the nvhda64v.sys driver is to reinstall the Nvidia graphics driver and deselect the audio driver. You don't need this driver if you're not sending audio over an HDMI connection.
  
  
• There is a Samsung Magician driver (magdrvamd64.sys) loading at boot time, unless you actively use Magician I would disable this in a clean boot (or uninstall Magician).
  
  
• There is an HWInfo driver (HWiNFO64A_187.SYS) loading at boot time. This may be harmless but I would disable it in a clean boot since you don't need it.
  
  
• The Intel graphics driver (igdkmdn64.sys) is quite old, dating from Aug 2021. See whether there is an update on the laptop vendor's website.
  
  
• The Nvidia graphics driver (nvlddmkm.sys) dates from April 2022, look for an updated driver from the laptop vendor's website.

It is well worth disabling all the features in a clean boot that you know you can live without, even temporarily, such as those mentioned above. With an intermittent problem such as this you have to take some pain in order to be able to identify the cause, there is no quick fix.

Thank you for taking the time to solve my problem. When the laptop was disassembled, the SSD was removed and left for testing in another serviceable laptop, so I think they would have noticed if something was wrong with the contacts. And reading files usually happens because of problems with the ssd? the only oddity that I noticed in him is a very fast consumption of the write and read resource, with 1,500 thousand hours of operation, about 15,000 GB of recording and 25,000 GB of reading, I did not record so much on him, as it seems to me, I have regular home use, sometimes I put-delete games, but hardly whether in such volumes. But in crystal disk info ssd has good condition with no critical Warning, there were also no problems in Victoria either. didn't understand a little about the Intel Wi-Fi adapter, it seems that this adapter is in these laptops. Or is the killer something else? I don't really understand, to be honest. Regarding magician, I recently installed the program, I will disable it.
Regarding the intel graphics driver, there is a separate story). In general, initially there was a driver from the manufacturer's website from 2021 (it is still listed on the site as the newest, apparently they do not update there). Then the system updated it to a newer one, from 2022. In search of similar cases and solutions to the problem, I came across a discussion of a lenovo laptop in sysnative, and a person with similar problems managed to reproduce the error when rolling back and subsequently updating the intel driver. I tried to reproduce the error according to his instructions (having a guaranteed ability to reproduce the error would help a lot in diagnosis), but it didn't work out.
Regarding the nvidia driver, there was the latest one, but it caused the errors you mentioned in the osst video memory tests. I read that it could be because of the driver, rolled it back to the version from the manufacturer's website (just in 2022), and the nvlkdm errors (Somehow so called) stopped. I will delete/disable the rest specified by you

 

[ubuysa]

If I understand correctly, you're saying that rolling back to the laptop vendor's Nvidia graphics driver solved the problem? That's quite common, as I mentioned, laptops often customise their graphics drivers (including the Intel graphics driver)...

 

[notebooker]

If I understand correctly, you're saying that rolling back to the laptop vendor's Nvidia graphics driver solved the problem? That's quite common, as I mentioned, laptops often customise their graphics drivers (including the Intel graphics driver)...

No, Rolling back the nvidia driver removed the nvlkdmd(Something like this) error you mentioned high, but this is not the main problem, and this error did not affect performance. The main problem is whea error