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
    2014-01-10T15:20:08+00:00

    Barry

    It is certainly worth trying.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2014-01-10T14:21:44+00:00

    One moire item - I did a search on EventID 55, and I found and downloaded

         46836-intl_i386z.zip.exe

    via

          http://support.microsoft.com/kb/2885209/en-us

    I have not instelled it.  Do you think that it might fix the EventId 55 proems?

    --Barry Finkel

    Was this answer helpful?

    0 comments
  3. Anonymous
    2014-01-10T02:35:29+00:00

    Gerry, how is chkdsk run in an administrator cmd window any different that running it during a reboot?  And is there a difference in specifying the "/f" option if chkdsk does not find any errors?  I just ran chkdsk, and the output is below.  I ran a clean chkdsk this morning at 08:15, and a clean chkdsk was run yesterday at 17:43 during the last auto-reboot before the Windows repair finished.

    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.

      1490 large file records processed.

      0 bad file records processed.

      4 EA records processed.

      104 reparse records processed.

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

      624924 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.

      60943 data files processed.

    CHKDSK is verifying Usn Journal...

      37320512 USN bytes processed.

    Usn Journal verification completed.

    Windows has checked the file system and found no problems.

     261369485 KB total disk space.

     130049468 KB in 270780 files.

        175004 KB in 60944 indexes.

             0 KB in bad sectors.

        618537 KB in use by the system.

         65536 KB occupied by the log file.

     130526476 KB available on disk.

          4096 bytes in each allocation unit.

      65342371 total allocation units on disk.

      32631619 allocation units available on disk.

    C:\Windows\system32>

    --Barry Finkel

    Was this answer helpful?

    0 comments
  4. Anonymous
    2014-01-10T00:03:55+00:00

    Barry

    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.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2014-01-09T21:17:55+00:00

    I have uploaded the three files you requested.  I was NOT in safe mode when I ran them.

    sysinfo.140109.nfo               http://sdrv.ms/JL623F

    SystemLog.140109.evtx        http://sdrv.ms/1imUpMg

    ApplicationLog.140109.evtx  http://sdrv.ms/JL6e38

    --Barry Finkel

    Was this answer helpful?

    0 comments