> For the complete documentation index, see [llms.txt](https://dev.solid-run.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dev.solid-run.com/amd/r8000-r7000/sbc-platform/bedrock-r8000-technical-documentation/software-bedrock-r8000/howto-guides-bedrock-r8000-r7000/running-memtest86.md).

# Running Memtest86

To run Memtest86 you will first need to create a USB bootable drive.\
You can do that with tools like:

* Rufus on windows
* dd on Linux: `dd if=memtest86-usb.img of=/dev/<sda, sdb, sdc> bs=1M status=progress; sync`
  * Note sda, sdb … is the enumeration by your linux system, you can check it with `lsblk`

Plug the USB drive with Memtest86 to your Bedrock device and power it on.\
Wait for the system to boot to Memtest86 or select its boot option from BIOS.

Once booted, select the default scan (option 1):

![image-20250124-083135.png](https://1160211108-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCsmHoAD7oNPYQbYxSWHU%2Fuploads%2Fgit-blob-bf975a65004de970c6a40aaa29a159966bb42ef4%2Fimage-20250124-083135.png?alt=media)

Wait for Memtest86 to finish the test (this will take time) and see results.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://dev.solid-run.com/amd/r8000-r7000/sbc-platform/bedrock-r8000-technical-documentation/software-bedrock-r8000/howto-guides-bedrock-r8000-r7000/running-memtest86.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.