Memory Management, Assorted other BSOD

[yamato77]

OS: Windows 7 Professional 64-bit
Processor: Intel Core i5 2320 @ 3.0 GHz
Graphics: Intel HD 2000 (integrated)
RAM: 8 GB

I bought this computer at Microcenter, they manufacture them and sell them under the brand PowerSpec. Mine is the B633 Since I bought it, it had had multiple errors, as shown in the attached .zip. I want to know what I need to do to fix these errors.

I have ran memtest and let it do 10 passes with 0 errors. I am running driver verifier right now and have had 2 BSOD that I have never seen before, one was Special Pool...? Most of the time it is Memory Management BSOD, however.

Should I just take it into the store? I have a warranty with them, for what it is worth.

 

[zigzag3143]

OK so it appears you memory has passed. Verifier points to memory corruption but verifier is often an "iffy" proposition. A few of the crashes point to the OS so we would like you to run a system file check. Make sure you disable verifier before running the System file check,

http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

How to use the System File Checker tool to troubleshoot missing or corrupted system files on Windows Vista or on Windows 7

 

[yamato77]

It says it did not find any integrity violations.

EDIT: added a .zip with the Performance Monitor test that the BSOD forum guidelines said to post.

 

[writhziden]

Security Software:

msmpeng.exe	c:\program files\microsoft security client\antimalware\msmpeng.exe	904	8	200	1380	3/21/2012 2:32 AM	3.0.8402.0	12.48 KB (12,784 bytes)	4/27/2011 6:21 PM
nissrv.exe	c:\program files\microsoft security client\antimalware\nissrv.exe	1092	8	200	1380	3/21/2012 2:32 AM	3.0.8402.0	281.52 KB (288,272 bytes)	4/27/2011 6:21 PM
msseces.exe	c:\program files\microsoft security client\msseces.exe	2452	8	200	1380	3/21/2012 2:32 AM	2.1.1116.0	1.37 MB (1,436,736 bytes)	6/15/2011 3:35 PM

Loading Dump File [D:\Kingston\BSODDmpFiles\yamato77\Windows_NT6_BSOD_jcgriff2\032112-19765-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`02c07000 PsLoadedModuleList = 0xfffff800`02e4b650
Debug session time: Wed Mar 21 01:31:17.831 2012 (UTC - 6:00)
System Uptime: 0 days 0:20:43.675
Loading Kernel Symbols
...............................................................
................................................................
..................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 4E, {99, 1de334, 2, 1de321}

Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )

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

3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

PFN_LIST_CORRUPT (4e)
Typically caused by drivers passing bad memory descriptor lists (ie: calling
MmUnlockPages twice with the same list, etc).  If a kernel debugger is
available get the stack trace.
Arguments:
Arg1: 0000000000000099, A PTE or PFN is corrupt
Arg2: 00000000001de334, page frame number
Arg3: 0000000000000002, current page state
Arg4: 00000000001de321, 0

Debugging Details:
------------------


BUGCHECK_STR:  0x4E_99

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME:  msinfo32.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002d0c20c to fffff80002c83d40

STACK_TEXT:  
fffff880`06c3a628 fffff800`02d0c20c : 00000000`0000004e 00000000`00000099 00000000`001de334 00000000`00000002 : nt!KeBugCheckEx
fffff880`06c3a630 fffff800`02c2bc37 : 00000000`00000000 fffff680`00029658 00000000`00000000 00000001`00000001 : nt!MiBadShareCount+0x4c
fffff880`06c3a670 fffff800`02cb5137 : 00000000`00000000 fffff680`00029ff8 fffffa80`0ada1b30 00000000`02e00000 : nt! ?? ::FNODOBFM::`string'+0x3264d
fffff880`06c3a820 fffff800`02c704bf : fffffa80`00000000 00000000`05519fff 00000000`00000000 00000000`00000000 : nt!MiDeleteVirtualAddresses+0x41f
fffff880`06c3a9e0 fffff800`02c82fd3 : ffffffff`ffffffff 00000000`0024dbd0 00000000`0024dbc8 00000000`00008000 : nt!NtFreeVirtualMemory+0x61f
fffff880`06c3aae0 00000000`772e14fa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0024db98 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x772e14fa


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiBadShareCount+4c
fffff800`02d0c20c cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!MiBadShareCount+4c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4ec79dd2

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x4E_99_VRF_nt!MiBadShareCount+4c

BUCKET_ID:  X64_0x4E_99_VRF_nt!MiBadShareCount+4c

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

We should check the RAM settings:

• Download and install CPU-Z and Upload screenshots of the CPU, Mainboard, Memory, and SPD tabs. In the SPD tab, upload an image of each slot.

 

[yamato77]

I did as you said. Any sections covered up were greyed out.

 

[writhziden]

Alright, remove one module and put it in an anti-static bag or container and see if Windows is more stable. You will want to disable Verifier first. Start Menu -> All Programs -> Accessories -> Right click Command Prompt -> Run as administrator ->

verifier /reset​

-> shut down and turn off your computer -> remove the module.

When moving Memory modules around, Avoid Static Damage to Your PC.

 

[yamato77]

So if I got Memory Management BSOD when using just one stick, then switched to the other and did the exact same thing(s) repeatedly that led up to the BSOD, am I looking at just a stick of bad RAM, or should I test the slot, too?

 

[writhziden]

Test the slots with the good module. See if it works in each slot to rule out the possibility of a bad motherboard slot.