Do you have access to the Graphics Debugger in Visual Studio? If so, please take a frame analysis and look through the sequence of operations that have been performed. This will likely show you why your frame ended up all white - just be sure to follow the operations and it should become more clear as you go.

First: some advice for learning how to debug your own code - you did a good job of determining that your rendering is affected by just a few lines of code (the sprite batch calls.) But you didn't take the next step to see why those lines cause the problem.

You could've done one of three things:

1. Looked at the source code for spriteBatch->Begin(...), DrawString() and End() to see what the code does that might affect your own rendering.

2. Set a breakpoint in debug mode at the spriteBatch->Begin call and stepped into the calls to see what might affect your rendering.

3. As Jason Z mentions, you can use a graphics debugger to see what happens (or doesn't happen) when your objects are rendered.

Admittedly, it's a bit hidden, but, assuming you're using the DXTK, you can look at the source (or step through it in debug mode) for SpriteBatch::Impl::PrepareForRendering() to see all the states that are set by the SpriteBatch::Begin(...) call (blend state, depth stencil state, etc.)

I suspect you don't specifically set all the states you need prior to rendering your own objects, and you're just relying on the initial states you setup when you create your context. So, once SpriteBatch::Begin has been called the first time, the states sprite batch sets up (probably incompatible with your own object rendering) persist through the next cycle in your loop.

So, either prior to rendering your objects, or following the sprite batch End() call, try setting the depth stencil state, the blend state, raster states, etc., you need for your own rendering.

my knowledge is not that great I am just a beginner at DirectX.

I'm going to assume you want to get better at programming. IF SO, then the next step, whether it's DirectX or any API, is for you to learn more about the code you're writing. Part of that process is to learn how to debug a program, so you can determine what you need to learn more about. You've taken a step in that direction by commenting out some code, and discovering where the problem is occurring. That is really good information! The next step, if you want to get better at programming, is to determine yourself why the problem is occurring.

Jason Z and I have taken some time to provide you with suggestions to do just that, including exactly where to look! However, you've chosen to ignore those responses.

If there is any particular information you need please ask away.

Okay. Have you done anything as suggested?

Tutorials are a horrible way to learn.

I've covered that before though, and so have others, so I won't go into a great deal of depth on the subject, but suffice it to say that tutorials don't have the depth nor breadth to cover a subject in any sufficient detail to be terribly useful. If you don't learn to program, and if you don't learn to learn, then you'll always be stuck in ruts like this...

That being said, I have written a sweet little snippet to demonstrate exactly how to render text to the screen using Direct2D.