Win 10 Memory Management BSOD

[Mrbractjones]

I keep getting BSOD you name it Memory Management. A lot of time my dump files are corrupt.

I updated drivers and stopped ocing.

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


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 10240 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 10240.16644.amd64fre.th1.160104-1507
Machine Name:
Kernel base = 0xfffff801`16878000 PsLoadedModuleList = 0xfffff801`16b9d070
Debug session time: Tue Feb 23 03:30:50.368 2016 (UTC - 5:00)
System Uptime: 0 days 0:07:28.008
Loading Kernel Symbols
.............................................................Page 142348 not present in the dump file. Type ".hh dbgerr004" for details
..
................................................................
........................................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 00000000`7ffdf018). Type ".hh dbgerr001" for details
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {61941, fe78000, b, ffffd00020e70610}

Page 132a76 not present in the dump file. Type ".hh dbgerr004" for details
Page 132284 not present in the dump file. Type ".hh dbgerr004" for details
Page 132a76 not present in the dump file. Type ".hh dbgerr004" for details
Page 132a76 not present in the dump file. Type ".hh dbgerr004" for details
Page 132a76 not present in the dump file. Type ".hh dbgerr004" for details
Probably caused by : win32kfull.sys ( win32kfull!vSrcCopyS24D32+99 )

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

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

MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000061941, The subtype of the bugcheck.
Arg2: 000000000fe78000
Arg3: 000000000000000b
Arg4: ffffd00020e70610

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

Page 132284 not present in the dump file. Type ".hh dbgerr004" for details
Page 132a76 not present in the dump file. Type ".hh dbgerr004" for details
Page 132a76 not present in the dump file. Type ".hh dbgerr004" for details
Page 132a76 not present in the dump file. Type ".hh dbgerr004" for details

DUMP_CLASS: 1

DUMP_QUALIFIER: 401

BUILD_VERSION_STRING: 10240.16644.amd64fre.th1.160104-1507

SYSTEM_MANUFACTURER: Gigabyte Technology Co., Ltd.

SYSTEM_PRODUCT_NAME: Z97X-SOC

SYSTEM_SKU: To be filled by O.E.M.

SYSTEM_VERSION: To be filled by O.E.M.

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: F5

BIOS_DATE: 05/30/2014

BASEBOARD_MANUFACTURER: Gigabyte Technology Co., Ltd.

BASEBOARD_PRODUCT: Z97X-SOC-CF

BASEBOARD_VERSION: x.x

DUMP_TYPE: 1

BUGCHECK_P1: 61941

BUGCHECK_P2: fe78000

BUGCHECK_P3: b

BUGCHECK_P4: ffffd00020e70610

BUGCHECK_STR: 0x1a_61941

CPU_COUNT: 8

CPU_MHZ: fa0

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 3c

CPU_STEPPING: 3

CPU_MICROCODE: 6,3c,3,0 (F,M,S,R) SIG: 1E'00000000 (cache) 1E'00000000 (init)

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

PROCESS_NAME: DriverBooster.

CURRENT_IRQL: 0

ANALYSIS_SESSION_HOST: SHIROICHIKARA

ANALYSIS_SESSION_TIME: 02-23-2016 06:16:04.0438

ANALYSIS_VERSION: 10.0.10586.567 amd64fre

TRAP_FRAME: ffffd00020e70610 -- (.trap 0xffffd00020e70610)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000000000001f rbx=0000000000000000 rcx=00000000001f1f1f
rdx=00000000000000ea rsi=0000000000000000 rdi=0000000000000000
rip=fffff960ec6a32b9 rsp=ffffd00020e707a0 rbp=ffffd00020e70c20
r8=0000000000000000 r9=0000000000000000 r10=0000000000000001
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
win32kfull!vSrcCopyS24D32+0x99:
fffff960`ec6a32b9 890f mov dword ptr [rdi],ecx ds:00000000`00000000=????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff801169e5f8e to fffff801169c74d0

STACK_TEXT:
ffffd000`20e704b8 fffff801`169e5f8e : 00000000`0000001a 00000000`00061941 00000000`0fe78000 00000000`0000000b : nt!KeBugCheckEx
ffffd000`20e704c0 fffff801`169d05bd : 00000000`0019f424 00000000`742202e8 00000000`01160000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0xfe8e
ffffd000`20e70610 fffff960`ec6a32b9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x13d
ffffd000`20e707a0 fffff960`ec62312a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : win32kfull!vSrcCopyS24D32+0x99
ffffd000`20e707f0 fffff960`ec62a4e5 : ffffe001`4e97f3e0 ffffd000`20e70c20 fffff901`439fa530 fffff901`426bd010 : win32kfull!EngCopyBits+0x37a
ffffd000`20e70b20 fffff801`169d1b63 : 00000000`00000001 00000000`0019f1fc 00000000`00000000 00000000`00000000 : win32kfull!NtGdiBitBltInternal+0xf25
ffffd000`20e70dd0 00000000`5f53346a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0009cd68 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x5f53346a


