BSOD: SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION (c1) - Windows 7 Professional

Barry

I would remove "05/19/2013  09:47 PM    <DIR>          found.000" etc. Keeping them serves no useful purpose.

Have you run chkdsk as I suggested? You need to do that before we move on to see what needs to be done next.

As for the driver for Virtual Disk Bus Enumerator - I assumed that this was the Comodo vdbus.sys driver rthat I had renamed earlier.  I renamed it back to the original name, and then via the Device Manager uninstalled it.  Then I scanned for new hardware, and the device did not re-appear.  I then rebooted, and the device did not appear in the Device Manager.  I am not going to worry, as I do not use Comodo Backup anymore.

As for corruption on my C: drive - I have seen cases in the past where the drive was corrupted, and I could not determine why.  On my C: drive I have 10 found.nnnn directories from previous disk corruptions and subsequent "chkdsk c: /f" executions.  I ran a chkcsk c: before I rebooted, and there were no errors reported.

05/19/2013  09:47 PM    <DIR>          found.000

07/06/2013  04:43 AM    <DIR>          found.001

08/01/2013  09:09 AM    <DIR>          found.002

08/09/2013  09:59 AM    <DIR>          found.003

08/12/2013  10:25 AM    <DIR>          found.004

08/28/2013  07:36 PM    <DIR>          found.005

09/14/2013  12:30 PM    <DIR>          found.006

09/22/2013  07:38 AM    <DIR>          found.007

10/22/2013  07:36 AM    <DIR>          found.008

12/20/2013  01:54 AM    <DIR>          found.009

In most cases, I cannot tell from the recovered files what directory was corrupted.  There have been times when I have experienced a BSOD, and, upon reboot, Windows 7 Pro automatically ran a chkdsk c:: command.

--Barry Finkel

Barry

Log Name:      System

Source:        Ntfs

Date:          20/12/2013 14:36:10

Event ID:      55

Level:         Error

Computer:      BarryFinkel-PC

Description:

The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume Win7-BOOT.

As a precaution please back up your data files to external media.

Select Start, Run, type cmd and press ENTER. Type "chkdsk c: /f /r" without the quotes and hit ENTER. Make sure you include the spaces indicated. Enter Y when asked whether you wish to run chkdsk on restarting the computer. Exit and restart the computer.

Marking off bad sectors on a hard drive takes time so be patient. Marking off does not repair a bad sector. It places pointers on the drive telling the system not to read or write to those sectors which have been damaged.

If the number of bad sectors continues to increase after you have run the procedure above several times then you should replace the drive. If an important system file is written to a bad sector you can corrupt registry hives and lose the whole contents of the drive.

On the other hand if having run chkdsk you see no more new bad sectors then the drive can work for you for years.

Barry

Code 39

Windows cannot load the device driver for this hardware. The driver may be corrupted or missing. (Code 39)

There are several causes of Code 39 errors:

• A required device driver is missing.
• A required binary file is corrupted.
• There is a problem with the file I/O process.
• A driver that is referencing an entry point in another binary file is unable to load.

Uninstall and reinstall the driver

Uninstall the driver from Device Manager, and then scan for new hardware to install the driver again.

1. In the device's Properties dialog box, click the Driver tab, and then click Uninstall. Follow the instructions.
2. Restart your computer.
3. Open Device Manager, click Action, and then click Scan for hardware changes. Follow the instructions.

Note You may be prompted to provide the path of the driver. Windows may have the driver built-in, or may still have the driver files installed from the last time that you set up the device. However, sometimes, it will open the New Hardware Wizard which may ask for the driver. If you are asked for the driver and you do not have it, you can try to download the latest driver from the hardware vendor's website.

Source: http://support.microsoft.com/kb/310123

The only Device Manager item with a yellow question mark is this:

