Page 1 of 1

Need help with error code on 600E

Posted: Thu Jun 22, 2006 6:47 pm
by bosco
I have a 600E (2645-8AU) that has been upgraded with a P3 650mhz cpu, but runs at 500mhz due to being non-speedstep. It also has 256mb of PC133 ram (2x128mb).

It has been running fine for months. However, within the past week or two it boots up intermittently with 160mb of ram instead of 288. I reseated the ram and it reboots fine, but every now and then it will boot with 160mb of ram.

I went into EZ Setup and ran a test on the memory and get a red X with the following code:

DEV 002
ERR 33
FRU 1110

It's a memory error, however, page 44 ofthe HMM states the following:

FRU Codes: If an error is detected by the diagnostic tests, a four digit FRU Code is displayed. The FRU code indicates two suspected FRUs. Replace the FRU that is indicated by the two leftmost digits first; then replace the FRU that indicated by the two rightmost digits.

Therefore FRU 1110 indicates CPU card (11), then system board (10). I can't find in the HMM what ERR 33 means.

Does this mean that my cpu and system board are going bad and that is why the memory is flaky at times? It would seem like maybe a memory chip is going bad and not the cpu.

This is confusing me. Is it the memory or the cpu or the system board? Could anyone explain please?

Re: Need help with error code on 600E

Posted: Thu Jun 22, 2006 7:26 pm
by rkawakami
bosco wrote:I have a 600E (2645-8AU) that has been upgraded with a P3 650mhz cpu, but runs at 500mhz due to being non-speedstep. It also has 256mb of PC133 ram (2x128mb).
Even with the 650Mhz processor I believe that it needs PC100 CL2 modules. If yours is PC133 CL2, then it should work. However, if they are CL3 then your memory may not be fast enough. (CL=CAS latency)
bosco wrote:It has been running fine for months. However, within the past week or two it boots up intermittently with 160mb of ram instead of 288. I reseated the ram and it reboots fine, but every now and then it will boot with 160mb of ram.
Has it been getting warmer where you are or perhaps the laptop is warmer? This may explain why you are now seeing what appears to be memory issues. High temperature slows down memory access.
bosco wrote: <snip> Therefore FRU 1110 indicates CPU card (11), then system board (10). I can't find in the HMM what ERR 33 means.
Not sure what error 33 means either, sorry.
bosco wrote:Does this mean that my cpu and system board are going bad and that is why the memory is flaky at times? It would seem like maybe a memory chip is going bad and not the cpu.
I would say that if your modules are CL3 then that might be your problem. If they are CL2, then it's time to run memory checks. You could also try downloading memtest86+, a memory diagnostic program. Once you have it on your computer, if you execute the program it will create a boot floppy. Boot the computer from that floppy and the memory tests will start running. Test the built-in 32M of memory separately from the modules, then plug one module in and re-run the test(s). Remove that module, plug in the other one (in the same socket) and run memory tests again. If no problems are found with both modules, retest them separately in the other socket. Finally, if all appears to work correctly, plug both modules in and run diagnostics. I know it's a lot of work but it is the only way to isolate which module/socket is giving you problems.

There could be an intermittent contact with one of the modules in the socket. Be sure that the side locking arms of the memory socket are firmly over the edges of the module. When installed, pull up slightly on the module to insure that it's locked in.

Better to start on the easier things to test (memory) than it is to disassemble the laptop to get to the CPU. Of course a loose CPU can exhibit these types of failures and can also prevent you from even booting. In that case, it may be time to crack open the case and re-seat the CPU. While I'm thinking about it, check to make sure the CPU fan is running.

Posted: Thu Jun 22, 2006 7:47 pm
by tfflivemb2
You might need to disable your onboard ram. There is a BIOS hex edit that you can perform to disable the onboard ram. Try disabling the onboard ram and see if you get the same error. You can learn exactly what to modify by reading through the upgrading thread, which I am sure that you have, in an effort to bypass the 127 error.

As for the intermittant amounts of total ram, this is one of the downfalls of some of the 600/600Es. There is a way to brace the ram into place using card board or something for support, to create a better connection.