Windows XP Community - XPHeads



Registry Mechanic - Free Scan Now

Interpreting MEMORY.DMP

microsoft.public.windowsxp.help_and_support


Reply
  #1 (permalink)  
Old 06-05-2008, 09:59 AM
RGSL
 
Posts: n/a
Interpreting MEMORY.DMP
I had used the dumpchk.exe to read the content of MEMORY.DMP to analyze which
file are causing BSOD but i can't seem to find the stated file, ati2cqag.dll
in the memory.dmp
C:\Program Files\Support Tools>dumpchk C:\WINDOWS\MEMORY.DMP
Loading dump file C:\WINDOWS\MEMORY.DMP
----- 32 bit Kernel Full Dump Analysis

DUMP_HEADER32:
MajorVersion 0000000f
MinorVersion 00000a28
DirectoryTableBase 29efe000
PfnDataBase 81ad3000
PsLoadedModuleList 8055b1c0
PsActiveProcessHead 80561358
MachineImageType 0000014c
NumberProcessors 00000001
BugCheckCode 00000050
BugCheckParameter1 e9eee85c
BugCheckParameter2 00000000
BugCheckParameter3 bf077276
BugCheckParameter4 00000001
PaeEnabled 00000000
KdDebuggerDataBlock 8054cde0

Physical Memory Description:
Number of runs: 3
FileOffset Start Address Length
00001000 00001000 0009e000
0009f000 00100000 00eff000
00f9e000 01000000 2eff0000
Last Page: 2ff8d000 2ffef000

KiProcessorBlock at 8055a0c0
1 KiProcessorBlock entries:
ffdff120


Windows XP Kernel Version 2600 (Service Pack 3) UP Free x86 compatible
Built by: 2600.xpsp.080413-2111
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055b1c0
Debug session time: Thu Jun 05 17:22:20 2008
System Uptime: 0 days 5:17:20
start end module name
804d7000 806ed680 nt Checksum: 002247C2 Timestamp: Mon Apr 14
03:
27:39 2008 (48025EAB)

Unloaded modules:
b8103000 b812e000 kmixer.sys Timestamp: Thu Jun 05 12:05:49 2008
(4847661D)

b812e000 b8151000 aec.sys Timestamp: Thu Jun 05 12:05:41 2008 (48476615)
f7d1c000 f7d1d000 drmkaud.sys Timestamp: Thu Jun 05 12:05:41 2008
(48476615
)
f788f000 f789c000 DMusic.sys Timestamp: Thu Jun 05 12:05:40 2008
(48476614)

ba7c0000 ba7ce000 swmidi.sys Timestamp: Thu Jun 05 12:05:40 2008
(48476614)

f7c47000 f7c49000 splitter.sys Timestamp: Thu Jun 05 12:05:40 2008
(4847661
4)
f7b4f000 f7b53000 kbdhid.sys Timestamp: Thu Jun 05 12:05:16 2008
(484765FC)

f7a2f000 f7a34000 Cdaudio.SYS Timestamp: Thu Jun 05 12:05:16 2008
(484765FC
)
f7b4b000 f7b4e000 Sfloppy.SYS Timestamp: Thu Jun 05 12:05:16 2008
(484765FC
)

Finished dump check

C:\Program Files\Support Tools>
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
Sponsored Links
  #2 (permalink)  
Old 06-06-2008, 02:45 AM
Andrew E.
 
Posts: n/a
RE: Interpreting MEMORY.DMP
Try kb315271

"RGSL" wrote:

