F5F Stay Refreshed Hardware Desktop It should work, since Linux likely includes it, which Windows would also have...

It should work, since Linux likely includes it, which Windows would also have...

It should work, since Linux likely includes it, which Windows would also have...

Pages (3): 1 2 3 Next
B
Bonnibel
Posting Freak
794
09-02-2016, 07:50 AM
#1
Processor - i5-6500 GPU - asus 750ti 2gb OC RAM - 16gb DDR4 2133MHz Motherboard - asus h170pro (excluding USB 3.1) HDD - 2TB WD SMR 5400rpm 2TB WD SMR 7200rpm PSU - MWE BRONZE V2 450W 230V Solution: I faced random freezes and shutdowns. Initially, I suspected the hard drive, but checked CPU, GPU, PSU—none resolved the problem. Switching to Linux Mint helped reduce crashes. (It was Windows that caused issues.) After observing, RAM cache would fill up above 5 minutes, then cause freezes or shutdowns even after hours. Memory usage in cache far exceeded actual usage. For example, 15GB cache with only 2GB active. I tried: `sudo echo 3 | sudo tee /proc/sys/vm/drop_caches`, but it was temporary and needed repeated. Eventually, I used the command: `sudo watch -n 180`. This worked consistently without crashes so far. **For Windows 10 Pro:** Is there a similar method to clear RAM cache? Any guidance would be appreciated. I’m considering SSDs, but storage cost is a concern. Please share any steps you’ve tried.**
B
Bonnibel
09-02-2016, 07:50 AM #1

Processor - i5-6500 GPU - asus 750ti 2gb OC RAM - 16gb DDR4 2133MHz Motherboard - asus h170pro (excluding USB 3.1) HDD - 2TB WD SMR 5400rpm 2TB WD SMR 7200rpm PSU - MWE BRONZE V2 450W 230V Solution: I faced random freezes and shutdowns. Initially, I suspected the hard drive, but checked CPU, GPU, PSU—none resolved the problem. Switching to Linux Mint helped reduce crashes. (It was Windows that caused issues.) After observing, RAM cache would fill up above 5 minutes, then cause freezes or shutdowns even after hours. Memory usage in cache far exceeded actual usage. For example, 15GB cache with only 2GB active. I tried: `sudo echo 3 | sudo tee /proc/sys/vm/drop_caches`, but it was temporary and needed repeated. Eventually, I used the command: `sudo watch -n 180`. This worked consistently without crashes so far. **For Windows 10 Pro:** Is there a similar method to clear RAM cache? Any guidance would be appreciated. I’m considering SSDs, but storage cost is a concern. Please share any steps you’ve tried.**

S
SnailNugget
Junior Member
40
09-05-2016, 03:01 AM
#2
I assessed the RAM sticks as acceptable since it would be better not to assume "I ran Memtest." Typically, a random crash in Windows without a real impact on performance usually relates to memory issues. This often means the memory is reaching its limit and can't recover, either because of a faulty stick (A) or a problem with the motherboard's memory handling (B). A simple test would be to run one stick at a time in the system and observe if it stabilizes. Using a dedicated memory test tool will likely produce a "we couldn't reproduce the issue" response, which isn't very informative.
S
SnailNugget
09-05-2016, 03:01 AM #2

I assessed the RAM sticks as acceptable since it would be better not to assume "I ran Memtest." Typically, a random crash in Windows without a real impact on performance usually relates to memory issues. This often means the memory is reaching its limit and can't recover, either because of a faulty stick (A) or a problem with the motherboard's memory handling (B). A simple test would be to run one stick at a time in the system and observe if it stabilizes. Using a dedicated memory test tool will likely produce a "we couldn't reproduce the issue" response, which isn't very informative.

