Man of Honour
- Joined
- 23 Mar 2011
- Posts
- 18,455
- Location
- West Side
What made you try memtest 64 is there much diffrence between the two ?
PC Crashing
- Thread starter Savan_P
- Start date
memtest64 runs inside the windows environment instead of the DOS environment that Memtest86 uses.
The main reason I had given MT64 a try was because i could not replicate the issues without windows running and it was slowly driving me insane not being to get a result. knowing that my BSOD results were pointing toward the RAM being the issue, i had already checked over the board and tested another set of RAM on the setup (sacrificing my wife's machine in the process). This helped to eliminate the board being an issue and i had already checked it over visually to ensure nothing had burnt out.
Taking a leaf out of Sherlock's book "When you have eliminated the impossible, whatever remains, however improbable, must be the truth." This left me with only on possibility. the DOS run memory testing was not detecting my results.
Hence the reason for me giving it a go, I ,honestly, had nothing to loose at that point.
The main reason I had given MT64 a try was because i could not replicate the issues without windows running and it was slowly driving me insane not being to get a result. knowing that my BSOD results were pointing toward the RAM being the issue, i had already checked over the board and tested another set of RAM on the setup (sacrificing my wife's machine in the process). This helped to eliminate the board being an issue and i had already checked it over visually to ensure nothing had burnt out.
Taking a leaf out of Sherlock's book "When you have eliminated the impossible, whatever remains, however improbable, must be the truth." This left me with only on possibility. the DOS run memory testing was not detecting my results.
Hence the reason for me giving it a go, I ,honestly, had nothing to loose at that point.
Saw your post and gave it a try. had the same results with OCCT memtest and memtest 64. on another ryzen machine.
One of the 2 sticks is faulty. All Memory sockets work and the fault follows the bad stick around, For other on a fault finding mission, if the fault sticks to the same mem socket you could might need to try a new CPU/main board as the issue could be with the memory controller on the CPU or bad connections on the motherboard. .
Thanks Jameswa23
One of the 2 sticks is faulty. All Memory sockets work and the fault follows the bad stick around, For other on a fault finding mission, if the fault sticks to the same mem socket you could might need to try a new CPU/main board as the issue could be with the memory controller on the CPU or bad connections on the motherboard. .
Thanks Jameswa23
Not being funny but if you have not memtest86 how do you know it is not ram issue?
also you have had a number of BSOD, and you have persisted in using the system regardless without getting to the bottom of the cause. I suspect your windows is now corrupt. You may pass memtest86 but your OS has damaged files or drivers. I would strongly recommend a fresh install to test the stability of the system in order to isolate any hardware issues.
also you have had a number of BSOD, and you have persisted in using the system regardless without getting to the bottom of the cause. I suspect your windows is now corrupt. You may pass memtest86 but your OS has damaged files or drivers. I would strongly recommend a fresh install to test the stability of the system in order to isolate any hardware issues.
Ragnarock, Glad you had some success with this process too.
pc-guy, I agree and this is why I had preformed multiple fresh boots to check if I had found the error and corrected it or if it still persisted to be an issue. It has taken me over 2 years to locate the bad module in my machine. along the way I found a failing HDD and a failing graphics card which were all mouthing to the BSOD's I was receiving. I started with over 20 different BSOD messages and finally worked my way down to one. I found that by running a certain game (Ark Survival Evolved) I would get my machine to crash within 30 minutes if the bad RAM module was installed which gave me the chance to be able to replicate the issue over and over again. Armed with this information and the BSOD information it was a further push to try and find the issue which in turn identified other issues that I had no idea where there. I am lucky to have lots of computer spare to be able to test various components and a sister machine to mine that has the same specs to compare results. Granted at one point I was concerned that I would be looking at needing to replace the motherboard and possibly the processor but in any fault finding process you start with analysing the cheapest items and work your way up to the more expensive ones.
in my case I feel I got lucky, if I had to replace the processor of Motherboard i may as well upgrade to a newer chipset as mine (LGA1155), it is very hard to find a new motherboard to give great performance and stay with the same chip set. this in turn would have meant I needed to throw out my DDR3 and upgrade to DDR4... very expensive if you have to replace the lot at once.
pc-guy, I agree and this is why I had preformed multiple fresh boots to check if I had found the error and corrected it or if it still persisted to be an issue. It has taken me over 2 years to locate the bad module in my machine. along the way I found a failing HDD and a failing graphics card which were all mouthing to the BSOD's I was receiving. I started with over 20 different BSOD messages and finally worked my way down to one. I found that by running a certain game (Ark Survival Evolved) I would get my machine to crash within 30 minutes if the bad RAM module was installed which gave me the chance to be able to replicate the issue over and over again. Armed with this information and the BSOD information it was a further push to try and find the issue which in turn identified other issues that I had no idea where there. I am lucky to have lots of computer spare to be able to test various components and a sister machine to mine that has the same specs to compare results. Granted at one point I was concerned that I would be looking at needing to replace the motherboard and possibly the processor but in any fault finding process you start with analysing the cheapest items and work your way up to the more expensive ones.
in my case I feel I got lucky, if I had to replace the processor of Motherboard i may as well upgrade to a newer chipset as mine (LGA1155), it is very hard to find a new motherboard to give great performance and stay with the same chip set. this in turn would have meant I needed to throw out my DDR3 and upgrade to DDR4... very expensive if you have to replace the lot at once.
That's the beauty of the running SFC /scannow from the command line. have occasionally had to re-install apps but haven't broken any windows system files yet.
Also dual or quad channel kits are great for diagnostics too. on my dual channel kit, I ran the memory on 1 stick . swapped them around and one clearly throws stuck address and other errors errors at the same address on the same test runs. the other come's back fine. you can swap dimm sockets and the errors only happen with the dodgy stick is in the machine. memtest64 ( and occt for that matter but with less detail ) throws the error almost right away or within the stuck address test Which is about within 2 or 3 minutes on my 32Gb kit, and in my case memtest86 pass half a day of testing 5-6 hours of testing.
I was fortunate to be able to borrow a similar slower kit from work. while waiting for an RMA. No errors. I didn't need the other kit to find the faulty ram module though.
Last edited:
