Please help BSOD!!!

Egg · 05 Feb 2011

Hi All,

I built a new pc three weeks ago and am getting random BSODs. I have attached reports as per instructions. I'm running windows 7 home premium 64bit OEM. Here are the parts I got:

CPU-Intel i5 2500
Mobo-ASUS P8P67 Pro
RAM-G.Skill Ripjaws 4GB kit DDR3 1333
SSD-Corsair 60GB
HDD-WD Green 2TB
GPU-Gigabyte 6950
PSU-Antec TP 550W
HSF-CM TX3

Any help would be much appreciated! Let me know if further info required.

Many Thanks,

zigzag3143 · 05 Feb 2011

Egg said:

Hi All,

I built a new pc three weeks ago and am getting random BSODs. I have attached reports as per instructions. I'm running windows 7 home premium 64bit OEM. Here are the parts I got:

CPU-Intel i5 2500
Mobo-ASUS P8P67 Pro
RAM-G.Skill Ripjaws 4GB kit DDR3 1333
SSD-Corsair 60GB
HDD-WD Green 2TB
GPU-Gigabyte 6950
PSU-Antec TP 550W
HSF-CM TX3

Any help would be much appreciated! Let me know if further info required.

Many Thanks,

latest minidump caused by memory corruption of unknown origin. In the interim I would run memtest to verify yours

Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot. Test the sticks individually, and if you find a good one, test it in all slots.

Code:

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


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

Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.20738.amd64fre.win7_ldr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02c06000 PsLoadedModuleList = 0xfffff800`02e3aeb0
Debug session time: Sat Feb  5 03:06:30.554 2011 (GMT-5)
System Uptime: 0 days 0:03:40.475
Loading Kernel Symbols
...............................................................
................................................................
...........................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {8885, fffffa8002171400, fffffa8001b78bd0, 204}

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

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

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

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000008885, The subtype of the bugcheck.
Arg2: fffffa8002171400
Arg3: fffffa8001b78bd0
Arg4: 0000000000000204

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


BUGCHECK_STR:  0x1a_8885

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  WerFault.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002d1da05 to fffff80002c6c580

STACK_TEXT:  
fffff880`09c6c3e8 fffff800`02d1da05 : 00000000`0000001a 00000000`00008885 fffffa80`02171400 fffffa80`01b78bd0 : nt!KeBugCheckEx
fffff880`09c6c3f0 fffff800`02ccab7e : 00000000`00000000 00000000`00000000 00000000`00000004 fffffa80`08bacea0 : nt!MiRelinkStandbyPage+0x115
fffff880`09c6c460 fffff800`02c1dc40 : fffffa80`07acb230 fffffa80`03d8ff10 fffffa80`03d8ff90 fffffa80`03dba6b0 : nt! ?? ::FNODOBFM::`string'+0x907e
fffff880`09c6c490 fffff800`02ecd242 : 00000000`00000000 fffffa80`03dba6f8 fffffa80`03dba6b0 00000000`000007ff : nt!MiUpdatePfnPriorityByPte+0x90
fffff880`09c6c4c0 fffff800`02ecd93c : 00000000`00000000 fffffa80`03dd1b48 00000000`00000006 00000000`00000004 : nt! ?? ::NNGAKEGL::`string'+0x379e5
fffff880`09c6c580 fffff800`030ca16c : 00000000`00000002 00000000`0000002c fffffa80`03dd1820 00000000`0000002c : nt!MmPrefetchPages+0x6c
fffff880`09c6c5e0 fffff800`030ca38d : fffff880`09c6c700 00000000`00000000 00000000`00000000 00000000`00000000 : nt!PfSnPrefetchSections+0x43c
fffff880`09c6c6d0 fffff800`030ca7cf : 00000000`1c48b5a5 fffffa80`03d216a0 fffff8a0`0892f000 00000000`00000000 : nt!PfSnPrefetchScenario+0x16d
fffff880`09c6c940 fffff800`02ec25af : 00000000`00000000 00000000`72d631b9 fffffa80`071f4ef0 00000000`00000000 : nt!PfSnBeginAppLaunch+0x35f
fffff880`09c6ca10 fffff800`02f39c80 : fffffa80`07b01060 fffffa80`071f4ef0 00000000`14050800 00000000`00000000 : nt! ?? ::NNGAKEGL::`string'+0x4d9a0
fffff880`09c6ca40 fffff800`02c49235 : fffff880`009ef180 00000000`00000000 fffff800`02f39b84 fffffa80`07b01060 : nt!PspUserThreadStartup+0xfc
fffff880`09c6caa0 fffff800`02c491b7 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartUserThread+0x16
fffff880`09c6cbe0 00000000`77bb3000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartUserThreadReturn
00000000`0011fdd8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77bb3000


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiRelinkStandbyPage+115
fffff800`02d1da05 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!MiRelinkStandbyPage+115

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c42e3

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x1a_8885_nt!MiRelinkStandbyPage+115

BUCKET_ID:  X64_0x1a_8885_nt!MiRelinkStandbyPage+115

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

Ken J

Egg · 05 Feb 2011

Ok thanks, will give that a try now. I will post results once done.

Egg · 05 Feb 2011

I ran memtest86 v3.5a with both sticks in and get the attached result. (Sorry for the poor image quality.) Seems to be failing test 6. Also I could not exit memtest by pressing Esc. What does this mean???

I will now test separate sticks of ram.

Egg · 05 Feb 2011

Hi I ran memtest and got no errors with one stick in. Ran it for 3 passes.

Now going to test the second stick in the same slot. Does anyone know what the above error mean in the post above when the two sticks were in? Thanks

CarlTR6 · 05 Feb 2011

You have identified a RAM problem. Here is a good tutorial on Memtest: RAM - Test with Memtest86+. Your next step is to remove one stick of RAM leaving one stick in the first slot. Run Memtest on that stick. Then replace it with the second stick and test that stick.

Take a known good stick and test each RAM slot. Post back with your results.

Egg · 05 Feb 2011

hi all thanks for the response so far.

Ran memtest as per instructions above and have received no errors with each single stick of ram. I let it run for seven passes. I also tried multiple slots with no errors. Any ideas why its failing with two sticks in as per post 4?

Could anything else be causing this issue?

Many Thanks.

CarlTR6 · 05 Feb 2011

Here is a list of things that can trigger RAM errors in Memtest: bad RAM stick(s); bad RAM slot on motherboard; RAM not compatible - different brands or two different models of the same brand; RAM incompatible with the motherboard; bad memory controller (motherboard); RAM votages and/or timings set improperly.

At this point I am going to ask a hardware Guru to take a look at this thread. They will want some information; so I will give you a head start. Download and install CPUZ. Please post your CPUZ, Mainboard, Memory, and SPD tabs. This will give everyone the basic info, Mainboard for the motherboard though the revision is usually not listed, Memory tab can indicate wrong OC attempts or wrong settings, confirmed by the SPD tab which is the JEDEC settings for the RAM. JEDEC is the industry standard that the RAM manufactures use to get stable settings for default.

We will also need the voltage settings for the CPU, RAM and NB or equivalent.
NB or memory controller is important. CPU voltage is listed on the CPU tab, RAM voltage is listed but it's not the actual voltage; it's the recommended voltage.

Egg · 05 Feb 2011

Ok CPUZ images attached, also put a HW monitor image in there too. Let me know if further info needed.

Thanks.

Egg · 06 Feb 2011

Also have attached the latest minidmp files. Thanks.