prsyahmi / badmemory Goto Github PK

Whenever I try to add the addresses 1048c3018 - 10c8c4ff8 (4168.7 - 4296.7) I keep getting [FAIL] as a result (MemTest86+ gave me 001048c3018 & 0010c8c4ff8). I have installed the signed driver.

Any ideas?

Hello!

Maybe a little off-topic but please help me the calculate the correct addresses.

I have 3 bad 'sectors' according to memtest86:
25EDDF830
25F5A1768
A23C2440

How these should be converted to be placed in bcdedit {Badmemory} ?
Only they should be divided by 1000 ?

With your driver it's easy to disable 3 addresses?

Hello,
I installed your driver because I had problems on one memory location.
After the restart, I launched RAMmap to check that the range was used by the driver. I saw that the physical pages were marked as system PTE in RAMmap. Is this normal with the call to MmAllocateContiguousMemorySpecifyCache () in your driver.

Hi,
I have 64gb of installed RAM and used memtest86 to detect the errors. It found over 10,000 before ending prematurely due to the number of errors. Assuming I can get it to report all the bad addresses, is there a limit or other issue to using BadMemory with so many bad addresses?

If the driver fails to reserve the broken RAM, will it give some kind of notification, or do I have to open BadMemoryManager every time I turn on my computer to check?

I really wanted to run it, but it doesn't work.

Is it possible to include this driver to Windows 10 Installer to avoid faulty installation?

I know of a great many GF cards with artifacts after long service.
If one could disable the bad RAM addresses on these cards, as you do for sys RAM, they could all be put back into service.

As you wrote GpuRamDrive (thx!); I assume you know how to address the VRAM! :D
I am unaware of a memtest like app for testing and getting the addresses of bad VRAM however?

On windows 10, after installing the driver and restart, the computer goes into repair mode loop saying:
"Boot critical file c:\windows\system32\drivers\badmemory.sys is corrupt.

Repair action: File repair
Result: Failed. Error code = 0x57
Time taken = 1422 ms"
Please advise.

It doesn't work (FAIL) so I want to uninstall it.

The KB5004945 update prevents BadMemory from taking the memory.
According to Autoruns64 the driver IS loaded, however the BadMemoryManager shows all ranges as [FAILED].
RamMap shows the memory use as Paged Pool.
Uninstalling the update enables it back.

Which kind of limitation in bootmanager would lead to STATUS_BUFFER_TOO_SMALL error?

I mean, it's not clear how one would trigger the issue.
EDIT: specifying too many pages perhaps?

Could you list the versions of Windows with which it is compatible?

In particular, it can't work on Windows XP, right?

I tried your driver and it does not appear to be working correctly. It is loaded according to systeminfo, but it is not loaded at the memory address that I specified in the badmemory application.

Here are the questions I had and the steps I tried.

1. Do you need to remove existing badmemory instance? i.e. if the same memory address that the driver asks for is in the {badmemory} list will it crash. ---- I removed the badmemory object before I started
2. Need to run BadMemoryManager as admin (goes without saying, but if you forget it does not give you an error). ----- I got this running but I was not able to confirm as the registry location is locked and I cannot access it to check if it registered with the driver or not.

3.  When the memory is locked it shows up as locked by shell32.dll  is this correct?   ----- This does not appear to be correct as it loaded something else on the next boot
   

Do you have time to look into this driver again? It would be great timing now that Microsoft has broken the BCDedit method.