BSOD: SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION (c1) - Windows 7 Professional

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

Barry

From your System Information file

[Problem Devices]

Device PNP Device ID Error Code       

Virtual Disk Bus Enumerator  ROOT\SYSTEM\0001   39         

Type Device Manager in the Search box above the Start button and press ENTER. Are there any yellow question marks in Device Manager? If yes what is the Device Error code.

To see Hidden Devices (Non Plug and Play Drivers) you need to select View, Show Hidden Devices. It is necessary to do this every time you open Device Manager if you need to see them.

A further complication can be Ghosted Devices –installed but not connected!

http://www.lockergnome.com/windows/2005/04/29/display-hidden-devices-in-device-manager-xp/

Error codes in Device Manager:

http://technet.microsoft.com/en-us/library/cc771355(v=ws.10).aspx

In Device Manager right click on the device and select Properties, Details tab. You will see displayed Property and Value. To the right of Property is a scroll. From the list accessed using the scroll, select Device Description and this may give an understandable Device Name as the value. Use the scroll again and select Device Instance Path. The value shown will most likely mean nothing to you. Place the cursor on the value, right click and copy into a further message here.

Please check the chipset installed version:

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

Please upload and share with everyone copies of your System and Application logs from your Event Viewer to your Sky Drive and post a link here.

To access the System log select Start, Control Panel, Administrative Tools, Event Viewer, from the list in the left side of the window select Windows Logs and System. Place the cursor on System, select Action from the Menu and Save All Events as (the default evtx file type) and give the file a name. Do the same for the Applications log. Do not provide filtered files.

I uninst5alled ASC.  I have not done anything with Spybot, as I am not concerned about the extra cycles used.  I like the PC Wizard temperature display in the screen, and I am not concerned about the extra cycles. I finally got the  HECI_allOS_2.1.22.1033_PV.exe installed.  It would not install by itself, as it is designed for XP and Vista.  I found an Intel site that told me how to install that driver.  Since that time

I have experienced three BSOD dumps/reboots:

12/19 21:33 BAD_POOL_HEADER (19) Arg1=20             Minidump 80250

12/20 01:58 BAD_POOL_HEADER (19) Arg1=03             Minidump 55515

12/20 13:11 SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e) Minidump 47343

I have uploaded these files:

121913-80250-01.dmp              http://sdrv.ms/1bWplwV

122013-55515-01.dmp              http://sdrv.ms/1bWpqRg

122013-47343-01.dmp              http://sdrv.ms/1bWpG2S

systeminformationm.131220.txt    http://sdrv.ms/1bWpKPW

driverview.131220.txt            http://sdrv.ms/1l1U3dA

I have no idea what is causing these seemingly random BSODs; I have no idea if they are related.  These three are the 96th - 98th BSODs logged since I replaced my motherboard on May 25.

--Barry Finkel