@W1zzard Will you be adding the ability to temporarily change memory timings and test them to this?:)

W1zzardYupyup :D

You true magician then! Thanks for this app.

Checked it out for 10 min run. 0 errors on lpx3000 cas15@1.27V. Nice ware. Good programming. Keeper.

DeathtoGnomes@W1zzard Will you be adding the ability to temporarily change memory timings and test them to this?:)

No, not possible on most hardware without reboot

Many congrats to @W1zzard for his effort in making this work so well in windows. A tool that every PC enthusiast was missing, as RAM testing was very slow and painful from DOS. Thanks again!

ima check this out when i get home :lovetpu:

W1zzardYupyup :D

Im in love.

W1zzardYupyup :D

YOU'RE A F3CKING INTERNET GOD!

Very good :D
A 32-bit version would be nice too :)

EDIT: I tried it on my desktop on default settings (maximum memory allocation) and my computer almost crashed, 100% memory usage, SSD paging like a crazy and the screen flashed black (because DWM crashed)
I will try lowering the memory setting
EDIT2: Now I get Memory locking failed (might be reserved by other apps/kernel)

Derek12Very good :D
But a 32-bit version would be nice too :)

EDIT: I run it on my desktop and my computer almost crashed, 100% memory usage, SSD paging like a crazy and the screen flashed black (because DWM crashed)

32-bit version isn't possible because it wouldn't be able to allocate enough memory for testing. Everybody uses 64-bit nowadays.

"Maximum" might slow down your system indeed, you did get the message about your system "appearing hung", right ? Windows 10 or Windows 7?

W1zzard32-bit version isn't possibly because it wouldn't be able to allocate enough memory for testing. Everybody uses 64-bit nowadays.

"Maximum" might slow down your system indeed, you did get the message about your system "appearing hung", right ? Windows 10 or Windows 7?

Windows 10.
There are currently lots of 32-bit systems out there (including my recently acquired 2-in-1) but yes, this tool is more focused to enthusiasts who have 64-bit systems
I didn't get any message but yes, the desktop started to lag badly and the screen turned black for a while, then memtest closed, and a event about DWM crashing appeared :(
I finally get it running by allocating 8 GB and after a few tries with the locking error. That means the rest of the RAM (4 GB) is not being tested right?


Module 0:
DDR3, 8192 MB, 64-bit, 1333 MHz
DIMM_A1 BANK 0 Kingston 99U5471-057.A00LF
Module 1:
DDR3, 4096 MB, 64-bit, 1333 MHz
DIMM_B1 BANK 2 Kingston 99U5474-016.A00LF

0.000: Detecting usable memory (12232 MB theoretical max)...
12.125: 11648 MB Test starting on 4 CPUs...
12.141: Allocating memory...
20.656: Starting loop 1
20.672: Stuck Address Test...
26.625: Random Data Test...
32.687: Move Data Test...
35.094: Bitpattern Test...
59.656: Test finished with no errors detected
0.000: Detecting usable memory (12232 MB theoretical max)...
2.703: Test finished with no errors detected
0.000: 8192 MB Test starting on 4 CPUs...
0.015: Allocating memory...
3.265: Memory locking failed (might be reserved by other apps/kernel)
3.640: Test finished with no errors detected
0.000: 8192 MB Test starting on 4 CPUs...
0.000: Allocating memory...
7.391: Memory locking failed (might be reserved by other apps/kernel)
7.906: Test finished with no errors detected
0.000: 8192 MB Test starting on 4 CPUs...
0.000: Allocating memory...
6.547: Memory locking failed (might be reserved by other apps/kernel)
7.094: Test finished with no errors detected
0.000: 8192 MB Test starting on 4 CPUs...
0.000: Allocating memory...
7.000: Starting loop 1
7.000: Stuck Address Test...
11.078: Random Data Test...
15.219: Move Data Test...
16.672: Bitpattern Test...
140.953: Starting loop 2
140.953: Stuck Address Test...
144.984: Random Data Test...
149.078: Move Data Test...
150.531: Bitpattern Test...
274.766: Starting loop 3
274.766: Stuck Address Test...
278.875: Random Data Test...
285.094: Move Data Test...
286.547: Bitpattern Test...
410.609: Starting loop 4
410.609: Stuck Address Test...
414.734: Random Data Test...
418.844: Move Data Test...
420.312: Bitpattern Test...
453.641: Test finished with no errors detected

Derek12That means the rest of the RAM (4 GB) is not being tested right?

It is not a linear allocation. The allocated 8 GB are not contiguous and tested memory pages can be located in any ram stick in your system.

The 11648 MB test is the one that crashed DWM? What if you select the next smaller test size?

W1zzardYupyup :D

I am very excited about this announcement and will definitely put this into my USB toolkit at work.

Thank you so much.

Derek12Very good :D
A 32-bit version would be nice too :)

EDIT: I tried it on my desktop on default settings (maximum memory allocation) and my computer almost crashed, 100% memory usage, SSD paging like a crazy and the screen flashed black (because DWM crashed)
I will try lowering the memory setting
EDIT2: Now I get Memory locking failed (might be reserved by other apps/kernel)

Turn off secure boot.

Memory locking failed (might be reserved by other apps/kernel)

I got this but just waited a second and tried again and it was fine.

OctopussLooks like complicated software. Do you code stuff for living then? I don't suppose TPU can generate enough money to live off?

He pays me too, as well as other more productive members of society.

Rosie ScenarioTurn off secure boot.

Doubt that has anything to do with this.

Awesome - thanks W1zzard! :D

Rosie ScenarioTurn off secure boot.

I don't think Secure boot has any effect.

The locking error happens when you ask it to test more memory than Windows thinks it can free up for testing.

I already have a purchased hci-memtest deluxe (that's the non memtest86+ version, the one running from windows), so will be comparing the two.

I asked it in the original thread, but received no reply, so let me try here again :)
Do number of cores have any bearing on the test process or results thereof? For example hci advises a minimum of 16 tests running parallel for me (one per core), RAM equally divided between them.

Rosie ScenarioTurn off secure boot.

I have it turn off :D

W1zzardIt is not a linear allocation. The allocated 8 GB are not contiguous and tested memory pages can be located in any ram stick in your system.

The 11648 MB test is the one that crashed DWM? What if you select the next smaller test size?

Many thanks

Yes, it is when DWM crashed! anyway seemed to happen only once
The next smaller size (11264) worked fine :)

Ooh a new toy, can't wait to try it

Thanks W1zz

AenraDo number of cores have any bearing on the test process or results thereof?

it's just faster afaik

Awesome program! :clap:

FrickThat right there is about the only legit reason to stay on Windows 7.

What is it that Win 7 task manager can do and Win 10 version cannot?
I mean, OK, you can't view the CPU and memory graphs at the same page... is that it?

Good tool. Here are some of my suggestions.

1. Only used ~30GB RAM for my 128GB RAM. I hoped it can test close to the limit at least.
2. Reports RAM speed at 2933 while they run at 3000
3. Can't run with Windows task manager open

I'd suspected my memory to be slightly unstable @ 10-12-12-31. So I've been running it @ 10-12-12-32 without issues. MemTest64 quickly and efficiently confirmed the tighter tRAS timing causes errors. I thought so. But now I know so.