|
Question : Memory Dump (WinDbg Provided)
|
|
This is the 1st Dump that I have not been able to figure out, and am also learning how to read them
Using the [WinDbg] as well.
Could someone please assist me with information on how to analyze these Dumps better?
Basically, explain it to me better on what I am looking for?
And were to find the information for it?
Thank you
Carrzkiss
=================================================================
kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: ef7ffffd, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: b784bc9a, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000000, (reserved)
Debugging Details:
------------------
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
MODULE_NAME: nt
FAULTING_MODULE: 80400000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4344ec59
READ_ADDRESS: unable to get nt!MmPoolCodeEnd
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPagedPoolEnd
unable to get nt!MmNonPagedPoolEnd
unable to get nt!MmNonPagedPoolStart
unable to get nt!MmSpecialPoolStart
unable to get nt!MmPagedPoolStart
unable to get nt!MmNonPagedPoolExpansionStart
unable to get nt!MmPoolCodeStart
ef7ffffd
FAULTING_IP:
+ffffffffb784bc9a
b784bc9a ?? ???
MM_INTERNAL_CODE: 0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x50
LAST_CONTROL_TRANSFER: from 00000000 to 80449d15
STACK_TEXT:
b6bce994 00000000 ef7ffffd 00000000 b784bc9a nt+0x49d15
STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_NAME: MachineOwner
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
---------
|
|
|
Answer : Memory Dump (WinDbg Provided)
|
|
b6bce994 00000000 ef7ffffd 00000000 b784bc9a nt!MmAccessFault+0x757 <-- This is the sign of faulty memory.
FAILURE_BUCKET_ID: 0x50_win32k!hdcOpenDCW+183 <-- This is also the sign of faulty memory (ram or video memory)
The culprit is faulty memory. You can run memtest to stress the ram. If memtest reports the ram is faulty, ram is bad. However Memtest is not a perfect tool to test the memory as some faulty ram can pass memtest.
Suggestion
1. Check the temperature of the CPU and make sure that it is not overheat (ie temperature < 60C)
Make sure that the CPU fan works properly
2. Reseat the memory stick to another memory slot. Reseat video card as well.
3. Downclock the ram. Check to default setting if you video card is overclocked.
4. Clean the dust inside the computer case
5. Make sure that the ram is compatible to the motherboard
For example : If the ram and the motherboard has dual mode compatibility problem, you must stop using dual mode and switch to single channel mode
http://www.techspot.com/vb/showthread.php?p=251045#post251045
6. Check the bios setting about memory timing and make sure that it is on
For example : DIMM1 and DIMM2 do not have the same timing.
DIMM1: Corsair CMX512-3200C2 512 MB PC3200 DDR SDRAM (2.5-3-3-8 @ 200 MHz) (2.0-3-3-7 @ 166 MHz)
DIMM2: Corsair CMX512-3200C2 512 MB PC3200 DDR SDRAM (3.0-3-3-8 @ 200 MHz)
DIMM3: Corsair CMX512-3200C2 512 MB PC3200 DDR SDRAM (3.0-3-3-8 @ 200 MHz)
7. Make sure that your PSU has adequate power to drive all the hardware including USB devices
8. Run chkdsk /r at command prompt
9. Run 3DMark 2005 to test your video card
10. Upgrade BIOS and make sure that the motherboard has no leaking capacitor
If it still crashes, diagnostic which memory stick is faulty
1. Take out one memory stick. If windows does not crash, the removed memory stick is faulty.
2. If you have only one memory stick, replace the ram
|
|
|
|
|