> I had used the dumpchk.exe to read the content of MEMORY.DMP to analyze which
> file are causing BSOD but i can't seem to find the stated file, ati2cqag.dll
> in the memory.dmp
> C:\Program Files\Support Tools>dumpchk C:\WINDOWS\MEMORY.DMP
> Loading dump file C:\WINDOWS\MEMORY.DMP
> ----- 32 bit Kernel Full Dump Analysis
>
> DUMP_HEADER32:
> MajorVersion 0000000f
> MinorVersion 00000a28
> DirectoryTableBase 29efe000
> PfnDataBase 81ad3000
> PsLoadedModuleList 8055b1c0
> PsActiveProcessHead 80561358
> MachineImageType 0000014c
> NumberProcessors 00000001
> BugCheckCode 00000050
> BugCheckParameter1 e9eee85c
> BugCheckParameter2 00000000
> BugCheckParameter3 bf077276
> BugCheckParameter4 00000001
> PaeEnabled 00000000
> KdDebuggerDataBlock 8054cde0
>
> Physical Memory Description:
> Number of runs: 3
> FileOffset Start Address Length
> 00001000 00001000 0009e000
> 0009f000 00100000 00eff000
> 00f9e000 01000000 2eff0000
> Last Page: 2ff8d000 2ffef000
>
> KiProcessorBlock at 8055a0c0
> 1 KiProcessorBlock entries:
> ffdff120
>
>
> Windows XP Kernel Version 2600 (Service Pack 3) UP Free x86 compatible
> Built by: 2600.xpsp.080413-2111
> Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055b1c0
> Debug session time: Thu Jun 05 17:22:20 2008
> System Uptime: 0 days 5:17:20
> start end module name
> 804d7000 806ed680 nt Checksum: 002247C2 Timestamp: Mon Apr 14
> 03:
> 27:39 2008 (48025EAB)
>
> Unloaded modules:
> b8103000 b812e000 kmixer.sys Timestamp: Thu Jun 05 12:05:49 2008
> (4847661D)
>
> b812e000 b8151000 aec.sys Timestamp: Thu Jun 05 12:05:41 2008 (48476615)
> f7d1c000 f7d1d000 drmkaud.sys Timestamp: Thu Jun 05 12:05:41 2008
> (48476615
> )
> f788f000 f789c000 DMusic.sys Timestamp: Thu Jun 05 12:05:40 2008
> (48476614)
>
> ba7c0000 ba7ce000 swmidi.sys Timestamp: Thu Jun 05 12:05:40 2008
> (48476614)
>
> f7c47000 f7c49000 splitter.sys Timestamp: Thu Jun 05 12:05:40 2008
> (4847661
> 4)
> f7b4f000 f7b53000 kbdhid.sys Timestamp: Thu Jun 05 12:05:16 2008
> (484765FC)
>
> f7a2f000 f7a34000 Cdaudio.SYS Timestamp: Thu Jun 05 12:05:16 2008
> (484765FC
> )
> f7b4b000 f7b4e000 Sfloppy.SYS Timestamp: Thu Jun 05 12:05:16 2008
> (484765FC
> )
>
> Finished dump check
>
> C:\Program Files\Support Tools>

Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #3 (permalink)  
Old 06-06-2008, 09:50 AM
RGSL
 
Posts: n/a
RE: Interpreting MEMORY.DMP
"Andrew E." wrote:

> Try kb315271


I tried that but it doesn't have a guide on how to pinpoint the exact files
that are causing BSOD.

Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #4 (permalink)  
Old 06-06-2008, 12:04 PM
John John (MVP)
 
Posts: n/a
Re: Interpreting MEMORY.DMP
It's an 0x50 error most likely caused by AV software or third party
driver. The file ati2cqag.dll is an ATI Radeon file, if this file is
mentioned in the BSOD then consider your Catalyst Video drivers at
fault. Contact ATI or maybe something here might help:
http://search.yahoo.com/search;_ylt=...t-501&ei=UTF-8

Possible Resolutions to STOP 0x0A, 0x01E, and 0x50 Errors
https://profile.microsoft.com/RegSys...aspx?lcid=1033

John

Andrew E. wrote:
> Try kb315271
>
> "RGSL" wrote:
>
>
>>I had used the dumpchk.exe to read the content of MEMORY.DMP to analyze which
>>file are causing BSOD but i can't seem to find the stated file, ati2cqag.dll
>>in the memory.dmp
>>C:\Program Files\Support Tools>dumpchk C:\WINDOWS\MEMORY.DMP
>>Loading dump file C:\WINDOWS\MEMORY.DMP
>>----- 32 bit Kernel Full Dump Analysis
>>
>>DUMP_HEADER32:
>>MajorVersion 0000000f
>>MinorVersion 00000a28
>>DirectoryTableBase 29efe000
>>PfnDataBase 81ad3000
>>PsLoadedModuleList 8055b1c0
>>PsActiveProcessHead 80561358
>>MachineImageType 0000014c
>>NumberProcessors 00000001
>>BugCheckCode 00000050
>>BugCheckParameter1 e9eee85c
>>BugCheckParameter2 00000000
>>BugCheckParameter3 bf077276
>>BugCheckParameter4 00000001
>>PaeEnabled 00000000
>>KdDebuggerDataBlock 8054cde0
>>
>>Physical Memory Description:
>>Number of runs: 3
>> FileOffset Start Address Length
>> 00001000 00001000 0009e000
>> 0009f000 00100000 00eff000
>> 00f9e000 01000000 2eff0000
>>Last Page: 2ff8d000 2ffef000
>>
>>KiProcessorBlock at 8055a0c0
>> 1 KiProcessorBlock entries:
>> ffdff120
>>
>>
>>Windows XP Kernel Version 2600 (Service Pack 3) UP Free x86 compatible
>>Built by: 2600.xpsp.080413-2111
>>Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055b1c0
>>Debug session time: Thu Jun 05 17:22:20 2008
>>System Uptime: 0 days 5:17:20
>>start end module name
>>804d7000 806ed680 nt Checksum: 002247C2 Timestamp: Mon Apr 14
>>03:
>>27:39 2008 (48025EAB)
>>
>>Unloaded modules:
>>b8103000 b812e000 kmixer.sys Timestamp: Thu Jun 05 12:05:49 2008
>>(4847661D)
>>
>>b812e000 b8151000 aec.sys Timestamp: Thu Jun 05 12:05:41 2008 (48476615)
>>f7d1c000 f7d1d000 drmkaud.sys Timestamp: Thu Jun 05 12:05:41 2008
>>(48476615
>>)
>>f788f000 f789c000 DMusic.sys Timestamp: Thu Jun 05 12:05:40 2008
>>(48476614)
>>
>>ba7c0000 ba7ce000 swmidi.sys Timestamp: Thu Jun 05 12:05:40 2008
>>(48476614)
>>
>>f7c47000 f7c49000 splitter.sys Timestamp: Thu Jun 05 12:05:40 2008
>>(4847661
>>4)
>>f7b4f000 f7b53000 kbdhid.sys Timestamp: Thu Jun 05 12:05:16 2008
>>(484765FC)
>>
>>f7a2f000 f7a34000 Cdaudio.SYS Timestamp: Thu Jun 05 12:05:16 2008
>>(484765FC
>>)
>>f7b4b000 f7b4e000 Sfloppy.SYS Timestamp: Thu Jun 05 12:05:16 2008
>>(484765FC
>>)
>>
>>Finished dump check
>>
>>C:\Program Files\Support Tools>


Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #5 (permalink)  
Old 06-09-2008, 11:05 AM
RGSL
 
