BSOD G73JH ntoskrnl.exe (nt+0x75BC0) BCC: 0x3B (0xC0000005,

Code:

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


Loading Dump File [C:\Users\YUSRA\Downloads\Compressed\ASUSTEK-Fri_02_06_2015_123020_07\020615-262253-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
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 (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Machine Name:
Kernel base = 0xfffff800`0325d000 PsLoadedModuleList = 0xfffff800`034a06d0
Debug session time: Fri Feb  6 23:20:24.720 2015 (UTC + 6:00)
System Uptime: 1 days 2:26:06.546
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

..............................................................
................................................................
................................................
Loading User Symbols
Loading unloaded module list
....................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff80003383c9f, fffff88004b4bc90, 0}

Probably caused by : memory_corruption ( nt!MiIdentifyPfn+26f )

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

1: 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: fffff80003383c9f, Address of the instruction which caused the bugcheck
Arg3: fffff88004b4bc90, 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+26f
fffff800`03383c9f f0410fba6e481f  lock bts dword ptr [r14+48h],1Fh

CONTEXT:  fffff88004b4bc90 -- (.cxr 0xfffff88004b4bc90;r)
rax=0000000000000001 rbx=02000000002d7f44 rcx=0400000000000020
rdx=000000000043c609 rsi=0000000000000000 rdi=fffffa8025b73ec8
rip=fffff80003383c9f rsp=fffff88004b4c670 rbp=fffffa8019e64910
 r8=000000000032890a  r9=0000000000000001 r10=0000000000000042
r11=0000058000000000 r12=fffff880009e9180 r13=0000000000000000
r14=61436d4d02100010 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010206
nt!MiIdentifyPfn+0x26f:
fffff800`03383c9f f0410fba6e481f  lock bts dword ptr [r14+48h],1Fh ds:002b:61436d4d`02100058=????????
Last set context:
rax=0000000000000001 rbx=02000000002d7f44 rcx=0400000000000020
rdx=000000000043c609 rsi=0000000000000000 rdi=fffffa8025b73ec8
rip=fffff80003383c9f rsp=fffff88004b4c670 rbp=fffffa8019e64910
 r8=000000000032890a  r9=0000000000000001 r10=0000000000000042
r11=0000058000000000 r12=fffff880009e9180 r13=0000000000000000
r14=61436d4d02100010 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010206
nt!MiIdentifyPfn+0x26f:
fffff800`03383c9f f0410fba6e481f  lock bts dword ptr [r14+48h],1Fh ds:002b:61436d4d`02100058=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  2

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) x86fre

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff80003383c9f

STACK_TEXT:  
fffff880`04b4c670 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiIdentifyPfn+0x26f


FOLLOWUP_IP: 
nt!MiIdentifyPfn+26f
fffff800`03383c9f f0410fba6e481f  lock bts dword ptr [r14+48h],1Fh

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!MiIdentifyPfn+26f

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  521ea035

IMAGE_VERSION:  6.1.7601.18247

STACK_COMMAND:  .cxr 0xfffff88004b4bc90 ; kb

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x3B_nt!MiIdentifyPfn+26f

BUCKET_ID:  X64_0x3B_nt!MiIdentifyPfn+26f

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x3b_nt!miidentifypfn+26f

FAILURE_ID_HASH:  {6585161c-ff2c-04cd-9eeb-d11732376406}

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.