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-11T00:01:00+00:00

    Barry

    Please allow 2/3 hours for the system to run before uploading further information so that the impact of making changes can become apparent. Restart your computer twice during this time.

    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.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2014-01-10T20:08:41+00:00

    I ran 468386_intl_i386_zip.exe , and it reported that all files had been successfully unzipped.  I assume that it did what it was supposed to do.  Exactly what it did or what it is supposed to do I do not know.

    --Barry Finkel

    Was this answer helpful?

    0 comments
  3. Anonymous
    2014-01-10T18:17:55+00:00

    Barry

    Have you now installed the Hotfix?

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

    Was this answer helpful?

    0 comments
  4. Anonymous
    2014-01-10T17:51:24+00:00

    I re-ran that fixup.  I backed up my c-drive last night; there were no problems.  This morning I saw an error window that "MS Software Shadow Copy Provider had crashed, did I want to send data to MS.  I clicked "Send".   I had today three EventID 7034 items today: 2:38:04, 2:38:09, and  8:22:47 (the event that triggered the error window).  There are over 100 EventID 7034 entries in the SystemLog; the previous one before today was at 12/26 at 9:44AM, and you have these in the SystemLog I uploaded to SkyDrive.

    --Barry Finkel

    Was this answer helpful?

    0 comments
  5. Anonymous
    2014-01-10T15:32:41+00:00

    Barry

    This is something I meant to mention earlier. It resolves a recurring error in your Application. It is nothing to do with main problem.

    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