Author Topic: Event Viewer reporting an error with the event ID of 7026  (Read 3506 times)

Offline abensonTopic starter

  • ByteSpeed Technician
  • Newbie
  • ***
  • Posts: 17
Event Viewer reporting an error with the event ID of 7026
« on: March 27, 2013, 04:51:17 PM »
You will also notice that your devices have corrupt or missing drivers.  For example in Device Manager every one of your CPU cores will have a problem.  This is on Windows 7.

We believe antivirus applications are doing this however it doesn't appear to be any particular one.  It is possible that the file is getting infected with a virus but we didn't find any indication in the antivirus logs.  On the machine I was working on, in the Event Viewer you could "watch" the machine turn on with the proper events occurring.  Then the antivirus filters were loaded.  Immediately after that the event viewer lists kernel errors.  You'll notice your machine doesn't work properly almost immediately.

We found a fix and we are also posting the fix here.  Open up the registry file attached and your machine should start working after a reboot.  Here is the contents of that file:

Code: [Select]
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\Wdf01000]
"DisplayName"="Kernel Mode Driver Frameworks service"
"Group"="WdfLoadGroup"
"ImagePath"=hex(2):73,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,64,00,\
  72,00,69,00,76,00,65,00,72,00,73,00,5c,00,57,00,64,00,66,00,30,00,31,00,30,\
  00,30,00,30,00,2e,00,73,00,79,00,73,00,00,00
"ErrorControl"=dword:00000001
"Start"=dword:00000000
"Type"=dword:00000001

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\Wdf01000\Enum]
"0"="Root\\LEGACY_WDF01000\\0000"
"Count"=dword:00000001
"NextInstance"=dword:00000001

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\Wdf01000\Parameters]
"MajorVersion"=dword:00000001
"MinorVersion"=dword:00000009
"BuildNumber"=dword:00001db0

On the blog post that I found it says to replace the wdf01000.sys file with one from a backup.  I found that I didn't have to do that.  I was also working on a 64bit system.  If the registry fix doesn't help, I would try running the System File Checker before trying to find a backup of that file:

http://support.microsoft.com/kb/929833

Since we are working with the registry and adjusting how the driver framework runs, I would recommend backing up your important data.  I don't expect any data corruption however we could potentially cause Windows to quit working completely.

Source:
http://www.explosiveknowledge.net/main/2012/02/05/drvcd3/

 

tech-project-offer