Hi all, trying to determine what the cause of these issues during load.
Every time I try to play a game (nothing intensive) I have huge lag as shown in video, this includes multiple crashes and even some BSOD’s or full freezing. Has been getting progressively worse, have replaced my ram, tried all different ram slots and combinations. Only managing to run this (barely at moment) using 1x 16GB stick in A1 Slot (A2 is reccomended for single but wont work)
BUILD (2017)
- CPU: i7 6770k (not OC)
- GPU: ASUS GTX1080 founders (not OC)
- MB: ASUS Maximus VIII Formula ROG
- RAM: new Corsair Vengeance LPX DDR4 2x 16GB (CMK32GX4M2D3600C18)(previously Corsair Dominator Platinum 3200 CMD16GX4M4B3200C16-ROG after issues started as the store said it was faulty)
- Cooler: Corsair H100i (temps are fine, fan fine - replaced few years ago)
- PSU: EVGA 850G2 (seems fine)
- Storage
- SSD primary (185gb / 475gb free) with OS
- HDD secondary (909gb / 1.81tb free)
- SSD secondary (402 / 931gb free)
RAM / MB
Memtest seems to show multiple fails. But this was done on this new 3600 MHz ram not the older ram. Not really sure how to read Memtest results; https://i.ibb.co/1mwYK4s/Mem-Test86-Report-20230921.jpg
Some pointed to the ram slots / motherboard? Unless it’s ram slots themselves? Cant see any physical damage and have cleaned them out well. Thermal wise, temps aren’t high on cooler or GPU / CPU… ram gets warm to touch after switching out slots recently and testing but never hot.
MHz - worth noting that the new ram is not on the Asus QVL list for ram. Corsair Vengeance LPX DDR4 - 2 x 16 GB (3600MHz). Apparently Corsair Dominator Platinums arent on QVL list either, although I believe the BIOS was updated to allow up to 4000MHz. So this prob not a cause. Task manager is showing 3600 MHz as current speed.
18/11 - tried second ram in A4 - seemed to be running ok, then after a reset it turned to shit again this morning… what the hell is going on…
GPU
Have tested with GPU removed and exactly same issue
ORIGIN
Happened mid game a while back playing Hell Let Loose, it randomly shit froze, sound buzz, shat itself, BSOD and restart. Has been an issue ever since then.
OTHER
- DX12
- Bios: up to date at current v.3801 (updated years ago)
- XMP: switching off doesnt seem to make a diff
- Voltage: Have tried boosting to 1.4 and 1.35 and now set to auto
- Page File: 12,872 MB / 26,708 MB (just set it based on 16gb single stick)
- CHKDSK: https://ibb.co/yWG6y55
- SFC /Scannow: Can’t seem to get it running?
- MEMTEST: https://i.ibb.co/1mwYK4s/Mem-Test86-Report-20230921.jpg
You must log in or register to comment.
Hmm… Don’t think there’s too much hope here, could be the CPU, could also be the PSU, I’m wondering if there’s something wrong about these EVGA G2/G3s where this is a reoccurring thing, I could be wrong.
It’s almost better starting from scratch with newer components, but let’s try a few things.
Just to rule out faulty disks, disconnect everything, run a new disk /w a brand new OS and stress test that. See if that relieves any HW issues.
Not really sure how to read Memtest results; https://i.ibb.co/1mwYK4s/Mem-Test86-Report-20230921.jpg
You can’t have any errors. Any errors means an issue with RAM. 3200MT/s is sometimes a bit fast for Skylake. It often works, but you can see memory issues like this. The highest officially supported speed when using a Skylake CPU is 2666MT/s. (MT/s = the advertised MHz. MHz is the wrong term with DDR RAM, MT/s the correct one).
-MINIDUMP Analysis: https://www.mediafire.com/file/d9uffiilimzcudf/analysis_minidump.txt/file
We don’t want text files, we want the dump file. Just pressing !analyze isn’t enough, and what you do depends on what you see. And I see that you were running Driver Verifier. Never run Driver Verifier. It’s not a tool for troubleshooting BSODs. I know there are lots of articles that tell you to do so and even the Microsoft forums tell you to do so, but it’s terrible advice. 99,9% of the time the result from a Driver Verifier crash will be completely useless.
Have you had any BSODs when not running Driver Verifier?
Updated, I believe this is solved