1st BSOD on Lenovo :( while on internet Chrome

Start by taking memtest,

Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.

• RAM - Test with Memtest86+

The goal is to test all the RAM sticks and all the motherboard slots.

Check your motherboard manual to ensure the RAM sticks are in the recommended motherboard slots. Some motherboards have very specific slots required for the number of RAM sticks installed.

If you get errors, stop the test and continue with the next step.

1. Remove all but one stick of RAM from your computer (this will be RAM stick #1), and run Memtest86 again, for 7 passes.

*Be sure to note the RAM stick, use a piece of tape with a number, and note the motherboard slot.

If this stick passes the test then go to step #3.

2. If RAM stick #1 has errors, repeat the test with RAM stick #2 in the same motherboard slot.

*If RAM stick #2 passes, this indicates that RAM stick #1 may be bad. If you want to be absolutely sure, re-test RAM stick #1 in another known good slot.

*If RAM stick #2 has errors, this indicates another possible bad RAM stick, a possible motherboard slot failure or inadequate settings.

3. Test the next stick of RAM (stick #2) in the next motherboard slot.

*If this RAM stick has errors repeat step #2 using a known good stick if possible, or another stick.

*If this RAM stick has no errors and both sticks failed in slot#1, test RAM stick #1 in this slot.

4. If you find a stick that passes the test, test it in all the other motherboard slots.

If Part 2 testing shows errors, and all tests in Part 3 show errors, you will need to test the RAM sticks in another computer and/or test other RAM in your computer to identify the problem.

In this way, you can identify whether it is a bad stick of RAM, a bad motherboard, or incompatibility between the sticks.

   Information

Errors are sometimes found after 8 passes.

   Tip

Do this test overnight, before going to bed.

Code:

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


Loading Dump File [C:\Users\admin\Downloads\MUSICMAKER-Sat_06_07_2014_130900_35\060714-32105-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
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.17835.amd64fre.win7sp1_gdr.120503-2030
Machine Name:
Kernel base = 0xfffff800`0300c000 PsLoadedModuleList = 0xfffff800`03250670
Debug session time: Sat Jun  7 23:55:41.400 2014 (UTC + 6:00)
System Uptime: 6 days 0:54:34.552
Loading Kernel Symbols
...............................................................
................................................................
..............................................
Loading User Symbols
Loading unloaded module list
......................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41201, fffff68000094008, 7bf7483862e484f3, fffffa800dfaf010}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+13c82 )

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

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

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041201, The subtype of the bugcheck.
Arg2: fffff68000094008
Arg3: 7bf7483862e484f3
Arg4: fffffa800dfaf010

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


BUGCHECK_STR:  0x1a_41201

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  chrome.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff800030e6cfe to fffff8000308b1c0

STACK_TEXT:  
fffff880`0a5ee878 fffff800`030e6cfe : 00000000`0000001a 00000000`00041201 fffff680`00094008 7bf74838`62e484f3 : nt!KeBugCheckEx
fffff880`0a5ee880 fffff800`030560b1 : ffffe555`746c6644 fffff880`00961000 00000000`00000000 7bf74838`62e484f3 : nt! ?? ::FNODOBFM::`string'+0x13c82
fffff880`0a5ee8c0 fffff800`03055d4a : fffffa80`0dfaf010 fffffa80`06dcb060 fffffa80`06dcb060 00000000`12801000 : nt!MiQueryAddressState+0x2b1
fffff880`0a5ee910 fffff800`03361314 : 00000000`00000000 00000000`12802000 fffffa80`0dfaf010 fffff680`00000000 : nt!MiQueryAddressSpan+0xaa
fffff880`0a5ee980 fffff800`0308a453 : ffffffff`ffffffff fffffa80`06fb6310 00000000`110cf008 00000000`0391e378 : nt!NtQueryVirtualMemory+0x382
fffff880`0a5eea70 00000000`76fd154a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0391e358 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76fd154a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+13c82
fffff800`030e6cfe cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+13c82

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4fa390f3

FAILURE_BUCKET_ID:  X64_0x1a_41201_nt!_??_::FNODOBFM::_string_+13c82

BUCKET_ID:  X64_0x1a_41201_nt!_??_::FNODOBFM::_string_+13c82

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

DJNRC said:

Thank you for taking the time to help me out. Looks like the RAM or motherboard huh? That sucks... it may be a week before I can take the time to run the tests. I'll report back though. Thanks

No problem. Take your time.