Posts: n/a
Re: Interpreting MEMORY.DMP
It displayed PAGE_FAULT_IN_NONPAGE_AREA and
STOP:0x00000050(0xE7E64FLC,0x0000000,0xDF077276,0x 00000001) in the BSOD.

Your provided links to "Possible Resolutions to STOP 0x0A, 0x01E, and 0x50
Errors" of
https://profile.microsoft.com/RegSys...aspx?lcid=1033

point to other pages.
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #6 (permalink)  
Old 06-09-2008, 12:38 PM
John John (MVP)
 
Posts: n/a
Re: Interpreting MEMORY.DMP
Ooops! Sorry about that, try:

Possible Resolutions to STOP 0x0A, 0x01E, and 0x50 Errors
http://support.microsoft.com/kb/183169/en-us

http://support.microsoft.com/search/... mode=r&lsc=0

Look in the Event Log to see if pertinent errors are logged.

John

RGSL wrote:
> It displayed PAGE_FAULT_IN_NONPAGE_AREA and
> STOP:0x00000050(0xE7E64FLC,0x0000000,0xDF077276,0x 00000001) in the BSOD.
>
> Your provided links to "Possible Resolutions to STOP 0x0A, 0x01E, and 0x50
> Errors" of
> https://profile.microsoft.com/RegSys...aspx?lcid=1033
>
> point to other pages.


Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #7 (permalink)  
Old 06-13-2008, 12:03 PM
RGSL
 
Posts: n/a
Re: Interpreting MEMORY.DMP
Is there any diagnostic tools that can perform test on graphic card and
mainboard as i suspect it's my GFX card.
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #8 (permalink)  
Old 06-13-2008, 12:48 PM
John John (MVP)
 
Posts: n/a
Re: Interpreting MEMORY.DMP
Ask your graphic card vendor and your PC/Motherboard manufacturer. If
the PC is from a large OEM check their support site, most of them have
diagnostic utilities that will check all the components in the computer.

John

RGSL wrote:

> Is there any diagnostic tools that can perform test on graphic card and
> mainboard as i suspect it's my GFX card.


Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #9 (permalink)  
Old 06-14-2008, 10:45 AM
RGSL
 
Posts: n/a
Re: Interpreting MEMORY.DMP
My PC are a custom build[D.I.Y], by the way do you know if there's any good
diagnostic tools out there in the market?
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #10 (permalink)  
Old 06-14-2008, 11:56 AM
John John (MVP)
 
Posts: n/a
Re: Interpreting MEMORY.DMP
RGSL wrote:

> My PC are a custom build[D.I.Y], by the way do you know if there's any good
> diagnostic tools out there in the market?


A hardware group would be the best place to get that kind of advice.

http://www.pccertify.com/Templates/default.dwt
http://www.pc-doctor.com/

John
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
Reply


Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On



All times are GMT. The time now is 09:07 AM.


Registry Mechanic - Free Scan Now
Driver Scanner 2009 - Free Scan Now




Design by Vjacheslav Trushkin for phpBBStyles.com.
Powered by vBulletin® Version 3.6.7
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO 3.1.0

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74