Windows диск отсутствует exception processing message c0000013
Windows — Диск отсутствует (ошибка c0000013) — данная ошибка иногда возникает при запуске некоего приложения или установке новой программы, а также после работы с съемным носителем.
Windows — Диск отсутствует решение проблемы
Для начала надо открыть редактор реестра. Для этого в меню «Пуск» надо найти строку «Выполнить»,
Нажать, появится окно, вставить туда слово: «regedit». Нажать ОК .
И тут пользователь говорит: «А у меня нет «Выполнить»!». Такое бывает, если в свойствах панели задач, в вкладке «Пуск», в настройках снят флажок «выполнить». Можно поставить флажок и продолжать. Альтернативно, можно воспользоваться поиском и найти regedit. Появится иконка программы, делаем двойной клик.
Редактор реестра открылся. Видим справа пустое окно, слева колонку, там Компьютер и папки. Выбираем ветку (папку) HKEY_LOCAL_MACHINE, давим на крестик. Выбираем SYSTEM, нажимаем плюс, снова выпадают папки, ищем СurrentControlSet, опять раскрываем, находим Control, снова крестик, выпадает огромное количество папок, в самом низу ищем Windows, кликаем по ней. В правом окне выбираем параметр ErrorMode, двойной клик. Открывается окошко, синим подсвечивается значение 0. Его нужно поменять на 2. Нажимаем ОК и закрываем редактор реестра.
Проблема с выскакивающим, надоедливым окном Wndows диск отсутствует exception processing message c0000013 — решена!
Если появляется сообщение, что редактирование реестра запрещается администратором, а администратор это Вы, то ищем
gpedit.msc , запускаем, ищем: «Групповая политика», нажимаем — «политика локальный компьютер», переходим- «конфигурация пользователя», дальше- «административные шаблоны»,выбираем – система.Там надо изменить параметр: «Сделать недоступным средство редактирования реестра», выбрать радиокнопку: «отключено».
Снова запускаем regedit.
В домашней версии Виндовс нет gpedit.msc. Исправить это можно установив дополнительный патч.
Если редактор реестра не запускается, и Вы уверены, что не запрещали себе ничего делать, значит, это сделали вирусы. В таком случае, я бы советовал найти файл regedit в папке Windows, скопировать и вставить в другую папку, изменить название и запустить. И избавиться от вирусов, само собой.
-
- Nov 19, 2020
-
- 1
-
- 0
-
- 10
- 0
-
#1
I have found two workarounds so far. The first one is just booting via the UEFI. Just opening it on startup, and exiting it, tends to do the job.
I have also found that when I turn the PSU off and on, the first boot after that will be successful. If I restart after that, the BSOD just returns.
Once booted, the PC works as intended. For the most part that is. In the last few weeks, I noticed AVG using about 70% of my CPU, so I uninstalled it.
I wanted to try and install Panda instead, but every time I try to install it, I get a BSOD about halfway through the process. It also happened when trying to install Adobe Acrobat DC last week.
But except for that, the PC still works as intended. I can still play games on it, etc.
My setup (5 years old):
- Intel Core i7 4790K (I have not overclocked it yet)
- Asus Z97K Motherboard
- Corsair Vengeance 2x8GB 1600MHz DDR3 Memory
- Samsung SSD 850 EVO 250GB
- MSI GTX980 4GB
- Corsair RM650 PSU
- Windows 10 Home
The things I tried/checked:
- Checked if the CMOS battery might be dead -> it is not
- Ran MemTest86 -> no errors found
- Googled the stop code -> didn’t find anything helpful
- Updated SSD Firmware -> the problem persists
- Ran chkdsk on the SSD (even though I doubt if it is a useful tool for SSD’s, since it was designed for HDD’s) -> no bad sectors found
- Tried running diagnostic scan for SSD in Samsung Magician -> feature not supported for my SSD
- Ran a Malwarebytes scan -> no malware was found
Since the recent crashes when installing software, I am suspecting that it might have something to do with either my SSD or my Windows installation, although I am in no way sure of this.
I am thinking about re-installing windows, but before I take such a drastic step I wanted to check here if anyone could help me finding a lead as to what is causing these BSOD’s.
I don’t want all my Windows settings lost if the problem is caused by the motherboard, CPU or RAM.
You can check out the dump files right here.
EDIT:
So about a day after posting this thread, I couldn’t boot into Windows at all. My workarounds didn’t work anymore, and instead of giving BSOD’s, it just went into some kind of boot loop for a few times, followed by the troubleshoot-menu. Because I wanted to make sure my personal files were safe first, I installed Windows on an external HDD in order to boot into my system. I copied all my personal files from the SSD to another external HDD, and then wiped the SSD to be sure that if the problem was indeed Windows-related, it would be fixed (wasn’t sure if a «repair Windows» option would do the job).
I installed Windows on the SSD, and I have rebooted several times for driver updates and register changes since, and I haven’t encountered a single BSOD anymore. So I think that the boot files of Windows got corrupted somehow. I didn’t really find the cause for that, but at least I found a solution that didn’t require purchasing new hardware. Now I can only hope that the problem won’t return.
Last edited: Nov 23, 2020
-
- Nov 4, 2012
-
- 9,827
-
- 157
-
- 55,890
-
- 2,200
-
#2
Second you want to check for drive errors that could cause the drive to delay finding data. Google for Crystaldiskinfo.exe. it can read the drive smart error data to see if it is failing. When windows can not read data from the drive it will call for a reset of the interface and try again. Since widows will try to move data from bad spots on the drive 5 minutes after the system goes idle it could mean the drive is going bad or the drive has very little room left on it for the system to move blocks of data around. Solid state drives have firmware that kind of fight with windows. Often you can boot a system into bios and leave it powered on but not running windows so that the ssd firmware can finish its cleanup routines. Powered on in bios for a few hours.
note: dump files show a size of zero bytes this would indicate the could not be written to
you might be able to tell the system to write dump files to different drive when the system crashes. Assuming the problem is not in the driver for the drive controller.
Last edited: Nov 21, 2020
-
- Nov 4, 2012
-
- 9,827
-
- 157
-
- 55,890
- 2,200
-
#2
Second you want to check for drive errors that could cause the drive to delay finding data. Google for Crystaldiskinfo.exe. it can read the drive smart error data to see if it is failing. When windows can not read data from the drive it will call for a reset of the interface and try again. Since widows will try to move data from bad spots on the drive 5 minutes after the system goes idle it could mean the drive is going bad or the drive has very little room left on it for the system to move blocks of data around. Solid state drives have firmware that kind of fight with windows. Often you can boot a system into bios and leave it powered on but not running windows so that the ssd firmware can finish its cleanup routines. Powered on in bios for a few hours.
note: dump files show a size of zero bytes this would indicate the could not be written to
you might be able to tell the system to write dump files to different drive when the system crashes. Assuming the problem is not in the driver for the drive controller.
Last edited: Nov 21, 2020
-
- Nov 4, 2012
-
- 9,827
-
- 157
-
- 55,890
-
- 2,200
-
#3
0xc0000013. I do not think this is a bugcheck code. I think it is a error code that indicates that a drive was disconnected. It would happen when a drive does not respond within some time out period. Normally you would update the bios and CPU chipset drivers from the motherboard vendors website as a first fix attempt.
Second you want to check for drive errors that could cause the drive to delay finding data. Google for Crystaldiskinfo.exe. it can read the drive smart error data to see if it is failing. When windows can not read data from the drive it will call for a reset of the interface and try again. Since widows will try to move data from bad spots on the drive 5 minutes after the system goes idle it could mean the drive is going bad or the drive has very little room left on it for the system to move blocks of data around. Solid state drives have firmware that kind of fight with windows. Often you can boot a system into bios and leave it powered on but not running windows so that the ssd firmware can finish its cleanup routines. Powered on in bios for a few hours.note: dump files show a size of zero bytes this would indicate the could not be written to
you might be able to tell the system to write dump files to different drive when the system crashes. Assuming the problem is not in the driver for the drive controller.
you could also get this problem with a loose connector to the drive. I have seen cases where a connector can connect and disconnect several times a second just because of thermal expansion and fan vibration. putting the drive on a different sata port with a different connector might help. I would guess a 5 year old system is more likely to be having the ssd drive shrinking in size due to bad blocks being mapped as bad by the ssd firmware. make sure you have plenty of free space on the drive , you might also want to turn off the windows paging subsystem, reboot and delete the pagefile.sys (if not already deleted) then turn the virtual memory back on and reboot again. it will create a new pagefile.sys that will not have bad blocks in it.
-
- Nov 4, 2012
-
- 9,827
-
- 157
-
- 55,890
- 2,200
-
#4
you could also get this problem with a loose connector to the drive. I have seen cases where a connector can connect and disconnect several times a second just because of thermal expansion and fan vibration. putting the drive on a different sata port with a different connector might help. I would guess a 5 year old system is more likely to be having the ssd drive shrinking in size due to bad blocks being mapped as bad by the ssd firmware. make sure you have plenty of free space on the drive , you might also want to turn off the windows paging subsystem, reboot and delete the pagefile.sys (if not already deleted) then turn the virtual memory back on and reboot again. it will create a new pagefile.sys that will not have bad blocks in it. (booting into bios to let the firmware run would also fix bad blocks in a pagefile.sys but would take longer for the system to scan and repair)
| Thread starter | Similar threads | Forum | Replies | Date |
|---|---|---|---|---|
|
W
|
Question Error: «Startup Repair couldn’t repair your PC» ? | Windows 10 | 0 | Jan 20, 2023 |
|
|
Question «Smart Disk Capability Disabled’ On Startup From Restart | Windows 10 | 4 | Jan 17, 2023 |
|
P
|
Question Windows crashes on startup | Windows 10 | 6 | Jan 15, 2023 |
|
T
|
[SOLVED] Computer scanning C: drive every startup | Windows 10 | 3 | Jan 9, 2023 |
|
C
|
[SOLVED] Error 0xc000021A on startup ? | Windows 10 | 2 | Dec 18, 2022 |
|
|
Question random crash on startup and shutdown | Windows 10 | 2 | Nov 17, 2022 |
|
|
[SOLVED] error code 0xc00000428 And can’t access startup settings | Windows 10 | 13 | Nov 14, 2022 |
|
F
|
Question Windows 10 needs to startup twice each time | Windows 10 | 10 | Oct 22, 2022 |
|
F
|
Question Bsod once on every cold startup | Windows 10 | 11 | Sep 30, 2022 |
|
M
|
Question Startup error — windows cannot access the specified device or path microsoft.your.phone.[version] | Windows 10 | 3 | Aug 23, 2022 |
- Advertising
- Cookies Policies
- Privacy
- Term & Conditions
- Topics
Я могу предложить вам решение и исправление этой ошибки. Я думаю, это вызвано программой под названием dit.exe которая установлена в некотором программном обеспечении card reader, чтобы позволить вам видеть название дисков и для них есть отдельные иконки. Она запускается при старте и в ней довольно много бесполезных процессов. Сначала вы должны проверить, чтобы увидеть, если это вызывает у вас проблемы. Запустите msconfig и если она появляется в списке автозапуска отключите её и перезагрузите компьютер. Если это не решает вашей проблемы, удалите dit.exe из папки Windows (вы можете также избавиться от dit.dll, диета.ini и ditxp.exe) . Теперь вы должны сделать registry sweep, чтобы избавиться от любых dit.exe записей.
Если вы по преженему получаете это сообщение об ошибке, которое появляется через некоторое время, это означает, что некоторые записи в реестре поменялись автоматически, и могут иметь заражение вирусами или вредоносными программами, которые меняют их значение в реестре, теперь мы должны изменить некоторые настройки реестра обратно на ту же стадию, как и должно быть. Вот несколько шагов для решения этой проблемы, пожалуйста, выполните следующие действия.
Шаги
Быстрое решение
HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlWindows , найдите ключи реестра ErrorMode и измените значение данных 2 и нажмите на кнопку «ОК». По умолчанию значение ключа Errormode должно быть 0X00000000(2)
Я объясню вам, как это сделать.
1. Нажмите на Пуск >> а затем нажмите на Выполнить.
2. Вы получите окно, в которое вы должны ввести regedit.
3. Редактор реестра будет открыт перед вами, здесь вы должны найти ключ реестра и нужно нажать на знак плюс HKEY_LOCAL_MACHINE.
4. Нажмите на знак плюс Система
5. Нажмите на знак плюс CurrentControlSet.
6. Нажмите на знак плюс Контроль.
7. Нажмите на Windows.
8. Когда вы нажмёте на Windows вам будет выдано ErrorMode на правой боковой панели.
9. Дважды щелкните на ErrorMode и измените значение данных на 2 и нажмите на кнопку » ОК». 0X00000000(2) , значение по умолчанию Errormode должно быть 0X00000000(2) .
Наконец, перезагрузите компьютер и проблема будет решена.
- Распечатать
Оцените статью:
- 5
- 4
- 3
- 2
- 1
(5 голосов, среднее: 5 из 5)
Поделитесь с друзьями!
I suddenly had this problem when starting up my (previous boots) working VS 2010 project.
The application was unable to start correctly (0xc0000013). Click OK to close the application.
Debug output:
`The program '[5940] myapp.exe: Native' has exited with code -1073741805 (0xc0000013).`
asked Sep 13, 2011 at 0:07
4
STATUS_NO_MEDIA_IN_DEVICE, «There is no disk in the drive». Your debugging working directory is probably set to a USB emulated disk that’s unavailable.
answered Sep 13, 2011 at 0:34
Hans PassantHans Passant
913k145 gold badges1671 silver badges2507 bronze badges
2
I suddenly had the same problem with projects under VS 2008 after some Windows updates. But upon reading this thread I’ve decided to check %PATH% and found that some paths referred to locations on an empty DVD drive. Fixing the paths solved the problem. (In the end, updates seem to be unrelated, the only thing that matters is that media was ejected from the device after restart.)
answered Dec 21, 2011 at 1:54
Victor KVictor K
4992 silver badges14 bronze badges
Remarkably I unplugged my charging Android 2.3 and it worked.
answered Sep 13, 2011 at 0:08
bobobobobobobobo
63.7k60 gold badges254 silver badges355 bronze badges
1
I had error STATUS_NO_MEDIA_IN_DEVICE and the issue turned out to be a missing debug DLL, I had to add a build step to copy it over.
answered Jun 7, 2013 at 16:02
paulmpaulm
5,5583 gold badges45 silver badges69 bronze badges
This error can also be due to conflicting DLL versions, to find out if this is the case, one can use the dependency walker, with a step-by-step tutorial by Code Yarns here. In my case it was because the program was 32-bits and the required libraries were 64-bits, where it expected 32-bits.
answered Feb 5, 2018 at 18:49
gaborousgaborous
15.2k10 gold badges81 silver badges100 bronze badges