BSOD playing BF3 error 0x0000001a

Hey there. I don't think I'm using the wrong ram. I know several people that use an AMD motherboard with corsair vengeance. I'm obviously not an expert or anything lol. I've also used a different set but same specs of the vengeance that was working great for about a year.

I guess there isn't a definitive answer to what is causing the bluescreens? Last night I played BF3 for a few hours no problem. Some days I can run it for hours on end, and others it will just keep crashing my computer. sigh.

It may work with AMD. I do not see anything on the site advertising that it does; that is all I was saying. Sometimes RAM that does not include AMD information will not work with AMD processors, and other times it just needs some adjustments.

Your timings look good. Try manually setting the DRAM Command Rate to 2T and see if that helps.

Hi there, just a quick update. After changing my the DRAM timing I have yet to have another BSOD. But every time I think the problem is fixed it happens again lol. Hopefully this time will prove me wrong Thank you again for your help and I will keep you posted.

Even if it does not resolve it completely, at least that indicates we are on the right track.

Best wishes it is solved now!

HA! spoke too soon well this time the crash occurred while I was on the internet getting ready to load bf3. Here's the dump file and thank you.

Alright, try running with one stick of RAM at a time and see if it provides more stability. Avoid Static Damage to Your PC when swapping out RAM modules.

Run one stick at a time in each slot; try to find a good module and a good slot. Then test the other module in the good slot to see if the module is good. Test a known good module in all slots to determine if any of the slots are bad.

Code:

Loading Dump File [D:\Kingston\BSODDmpFiles\JCL III\Windows_NT6_BSOD_jcgriff2 (2)\Windows_NT6_BSOD_jcgriff2\032512-21278-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`0305b000 PsLoadedModuleList = 0xfffff800`0329f650
Debug session time: Sun Mar 25 01:03:28.445 2012 (UTC - 6:00)
System Uptime: 1 days 10:33:12.631
Loading Kernel Symbols
...............................................................
................................................................
....................
Loading User Symbols
Loading unloaded module list
...................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {8885, fffffa8005880d50, fffffa800587f6a0, 605}

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

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

1: 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: fffffa8005880d50
Arg3: fffffa800587f6a0
Arg4: 0000000000000605

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


BUGCHECK_STR:  0x1a_8885

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff8000317e9a5 to fffff800030d7d40

STACK_TEXT:  
fffff880`06a1b8b8 fffff800`0317e9a5 : 00000000`0000001a 00000000`00008885 fffffa80`05880d50 fffffa80`0587f6a0 : nt!KeBugCheckEx
fffff880`06a1b8c0 fffff800`031dee15 : fffffa80`0726e060 fffffa80`06aac000 00000000`00000000 00000000`00000020 : nt!MiRelinkStandbyPage+0x115
fffff880`06a1b930 fffff800`034e7924 : fffffa80`0726d000 fffff880`06a1bca0 fffff880`06a1ba08 00000000`0140b701 : nt!MmSetPfnListPriorities+0x175
fffff880`06a1b980 fffff800`035493da : 00000000`00000020 00000000`00000000 fffffa80`0726d000 00000000`00000001 : nt!PfpPfnPrioRequest+0x84
fffff880`06a1b9d0 fffff800`0354dc1a : 00000000`00000000 00000000`0000004f 00000000`00000000 fffffa80`06aaa001 : nt!PfSetSuperfetchInformation+0x199
fffff880`06a1bab0 fffff800`030d6fd3 : fffffa80`09bc3060 00000000`025e2da0 00000000`025e2da0 00000000`0140cb48 : nt!NtSetSystemInformation+0xc8d
fffff880`06a1bc20 00000000`77942a0a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0140b648 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77942a0a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiRelinkStandbyPage+115
fffff800`0317e9a5 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!MiRelinkStandbyPage+115

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4ec79dd2

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x1a_8885_nt!MiRelinkStandbyPage+115

BUCKET_ID:  X64_0x1a_8885_nt!MiRelinkStandbyPage+115

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

Crashes all point to memory as the culprit...


Yes, run your system normally with one stick of RAM. Hardware failures can be finicky if they are not outright failures. The fact that your crashes do not occur regularly means you may have this type of failure. We need to try to narrow down the root cause, and RAM is one of the most common components to go due to its delicate nature. That is why I included that link to the article about avoiding static damage to the PC.

So I tried running with 1 stick of ram in the first slot, but it crashed when the game loaded up. Then i moved that same stick of ram into the 2nd slot and the game was running slower but no crash. I think the first slot on my motherboard was messed up.

Even though memtest and windows mem diag didn't pick up any errors with the ram, is it possible that the ram slot on my motherboard went bad? And how do the mobo slots randomly go bad lol?

Last night I was running bf3 with the ram sticks in slots 2 and 3 instead of 1 and 2, and there weren't any crashes. SOOOO... fingers crossed, I hope this is the permanent fix and not just a run of good luck before the string of next crashes . Will keep you updated and thank you!

JCL III said:

Even though memtest and windows mem diag didn't pick up any errors with the ram, is it possible that the ram slot on my motherboard went bad? And how do the mobo slots randomly go bad lol?

You're welcome for the help.

To answer your question quoted above, I provide you with further reading (I linked this earlier, but I am not sure if you read it): Avoid Static Damage to Your PC | PCWorld