A Walk Through Hades
-
jmaida wrote:
BTW I don't think Honey argues for the sake of it.
Honey doesn't even fully read my posts or bother to understand it before disagreeing. Honey can dish the heat but cannot take it. I have no time for that. I've asked for the bad apples to just leave me alone. They can't even do that. Just goes to show how little they actually read the posts they argue on. So, we're just gonna have to disagree on this buddy. :) And that's ok. I should just be able to block people that are nothing but trouble and arguments and go on with my life. But, I can't.
Jeremy Falcon
-
There is many ways to check, you can use the Windows Memory Test [Point 9 here](https://www.digitalcitizen.life/start-the-windows-memory-diagnostic/) , you can make your own bootable memtest86+ stick (download UEFI or MBR boot): [MemTest86 - Download now!](https://www.memtest86.com/download.htm), or use [Hiren's BootCD 15.2 Download | TechSpot](https://www.techspot.com/downloads/6966-hirens-bootcd.html). Maybe checking that the RAM runs on the specs in the motherboard helps, my Kingston Fury RAMs did not start with the last two AMD boards (Asus, Asrock), had to manually set the frequency (lucky me, nothing beyond that). It was auto-recognized as a much slower RAM with different timing.
The MemTest86 UEFI boot stick did the trick. I've isolated it to one pair of memory sticks, but can't sort it out beyond that. Sadly, since I've never had a failure before, I didn't keep the original packaging, so I can't return those two. Oh well, I suppose 32 GB will do for now. Thanks for the tip!
Will Rogers never met me.
-
The question was already answered, but yeah it's just me being silly _trying_ to keep this chat somewhat lighthearted. Not successfully though. :laugh:
Jeremy Falcon
Jeremy Falcon wrote:
it's just me being silly trying to keep this chat somewhat lighthearted
Sorry... to be effective has to be understood ;) ;P :-D
M.D.V. ;) If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about? Help me to understand what I'm saying, and I'll explain it better to you Rating helpful answers is nice, but saying thanks can be even nicer.
-
Understood. Not a problem. Your posts, especially the tech stuff, provides me useful info (as do many others on CP).
"A little time, a little trouble, your better day" Badfinger
Thanks man.
Jeremy Falcon
-
Jeremy Falcon wrote:
it's just me being silly trying to keep this chat somewhat lighthearted
Sorry... to be effective has to be understood ;) ;P :-D
M.D.V. ;) If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about? Help me to understand what I'm saying, and I'll explain it better to you Rating helpful answers is nice, but saying thanks can be even nicer.
I’m on mobile so can’t easily toss out an emoji response. So, I’ll just say…. Daaaaaayyyyyyyyuuuuuummmm lol
Jeremy Falcon
-
A good plan! I'll give it a try. I think I'll try easter-egging the RAM, as well, removing half of it at a time and rebooting. If there's a memory problem, that should help to isolate it.
Will Rogers never met me.
-
Yes, that was the first thing I tried. But now I'm wondering if I have too little capacity on the PSU. The recommended power from the vendor was 650W, I bought a 750W unit. But this processor and the video card can get greedy. Perhaps a 1000W would be a better choice.
Will Rogers never met me.
-
Yep, I've done that too. A memory tester might also help (memtestx86? whatever its name is...) If you don't mind, post a follow-up - I'd be genuinely curious to know if/how you got this resolved.
Having removed half the RAM, it now runs MemTest86 with no errors through multiple passes, and Windows 11 installed without a glitch. Well, almost. At the point where Setup wants to check for updates, it doesn't recognize the built in WiFi adapter on this MB. So I spent an hour or so rummaging around storage to find a 100' Cat5 cable to reach the router. Once Setup was done, an ASUS program kicked in and downloaded drivers for the MB. After that, the WiFi adapter was recognized and usable. So, all is good for now, and the excess RAM will be set aside.
Will Rogers never met me.
-
Having removed half the RAM, it now runs MemTest86 with no errors through multiple passes, and Windows 11 installed without a glitch. Well, almost. At the point where Setup wants to check for updates, it doesn't recognize the built in WiFi adapter on this MB. So I spent an hour or so rummaging around storage to find a 100' Cat5 cable to reach the router. Once Setup was done, an ASUS program kicked in and downloaded drivers for the MB. After that, the WiFi adapter was recognized and usable. So, all is good for now, and the excess RAM will be set aside.
Will Rogers never met me.
Interesting. Have you retried MemTest86 with *only* the suspect stick? Odds are, it'll confirm there's something wrong with it. Or maybe it's not identical to your other one(s), and they have problems running in sync. Either way - good news. At least you found the culprit.
-
Interesting. Have you retried MemTest86 with *only* the suspect stick? Odds are, it'll confirm there's something wrong with it. Or maybe it's not identical to your other one(s), and they have problems running in sync. Either way - good news. At least you found the culprit.
Interesting you should mention that. As part of the process, I tried booting with just one stick installed, despite the fact that I've always been told by the manual to install them in pairs. This manual showed installing one as an available option, so I went for it. The PC went nuts! Start, stop, LEDs go on then off... then on again. Crazy stuff, so I figured the manual was wrong, and traditional instructions to install them in pairs must be correct. But if that's no longer a requirement, I must have plugged in the one bad stick first! Oh well, I'll save them both of that set for the next build.
Will Rogers never met me.