[Slash12a]

Looks like no luck... Ran well for a little while, but I just BSOD'd with the 'MEMORY_MANAGEMENT' error, then as soon as I logged into the computer again it BSOD'd with 'PFN_LIST_CORRUPT'

[Advertisements]

Hi Slash12a,

One of my colleagues much wiser than I thinks that the symptoms of your machine suggest strongly that your RAM is going bad.

Way to find out would be to try removing one stick of RAM at a time to see if the problem keeps happening.

[emeraldnzl]

Hi Slash12a,

One of my colleagues much wiser than I thinks that the symptoms of your machine suggest strongly that your RAM is going bad.

Way to find out would be to try removing one stick of RAM at a time to see if the problem keeps happening.

[Slash12a]

That's kind of what I'm thinking at this point as well. My only other thought is that when I found out I had to update my BIOS in order to use all my ram it somehow didn't play nice with everything else... I can try rotating out sticks of ram though.

[emeraldnzl]

I can try rotating out sticks of ram though.

It will allow us to discount RAM failure if it doesn't show up anything.

[Slash12a]

I started swapping them out, before I realized that it'd take forever waiting a day or two for each BSOD. So I started swapping out RAM and running memory checks until it came up as a pass instead of failing with a Memory Compare Error. I got it to pass eventually with one stick out. I'm just curious if the slot could be the problem of if it's just the RAM, because I kept all the positions the same (It's triple channel RAM). I'm currently running on two sticks and seeing if anything happens.

[emeraldnzl]

I got it to pass eventually with one stick out.

I will be interested to see if things improve with it out.

I'm just curious if the slot could be the problem of if it's just the RAM, because I kept all the positions the same (It's triple channel RAM).

I think this one does need to be taken to the tech section. Well outside my expertise.

I think here would be the place to open a new topic about the memory and what effect slots might or might not have. Also the fact that it's triple channel RAM... might have chipset implications.

[Slash12a]

I've been running on 2 sticks of RAM for a couple days now and haven't had a game crash or blue screen. The only problem is that my NonPaged pool is still getting really high for no reason, so I'm going to make a post asking about it in the forum you suggested now. I still have to test the slots, but it looks like either that stick of ram or the slot is what was causing all the BSODs at least.

[emeraldnzl]

I've been running on 2 sticks of RAM for a couple days now and haven't had a game crash or blue screen.

I'd say that proves my colleague right about the RAM but as you say... other things going on.

I will follow your progress with interest.

Meantime I will leave this topic open for a day or two and then close.

Best of luck.

emeraldnzl

[Slash12a]

Looks like I spoke too soon... Computer just BSOD'd again with an error that's happened before when running with a stick on that slot, but on the other hand the memtest with this memory passed just fine. I now have no idea if it's my motherboard. I think I'll have to swap the stick I took out and put it in the previous 'Non-BSOD' position and see how that works to find out... I already ordered new RAM though, so hopefully it's not the motherboard...

[emeraldnzl]

Hello Slash12a,

Looks like I spoke too soon... Computer just BSOD'd again

Let's see what this turns up:

Please download Event Viewer by Vino Rosso and save it to your desktop.

• Double-click VEW.exe
• Under 'Select log to query', Check the System box
• Under 'Select type to list', Check Error & Warning boxes
• Under Number or date of Events > 'Number of events' Type 20 in the 1 to 20 box
• Click the Run button.

Notepad will open with a log. Please post the log back here.

[Slash12a]

Vino's Event Viewer v01c run on Windows 2008 in English
Report run at 03/11/2012 1:48:39 PM

Note: All dates below are in the format dd/mm/yyyy

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Critical Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 03/11/2012 5:46:13 AM
Type: Error Category: 0
Event: 18 Source: Microsoft-Windows-WHEA-Logger
A fatal hardware error has occurred. Reported by component: Processor Core Error Source: Machine Check Exception Error Type: Internal Unclassified Error Processor ID: 0 The details view of this entry contains further information.

Log: 'System' Date/Time: 03/11/2012 5:45:51 AM
Type: Error Category: 0
Event: 10016 Source: Microsoft-Windows-DistributedCOM
The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID {C97FCC79-E628-407D-AE68-A06AD6D8B4D1} and APPID {344ED43D-D086-4961-86A6-1106F4ACAD9B} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC). This security permission can be modified using the Component Services administrative tool.

Log: 'System' Date/Time: 03/11/2012 5:45:21 AM
Type: Error Category: 0
Event: 7000 Source: Service Control Manager
The SQL Server (SQLEXPRESS) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion.

Log: 'System' Date/Time: 03/11/2012 5:45:21 AM
Type: Error Category: 0
Event: 7009 Source: Service Control Manager
A timeout was reached (30000 milliseconds) while waiting for the SQL Server (SQLEXPRESS) service to connect.

Log: 'System' Date/Time: 03/11/2012 5:44:47 AM
Type: Error Category: 0
Event: 7000 Source: Service Control Manager
The LogMeIn Kernel Information Provider service failed to start due to the following error: The system cannot find the path specified.

