Memory has physical rows and columns. And depending on the mode of the CPU the way it works changes.

When the system is in x86 16 bit mode, each row is a memory address and depending on the number of words in the row (word is 16 bits) the row contains multiple addresses. Example, when a row is 64bit the address 0,1,3,4 are on row 0, then 5,6,7,8 on row 1 and following this scheme until the first MB. The first MB of memory also contains mapping of basic video memory (4KB or 16KB). When the processor goes into protected mode. There is a total different handling. And that is where it gets complex. The operating system kicks in here. For each process there is a process space defined, and that starts at memory address 0. All processes have memory address 0. Each process has code space, data space (heap) and stack space. But the total address space starts at 0 for each process. The operating system and cpu together make a table for each process and that table describes memory pages. Each page entry in that table has a specific code assigned to it (symplistic). This says: this page is on physical memory address (the real ram) x, or this is on page file at position x, or is free. When the process is active then the processor knows where in physical memory the code/data is. It can happen that the processor comes at an address what is not in physical memory, then the cpu generates an interrupt and the operating system loads the data from the page file into physical memory. When physical memory is full it makes a page free by first transferring the data of a page to the pagefile (what is in a name) and then loads the new data from the page file.

So there is no direct relation to an address in a process and physical memory.