Andrew:
Get a copy of memtest and test the memory module. You may have a
defective module or you may only need to upgrade the BIOS to allow it to
use all available memeory. Memtest86 does come in a bootable floppy
format that could be written to a CDROM image.
James McKenzie
Andrew in Ann Arbor wrote:
> Summery:
> I bought a 128 Mb RAM card on E-bay (Seller ID "for_the_animalzzz",
> item #3481287113). The text of the auction listing said:
> "*Models 385XD/560X running Windows 2000/XP work fine with this module."
>
> I started up my W2K 560x (Windows 2000 5.00.2195 Bios 97H4575 12/4/97)
> and made sure that it stared and ran with the 64Mb card present. Then I
> installed the 128 Mb card and started up.
> The Post memory check looked good reporting 163,264 Kb OK.
> I went to the device manager reported 163,188 KB RAM under "computer:".
> When I tried to check the memory under "system tools>system information"
> I got a blue screen:
> ***STOP:0x000000BE (0xA0014CEA,0x04479021,0xBE4CEF34,0x0000000B)
> An attempt was made to write to read-only memory.
> This driver may be at fault :win32k.sys
> *** Address A0014CEA base at A0000000, DataStamp 38438ff7 - win32k.sys
> Beginning dump of physical memory
> Physical memory dump complete.
> Contact your sys admin or tech support group.
>
> I've never claimed to understand what goes on inside Windows but
> "Beginning dump of physical memory" doesn't sound good.
>
> To be fair the auction listing also mentioned that you might need to
> update the BIOS so I'm going to do that this weekend and try again.
>
> I should also mention that this is an existing install of W2K so I
> can't vouch for any past abuses.
> This machine is scheduled for a new drive and clean install of W2K
> lite but I don't think that will have any effect on the RAM problems.
>
> Any thoughts?
> Is there hope?
>
>
> More Details (hopefully they make sense to someone)
>
> I went through several reboot, scandisk (actually W2K equivalent), the
> POST memory check always worked, all the internal tests (including
> memory) came back OK but I kept getting fatal errors in svchost.exe,
> MStask.exe, userinit.exe and rundll32.exe among others.
> Sometimes it would crash when I asked for the control panel.
> I also had it hang at the splash screen on startup.
>
> I booted from a floppy and ran Memtest-86 v1.4a and let it run all day.
> It completed 33 passes with no errors.
>
> The auction listing provided the following details:
>
> Compatible P/N: Kingston KTM-TP380Z/128
> Memory Size: 128 MB Memory Speed: 60ns
> Memory Type: EDO (Extended Data Output)
> Module Type: SODIMM (Small Outline Dual Inline Memory Module)
> Profile: 1" Configuration: 16Mx64 , 8 Chips
> Date Error Checking: Non-parity
> Supply Voltage: 3.3 Volts Pins: 144 pins
>
> The actual card had the following text on a white sticker
> HB56SW1664DBC-6L
> 9917xD06651C
> made in Japan
>
> Some more error messages:
>
> svchost.exe-Application error
> The instruction at "0x77fc98e5" referenced memory at "0x0000000a"
> he memory could not be "written"
>
> Windows - Application Error
> The application failed to initialize properly (0xc0000005).
> Click on OK to terminate the application
>
> Program Error
> MSTask.exe has generated errors and will be closed by Windows.
> You will need to restart the program.
> An error log is being created.
> userinit.exe- Application Error
> The application failed to initialize properly (0xc0000005).
> Click on OK to terminate the application
>
> Program Error
> rundll32.exe has generated errors and will be closed by Windows.
> You will need to restart the program.
> An error log is being created.
>
> Program Error
> svchost.exe has generated errors and will be closed by Windows.
> You will need to restart the program.
> An error log is being created.
>
> Program Error
> Explorer.exe has generated errors and will be closed by Windows.
> You will need to restart the program.
> An error log is being created.
> Windows- Application Error
> The application failed to initialize properly (0xc0000005).
> Click on OK to terminate the application
>
> I did look for the log files and found them in Windows>debug.
> The strange thing is that they are all 0Kb except NteSetup.log which
> is 4Kb
> ipsecpa.log
> ipsecpa.last
> NetSetup.log
> oakley.log
> oakly.log.sav
> PASSWD.LOG
>
> I also found the memory dump files in Windows>minidump:
> Mini051904-01.dmp
> Mini051904-01.dmp
> Mini051904-01.dmp
> Mini052004-01.dmp
> All are 64 Kb
>
> If anyone is motivated to look at any of these files I'd be happy to
> send them alone but I suspect the answer is much more basic.
>
>
>
_______________________________________________
Thinkpad mailing list
Thinkpad@stderr.org
http://stderr.org/cgi-bin/mailman/listinfo/thinkpad
Received on Fri May 21 20:43:46 2004
This archive was generated by hypermail 2.1.8 : Fri May 26 2006 - 16:02:56 EDT