Log: 'System' Date/Time: 03/11/2012 5:44:46 AM
Type: Error Category: 0
Event: 1001 Source: Microsoft-Windows-WER-SystemErrorReporting
The computer has rebooted from a bugcheck. The bugcheck was: 0x00000124 (0x0000000000000000, 0xfffffa8008af5028, 0x00000000fa000000, 0x0000000000400405). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 110312-20092-01.

Log: 'System' Date/Time: 03/11/2012 5:44:43 AM
Type: Error Category: 0
Event: 6008 Source: EventLog
The previous system shutdown at 1:43:18 AM on ?11/?3/?2012 was unexpected.

Log: 'System' Date/Time: 02/11/2012 8:08:36 PM
Type: Error Category: 0
Event: 10016 Source: Microsoft-Windows-DistributedCOM
The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID {C97FCC79-E628-407D-AE68-A06AD6D8B4D1} and APPID {344ED43D-D086-4961-86A6-1106F4ACAD9B} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC). This security permission can be modified using the Component Services administrative tool.

Log: 'System' Date/Time: 02/11/2012 8:07:28 PM
Type: Error Category: 0
Event: 7000 Source: Service Control Manager
The LogMeIn Kernel Information Provider service failed to start due to the following error: The system cannot find the path specified.

Log: 'System' Date/Time: 02/11/2012 2:46:11 AM
Type: Error Category: 0
Event: 10016 Source: Microsoft-Windows-DistributedCOM
The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID {C97FCC79-E628-407D-AE68-A06AD6D8B4D1} and APPID {344ED43D-D086-4961-86A6-1106F4ACAD9B} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC). This security permission can be modified using the Component Services administrative tool.

Log: 'System' Date/Time: 02/11/2012 2:44:50 AM
Type: Error Category: 0
Event: 7000 Source: Service Control Manager
The LogMeIn Kernel Information Provider service failed to start due to the following error: The system cannot find the path specified.

Log: 'System' Date/Time: 02/11/2012 2:43:29 AM
Type: Error Category: 0
Event: 7034 Source: Service Control Manager
The HP Network Devices Support service terminated unexpectedly. It has done this 1 time(s).

Log: 'System' Date/Time: 30/10/2012 12:49:45 PM
Type: Error Category: 0
Event: 10016 Source: Microsoft-Windows-DistributedCOM
The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID {C97FCC79-E628-407D-AE68-A06AD6D8B4D1} and APPID {344ED43D-D086-4961-86A6-1106F4ACAD9B} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC). This security permission can be modified using the Component Services administrative tool.

Log: 'System' Date/Time: 30/10/2012 12:48:41 PM
Type: Error Category: 0
Event: 7000 Source: Service Control Manager
The LogMeIn Kernel Information Provider service failed to start due to the following error: The system cannot find the path specified.

Log: 'System' Date/Time: 30/10/2012 12:48:23 PM
Type: Error Category: 0
Event: 6008 Source: EventLog
The previous system shutdown at 12:27:35 AM on ?10/?30/?2012 was unexpected.

Log: 'System' Date/Time: 30/10/2012 1:47:07 AM
Type: Error Category: 0
Event: 10016 Source: Microsoft-Windows-DistributedCOM
The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID {C97FCC79-E628-407D-AE68-A06AD6D8B4D1} and APPID {344ED43D-D086-4961-86A6-1106F4ACAD9B} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC). This security permission can be modified using the Component Services administrative tool.

Log: 'System' Date/Time: 30/10/2012 1:46:08 AM
Type: Error Category: 0
Event: 7000 Source: Service Control Manager
The LogMeIn Kernel Information Provider service failed to start due to the following error: The system cannot find the path specified.

Log: 'System' Date/Time: 30/10/2012 1:22:48 AM
Type: Error Category: 0
Event: 10016 Source: Microsoft-Windows-DistributedCOM
The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID {C97FCC79-E628-407D-AE68-A06AD6D8B4D1} and APPID {344ED43D-D086-4961-86A6-1106F4ACAD9B} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC). This security permission can be modified using the Component Services administrative tool.

Log: 'System' Date/Time: 30/10/2012 1:21:41 AM
Type: Error Category: 0
Event: 7000 Source: Service Control Manager
The LogMeIn Kernel Information Provider service failed to start due to the following error: The system cannot find the path specified.

Log: 'System' Date/Time: 30/10/2012 1:14:31 AM
Type: Error Category: 0
Event: 7043 Source: Service Control Manager
The Group Policy Client service did not shut down properly after receiving a preshutdown control.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Warning Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 03/11/2012 5:47:43 PM
Type: Warning Category: 0
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name hamachi-dc.logmein-gateway.com timed out after none of the configured DNS servers responded.

Log: 'System' Date/Time: 03/11/2012 5:47:35 PM
Type: Warning Category: 0
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name www.google.com timed out after none of the configured DNS servers responded.

Log: 'System' Date/Time: 03/11/2012 5:44:40 AM
Type: Warning Category: 0
Event: 4 Source: k57nd60a
Broadcom NetLink ™ Gigabit Ethernet #2: The network link is down. Check to make sure the network cable is properly connected.

