BSOD: SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION (c1) - Windows 7 Professional

Anonymous
2013-12-17T16:43:19+00:00

In the past week I have experienced on my Windows 7 Professional system three BSODs.  I have done Google searches, and I am not sure what the casuse(s) is/are.  Some sites point to a device driver.  I am running verifier on seven non-MS drivers.  I have loaded the three minidumps to SkyDrive.  I am not sure for what to look in the minidumps (or the full dumps, which I also have)) to locate the failing driver.  Note that I spent 25+ years as an IBM mainframe systems programmer, and I looked at many system dumps during those 25+ years.  I do not know enough about the internals of Windows 7 to be able to look at the dumps and determine what happened.

Also, I have experienced many seemingly random BSODs since I installed a new motherboard on May 25; I am currently concentrating on the last three BSODs, which were all (c1) symptoms.  As far as I know, all of my device drivers are up-to-date; there are web sites that offer me newer drivers, but those are not manufacturers' web sites, so I do not download drivers from them.  I ran a memory test for 8 hours on Sunday; no problems were found.

My last three BSODs were (c1), and there were no dumps of that type in the previous 90 BSODs, so this problem is new.  The first of the three was 12/11 at 09:25, and the previous day I had installed 10 hotfixes on patch Tuesday.

Thanks.

--Barry S. Finkel

Windows for home | Previous Windows versions | Windows update

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

52 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2013-12-22T19:42:06+00:00

    Microsoft Windows [Version 6.1.7601]

    Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

    C:\Windows\system32>time

    The current time is: 13:35:04.55

    Enter the new time:

    C:\Windows\system32>date

    The current date is: Sun 12/22/2013

    Enter the new date: (mm-dd-yy)

    C:\Windows\system32>chkdsk c:

    The type of the file system is NTFS.

    Volume label is Win7-BOOT.

    WARNING!  F parameter not specified.

    Running CHKDSK in read-only mode.

    CHKDSK is verifying files (stage 1 of 3)...

      503040 file records processed.

    File verification completed.

      1681 large file records processed.

      0 bad file records processed.

      4 EA records processed.

      117 reparse records processed.

    CHKDSK is verifying indexes (stage 2 of 3)...

      620786 index entries processed.

    Index verification completed.

      0 unindexed files scanned.

      0 unindexed files recovered.

    CHKDSK is verifying security descriptors (stage 3 of 3)...

      503040 file SDs/SIDs processed.

    Security descriptor verification completed.

      58874 data files processed.

    CHKDSK is verifying Usn Journal...

      35596432 USN bytes processed.

    Usn Journal verification completed.

    Windows has checked the file system and found no problems.

     261369485 KB total disk space.

     122182556 KB in 269562 files.

        174620 KB in 58875 indexes.

             0 KB in bad sectors.

        615729 KB in use by the system.

         65536 KB occupied by the log file.

     138396580 KB available on disk.

          4096 bytes in each allocation unit.

      65342371 total allocation units on disk.

      34599145 allocation units available on disk.

    C:\Windows\system32>

    Was this answer helpful?

    0 comments
  2. Anonymous
    2013-12-22T18:50:30+00:00

    Barry

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

    This indicates a problem as recently as two days ago.

    Please provide a copy of a chkdsk report on your C partition select Start, All Programs, and Accessories, right click on Command Prompt and click Run as Administrator. Type chkdsk and press the ENTER key and a report, detailing amongst other things a summary of how the disk space is utilised, is provided. If you want a report on a partition or drive other than C you need to go to that partition. To access F, where F is the required partition you type F: and press the ENTER key.

    Copying reports from a command prompt can be tricky. Right click and select Mark. This enables you to highlight selected text and click to copy. You then go to an open Word, Notepad or similar file, right click and paste. The selected text transfers from your clipboard to the open file. You can paste directly into a reply message to most forums.

    In Windows 7 you may need to use an Elevated Command Prompt;

    http://www.sevenforums.com/tutorials/783-elevated-command-prompt.html

    Was this answer helpful?

    0 comments
  3. Anonymous
    2013-12-22T16:55:43+00:00

    I have plenty of space on my C: drive, so I see no need to remove the found.000 - found.009 directories.  As I wrote earlier today, I did run chkdsk c: before I rebooted at 09:19; no errors were found.

    --Barry Finkel

    Was this answer helpful?

    0 comments
  4. Anonymous
    2013-12-22T16:27:50+00:00

    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.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2013-12-22T15:49:17+00:00

    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

    Was this answer helpful?

    0 comments