Manufacturer Micro-Star International Co., Ltd.
Product Name GT70 2OC/2OD
Product MS-1763
Version REV:0.C
Processor Version Intel(R) Core(TM) i7-4700MQ CPU @ 2.40GHz
Processor Voltage 8ch - 1.2V
Device Locator ChannelA-DIMM0
memory bank 0 4096MB
Speed 1600MHz
Manufacturer Kingston
Serial Number
Asset Tag Number
Part Number ASU16D3LS1KBG/4G
Device Locator ChannelA-DIMM1
bank 1 4096 MB Speed 1600MHz Hynix/hyundai
Part Number HMT351S6CFR8A-PB
Memory Type 18h - Specification Reserved
Type Detail 0080h - Synchronous
Speed 1600MHz
Manufacturer Kingston
Serial Number
Asset Tag Number
Part Number ASU16D3LS1KBG/4G
Device Locator ChannelB-DIMM1
Bank Locator BANK 3
Memory Type 18h - Specification Reserved
Type Detail 0080h - Synchronous
Speed 1600MHz
Manufacturer Hynix/Hyundai
Serial Number
Asset Tag Number
Part Number HMT351S6CFR8A-PB
---------------------
memory specs: I am not sure of this as a cause but does your BIOS let you set the voltage and timings to each bank of memory?
you have two different sets of memory both at the same speed but they have different timing and voltage requirements. Some BIOS will not detect and set them correctly and you will get strange results. at a minimum you will want to confirm that they are paired together in the correct banks
on your motherboard (you will have to look in the manual for this)
the hynix chip runs on 1.35 volts (1.28- 1.45v) and
tCK= 1.25 ns
Cas Latency (tCK) = 11 ns
tRCD = 13.75 ns
tRas = 35ns
CL= 11ns
tRCD= 11ns
tRP= 11
the kingston memory
voltage 1.5V (1.425 to 1.575v)
9-9-9-27 at 1.65v
specs
http://www.kingston.com/datasheets/KHX1600C9D3_4G.pdf
if you can not set the timing, you will want to under clock the memory and see if your issue goes away.
-maybe power down, remove 2 of your matchine memory modules, power up into BIOS, reset your BIOS to defaults and reboot and see if the machine works better on one set of matched memory.
----------------------
notes:
old drivers:
btath_hcrp.sys Tue Dec 18 01:54:54 2012 Atheros Bluetooth Driver(update)
e22w8x64.sys Mon Dec 03 07:42:37 2012 update because bugcheck issues (killer network driver) check with msi or find the killergaming support website.
NTIOLib_X64.sys Thu Oct 25 03:27:58 2012 MSI AfterBurner driver (remove)
-------------------
I think your issue is caused by one of the above drivers corrupting kernel memory structure resulting in a driver not completing a interrupt routine in the allocated time and causing a bugcheck. I would focus on updating the drivers or removing them for testing to see if you can find out which one is the cause. (all three have known issues)
Facebook
Twitter
Instagram