Log: 'System' Date/Time: 02/11/2012 10:35:21 PM
Type: Warning Category: 0
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name www.twitterbuttons.com timed out after none of the configured DNS servers responded.

Log: 'System' Date/Time: 02/11/2012 8:07:24 PM
Type: Warning Category: 0
Event: 4 Source: k57nd60a
Broadcom NetLink ™ Gigabit Ethernet #2: The network link is down. Check to make sure the network cable is properly connected.

Log: 'System' Date/Time: 02/11/2012 7:48:11 PM
Type: Warning Category: 0
Event: 4001 Source: Microsoft-Windows-WLAN-AutoConfig
WLAN AutoConfig service has successfully stopped.

Log: 'System' Date/Time: 02/11/2012 7:46:40 PM
Type: Warning Category: 0
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name www.google.com timed out after none of the configured DNS servers responded.

Log: 'System' Date/Time: 02/11/2012 2:44:44 AM
Type: Warning Category: 0
Event: 4 Source: k57nd60a
Broadcom NetLink ™ Gigabit Ethernet #2: The network link is down. Check to make sure the network cable is properly connected.

Log: 'System' Date/Time: 01/11/2012 7:22:00 PM
Type: Warning Category: 0
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name hamachi-dc.logmein-gateway.com timed out after none of the configured DNS servers responded.

Log: 'System' Date/Time: 31/10/2012 7:41:13 PM
Type: Warning Category: 0
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name www.google.com timed out after none of the configured DNS servers responded.

Log: 'System' Date/Time: 31/10/2012 7:41:05 PM
Type: Warning Category: 0
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name www.google.com timed out after none of the configured DNS servers responded.

Log: 'System' Date/Time: 31/10/2012 12:15:32 PM
Type: Warning Category: 0
Event: 4 Source: k57nd60a
Broadcom NetLink ™ Gigabit Ethernet: The network link is down. Check to make sure the network cable is properly connected.

Log: 'System' Date/Time: 30/10/2012 12:48:13 PM
Type: Warning Category: 0
Event: 4 Source: k57nd60a
Broadcom NetLink ™ Gigabit Ethernet #2: The network link is down. Check to make sure the network cable is properly connected.

Log: 'System' Date/Time: 30/10/2012 1:45:43 AM
Type: Warning Category: 0
Event: 4 Source: k57nd60a
Broadcom NetLink ™ Gigabit Ethernet #2: The network link is down. Check to make sure the network cable is properly connected.

Log: 'System' Date/Time: 30/10/2012 1:23:40 AM
Type: Warning Category: 0
Event: 4001 Source: Microsoft-Windows-WLAN-AutoConfig
WLAN AutoConfig service has successfully stopped.

Log: 'System' Date/Time: 30/10/2012 1:21:17 AM
Type: Warning Category: 0
Event: 4 Source: k57nd60a
Broadcom NetLink ™ Gigabit Ethernet #2: The network link is down. Check to make sure the network cable is properly connected.

Log: 'System' Date/Time: 30/10/2012 1:19:11 AM
Type: Warning Category: 0
Event: 4 Source: k57nd60a
Broadcom NetLink ™ Gigabit Ethernet #2: The network link is down. Check to make sure the network cable is properly connected.

Log: 'System' Date/Time: 30/10/2012 1:13:40 AM
Type: Warning Category: 0
Event: 4 Source: k57nd60a
Broadcom NetLink ™ Gigabit Ethernet #2: The network link is down. Check to make sure the network cable is properly connected.

Log: 'System' Date/Time: 30/10/2012 1:03:40 AM
Type: Warning Category: 0
Event: 4101 Source: Display
Display driver nvlddmkm stopped responding and has successfully recovered.

Log: 'System' Date/Time: 29/10/2012 11:13:17 PM
Type: Warning Category: 0
Event: 4 Source: k57nd60a
Broadcom NetLink ™ Gigabit Ethernet #2: The network link is down. Check to make sure the network cable is properly connected.

[emeraldnzl]

Hello Slash12a,

As you know this is really outside my area of expertise but I do see this in this.

The application-specific permission settings do not grant Local Launch permission for the COM Server application

Seems there may be an adjustment to permission settings required.

I have found this link which tells you how to access the Component Services administrative tool.

http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/snap_comp_exp.mspx?mfr=true

Maybe that will be of some help.

[Slash12a]

Interesting. I'm not entirely sure what that is, but it looks like it might be related to the blue screens. After a bit of online research I found a tutorial related to my specific error found here: http://www.itexperie...8-a06ad6d8b4d1/

I added permission for my system from that tutorial. Maybe that'll help things.

[emeraldnzl]

Fingers crossed.

[Slash12a]

New RAM came today, I'll see how it runs. I've also done some research and found out that the nonpaged memory leak might be a conflict with McAfee and Windows that McAfee is apparently ignoring. So if the new RAM doesn't make a change I'll uninstall McAfee and see what happens.