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-06T17:59:41+00:00

    Barry

    Log Name:      Application

    Source:        Microsoft-Windows-Defrag

    Date:          06/01/2014 12:51:15

    Event ID:      257

    Level:         Error

    Description:

    The volume Win7-BOOT (C:) was not defragmented because an error was encountered: The dirty bit is set on this volume. (0x89000015)

      <EventData>

        <Data>Win7-BOOT (C:)</Data>

        <Data>The dirty bit is set on this volume. (0x89000015)</Data>

    Do you have a full Windows 7 Professional  DVD?

    To eliminate recurring Event ID: 10 errors in your Application log please run the Fix it in this KB Article

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

    Was this answer helpful?

    0 comments
  2. Anonymous
    2014-01-06T17:10:57+00:00

    Gerry, I rebooted into safe mode.  In the process I checked the BIOS clock, and the clock was correct.  I have no idea what would cause the systray clock to be fast.  I got the system info and the application and system event logs.

    sysingo.140106.txt               http://sdrv.ms/1efzZ58

    ApplicationLog.140106.evtx  http://sdrv.ms/JDOaaV

    SystemLog.140106.evtx        http://sdrv.ms/1iJQ1ts

    Let me know what you find in these logs.  Thanks.

    --Barry Finkel

    Was this answer helpful?

    0 comments
  3. Anonymous
    2014-01-06T15:46:25+00:00

    Barry

    Please provide a copy of your System Information file. Type System Information in the Search Box above the start Button and press the ENTER key (alternative is Select Start, All Programs, Accessories, System Tools, System Information). Select File, Export and give the file a name noting where it is located. The system creates a new System Information file each time system information is accessed. You need to allow a minute or two for the file to be fully populated before exporting a copy. Please upload to your Sky Drive, share with everyone and post a link here. Please say if the report has been obtained in safe mode.

    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.

    For help with Sky Drive see paragraph 9.3:

    http://www.gerryscomputertips.co.uk/MicrosoftCommunity1.htm

    Was this answer helpful?

    0 comments
  4. Anonymous
    2014-01-06T15:35:30+00:00

    I am not sure where this problem stands - whether it is my turn to reply or yours.

    Here is an update.

    1. I have noticed that the c;lock in the system tray is running fast.  It is now 44 seconds fast.  With my old motherboard, the system tray clock was slow,   When I installed my new motherboard last May 25, the systray clock was accurate, until a few weeks ago, when I noticed that it was fast.  I did a Google search and found one posting where someone had to uninstall and re-install Adobe Acrobat Reader.  I have not done that.
    2. This trouble ticket pertains to a  (c1) BSOD.  Since you replied on Dec 22 I have experienced these BSODs, with minidumps and full dumps:

    12/25/2013  06:29   SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION (c1)  arg4=00000023

    12/26/2013  23:42   MEMORY_MANAGEMENT (1a)

    12/28/2013  18:05   NTFS_FILE_SYSTEM (24)  arg1=001904fb

    12/29/2013  14:52   NTFS_FILE_SYSTEM (24)  arg1=001904fb

    12/30/2013  18:20   SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION (c1)  arg4=00000023

    01/06/2013  05:47   SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION (c1)  arg4=00000023

    I still do not have a handle on what may be causing these c1, 24, or 1a dumps.

    I did see EventLog entries about a corrupt C: drive - EventID 55 "The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume Win7-BOOT.".  The last one occurred at 06:22 this morning.  I just ran a "chkdsk c:" and no errors were reported.  Also, "0 KB in bad sectors"  And there are no chldsk fixups since December 20.  I ran a "sfc /scannow" last week, and I could not tell from the log what file(s) it could not repair.  Thanks.

    --Barry Finkel

    .

    Was this answer helpful?

    0 comments
  5. Anonymous
    2013-12-22T20:04:37+00:00

    Barry

    I do not recollect seeing this before.

    C:\Windows\system32>timeThe current time is: 13:35:04.55Enter the new time:C:\Windows\system32>dateThe current date is: Sun 12/22/2013Enter the new date: (mm-dd-yy)

    Please check the current date and time is correct.

    I was expecting to see a figure for bad sectors but none is there. Strange.

    Was this answer helpful?

    0 comments