View Single Post
  #3  
Old 08-29-2016, 15:46
Kerlingen Kerlingen is offline
VIP
 
Join Date: Feb 2011
Posts: 324
Rept. Given: 0
Rept. Rcvd 276 Times in 98 Posts
Thanks Given: 0
Thanks Rcvd at 308 Times in 95 Posts
Kerlingen Reputation: 200-299 Kerlingen Reputation: 200-299 Kerlingen Reputation: 200-299
I read the bcdedit documentation and hoped to find something there, but I only found truncating memory and burning memory settings. I hate it when something from Microsoft has useful features and they don't care about documenting them.

The corrupted RAM module is at bank 4. I could put it even further away, but I then I would need to run memtest again to find out the new location, so I'm sticking with this where I already know the bad memory address.

"bcdedit /set badmemorylist" will not work, the correct syntax would be "bcdedit /set {badmemory} badmemorylist".

So now I'm hoping to see no more corrupted files or random crashes in the future.
Reply With Quote
The Following 2 Users Say Thank You to Kerlingen For This Useful Post:
niculaita (08-30-2016), tonyweb (08-31-2016)