• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Software to monitor... software?

John Connor

John Connor

Lifer
LOL Well, I am looking for something that shows all the drivers that are loaded at first run of a program. I am having some minor difficulty withy FS2004 and would like to narrow it down. It's GUI related and I narrowed it down to a possible driver or module loading that isn't playing nice with Win 7.
 
John Connor said:
LOL! Mod must have cleaned up the thread. Procmon looks viable. How do I filter drivers only? I don't see that option.

Edit- I thought the mod cleaned this thread up. I was looking at this similar thread. http://forums.anandtech.com/showthread.php?t=2387648&highlight=
Click to expand...

You also might want to investigate "Latency Monitor:"

http://www.resplendence.com/latencymon

Since I don't know specifically what it is that you're troubleshooting, I can only say that I (and others) wanted to find out how and why a single core of a processor was "loading up" or showing near-100% usage when the computer wasn't being used for anything intensive. That is, the CPU temperatures would be "about right," but usage on one core would show above 95%.

To confess, not only was latency-mon "helpful" in locating the offending drivers that caused DPCs and interrupts, but the documented experiences of people using it revealed the nature of specific problems with specific drivers -- confirmed by Latency Mon to be causing the problem on my system.
 
LatencyMon is not really what I need. I just thought of something of the top of my head today and I have seen mentioned in other forums, Dependency walker. This shows the drivers that are in use. So I will check out ProcMon and Dependency walker and narrow down what is giving me a bad GUI in FS2004.

When I first installed FS2004 it played fine. Then I copy/paste my 26 GB worth of data to the FS2004 directory and I'm guessing a dll isn't playing nice in Win 7. I did this copy/paste before in XP and had no problems. I was able to fly my F-22 but had to guess where the button was to start a flight with the screen half black. I'm assuming it could be FS Navigator which is a map.
 
Dependency Walker only shows DLLs (and you'll need to profile a running process if you want to also catch the DLLs that are dynamically loaded at runtime and not just the ones baked in at compile-time by the linker).

Procmon can show DLL loads, too (filter on LoadImage and CreateFile), but, yea, depends is more specialized and better for DLLs.

Is that what you're looking for? Because you said drivers, and DLLs are not drivers. 😛 If you really are looking for drivers, I'm not sure how (and if) you could tell what user-mode drivers are being loaded and used by a process, but if such a thing were possible, it would probably be in the form of some clue left in a procmon capture.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top