Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Windows Crashes installing new identical RAM


  • Please log in to reply
8 replies to this topic

#1 Xebozone

Xebozone

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:03:39 PM

Posted 12 October 2016 - 10:54 AM

I was doing a RAM upgrade for a friend tonight, and in all my >10 years in computer support I've never had such confusing issues.

 

Motherboard: GA-Z170XP-SLI

Current RAM: HX421C14FBK2/8 Kingston HyperX Fury 8GB Kit - 2x4GB

New Ram: HX421C14FBK2/8 (same)

The only difference is the revision numbers. The new ram says 059.A00LF while the old ram was 035 or something in the 03x range. Visually, they are identical.

 

Placing the RAM in the PC is fine. Bios reports 16GB of ram.

The only thing I noticed different in BIOS were the memory stats for Channel A being 1 number different from Channel B.

The tWTR was 4 on one channel, and 5 on the other if memory serves correctly.

 

Now the issue:

Windows 10 is not happy and bluescreens on any and all attempts to boot, be it in automated recovery or standard boot modes.

Bluescreens have random messages. Sometimes Kernel errors, sometimes IRQL, sometimes memory management, etc etc.

 

This only happens when the old RAM and the new RAM are mixed... which is odd, because they are the same model numbers.

This build is not even 1 year old, so I wouldn't imagine that the box of new ram will have changed so much that it's incompatible!

I did windows memory diagnostics with just the two new sticks in (and on the two new slots), and everything was fine.

 

I tested ram in all slots and in all combinations.

Everything is fine until I insert 1 or more of the new ram sticks in combination with the old.

The system is even fine running the new ram alone in slots 1 & 3 (Channel A) or in slots 2 & 4 (Channel B ).

The only thing that causes an issue is when the new and old RAM are mixed.

 

I tried changing the tWTR timing on the new ram to be 1 unit slower to match the stats of the old ram, and that doesn't help either.

 

No BIOS updates exist for this motherboard, and Windows 10 is fully up-to-date.

 

Does anyone have any advice on how to get this working?
I don't have the PC with me now, but I can go back and try some things.

I wouldn't like to return the RAM, as I believe it is not faulty, nor is the motherboard. Every stick of ram works fine in every slot until they are mixed...

 

I have yet to run a memtestx86 or ubuntu boot disk with all ram inside... that is the next step... but that's probably not going to resolve the windows issues.

 

Edit: Attached memory dumps and BlueScreenView report

 

Edit2:

After cross-referencing the bug check codes with the documentation on the MSDN

The following errors were found matching from the parameters:

  • The allocation bitmap is corrupt. The memory manager is about to overwrite a virtual address that was already in use.
  • A memory access violation occurred

Attached Files

  • Attached File  BSOD.zip   296.88KB   1 downloads

Edited by hamluis, 13 October 2016 - 02:29 PM.
Moved from Internal Hardware to Crashes/BSODs - Hamluis.


BC AdBot (Login to Remove)

 


#2 Xebozone

Xebozone
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:03:39 PM

Posted 13 October 2016 - 11:31 AM

Edit3:

 

I downloaded the Windows debugging tools and I followed this guide on running bugchecks

 

Bugchecks for 3/4 dumps are as follows (one just took too long, and so I gave up... but I think this will say enough):

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


