Windows 7 Windows 7 Pro X64 with 2 BSODs happening

[Firekatt]

First of al, hello to everyone!! I jut finished building a custom pc and am having BSOD's happening. The main one I'm getting is the PFN_LIST_CORRUPT and the other is MEMORY_MANAGMENT. The PFN occurs more frequently then the other one does though. There's no one or two things that I'm doing at the time they happen, in fact, they happen while my PC is sitting at idle. Along with these BS's, I also have applications crashing randomly. This mainly tends to be the 2 online games I play, Lord of the Rings Online and Tera Online. No other applications seem to crash. At first I was thinking that something with the SSD I use for the OS was causing the problem, but after doing some research it seems like it may be a memory problem?? I performed all the steps in the "How to ask for help" thread and attached the folder to this post.

Link Removed

A bit about my system....
Mobo - ASUS M5A99X EVO R2.0 AM3+ AMD 990X SATA 6Gb/s USB 3.0 ATX AMD Motherboard with UEFI BIOS

Processor - AMD FX-4170 Zambezi 4.2GHz (4.3GHz Turbo) Socket AM3+ 125W Quad-Core Desktop Processor FD4170FRGUBOX

Memory - G.SKILL Ripjaws X Series 8GB (2 x 4GB) 240-Pin DDR3 SDRAM DDR3 1866 (PC3 14900) Desktop Memory Model F3-14900CL9D-8GBXL

SSD - G.SKILL Phoenix III FM-25S3-120GBP3 2.5" 120GB SATA III Internal 7mm Solid State Drive

HDD - Seagate Barracuda ST1000DM003 1TB 7200 RPM 64MB Cache SATA 6.0Gb/s 3.5" Internal Hard Drive

Graphics card - NVIDIA GeForce GTX 550 Ti from EVGA with 1023MB Memory

Any help is appreciated and thanks in advance!!!

 

[usasma]

We've seen a number of BSOD issues with SSD's. Here's the information that I've compiled so far:

There's not a whole bunch available to test SSD's. The "easiest" test is to remove the SSD, install a platter-based hard drive, install Windows and test for stability that way.

