nborowicz
asked on
How do I find out what driver/application is loaded at a certain memory address?
We have a few identical computers which occasionally blue screen with identical STOP error codes (all the "numbers" at the bottom of the BSOD match not just the STOP code). I know the last "number" is the address which referenced memory but I want to find out what is actually loded at that memory address.
If I can find out what is loaded at this address I may be able to find out what is causing the BSODs. I've attached one of the BSOD's for your reference. Thanks.
BSOD.jpg
If I can find out what is loaded at this address I may be able to find out what is causing the BSODs. I've attached one of the BSOD's for your reference. Thanks.
BSOD.jpg
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thank you maze-uk, I can now view the contents of the memory at an address (I was able to do this with a similar tool windbg) but I still cannot see what driver or application is loaded into that memory address. Do you know how I might be able to do this using DEBUG or another tool?
Here'a a Microsoft KB article about Stop 0x0A errors: http://support.microsoft.com/kb/314063
ASKER
Thanks Callandor, I have seen that KB article already, it was very useful in describing what the 4 parameters mean, hence me asking this question.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
You may be unsuccessful trying to find out what soft is the source.
As I told you we had a 'bad serie' of hardware. Once (all) our laptop's motherboard where replace, everything came fine.
Browse the Net (google is your friend) to look for other people with similar hardware (make/model), who alos have the issue. (and possible solution...)
Also try the support from your hardware manufacturer. They may be aware of an issue and may replace the faulty hardware. Don't wait so you can benefit of the manufacturer's warranty...
As I told you we had a 'bad serie' of hardware. Once (all) our laptop's motherboard where replace, everything came fine.
Browse the Net (google is your friend) to look for other people with similar hardware (make/model), who alos have the issue. (and possible solution...)
Also try the support from your hardware manufacturer. They may be aware of an issue and may replace the faulty hardware. Don't wait so you can benefit of the manufacturer's warranty...
I said 'may be'... you may also prove me wrong... :-)
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Runs Debug, a program testing and editing tool.
DEBUG [[drive:][path]filename [testfile-parameters]]
[drive:][path]filename Specifies the file you want to test.
testfile-parameters Specifies command-line information required by
the file you want to test.
After Debug starts, type ? to display a list of debugging commands.