BSOD's Galore, Mostly Special Pool Detected

Welcome to SevenForums.

Ntoskrnl is not the true cause of your crash and blue screen view ain't reliable.

You can take a look at this thread: Debugging A BSOD - My way for some steps if you are interested and want to learn bsods :)

All your BSODs were caused by McAfee and I am not surprised, it is a frequent cause of BSODs. Please remove it using its removal tool from here: Uninstallers (removal tools) for common antivirus software - ESET Knowledgebase

Recommended from a strict BSOD perspective, compatibility & stability compared to other antiviruses/internet security software. It is free and lightweight:-

• Microsoft Security Essentials, Free antivirus for windows.
• Malwarebytes Anti-Malware Free
• Good and Free system security combination
  
  

   Warning

Do not start the free trial of Malware Bytes; remember to deselect that option when prompted.

Run a full scan with both (separately) once downloaded, installed and updated.

Perform a System File Check to check the integrity of all protected Windows 7 :

1. Click on the start
2. Type CMD on Search
3. Left click and Run as Administrator
4. Type
   Code:

   SFC /scannow

Full tutorial here:

• SFC /Scannow Command - System File Checker

Disk Check on your hard drive for file system errors and bad sectors on it.

• How to run Disk Check on Windows 7

Number down items at start-up. Keep only your anti-virus, this also improves the time for logging into windows.

• Startup Programs - Change
• Troubleshoot Application Conflicts by Performing a Clean Startup

Then disable driver verifier.

Let us know the results and further BSOD reports if any.

BSOD BUGCHECK SUMMARY

Code:

Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431
Debug session time: Mon Mar  4 09:40:45.024 2013 (UTC + 6:00)
System Uptime: 0 days 0:09:04.289
*** WARNING: Unable to verify timestamp for mfefirek.sys
*** ERROR: Module load completed but symbols could not be loaded for mfefirek.sys
Probably caused by : mfefirek.sys ( mfefirek+53556 )
SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION (c1)
BUGCHECK_STR:  0xC1_23
VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  McSvHost.exe
FAILURE_BUCKET_ID: X64_0xC1_23_VRF_mfefirek+53556

I think you should start testing hardware:

Upload a screenshot of your hard disk using CrystalDiskInfo:

• CrystalDiskInfo Standard Edition
• How to Upload and Post a Screenshot and File in Seven Forums

Make a hard drive test from the hard drive manufacturers website:

• Hard Drive Diagnostic Procedure

Run Disk Check on your hard disk for file system errors and bad sectors on it:

• Disk Check

Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.

• RAM - Test with Memtest86+

   Note

Pay close attention to part 3 of the tutorial in order to rule out the faulty stick.

   Information

Errors are sometimes found after 8 passes.

   Tip

Do this test overnight, before going to bed.

If Memtest86+ does not find any errors with ram run Windows Memory Diagnostics for 7-8 passes following its tutorial:

• Memory Diagnostics Tool

Here is the screenshot of my hard drive. I will do the memtest tonight, but I do not have a blank disc to do the memory diagnostics so I'll have to get that tomorrow. Thank you so much for your help. Any other tips?

I've asked for more help.

BTW, you should disable Driver Verifier.

• Driver Verifier Enable/Disable

koolkat77 said:

I've asked for more help.

BTW, you should disable Driver Verifier.

• Driver Verifier Enable/Disable

+1. DV is not to use unnecessarily.

ReddRicochet said:

Hello,
Last night I uninstalled McAfee and begin the full scan of Microsoft security essentials. This morning, I woke up to "windows recovered from an unexpected shutdown" error. I know you said it isn't reliable but blue screen viewer said that two memory management blue screens happened. Does this mean anything? Thanks in advance for any help.

The last crash dump we have seen is caused by McAfee. Have you experienced any more BSODs? If so, post it following the Blue Screen of Death (BSOD) Posting Instructions. If not, wait and observe if the situation is stable or not.