Virttual Disk Bus Enumerator

   General Properties: Windows cannot load the device driver for the hardware.  The driver may be corrupted or missing.  (Code 39)

   Driver Details: C:\Windows\system32\WdfCoInstaller01009.dll

                   Microsoft

                   1.9.7600.16385 (win7_rtm.090713-1255)

   Device Description: Virtual Disk Bus Enumerator

   Device Instance Path: ROOT\SYSTEM\0001

   Hardware Ids:  root\vdbus

   Service: vdbus

   Device Class: System

   Device class guid: {4d36e97d-e325-11ce-bfc1-08002be10318}

   Driver key: {4d36e97d-e325-11ce-bfc1-08002be10318}\0037

   ConfigFlags: 00000000

   Manufacturer: (Standard system devices)

   Physical Device Object Name: \Device\0000004a

   Capabilities: 00000000

   Enumerator: ROOT

   Security: 00 04 90 00 00 00 00 00 00 00 00 00 00 00 00 14 00 00 00

             00 34 00 02 00 00 00 00 00 18 00 00 00 00 10 01 02 00 00

             00 00 05 20 00 00 00 20 02 00 00 00 00 14 00 00 00 00 10

             01 00 00 00 00 00 05 12 00 00 00

   Security SDS: D:P(A;;GA;;;BA)(A;;GA;;;SY)

   Characteristics: 00000100

                    FILE_DEVICE_SECURE_OPEN

   Power data:

                Current power state:

                D3

                Power capabilities:

                00000009

                PDCAP_D0_SUPPORTED

                PDCAP_D3_SUPPORTED

                Power state mappings:

                S0 -> D0

                S1 -> D3

                S2 -> D3

                S3 -> D3

                S4 -> D3

                S5 -> D3

   Removal policy: 00000001

   Removal policy default: 00000001

   Install state: 00000000

   Base Container Id: {00000000-0000-0000-ffff-ffffffffffff}

   DevNode status: 01802401

                   DN_ROOT_ENUMERATED

                   DN_HAS_PROBLEM

                   DN_DISABLEABLE

                   DN_NT_ENUMERATOR

                   DN_NT_DRIVER

   Problem code: 00000027   [Is this decimal or hex?]

   Parent: HTREE\ROOT\0

   Siblings: Root\*ISATAP\0000

             Root\*TEREDO\0000

             Root\ACPI_HAL\0000

             Root\blbdrive\0000

             Root\COMPOSITEBUS\0000

             Root\COMPOSITE_BATTERY\0000

             Root\LEGACY_AFD\0000

             Root\LEGACY_BEEP\0000

             Root\LEGACY_CBVD\0000

             Root\LEGACY_CLFS\0000

             Root\LEGACY_CNG\0000

             Root\LEGACY_CPUZ135\0000

             Root\LEGACY_CPUZ136\0000

             Root\LEGACY_CSC\0000

             Root\LEGACY_DISCACHE\0000

             Root\LEGACY_DXGKRNL\0000

             Root\LEGACY_EUBKMON\0000

             Root\LEGACY_EUDSKACS\0000

             Root\LEGACY_EUFDDISK\0000

             Root\LEGACY_FVEVOL\0000

             Root\LEGACY_HTTP\0000

             Root\LEGACY_HWPOLICY\0000

             Root\LEGACY_IASTORV\0000

             Root\LEGACY_INTELIDE\0000

             Root\LEGACY_KSECDD\0000

             Root\LEGACY_KSECPKG\0000

             Root\LEGACY_LLTDIO\0000

             Root\LEGACY_MOUNTMGR\0000

             Root\LEGACY_MPSDRV\0000

             Root\LEGACY_MSISADRV\0000

             Root\LEGACY_NDIS\0000

             Root\LEGACY_NDPROXY\0000

             Root\LEGACY_NETBT\0000

             Root\LEGACY_NISDRV\0000

             Root\LEGACY_NPF\0000

             Root\LEGACY_NSIPROXY\0000

             Root\LEGACY_NULL\0000

             Root\LEGACY_PARVDM\0000

             Root\LEGACY_PCW\0000

             Root\LEGACY_PEAUTH\0000

             Root\LEGACY_PSCHED\0000

             Root\LEGACY_RDPCDD\0000

             Root\LEGACY_RDPENCDD\0000

             Root\LEGACY_RDPREFMP\0000

             Root\LEGACY_RSPNDR\0000

             Root\LEGACY_SECDRV\0000

             Root\LEGACY_SMARTDEFRAGDRIVER\0000

             Root\LEGACY_SPLDR\0000

             Root\LEGACY_SSPORT\0000

             Root\LEGACY_STORFLT\0000

             Root\LEGACY_TCPIP\0000

             Root\LEGACY_TCPIPREG\0000

             Root\LEGACY_TDX\0000

             Root\LEGACY_VGASAVE\0000

             Root\LEGACY_VOLMGRX\0000

             Root\LEGACY_VOLSNAP\0000

             Root\LEGACY_WANARPV6\0000

             Root\LEGACY_WDF01000\0000

             Root\LEGACY_WFPLWF\0000

             Root\LEGACY_WRKRN\0000

             Root\mssmbios\0000

             Root\MS_AGILEVPNMINIPORT\0000

             Root\MS_L2TPMINIPORT\0000

             Root\MS_NDISWANBH\0000

             Root\MS_NDISWANIP\0000

             Root\MS_NDISWANIPV6\0000

             Root\MS_PPPOEMINIPORT\0000

             Root\MS_PPTPMINIPORT\0000

             Root\MS_SSTPMINIPORT\0000

             Root\RDPBUS\0000

             Root\RDP_KBD\0000

             Root\RDP_MOU\0000

             Root\SYSTEM\0000

             Root\UMBUS\0000

             Root\vdrvroot\0000

             Root\volmgr\0000

   Container Id: {00000000-0000-0000-ffff-ffffffffffff}

   Safe Removal Required: <false>

   Driver Node Stong Name: oem8.inf:Standard:VDBus_Device:6.1.7100.0:root\vdbus

   Rollback Driver Node Strong Name: oem7.inf:Standard:VDBus_Device:6.1.7100.0:root\vdbus

   Install Date: 5/23/2013 1:06:53 PM

   First Install Date: 5/23/2013 12:08:47 PM

   Driver assembly date: 3/29/2010 6:00:00 PM

   Driver assembly version: 6.1.7100.0

   Driver assembly description: Virtual Disk Bus Enumerator

   lnf name: oem8.inf

   lnf section: VDBus_Device

   lnf section extension: NT

   Matching device id: root\vdbus

   Provider: Comodo Security Solutions

   Device co-installers: WdfCoInstaller01009.dll,WdfCoInstaller

   Rank of Installed Drivber: 00FF0000

   Class long name: System devices

   Class short name: System

   Class icon path: %SystemRoot%\System32\setupapi.dll,-27

   Display name: System devices

   Class co-installers: SysClass.Dll,CriticalDeviceCoInstaller

---

http://www.tomshardware.co.uk/forum/209590-30-which-chipset-driver-version-have#

Error 500 - Ohoh Something is wrong ..

--US2-- It looks like something is broken in our systems...

Perhaps you can find what you are looking for by searching:

---

I do not see code 39 in the URL http://technet.microsoft.com/en-us/library/cc771355(v=ws.10).aspx

---

ApplicationLog.131221.evtx    http://sdrv.ms/1bY4HjC

SysteLog.131221.evtx          http://sdrv.ms/1fPVlIm

---

About the Comodo software - I installed Comodo Backup, and I was using

it to backup my disks.  Then I had a BSOD that pointed to CBUFS.sys,

so I decided to switch to another backup software.  I got no response

from my posting on the Comodo Forums.  Because I might need to restore

a file that is on a Comodo backup file, I decided to rename most of

the Comodo driver files: cbufs.sys, cfrmd.sys, cbparse.sys, cbvd.sys,

vdbus.sys.  I have not uninstalled Comodo Backup.

--Barry Finkel