Here's some suggestions:
- Update the SSD's firmware to the latest available version (VERY IMPORTANT!!!)
- Update the motherboard controllers drivers to the latest available version from the controller manufacturer (NOT the mobo manufacturer unless you can't find any on the controller manufacturer's website)
- Slow the memory (RAM) down to the next slower speed (I've only seen one person who claimed that this worked for them).
- Use any manufacturer's utilities that you may have. If you don't have any, then try this free one (I haven't used it myself): Crystal Dew World
- Update chipset and storage controller drivers to the latest available from the manufacturer of the device (not the manufacturer of the motherboard). Be sure to update ALL controllers on the motherboard!
....NOTE: Recently (Nov 2011) we had BSOD issues with the Marvell 91xx controller and an SSD. You may have to switch controllers also.
- Replace the SSD with a platter based hard drive and see if that stops the BSOD's. If it does, then it's likely that there's a problem with the SSD OR an incompatibility with your system.
It's my opinion that SSD's aren't reliable enough (with current hardware) to be used on a system that needs to work reliably. Until I see reliability I will not recommend, nor will I use, SSD's for critical applications.
06 Dec 2011 - This post tends to confirm issues with certain SSD chipsets and certain controllers - [SOLVED] cant find the cause of BSOD F4 - Tech Support Forum
29 May 2012 - The frequency of BSOD's with SSD's seems to have been decreasing over the last several months. It may be approaching time to re-evaluate my stand on their suitability for use in production systems.
10 Nov 2012 - I'm seeing an upswing in SSD errors - but most appear due to older storage controller drivers. I strongly suggest NOT using storage controller drivers that don't date from 2012 (if none are available, don't connect an SSD to that controller)
05 Jan 2013 - very interesting post about difficulties with the Marvell controllers even when not connected to the SSD drives: https://www.eightforums.com/bsod-cr...-pc-reboots-when-waking-sleep.html#post169956

If you are using the ASMedia controller for your SSD, please ensure that you update it's drivers to the latest 2012 version (this should be done even if you're not using it for the SSD).

Only 113 Windows Updates installed. Most systems have 140 or more. Please visit Windows Update and get ALL available updates (it may take several trips to get them all).

Daemon Tools (and Alcohol % software) are known to cause BSOD's on some Win7 systems (mostly due to the sptd.sys driver, although I have seen dtsoftbus01.sys blamed on several occasions). I strongly suspect that this hold true for Win8 systems also.

Please un-install the program, then use the following free tool to ensure that the troublesome sptd.sys driver is removed from your system (pick the 32 or 64 bit system depending on your system's configuration): [DEL] Link Removed [/DEL] Link broken as of 21 Jul 2012
New link (15 Aug 2012): Link Removed (pick the appropriate version for your system and select "Un-install" when you run it).
Alternate link: Disc-Tools.com
Manual procedure here: Registry and SPTD problems | DAEMON Pro Help

Please remove the Asus Charger Driver from your system while we're troubleshooting. If needed, feel free to install the latest Win7 compatible version AFTER we're finished troubleshooting:
AiChargerPlus.sys Wed Apr 18 21:17:35 2012 (4F8F67AF)
Asus Charger Driver [br] Likely BSOD cause - haven't seen recently (15Jan2013)
Link Removed



Analysis:
The following is for informational purposes only.

[FONT=lucida console]**************************Wed Feb 13 23:26:04.308 2013 (UTC - 5:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\021313-14071-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]0 days 0:02:44.417[/B]
Probably caused by :[B]memory_corruption ( nt!MiUpdateWsle+2b9 )[/B]
BugCheck [B]50, {fffff7063f967558, 1, fffff800030e4469, 2}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: fffff7063f967558, memory referenced.
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
Arg3: fffff800030e4469, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000002, (reserved)
BUGCHECK_STR:  0x50
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  wermgr.exe
FAILURE_BUCKET_ID: [B]X64_0x50_nt!MiUpdateWsle+2b9[/B]
  BIOS Version                  1503
  BIOS Release Date             01/16/2013
  Manufacturer                  To be filled by O.E.M.
  Product Name                  To be filled by O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Wed Feb 13 23:22:40.896 2013 (UTC - 5:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\021313-14149-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]0 days 0:08:04.005[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4ac3 )[/B]
BugCheck [B]1A, {41284, fffff70440200001, 8814, fffff70001080000}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 0000000000041284, A PTE or the working set list is corrupt.
Arg2: fffff70440200001
Arg3: 0000000000008814
Arg4: fffff70001080000
BUGCHECK_STR:  0x1a_41284
PROCESS_NAME:  WerFault.exe
FAILURE_BUCKET_ID: [B]X64_0x1a_41284_nt!_??_::FNODOBFM::_string_+4ac3[/B]
  BIOS Version                  1503
  BIOS Release Date             01/16/2013
  Manufacturer                  To be filled by O.E.M.
  Product Name                  To be filled by O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Wed Feb 13 23:13:57.550 2013 (UTC - 5:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\021313-13696-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]0 days 0:11:37.033[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt!KiPageFault+260 )[/B]
BugCheck [B]D1, {fffff800010dce7a, 2, 8, fffff800010dce7a}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: fffff800010dce7a, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000008, value 0 = read operation, 1 = write operation
Arg4: fffff800010dce7a, address which referenced memory
BUGCHECK_STR:  0xD1
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  audiodg.exe
FAILURE_BUCKET_ID: [B]X64_0xD1_CODE_AV_BAD_IP_nt!KiPageFault+260[/B]
  BIOS Version                  1503
  BIOS Release Date             01/16/2013
  Manufacturer                  To be filled by O.E.M.
  Product Name                  To be filled by O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Wed Feb 13 23:01:40.997 2013 (UTC - 5:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\021313-12963-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]0 days 0:07:17.480[/B]
Probably caused by :[B]memory_corruption ( nt!MiBadShareCount+4c )[/B]
BugCheck [B]4E, {99, 10129, 0, 10229}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 0000000000000099, A PTE or PFN is corrupt
Arg2: 0000000000010129, page frame number
Arg3: 0000000000000000, current page state
Arg4: 0000000000010229, 0
BUGCHECK_STR:  0x4E_99
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID: [B]X64_0x4E_99_nt!MiBadShareCount+4c[/B]
  BIOS Version                  1503
  BIOS Release Date             01/16/2013
  Manufacturer                  To be filled by O.E.M.
  Product Name                  To be filled by O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Wed Feb 13 22:53:44.245 2013 (UTC - 5:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\021313-14008-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]0 days 2:30:06.727[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+136f2 )[/B]
BugCheck [B]1A, {41201, fffff683ff7f8000, 2c80000149b78025, fffffa80086c3140}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 0000000000041201, The subtype of the bugcheck.
Arg2: fffff683ff7f8000
Arg3: 2c80000149b78025
Arg4: fffffa80086c3140
BUGCHECK_STR:  0x1a_41201
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID: [B]X64_0x1a_41201_nt!_??_::FNODOBFM::_string_+136f2[/B]
  BIOS Version                  1503
  BIOS Release Date             01/16/2013
  Manufacturer                  To be filled by O.E.M.
  Product Name                  To be filled by O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Wed Feb 13 20:22:32.553 2013 (UTC - 5:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\021313-12589-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]0 days 0:12:26.036[/B]
Probably caused by :[B]memory_corruption ( nt!MmCopyToCachedPage+223 )[/B]
BugCheck [B]3B, {c0000005, fffff800030b6383, fffff88003c4a8e0, 0}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff800030b6383, Address of the instruction which caused the bugcheck
Arg3: fffff88003c4a8e0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
BUGCHECK_STR:  0x3B
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  WerFault.exe
FAILURE_BUCKET_ID: [B]X64_0x3B_nt!MmCopyToCachedPage+223[/B]
  BIOS Version                  1503
  BIOS Release Date             01/16/2013
  Manufacturer                  To be filled by O.E.M.
  Product Name                  To be filled by O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Wed Feb 13 20:09:00.180 2013 (UTC - 5:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\021313-12979-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]0 days 3:12:02.288[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt!ExAllocatePoolWithTag+537 )[/B]
BugCheck [B]3B, {c0000005, fffff800031be617, fffff8800ad83ed0, 0}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff800031be617, Address of the instruction which caused the bugcheck
Arg3: fffff8800ad83ed0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
BUGCHECK_STR:  0x3B
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  explorer.exe
FAILURE_BUCKET_ID: [B]X64_0x3B_nt!ExAllocatePoolWithTag+537[/B]
  BIOS Version                  1503
  BIOS Release Date             01/16/2013
  Manufacturer                  To be filled by O.E.M.
  Product Name                  To be filled by O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Wed Feb 13 15:53:38.902 2013 (UTC - 5:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\021313-20935-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]0 days 3:39:10.384[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt!CmpReportNotifyHelper+12b )[/B]
BugCheck [B]3B, {c0000005, fffff8000331d53f, fffff8800ce3fd90, 0}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff8000331d53f, Address of the instruction which caused the bugcheck
Arg3: fffff8800ce3fd90, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
BUGCHECK_STR:  0x3B
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID: [B]X64_0x3B_nt!CmpReportNotifyHelper+12b[/B]
  BIOS Version                  1503
  BIOS Release Date             01/16/2013
  Manufacturer                  To be filled by O.E.M.
  Product Name                  To be filled by O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Feb 12 19:46:43.837 2013 (UTC - 5:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\021213-16380-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]0 days 0:18:48.335[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt!CmpDereferenceNameControlBlockWithLock+dc )[/B]
BugCheck [B]C2, {7, 109b, 1060303, fffff8a01562e830}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 0000000000000007, Attempt to free pool which was already freed
Arg2: 000000000000109b, (reserved)
Arg3: 0000000001060303, Memory contents of the pool block
Arg4: fffff8a01562e830, Address of the block of pool being deallocated
BUGCHECK_STR:  0xc2_7_CMNb
PROCESS_NAME:  System
FAILURE_BUCKET_ID: [B]X64_0xc2_7_CMNb_nt!CmpDereferenceNameControlBlockWithLock+dc[/B]
  BIOS Version                  1503
  BIOS Release Date             01/16/2013
  Manufacturer                  To be filled by O.E.M.
  Product Name                  To be filled by O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Feb 12 19:27:21.724 2013 (UTC - 5:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\021213-12558-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]0 days 0:51:56.833[/B]
Probably caused by :[B]memory_corruption ( nt!MiBadShareCount+4c )[/B]
BugCheck [B]4E, {99, 1404b3, 0, 15d0b3}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 0000000000000099, A PTE or PFN is corrupt
Arg2: 00000000001404b3, page frame number
Arg3: 0000000000000000, current page state
Arg4: 000000000015d0b3, 0
BUGCHECK_STR:  0x4E_99
PROCESS_NAME:  FlashPlayerPlu
FAILURE_BUCKET_ID: [B]X64_0x4E_99_nt!MiBadShareCount+4c[/B]
  BIOS Version                  1503
  BIOS Release Date             01/16/2013
  Manufacturer                  To be filled by O.E.M.
  Product Name                  To be filled by O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Feb 12 16:46:36.536 2013 (UTC - 5:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\021213-9890-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]0 days 0:07:22.034[/B]
Probably caused by :[B]memory_corruption ( nt!MiBadShareCount+4c )[/B]
BugCheck [B]4E, {99, 158ffa, 0, 1468fa}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 0000000000000099, A PTE or PFN is corrupt
Arg2: 0000000000158ffa, page frame number
Arg3: 0000000000000000, current page state
Arg4: 00000000001468fa, 0
BUGCHECK_STR:  0x4E_99
PROCESS_NAME:  TurbineLaunche
FAILURE_BUCKET_ID: [B]X64_0x4E_99_nt!MiBadShareCount+4c[/B]
  BIOS Version                  1503
  BIOS Release Date             01/16/2013
  Manufacturer                  To be filled by O.E.M.
  Product Name                  To be filled by O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Feb 12 16:38:45.928 2013 (UTC - 5:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\021213-9406-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]0 days 0:57:10.427[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt!ExFreePoolWithTag+43 )[/B]
BugCheck [B]1000007E, {ffffffffc0000005, fffff80002fb1dd3, fffff880033a8778, fffff880033a7fd0}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80002fb1dd3, The address that the exception occurred at
Arg3: fffff880033a8778, Exception Record Address
Arg4: fffff880033a7fd0, Context Record Address
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
FAILURE_BUCKET_ID: [B]X64_0x7E_nt!ExFreePoolWithTag+43[/B]
  BIOS Version                  1503
  BIOS Release Date             01/16/2013
  Manufacturer                  To be filled by O.E.M.
  Product Name                  To be filled by O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Feb  7 13:10:12.028 2013 (UTC - 5:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\020713-9968-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]0 days 1:02:11.526[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt!CmpDereferenceNameControlBlockWithLock+dc )[/B]
BugCheck [B]C2, {7, 109b, 1050403, fffff8a00903b2e0}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 0000000000000007, Attempt to free pool which was already freed
Arg2: 000000000000109b, (reserved)
Arg3: 0000000001050403, Memory contents of the pool block
Arg4: fffff8a00903b2e0, Address of the block of pool being deallocated
BUGCHECK_STR:  0xc2_7_CMNb
PROCESS_NAME:  System
FAILURE_BUCKET_ID: [B]X64_0xc2_7_CMNb_nt!CmpDereferenceNameControlBlockWithLock+dc[/B]
  BIOS Version                  0601
  BIOS Release Date             07/17/2012
  Manufacturer                  To be filled by O.E.M.
  Product Name                  To be filled by O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Wed Feb  6 16:32:03.634 2013 (UTC - 5:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\020613-10249-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]0 days 1:33:00.133[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt!FsRtlUninitializeBaseMcb+41 )[/B]
BugCheck [B]C2, {7, 109b, 25090101, fffff8a0107ac520}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 0000000000000007, Attempt to free pool which was already freed
Arg2: 000000000000109b, (reserved)
Arg3: 0000000025090101, Memory contents of the pool block
Arg4: fffff8a0107ac520, Address of the block of pool being deallocated
BUGCHECK_STR:  0xc2_7_FSim
PROCESS_NAME:  System
FAILURE_BUCKET_ID: [B]X64_0xc2_7_FSim_nt!FsRtlUninitializeBaseMcb+41[/B]
  BIOS Version                  0601
  BIOS Release Date             07/17/2012
  Manufacturer                  To be filled by O.E.M.
  Product Name                  To be filled by O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Feb  3 01:56:09.007 2013 (UTC - 5:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\020213-9609-01.dmp]
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
[B][COLOR=RED]Missing Windows 7 Service Pack 1[/COLOR][/B]
Built by: [B]7600[/B].17118.amd64fre.win7_gdr.120830-0334
System Uptime:[B]0 days 10:36:22.848[/B]
Probably caused by :[B]memory_corruption ( nt!MiUnlinkPageFromLockedList+8d )[/B]
BugCheck [B]4E, {2, 1495d6, 22efff, 1}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 0000000000000002, A list entry was corrupt
Arg2: 00000000001495d6, entry in list being removed
Arg3: 000000000022efff, highest physical page number
Arg4: 0000000000000001, reference count of entry being removed
BUGCHECK_STR:  0x4E_2
PROCESS_NAME:  TurbineLaunche
FAILURE_BUCKET_ID: [B]X64_0x4E_2_nt!MiUnlinkPageFromLockedList+8d[/B]
  BIOS Version                  0601
  BIOS Release Date             07/17/2012
  Manufacturer                  To be filled by O.E.M.
  Product Name                  To be filled by O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/FONT]

3rd Party Drivers:
The following is for information purposes only.
Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.

[FONT=lucida console]**************************Wed Feb 13 23:26:04.308 2013 (UTC - 5:00)**************************
amdxata.sys                 Fri Mar 19 12:18:18 2010 (4BA3A3CA)
AsUpIO.sys                  Mon Aug  2 22:47:59 2010 (4C57835F)
asmtxhci.sys                Wed Nov  2 23:00:22 2011 (4EB203C6)
asmthub3.sys                Wed Nov  2 23:00:32 2011 (4EB203D0)
asahci64.sys                Thu Jan  5 00:08:19 2012 (4F053043)
[COLOR=RED][B]dtsoftbus01.sys             Fri Jan 13 08:45:46 2012 (4F10358A)[/B][/COLOR]
Rt64win7.sys                Fri Feb  3 08:00:02 2012 (4F2BDA52)
amd_sata.sys                Wed Apr 11 10:40:24 2012 (4F8597D8)
amd_xata.sys                Wed Apr 11 10:40:27 2012 (4F8597DB)
nvhda64v.sys                Tue Jul  3 11:25:04 2012 (4FF30ED0)
RTKVHD64.sys                Tue Aug  7 06:49:39 2012 (5020F2C3)
AsIO.sys                    Wed Aug 22 05:54:47 2012 (5034AC67)
MpFilter.sys                Thu Aug 23 19:03:14 2012 (5036B6B2)
usbfilter.sys               Tue Aug 28 21:27:12 2012 (503D6FF0)
nvlddmkm.sys                Sat Dec 29 01:47:52 2012 (50DE9218)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Wed Feb 13 23:13:57.550 2013 (UTC - 5:00)**************************
cpuz135_x64.sys             Sat Aug 11 03:48:20 2012 (50260E44)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Feb 12 19:46:43.837 2013 (UTC - 5:00)**************************
ASUSFILTER.sys              Tue Sep 20 11:46:33 2011 (4E78B559)
[COLOR=RED][B]AiChargerPlus.sys           Wed Apr 18 21:17:35 2012 (4F8F67AF)[/B][/COLOR]
ndisrd.sys                  Wed May 30 23:03:33 2012 (4FC6DF85)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Feb 12 16:46:36.536 2013 (UTC - 5:00)**************************
usbfilter.sys               Wed Dec 14 02:44:02 2011 (4EE853C2)
RTKVHD64.sys                Tue Feb 14 05:55:35 2012 (4F3A3DA7)
amd_sata.sys                Wed Feb 29 18:37:53 2012 (4F4EB6D1)
amd_xata.sys                Wed Feb 29 18:37:56 2012 (4F4EB6D4)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Feb  3 01:56:09.007 2013 (UTC - 5:00)**************************
amdxata.sys                 Tue May 19 13:56:59 2009 (4A12F2EB)
[/FONT]

Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed

 

[Firekatt]

Thanks for the reply and the info. I have performed the steps you mentioned, removed Deamon tools as well as the .sys files associated with it, and removed the AiCharger driver. Other things I've done in my troubleshooting is last night after posting, I removed 1 memory DIMM from slot 2, reducing me to 4GB instead of 8GB. after doing this, the computer ran fine for several hours. No application crashes and no BSOD. I shut down and went to bed. Turned it on this morning and it ran fine again. After performing the steps you mentioned, I re-installed the DIMM and started getting BSOD's again. I played with the timing in the bios with no luck. I then shut down and switched the 2 DIMMs to slots 3 and 4 instead of 1 and 2. So far, still no BSOD. This is leading me to believe that I have a bad slot on my mobo? I'll let the system idle while I'm at work and see if it blue screens again and keep you updated.

 

[usasma]

Try the memory diagnostic here: Link Removed
Also, try Prime95 (do the Blend test) to stress the RAM: Link Removed

Good luck!

 

[Firekatt]

Problem Solved!!!!

Thanks soooo much for your help as you pointed me onto the right track. It seems that the memory sticks in my system were not 100% compatible with my mobo. After a lot of digging, and contacting Asus support, I learned that the Asus mobo wanted PC3-10600 or PC3-12800 and the sticks I had installed were PC3-14900. The sticks worked fine if there was just one installed but when installed in a dual channel configuration, it caused the BSOD's I was having. I purchased some new sticks from Corsair, another 8GB dual channel kit, and then wiped both drives and reinstalled windows. So far the system has been up and running for 6 hours with no application crashes and no Blue Screens.

I'm very rusty as to my knowledge of memory so I'm not sure why the 14900 caused the errors and why it worked fine if there was just one stick installed, so any enlightenment in that area would be appreciated.

 

[usasma]

Thanks for letting us know! Just FYI - I've seen several of these type memory issues over the last couple of weeks and I suspect that your discovery will make things easier for many people suffering from similar problems. Thanks again!

 

[Firekatt]

Just wanted to update this. The memory change fixed the problem for sure. I't s now been a week and have had no problems at all!!!

 

[usasma]

Thanks for letting us know!

Good luck!