Chad Beeder
ChadBeeder
-
Defrag Tools: #40 - WPT - WPR & WPAIn this episode of Defrag Tools, Andrew Richards, Chad Beeder and Larry Larsen continue walking you through the Windows Performance Toolkit (WPT).
Resources:
Defrag Tools: #23 - Windows 8 SDK
Defrag Tools: #29 - WinDbg - ETW Logging
Windows Performance Analysis Developer Center
Windows Performance Toolkit... -
Defrag Tools: #39 - Windows Performance ToolkitIn this episode of Defrag Tools, Andrew Richards, Chad Beeder and Larry Larsen starting walking you through the Windows Performance Toolkit (WPT).
Resources:
Defrag Tools: #23 - Windows 8 SDK
Defrag Tools: #29 - WinDbg - ETW Logging
Windows Performance Analysis Developer Center
Windows Performance Toolkit... -
Defrag: Keyboard Fail, Search Auto-Suggest, Wider CMD WindowMicrosoft tech troubleshooter extraordinaire Chad Beeder (filling in for Gov who will be back next week) and I help walk you through troubleshooting solutions to your tech support problems. If you have a problem you want to send us, you can use the Problem Step Recorder in Windows 7 (see this for...
-
Defrag Tools: #32 - DesktopsIn this episode of Defrag Tools, Andrew Richards, Chad Beeder and Larry Larsen walk you through Sysinternals Desktops. Desktops allows you to organize your applications on up to four virtual desktops. We go under the covers and show how Desktops fits in to the Session, Window Station and Desktop object/security...
-
Defrag Tools: #31 - ZoomItIn this episode of Defrag Tools, Andrew Richards, Chad Beeder and Larry Larsen walk you through Sysinternals ZoomIt. ZoomIt is a screen zoom and annotation tool for technical presentations that include application demonstrations. ZoomIt runs unobtrusively in the tray and activates with customizable hotkeys...
-
Defrag Tools: #30 - MCTS Windows InternalsIn this episode of Defrag Tools, Andrew Richards, Chad Beeder and Larry Larsen review MCP exam 70-660 - MCTS Windows Internals.
Resources:
MCTS Windows Internals
Windows Internals Books
Kernrate
Poolmon
UMDHTimeline:
[01:42] - Summary of the exam
... -
Defrag Tools: #29 - WinDbg - ETW LoggingIn this episode of Defrag Tools, Andrew Richards, Chad Beeder and Larry Larsen continue looking at the Debugging Tools for Windows (in particular WinDbg). WinDbg is a debugger that supports user mode debugging of a process, or kernel mode debugging of a computer.
This installment goes over the Event Tracing...
-
Defrag Tools: #28 - WinDbg - SchedulingIn this episode of Defrag Tools, Andrew Richards, Chad Beeder and Larry Larsen continue looking at the Debugging Tools for Windows (in particular WinDbg). WinDbg is a debugger that supports user mode debugging of a process, or kernel mode debugging of a computer.
This installment goes over the Windows...
-
Defrag Tools: #27 - WinDbg - Configure Kernel DebuggingIn this episode of Defrag Tools, Andrew Richards, Chad Beeder and Larry Larsen continue looking at the Debugging Tools for Windows (in particular WinDbg). WinDbg is a debugger that supports user mode debugging of a process, or kernel mode debugging of a computer.
This installment goes over the cables...
-
Defrag Tools: #26 - WinDbg - Semaphores, Mutexes and TimersIn this episode of Defrag Tools, Andrew Richards, Chad Beeder and Larry Larsen continue looking at the Debugging Tools for Windows (in particular WinDbg). WinDbg is a debugger that supports user mode debugging of a process, or kernel mode debugging of a computer.
This installment goes over the commands...
Staff
Here is a list of Channel 9 staff members.
Defrag: Keyboard Fail, Search Auto-Suggest, Wider CMD Window
Apr 29, 2013 at 12:00 AM@android: I don't know how it got changed, but Occam's razor says that I probably unchecked the box at some point in the past without realizing it.
Incidentally, this behavior is not specific to Windows 8. You can turn off "Find partial matches" in the Windows 7 search options and see the same behavior when searching from the start menu.
Defrag: Keyboard Fail, Search Auto-Suggest, Wider CMD Window
Apr 27, 2013 at 2:36 PM@Dark_Halmut: Cool, good to hear you got it worked out. I wonder if there's a bit more RF interference causing problems when it's in the back port, or something to do with the position of the antenna.
Defrag: VS Compile prob, Moving AppData, Versioning AX
Apr 02, 2013 at 11:08 AMWe now have a KB article published which explains the monitor timeout at lock screen issue [07:57].
Monitor powers off after 1 minute when PC is locked
Defrag: VS Compile prob, Moving AppData, Versioning AX
Apr 01, 2013 at 3:02 PM@Emkay1001: Right, it is the console lock timeout, which is separate from the regular video idle timeout. The "Turn off the display" setting in the Power control panel allows you to adjust the video idle timeout, but the timeout when on the lock screen (which defaults to 1 minute) is not adjustable via the GUI.
You don't need to add any special registry hacks to adjust the lock screen display timeout, though. You can do it via an elevated command prompt using the following commands:
This would set the console lock timeout for when the system is on AC power. To change it for the battery power profile (I wouldn't recommend this), use "/setdcvalueindex" instead.
Defrag Tools: #27 - WinDbg - Configure Kernel Debugging
Feb 15, 2013 at 12:48 PM@FFE: You got it! I set the breakpoint on the dispatch routine for IRP_MJ_POWER (modem!ModemPower), then disabled the modem in device manager, which would result in, not a power IRP, but a Plug and Play IRP (IRP_MJ_PNP).
I should have set the breakpoint on modem!ModemPnP instead of modem!ModemPower.
Defrag Tools: #27 - WinDbg - Configure Kernel Debugging
Feb 11, 2013 at 3:16 PMBrownie points to the first person who can tell me why my modem.sys breakpoint didn't get hit! I went back and watched the show later and figured out my mistake.
Defrag Tools: #23 - Windows 8 SDK
Feb 11, 2013 at 10:49 AM@dcrearer: Sorry, I didn't see this question earlier.
The !d commands (!db, !dc, !dd, etc.) take a physical memory address as the parameter. The regular d commands (db, dc, dd, etc.) take a virtual address. Other than that, they are the same.
Defrag Tools: #15 - WinDbg - Bugchecks (BSOD)
Dec 01, 2012 at 10:35 AM@MagicAndre1981: Yes, I've asked. A few of the newer bugchecks have been added to the documentation, but it's not clear every single one needs to be added. A lot of these bugchecks are rarely, if ever, seen in the wild. If there are specific ones that need to be documented, we can ask for them.
Defrag Tools: #15 - WinDbg - Bugchecks (BSOD)
Nov 26, 2012 at 6:04 PM@MagicAndre1981: Did you try adding the DedicatedDumpFile setting?
Yeah, it looks like the people in charge of maintaining the debugger help file haven't gotten around to documenting all those newer bugchecks. Bugcodes.h contains the most definitive list of codes used by Windows components. Of course, third-party drivers are free to use any bugcheck code they want.
Defrag Tools: #15 - WinDbg - Bugchecks (BSOD)
Nov 19, 2012 at 6:47 PM@dcrearer: I don't have a 6th Edition Windows Internals handy at the moment, but in my 5th Edition copy, there is a chart of the x64 address space layout, so hopefully it's still there!
On x64, user process address space is 0x0000000000000000 - 0x000007FFFFFEFFFF (8TB minus 64KB).
System space is from 0xFFFF080000000000 - 0xFFFFFFFFFFFFFFFF.
We will do more episodes on debugging. Thanks for watching!
See more comments…