X
xXSuperNovaXx
Posting Freak
811
09-05-2016, 05:21 AM
#3
Don’t let it sit for long periods trying to thaw—this device shouldn’t freeze at all. If it takes more than a couple of seconds to start thawing, it’s likely damaged. Waiting an hour and a half just to see something happen isn’t practical.
X
xXSuperNovaXx
09-05-2016, 05:21 AM #3

Don’t let it sit for long periods trying to thaw—this device shouldn’t freeze at all. If it takes more than a couple of seconds to start thawing, it’s likely damaged. Waiting an hour and a half just to see something happen isn’t practical.

T
TooFarAway
Member
63
09-05-2016, 07:28 AM
#4
It seems you're asking about a persistent issue you've been dealing with since early 2018. The problem might be related to hardware limitations or software glitches. There doesn't appear to be a direct solution or command to fix it, but you can try reducing variables or checking for updates. Let me know if you'd like more guidance!
T
TooFarAway
09-05-2016, 07:28 AM #4

It seems you're asking about a persistent issue you've been dealing with since early 2018. The problem might be related to hardware limitations or software glitches. There doesn't appear to be a direct solution or command to fix it, but you can try reducing variables or checking for updates. Let me know if you'd like more guidance!

L
LPmitBaumi
Member
66
09-06-2016, 04:33 PM
#5
AMD chips using mostly Hynix memory modules face significant issues. Testing with hardware, two motherboards and four processors each had four memory sets. Corsair Vengeance 3000mhz performed poorly, acting as garbage. Replacing them with a good kit—Micron E-Die or Samsung B-die—resolved the problem completely. The memory would enter idle mode even when reading an article and never return. To address this, disable C-states and memory power down mode. System shutdowns (restarts) on AMD products triggering error event 41 are usually fixed by returning the processor to the manufacturer.
L
LPmitBaumi
09-06-2016, 04:33 PM #5

AMD chips using mostly Hynix memory modules face significant issues. Testing with hardware, two motherboards and four processors each had four memory sets. Corsair Vengeance 3000mhz performed poorly, acting as garbage. Replacing them with a good kit—Micron E-Die or Samsung B-die—resolved the problem completely. The memory would enter idle mode even when reading an article and never return. To address this, disable C-states and memory power down mode. System shutdowns (restarts) on AMD products triggering error event 41 are usually fixed by returning the processor to the manufacturer.

S
Stocked
Junior Member
6
09-06-2016, 05:04 PM
#6
That's helpful. I'm sure you meant to reference the Intel i5-6500 processor.
S
Stocked
09-06-2016, 05:04 PM #6

That's helpful. I'm sure you meant to reference the Intel i5-6500 processor.

A
Arazon
Member
177
09-06-2016, 11:33 PM
#7
It could fail if your setup isn’t right during the boost, but you might not realize it unless you check the specs and settings carefully.
A
Arazon
09-06-2016, 11:33 PM #7

It could fail if your setup isn’t right during the boost, but you might not realize it unless you check the specs and settings carefully.

M
mentality_man
Member
123
09-07-2016, 03:08 AM
#8
Yes, I included an extra stick while leaving the original one in place.
M
mentality_man
09-07-2016, 03:08 AM #8

Yes, I included an extra stick while leaving the original one in place.

J
JetFighter01
Junior Member
20
09-09-2016, 12:21 AM
#9
Ah i see. Hm... Memory speed is 2133mhz. I don't fiddle with it. Hm let me add my mobo description too.
J
JetFighter01
09-09-2016, 12:21 AM #9

Ah i see. Hm... Memory speed is 2133mhz. I don't fiddle with it. Hm let me add my mobo description too.

A
anakindaur
Senior Member
576
09-09-2016, 02:02 PM
#10
Memory details: Part number not specified, but considering model Cpu-z, please capture the SPD tab. W10 or W11?
A
anakindaur
09-09-2016, 02:02 PM #10

Memory details: Part number not specified, but considering model Cpu-z, please capture the SPD tab. W10 or W11?

Pages (3): 1 2 3 Next