STACK_COMMAND: kb

THREAD_SHA1_HASH_MOD_FUNC: 5f4dfef02a90e7d140ae4df85b5bd30fc8d99891

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: e42e66ed960b6bb91e31acf5ddab5cc0be318198

THREAD_SHA1_HASH_MOD: 48f2b5b10bd8f9f270ff8d5fd128fb827137b27f

FOLLOWUP_IP:
win32kfull!vSrcCopyS24D32+99
fffff960`ec6a32b9 890f mov dword ptr [rdi],ecx

FAULT_INSTR_CODE: 83480f89

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: win32kfull!vSrcCopyS24D32+99

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: win32kfull

IMAGE_NAME: win32kfull.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 56ad9827

BUCKET_ID_FUNC_OFFSET: 99

FAILURE_BUCKET_ID: 0x1a_61941_win32kfull!vSrcCopyS24D32

BUCKET_ID: 0x1a_61941_win32kfull!vSrcCopyS24D32

PRIMARY_PROBLEM_CLASS: 0x1a_61941_win32kfull!vSrcCopyS24D32

TARGET_TIME: 2016-02-23T08:30:50.000Z

OSBUILD: 10240

OSSERVICEPACK: 0

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 272

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:












USER_LCID: 0

OSBUILD_TIMESTAMP: 2016-01-04 21:09:59

BUILDDATESTAMP_STR: 160104-1507

BUILDLAB_STR: th1

BUILDOSVER_STR: 10.0.10240.16644.amd64fre.th1.160104-1507

ANALYSIS_SESSION_ELAPSED_TIME: e63

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x1a_61941_win32kfull!vsrccopys24d32

FAILURE_ID_HASH: {893f8dca-e1cf-ac9e-66a3-55eb9feced9d}

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

This is my dump latest but its not right I just installed driver booster to install drivers / and this error happens all the time prior.

This is my ram http://www.amazon.com/gp/product/B00GM83C86?psc=1&redirect=true&ref_=oh_aui_detailpage_o08_s03

I just went into bios and manually oc my ram instead of XMP. Intel Core i7 47490k I have SOC 97 Gigabyte mobo.

 

[combinebasic]

Have you check the bandwidth of your RAM?be sure that it have a same SPECS and check also if there are problems of your RAM. Try to use your BIOS if there are any RAM diagnostics or use any software to test your memory. Check also the supports of your HDD in your BIOS. Then try to install your windows using a DVD ROM rather than the USB. Avoid OC to avoid over heat of the processor that probably cause also of the BSOD. Go back here after

 

[Mrbractjones]

Have you check the bandwidth of your RAM?be sure that it have a same SPECS and check also if there are problems of your RAM. Try to use your BIOS if there are any RAM diagnostics or use any software to test your memory. Check also the supports of your HDD in your BIOS. Then try to install your windows using a DVD ROM rather than the USB. Avoid OC to avoid over heat of the processor that probably cause also of the BSOD. Go back here after

I just went into bios and manual configed my Ram. It was not getting right volt that said on product page. 1.50v instead of 1.65v. I have been getting bsod in 30 to 1hr intervals in morning. Now that I did this to the ram I seem to be fine.

 

[combinebasic]

Ok try to isolate the PSU in system case and power up it using a paper clip and measure the voltage output using voltmeter to sure its the PSU is bad. It probably also the cause because of the low voltage supplied to the system.

 

[Mrbractjones]

Ok try to isolate the PSU in system case and power up it using a paper clip and measure the voltage output using voltmeter to sure its the PSU is bad. It probably also the cause because of the low voltage supplied to the system.

I have been thru that error in the past , its not that as well as I checked volts earlier. I think this was a case of me just hoping the xmp profile did its job for long time. It did not not , and finally this error made me have to get up and do it manually. so far very long run untill a bsod.

 

[Mrbractjones]

Just had bsod again after about 12hrs .

NEW dump

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


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 10240 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 10240.16644.amd64fre.th1.160104-1507
Machine Name:
Kernel base = 0xfffff801`1ba03000 PsLoadedModuleList = 0xfffff801`1bd28070
Debug session time: Tue Feb 23 14:06:00.061 2016 (UTC - 5:00)
System Uptime: 0 days 7:32:42.689
Loading Kernel Symbols
...............................................................
................................................................
..........................................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 00007ff7`942af018). Type ".hh dbgerr001" for details
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41792, fffff6bffc72ec00, 80000000000000, 0}

