BSOD on startup or browsing the internet (Chrome)

[unicornz]

please help me out here. been happening at least once a day.

You can just focus on dmp file dated in 2014.

thx.

 

[koolkat77]

Welcome to the forum.

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


Loading Dump File [C:\Users\USER\Downloads\Compressed\MARK-PC-29_12_2014_203614_69\122814-7690-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.18526.amd64fre.win7sp1_gdr.140706-1506
Machine Name:
Kernel base = 0xfffff800`03251000 PsLoadedModuleList = 0xfffff800`03494890
Debug session time: Mon Dec 29 12:15:32.000 2014 (UTC + 6:00)
System Uptime: 0 days 0:06:42.906
Loading Kernel Symbols
...............................................................
................................................................
..................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff6c1001fa088, 0, fffff800033ef3b6, 5}


Could not read faulting driver name
Probably caused by : memory_corruption ( nt!MiGetWorkingSetInfo+286 )

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

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff6c1001fa088, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff800033ef3b6, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 0000000000000005, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800034fe100
GetUlongFromAddress: unable to read from fffff800034fe1c0
 fffff6c1001fa088 Nonpaged pool

FAULTING_IP: 
nt!MiGetWorkingSetInfo+286
fffff800`033ef3b6 488b0408        mov     rax,qword ptr [rax+rcx]

MM_INTERNAL_CODE:  5

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  chrome.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff8800828c8a0 -- (.trap 0xfffff8800828c8a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000041001fa088 rbx=0000000000000000 rcx=fffff68000000000
rdx=0000000016c37004 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800033ef3b6 rsp=fffff8800828ca30 rbp=fffff8800828cca0
 r8=fffff8800b75b058  r9=fffff7000108c048 r10=fffffa8004b17b50
r11=fffff7000108c3d0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
nt!MiGetWorkingSetInfo+0x286:
fffff800`033ef3b6 488b0408        mov     rax,qword ptr [rax+rcx] ds:fffff6c1`001fa088=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800033435b3 to fffff800032c6bc0

STACK_TEXT:  
fffff880`0828c738 fffff800`033435b3 : 00000000`00000050 fffff6c1`001fa088 00000000`00000000 fffff880`0828c8a0 : nt!KeBugCheckEx
fffff880`0828c740 fffff800`032c4cee : 00000000`00000000 fffff6c1`001fa088 00000000`00000000 fffffa80`098533c0 : nt! ?? ::FNODOBFM::`string'+0x43801
fffff880`0828c8a0 fffff800`033ef3b6 : fffff880`0828cca0 00000000`00000000 00000000`00000068 fffff880`00000000 : nt!KiPageFault+0x16e
fffff880`0828ca30 fffff800`03626a25 : 00000000`fffeffff 00000000`c0000001 fffffa80`098533c0 fffffa80`00000001 : nt!MiGetWorkingSetInfo+0x286
fffff880`0828cac0 fffff800`032c5e53 : 00000000`00001a9c fffffa80`098533c0 00000000`0605dd30 00000000`0605e108 : nt! ?? ::NNGAKEGL::`string'+0x4c5f3
fffff880`0828cbb0 00000000`76d814ea : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0605e0e8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76d814ea


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiGetWorkingSetInfo+286
fffff800`033ef3b6 488b0408        mov     rax,qword ptr [rax+rcx]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!MiGetWorkingSetInfo+286

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  53b9f073

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x50_nt!MiGetWorkingSetInfo+286

BUCKET_ID:  X64_0x50_nt!MiGetWorkingSetInfo+286

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

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


Loading Dump File [C:\Users\USER\Downloads\Compressed\MARK-PC-29_12_2014_203614_69\122814-7722-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.18526.amd64fre.win7sp1_gdr.140706-1506
Machine Name:
Kernel base = 0xfffff800`0320c000 PsLoadedModuleList = 0xfffff800`0344f890
Debug session time: Mon Dec 29 12:08:07.705 2014 (UTC + 6:00)
System Uptime: 0 days 0:00:19.000
Loading Kernel Symbols
...............................................................
................................................................
...............................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {31, fffffa8008c76620, fffff880046cb000, fffff8a00332934e}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::NNGAKEGL::`string'+71b1 )

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

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

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000000031, The subtype of the bugcheck.
Arg2: fffffa8008c76620
Arg3: fffff880046cb000
Arg4: fffff8a00332934e

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


BUGCHECK_STR:  0x1a_31

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  MOM.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff800034e0515 to fffff80003281bc0

STACK_TEXT:  
fffff880`068d1888 fffff800`034e0515 : 00000000`0000001a 00000000`00000031 fffffa80`08c76620 fffff880`046cb000 : nt!KeBugCheckEx
fffff880`068d1890 fffff800`03559187 : 00000000`00000000 fffffa80`08d71b50 00000000`00000185 fffff8a0`0331c000 : nt! ?? ::NNGAKEGL::`string'+0x71b1
fffff880`068d18f0 fffff800`032b095b : ffffffff`ffffffff fffff880`068d1a78 00000000`00004000 fffffa80`08b84a00 : nt!MiRelocateImagePfn+0xf7
fffff880`068d1950 fffff800`032a891f : fffffa80`086e2cc0 fffff880`068d1a80 fffffa80`08d843f8 fffff800`0324c80a : nt!MiWaitForInPageComplete+0x7ef
fffff880`068d1a30 fffff800`0328f28a : 00000000`00000000 00000000`00000000 ffffffff`ffffffff fffff900`00000000 : nt!MiIssueHardFault+0x28b
fffff880`068d1ac0 fffff800`0327fcee : 00000000`00000000 000007fe`f18d5520 00000000`024d6301 000007fe`f17511b8 : nt!MmAccessFault+0x146a
fffff880`068d1c20 000007fe`f520c1ee : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
00000000`0030cff0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x000007fe`f520c1ee


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::NNGAKEGL::`string'+71b1
fffff800`034e0515 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::NNGAKEGL::`string'+71b1

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  53b9f073

FAILURE_BUCKET_ID:  X64_0x1a_31_nt!_??_::NNGAKEGL::_string_+71b1

BUCKET_ID:  X64_0x1a_31_nt!_??_::NNGAKEGL::_string_+71b1

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

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

Memtest should be done overnight.

 

[unicornz]

thx, i will do it tonight and nights after.