Answer the question
In order to leave comments, you need to log in
BSODs - I sin by memory, what to do?
UPD
noticed right now that the i7-4790 processor, which is calm by nature (without K), having a natural frequency of 3.6 GHz, operates in the region of 4.00 GHz (plus or minus). Something I don’t like it, I don’t see the reason why he accelerated so much. The browser, explorer and task manager are open. The latter shows 1% CPU usage. Nothing slows down and does not eat up processor time too much, really just a few small things with fractions of a percent.
What to do? Can something cause BSODs and overclock the processor like that?
---- original question ---
I bought the second bar and started. The error code is different every time. I read the Internet, installed WhoCrashed, it drives on the kernel and drivers, under each interpretation it is written "this is most likely a software glitch."
Checked hdd - found errors, corrected. Did not help. Updated all drivers. Did not help. Bios updated. Performed a clean installation of the axis - did not help. What kind of software glitch is this then?
I looked at the characteristics of the bars through cpu-z and aida64 - all the frequencies and timings are the same! Yes, strips from different manufacturers, because. The computer is 3 years old and I could not find a twin bar, but in all respects they are the same.
DIMM1: Crucial CT102464BA160B.C16 8GB DDR3-1600 DDR3 SDRAM
(11-11-11-28 @ 800 МГц) (10-10-10-27 @ 761 МГц) (9-9-9-24 @ 685 МГц) (8-8-8-22 @ 609 МГц) (7-7-7-19 @ 533 МГц) (6-6-6-16 @ 457 МГц)
(11-11-11-28 @ 800 МГц) (10-10-10-27 @ 761 МГц) (9-9-9-24 @ 685 МГц) (8-8-8-22 @ 609 МГц) (7-7-7-19 @ 533 МГц) (6-6-6-16 @ 457 МГц)
Answer the question
In order to leave comments, you need to log in
I had a similar glitch for a long time, when I decided to be smart and bought a distributed memory, I don’t remember the brand anymore, something in radiators with camouflage coloring (it was 2007). There were constant freezes, reboots, pearl sausage like in a sausage factory ... I
carefully studied the datasheet as a keepsake. Everything turned out to be simple - it required an increased supply voltage! I added voltage by 0.2V in the BIOS - and it has been working for ten years now (although it has been standing for half a year).
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question