Constant memory_management BSODs

writhziden said:

Manually set the first four timing to 9-9-9-20 with a command rate of 2T. Start by setting the DRAM voltage back to AUTO. See if it improves stability.

I changed the timing and the voltage, but I don't see anything to change command rate.

I've also run chkdsk

Code:

Log Name:      Application
Source:        Microsoft-Windows-Wininit
Date:          25/02/2012 1:26:53 AM
Event ID:      1001
Task Category: None
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      Khoi-PC
Description:


Checking file system on C:
The type of the file system is NTFS.

A disk check has been scheduled.
Windows will now check the disk.                         

CHKDSK is verifying files (stage 1 of 5)...
  463616 file records processed.                                         

File verification completed.
  1046 large file records processed.                                   

  0 bad file records processed.                                     

  0 EA records processed.                                           

  60 reparse records processed.                                      

CHKDSK is verifying indexes (stage 2 of 5)...
  530060 index entries processed.                                        

Index verification completed.
  0 unindexed files scanned.                                        

  0 unindexed files recovered.                                      

CHKDSK is verifying security descriptors (stage 3 of 5)...
  463616 file SDs/SIDs processed.                                        

Cleaning up 69 unused index entries from index $SII of file 0x9.
Cleaning up 69 unused index entries from index $SDH of file 0x9.
Cleaning up 69 unused security descriptors.
Security descriptor verification completed.
  33223 data files processed.                                           

CHKDSK is verifying Usn Journal...
  36613568 USN bytes processed.                                            

Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
  463600 files processed.                                                

File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
  209782298 free clusters processed.                                        

Free space verification is complete.
Windows has checked the file system and found no problems.

 976657407 KB total disk space.
 136814108 KB in 154245 files.
    116000 KB in 33224 indexes.
         0 KB in bad sectors.
    598107 KB in use by the system.
     65536 KB occupied by the log file.
 839129192 KB available on disk.

      4096 bytes in each allocation unit.
 244164351 total allocation units on disk.
 209782298 allocation units available on disk.

Internal Info:
00 13 07 00 59 dc 02 00 7c 77 05 00 00 00 00 00  ....Y...|w......
2e 03 00 00 3c 00 00 00 00 00 00 00 00 00 00 00  ....<...........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................

Windows has finished checking your disk.
Please wait while your computer restarts.

Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Wininit" Guid="{206f6dea-d3c5-4d10-bc72-989f03c8b84b}" EventSourceName="Wininit" />
    <EventID Qualifiers="16384">1001</EventID>
    <Version>0</Version>
    <Level>4</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2012-02-25T08:26:53.000000000Z" />
    <EventRecordID>13133</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>Application</Channel>
    <Computer>Khoi-PC</Computer>
    <Security />
  </System>
  <EventData>
    <Data>

Checking file system on C:
The type of the file system is NTFS.

A disk check has been scheduled.
Windows will now check the disk.                         

CHKDSK is verifying files (stage 1 of 5)...
  463616 file records processed.                                         

File verification completed.
  1046 large file records processed.                                   

  0 bad file records processed.                                     

  0 EA records processed.                                           

  60 reparse records processed.                                      

CHKDSK is verifying indexes (stage 2 of 5)...
  530060 index entries processed.                                        

Index verification completed.
  0 unindexed files scanned.                                        

  0 unindexed files recovered.                                      

CHKDSK is verifying security descriptors (stage 3 of 5)...
  463616 file SDs/SIDs processed.                                        

Cleaning up 69 unused index entries from index $SII of file 0x9.
Cleaning up 69 unused index entries from index $SDH of file 0x9.
Cleaning up 69 unused security descriptors.
Security descriptor verification completed.
  33223 data files processed.                                           

CHKDSK is verifying Usn Journal...
  36613568 USN bytes processed.                                            

Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
  463600 files processed.                                                

File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
  209782298 free clusters processed.                                        

Free space verification is complete.
Windows has checked the file system and found no problems.

 976657407 KB total disk space.
 136814108 KB in 154245 files.
    116000 KB in 33224 indexes.
         0 KB in bad sectors.
    598107 KB in use by the system.
     65536 KB occupied by the log file.
 839129192 KB available on disk.

      4096 bytes in each allocation unit.
 244164351 total allocation units on disk.
 209782298 allocation units available on disk.

