Файл halmacpi.dll считается разновидностью DLL-файла. DLL-файлы, такие как halmacpi.dll, по сути являются справочником, хранящим информацию и инструкции для исполняемых файлов (EXE-файлов), например sapisvr.exe. Данные файлы были созданы для того, чтобы различные программы (например, Windows) имели общий доступ к файлу halmacpi.dll для более эффективного распределения памяти, что в свою очередь способствует повышению быстродействия компьютера.
К сожалению, то, что делает файлы DLL настолько удобными и эффективными, также делает их крайне уязвимыми к различного рода проблемам. Если что-то происходит с общим файлом DLL, то он либо пропадает, либо каким-то образом повреждается, вследствие чего может возникать сообщение об ошибке выполнения. Термин «выполнение» говорит сам за себя; имеется в виду, что данные ошибки возникают в момент, когда происходит попытка загрузки файла halmacpi.dll — либо при запуске приложения Windows, либо, в некоторых случаях, во время его работы. К числу наиболее распространенных ошибок halmacpi.dll относятся:
- Нарушение прав доступа по адресу — halmacpi.dll.
- Не удается найти halmacpi.dll.
- Не удается найти C:WindowsSystem32halmacpi.dll.
- Не удается зарегистрировать halmacpi.dll.
- Не удается запустить Windows. Отсутствует требуемый компонент: halmacpi.dll. Повторите установку Windows.
- Не удалось загрузить halmacpi.dll.
- Не удалось запустить приложение, потому что не найден halmacpi.dll.
- Файл halmacpi.dll отсутствует или поврежден.
- Не удалось запустить это приложение, потому что не найден halmacpi.dll. Попробуйте переустановить программу, чтобы устранить эту проблему.
Файл halmacpi.dll может отсутствовать из-за случайного удаления, быть удаленным другой программой как общий файл (общий с Windows) или быть удаленным в результате заражения вредоносным программным обеспечением. Кроме того, повреждение файла halmacpi.dll может быть вызвано отключением питания при загрузке Windows, сбоем системы при загрузке halmacpi.dll, наличием плохих секторов на запоминающем устройстве (обычно это основной жесткий диск) или, как нередко бывает, заражением вредоносным программным обеспечением. Таким образом, крайне важно, чтобы антивирус постоянно поддерживался в актуальном состоянии и регулярно проводил сканирование системы.
0 / 0 / 0 Регистрация: 30.08.2011 Сообщений: 4 |
|
1 |
|
30.08.2011, 17:19. Показов 21109. Ответов 7
На той неделе переустановил Windows 7. Все чистенько. Драйвера с дисков. Все подходит. Все прекрасно работало. Сегодня целый день компьютер работал ушел на кухню, прихожу в комнату и как в страшном сне. ЭТО Помогите, что делать? ==================================================
__________________
0 |
13175 / 4623 / 168 Регистрация: 25.10.2010 Сообщений: 9,412 |
|
30.08.2011, 20:31 |
2 |
lipovii, если это разовый случай, то может и не стоит обращать внимание. Вот если такое будет повторятся…то скажите, посмотрим что можно сделать. Не по теме: У меня тоже вылетал тут недавно синяк. перегрузился и дальше работаю, он больше и не возвращался))
0 |
0 / 0 / 0 Регистрация: 30.08.2011 Сообщений: 4 |
|
30.08.2011, 21:36 [ТС] |
3 |
Sanya, а разве бывает такое, что это может не повторится? Просто хотелось бы узнать что именно произошло? с неделю все работало как часы и компьютер новый, до переустановки работал ровно с мая месяца (с покупки)
0 |
13175 / 4623 / 168 Регистрация: 25.10.2010 Сообщений: 9,412 |
|
30.08.2011, 21:41 |
4 |
что это может не повторится? бывает. если ошибка связана например с программами , которые вступили в конфликт. у меня последний синяк вызвал плеер, на следующий день сутки гонял его и ничего подобного больше не наблюдалось.
0 |
0 / 0 / 0 Регистрация: 30.08.2011 Сообщений: 4 |
|
30.08.2011, 21:48 [ТС] |
5 |
А можно все же переустановиться?
0 |
Почетный модератор 28037 / 15768 / 981 Регистрация: 15.09.2009 Сообщений: 67,753 Записей в блоге: 78 |
|
31.08.2011, 09:35 |
6 |
попробуй дровишки на чипсет сначала обновить…
0 |
nepopolo |
|
29.12.2011, 23:59 |
7 |
lipovii, у меня та же проблема экран BSOD выскакивает регулярно!!! Раз в два дня минимум( Перестановка ОС не помогла! |
Почетный модератор 28037 / 15768 / 981 Регистрация: 15.09.2009 Сообщений: 67,753 Записей в блоге: 78 |
|
30.12.2011, 09:36 |
8 |
nepopolo, что за бсод, номер в студию…
0 |
IT_Exp Эксперт 87844 / 49110 / 22898 Регистрация: 17.06.2006 Сообщений: 92,604 |
30.12.2011, 09:36 |
8 |
- Remove From My Forums
-
Вопрос
-
I have been getting BSOD with my windows 7 32-bit Professional (6.1.7601 SP1)
Motherboard = ASUS M4A88TD-V. BIOS: American Megatrends 2301 8/9/2012.
No new hardware.
Using a utility, the driver causing this crash (BAD-POOL-CALLER) = halmacpi.dll
I have checked the video driver (embedded GPU): ATI Radeon HD 4250 — Windows says that the driver is up to date.
Any help would be greatly appreciated.
Ответы
-
Alan
Related to
AODDriver.sys AMD Over Drive Service Driver from Advanced Micro Devices. Yours is 4 years old. If you are overclocking stop. I would install the newest driver available. You can turn off verifier by typing verifier /resetOld drivers needing updating
ATMhelpr.SYS 4/15/1997 8:45:23 PM
AsUpIO.sys 7/5/2009 9:21:27 PM
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.18247.x86fre.win7sp1_gdr.130828-1532 Machine Name: Kernel base = 0x82c12000 PsLoadedModuleList = 0x82d5b4d0 Debug session time: Wed Jan 29 11:22:55.077 2014 (UTC - 5:00) System Uptime: 0 days 4:27:53.623 BugCheck C4, {62, aaef771c, a7385008, 16} *** WARNING: Unable to verify timestamp for AODDriver.sys *** ERROR: Module load completed but symbols could not be loaded for AODDriver.sys Probably caused by : AODDriver.sys Followup: MachineOwner --------- 3: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* DRIVER_VERIFIER_DETECTED_VIOLATION (c4) A device driver attempting to corrupt the system has been caught. This is because the driver was specified in the registry as being suspect (by the administrator) and the kernel has enabled substantial checking of this driver. If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will be among the most commonly seen crashes. Arguments: Arg1: 00000062, A driver has forgotten to free its pool allocations prior to unloading. Arg2: aaef771c, name of the driver having the issue. Arg3: a7385008, verifier internal structure with driver information. Arg4: 00000016, total # of (paged+nonpaged) allocations that weren't freed. Type !verifier 3 drivername.sys for info on the allocations that were leaked that caused the bugcheck. Debugging Details: ------------------ BUGCHECK_STR: 0xc4_62 IMAGE_NAME: AODDriver.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4b8f8e60 MODULE_NAME: AODDriver FAULTING_MODULE: a3a76000 AODDriver VERIFIER_DRIVER_ENTRY: dt nt!_MI_VERIFIER_DRIVER_ENTRY ffffffffa7385008 Symbol nt!_MI_VERIFIER_DRIVER_ENTRY not found. CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP PROCESS_NAME: GpuBoostServer CURRENT_IRQL: 2 ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre LAST_CONTROL_TRANSFER: from 82f48f03 to 82cf0bfc STACK_TEXT: a334ba88 82f48f03 000000c4 00000062 aaef771c nt!KeBugCheckEx+0x1e a334baa8 82f4d5eb aaef771c a7385008 a3a76000 nt!VerifierBugCheckIfAppropriate+0x30 a334bab8 82c214ca aaef76c0 82d52c08 82d52c08 nt!VfPoolCheckForLeaks+0x33 a334baf4 82db110a aaef76c0 aaef76c0 00000100 nt!VfTargetDriversRemove+0x66 a334bb08 82dbeb84 82d5b4a0 8d16ece0 00000000 nt!VfDriverUnloadImage+0x5e a334bb40 82dbe90b aaef76c0 ffffffff 00000000 nt!MiUnloadSystemImage+0x231 a334bb64 82ecc26f aaef76c0 86687d20 aaefb608 nt!MmUnloadSystemImage+0x36 a334bb7c 82e347c9 aaefb620 aaefb620 aaefb608 nt!IopDeleteDriver+0x38 a334bb94 82c8a200 00000000 aaefb620 00000000 nt!ObpRemoveObjectRoutine+0x59 a334bba8 82c8a170 aaefb620 82c2676b b2adcf68 nt!ObfDereferenceObjectWithTag+0x88 a334bbb0 82c2676b b2adcf68 a73f94c8 aae43598 nt!ObfDereferenceObject+0xd a334bc00 82cb9064 a73f94c8 00000000 36e20000 nt!IopCompleteUnloadOrDelete+0x23e a334bc18 82e43c89 00000000 00000000 86687b90 nt!IopDecrementDeviceObjectRef+0x37 a334bc64 82e347c9 aae43598 aae43598 aae43580 nt!IopDeleteFile+0x1af a334bc7c 82c8a200 00000000 8d16ece0 aae43580 nt!ObpRemoveObjectRoutine+0x59 a334bc90 82c8a170 aae43598 82e57556 a7a78390 nt!ObfDereferenceObjectWithTag+0x88 a334bc98 82e57556 a7a78390 8d16ece0 0000033c nt!ObfDereferenceObject+0xd a334bcdc 82e5727c a7a78390 a7b50678 a27c0a60 nt!ObpCloseHandleTableEntry+0x21d a334bd0c 82e57616 a27c0a60 8d16ec01 0012f4a8 nt!ObpCloseHandle+0x7f a334bd28 82c4f8c6 0000033c 0012f4ac 76e570f4 nt!NtClose+0x4e a334bd28 76e570f4 0000033c 0012f4ac 76e570f4 nt!KiSystemServicePostCall WARNING: Frame IP not in any known module. Following frames may be wrong. 0012f4ac 00000000 00000000 00000000 00000000 0x76e570f4 STACK_COMMAND: kb FOLLOWUP_NAME: MachineOwner FAILURE_BUCKET_ID: 0xc4_62_VRF_LEAKED_POOL_IMAGE_AODDriver.sys BUCKET_ID: 0xc4_62_VRF_LEAKED_POOL_IMAGE_AODDriver.sys ANALYSIS_SOURCE: KM FAILURE_ID_HASH_STRING: km:0xc4_62_vrf_leaked_pool_image_aoddriver.sys FAILURE_ID_HASH: {207b4d79-d842-cfa2-919b-d10b5ebc2686} Followup: MachineOwner ---------
Wanikiya and Dyami—Team Zigzag
-
Помечено в качестве ответа
5 февраля 2014 г. 7:25
-
Помечено в качестве ответа
- Remove From My Forums
-
Question
-
G’day,
This problem is causing me a hell of a lot of grief at the moment. My computer bluescreens randomly. Sometimes it will run for days without issue, and other days it will bluescreen once or twice. There does not seem to be any discernible pattern. Any advice
would be greatly appreciated. Thanks in advance.Details as follows:
TOSHIBA Satellite C650 PSC12A-00S00T
OS: Windows 7 Home Premium Service Pack 1 (32 bit)
RAM: 4 GB
Dump File 110213-32838-01.dmp Crash Time 2/11/2013 22:03 Bug Check String KERNEL_MODE_EXCEPTION_NOT_HANDLED Bug Check Code 0x1000008e Parameter 1 0xc0000046 Parameter 2 0x83a90e0f Parameter 3 0xc560b5a0 Parameter 4 0x00000000 Caused by Driver halmacpi.dll Caused by Address halmacpi.dll+5ba9 File Description Hardware Abstraction Layer DLL Product Name Microsoft® Windows® Operating System Company Microsoft Corporation File Version 6.1.7601.17514 (win7sp1_rtm.101119-1850) Processor 32-bit Crash Address ntkrnlpa.exe+80e0f Stack Address 1 ntkrnlpa.exe+80bf1 Stack Address 2 ULCDRHlp.sys+30e4 Stack Address 3 ULCDRHlp.sys+a7f File Path C:WindowsMinidump110213-32838-01.dmp Processor Count 4 Major Version 15 Minor Version 7601 Dump File Size 147,680
Answers
-
Duane
These were Related to
ULCDRHlp.sys ULCDRHlp driver from Ulead Systems, Inc. Yours is from
2004. Remove Ulead completely.Other old drivers needing updating
pcouffin.sys 12/5/2006 9:39:53 AM
modrc.sys 7/11/2007 3:06:20 AM
PxHelp20.sys 10/17/2007 1:24:26 PM
CSN5PDTS82.sys 4/22/2009 5:37:57 AM
sxuptp.sys 5/7/2009 11:13:24 PM
pgeffect.sys 6/22/2009 4:04:57 AMhttp://www.carrona.org/drivers/driver.php?id=pcouffin.sys
http://www.carrona.org/drivers/driver.php?id=modrc.sys
http://www.carrona.org/drivers/driver.php?id=PxHelp20.sys
http://www.carrona.org/drivers/driver.php?id=sxuptp.sys
http://www.carrona.org/drivers/driver.php?id=pgeffect.sysBugCheck 1000008E, {c0000046, 83a90e0f, c560b5a0, 0} Probably caused by : ULCDRHlp.sys ( ULCDRHlp+30e4 ) ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨`` BugCheck 1000008E, {c0000046, 83a90e0f, c28a15a0, 0} Probably caused by : ULCDRHlp.sys ( ULCDRHlp+30e4 ) ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨`` BugCheck 1000008E, {c0000046, 83acfe0f, 9db2f5a0, 0} Probably caused by : ULCDRHlp.sys ( ULCDRHlp+30e4 ) ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨`` BugCheck 1000008E, {c0000046, 83ab8e0f, 8e1fb1e0, 0} Probably caused by : ULCDRHlp.sys ( ULCDRHlp+313c ) ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨`` BugCheck 1000008E, {c0000046, 83a87e0f, ef65b5a0, 0} Probably caused by : ULCDRHlp.sys ( ULCDRHlp+30e4 ) ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨`` BugCheck 1000008E, {c0000046, 83a88e0f, cd270410, 0} Probably caused by : ULCDRHlp.sys ( ULCDRHlp+313c ) ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨`` BugCheck 1000008E, {c0000046, 83ab9e0f, b9cff5a0, 0} Probably caused by : ULCDRHlp.sys ( ULCDRHlp+30e4 )
Wanikiya and Dyami—Team Zigzag
-
Proposed as answer by
Friday, November 15, 2013 3:54 AM
-
Marked as answer by
暁北
Friday, November 15, 2013 5:52 AM
-
Proposed as answer by
-
Duane
I am unsure about what Ulead did back in 2004 but what you could try is to rename the driver (just in case) from *.sys to *.bak so it cant load. If nothing complains you can then delete it or follow the procedures you have suggested.
Wanikiya and Dyami—Team Zigzag
-
Marked as answer by
暁北
Friday, November 15, 2013 5:52 AM
-
Marked as answer by
-
Hello,
I’ve disabled the Ulead Burning Helper service, and renamed the driver: C:WindowsSystem32driversULCDRHlp.old — That was interesting. Restarted my computer, started Windows Media Centre, was able to activate the TV tuner. All looked good so far. I then tried
to burn files to a CD. Failed. It seems I have now lost the DVD drive.I then opened the Computer Management console and scanned for hardware changes. This re-installed the DVD drive, and I have just now successfully burned some data to a CD.
All looks good for the moment. Once again, thanks to you and your colleagues for all of your assistance.
-
Marked as answer by
暁北
Friday, November 15, 2013 5:53 AM -
Edited by
Duane John
Friday, November 15, 2013 9:37 AM
-
Marked as answer by
- Remove From My Forums
-
Question
-
G’day,
This problem is causing me a hell of a lot of grief at the moment. My computer bluescreens randomly. Sometimes it will run for days without issue, and other days it will bluescreen once or twice. There does not seem to be any discernible pattern. Any advice
would be greatly appreciated. Thanks in advance.Details as follows:
TOSHIBA Satellite C650 PSC12A-00S00T
OS: Windows 7 Home Premium Service Pack 1 (32 bit)
RAM: 4 GB
Dump File 110213-32838-01.dmp Crash Time 2/11/2013 22:03 Bug Check String KERNEL_MODE_EXCEPTION_NOT_HANDLED Bug Check Code 0x1000008e Parameter 1 0xc0000046 Parameter 2 0x83a90e0f Parameter 3 0xc560b5a0 Parameter 4 0x00000000 Caused by Driver halmacpi.dll Caused by Address halmacpi.dll+5ba9 File Description Hardware Abstraction Layer DLL Product Name Microsoft® Windows® Operating System Company Microsoft Corporation File Version 6.1.7601.17514 (win7sp1_rtm.101119-1850) Processor 32-bit Crash Address ntkrnlpa.exe+80e0f Stack Address 1 ntkrnlpa.exe+80bf1 Stack Address 2 ULCDRHlp.sys+30e4 Stack Address 3 ULCDRHlp.sys+a7f File Path C:WindowsMinidump110213-32838-01.dmp Processor Count 4 Major Version 15 Minor Version 7601 Dump File Size 147,680
Answers
-
Duane
These were Related to
ULCDRHlp.sys ULCDRHlp driver from Ulead Systems, Inc. Yours is from
2004. Remove Ulead completely.Other old drivers needing updating
pcouffin.sys 12/5/2006 9:39:53 AM
modrc.sys 7/11/2007 3:06:20 AM
PxHelp20.sys 10/17/2007 1:24:26 PM
CSN5PDTS82.sys 4/22/2009 5:37:57 AM
sxuptp.sys 5/7/2009 11:13:24 PM
pgeffect.sys 6/22/2009 4:04:57 AMhttp://www.carrona.org/drivers/driver.php?id=pcouffin.sys
http://www.carrona.org/drivers/driver.php?id=modrc.sys
http://www.carrona.org/drivers/driver.php?id=PxHelp20.sys
http://www.carrona.org/drivers/driver.php?id=sxuptp.sys
http://www.carrona.org/drivers/driver.php?id=pgeffect.sysBugCheck 1000008E, {c0000046, 83a90e0f, c560b5a0, 0} Probably caused by : ULCDRHlp.sys ( ULCDRHlp+30e4 ) ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨`` BugCheck 1000008E, {c0000046, 83a90e0f, c28a15a0, 0} Probably caused by : ULCDRHlp.sys ( ULCDRHlp+30e4 ) ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨`` BugCheck 1000008E, {c0000046, 83acfe0f, 9db2f5a0, 0} Probably caused by : ULCDRHlp.sys ( ULCDRHlp+30e4 ) ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨`` BugCheck 1000008E, {c0000046, 83ab8e0f, 8e1fb1e0, 0} Probably caused by : ULCDRHlp.sys ( ULCDRHlp+313c ) ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨`` BugCheck 1000008E, {c0000046, 83a87e0f, ef65b5a0, 0} Probably caused by : ULCDRHlp.sys ( ULCDRHlp+30e4 ) ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨`` BugCheck 1000008E, {c0000046, 83a88e0f, cd270410, 0} Probably caused by : ULCDRHlp.sys ( ULCDRHlp+313c ) ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨`` BugCheck 1000008E, {c0000046, 83ab9e0f, b9cff5a0, 0} Probably caused by : ULCDRHlp.sys ( ULCDRHlp+30e4 )
Wanikiya and Dyami—Team Zigzag
-
Proposed as answer by
Friday, November 15, 2013 3:54 AM
-
Marked as answer by
暁北
Friday, November 15, 2013 5:52 AM
-
Proposed as answer by
-
Duane
I am unsure about what Ulead did back in 2004 but what you could try is to rename the driver (just in case) from *.sys to *.bak so it cant load. If nothing complains you can then delete it or follow the procedures you have suggested.
Wanikiya and Dyami—Team Zigzag
-
Marked as answer by
暁北
Friday, November 15, 2013 5:52 AM
-
Marked as answer by
-
Hello,
I’ve disabled the Ulead Burning Helper service, and renamed the driver: C:WindowsSystem32driversULCDRHlp.old — That was interesting. Restarted my computer, started Windows Media Centre, was able to activate the TV tuner. All looked good so far. I then tried
to burn files to a CD. Failed. It seems I have now lost the DVD drive.I then opened the Computer Management console and scanned for hardware changes. This re-installed the DVD drive, and I have just now successfully burned some data to a CD.
All looks good for the moment. Once again, thanks to you and your colleagues for all of your assistance.
-
Marked as answer by
暁北
Friday, November 15, 2013 5:53 AM -
Edited by
Duane John
Friday, November 15, 2013 9:37 AM
-
Marked as answer by
If you have ever encountered with the blue screen error, then you might be aware of the fact how frustrating experience it is. Commonly it is known as (BSOD), the error occurs because of hardware or driver related glitches that can create a serious impact on Windows.
To fix the blue screen error on Windows 7, you will need to check common causes of BSOD like Ram and drivers. To resolve the issue, you can reinstall the faulty driver, clean-up your hard disk, run virus and registry scans, and perform other fixes. You can adopt one of the below-mentioned methods to get rid of blue screen error.
Method 1: Use Driver Verifier to find faulty driver(s) and fix them
- Enable Driver Verifier by clicking on Start orb, open cmd, and files box, right click on cmd and choose Run as administrator
- In Command Prompt type verifier /standard /all. Don’t forget to provide space between the verifier and /standard and /all.
- Reboot your system and keep it running until it got crashes.
- Make a listing of faulty drivers, then download and install the latest version of these all.
- Just after installing new drivers boot your computer into Safe Mode. Turned off your computer, press the power button on and immediately tap the F8 key. You will receive Advanced Boot Options.
- Navigate to Safe Mode in Advanced Boot Options, and press Enter. This will boot your computer into the Elevated Command Prompt.
- Disable the Driver Verifier, by typing verifier /reset in Command Prompt.
- Type Exit in Command Prompt, and then reinstate your device, and you will not get Blue Screen Error on your computer.
Method 2: Run Malware, Virus and Registry Scan
Perform malware, virus and registry scan, while keeping your computer in safe mode. This is the preferable time to run these apps as any viruses that try to disable them normally get disabled itself in this mode. Another useful scan that needs to address is odd Registry entries. A highly recommendable open source app that people use to check the registry for any known problems is the Little Registry Cleaner; you can use this app to address your problem in the best possible manner.
Method 3: Opt for system restoring
If both of the methods as mentioned above don’t work for you, then it’s better to opt for restoring your system. Open the CP (Control Panel) and then go to Security and system, check for Backup and Restore, and select “Recover System Settings for your Computer“.
Follow the instructions, after choosing a valid restore point from the list. Ensure you are restoring a system to a date where your computer was running fine. Finally, if it doesn’t work for you, then you need to look at your hard disk to resolve the issue.
A computer that is working perfectly can lead to blue screen error just because one faulty piece of hardware or software installed in it. If your computer reflects blue screen error once in a while, then nothing is serious. However, if you are getting it frequently, then you should try one of the any of the mentioned methods to resolve your issue as soon as possible.
Kevin Arrows
Kevin is a dynamic and self-motivated information technology professional, with a Thorough knowledge of all facets pertaining to network infrastructure design, implementation and administration. Superior record of delivering simultaneous large-scale mission critical projects on time and under budget.