Sign in with
Sign up | Sign in
Your question

Blue Screen Of Death - Memory.DMP analysis inside

Tags:
Last response: in Windows 7
Share
May 5, 2014 12:20:38 PM

As per the title, my new build (about a month old now) has been crashing when i shutdown and once just now whilst i was using firefox.

Build:
120gb Samsung SSD - Windows is installed on this
i5-4670k - not overclocked
Artic Cooling Freezer 13 cpu cooler with mx-4 thermal paste (Same problem occured on stock cooler+paste)
8gb Hyper X Beast Kingston RAM (Same problem with different ram , so its definitely not this)
Gigabyte Z87 HD3
1TB Western Digital - Blue Hardrive
600w Corsair Bronze rated power supply
Samsung optical drive
These are the specs I can remember off the top of my head,if you need more detailed information let me know.


Here's the log from MEMORY.DMP using the windows debug software:
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80002ef7e5f, Address of the instruction which caused the bugcheck
Arg3: fffff88009aacbc0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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

Page 1f7303 not present in the dump file. Type ".hh dbgerr004" for details

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

FAULTING_IP:
nt!MiCheckControlArea+17f
fffff800`02ef7e5f 49395d50 cmp qword ptr [r13+50h],rbx

CONTEXT: fffff88009aacbc0 -- (.cxr 0xfffff88009aacbc0;r)
rax=fffffa8008c5473d rbx=0000000000000000 rcx=0000000000004080
rdx=0000000000000000 rsi=fffffa8006df23b0 rdi=0000000000000000
rip=fffff80002ef7e5f rsp=fffff88009aad5a0 rbp=0000000000000000
r8=0000000fffffffff r9=0000000000000012 r10=0000000000000000
r11=0000000000000000 r12=0000000000000000 r13=0100000000000000
r14=000000000000fffe 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!MiCheckControlArea+0x17f:
fffff800`02ef7e5f 49395d50 cmp qword ptr [r13+50h],rbx ds:002b:01000000`00000050=????????????????
Last set context:
rax=fffffa8008c5473d rbx=0000000000000000 rcx=0000000000004080
rdx=0000000000000000 rsi=fffffa8006df23b0 rdi=0000000000000000
rip=fffff80002ef7e5f rsp=fffff88009aad5a0 rbp=0000000000000000
r8=0000000fffffffff r9=0000000000000012 r10=0000000000000000
r11=0000000000000000 r12=0000000000000000 r13=0100000000000000
r14=000000000000fffe 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!MiCheckControlArea+0x17f:
fffff800`02ef7e5f 49395d50 cmp qword ptr [r13+50h],rbx ds:002b:01000000`00000050=????????????????
Resetting default scope

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

BUGCHECK_STR: 0x3B

PROCESS_NAME: firefox.exe

CURRENT_IRQL: 2

ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre

LAST_CONTROL_TRANSFER: from fffff80002f0f96c to fffff80002ef7e5f

STACK_TEXT:
fffff880`09aad5a0 fffff800`02f0f96c : 00000000`00000000 fffffa80`06df2430 00000000`00000000 fffffa80`06df23b0 : nt!MiCheckControlArea+0x17f
fffff880`09aad610 fffff800`02eada24 : ffffffff`ffffffff 00000000`00000000 fffffa80`06df2430 fffffa80`06df2430 : nt!MiRemoveMappedView+0x26c
fffff880`09aad730 fffff800`031b115a : fffff8a0`14df4060 00000000`00000001 00000000`00000000 fffffa80`08bc3060 : nt!MmCleanProcessAddressSpace+0x228
fffff880`09aad780 fffff800`031956b8 : 00000000`00000000 00000000`00000001 00000000`fffdb000 00000000`00000000 : nt!PspExitThread+0x56a
fffff880`09aad880 fffff800`02edbe53 : fffffa80`09241060 00000000`00000000 fffffa80`08bc3060 00000000`003235c8 : nt!NtTerminateProcess+0x138
fffff880`09aad900 00000000`76eb157a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0022b1e8 fffff800`02ed4210 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76eb157a
fffff880`09aadae0 00000000`00000000 : fffffa80`08bc3060 00000000`0022fd01 fffff880`09aadb50 00000000`6d47b770 : nt!KiCallUserMode


FOLLOWUP_IP:
nt!MiCheckControlArea+17f
fffff800`02ef7e5f 49395d50 cmp qword ptr [r13+50h],rbx

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!MiCheckControlArea+17f

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 521ea035

IMAGE_VERSION: 6.1.7601.18247

STACK_COMMAND: .cxr 0xfffff88009aacbc0 ; kb

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: X64_0x3B_nt!MiCheckControlArea+17f

BUCKET_ID: X64_0x3B_nt!MiCheckControlArea+17f

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:x64_0x3b_nt!micheckcontrolarea+17f

FAILURE_ID_HASH: {c686d968-61ed-f972-770f-e6ac25493c76}

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


a b $ Windows 7
May 5, 2014 5:05:49 PM

What is the exact ram kit you're currently using and what are the specs it is currently running at?
m
1
l
May 6, 2014 8:38:10 AM

C12Friedman said:
What is the exact ram kit you're currently using and what are the specs it is currently running at?

It was previously 1 x 8gb cl11 corsair xms3.However, thinking that it was the problem I replaced it with 2 x 4 gb Hyper X Beast Kingston CL9 RAM which are running in dual channel memory mode at 1800mhz.
m
0
l
Related resources
a b $ Windows 7
May 6, 2014 11:38:12 AM

If running the Hyper-X at 1.65V, I'm going to suggest resetting ram to default (1600MHz and 1.5v). I'm thinking the memory controller isn't real happy about 1.65v. Not necessarily the problem but just what I would try first
m
1
l
May 9, 2014 12:01:21 PM

I'll try putting the speed down to 1600mhz . I may have gotten confused with the clock speeds of the cl11 beast, which is why i put it up to 1800 as I read that there's no benefit of running it higher than that.
m
0
l
!