Internal Info:
00 13 07 00 59 dc 02 00 7c 77 05 00 00 00 00 00  ....Y...|w......
2e 03 00 00 3c 00 00 00 00 00 00 00 00 00 00 00  ....&lt;...........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................

Windows has finished checking your disk.
Please wait while your computer restarts.
</Data>
  </EventData>
</Event>

DRAM Timing mode: 2N = 2T, verify after setting it that CPU-Z shows 2T for the Command Rate under the Memory tab.

Well, I crashed again after running chkdsk. Was going good for a few days

Code:

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [D:\Kingston\BSODDmpFiles\Joaks\minidump\022712-33789-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*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 Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02e52000 PsLoadedModuleList = 0xfffff800`03097670
Debug session time: Mon Feb 27 20:43:35.781 2012 (UTC - 7:00)
System Uptime: 0 days 3:31:42.170
Loading Kernel Symbols
...............................................................
................................................................
.................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 34, {55f, ffffffffc0000420, 0, 0}

Unable to load image \??\C:\Windows\system32\drivers\aswMonFlt.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for aswMonFlt.sys
*** ERROR: Module load completed but symbols could not be loaded for aswMonFlt.sys
Probably caused by : aswMonFlt.sys ( aswMonFlt+7603 )

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

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

CACHE_MANAGER (34)
    See the comment for FAT_FILE_SYSTEM (0x23)
Arguments:
Arg1: 000000000000055f
Arg2: ffffffffc0000420
Arg3: 0000000000000000
Arg4: 0000000000000000

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


EXCEPTION_RECORD:  ffffffffc0000420 -- (.exr 0xffffffffc0000420)
Cannot read Exception record @ ffffffffc0000420

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x34

PROCESS_NAME:  AvastSvc.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002f430c3 to fffff80002ecec40

STACK_TEXT:  
fffff880`0804d488 fffff800`02f430c3 : 00000000`00000034 00000000`0000055f ffffffff`c0000420 00000000`00000000 : nt!KeBugCheckEx
fffff880`0804d490 fffff800`031b8dc2 : 00000000`00000000 00000000`00104f67 fffff880`0804d560 fffff880`0804d5f0 : nt! ?? ::FNODOBFM::`string'+0x3b51b
fffff880`0804d520 fffff880`012adf08 : fffff880`00000000 00000000`00000004 fffffa80`068fcd60 fffffa80`00000001 : nt!CcCopyRead+0x132
fffff880`0804d5e0 fffff880`010d8098 : fffffa80`04835bd0 fffffa80`068fccf8 fffffa80`05e3ba00 00000000`00000001 : Ntfs!NtfsCopyReadA+0x1a8
fffff880`0804d7c0 fffff880`010db8ba : fffff880`0804d8b8 fffffa80`05e3ba03 fffff880`0804da00 00000000`00000000 : fltmgr!FltpPerformFastIoCall+0x88
fffff880`0804d820 fffff880`010e91a0 : 00000000`00000004 00000000`00000000 fffffa80`04835bd0 00000000`00000000 : fltmgr!FltpPassThroughFastIo+0xda
fffff880`0804d860 fffff880`053c6603 : fffffa80`063b1b80 00000000`00000000 fffffa80`00000001 fffffa80`06a799d0 : fltmgr!FltReadFile+0x260
fffff880`0804d940 fffffa80`063b1b80 : 00000000`00000000 fffffa80`00000001 fffffa80`06a799d0 fffff880`00b73d30 : aswMonFlt+0x7603
fffff880`0804d948 00000000`00000000 : fffffa80`00000001 fffffa80`06a799d0 fffff880`00b73d30 fffff680`00000004 : 0xfffffa80`063b1b80


STACK_COMMAND:  kb

FOLLOWUP_IP: 
aswMonFlt+7603
fffff880`053c6603 ??              ???

SYMBOL_STACK_INDEX:  7

SYMBOL_NAME:  aswMonFlt+7603

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: aswMonFlt

IMAGE_NAME:  aswMonFlt.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4f4664fc

FAILURE_BUCKET_ID:  X64_0x34_aswMonFlt+7603

BUCKET_ID:  X64_0x34_aswMonFlt+7603

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

Caused by avast!

Please replace avast! by first uninstalling it with the avast uninstall utility and replace it with Microsoft Security Essentials - Free Antivirus for Windows to run with Windows firewall. You can also read about the Good and Free system security combination.

...

I reinstalled but it's still crashing. ¯\_(ツ)_/¯

Code:

Loading Dump File [D:\Kingston\BSODDmpFiles\Joaks\docs\Windows_NT6_BSOD_jcgriff2\032112-17612-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 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02c0f000 PsLoadedModuleList = 0xfffff800`02e4ce50
Debug session time: Wed Mar 21 19:22:18.363 2012 (UTC - 6:00)
System Uptime: 0 days 0:31:30.455
Loading Kernel Symbols
...............................................................
................................................................
..........
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 4E, {99, 46d9d, 2, 1991c}

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: 0000000000046d9d, page frame number
Arg3: 0000000000000002, current page state
Arg4: 000000000001991c, 0

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


BUGCHECK_STR:  0x4E_99

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  chrome.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002d0f32c to fffff80002c80f00

STACK_TEXT:  
fffff880`08f09f18 fffff800`02d0f32c : 00000000`0000004e 00000000`00000099 00000000`00046d9d 00000000`00000002 : nt!KeBugCheckEx
fffff880`08f09f20 fffff800`02c36545 : 00000000`00000000 fffff680`00014578 00000000`00000002 00000000`00000001 : nt!MiBadShareCount+0x4c
fffff880`08f09f60 fffff800`02c55493 : fffffa80`06dc8060 fffff700`00002510 0000007f`fffffff8 fffff8a0`0761f5c8 : nt! ?? ::FNODOBFM::`string'+0x322ac
fffff880`08f09ff0 fffff800`02c53eee : fffffa80`06dc8060 fffffa80`00000000 fffff880`000015f1 fffff800`00000000 : nt!MiDeleteAddressesInWorkingSet+0x307
fffff880`08f0a8a0 fffff800`02f637af : fffff8a0`0367da70 fffff880`08f0ac20 00000000`00000000 fffffa80`0663d060 : nt!MmCleanProcessAddressSpace+0x96
fffff880`08f0a8f0 fffff800`02f3db3d : 00000000`00000000 00000000`00000001 00000000`7efd5000 00000000`00000000 : nt!PspExitThread+0x47f
fffff880`08f0a9c0 fffff800`02c5da43 : fffffa80`0366db30 00000000`00000000 fffffa80`0663d060 fffff800`02f94094 : nt!PsExitSpecialApc+0x1d
fffff880`08f0a9f0 fffff800`02c5de80 : 00000000`77371c20 fffff880`08f0aa70 fffff800`02f3e710 00000000`00000001 : nt!KiDeliverApc+0x2eb
fffff880`08f0aa70 fffff800`02c801f7 : 00000000`00000001 fffffa80`06d0d420 00000000`00000000 fffff880`08f0ac00 : nt!KiInitiateUserApc+0x70
fffff880`08f0abb0 00000000`74db2dd9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x9c
00000000`014cea08 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x74db2dd9


STACK_COMMAND:  kb

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

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!MiBadShareCount+4c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc600

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c

BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c

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

Still pointing to Memory. Check your memory for your graphics card and run Memtest86+ again (sometimes it misses errors on the the first run):

• Use the |MG| Video Memory Stress Test 1.7.116 Download to test your graphics card memory. Let the memory test run for at least seven passes; the more the better.
  
  
• Run the boot version of Memtest86+ for at least seven passes (more is better) paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).
  
  If you swap any memory components, follow these steps for ESD safety:
  
  1. Shut down and turn off your computer.
  2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
  3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
  4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working.
  
  Once these steps have been followed, it is safe to remove and replace components within your computer.

If you would like to forego the Memtest86+ test, I understand, but I would recommend doing another test of your memory in its place. You can run one module at a time in one slot at a time and see if stability improves through Windows. You want to find a good module and a good slot, then test the known good module in all slots to find any bad slots, and then test the other module in a good slot to determine if the module is bad.

I haven't run memtest yet but the video memory stress test came up with a crazy amount of errors.

After 8 passes there are over 15,000 errors