New
#61
While working up the hardware: at some time see if you can post a zip that is not a short cut to the zip but a zip of a 1 - 2 GB memory dump.
While working up the hardware: at some time see if you can post a zip that is not a short cut to the zip but a zip of a 1 - 2 GB memory dump.
I just reset bios again pinned on cmos and pulled battery and booted up all factory didn't enter bios settings so imagined reset total
resetting memory dump to automatic memory dump
is my settings correct?
sending both log collector and zip folder
trying one more step before replacing CPU or MB I moved (Evo 960 M.2 that is what I use boot up with windows installed) away from CPU into lowest slot on MB below it may have been getting hot, thanks for all the help
I would like to have a reply about this option thanks
Overheating is a common cause of BSOD events. If you suspect drive temperatures you can monitor your system for this using HWmonitor and there may be a disk analysis tool for the EVO drive that you can download.
My problem is solved I changed out my memory sticks been running 7 days now and not any blue screens.
Running my system @4.7 CPU and DDR4 3200MHz now and did run @4.9GHz CPU no problems.
My Ram running was Corsair DDR4 3000MHz I don't know why it failed was listed as compatible on my Z370 Aorus Gaming 5 motherboard Now running PNY 3200MHz 16GB and PNY ram is not listed on compatible list I asked at BestBuy in Geeks Squad the gentleman said it should work, so far it has worked.
Thanks for trying to help solve this problem
Speccy below
Type DDR4
Size 16384 MBytes
Channels # Dual
DRAM Frequency 1600.1 MHz
CAS# Latency (CL) 16 clocks
RAS# to CAS# Delay (tRCD) 18 clocks
RAS# Precharge (tRP) 18 clocks
Cycle Time (tRAS) 36 clocks
Command Rate (CR) 2T
Physical Memory
Memory Usage 24 %
Total Physical 16 GB
Available Physical 12 GB
Total Virtual 18 GB
Available Virtual 12 GB
SPD
Number Of SPD Modules 2
Last edited by Howiewowie; 08 Aug 2018 at 22:27. Reason: looked at calender wrong
Glad to hear that it is fixed, thanks for the feedback. Good to know these internal timer errors can be traced back to faulty RAM.