Replaced CPU/PSU still get BSODs

Here's my latest batch of minidumps. Any ideas?

Hey.

Well, to start with, you have a 0x1A error which is described as
"Internal memory management structures are corrupted. To further investigate the cause, a kernel memory dump file is needed."

Another is a 0x24 error.

Wait, let me stop here for a moment. You have all different assorted varieties of errors.

So what we are going to do is the following. Open an elevated command prompt and run this command for each partition you have, changing C each time for the partition:

chkdsk /r C:

Then completely uninstall any antivirus and firewall applications.

Then, open another elevated command prompt and run this in it:

sfc /scannow

These drivers are old and should be Googled and updated to newest possible:

fet6x64 fet6x64.sys Thu Jun 19 07:40:18 2008
speedfan speedfan.sys Sun Sep 24 09:26:48 2006


I'd also check that the Vdimm (Ram voltage) and timings and set correctly for the modules you're using. You can visit the manufacturer's page of the RAM and find the specific model. Then adjust your bios accordingly.

Then run Memtest overnight to see if any errors are shown.



-------------------------

After you've done these things, please post any new bsod dumps and we can look at them to see what else we can do.

MY 2 cts worth memtest download Memtest86+ - Advanced Memory Diagnostic Tool and information on running it. Fabe Memory Diagnostics

torrentg said:

I'd also check that the Vdimm (Ram voltage) and timings and set correctly for the modules you're using. You can visit the manufacturer's page of the RAM and find the specific model. Then adjust your bios accordingly.

Ok so my ram timings are 5-5-5-15-2T and voltage is supposed to be 2.1. The BIOS on my motherboard allows me to set the 5-5-5-15 (which it actually defaults at) but it defaults the voltage at 1.8. It will not let me change the 2T (there's not even a setting for it) and there's also a bunch of additional settings for RAM timings that I can't get information on.

Also, I don't even know what fet6x64.sys is, or how to update or remove it. I just got rid of speedfan, I don't need it anyway. Did the command prompts and nothing came up as bad.

Try these settings.
Use the yellow slots on your board if running two sticks.

REF cycle time from 40 to 60 depending on frequency used.
NB voltage 1.26V "very important"
Memory voltage 2.1
DRAM OC Charger enabled
DRAM Training enabled
DRAM Static read enabled
Ai clock twister light

Also take your Dram timing control off Auto so that you can adjust timings 5 5 5 15 2T. You won't get anywhere using the 1T setting.

AI overclock tuner switch from Auto to Manual. "Settings won't stick unless you do this."

You have to adjust these settings manually or there is no way your board will run stable. :)

Let me know if these settings work.

mpohutsk said:

Here's my latest batch of minidumps. Any ideas?

Hi and welcome

You dmps fall in 2 categories. First MEMORY, second system files. The memory may be causing the system files to fail

I would
download and run memtestx86 and run it overnight.
I would also run a system file check by typing cmd in search>right click and run as admin> SFC /SCANNOW

Let us know the results

If you are overclocking stop
If you have a raid update the driver

Ken J++


Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\111809-17862-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*d:\symbols*Symbol information
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02c56000 PsLoadedModuleList = 0xfffff800`02e93e50
Debug session time: Wed Nov 18 22:15:26.471 2009 (GMT-5)
System Uptime: 0 days 1:51:11.048
Loading Kernel Symbols
...............................................................
................................................................
.........................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {28, 2, 0, fffff80002d0a090}

Probably caused by : memory_corruption ( nt!MiFindNodeOrParent+0 )

Followup: MachineOwner

Hope this helps

Ken J++
---------

chev65 said:

Try these settings.
Use the yellow slots on your board if running two sticks.

REF cycle time from 40 to 60 depending on frequency used.
NB voltage 1.26V "very important"
Memory voltage 2.1
DRAM OC Charger enabled
DRAM Training enabled
DRAM Static read enabled
Ai clock twister light

Also take your Dram timing control off Auto so that you can adjust timings 5 5 5 15 2T. You won't get anywhere using the 1T setting.

AI overclock tuner switch from Auto to Manual. "Settings won't stick unless you do this."

You have to adjust these settings manually or there is no way your board will run stable. :)

Let me know if these settings work.

Ok these settings seemed to have stabilized the system. If I get another BSOD I'll post the minidump.

Blah. Spoke too soon. Here's the newest one. By the way, I ran Memtest86+ after I changed the RAM settings and it made 3 passes no problems.

mpohutsk said:

Blah. Spoke too soon. Here's the newest one. By the way, I ran Memtest86+ after I changed the RAM settings and it made 3 passes no problems.

Unfortunately, even a clear run overnight is not indicative of perfect memory. The longer you run it, the more conclusive it is, however. It is still technically possible for RAM to be defective with clear passes indefinitely, too.

On the fortunate side of things, the bsod looks to be from a faulty driver trying to write to a read only part of memory.

If you know what this process is, update it: "BackgroundDown" (Or could be a virus - scan with multiple scanners.)

These are the older drivers you have so I'd try to get these updated and see how it goes:

ASACPI ASACPI.sys Sun Mar 27 22:30:36 2005
ctac32k ctac32k.sys Wed Jul 02 04:38:22 2008
fet6x64 fet6x64.sys Thu Jun 19 07:40:18 2008
Rt64win7 Rt64win7.sys Thu Feb 26 04:04:13 2009

You could possibly look at these too:

amdxata amdxata.sys Tue May 19 13:56:59 2009
spldr spldr.sys Mon May 11 12:56:27 2009
ctsfm2k ctsfm2k.sys Wed Jun 03 13:57:30 2009
ctoss2k ctoss2k.sys Wed Jun 03 13:57:43 2009
ctprxy2k ctprxy2k.sys Wed Jun 03 13:59:48 2009
ha20x2k ha20x2k.sys Wed Jun 03 13:59:09 2009
emupia2k emupia2k.sys Wed Jun 03 13:57:22 2009
CT20XUT CT20XUT.SYS Wed Jun 03 14:01:05 2009
CTHWIUT CTHWIUT.SYS Wed Jun 03 14:01:09 2009
CTEXFIFX CTEXFIFX.SYS Wed Jun 03 14:01:00 2009