Solved 0xC1 SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION on new build

[Archetype]

I recently completed a new computer build and have had nothing but trouble at only a few days old. After many hours of troubleshooting and loading drivers and even an in place upgrade, I am receiving BSOD's at seemingly random instances (even sitting at the desktop). Before going for a second nuke/reinstall, I want to see if anyone else has any suggestions.

Windows - Fully updated
Memtest - No errors after 8 hours of running (I believe it was on pass 7 or 8)
OS SSD - The 840 Evo firmware is up to date and has gone through the performance restoration process.
Safe Mode - Works fine
Drivers - All latest drivers installed from ASUS and Nvidia
Programs - I have uninstalled all virus scan software just to be sure that it was not a cause (I was using Avast)
SFC - Fails (Reason behind in place upgrade). I am not sure if this is related, but would like to avoid another fresh install and ending up back here with the same BSOD's... I have attached CBS log

Any ideas? Thank you!

 

[Golden]

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C9, {220, fffff88007921710, fffff980244dadc0, fffffa80116a2d90}

*** WARNING: Unable to verify timestamp for [B][COLOR="Red"]LGVirHid.sys[/COLOR][/B]
*** ERROR: Module load completed but symbols could not be loaded for LGVirHid.sys
Probably caused by : HIDCLASS.SYS ( HIDCLASS!HidpMajorHandler+0 )

Followup: MachineOwner
---------

6: kd> lmvm lgvirhid
start             end                 module name
fffff880`0a3f8000 fffff880`0a3fa480   LGVirHid T (no symbols)           
    Loaded symbol image file: LGVirHid.sys
    Image path: \SystemRoot\system32\drivers\LGVirHid.sys
    Image name: LGVirHid.sys
    Timestamp:        Tue [B][COLOR="red"]Nov 24[/COLOR][/B] 12:06:48 [B][COLOR="red"]2009[/COLOR][/B] (4B0B38B0)
    CheckSum:         00012CDE
    ImageSize:        00002480
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

The outdated Logitech game panel device driver seems to be an issue. Update it here if possible, else uninstall:
Logitech Support + Downloads

 

[Archetype]

Hello Golden,

Thank you for the response. I have seen the LCD panel driver referenced in a few other post. After receiving a BSOD with a reference to the LGVirHid.sys (This is actually the latest driver; Apparently they have made no changes to the driver since 2009 which is bundled with the latest Logitech Gaming software which [powers my mouse and Logitech G930 headset) I uninstalled the LCD drivers and removed the Logitech Gaming Software, and attempted to restart with a basic usb keyboard with the G-19 unplugged.

I still receive the issue with the keyboard unplugged and also with the LGVirHid driver uninstalled and the keyboard plugged in, so I am thinking that the LGVirHid.sys has been taken care of and there may be something else in play. Is there something later in the dmp's that show anything else?

The most recent BSOD have been for the following which seems to happen every hour or earlier.

On Wed 12/31/2014 8:13:54 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\123114-11887-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xC1 (0xFFFFF980A9976FE0, 0xFFFFF980A9976B68, 0xF4028, 0x32)
Error: SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the driver wrote to an invalid section of the special pool.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 12/31/2014 8:13:54 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xC1 (0xFFFFF980A9976FE0, 0xFFFFF980A9976B68, 0xF4028, 0x32)
Error: SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION
Bug check description: This indicates that the driver wrote to an invalid section of the special pool.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

 

[Golden]

I did see the 2 x 0xC1 .dmp's, but the analysis seemed inconclusive and they didn't point to a specific driver. Can you confirm it was MemTest86+ that you ran, not just plain MemTest86?.

Lets try something else. With the Logitech device uninstalled, please do this:

Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.
http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

Driver Verifier will cause your computer to run very sluggishly - this is normal. What it is trying to do is force your system to BSOD and isolate the offending driver/s. When it does, reboot, disable driver verifier, reboot as normal and upload the new dmp file/s here.

I recommend creating a system restore point before turning on driver verifier:
http://www.sevenforums.com/tutorials/697-system-restore-point-create.html

If your system fails to boot to desktop once driver verifier is enabled, turn it off by booting into Safe Mode:
http://www.sevenforums.com/tutorials/69585-safe-mode.html

 

[Archetype]

Hello Golden,

Happy New Years!

I thought I would give it one more go... I removed the drivers (LCD drivers fully uninstalled) and software once again and re-installed with only my Logitech Mouse, Headset, and the generic keyboard plugged in and tested with a few CPU and GPU intensive task and left it running for a few hours with no issues.

I then took the dive and plugged in my G19 Keyboard and restarted. No issues so far!

I will keep you updated. Thanks again for the help!

Update: I received a 0xa on ntoskrnl & ntkrnlmp.exe a few minutes after posting this message... Please see new dmp

 

[Golden]

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {fffff6fc5015bbe8, 0, 0, fffff800034533a0}

Probably caused by : memory_corruption ( nt!MiRemoveWorkingSetPages+388 )

Followup: MachineOwner
---------

Still inconclusive. Did you run MemTest86+ for 8 consecutive passes? That should take upwards of 12 hrs for 16GB RAM.

 

[Archetype]

Darn...

I ran memtestx86 for about 7 or 8 hours last night (I believe it was on pass 7 or 8) but will give it a go again in the morning

Just curious, did you see anything troubling in the CBS log from SFC? I see references to what looks like a Radeon or ATI driver and AMD 64? I don't have an ATI card or AMD processor so I think these errors are erroneous.

 

[Golden]

I'll have a look at those shortly.

Be sure its MemTest86+ you run please.

 

[Archetype]

After re-enabling Verifier and restarting, I received the attached BSOD with 0xC9 on HIDCLASS.sys

This occurred after having my G19 Keyboard plugged and restarting the computer. As soon as Windows prepares to start I receive this BSOD.

 

[Archetype]

I ran MemTest once more (this time for 10 hours and 9 Passes) and no issues with the RAM.

I unloaded the Logitech Gaming Software and uninstalled the LCD driver, disabled Verifier and so far no crashes with the G19 plugged in.

If I can get the darn thing working with the LCD driver disabled, I would not mind one bit as it is only eye candy...

 

[Archetype]

Golden, I noticed I forgot to add "+" to Memtestx86. It was indeed Memtestx86+ that I was running and removing the drivers for the G19 seemed to do the trick.

I started a thread for a new BSOD I am receiving now http://www.sevenforums.com/bsod-help-support/358336-random-bsod-memory-management-0x1a.html

Thank you for the assistance!