BSOD while gaming, browsing the internet, etc. multiple causes?

noll11 · 09 Oct 2014

hi all, for the past while, my PC has been BSOD-ing intermittently, mostly while gaming, but sometimes while just browsing the internet.

any solutions would be awesome!

DM log collector file included.

noll11 · 11 Oct 2014

any assistance would be greatly appreciated.

noll11 · 15 Oct 2014

bump.

noll11 · 02 Nov 2014

Still looking for help with this.

koolkat77 · 02 Nov 2014

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\OLIVERBARBER-PC-Thu_10_09_2014_202835_01\100914-29140-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.18409.amd64fre.win7sp1_gdr.140303-2144
Machine Name:
Kernel base = 0xfffff800`02e08000 PsLoadedModuleList = 0xfffff800`0304b890
Debug session time: Fri Oct 10 02:39:25.041 2014 (UTC + 6:00)
System Uptime: 0 days 2:01:54.070
Loading Kernel Symbols
...............................................................
................................................................
.....................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff80002f2ed47, fffff88006584c90, 0}

Probably caused by : memory_corruption ( nt!MiIdentifyPfn+317 )

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

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

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80002f2ed47, Address of the instruction which caused the bugcheck
Arg3: fffff88006584c90, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
nt!MiIdentifyPfn+317
fffff800`02f2ed47 488b4118        mov     rax,qword ptr [rcx+18h]

CONTEXT:  fffff88006584c90 -- (.cxr 0xfffff88006584c90)
rax=0000000000000001 rbx=0200000000051f87 rcx=00fffa8003dd2dd0
rdx=0000000000014c61 rsi=0000000000000000 rdi=fffffa8007378720
rip=fffff80002f2ed47 rsp=fffff88006585670 rbp=fffffa800397c8e8
 r8=000000000001503b  r9=0000000000000001 r10=0000000000000042
r11=0000058000000000 r12=0000000000000000 r13=0000000000000000
r14=fffffa800397c830 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
nt!MiIdentifyPfn+0x317:
fffff800`02f2ed47 488b4118        mov     rax,qword ptr [rcx+18h] ds:002b:00fffa80`03dd2de8=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff80002f2ed47

STACK_TEXT:  
fffff880`06585670 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiIdentifyPfn+0x317


FOLLOWUP_IP: 
nt!MiIdentifyPfn+317
fffff800`02f2ed47 488b4118        mov     rax,qword ptr [rcx+18h]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!MiIdentifyPfn+317

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  531590fb

STACK_COMMAND:  .cxr 0xfffff88006584c90 ; kb

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x3B_nt!MiIdentifyPfn+317

BUCKET_ID:  X64_0x3B_nt!MiIdentifyPfn+317

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

Start by testing RAM.

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.