Page 129c82 not present in the dump file. Type ".hh dbgerr004" for details
Probably caused by : memory_corruption ( ONE_BIT )

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

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

MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041792, A corrupt PTE has been detected. Parameter 2 contains the address of
the PTE. Parameters 3/4 contain the low/high parts of the PTE.
Arg2: fffff6bffc72ec00
Arg3: 0080000000000000
Arg4: 0000000000000000

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

Page 129c82 not present in the dump file. Type ".hh dbgerr004" for details

DUMP_CLASS: 1

DUMP_QUALIFIER: 401

BUILD_VERSION_STRING: 10240.16644.amd64fre.th1.160104-1507

SYSTEM_MANUFACTURER: Gigabyte Technology Co., Ltd.

SYSTEM_PRODUCT_NAME: Z97X-SOC

SYSTEM_SKU: To be filled by O.E.M.

SYSTEM_VERSION: To be filled by O.E.M.

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: F5

BIOS_DATE: 05/30/2014

BASEBOARD_MANUFACTURER: Gigabyte Technology Co., Ltd.

BASEBOARD_PRODUCT: Z97X-SOC-CF

BASEBOARD_VERSION: x.x

DUMP_TYPE: 1

BUGCHECK_P1: 41792

BUGCHECK_P2: fffff6bffc72ec00

BUGCHECK_P3: 80000000000000

BUGCHECK_P4: 0

MEMORY_CORRUPTOR: ONE_BIT

BUGCHECK_STR: 0x1a_41792

CPU_COUNT: 8

CPU_MHZ: fa0

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 3c

CPU_STEPPING: 3

CPU_MICROCODE: 6,3c,3,0 (F,M,S,R) SIG: 1E'00000000 (cache) 1E'00000000 (init)

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

PROCESS_NAME: svchost.exe

CURRENT_IRQL: 2

ANALYSIS_SESSION_HOST: SHIROICHIKARA

ANALYSIS_SESSION_TIME: 02-23-2016 14:09:22.0569

ANALYSIS_VERSION: 10.0.10586.567 amd64fre

STACK_TEXT:
ffffd000`e21e96a8 fffff801`1bb81ef8 : 00000000`0000001a 00000000`00041792 fffff6bf`fc72ec00 00800000`00000000 : nt!KeBugCheckEx
ffffd000`e21e96b0 fffff801`1ba314f0 : fffff801`01401903 00000000`00000002 ffffe001`76f48d38 00000000`00000344 : nt! ?? ::FNODOBFM::`string'+0x20df8
ffffd000`e21e98b0 fffff801`1be1ecac : 00000000`00376000 ffffe001`77691f70 ffffe001`7201a180 00007ff8`e5d70000 : nt!MiDeleteVad+0x4b0
ffffd000`e21e99e0 fffff801`1be1f367 : 00000000`00000000 00000000`00000008 00007ff8`e5d70000 00000000`00000001 : nt!MiUnmapViewOfSection+0xec
ffffd000`e21e9ab0 fffff801`1bb5cb63 : ffffe001`76288840 00000000`00000000 ffffe001`76288840 ffffe001`76f48840 : nt!NtUnmapViewOfSectionEx+0x77
ffffd000`e21e9b00 00007ff8`f53a3aca : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000016`24fa9d18 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff8`f53a3aca


STACK_COMMAND: kb

THREAD_SHA1_HASH_MOD_FUNC: 26b5e3f78698d2c1711b87b803223a7d339d110b

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 9c63e9d3c1782a20b8d06544b52c8905b4c35f2a

THREAD_SHA1_HASH_MOD: ee8fcf1fb60cb6e3e2f60ddbed2ec02b5748a693

SYMBOL_NAME: ONE_BIT

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: hardware

IMAGE_NAME: memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP: 0

IMAGE_VERSION:

FAILURE_BUCKET_ID: MEMORY_CORRUPTION_ONE_BIT

BUCKET_ID: MEMORY_CORRUPTION_ONE_BIT

PRIMARY_PROBLEM_CLASS: MEMORY_CORRUPTION_ONE_BIT

TARGET_TIME: 2016-02-23T19:06:00.000Z

OSBUILD: 10240

OSSERVICEPACK: 0

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 272

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:

USER_LCID: 0

OSBUILD_TIMESTAMP: 2016-01-04 21:09:59

BUILDDATESTAMP_STR: 160104-1507

BUILDLAB_STR: th1

BUILDOSVER_STR: 10.0.10240.16644.amd64fre.th1.160104-1507

ANALYSIS_SESSION_ELAPSED_TIME: a2f

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:memory_corruption_one_bit

FAILURE_ID_HASH: {e3faf315-c3d0-81db-819a-6c43d23c63a7}

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

 

[combinebasic]

Because you do overclocking I suggest to default to manufacturer settings your BIOS, might be help.