Hi Scoot,

Do you resolve your problem?

cpc2004

Dear Expert,

I have copy the error report here attached in the attachment.

It occurs everytime entering XP. see the previous reply with a txt file.

Thanks.

William

I have read through the problems on this forum and some things seem to coinside with my problem, but others don't.

so here we go.

not too long ago, my computer began to restart on me out of the blue. pretty much at random times. it restarts and comes up with the blue screen that has the begin physical dump of memory. now here is the odd twist that my situation has. my RAM, i use 2 sticks. and i have it in slots 3 & 4. when i have both of them in, the computer restarts everytime, i cant even start windows at all. BUT when i have only one stick of the RAM in slot 3 it works. to use the RAM for any of my gaming needs, i do need to have both in....or else i would just deal with the one. is there any reason that my computer would start with just one stick of the RAM in slot 3, but not both sticks in slot 3 & 4??

any help on this would be wonderous, cause i have been lookin at it all week long!

thanks!!!

here is something that might help


The computer has rebooted from a bugcheck. The bugcheck was: 0x1000000a (0x00000008, 0x00000002, 0x00000001, 0x8051e17d). A dump was saved in: C:\WINDOWS\Minidump\Mini081905-06.dmp.


i attached some files... please help!

thank you so much!!!

Attached Files

winzip for comp prob.zip (87.6 KB, 3 views)

Dear Expert,

I have attached dmp file in the attachment.

Thanks.

William

Attached Files

crash.zip (40.0 KB, 2 views)

Hi Viper,

Obviously, this is the faulty RAM. Two bits were lost can cause bugcheck code 4E.

PFN_LIST_CORRUPT (4e)
Typically caused by drivers passing bad memory descriptor lists (ie: calling
MmUnlockPages twice with the same list, etc). If a kernel debugger is
available get the stack trace.
Arguments:
Arg1: 0000008f, The free or zeroed page listhead is corrupt
Arg2: c001bbd1, new page
Arg3: 0001bbd1, old page <--- (the high order byte shoud be c and it is 0. Two bits were lost and it is two bits corruption)
Arg4: 00000000, 0

Debugging Details:
------------------
CUSTOMER_CRASH_COUNT: 4
DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT
BUGCHECK_STR: 0x4E
LAST_CONTROL_TRANSFER: from 80518891 to 804f8925

STACK_TEXT:
f8a80804 80518891 0000004e 0000008f c001bbd1 nt!KeBugCheckEx+0x1b
f8a80844 8068466d 825ca788 00000000 00000044 nt!MmZeroPageThread+0x123
f8a80dac 805c4a06 80087000 00000000 00000000 nt!Phase1Initialization+0x1145
f8a80ddc 80540fa2 80683528 80087000 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16

FOLLOWUP_IP:
nt!MmZeroPageThread+123
80518891 cc int 3

SYMBOL_STACK_INDEX: 1
FOLLOWUP_NAME: MachineOwner
SYMBOL_NAME: nt!MmZeroPageThread+123
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 42250a1d
STACK_COMMAND: kb
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: 0x4E_nt!MmZeroPageThread+123
BUCKET_ID: 0x4E_nt!MmZeroPageThread+123

Hi William,

If you don't convice it is faulty ram. Post your problem at windowsbbs.com and this webpage does not accept attachment and you have to post the output of windbg there.

cpc

Dear expert,

What is fault ram, does it mean my memory went wrong?

William

Hi William,

RAM means that Random Access Memory. AV is the abbreviation of antivirus. Search google and find out the question such as RAM, Norton AV. There have a lot of posts within this forum how to handle faulty ram. Do some reading b4 you ask question. You had better take your PC to hardware shop. You don't have the basic hardware knowledge. I am afraid that you will screw up your computer.

cpc

Could someone please have a look at my dump files and tell me what is wrong with this PC? It reboot by itself once evey few days. I have attached the files. Thanks.

Attached Files

error.zip (62.3 KB, 3 views)

Hi ndlu,

Your version of W2K is the most current version. The corresponding windows symbol files of your W2k is not available. I could not format your minidump properly without the symbol file. I believe that it is faulty RAM as you have three different bugcheck codes 0A, 1E and 50.

You have to install windbg and run the following command
Debugging Tools from Microsoft
1) Create folder c:\symbols
2) Download and install the http://www.microsoft.com/whdc/devtoo...nstallx86.mspx
3) Locate your latest memory.dmp file- C:\WINDOWS\ Minidump\Mini082605-01.dmp or whatever
4) open a CMD prompt and cd\program files\debugging tools for windows\
5) type the following stuff:

Code:
c:\program files\debugging tools>kd -z C:\WINDOWS\ Minidump\Mini082605-01.dmp
(it will spew a bunch)
kd> .logopen c:\debuglog.txt
kd> .sympath srv*c:\symbols*http://msdl.microsoft.com/download/symbols
kd> .reload;!analyze -v;r;kv;lmnt;.logclose;q
(it will spew)

5) You now have a debuglog.txt in c:\, open it in notepad and post to this thread.

Post the debug report mini082505-03.dmp and mini082405-01.dmp and mini082505-02.dmp

cpc

Thanks for your reply cpc, yesterday I tried disable my Norton AV and so far it is going well. I will try the debugging tool if the PC start to reboot again. Cheers.

Hi,

If I were you I would investigate the optical drive you are using. I have seen instances were a faulty drive causes XP to crash - it depends on the driver and drive being used. This would explain your read errors during install and the initial crash dumps you were getting -its worth a try.