Loading Dump File [L:\Gary BSOD\101216-9484-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       srv*L:\DebugSymbols*https://msdl.microsoft.com/download/symbols
Symbol search path is: srv*L:\DebugSymbols*https://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 10 Kernel Version 14393 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 14393.321.amd64fre.rs1_release_inmarket.161004-2338
Machine Name:
Kernel base = 0xfffff801`bee1b000 PsLoadedModuleList = 0xfffff801`bf11f080
Debug session time: Wed Oct 12 20:45:09.455 2016 (UTC + 8:00)
System Uptime: 0 days 0:00:22.076
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 1E, {ffffffffc0000005, fffff801bee5b650, 0, ffffffffffffffff}

*** WARNING: Unable to verify timestamp for mssmbios.sys
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
Probably caused by : memory_corruption

Followup:     memory_corruption
---------

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

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff801bee5b650, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffffffffffffffff, Parameter 1 of the exception

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


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  10.0.14393.321 (rs1_release_inmarket.161004-2338)

DUMP_TYPE:  2

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff801bee5b650

BUGCHECK_P3: 0

BUGCHECK_P4: ffffffffffffffff

READ_ADDRESS: fffff801bf1c1338: Unable to get MiVisibleState
 ffffffffffffffff 

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

FAULTING_IP: 
nt!KiExpireTimer2+340
fffff801`bee5b650 ffd6            call    rsi

EXCEPTION_PARAMETER2:  ffffffffffffffff

BUGCHECK_STR:  0x1E_c0000005_R

CPU_COUNT: 4

CPU_MHZ: db0

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 5e

CPU_STEPPING: 3

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

PROCESS_NAME:  System

CURRENT_IRQL:  2

ANALYSIS_SESSION_HOST:  NEWCOMP

ANALYSIS_SESSION_TIME:  10-14-2016 00:07:04.0101

ANALYSIS_VERSION: 10.0.14321.1024 amd64fre

LAST_CONTROL_TRANSFER:  from fffff801befec7c2 to fffff801bef652c0

STACK_TEXT:  
ffffb680`ff1fc628 fffff801`befec7c2 : 00000000`0000001e ffffffff`c0000005 fffff801`bee5b650 00000000`00000000 : nt!KeBugCheckEx
ffffb680`ff1fc630 fffff801`bef6b6bd : fffff801`bf16f000 fffff801`bee1b000 0004f608`0081f000 0ffa3b00`00008024 : nt!KiFatalExceptionHandler+0x22
ffffb680`ff1fc670 fffff801`bee76a01 : ffffb680`ff1fe000 00000000`00000000 ffffb680`ff1f7000 00a024a4`280fc4ef : nt!RtlpExecuteHandlerForException+0xd
ffffb680`ff1fc6a0 fffff801`bee757b4 : ffffb680`ff1fcdd0 ffffb680`ff1fd2d0 ffffb680`ff1fcdd0 ffffb680`ff1fd5a8 : nt!RtlDispatchException+0x421
ffffb680`ff1fcda0 fffff801`bef70502 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchException+0x144
ffffb680`ff1fd470 fffff801`bef6e7bd : 00000000`00000000 00000000`00000000 ffffb680`ff178180 00000000`00000000 : nt!KiExceptionDispatch+0xc2
ffffb680`ff1fd650 fffff801`bee5b650 : ffff8006`be598d10 ffffb680`ff178180 ffffffff`ffd016f8 ffff8006`ba9cf001 : nt!KiGeneralProtectionFault+0xfd
ffffb680`ff1fd7e0 fffff801`bee4f86c : 00000000`0d288a4d ffff8006`be598d28 00000000`00000000 ffffb680`ff1fdae0 : nt!KiExpireTimer2+0x340
ffffb680`ff1fd8f0 fffff801`bee4e13c : 00000000`0d288a4d ffff8006`ba9d2578 00000000`00000000 ffffb680`ff178180 : nt!KiTimer2Expiration+0x11c
ffffb680`ff1fd960 fffff801`bef6834a : 00000000`00000000 ffffb680`ff178180 ffffb680`ff184bc0 ffff8006`baf35040 : nt!KiRetireDpcList+0x5cc
ffffb680`ff1fdbe0 00000000`00000000 : ffffb680`ff1fe000 ffffb680`ff1f7000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
    fffff801bee5b261 - nt!MiVaToPfn+31
	[ f6:fd ]
1 error : !nt (fffff801bee5b261)

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  ONE_BYTE

FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_ONE_BYTE

BUCKET_ID:  MEMORY_CORRUPTION_ONE_BYTE

PRIMARY_PROBLEM_CLASS:  MEMORY_CORRUPTION_ONE_BYTE

TARGET_TIME:  2016-10-12T12:45:09.000Z

OSBUILD:  14393

OSSERVICEPACK:  321

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-10-05 17:17:53

BUILDDATESTAMP_STR:  161004-2338

BUILDLAB_STR:  rs1_release_inmarket

BUILDOSVER_STR:  10.0.14393.321

ANALYSIS_SESSION_ELAPSED_TIME: 26df

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:memory_corruption_one_byte

FAILURE_ID_HASH:  {ad110d6a-3b33-2c0a-c931-570eae1ba92d}

Followup:     memory_corruption
---------

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

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff801bee5b650, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffffffffffffffff, Parameter 1 of the exception

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


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  10.0.14393.321 (rs1_release_inmarket.161004-2338)

DUMP_TYPE:  2

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff801bee5b650

BUGCHECK_P3: 0

BUGCHECK_P4: ffffffffffffffff

READ_ADDRESS:  ffffffffffffffff 

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

FAULTING_IP: 
nt!KiExpireTimer2+340
fffff801`bee5b650 ffd6            call    rsi

EXCEPTION_PARAMETER2:  ffffffffffffffff

BUGCHECK_STR:  0x1E_c0000005_R

CPU_COUNT: 4

CPU_MHZ: db0

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 5e

CPU_STEPPING: 3

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

PROCESS_NAME:  System

CURRENT_IRQL:  2

ANALYSIS_SESSION_HOST:  NEWCOMP

ANALYSIS_SESSION_TIME:  10-14-2016 00:07:19.0491

ANALYSIS_VERSION: 10.0.14321.1024 amd64fre

LAST_CONTROL_TRANSFER:  from fffff801befec7c2 to fffff801bef652c0

STACK_TEXT:  
ffffb680`ff1fc628 fffff801`befec7c2 : 00000000`0000001e ffffffff`c0000005 fffff801`bee5b650 00000000`00000000 : nt!KeBugCheckEx
ffffb680`ff1fc630 fffff801`bef6b6bd : fffff801`bf16f000 fffff801`bee1b000 0004f608`0081f000 0ffa3b00`00008024 : nt!KiFatalExceptionHandler+0x22
ffffb680`ff1fc670 fffff801`bee76a01 : ffffb680`ff1fe000 00000000`00000000 ffffb680`ff1f7000 00a024a4`280fc4ef : nt!RtlpExecuteHandlerForException+0xd
ffffb680`ff1fc6a0 fffff801`bee757b4 : ffffb680`ff1fcdd0 ffffb680`ff1fd2d0 ffffb680`ff1fcdd0 ffffb680`ff1fd5a8 : nt!RtlDispatchException+0x421
ffffb680`ff1fcda0 fffff801`bef70502 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchException+0x144
ffffb680`ff1fd470 fffff801`bef6e7bd : 00000000`00000000 00000000`00000000 ffffb680`ff178180 00000000`00000000 : nt!KiExceptionDispatch+0xc2
ffffb680`ff1fd650 fffff801`bee5b650 : ffff8006`be598d10 ffffb680`ff178180 ffffffff`ffd016f8 ffff8006`ba9cf001 : nt!KiGeneralProtectionFault+0xfd
ffffb680`ff1fd7e0 fffff801`bee4f86c : 00000000`0d288a4d ffff8006`be598d28 00000000`00000000 ffffb680`ff1fdae0 : nt!KiExpireTimer2+0x340
ffffb680`ff1fd8f0 fffff801`bee4e13c : 00000000`0d288a4d ffff8006`ba9d2578 00000000`00000000 ffffb680`ff178180 : nt!KiTimer2Expiration+0x11c
ffffb680`ff1fd960 fffff801`bef6834a : 00000000`00000000 ffffb680`ff178180 ffffb680`ff184bc0 ffff8006`baf35040 : nt!KiRetireDpcList+0x5cc
ffffb680`ff1fdbe0 00000000`00000000 : ffffb680`ff1fe000 ffffb680`ff1f7000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
    fffff801bee5b261 - nt!MiVaToPfn+31
	[ f6:fd ]
1 error : !nt (fffff801bee5b261)

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  ONE_BYTE

FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_ONE_BYTE

BUCKET_ID:  MEMORY_CORRUPTION_ONE_BYTE

PRIMARY_PROBLEM_CLASS:  MEMORY_CORRUPTION_ONE_BYTE

TARGET_TIME:  2016-10-12T12:45:09.000Z

OSBUILD:  14393

OSSERVICEPACK:  321

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-10-05 17:17:53

BUILDDATESTAMP_STR:  161004-2338

BUILDLAB_STR:  rs1_release_inmarket

BUILDOSVER_STR:  10.0.14393.321

ANALYSIS_SESSION_ELAPSED_TIME: 27aa

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:memory_corruption_one_byte

FAILURE_ID_HASH:  {ad110d6a-3b33-2c0a-c931-570eae1ba92d}

Followup:     memory_corruption
---------


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


Loading Dump File [L:\Gary BSOD\101216-8796-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       srv*L:\DebugSymbols*https://msdl.microsoft.com/download/symbols
Symbol search path is: srv*L:\DebugSymbols*https://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 10 Kernel Version 14393 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 14393.321.amd64fre.rs1_release_inmarket.161004-2338
Machine Name:
Kernel base = 0xfffff800`d1e94000 PsLoadedModuleList = 0xfffff800`d2198080
Debug session time: Wed Oct 12 21:03:14.118 2016 (UTC + 8:00)
System Uptime: 0 days 0:00:04.740
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
....
*** WARNING: Unable to verify timestamp for avgmfx64.sys
*** ERROR: Module load completed but symbols could not be loaded for avgmfx64.sys
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff800d1eddb3a, ffffd181c3355f28, ffffd181c3355750}

*** WARNING: Unable to verify timestamp for mssmbios.sys
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
Probably caused by : memory_corruption

Followup:     memory_corruption
---------

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff800d1eddb3a, The address that the exception occurred at
Arg3: ffffd181c3355f28, Exception Record Address
Arg4: ffffd181c3355750, Context Record Address

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


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  10.0.14393.321 (rs1_release_inmarket.161004-2338)

DUMP_TYPE:  2

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff800d1eddb3a

BUGCHECK_P3: ffffd181c3355f28

BUGCHECK_P4: ffffd181c3355750

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

FAULTING_IP: 
nt!ExReleaseFastMutex+a
fffff800`d1eddb3a 0fb67930        movzx   edi,byte ptr [rcx+30h]

EXCEPTION_RECORD:  ffffd181c3355f28 -- (.exr 0xffffd181c3355f28)
ExceptionAddress: fffff800d1eddb3a (nt!ExReleaseFastMutex+0x000000000000000a)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  ffffd181c3355750 -- (.cxr 0xffffd181c3355750)
rax=ffffe70faa1556e8 rbx=7fffe70faa1556e8 rcx=7fffe70faa155758
rdx=000000000000003d rsi=0000000000120089 rdi=0000000000000001
rip=fffff800d1eddb3a rsp=ffffd181c3356160 rbp=0000000000000001
 r8=ffffe70faa1556e8  r9=ffffe70faa1556e8 r10=0000000001000060
r11=0000000000120089 r12=0000000010000000 r13=ffffe70faa180c00
r14=0000000000000001 r15=ffffe70faa85e200
iopl=0         nv up ei ng nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010286
nt!ExReleaseFastMutex+0xa:
fffff800`d1eddb3a 0fb67930        movzx   edi,byte ptr [rcx+30h] ds:002b:7fffe70f`aa155788=??
Resetting default scope

CPU_COUNT: 4

CPU_MHZ: db0

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 5e

CPU_STEPPING: 3

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

PROCESS_NAME:  System

CURRENT_IRQL:  1

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

EXCEPTION_CODE_STR:  c0000005

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

FOLLOWUP_IP: 
nt!ExReleaseFastMutex+a
fffff800`d1eddb3a 0fb67930        movzx   edi,byte ptr [rcx+30h]

READ_ADDRESS: fffff800d223a338: Unable to get MiVisibleState
 ffffffffffffffff 

BUGCHECK_STR:  AV

ANALYSIS_SESSION_HOST:  NEWCOMP

ANALYSIS_SESSION_TIME:  10-14-2016 00:07:30.0291

ANALYSIS_VERSION: 10.0.14321.1024 amd64fre

LAST_CONTROL_TRANSFER:  from fffff806227b2b8a to fffff800d1eddb3a

STACK_TEXT:  
ffffd181`c3356160 fffff806`227b2b8a : 7fffe70f`aa1556e8 ffffd181`00000000 00000000`00000001 00000000`00120089 : nt!ExReleaseFastMutex+0xa
ffffd181`c3356190 7fffe70f`aa1556e8 : ffffd181`00000000 00000000`00000001 00000000`00120089 ffffe70f`a6f3d040 : avgmfx64+0x12b8a
ffffd181`c3356198 ffffd181`00000000 : 00000000`00000001 00000000`00120089 ffffe70f`a6f3d040 fffff806`227a5807 : 0x7fffe70f`aa1556e8
ffffd181`c33561a0 00000000`00000001 : 00000000`00120089 ffffe70f`a6f3d040 fffff806`227a5807 00000000`00000001 : 0xffffd181`00000000
ffffd181`c33561a8 00000000`00120089 : ffffe70f`a6f3d040 fffff806`227a5807 00000000`00000001 ffffd181`c3356330 : 0x1
ffffd181`c33561b0 ffffe70f`a6f3d040 : fffff806`227a5807 00000000`00000001 ffffd181`c3356330 00000000`00000000 : 0x120089
ffffd181`c33561b8 fffff806`227a5807 : 00000000`00000001 ffffd181`c3356330 00000000`00000000 00000000`00000001 : 0xffffe70f`a6f3d040
ffffd181`c33561c0 00000000`00000001 : ffffd181`c3356330 00000000`00000000 00000000`00000001 ffffe70f`aa85e298 : avgmfx64+0x5807
ffffd181`c33561c8 ffffd181`c3356330 : 00000000`00000000 00000000`00000001 ffffe70f`aa85e298 fffff806`227a59de : 0x1
ffffd181`c33561d0 00000000`00000000 : 00000000`00000001 ffffe70f`aa85e298 fffff806`227a59de ffffe70f`00000000 : 0xffffd181`c3356330


CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
    fffff800d1f02802 - nt!MiAllocateWsle+422
	[ f6:97 ]
    fffff800d20df387-fffff800d20df389  3 bytes - nt!ExFreePoolWithTag+387
	[ 40 fb f6:c0 cb 97 ]
4 errors : !nt (fffff800d1f02802-fffff800d20df389)

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  LARGE

STACK_COMMAND:  .cxr 0xffffd181c3355750 ; kb

FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_LARGE

BUCKET_ID:  MEMORY_CORRUPTION_LARGE

PRIMARY_PROBLEM_CLASS:  MEMORY_CORRUPTION_LARGE

TARGET_TIME:  2016-10-12T13:03:14.000Z

OSBUILD:  14393

OSSERVICEPACK:  321

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-10-05 17:17:53

BUILDDATESTAMP_STR:  161004-2338

BUILDLAB_STR:  rs1_release_inmarket

BUILDOSVER_STR:  10.0.14393.321

ANALYSIS_SESSION_ELAPSED_TIME: 2662

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:memory_corruption_large

FAILURE_ID_HASH:  {e29154ac-69a4-0eb8-172a-a860f73c0a3c}

Followup:     memory_corruption
---------

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff800d1eddb3a, The address that the exception occurred at
Arg3: ffffd181c3355f28, Exception Record Address
Arg4: ffffd181c3355750, Context Record Address

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


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  10.0.14393.321 (rs1_release_inmarket.161004-2338)

DUMP_TYPE:  2

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff800d1eddb3a

BUGCHECK_P3: ffffd181c3355f28

BUGCHECK_P4: ffffd181c3355750

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

FAULTING_IP: 
nt!ExReleaseFastMutex+a
fffff800`d1eddb3a 0fb67930        movzx   edi,byte ptr [rcx+30h]

EXCEPTION_RECORD:  ffffd181c3355f28 -- (.exr 0xffffd181c3355f28)
ExceptionAddress: fffff800d1eddb3a (nt!ExReleaseFastMutex+0x000000000000000a)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  ffffd181c3355750 -- (.cxr 0xffffd181c3355750)
rax=ffffe70faa1556e8 rbx=7fffe70faa1556e8 rcx=7fffe70faa155758
rdx=000000000000003d rsi=0000000000120089 rdi=0000000000000001
rip=fffff800d1eddb3a rsp=ffffd181c3356160 rbp=0000000000000001
 r8=ffffe70faa1556e8  r9=ffffe70faa1556e8 r10=0000000001000060
r11=0000000000120089 r12=0000000010000000 r13=ffffe70faa180c00
r14=0000000000000001 r15=ffffe70faa85e200
iopl=0         nv up ei ng nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010286
nt!ExReleaseFastMutex+0xa:
fffff800`d1eddb3a 0fb67930        movzx   edi,byte ptr [rcx+30h] ds:002b:7fffe70f`aa155788=??
Resetting default scope

CPU_COUNT: 4

CPU_MHZ: db0

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 5e

CPU_STEPPING: 3

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

PROCESS_NAME:  System

CURRENT_IRQL:  1

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

EXCEPTION_CODE_STR:  c0000005

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

FOLLOWUP_IP: 
nt!ExReleaseFastMutex+a
fffff800`d1eddb3a 0fb67930        movzx   edi,byte ptr [rcx+30h]

READ_ADDRESS:  ffffffffffffffff 

BUGCHECK_STR:  AV

ANALYSIS_SESSION_HOST:  NEWCOMP

ANALYSIS_SESSION_TIME:  10-14-2016 00:07:45.0704

ANALYSIS_VERSION: 10.0.14321.1024 amd64fre

LAST_CONTROL_TRANSFER:  from fffff806227b2b8a to fffff800d1eddb3a

STACK_TEXT:  
ffffd181`c3356160 fffff806`227b2b8a : 7fffe70f`aa1556e8 ffffd181`00000000 00000000`00000001 00000000`00120089 : nt!ExReleaseFastMutex+0xa
ffffd181`c3356190 7fffe70f`aa1556e8 : ffffd181`00000000 00000000`00000001 00000000`00120089 ffffe70f`a6f3d040 : avgmfx64+0x12b8a
ffffd181`c3356198 ffffd181`00000000 : 00000000`00000001 00000000`00120089 ffffe70f`a6f3d040 fffff806`227a5807 : 0x7fffe70f`aa1556e8
ffffd181`c33561a0 00000000`00000001 : 00000000`00120089 ffffe70f`a6f3d040 fffff806`227a5807 00000000`00000001 : 0xffffd181`00000000
ffffd181`c33561a8 00000000`00120089 : ffffe70f`a6f3d040 fffff806`227a5807 00000000`00000001 ffffd181`c3356330 : 0x1
ffffd181`c33561b0 ffffe70f`a6f3d040 : fffff806`227a5807 00000000`00000001 ffffd181`c3356330 00000000`00000000 : 0x120089
ffffd181`c33561b8 fffff806`227a5807 : 00000000`00000001 ffffd181`c3356330 00000000`00000000 00000000`00000001 : 0xffffe70f`a6f3d040
ffffd181`c33561c0 00000000`00000001 : ffffd181`c3356330 00000000`00000000 00000000`00000001 ffffe70f`aa85e298 : avgmfx64+0x5807
ffffd181`c33561c8 ffffd181`c3356330 : 00000000`00000000 00000000`00000001 ffffe70f`aa85e298 fffff806`227a59de : 0x1
ffffd181`c33561d0 00000000`00000000 : 00000000`00000001 ffffe70f`aa85e298 fffff806`227a59de ffffe70f`00000000 : 0xffffd181`c3356330


CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
    fffff800d1f02802 - nt!MiAllocateWsle+422
	[ f6:97 ]
    fffff800d20df387-fffff800d20df389  3 bytes - nt!ExFreePoolWithTag+387
	[ 40 fb f6:c0 cb 97 ]
4 errors : !nt (fffff800d1f02802-fffff800d20df389)

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  LARGE

STACK_COMMAND:  .cxr 0xffffd181c3355750 ; kb

FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_LARGE

BUCKET_ID:  MEMORY_CORRUPTION_LARGE

PRIMARY_PROBLEM_CLASS:  MEMORY_CORRUPTION_LARGE

TARGET_TIME:  2016-10-12T13:03:14.000Z

OSBUILD:  14393

OSSERVICEPACK:  321

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-10-05 17:17:53

BUILDDATESTAMP_STR:  161004-2338

BUILDLAB_STR:  rs1_release_inmarket

BUILDOSVER_STR:  10.0.14393.321

ANALYSIS_SESSION_ELAPSED_TIME: 2622

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:memory_corruption_large

FAILURE_ID_HASH:  {e29154ac-69a4-0eb8-172a-a860f73c0a3c}

Followup:     memory_corruption
---------



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


Loading Dump File [L:\Gary BSOD\101216-11171-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       srv*L:\DebugSymbols*https://msdl.microsoft.com/download/symbols
Symbol search path is: srv*L:\DebugSymbols*https://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 10 Kernel Version 14393 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 14393.321.amd64fre.rs1_release_inmarket.161004-2338
Machine Name:
Kernel base = 0xfffff802`3ae02000 PsLoadedModuleList = 0xfffff802`3b106080
Debug session time: Wed Oct 12 20:15:29.617 2016 (UTC + 8:00)
System Uptime: 0 days 0:00:04.237
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 1A, {5100, fffff965c0f592f8, 1, 40000000000040}

*** WARNING: Unable to verify timestamp for mssmbios.sys
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for storport.sys - 
*** WARNING: Unable to verify timestamp for CLASSPNP.SYS
*** ERROR: Module load completed but symbols could not be loaded for CLASSPNP.SYS
Probably caused by : memory_corruption

Followup:     memory_corruption
---------

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

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000005100, The subtype of the bugcheck.
Arg2: fffff965c0f592f8
Arg3: 0000000000000001
Arg4: 0040000000000040

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


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  10.0.14393.321 (rs1_release_inmarket.161004-2338)

DUMP_TYPE:  2

BUGCHECK_P1: 5100

BUGCHECK_P2: fffff965c0f592f8

BUGCHECK_P3: 1

BUGCHECK_P4: 40000000000040

BUGCHECK_STR:  0x1a_5100

CPU_COUNT: 4

CPU_MHZ: db0

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 5e

CPU_STEPPING: 3

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

PROCESS_NAME:  System

CURRENT_IRQL:  2

ANALYSIS_SESSION_HOST:  NEWCOMP

ANALYSIS_SESSION_TIME:  10-14-2016 00:07:13.0922

ANALYSIS_VERSION: 10.0.14321.1024 amd64fre

LAST_CONTROL_TRANSFER:  from fffff8023af86481 to fffff8023af4c2c0

STACK_TEXT:  
ffffcb81`eb296fc8 fffff802`3af86481 : 00000000`0000001a 00000000`00005100 fffff965`c0f592f8 00000000`00000001 : nt!KeBugCheckEx
ffffcb81`eb296fd0 fffff802`3ae949b9 : 00000000`00000000 fffff80b`2fcb3bdf 00000000`00000000 00000000`00001c40 : nt! ?? ::FNODOBFM::`string'+0x2aff1
ffffcb81`eb297120 fffff802`3ae94123 : fffff802`3b123d30 ffffe08f`00000020 00000000`00000000 00000000`00000000 : nt!MiReservePtes+0x299
ffffcb81`eb2971f0 fffff80b`2f8b4c70 : ffffcb81`eb297330 ffffcb81`eb2972d8 ffffcb81`ea188010 00000000`000007d0 : nt!MmMapLockedPagesSpecifyCache+0xd3
ffffcb81`eb2972b0 fffff80b`2f8b4765 : ffffe08f`9530b1a0 ffffe08f`9530b050 ffffe08f`981cb088 fffff80b`2f8b451b : storport!StorPortSetDeviceQueueDepth+0x2260
ffffcb81`eb2973b0 fffff80b`2f8b4155 : 00000000`00000001 ffffcb81`40200342 ffffcb81`eb2974c8 00000000`00000000 : storport!StorPortSetDeviceQueueDepth+0x1d55
ffffcb81`eb297470 fffff80b`2f8b3a32 : 00000000`00001000 ffffe08f`94734100 ffffe08f`00000000 ffffe08f`9878ae01 : storport!StorPortSetDeviceQueueDepth+0x1745
ffffcb81`eb297550 fffff80b`2f8b389a : ffffe08f`98466b40 00000000`002d1400 ffffe08f`952f5e40 00000000`00000007 : storport!StorPortSetDeviceQueueDepth+0x1022
ffffcb81`eb2975f0 fffff80b`2f524577 : ffffe08f`981cb010 ffffe08f`981cb010 ffffe08f`952f5e40 fffff80b`2f8b1d6b : storport!StorPortSetDeviceQueueDepth+0xe8a
ffffcb81`eb297630 fffff80b`2f52420e : ffffe08f`947bc010 00000000`00000007 ffffe08f`981cb1b8 fffff802`3b04dd12 : ACPI!ACPIIrpDispatchDeviceControl+0x97
ffffcb81`eb297670 fffff80b`2f524577 : 00000000`00000007 ffffe08f`981cb010 ffffe08f`981cb010 ffffe08f`952ed970 : ACPI!ACPIDispatchIrp+0xce
ffffcb81`eb2976f0 fffff80b`2f52420e : ffffe08f`947e2400 00000000`00000007 ffffe08f`981cb1b8 fffff802`3ae3e05b : ACPI!ACPIIrpDispatchDeviceControl+0x97
ffffcb81`eb297730 fffff80b`30a35f01 : 00000000`00000007 ffffe08f`97c24e90 00000000`00000002 00000000`00000103 : ACPI!ACPIDispatchIrp+0xce
ffffcb81`eb2977b0 00000000`00000007 : ffffe08f`97c24e90 00000000`00000002 00000000`00000103 00000000`00000000 : CLASSPNP+0x5f01
ffffcb81`eb2977b8 ffffe08f`97c24e90 : 00000000`00000002 00000000`00000103 00000000`00000000 00000000`00000004 : 0x7
ffffcb81`eb2977c0 00000000`00000002 : 00000000`00000103 00000000`00000000 00000000`00000004 ffffe08f`987c2010 : 0xffffe08f`97c24e90
ffffcb81`eb2977c8 00000000`00000103 : 00000000`00000000 00000000`00000004 ffffe08f`987c2010 ffffe08f`98466b40 : 0x2
ffffcb81`eb2977d0 00000000`00000000 : 00000000`00000004 ffffe08f`987c2010 ffffe08f`98466b40 00000000`00000000 : 0x103


STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
    fffff8023ae94155-fffff8023ae94156  2 bytes - nt!MmMapLockedPagesSpecifyCache+105
	[ 80 f6:00 f9 ]
    fffff8023ae941f0-fffff8023ae941f2  3 bytes - nt!MmMapLockedPagesSpecifyCache+1a0 (+0x9b)
	[ 40 fb f6:80 7c f9 ]
5 errors : !nt (fffff8023ae94155-fffff8023ae941f2)

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  LARGE

FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_LARGE

BUCKET_ID:  MEMORY_CORRUPTION_LARGE

PRIMARY_PROBLEM_CLASS:  MEMORY_CORRUPTION_LARGE

TARGET_TIME:  2016-10-12T12:15:29.000Z

OSBUILD:  14393

OSSERVICEPACK:  321

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-10-05 17:17:53

BUILDDATESTAMP_STR:  161004-2338

BUILDLAB_STR:  rs1_release_inmarket

BUILDOSVER_STR:  10.0.14393.321

ANALYSIS_SESSION_ELAPSED_TIME: 269e

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:memory_corruption_large

FAILURE_ID_HASH:  {e29154ac-69a4-0eb8-172a-a860f73c0a3c}

Followup:     memory_corruption
---------


Thanks! I hope we can work out why this memory is getting corrupted and if we can resolve the issue!


Edited by Xebozone, 13 October 2016 - 11:33 AM.


#3 RolandJS

RolandJS

  • Members
  • 4,525 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Austin TX metro area
  • Local time:02:39 AM

Posted 13 October 2016 - 12:13 PM

A hardware guru in a business computer store told me years ago that any RAM stick "architecture" has to be exactly what the motherboard calls for.  I don't know technically-wise what that means, I do know that I had to purchase exact sticks from the laptop's manufacturer and send back my locally purchased sticks -- because the local RAM sticks architecture was not the same as the manufacturer's RAM sticks architecture.


"Take care of thy backups and thy restores shall take care of thee."  -- Ben Franklin revisited.

http://collegecafe.fr.yuku.com/forums/45/Computer-Technologies/

Backup, backup, backup! -- Lady Fitzgerald (w7forums)

Clone or Image often! Backup... -- RockE (WSL)


#4 hamluis

hamluis

    Moderator


  • Moderator
  • 55,876 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:02:39 AM

Posted 13 October 2016 - 02:29 PM

How to receive help diagnosing Blue Screens and Windows crashes - http://www.bleepingcomputer.com/forums/topic176011.html

 

Moved to Crashes/BSODs.

 

Louis



#5 Xebozone

Xebozone
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:03:39 PM

Posted 13 October 2016 - 08:03 PM

A hardware guru in a business computer store told me years ago that any RAM stick "architecture" has to be exactly what the motherboard calls for.  I don't know technically-wise what that means, I do know that I had to purchase exact sticks from the laptop's manufacturer and send back my locally purchased sticks -- because the local RAM sticks architecture was not the same as the manufacturer's RAM sticks architecture.

This is a custom-built desktop PC. I purchased identical RAM from the same store I purchased parts from when I built the machine at the beginning of the year (10 months ago).


Edited by Xebozone, 13 October 2016 - 08:03 PM.


#6 RolandJS

RolandJS

  • Members
  • 4,525 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Austin TX metro area
  • Local time:02:39 AM

Posted 14 October 2016 - 09:34 AM

This is a custom-built desktop PC. I purchased identical RAM from the same store I purchased parts from when I built the machine at the beginning of the year (10 months ago).

Have you already tried a swap, another pair, just to rule out a possible defect in the newest RAM sticks?


Edited by RolandJS, 14 October 2016 - 09:36 AM.

"Take care of thy backups and thy restores shall take care of thee."  -- Ben Franklin revisited.

http://collegecafe.fr.yuku.com/forums/45/Computer-Technologies/

Backup, backup, backup! -- Lady Fitzgerald (w7forums)

Clone or Image often! Backup... -- RockE (WSL)


#7 Xebozone

Xebozone
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:03:39 PM

Posted 14 October 2016 - 10:49 AM

Thanks for your reply.

Tonight I did more testing. Firstly, I reset BIOS settings to default. I then placed different sticks of RAM into various configurations and ram a memtestx86 all the way to the end (1 pass) to try to figure out the failures.

 

  1. Placed all sticks inside the computer - FAILED
  2. Tried underclocking the RAM - FAILED
  3. Tried undervolting the RAM - FAILED
  4. Tried setting timing to original timings +5 (same for both channels) - BIOS failed to boot, reverted back to original settings.
  5. Tried various other settings like disabling fast boot on RAM -  FAILED each time. Reset BIOS back to defaults again.
  6. Tested new RAM in slots 2 & 4 - OK
  7. Tested new RAM in slots 1 & 3 - OK
  8. Tested each single stick of RAM individually in slot 1 - OK
  9. Tested a single stick of RAM in each slot - OK
  10. Tested original RAM in slots 1 & 2 - FAILED! (This surprised me)

I will need to test more configurations next time, as I've been testing for hours. I was surprised at my last test.

I tested each stick of RAM and each slot, and I'm convinced that each individual stick of RAM and each slot is not faulty.

There must be a software issue/firmware issue with the motherboard. I'm going to email Gigabyte about it...

 

Can anyone advise anything else I can do to diagnose/resolve the issue?


Edited by Xebozone, 14 October 2016 - 10:50 AM.


#8 RolandJS

RolandJS

  • Members
  • 4,525 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Austin TX metro area
  • Local time:02:39 AM

Posted 14 October 2016 - 03:59 PM

Xebozone, my hat's off to ya!  You're very thorough!  Obviously, the old and new sticks work just fine, something else is the problem.


"Take care of thy backups and thy restores shall take care of thee."  -- Ben Franklin revisited.

http://collegecafe.fr.yuku.com/forums/45/Computer-Technologies/

Backup, backup, backup! -- Lady Fitzgerald (w7forums)

Clone or Image often! Backup... -- RockE (WSL)


#9 Xebozone

Xebozone
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:03:39 PM

Posted 15 October 2016 - 06:27 AM

SOLVED!

Latest BIOS update fixed the issue (F6)

Downloaded it, put it on a USB flash drive formatted at FAT32... updated... memtest - all was well!

I thought I checked this... obviously I hadn't...

 

I had noticed before that Speccy wasn't able to report on much memory information before the update..
Now Speccy reports on each slot, how many slots free, etc, so this update must have fixed many issues.






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users