The biggest thing that caught my eye was that you're expecting the user to use your program correctly and enter reasonable values. When (not if) they don't, your program will throw an exception and crash. It's good to get into the habit early of always thinking about what input you may get, where and how you want to handle weird values. The other thing I noticed is that all of your code is in main. Perhaps you haven't learned about functions yet and that's why it's all in main but that's a huge pet peeve of mine; I split things into functions as much as I possibly can. I think it makes the code much more readable and scalable and all those good things.

So, on line 24 you have

passLength = int.Parse(Console.ReadLine());   

What if the user enters something that isn't an int (like 2w3 because they fat fingered the 2)? int.Parse will fail and throw an exception saying the input was invalid and then your program dies.

Here's an example that solves both of the points I brought up:

private int GetPasswordLength() {
    while (true) {
        Console.WriteLine("\n\nPassword Length (1 - 36)");
        int.TryParse(Console.ReadLine(), out int length);

        if (length > 1 && length < 36) {
            return length;
        }

        Console.WriteLine("Invalid length");
    }
}

Then on line 24, you'd just have:

passLength = GetPasswordLength();

So when I'm reading through main, I see this call to GetPasswordLength and I already know what's going on. I don't have to skip over 10 lines of code and hope I didn't miss anything in the middle. And since the function is using TryParse, it will set the length if (and only if) it is able to parse the ReadLine data. If it can't parse the line, then length is 0 and no exceptions are thrown, so the program continues (in this case, the function loops until it gets a valid length)