- If you have 2 optical drives try using the other CD/DVD drive. Open your case and disconnect the ribbon cable from the drive you usually use and try re-installing from the other drive.

-If you have a spare ide cable, try it, the one your using may be shorting or has a break in the cable causing an intermittant fault.

- Try running the optical drive on the other IDE channel.

Another reason which is easily tested for is that your PSU may be faulty and is not supplying a steady voltage. You will need another PSU to test this theory. This may be the cause if you are seeing a variety of errors (i.e. not the same every time)

I have this problem of blue screen getting physical dump..
please let me know what am I supposed to do.. here is the dump log file..:-(

Attached Files

Mini090805-01.zip (16.6 KB, 2 views)

RAM is the issue in my is laptop, after i changed all issue got over!!
Thanks a lot :bounce:

hi guys i had the same problem..my laptop showed a blue screen and then it does not start in safe modealso... but my concern is tht i have some ver important files on my hard disk..will they still be there if i remove my hard disk and connect it to another computer as a xternal hard drive??
plssssssss help me out

hi its my first post, so i am not sure if i have done this correctly.

can cpc2004 please help me with this dumpfile attachments.

i am getting the bsod errors, and they seem to be two different error #s.

can you please help me.

thank you

Attached Files

dumpfiles.zip (35.7 KB, 1 views)

Hi,

Open a new thread for a new problem.

How can I find out what is going on with this file? I noticed that you were pretty good with this.

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\>dumpchk.exe e:\memory.dmp
Loading dump file e:\memory.dmp
----- 32 bit Kernel Full Dump Analysis

DUMP_HEADER32:
MajorVersion 0000000f
MinorVersion 00000a28
DirectoryTableBase 00039000
PfnDataBase 81051000
PsLoadedModuleList 8055a420
PsActiveProcessHead 805604d8
MachineImageType 0000014c
NumberProcessors 00000001
BugCheckCode 0000007e
BugCheckParameter1 c0000005
BugCheckParameter2 804e37f3
BugCheckParameter3 f766082c
BugCheckParameter4 f7660528
PaeEnabled 00000000
KdDebuggerDataBlock 8054c060

Physical Memory Description:
Number of runs: 3
FileOffset Start Address Length
00001000 00001000 0009e000
0009f000 00100000 00eff000
00f9e000 01000000 1efd0000
Last Page: 1ff6d000 1ffcf000

KiProcessorBlock at 80559320
1 KiProcessorBlock entries:
ffdff120


Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Built by: 2600.xpsp_sp2_gdr.050301-1519
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a420
Debug session time: Sat Nov 04 13:54:58 2006
System Uptime: 0 days 2:23:06
start end module name
804d7000 806eb100 nt Checksum: 002198AF Timestamp: Tue Mar 01 19:
59:37 2005 (42250FF9)

Unloaded modules:
ecc9f000 eccf1000 srv.sys Timestamp: Sat Nov 04 13:54:53 2006 (454CE1FD)
f88e4000 f88eb000 USBSTOR.SYS Timestamp: Sat Nov 04 13:52:26 2006 (454CE16A
)
ec0b2000 ec0dd000 kmixer.sys Timestamp: Sat Nov 04 12:31:03 2006 (454CCE57)

ec0b2000 ec0dd000 kmixer.sys Timestamp: Sat Nov 04 12:08:15 2006 (454CC8FF)

ec0b2000 ec0dd000 kmixer.sys Timestamp: Sat Nov 04 12:01:37 2006 (454CC771)

ec7b1000 ec7dc000 kmixer.sys Timestamp: Sat Nov 04 11:37:26 2006 (454CC1C6)

f8c42000 f8c43000 drmkaud.sys Timestamp: Sat Nov 04 11:35:03 2006 (454CC137
)
ecaff000 ecb0c000 DMusic.sys Timestamp: Sat Nov 04 11:35:03 2006 (454CC137)

ec7dc000 ec7ff000 aec.sys Timestamp: Sat Nov 04 11:35:03 2006 (454CC137)
ecdf2000 ece00000 swmidi.sys Timestamp: Sat Nov 04 11:35:03 2006 (454CC137)

f8a96000 f8a98000 splitter.sys Timestamp: Sat Nov 04 11:35:03 2006 (454CC13
7)
f76c1000 f76c4000 wmiacpi.sys Timestamp: Sat Nov 04 11:32:15 2006 (454CC08F
)
f86e4000 f86ed000 processr.sys Timestamp: Sat Nov 04 11:32:15 2006 (454CC08
F)
f8a0c000 f8a10000 kbdhid.sys Timestamp: Sat Nov 04 11:32:15 2006 (454CC08F)

f891c000 f8921000 Cdaudio.SYS Timestamp: Sat Nov 04 11:32:15 2006 (454CC08F
)

Finished dump check

well, I've read quite a bit on this physical memory dump problem, but somehow I've missed the cuplprit.. I know its not faulty ram, cpu, motherboard, and other hardware.... too many people on too many different computers are having the same problem, and with different types software... different operating systems... so... what gives... I bought my HP/Compaq 3000 presario laptop from Frys.. it has the 2.8Ghz, 512 Ram, 80Gb hd... etc... it got this physical memory dump 2 weeks from the date I bought it.. 2 1/2 weeks from the date I bought it and its a total a worthless heap of plastic... it won't start up, it won't do anything. it won't reload, it is totally worthless.... Frys won't talk to me about it, HP won't warranty it, so, I'm out $1300.00 unless I can figure out what the heck this problem is or how to resolve it.. someone somewhere has created this monster and its effecting too many people to let it go un-announced.. so lets get whomever it is that did this!