Event ID 7026 Source Service Control Manager
| Event ID | 7026 |
| Source | Service Control Manager |
| Type | Error |
| Description | The following boot-start or system-start driver(s) failed to load: <device name> |
| English, please! | This information is only available to subscribers. An example of English, please! |
| Concepts to understand | What is the role of the Service Control Manager? |
| Comments |
Adrian Grigorof
If a device is not working properly, its driver fails to load when Windows starts. A device can be related to a backup tape, cdrom driver, zip drive, any type of hardware actually. The message is quite typical to occur when a a tape drive is removed from a server. See the following Q articles for various devices: - M129115 for PRLNTSS.SYS - M157678 and M152346 for 4mmdat.sys - M178558 for HPDANT Dave Murphy (Last update 2/2/2009): Device: halfinchVRTS - Resolution may involve loading the Symantec plug and play device drivers for tape drives. Additionally, though not in my case, can be related to SCSI driver conflicts. We were working with an old version of Veritas 9.1. Pending an update to see if the error goes away. See Symantec Document ID 281781. SchroederX (Last update 2/2/2009): Device: nvport - Error occured after Nvidia Pure Video Decoder was uninstalled from the system. The file is removed from the system32/drivers directory but remains in registry. To resolve this issue go to the registry editor and delete the following keys: [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\nvport] [HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\nvport] [HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\Services\nvport] Please perform a backup of the existing registry before removing any registry keys. Anonymous (Last update 1/6/2008): - Device: IPMIDRV - The Intelligent Platform Management Interface server management system does not work in Windows Server 2003 R2. See M912134 for details. Oyvind Johansen (Last update 10/22/2007): - Device: i8042prt - In my case deleting the registry key: [HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\i8042prt] solved this issue. Why bother deciphering Event logs when GFI EventsManager can do everything for you? Free trial here! Charley Rouse (Last update 8/18/2006): - Device: i8042prt - In my case, there was an issue with Hotplugging of the USB keyboard. I solved this problem by opening the registry, going to [HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\i8042prt\Parameters] and changing the value Headless data to 0x1 (Allow Hotplugging). Mihai Andrei (Last update 3/7/2006): - Device: i2oexec iopbus - See "Intel Support Solution ID: CS-001293". - Device: Adsmscsi - See the link to "IBM Support Reference #1111729". - Device: Cpq32fs2.sys - See M244984. - Device: i8042prt - From a newsgroup post: "i8042prt is a keyboard or a mouse driver. Try deleting this driver and see if Windows operates normally and then reinstall your device (either keyboard or mouse) relating to this driver". Make a back-up first. Ionut Marin (Last update 6/28/2005): - Device: tratapi-VRTS - See the link to "Veritas Support Document ID: 231444". - Device: SAVRT - See the link to "Symantec Support Document ID: 2004072905471148". See M184208 and MSW2KDB for information regarding this event. Sorin Ciulpan (Last update 3/18/2005): - Device: cmosa - As per M319129, "This issue may occur after you apply Microsoft's BIOS3 Y2K Update (Biosfixi.exe) to a computer that was installed by using Dell Computer Corporation's OpenManage Client computer imaging software. The computer contains drivers that are leftover from the imaging process". Contact Dell to resolve this problem. Andreas Rosén (Last update 9/10/2003): Device: i8042prt - it could be because you have an USB-connected keyboard but PS/2 keyboard support is still enabled in BIOS. Anonymous (Last update 9/10/2003): Device: IMOUFLTR - Found it to be associated with the Logitech mouse driver. Removed and reinstalled software and the error went away. Woodrow Wayne Collins (Last update 5/21/2003): Device: "Otman4" - Otman4.sys is the driver which is Open File Option (OFO). It is used to make the static volume OFO uses to protect open/changed files. If the file is missing or corrupt, this error could occur. To resolve this error OFO must be reinstalled. See Veritas TechNote ID: 239054 link. Mario C (Last update 5/19/2003): A Windows 2000 professional workstation kept getting this error along with blue screen of death with STOP: 0x0000007B (INACCESSIBLE_BOOT_DEVICE). The cable to the hard drive was good so I got the computer to boot into safe mode, then updated the driver on the hard drive and ran CHKDSK /F. The computer then rebooted normally. I still need to replace the hard drive, it is making a lot of noise while running. Paul Mooney Device: Cdrom - I got this problem on my Dell PowerEdge after I received a problem with an IDE drive on the same cable. However, after fixing the bad block problem the hard drive, the CD drive failed to load and I could not see it in my computer. To fix this go into the BIOS at startup (F2). Turn on the Num Lock, Scroll Lock and Caps Lock keys (ensure all light are on on the keyboard). Then press Alt-E and Alt-F to reset the BIOS. Reboot the machine and the CD Rom drive will be available again. This also works for Optiplex and newer Dimension systems. Note: you will have to reset any other changes you made to the BIOS before the reset. Why bother deciphering Event logs when GFI EventsManager can do everything for you? Free trial here! |
| Links | M129115, M152346, M157678, M178558, M184208, M244984, M319129, M912134, Intel Support Solution ID: CS-001293, IBM Support Reference #1111729, Veritas TechNote ID: 239054, Veritas Support Document ID: 231444, Symantec Support Document ID: 2004072905471148, MSW2KDB, Symantec Document ID 281781 |
| Search | Google Web - Microsoft Support - Bing - EventID.Net Queue - More links... |
| Custom search | The custom search information is available to subscribers only. |
| Feedback | Send comments - Notify me when updated |
| Print version |