Not sure if this is the right fix? We’ve added this issue to our memory dump diagnostic which can confirm.
Symptoms
When you run certain applications on a computer that is running Windows 7 or Windows Server 2008 R2, you receive the following Stop error message:
Stop 0x0000003B (c0000094, fffff8800ff22e54, fffff880098897f0, 0)SYSTEM_SERVICE_EXCEPTION
For example, you may experience this issue when you run Cyberlink YouCam.
Cause
This issue occurs because the D3D9 runtime does not perform parameter validation on the rectangle values that are passed by applications such as YouCam. Therefore, invalid rectangle coordinates are passed to the Dxgkrnl.sys module. However, the Dxgkrnl.sys module also does not validate the rectangle coordinates, and a «divide by zero» exception occurs.
Resolution
Hotfix information
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
If the hotfix is available for download, there is a «Hotfix download available» section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=supportNote The «Hotfix download available» form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
Prerequisites
To apply this hotfix, you must be running one of the following operating systems:
-
Windows 7
-
Windows 7 Service Pack 1 (SP1)
-
Windows Server 2008 R2
-
Windows Server 2008 R2 Service Pack 1 (SP1)
For more information about how to obtain a Windows 7 or Windows Server 2008 R2 service pack, click the following article number to view the article in the Microsoft Knowledge Base:
976932 Information about Service Pack 1 for Windows 7 and for Windows Server 2008 R2
Registry information
To use the hotfix in this package, you do not have to make any changes to the registry.
Restart requirement
You must restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace a previously released hotfix.
File information
The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.
Windows 7 and Windows Server 2008 R2 file information notes
Important Windows 7 hotfixes and Windows Server 2008 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under «Windows 7/Windows Server 2008 R2» on the page. Always refer to the «Applies To» section in articles to determine the actual operating system that each hotfix applies to.
-
The files that apply to a specific product, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:
Version
Product
Milestone
Service branch
6.1.760 0.16xxx
Windows 7 and Windows Server 2008 R2
RTM
GDR
6.1.760 0.21xxx
Windows 7 and Windows Server 2008 R2
RTM
LDR
6.1.760 1.17xxx
Windows 7 and Windows Server 2008 R2
SP1
GDR
6.1.760 1.21xxx
Windows 7 and Windows Server 2008 R2
SP1
LDR
-
GDR service branches contain only those fixes that are widely released to address widespread, critical issues. LDR service branches contain hotfixes in addition to widely released fixes.
-
The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the «Additional file information for Windows 7 and for Windows Server 2008 R2» section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are critical to maintaining the state of the updated component. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x86-based versions of Windows 7
File name |
File version |
File size |
Date |
Time |
---|---|---|---|---|
Cdd.dll |
6.1.7600.16699 |
107,520 |
02-Nov-2010 |
04:23 |
Dxgkrnl.sys |
6.1.7600.16870 |
728,944 |
23-Aug-2011 |
04:30 |
Dxgmms1.sys |
6.1.7600.16870 |
218,992 |
23-Aug-2011 |
04:30 |
Lddmcore.ptxml |
Not applicable |
1,151 |
01-Nov-2010 |
23:04 |
Cdd.dll |
6.1.7600.21034 |
107,520 |
23-Aug-2011 |
04:26 |
Dxgkrnl.sys |
6.1.7600.21034 |
729,456 |
23-Aug-2011 |
04:40 |
Dxgmms1.sys |
6.1.7600.21034 |
218,992 |
23-Aug-2011 |
04:40 |
Lddmcore.ptxml |
Not applicable |
1,151 |
13-Jul-2009 |
20:32 |
Cdd.dll |
6.1.7601.17514 |
107,520 |
20-Nov-2010 |
11:56 |
Dxgkrnl.sys |
6.1.7601.17672 |
728,944 |
23-Aug-2011 |
04:32 |
Dxgmms1.sys |
6.1.7601.17672 |
218,992 |
23-Aug-2011 |
04:32 |
Lddmcore.ptxml |
Not applicable |
1,151 |
13-Jul-2009 |
20:32 |
Cdd.dll |
6.1.7601.17514 |
107,520 |
20-Nov-2010 |
11:56 |
Dxgkrnl.sys |
6.1.7601.21796 |
729,456 |
23-Aug-2011 |
05:50 |
Dxgmms1.sys |
6.1.7601.21796 |
218,992 |
23-Aug-2011 |
05:50 |
Lddmcore.ptxml |
Not applicable |
1,151 |
13-Jul-2009 |
20:32 |
For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
File name |
File version |
File size |
Date |
Time |
---|---|---|---|---|
Cdd.dll |
6.1.7600.16699 |
144,384 |
02-Nov-2010 |
04:59 |
Dxgkrnl.sys |
6.1.7600.16870 |
982,896 |
23-Aug-2011 |
05:46 |
Dxgmms1.sys |
6.1.7600.16870 |
265,072 |
23-Aug-2011 |
05:46 |
Lddmcore.ptxml |
Not applicable |
1,151 |
01-Nov-2010 |
22:58 |
Cdd.dll |
6.1.7600.21034 |
144,384 |
23-Aug-2011 |
05:26 |
Dxgkrnl.sys |
6.1.7600.21034 |
983,920 |
23-Aug-2011 |
05:54 |
Dxgmms1.sys |
6.1.7600.21034 |
265,072 |
23-Aug-2011 |
05:54 |
Lddmcore.ptxml |
Not applicable |
1,151 |
13-Jul-2009 |
20:25 |
Cdd.dll |
6.1.7601.17554 |
144,384 |
03-Feb-2011 |
11:25 |
Dxgkrnl.sys |
6.1.7601.17672 |
982,896 |
23-Aug-2011 |
05:36 |
Dxgmms1.sys |
6.1.7601.17672 |
265,072 |
23-Aug-2011 |
05:36 |
Lddmcore.ptxml |
Not applicable |
1,151 |
08-Jul-2010 |
18:22 |
Cdd.dll |
6.1.7601.17514 |
144,384 |
20-Nov-2010 |
12:55 |
Dxgkrnl.sys |
6.1.7601.21796 |
983,920 |
23-Aug-2011 |
05:21 |
Dxgmms1.sys |
6.1.7601.21796 |
265,072 |
23-Aug-2011 |
05:21 |
Lddmcore.ptxml |
Not applicable |
1,151 |
13-Jul-2009 |
20:25 |
For all supported IA-64-based versions of Windows Server 2008 R2
File name |
File version |
File size |
Date |
Time |
---|---|---|---|---|
Cdd.dll |
6.1.7600.16595 |
347,648 |
19-May-2010 |
14:27 |
Dxgkrnl.sys |
6.1.7600.16870 |
2,502,000 |
23-Aug-2011 |
04:15 |
Dxgmms1.sys |
6.1.7600.16870 |
669,040 |
23-Aug-2011 |
04:15 |
Lddmcore.ptxml |
Not applicable |
1,151 |
13-Jul-2009 |
20:25 |
Cdd.dll |
6.1.7600.21034 |
347,136 |
23-Aug-2011 |
09:11 |
Dxgkrnl.sys |
6.1.7600.21034 |
2,504,560 |
23-Aug-2011 |
09:21 |
Dxgmms1.sys |
6.1.7600.21034 |
669,040 |
23-Aug-2011 |
09:21 |
Lddmcore.ptxml |
Not applicable |
1,151 |
13-Jul-2009 |
20:25 |
Cdd.dll |
6.1.7601.17514 |
347,136 |
20-Nov-2010 |
10:06 |
Dxgkrnl.sys |
6.1.7601.17672 |
2,502,512 |
23-Aug-2011 |
04:05 |
Dxgmms1.sys |
6.1.7601.17672 |
671,088 |
23-Aug-2011 |
04:05 |
Lddmcore.ptxml |
Not applicable |
1,151 |
13-Jul-2009 |
20:25 |
Cdd.dll |
6.1.7601.17514 |
347,136 |
20-Nov-2010 |
10:06 |
Dxgkrnl.sys |
6.1.7601.21796 |
2,504,560 |
23-Aug-2011 |
04:17 |
Dxgmms1.sys |
6.1.7601.21796 |
671,600 |
23-Aug-2011 |
04:17 |
Lddmcore.ptxml |
Not applicable |
1,151 |
13-Jul-2009 |
20:25 |
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the «Applies to» section.
More Information
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
Additional file information
Additional file information for Windows 7 and for Windows Server 2008 R2
Additional files for all supported x86-based versions of Windows 7
File name |
X86_69192ff43b64dabdb5a4f548688e70dd_31bf3856ad364e35_6.1.7601.17672_none_53c1f540f5aec375.manifest |
File version |
Not applicable |
File size |
696 |
Date (UTC) |
23-Aug-2011 |
Time (UTC) |
11:36 |
File name |
X86_96b36211638d27a5186260481543ae86_31bf3856ad364e35_6.1.7601.21796_none_819cb589c01b69e5.manifest |
File version |
Not applicable |
File size |
696 |
Date (UTC) |
23-Aug-2011 |
Time (UTC) |
11:36 |
File name |
X86_cbd9709d2e643978ce1140fda8ef7ef7_31bf3856ad364e35_6.1.7600.16870_none_cb474bb1f485ce10.manifest |
File version |
Not applicable |
File size |
696 |
Date (UTC) |
23-Aug-2011 |
Time (UTC) |
11:36 |
File name |
X86_f9b2b59992849d081f681ae3084963a1_31bf3856ad364e35_6.1.7600.21034_none_58082c9a4644963c.manifest |
File version |
Not applicable |
File size |
696 |
Date (UTC) |
23-Aug-2011 |
Time (UTC) |
11:36 |
File name |
X86_microsoft-windows-lddmcore_31bf3856ad364e35_6.1.7600.16870_none_aba4c6ba44dcb20c.manifest |
File version |
Not applicable |
File size |
13,305 |
Date (UTC) |
23-Aug-2011 |
Time (UTC) |
11:46 |
File name |
X86_microsoft-windows-lddmcore_31bf3856ad364e35_6.1.7600.21034_none_ac5d7c7f5dd67ab0.manifest |
File version |
Not applicable |
File size |
13,193 |
Date (UTC) |
23-Aug-2011 |
Time (UTC) |
04:58 |
File name |
X86_microsoft-windows-lddmcore_31bf3856ad364e35_6.1.7601.17672_none_ad8d2454420150a6.manifest |
File version |
Not applicable |
File size |
13,305 |
Date (UTC) |
23-Aug-2011 |
Time (UTC) |
11:46 |
File name |
X86_microsoft-windows-lddmcore_31bf3856ad364e35_6.1.7601.21796_none_ae05226f5b2b8dae.manifest |
File version |
Not applicable |
File size |
13,305 |
Date (UTC) |
23-Aug-2011 |
Time (UTC) |
11:46 |
Additional files for all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
File name |
Amd64_0e072a9b97fd3860ef90de3602af0324_31bf3856ad364e35_6.1.7601.21796_none_f3f23a6b7940c654.manifest |
File version |
Not applicable |
File size |
700 |
Date (UTC) |
23-Aug-2011 |
Time (UTC) |
11:36 |
File name |
Amd64_577d30bb053afa581e6b503139cf12b0_31bf3856ad364e35_6.1.7601.17672_none_76058c6102c583cb.manifest |
File version |
Not applicable |
File size |
700 |
Date (UTC) |
23-Aug-2011 |
Time (UTC) |
11:36 |
File name |
Amd64_ccf4e7bda9f951359ea4957257fc5852_31bf3856ad364e35_6.1.7600.21034_none_81122151b470f107.manifest |
File version |
Not applicable |
File size |
700 |
Date (UTC) |
23-Aug-2011 |
Time (UTC) |
11:36 |
File name |
Amd64_f7886920e364adae137a9ab16f3be8c9_31bf3856ad364e35_6.1.7600.16870_none_5bff36e1cae6a169.manifest |
File version |
Not applicable |
File size |
700 |
Date (UTC) |
23-Aug-2011 |
Time (UTC) |
11:36 |
File name |
Amd64_microsoft-windows-lddmcore_31bf3856ad364e35_6.1.7600.16870_none_07c3623dfd3a2342.manifest |
File version |
Not applicable |
File size |
13,309 |
Date (UTC) |
23-Aug-2011 |
Time (UTC) |
11:49 |
File name |
Amd64_microsoft-windows-lddmcore_31bf3856ad364e35_6.1.7600.21034_none_087c18031633ebe6.manifest |
File version |
Not applicable |
File size |
13,197 |
Date (UTC) |
23-Aug-2011 |
Time (UTC) |
06:14 |
File name |
Amd64_microsoft-windows-lddmcore_31bf3856ad364e35_6.1.7601.17672_none_09abbfd7fa5ec1dc.manifest |
File version |
Not applicable |
File size |
13,309 |
Date (UTC) |
23-Aug-2011 |
Time (UTC) |
11:49 |
File name |
Amd64_microsoft-windows-lddmcore_31bf3856ad364e35_6.1.7601.21796_none_0a23bdf31388fee4.manifest |
File version |
Not applicable |
File size |
13,309 |
Date (UTC) |
23-Aug-2011 |
Time (UTC) |
11:49 |
Additional files for all supported IA-64-based versions of Windows Server 2008 R2
File name |
Ia64_5d1481bdfcefd1e998db08eebb27a5ef_31bf3856ad364e35_6.1.7601.21796_none_6d720f7a9e1be760.manifest |
File version |
Not applicable |
File size |
698 |
Date (UTC) |
23-Aug-2011 |
Time (UTC) |
11:36 |
File name |
Ia64_7823d3f487c5316dd33a2af562fe730f_31bf3856ad364e35_6.1.7600.16870_none_78030a6329aeef2d.manifest |
File version |
Not applicable |
File size |
698 |
Date (UTC) |
23-Aug-2011 |
Time (UTC) |
11:36 |
File name |
Ia64_d86db521dd70babe089461aeab460c4b_31bf3856ad364e35_6.1.7600.21034_none_bac49cef5ba2b82e.manifest |
File version |
Not applicable |
File size |
698 |
Date (UTC) |
23-Aug-2011 |
Time (UTC) |
11:36 |
File name |
Ia64_eb17eef51c8dbf4b16aae7a0f6bf33ef_31bf3856ad364e35_6.1.7601.17672_none_ce575819e647645a.manifest |
File version |
Not applicable |
File size |
698 |
Date (UTC) |
23-Aug-2011 |
Time (UTC) |
11:36 |
File name |
Ia64_microsoft-windows-lddmcore_31bf3856ad364e35_6.1.7600.16870_none_aba66ab044dabb08.manifest |
File version |
Not applicable |
File size |
13,307 |
Date (UTC) |
23-Aug-2011 |
Time (UTC) |
11:36 |
File name |
Ia64_microsoft-windows-lddmcore_31bf3856ad364e35_6.1.7600.21034_none_ac5f20755dd483ac.manifest |
File version |
Not applicable |
File size |
13,195 |
Date (UTC) |
23-Aug-2011 |
Time (UTC) |
09:36 |
File name |
Ia64_microsoft-windows-lddmcore_31bf3856ad364e35_6.1.7601.17672_none_ad8ec84a41ff59a2.manifest |
File version |
Not applicable |
File size |
13,307 |
Date (UTC) |
23-Aug-2011 |
Time (UTC) |
11:36 |
File name |
Ia64_microsoft-windows-lddmcore_31bf3856ad364e35_6.1.7601.21796_none_ae06c6655b2996aa.manifest |
File version |
Not applicable |
File size |
13,307 |
Date (UTC) |
23-Aug-2011 |
Time (UTC) |
11:36 |
The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.
Все способы:
- Исправление BSOD 0x0000003b
- Способ 1: Автоматическое исправление
- Способ 2: Восстановление системы
- Способ 3: Проверка оперативной памяти
- Способ 4: Чистая загрузка
- Способ 5: Удаление вирусов
- Частные случаи
- Заключение
- Вопросы и ответы: 3
Синие экраны смерти – это извечная проблема пользователей ОС Windows. Появляются они по разным причинам, но всегда говорят о том, что в системе произошла критическая ошибка и дальнейшая ее работа невозможна. В этой статье мы разберем несколько способов устранения BSOD с кодом 0x0000003b.
Исправление BSOD 0x0000003b
В основном данная ошибка преследует пользователей Windows 7 с разрядностью 64 бита и сообщает о проблемах в работе оперативной памяти. Причины здесь две: физическая неисправность установленных в ПК модулей ОЗУ или сбой в одном из системных драйверов (Win32k.sys, IEEE 1394). Существует и несколько частных случаев, которые мы также рассмотрим ниже.
Способ 1: Автоматическое исправление
Специально для таких случаев компания Майкрософт разработала специальное исправление, решающее нашу проблему. Поставляется оно в виде системного обновления KB980932, которое нужно скачать и запустить на своем ПК.
Скачать обновление
- После загрузки мы получим файл с названием 406698_intl_x64_zip.exe, представляющий собой самораспаковывающийся архив, содержащий обновление KB980932. Его можно распаковать вручную каким-нибудь архиватором, например, 7-Zip, или кликнув дважды, перейти к установке.
После запуска файла нажимаем «Continue».
- Выбираем место для распаковки архива.
- В следующем окне нажимаем ОК.
- Переходим в папку, которую указывали в п. 2, и запускаем обновление.
Читайте также: Ручная установка обновлений на Windows 7
Способ 2: Восстановление системы
Эта процедура спасет нас в ситуациях, когда ошибка возникла после установки какой-нибудь программы или драйвера. Восстановить систему можно разными способами, от использования системной утилиты до загрузки в среду восстановления.
Подробнее: Восстановление системы в Windows 7
Способ 3: Проверка оперативной памяти
Ошибка 0x0000003b может быть вызвана неисправностями в модулях ОЗУ. Определить, какие из них работают со сбоями, можно воспользовавшись встроенным в систему средством или специальным софтом для проверки памяти. Обратите внимание, что если у вас установлен большой объем «оперативы», то данная процедура может занять довольно много времени, в некоторых случаях до суток.
Подробнее: Как проверить оперативную память на работоспособность
Способ 4: Чистая загрузка
Данный прием поможет нам определить, виноваты ли в сбое сторонние службы и приложения. Приготовьтесь проявить терпение, так как процесс довольно трудоемкий.
- Все действия мы будем производить в системной оснастке «Конфигурация системы». Получить к ней доступ можно из строки «Выполнить» (Windows+R), используя команду
msconfig
- На вкладке «Общие» ставим переключатель в положение «Выборочный запуск» и разрешаем загружать системные службы соответствующей галкой.
- Переходим на вкладку «Службы», выключаем отображение служб Майкрософт (ставим флажок) и жмем кнопку «Отключить все».
- Нажимаем «Применить». Система предложит нам перезагрузиться. Соглашаемся или, если сообщение не появилось, перезапускаем компьютер вручную.
- После перезагрузки продолжаем работу на ПК и следим за поведением ОС. Если ошибка продолжает появляться, то переходим к другим решениям (не забудьте включить отключенные службы). Если же проблема решена, то снова заходим в «Конфигурацию системы» и ставим флажки напротив половины позиций в списке служб. Далее следует перезагрузка и наблюдение.
- Следующий шаг также зависит от того, появилась ли ошибка или нет. В первом случае становится ясно, что проблемная служба находится в отмеченной части списка и нужно снова его отсортировать, то есть снять половину установленных флажков и перезагрузиться. Эти действия нужно повторять до тех пор, пока не будет выявлен виновник сбоя.
Если синий экран не появляется, то убираем все галки, устанавливаем их напротив второй половины служб и повторяем сортировку. После того как сбойный элемент будет найден, нужно от него избавиться, удалив соответствующую программу или остановив службу.
Описанную процедуру необходимо произвести и для списка «Автозагрузка» в той же оснастке.
Способ 5: Удаление вирусов
В описании ошибки мы упомянули, что ее причиной могут являться сбойные драйверы Win32k.sys и IEEE 1394. Одним из факторов, вызывающих их некорректную работу, являются вредоносные программы. Определить, имела ли место вирусная атака, а также удалить вредителей, можно, воспользовавшись специальными сканерами.
Подробнее: Борьба с компьютерными вирусами
Частные случаи
В этом параграфе мы приведем еще несколько часто встречающихся причин возникновения сбоя и варианты их устранения.
- Драйвер видеокарты. В некоторых ситуациях это ПО может работать нестабильно, вызывая различные ошибки в системе. Решение: выполнить процедуру по его переустановке, следуя инструкции, доступной по ссылке ниже.
Подробнее: Переустанавливаем драйвера видеокарты
- DirectX. Данные библиотеки также могут быть повреждены и их необходимо обновить.
Подробнее: Обновить DirectX до последней версии
- Браузер Google Chrome со своим повышенным аппетитом к ОЗУ нередко становится причиной неполадок. Решить проблему можно, переустановив Хром или перейдя на другой обозреватель.
Заключение
Инструкции, приведенные выше, чаще всего помогают решить проблему с BSOD 0x0000003b, но бывают и исключения. В такой ситуации спасет только переустановка Windows, причем, только ее «чистый» вариант с форматированием диска и потерей всех данных.
Наша группа в TelegramПолезные советы и помощь
Как исправить ошибку 0x0000003b в Windows 11/10/7
В данном материале приведены способы, позволяющие исправить ошибку 0x0000003b, так называемая system service exception в Windows 11/10/7. Ошибка не является повторяющейся, но если она мешает открыть рабочий стол, то у вас несколько вариантов загрузки, а какие именно смотрите ниже:
Первый способ — обновить/переустановить графический драйвер.
Для выявления и исправления причины появления system service exception, выполните следующие действия:
Шаг 1. Нажмите Win + R и введите «devmgmt.msc», чтобы открыть диспетчер устройств;
Шаг 2. Откройте «Видеоадаптеры»;
Шаг 3. Выберите вашу видекарту и кликниет по ней правой кнопкой мыши, затем «свойства» и «драйвер» ;
Шаг 4. В разделе «Драйвер» нажмите «Обновить драйвер»;
Шаг 5. «Автоматический поиск драйверов»;
Шаг 6. Выполняйте все необходимые шаги согласно инструкций системы.
Способ второй — используйте Центр обновления Windows
Ошибка system service exception также может быть связана с версией системы Windows. В настройках Windows мы можем проверить, требуется ли какое-либо обновление. Win + I, чтобы открыть настройки, затем выберите ОБНОВЛЕНИЕ и БЕЗОПАСНОСТЬ для проверки.
Способ третий — восстановление файловой целостности
Этот метод делает возможным првоерку файлов системы и восстанавливает все при необходимости. Для устранения последствий system service exception все шаги будут реализовываться в «Командной строке» ОС Windows, следуйте следующей инстркции:
Шаг 1. Нажмите Win + R и введите «cmd», чтобы открыть диспетчер устройств;
— Поочередно вводим необходимые команды:
DISM.exe /Online /Cleanup-image /Restorehealth
sfc /scannow
chkdsk /f
Учтите, что выполнение обработка команды занимает определенное время. Наша рекомендация не прерывать их работу и дождаться окончания всего процесса — выполнения операций и комад для проверки целостности файлов в ОС Windows.
По завершении ваш ПК необходимо перезагрузить.
Способ четвертый — устранить проблему при помощи Driver Booster
Все сложности в работе ПК связанные с драйверами, в том числе ошибку 0x0000003b или system service exception могут быть с легкостью устранены Driver Booster. Нащш продукт поможет вам в автоматическом режиме обновлять все драйверы на вашем ПК при помощи расширенной базы данных драйверов, с Driver Booster вам не придется тратить драгоценное временя на подбор необходимого драйвера — просто скачайте и запустите Driver Booster, он автоматически начнет подбор нужных драйверов на ваш компьютер, после чего вам будет показан список устаревшего ПО. Затем вы можете указать, какие именно драйвера обновить.
Советы, которые вам также могут понравиться:
Как исправить ошибку DPC WATCHDOG VIOLATION в ОС Windows
Windows 10 работает медленно? Актуальные в 2023 способы исправления ситуации
Удаление встроенных в Windows 10 приложений
If you’re trying boot your computer into Windows but it fails and shows the blue screen, and you’re seeing this error saying STOP: 0x0000003b, you’re not alone. Many Windows users are reporting it. But the goo news is you can fix it easily by yourself.
2 easy solutions to fix 0x0000003b:
Here are 3 solutions for you to try. You may not need to try them all; just work your way down until you find the one works for you.
- Update all the available drivers
- Install the hotfix from Microsoft
You’ll need to be logged into Windows on the problem computer to try any of these solutions. If you can’t log into Windows, power on and off your PC 3 times to perform a hard reboot and restart it in Safe Mode, then try these solutions.
Solution 1: Update all the available drivers
0x0000003b BSOD error is probably caused by any old or incorrect drivers, especially your corrupted graphics driver. You need to verify that all your devices have the right driver, and update those that don’t. If you’re not comfortable playing around with drivers manually, you can do it automatically with Driver Easy.
Driver Easy will automatically recognize your system and find the correct drivers for it. You don’t need to know exactly what system your computer is running, you don’t need to be troubled by the wrong driver you would be downloading, and you don’t need to worry about making a mistake when installing. Driver Easy handles it all.
You can update your drivers automatically with either the 7 days free trial or the Pro version of Driver Easy. It takes just 2 clicks, and you get full support and a 30-day money-back guarantee with the Pro version:
- Download and install Driver Easy.
- Run Driver Easy and click the Scan Now button. Driver Easy will then scan your computer and detect any problem drivers.
- Click the Activate & Update button next to the flagged device to automatically download and install the correct version of this driver.
Or click Update All to automatically download and install the correct version of all the drivers that are missing or out of date on your system (You’ll need the Pro version for this – when you select Update All, you’ll get a prompt to upgrade. If you’re not prepared to purchase the Pro version yet, Driver Easy provides a 7-day trial at no cost, granting access to all Pro features like fast downloads and easy installation. No charges will occur until after your 7-day trial period ends.)
- Restart your computer for the change to take effect.
Solution 2: Install the hotfix from Microsoft
To help users solve the 0x0000003b BSOD error, Microsoft has released a Hotfix for those who’re on Windows 7 or Windows Server 2008 R2 and using some IEEE 1394 device.
For more concrete information or to download the Hotfix, please go to Microsoft website.
Summary: Besides being widely used, Windows operating system is well-known for its user-friendliness. However, it could still encounter errors while performing various operations. There are a healthy number of errors that users might trigger while using a Windows system, like Runtime Error and MBR Error. But the most common ones belong to the category of BSOD (Blue Screens of Death) errors such as 0x0000003B. In this article, we will explain to you how to solve it. And in addition to common problems triggered by the error, it might well lead to a data loss issue. In this case, you can use our reliable and user-friendly data recovery tool, Bitwar Data Recovery to recover lost files.
WIN VERSION MAC VERSION
Table of Contents
Causes of Blue Screen Stop 0x0000003b
The BSOD error 0x0000003B is a system error usually triggered by corrupt system files or wrongly configured Microsoft IEEE 1394 device drivers. However, when we scoured the Internet for similar cases, we found other possible causes reported by some users:
- Misconfigured or corrupt drivers
- Corrupted registry entries
- Damaged system files
- Memory errors/corruption
- Virus or malware invasion
- Hard disk damage
Basic Methods
Method 1: Perform a Virus Check
Viruses or malicious malware may well corrupt the system files and Windows registries. All these can hobble the normal functioning of your Windows system, leading to 0x0000003B. Thus, if you reckon that the frequent 0x0000003B error is caused by virus attacks, you could run a virus check with the help of effective anti-virus software.
The Anti-virus software will scour the computer for infected files and viruses and root out them, freeing the system of harmful files. We recommended you to perform a full system scan via Windows Security. Refer to the following steps to learn how to do so:
Step 1: Press Windows key + Q, type in Windows Security, and open it.
Step 2: Click on Virus & threat protection button on the right pane.
Step 3: Click Start action and then Quick scan.
Step 4: If you want a more tailored scan, click the Scan options button.
Step 5: Choose the scan mode you want and click Scan now to start it.
Step 6: After removing those malicious viruses, restart your PC to check the efficacy of the solution.
Method 2: Update the Wireless Card Drivers
Some users have reported that they managed to fix the problem by updating the wireless card drivers. Since the 0x0000003B Error is quite common on laptops of Windows 10 where wireless drivers are installed.
Hence, if you suspect that this problem may be the cause of the 0x0000003B BSOD crash, use the following steps to make sure that the computer has updated the latest wireless card driver:
Step 1: Press the Windows key + R to open a Run box. Type in devmgmt.msc and then press Enter to launch Device Manager.
Step 2: In the Device Manager window, expand the entry of Network adapters. Then, right-click on Wireless Network Adapter and then click on Update driver.
Step 3: In the ensuing window, click the Search automatically for updated driver software option.
Note: If that operation fails to find a new driver version, you could click Search for updated drivers on Windows Update.
Step 4: If a new version is found and successfully installed, exit Device Manager, reboot your computer to check whether the error is fixed.
Method 3: Remove and Switch RAM Modules
Some users reported that they successfully coped with the BSOD 0x0000003B stop error by removing and switching places of the RAM modules. This method, Of course, is only applicable when your computer runs different RAM modules.
Note: If your PC uses only one RAM module, you could re-insert it in a different slot.
Generally, with old RAM modules inserted for a long time, the connectors might well become dirty. Re-inserting the RAM modules in a different slot may well bring about frictions that are capable of shaking off the dirty material.
This method can improve electrical connectivity and minimize the risk of crashes caused by the RAM modules. After you have re-inserted the RAM modules, Reboot your PC and see whether the 0x0000003B error persists.
Recover Lost Data Using Bitwar Data Recovery
Data deletion after the 0x0000003b error is more or less common since the files may be lost when you are in the process of fixing the error. For instance, If you fail to boot into Windows after the crash and you can only resort to reinstalling the Windows, it can lead to a file loss issue.
In that case, you can recover data from your computer hard disk by using our reliable and effective data recovery tool, Bitwar Data Recovery.
Refer to the following content to learn how it works like magic:
Step 1: Download and install Bitwar Data Recovery from Bitwarsoft Download Center.
Step 2: Open the tool and select the disk drive where your missing data were stored and then click Next.
Step 3: Choose a scan mode in this stage. We would like to recommend Quick Scan, which is capable of retrieving a healthy number of lost files. If it doesn’t work, you could run the tool again and use Deep scan, which is more effective.
Step 4: Select the types of data you want to recover and click on Next.
Step 5: Preview wanted files to check their intactness. Select them and click Recover to start the recovery process.
Important: To ensure that those files you want will be recovered in an intact state, you should save them to other disks except the one where the lost data were stored.
Advanced Methods
Method 1: Use SFC
Damaged system files are one of the aforementioned reasons for the 0x0000003B error. System files are central to the proper functioning of the system. Hence, corruption in them may bring about serious problems. Seeing how vulnerable these important system files are, Windows has provided a tool named SFC (System File Checker) to help users search the computer for corrupted system files and replace them with healthy ones. Refer to the following steps to learn how to use this tool:
Step 1: Enter Command prompt in the search box and right-click on it.
Step 2: Click Run as administrator.
Step 3: Type in the following command and then press Enter:
sfc /scannow
Step 4: After the process is complete, reboot the computer to check whether this method works.
Important: To run this tool doesn’t require an active internet connection. But bear in mind that when it is in the process of searching for and replacing computer errors, you shouldn’t interrupt it. Otherwise, it may bring about even more errors.
Method 2: Use CHKDSK
As we have mentioned before, damage to the hard disk might well trigger the 0x0000003B error. If the file system on which your hard disk is based gets corrupted, this error could ensue. In this case, you can use the chkdsk tool provided by Windows to fix bad sectors errors it finds on the hard drive. Use these steps:
Step 1: Right-click the Start Menu button and select Command Prompt (Admin).
Step 2: Type in the following command and press Enter:
chkdsk C:/f
Note: Replace C with the letter of the drive you want to scan.
Step 3: Wait for the process to finish.
Step 4: Restart your computer to see whether the error persists.
When using the chkdsk, If you run into any problems such as Chkdsk cannot open volume for direct access error, you could refer to the link to learn how to solve it. Besides, you could also use Error checking, a graphical version of Chkdsk, to do the trick:
Step 1: Press the Windows key + E to open File Explorer.
Step 2: Right-click on the faulty disk drive and then click on Properties.
Step 3: Switch to the Tools tab.
Step 4: Click Check within the Error checking section.
Step 5: Click Scan drive.
Method 3: Check RAM for Corruption
A faulty RAM could well lead to a blue screen of death crash with the 0x0000003B error. In fact, a lot of the errors found on Windows is triggered by a faulty memory. But instead of rushing into replacing your RAM, you can use the Windows Memory Diagnostics Tool to check whether the RAM is indeed corrupted. You could use the following steps to do so:
Step 1: Launch the Run box by pressing Windows key + R.
Step 2: Type in mdsched.exe and then select the Restart Now and check for problems option.
Step 3: Wait for the computer to diagnose the memory.
Step 4: If it turns out that the RAM is faulty, it might be time to replace the RAM.
Method 4: Use System Restore
Windows has also provided a tool called System Restore that allows users to revert any changes made after a certain time that is referred to as Restore point. It’s also an effective way to solve the 0x0000003B error.
Refer to the following steps to learn how to use it.
Step 1: Press Windows + R to open the Run dialogue box.
Step 2: Type in rstrui.exe and then click on OK to open System Restore.
Step 3: Click on Next in the first stage, select a restore point prior to the time when your computer started to encounter the 0x0000003B errors and then click Next.
Step 4: Click the Finish button to start the restore process.
Conclusion
Data loss issue in the wake of the 0x0000003B error can be very frustrating. Hence, to help users who have suffered this kind of issue, this article has not only explained how to use different methods to fix the blue screen of death crash, but also expound on how to use our reliable and effective data recovery tool, Bitwar Data Recovery to bring their valuable data back.