|
Post by bwims on Feb 21, 2019 10:46:14 GMT
Hello, could someone please point me at where there is information pertaining to the JEDEC numbers next to the DIMM banks? Also could you comment on my DIMM arrangement in the attached screenshot? It seems to work fine, but I think my system is susceptible to software with memory leakage, which is why I am looking at my memory specs. I notice that Chrome swallows huge amounts of Ram over time. I have started getting "unexpected shutdowns" every few days, unless I shut down all my chrome instances every night. That's why I'm wondering if there is a problem in my ram that only manifests when it gets full. Thanks in advance! Brian Attachments:
|
|
|
Post by siv on Feb 21, 2019 11:19:14 GMT
I suspect the issue is Chrome leaking memory rather than the DIMMs. Use Windows task manager to look at the Chrome memory usage, does it keep increasing over time?
What does SIV report as the System Physical Memory + System Paging File usage after Chrome has been active for a while and what happens to the values when you exit Chrome.
Windows 10 RS2 is rather old and you should consider updating to RS5. I am also wondering how old a version of Chrome you have and if the memory leak has been fixed in a later version.
In general terms when programs fail to allocate memory they tend do unexpected/undesirable things, this is also true of operating systems which may well crash/shutdown the system. Are there any dumps in C:\Windows\Minidumps\?
The DDR3 standard is spams://www.jedec.org/sites/default/files/docs/JESD79-3F.pdf, but I suspect you will find it "heavy going".
|
|
|
Post by bwims on Feb 22, 2019 12:41:32 GMT
I suspect the issue is Chrome leaking memory rather than the DIMMs. Use Windows task manager to look at the Chrome memory usage, does it keep increasing over time? What does SIV report as the System Physical Memory + System Paging File usage after Chrome has been active for a while and what happens to the values when you exit Chrome. Windows 10 RS2 is rather old and you should consider updating to RS5. I am also wondering how old a version of Chrome you have and if the memory leak has been fixed in a later version. In general terms when programs fail to allocate memory they tend do unexpected/undesirable things, this is also true of operating systems which may well crash/shutdown the system. Are there any dumps in C:\Windows\Minidumps\? The DDR3 standard is spams://www.jedec.org/sites/default/files/docs/JESD79-3F.pdf, but I suspect you will find it "heavy going". Many thanks for replying! I suspect the same. In Task Manager, usage goes up and down, but I see the System Page File increasing steadily. Right now, after Chrome has been active for a couple of hours, System Physical Memory + System Paging File usage = 7.4Gb and 11.97Gb respectively; after exiting, System Physical Memory + System Paging File usage = 4.28Gb and 6.5Gb respectively. After restarting Chrome, System Physical Memory + System Paging File usage = 6.26Gb and 8.8Gb respectively, though this figures are slowly ticking up. I have been delaying upgrading windows 10 because the "unexpected shutdowns" increased in frequency after the last patches that I installed and I rolled back thinking I might try to find out the reason for them first. These are not BSODs. Therefore no dump file is created. I do not think I have ever had a BSOD, because there are no .DMP files of either kind (normal or minidump) on my system, which is configured for automatic dumps. My suspicion is that the pagefile increases until the 480Gb of space on my disk is used up, though I have not checked this. What is perplexing is that good operating systems should at least crash with a dump if an exception occurs, though possibly if the disk is full there is no space to create a dump file? Also, I have not upgraded Chrome past V66 for two reasons: aesthetic, and more importantly, performance. The trivial reason is that I cannot stand the look and feel of V70 onwards, but from V67 Google put some code in to defeat the Meltdown/Spectre attack vectors which takes even _more_ memory. I experienced a huge performance impact. Given the huge difficulties I had keeping to V66, I will rely on the unattractiveness to virus writers of attacking via the now-protected Chrome! I was hoping that this problem might be faulty memory, but having chatted with you, my guess is that a memory fault _would_ produce a BSOD, whereas I can see a possiblity of it being a disk full through pagefile problem. Do you agree? Many thanks Brian
|
|
|
Post by siv on Feb 22, 2019 17:18:34 GMT
I would be inclined to manually set the page file size rather than let the system control it.
Without knowing why the system restarts I can't even guess what to do.
|
|