BSOD/Random Shut Downs - New Build

[Triopas]

Two days ago I completed the build of my new pc. At first, it was running fine, but then i started getting a number of different BSOD errors, as well as random shut downs. So far it has only been on the mornings when I have had this problem. After restarting many times yesterday morning (for around 2 hours) the problem finally disappeared and the pc worked fine until 11pm. Then again, this morning the pc is repeatedly showing BSOD. System specs are:

OS - x64 Windows 7 Home Premium - Full retail
Motherboard - MSI MS-7640 GD-65
Processor - AMD Phenom II X6
Memory - Corsair XMS3 DDR3 2x4gb 1600MHz CMX8GX3M2A1600C9 (Taken one stick out currently)
Graphics Card - Sapphire HD5850 Extreme 1gb

I have included the zipped files.

Any help is appreciated

 

[Maguscreed]

Right off the bat the errors look kind of random, there is only one consistent thing though, pretty much every other crash is the direct result of a memory problem.

The only thing I can suggest to test this is running memtest86 overnight (5 to 7 passes) to check your ram.
It's not a 100% test method but it works better than the windows memtest util.
http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

I guess it goes without saying that if you have any custom timings or overclocks going on, to remove them at this time as well.

Probably caused by : memory_corruption ( nt!MiRelinkStandbyPage+c6 )

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

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

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000008884, The subtype of the bugcheck.
Arg2: fffffa800371bc80
Arg3: fffffa8003625cb0
Arg4: 0000000000000504

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


BUGCHECK_STR:  0x1a_8884

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002f72d46 to fffff80002ec4700

STACK_TEXT:  
fffff880`045fa8b8 fffff800`02f72d46 : 00000000`0000001a 00000000`00008884 fffffa80`0371bc80 fffffa80`03625cb0 : nt!KeBugCheckEx
fffff880`045fa8c0 fffff800`02fd1575 : fffffa80`03d5a408 fffffa80`03d57000 00000000`00000000 00000000`00000000 : nt!MiRelinkStandbyPage+0xc6
fffff880`045fa930 fffff800`032d6b44 : fffffa80`03d59000 fffff880`045faca0 fffff880`045faa08 00000000`00140001 : nt!MmSetPfnListPriorities+0x175
fffff880`045fa980 fffff800`0333786a : 00000000`00000020 00000000`00000000 fffffa80`03d59000 00000000`00000001 : nt!PfpPfnPrioRequest+0x84
fffff880`045fa9d0 fffff800`0333bfae : 00000000`00000000 00000000`0160b830 00000000`0000004f 00000000`07ab4f01 : nt!PfSetSuperfetchInformation+0x199
fffff880`045faab0 fffff800`02ec3953 : fffffa80`061f3b60 00000000`02d67800 00000000`02cbb5d0 00000000`002ca0b6 : nt!NtSetSystemInformation+0xb91
fffff880`045fac20 00000000`77af0daa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0160b7b8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77af0daa


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiRelinkStandbyPage+c6
fffff800`02f72d46 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!MiRelinkStandbyPage+c6

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4d9fdd34

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x1a_8884_nt!MiRelinkStandbyPage+c6

BUCKET_ID:  X64_0x1a_8884_nt!MiRelinkStandbyPage+c6

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

 

[Triopas]

Thanks for the fast reply I will have to contact my friend and see if he can make the memtest disk for me, since I dont have the facilities

 

[Maguscreed]

Okay meanwhile you can clear out the minidump folder so that any new ones will be easier for you to find and upload in the meantime.
(just the files inside, not the actual folder)

 

[Triopas]

So, is there any particular reason why the memory would be giving me these BSOD's? such as wrong installation etc?

 

[Maguscreed]

If a memory stick is bad, pretty much anything can fail because of it resulting in a bsod. If the computer checks the ram for something and receives corrupt data ... you crash basically.
The actual driver/cause may vary too.
Anyhow, it's the best first step I have.
If you are just dying to do something right now it never hurts to run a secure file check on your windows installation, I would still work on getting a memtest disc made though.
http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

 

[Triopas]

Okay the memtest has been running for 1 hour and so far there are 4million errors, what does it mean?

Edit - "Unexpected Interrupt - Halting CPU0" - Just got that with 5.7million errors

Edit2 - Running with 1 stick of RAM now and in the Test #7 [Block move] there are lots of errors.

 

[Maguscreed]

I don't think I have ever seen a failure rate that bad.
Let's try running memtest on each stick individually (pull one stick test/replace with other)
hopefully you'll only need to rma one.

You can also try testing both memory slots on the motherboard. It's possible one of them is the problem as well.

 

[Triopas]

Ok it appears that all of the errors arise in the Block move section, which happens when the single ram is used in each socket.

 

[Maguscreed]

Do you have another computer you can test that ram in around?
It's about 50/50 whether it's the ram or the motherboard at this point.

 

[Triopas]

I have just taken 1 stick of RAM to my friends house and tried it in his computer, the pc starts up and everything, but nothing is displayed. Just thinking its strange that mine boots with the RAM but his doesnt. Is this inconclusive?

Edit: Now when I have put the RAM back into my computer, everything lights up and the fans are going, but nothing is shown on the screen. (FIXED)

 

[Maguscreed]

No I think it would be pretty safe to say it's a problem.
I would go ahead and start the RMA process on it.
The fact that you are even able to post with ram that gets that many errors in such a short time is kind of amazing to begin with. I will grant you that.

 

[Triopas]

Could RAM actually result in no display?

And I have just checked for RAM compatibility with my motherboard and its not on the list, does this mean there's a guaranteed non incompatibility and could this have been the source of the problems?

Motherboard - "Supports four unbuffered DIMM of 1.5 Volt DDR3 800/1066/1333/1600/1866*/2133* (OC) DRAM, 32GB Max"

RAM - "DDR3-1600 (XMS3-9-9-9-24*1.65v) Dual Channel"

 

[Maguscreed]

Well see that's the thing though.
When we ran memtest86 we were completely outside of windows. Windows wasn't even involved, and it was spitting out errors like mad.


Something is going on with either
a - the ram
or
b - the motherboard

We have identified this as a hardware related issue though which means there's not a whole lot I can do to solve it for you at this point.
You'll just need to continue troubleshooting until you are sure.
It sounds to me like one of the ram sticks is bad, or it's also possible it's a compatiblity issue there.
Either way spitting out that kind of error rate in memtest is a clear indication that the problem is either ram or motherboard.
Personally I'd be hoping it's the ram. Motherboard rma's are a nightmare and you'll have no computer at all while it's out.

 

[Triopas]

Is there anything else I can do to know for definite what's wrong before I start RMA?

 

[Maguscreed]

Well when you contact their customer support tell them the results of the tests I had you run here.
I would contact motherboard and memory manufacturer both.
Especially for troubleshooting the motherboard they may have tests to run I don't know about.