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: Newest
Most helpful Newest Oldest
  1. 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
  2. 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
  3. Anonymous
    2014-01-09T18:33:04+00:00

    Barry

    That is better than I feared.

    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 fresh copies of your System and Application logs from your Event Viewer to your Sky Drive and post a link here. You can remove the earlier copies of the logs from your Sky Drive.

    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-09T16:27:58+00:00

    Here is what happened:

    1. I chose the option "Restore to a previous system image".  That failed, as I had expected, because the Windows directory had not yet been completely rebuilt, and there was no system image.
    2. I did something (I did not keep exact notes), and I got into a "System repair".  The machine was attempting a repair (with constant disk activity) for about two hours before the repair failed.
    3. I rebooted (with the Windows 7 DVD removed), and the initial Windows repair session continued at sreenshot/step 13.
    4. There were a number of reboots, plus a message about a corrupt .jpg file in, I think. my \Users directory.  The file was from some software I have installed.  I looked, and I could not find that directory, but I did not do a thorough search, nor did I write the entire path to that corrupt file.  I am not worried about a potentially corrupt graphical image.
    5. Eventually there was a window stating that .NET 4.5 needed to be repaired.
    6. At about the same time I was prompted to enter the license key; the key was accepted.
    7. I rebooted after .NET 4.5 was repaired; I am not sure what was done during the repair.
    8. At 18:05 Windows was up and running.  Windows Update showed 133 patches, which I installed.

    One failed.  WU then showed 9 patches, which I installed.  I did not install IE11.  There are two Bing updates that are shown to me each time I open Windows Update, and each time I hide those two.  I have no idea why Windows does not remember my "hide" commands.

    1. Windows repair did not keep my WU setting (let me install updates on my schedule), so Windows Update auto-installed IE11 at 03:05 this morning, with an auto-reboot.  I do not like auto reboots, as I sometimes have applications open overnight.
    2. At 03:56 I saw in the System EventLog an EventID 55 (NTFS) entry, and there were two more later at 8:01.  I ran chkdsk c: at 8:15, and there were no problems found.
    3. At 08:28 WU had me install two more security patches, one for IE11 and one for Win 7.   The reboot after those patches did an auto-chkdsk c::, and there were no problems found.

    I have no idea what the NTFS "process" thinks is wrong with my disk, when chkdsk finds nothing.  Is there any way to get more diagnostics when the EventID 55 is written to know what NTFS thinks is wrong?  I do not know if the "Details" tab in the EventLog entry has further information; I have not yet done a Google search.

    Thanks.

    --Barry Finkel

    Was this answer helpful?

    0 comments
  5. Anonymous
    2014-01-09T13:03:20+00:00

    Barry

    What is happening or has happened?

    Was this answer helpful?

    0 comments