PFN_LIST_ERROR, MEMORY MANAGEMENT BSOD with new build.

[maxgpcpi]

So I built a new computer (all components in my sig). For those of you not interested in reading the sig, here is an abbreviated version (Biostar 86k+, 2700K, Corsaid 16GB DDR3 1333, MSI GTX 570, Intel 320 160GB SSD). I thought things were going ok but then I began getting BSOD's. I have been getting several different ones. I forget which order they came but I've been getting the PFN_LIST_ERROR message and MEMORY MANAGEMENT errors. I ram memtest86 and Windows Memory Tool and neither found any issues. The most recurring error I am getting is returning this message when I boot up windows. I already bought new RAM (and it's on the way) incase it IS a RAM issue.

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033
Additional information about the problem:
BCCode: 24
BCP1: 00000000001904FB
BCP2: FFFFF880056DD458
BCP3: FFFFF880056DCCB0
BCP4: FFFFF880014C1555
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1
Files that help describe the problem:
C:\Windows\Minidump\082312-16411-01.dmp
C:\Users\Max\AppData\Local\Temp\WER-21715-0.sysdata.xml
Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows
If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

I have attached the Seven Forums info. I tried to look at it myself but got an error with the Tool Kit program. Any help would be appreciated. I downloaded the latest drivers as well.

 

[Anthony]

Can you uninstall Agnitum Ltd Outpost Security Completely and install Microsoft Security Essentials - Free Antivirus for Windows

Just while we find out why we are getting BSODs , there is a lot of memory corruption maybe this is causing it

Thanks

 

[maxgpcpi]

I uninstalled agitum. Should I install the MSE now or just wait?

 

[Anthony]

You need some anti virus if your on the net!!

 

[maxgpcpi]

So I installed MSE and I tried running the SF Tool again to get the new information but it won't run anymore.. Don't know if it matters:

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.IO.FileNotFoundException: Could not find file 'C:\hosts.txt'.
File name: 'C:\hosts.txt'
at Microsoft.VisualBasic.FileIO.FileSystem.CopyOrMoveFile(CopyOrMove operation, String sourceFileName, String destinationFileName, Boolean overwrite, UIOptionInternal showUI, UICancelOption onUserCancel)
at Microsoft.VisualBasic.FileIO.FileSystem.CopyFile(String sourceFileName, String destinationFileName, UIOption showUI, UICancelOption onUserCancel)
at Microsoft.VisualBasic.MyServices.FileSystemProxy.CopyFile(String sourceFileName, String destinationFileName, UIOption showUI, UICancelOption onUserCancel)
at SF_Diag_Toolv3.Form1.Button6_Click(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5456 (Win7SP1GDR.050727-5400)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
SF Diag Toolv3
Assembly Version: 3.0.0.0
Win32 Version: 4.0.0.0
CodeBase: file:///C:/Users/Max/Desktop/SF%20Diagnostic%20Tool.exe
----------------------------------------
Microsoft.VisualBasic
Assembly Version: 8.0.0.0
Win32 Version: 8.0.50727.5420 (Win7SP1.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.VisualBasic/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5456 (Win7SP1GDR.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5460 (Win7SP1GDR.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5462 (Win7SP1GDR.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Runtime.Remoting
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Runtime.Remoting/2.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll
----------------------------------------
CustomMarshalers
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_32/CustomMarshalers/2.0.0.0__b03f5f7f11d50a3a/CustomMarshalers.dll
----------------------------------------
System.Xml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

 

[maxgpcpi]

OK Had to re-download it. Don't know if it helps cause it's so soon but here's the newest scan and sweep with the SF Tool.

 

[Anthony]

Just wait and see if you get a bsod then post it here, I'm off to bed now, so I will carry on tomorrow, unless somebody else jumps in.

Catch you Later

 

[maxgpcpi]

Well I got it again just a minute ago.. The same error. I attached the file.

 

[Anthony]

Probably caused by : memory_corruption

Follow this tutorial: http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

Let us know how it went

Thanks - Ant

 

[maxgpcpi]

Probably caused by : memory_corruption

Follow this tutorial: Probably caused by : memory_corruption

Let us know how it went

Thanks - Ant

Uh.. What tutorial? Also, does that mean the physical RAM is bad and I should replace it?

 

[maxgpcpi]

so I ran memtest86+ overnight and it found no errors.

 

[maxgpcpi]

What I'm going to do is suffer with the BSOD (still getting them). The most recent one was memory management followed by PFN_LIST_ERROR. I will let memtest86+ run from Friday-Sunday and see what it comes up with on Sunday night. Hopefully it's my RAM and not my mobo....

 

[maxgpcpi]

so I ran memtest86+ over the weekend and it found many errors. Where can I go to get that info and to determine what it means?

 

[maxgpcpi]

so I ran memtest86+ over the weekend and it came back with many errors. How do I find the log for memtest and determine what it all means?

From what I can guess (from other forums), the errors I got means that the memory sticks are bad. Does this prove that my slots are still OK or could it be the mobo? I ran the memtest86+ earlier for a few hours (18) and it didn't show up anything.. But after 4 days (friday morning- sunday evening), it came up with all of those errors.

Basically, I'd like to be able to conclude that the memory is at fault so that I can simply buy new ram and be done with it. Is there a way to check the logs?