How to debug windows 7

Note If you don't see any output, enter. To see symbols in the Notepad. Notepad runs until it comes to the WinMain function, and then breaks in to the debugger. Enter g to start Notepad running again. In the Notepad window, enter some text and choose Save from the File menu. The running code breaks in when it comes to ZwCreateFile. Enter k to see the stack trace.

In the WinDbg window, just to the left of the command line, notice the processor and thread numbers. In this example the current processor number is 0, and the current thread number is So we are looking at the stack trace for thread 11 which happens to be running on processor 0. For this exercise, we will assume that the built application MyApp. For File name , enter MyApp. Now WinDbg knows where to find symbols and source code for your application.

Kernel mode is the processor-access mode in which the operating system and privileged programs run. Kernel-mode code has permission to access any part of the system, and it is not restricted like user-mode code. Kernel-mode code can gain access to any part of any other process running in either user mode or kernel mode. Much of the core OS functionality and many hardware device drivers run in kernel mode. User mode is the mode that applications and subsystems on the computer run in.

Processes that run in user mode do so within their own virtual address spaces. They are restricted from gaining direct access to many parts of the system, including system hardware, memory that was not allocated for their use, and other portions of the system that might compromise system integrity.

Because processes that run in user mode are effectively isolated from the system and other user-mode processes, they cannot interfere with these resources. If your goal is to debug a driver, determine if the driver is a kernel-mode driver or a user-mode driver.

For some issues, it can be difficult to determine which mode the code executes in. In that case, you may need to pick one mode and look to see what information is available in that mode. Some issues require using the debugger in both user mode and kernel mode.

Depending on what mode you decide to debug in, you will need to configure and use the debuggers in different ways. Some debugging commands operate the same in both modes, and some commands operate differently in different modes. For information about using the debugger in user mode, see Getting started with WinDbg user-mode. WinDbg works well in most situations, but there are times when you may want to use another debugger, such as console debuggers for automation or Visual Studio.

For more information, see Debugging environments. Typically, target and host systems are connected by an Ethernet network. Asked 6 years ago. Active 1 year, 11 months ago. Viewed 1k times. The actual question is really about "How can I debug" this see below , but for background a bit more story: I'm running Windows 7 bit fully updated on a new Dell Precision M SSD, and I constantly run into the following situation: All fine with the system.

Can shut down. I add a new user account for a domain-login for which I need the VPN at least once reboot and get it running. I can now use the domain-account even without being VPN-connected.

I want to regularly shut-down or log-off from windows7 and then I run into the issue The issue Situation: Windows 7 no problem with either local or domain account. Trigger: Restart system any way , select shutdown or log-off: Issue: Instead of seeing the "log-off" or "shutting-down" message I get to the same blue screen without any text.

What options do I have to debug the shut-down process and find the culprit? Attempted things: Following the answer in this question here on superuser : Switching on verbose-mode : While it works when I can shut-down it does not give any text message in my troubled case. Following suggestions here in the thread: Running 'chkdsk': No problem found.

Improve this question. Community Bot 1. BmyGuest BmyGuest 2 2 silver badges 12 12 bronze badges. If you haven't already, run a chkdsk and ensure there's no file-system corruption. After the problem shows up and before you do a system restore , if you log back in as your non-domain user, does it still always shut down as expected?

If you make another new, local user, does shutting down work as expected? Done no problem found. No, in the "bad" state neither user-account can shut down correctly. I have not tried a third one yet.

I had 7-Zip but removing it did not make any difference. None of the other apply. I also think there is a difference: Most reports I googled seem to freeze while shutting down is written on the screen.