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.
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:
An exception happened while executing a system service routine.
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.
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.
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.
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
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.