Digital Center
Home Register FAQ New Posts Members List Contact Us Log In
Digital Center Computer Workbench PC Problems

Laptop out of warrenty please help

Lou_smorals 06.08.2006, 15:28
Hi
I have a toshiba m30x laptop, out of warrenty by 7 weeks. It has pheonix bios and after a year of sterling service last night on boot up I get one long beep and then 2 short. if the odd time it did boot up it would freeze on loading of desktop.
called toshiba technical no help line, they had me recover from cd. did that...
Now when I boot I get message on black screen saying
PXE-E81: media test failure - check cable
PXE-M0F: exiting PXE rom
then nothing.
called a few laptop repair companies who want ?200 for repair...can anybody tell me the best place or sollution please
should this just go in bin?
thanks
LS
Mr_Flash 06.08.2006, 16:00
Sound like the Hard Drive has failed to me. Can you look in the BIOS and see if is detected.

If it isn't and has failed then you could by a replacement and fit it yourself.

Very simple to do
chubblies 06.08.2006, 16:50
Just googled it and found a list of pxe error codes, not sure if they are a lot of use though...
Attached : Complete List of PXE Once Codes

If you 're using Deployment Server to roll-out new p., these error codes will come in handy :

Init/Boot/Loader Codes

PXE-E00 : Could not find enough free base memory.
PXE BaseCode and Undi runtime modules are copied from flash memory or roughly into the top of free base memory between 480K (78000h) and 640K (A0000h). This memory must be zero filled by the system BIOS. If this memory is not zero filled. the relocation code in the PXE directory will assume that this memory is being used by the system BIOS or other boot directory.

PXE-E01 : PCI Vendor and Device IDs do not match!
This message should never be seen in a production BIOS. When the system BIOS initializes a PCI option ROM it is supposed to pass the PCI bus/device/function numbers in the X register. If the PCI device defined in the X register does not match the Undi device, this error is displayed.

PXE-E04 : Once reading PCI configuration space.
This message is displayed if any of the PCI BIOS calls made to read the PCI configuration space return an error code. This should not happen with a properly 闁 嬪  production BIOS and hardware.

PXE-E05 : EEPROM checksum error.
This message is displayed if the NIC EEPROM contents have been corrupted. This can happen if the system is reset or powered down when the NIC EEPROM is being reprogrammed. If this message is displayed the PXE ROM will not boot.

PXE-E06 : Option ROM requires ddim support.
This message should not be seen in a production BIOS. PCI option ROMs must always be installed as ddim option directory (they must be installed into read/write differential memory).

PXE-E07 : PCI BIOS calls not supported.
This message should not be seen in a production BIOS. PCI NIC BIOS must have BIOS services.

PXE-E08 : Unexpected drive errors. API : xxxxh Status : xxxxh
This message is displayed if a PXE API returns a status code that is not expected by the runtime
Loader.

PXE-E09 : Unexpected Undi loader errors. Status : xxxxh
This message is displayed if the Undi runtime loader returns an unexpected status code.


Arp Codes

PXE-E11 : Arp timeout.
The PXE ROM will retry the Arp request four times, if it does not get any valid Arp replies. this message is displayed. This error can be caused by a number of network and service configuration errors. The most common are :

Setting the DHCP Class Identifier (option 60) on the DHCP server and installing theproxyDHCP on a separate machine.
Wireless routers that do not respond to Arp requests.

BIOS and BIS codes

PXE-E20 : BIOS extended memory copy errors. AH == nn
This message is displayed if the BIOS extended memory copy service returns an error. This should not happen on a production BIOS. Nn is the BIOS error code returned by the BIOS extended memory copy service (1******5h, AH = 87h).

PXE-E21 : BIS integrity check failed.
This message is displayed if the BIS in extended memory has been corrupted image.

PXE-E22 : BIS image/credential validation failed.
The downloaded image and credential do not match the 瀹 ㈡ 埗 17-19.

PXE-E23 : BIS initialization failed.
Reuters could not be initialized. No more data is available.

PXE-E24 : BIS shutdown failed.
Reuters could not be shutdown. No more data is available.

PXE-E25 : BIS get boot object authorization check flag failed.
Could not determine if BIS is enabled/disabled.

PXE-E26 : BIS free memory failed.
Could not release BIS allocated memory.

PXE-E27 : BIS get signature information failed.
Required BIS credential type information could not be determined.

PXE-E28 : BIS bad entry module checksum.
BIS 9******2 structure in the SM BIOS table is invalid

TFTP/MTFTP Codes

PXE-E32 : TFTP open timeout.
TFTP open request was not acknowledged. Verify that the TFTP service is running.

PXE-E35 : TFTP read timeout.
Next TFTP data packet was not received.

PXE-E36 : Once received from TFTP server.
A packet was received from the TFTP error TFTP server.

PXE-E38 : TFTP generation open connection.
A hardware error occurred when trying to send the TFTP open packet out.

PXE-E39 : TFTP Cohen read from connection.
A hardware error occurred when trying to send a TFTP acknowledge packet out.

PXE-E3A : TFTP too many packages.
This message can mean one of two things :

You are trying to Expo a file using TFTP that is larger than the allocated buffer.
You started downloading a file as a slave 瀹 ㈡ 埗 using MTFTP and the file increased in size when you became the master 瀹 ㈡ 埗.
PXE-E3B : TFTP U.S. C File not found error.
The requested file was not found on the TFTP server.

PXE-E3C : TFTP U.S. C Access violation error.
The request was found on the TFTP file server. The TFTP service does not have enough access rights to open/read the file.

PXE-E3F : TFTP packet size is invalid.
The TFTP packet received is larger than 1456 bytes.


BOOTP/DHCP Codes

PXE-E51 : No DHCP or proxyDHCP offers were received.
The 瀹 ㈡ 埗 did not receive any valid DHCP, BOOTP or proxyDHCP offers.

PXE-E52 : proxyDHCP offers were received. No. DHCP offers were received. .
The 瀹 ㈡ 埗 did not receive any valid DHCP or BOOTP offers. The 瀹 ㈡ 埗 did receive at least one valid proxyDHCP offer.

PXE-E53 : No boot filename received.
The 瀹 ㈡ 埗 received at least one valid DHCP/BOOTP offer, but does not have a boot filename to Expo.

PXE-E55 : proxyDHCP service did not reply to request on port 4011.
The 瀹 ㈡ 埗 issued a proxyDHCP request to the DHCP server on port 4011 and did not receive a reply.


Undi Codes

PXE-E60 : Invalid Undi API function number.
An API being used by the BaseCode is not implemented in the Undi ROM.

PXE-E61 : Media test failed, check cable.
Most likely the cable is not plugged in or connected. Could be a bad cable, Nic or connection.

PXE-E63 : Once while initializing the Nic.
An error occurred while trying to initialize the Nic hardware. Try another Nic.

PXE-E64 : Once while initializing the PHY.
An error occurred while trying to initialize the PHY hardware. Try another Nic.

PXE-E65 : Once while reading the configuration data.
An error occurred while reading the Nic configuration data. Try another Nic.

PXE-E66 : Once while reading the initialization data.
An error occurred while reading the Nic initialization data. Try another Nic.

PXE-E67 : Invalid Mac address.
The Mac address stored in this Nic is invalid. Try another Nic.

PXE-E68 : Invalid EEPROM checksum.
The EEPROM checksum is invalid. The contents of the EEPROM have been corrupted. Try another Nic.

PXE-E69 : Once while setting interrupt.
The interrupt hardware could not be configured. Try another Nic.


Bootstrap and Discovery Codes

PXE-E74 : Bad or missing PXE menu and/or prompt information.
PXE boot menu tags were detected but the tags were not found/valid and/or boot prompt.

PXE-E76 : Bad or missing multicast discovery address.
Multicast discovery is enabled but the multicast discovery address tag is missing.

PXE-E77 : Bad or missing discovery server list.
Multicast and 寤 f 挱 discovery are both disabled, or use server list is enabled, and the tag was not found/valid server list.

PXE-E78 : Could not locate boot server.
A valid boot server reply was not received by the 瀹 ㈡ 埗.

PXE-E79 : NBP is too big to fit in free base memory.
The NBP is larger than the amount of free base memory.

PXE-E7A : Client could not locate a secure server.
This message is displayed when the 瀹 ㈡ 埗 did not receive any information from the boot server and security is enabled on the 瀹 ㈡ 埗 Reuters.

PXE-E7B : Missing MTFTP server IP address.
This message is displayed when the ROM did not receive any PXE discovery tags or proxyDHCP offers and the DHCP Siaddr field is set to 0.0.0.0.

APITest.0 and DOSUNDI.0 Codes

PXE-E81 : !PXE structure is invalid.
The !PXE structure was missing or has been corrupted.

PXE-E82 : PXENV+ structure is invalid.
The PXENV+ structure was missing or has been corrupted.

PXE-E83 : Invalid DHCP option format.
PXE discovery tags in the cached packets is not valid.

PXE-E84 : Could not get pointer to original online storage.
The PXE ROM being used did not return pointers to its local cached online storage. The drive test bootstrap program will not work with this boot ROM.

PXE-E85 : Not enough extended memory.
The size of the RAMdisk image is larger that the available extended memory.

PXE-E86 : ENV RAMdisk image corrupted.
The bootstrap program was expecting a Dos diskette image. The first 512 bytes of the downloaded image did not contain a Dos boot signature.

PXE-E87 : Could not find selected boot item.
The cached discovery packet did not contain a PXE reply boot-item tag (PXE option 71).

PXE-E88 : Could not locate boot server.
The bootserver did not reply to the RAMdisk image discovery request. The RAMdisk image is not on the bootserver or the bootserver service is not running.

PXE-E89 : Could not Expo boot image.
The RAMdisk image could not be downloaded. The RAMdisk image is not on the bootserver or the TFTP service on the bootserver is not running.

Water Codes

PXE-EA0 : Network boot canceled by gained.
User pressed ESC during DHCP/Discovery/TFTP.


BaseCode/UNDI Loader Codes

PXE-EC1 : BaseCode ROM ID structure was not found.
Undi boot module could not find the BaseCode ROM ID structure. If there is a BaseCode ROM image in the system. it has probably been corrupted.

PXE-EC3 : BaseCode ROM ID structure is invalid.
The BaseCode ROM ID structure is invalid. The BaseCode ROM image has probably been corrupted.

PXE-EC4 : Undi ROM ID structure was not found.
The BaseCode loader module could not locate the Undi ROM ID structure.

PXE-EC5 : Undi ROM ID structure is invalid.
The Undi ROM image has probably been corrupted.

PXE-EC6 : Undi driver image is invalid.
The Undi ROM image has probably been corrupted.

PXE-EC8 : !PXE structure was not found in Undi driver code segment.
The Undi ROM image has probably been corrupted. or has not been initialized by the BIOS. This error is caused by one of three most overlooked things :

Nic image was programmed into a BIOS when a. Lom image should have been used.
The memory allocated by the office Memory Manager ($PMM) during PXE option ROM initialization has been corrupted or erased before PXE option ROM boot.
The structure was not properly initialized during UNDI_Loader option ROM initialization.
PXE-EC9 : PXENV+ structure was not found in Undi driver code segment.
The Undi ROM image has probably been corrupted. or has not been initialized by the BIOS. This error is caused by one of three most overlooked things :

Nic image was programmed into a BIOS when a. Lom image should have been used.
The memory allocated by the office Memory Manager ($PMM) during PXE option ROM initialization has been corrupted or erased before PXE option ROM boot.
The structure was not properly initialized during UNDI_Loader option ROM initialization.
And from what I can see, it looks like pxe is some sort of LAN boot-I would check in the bios, and make sure that the bios is seeing your hdd, and that the boot from LAN option is disabled. If your hdd is fucked, boot from LAN might be the 2nd boot option, hence you getting the error message
criminalben 06.08.2006, 17:02
Yeah, defo sounds like the hard drive. You should be able to get a replacement 40GB for less than ?50. Or, you could try calling Topaz on 0******6, i've sent them out of warranty laptops in the past and they've repaired them without charge. No promises though!
blacksheep 06.08.2006, 17:20
Where did you buy it from? and how long ago?
Lou_smorals 06.08.2006, 21:12
Hi
thanks everybody, looking into hard drive. you guys are great.
I bought from PC world april 2005 so warrenty just out!
power supply went after 3 months so they fitted a new hard drive so I was hoping motherboard would still be under warrenty...but they don't give 12 months on parts...
will keep you advised on hard drive but toshiba said the one long beep and 2 short meant motherboard issue.
Thanks lads - Karma shjowered apon you
LOL
LS
I got Hirens - going to try that
Lou_smorals 06.08.2006, 22:42
Hi
ok ran Hirens and cannot find any fault with hard drive. when I get into bios it sees hard drive and DVD rom. I have them in correct order but when I try to get it to boot it still tries to connect to ethernet.
Most times it will not boot at all - just black screen and one long beep and 2 short beeps from motherboard.
thanks again m8s
LS
Lou_smorals 09.08.2006, 23:00
Hi
update time, thanks for all your help. I called Topaz and a few others, most said problem almost certainly motherboard. Quotes aroud the ?200 - ?450 mark for repair.
Found one in Stone, Staffs called Ologic sent to them, they opened up and say bit of fluff in fan and although working, not properly, and CPU had overheated and crack through core.
Total bill ?95+vat.....
I am pretty happy tbh/
thanks again everybody for help
LS
venkata 23.08.2006, 23:20
Just a note, Toshiba have a policy whereby if there is a known fault on their Laptops and that fault occurs, Toshiba give you lifetime warranty on the fault.

Had a tosh laptop which gradually would no longer charge the battery. It was 2 years old, and rang Toshiba CS. They said it was a recorded fault with the model and asked me to send it in for a repair (Free of Charge).
Lou_smorals 23.08.2006, 23:29
Hi
thanks, but getting them to admit that fault is a design fault is very difficult see here ....

They said to me if I took out a 3yr warrenty for ?170 they would fix my laptop - fixed in 48 hours and on it now
thanks again
LS
baby j 20.09.2006, 02:12
when my wife was on the laptop last week my daughter spilled coke over it
and smoke started coming from it, then it packed in i thought i would have to fork out the money on a new one then my wife said it might be covered under the house insurance lucky enought i have cover for accidental damage
so hopeing to get the money back
Similar Threads
HD out of warrenty
360 3 year warrenty
Acer Warrenty Stickers
CTX PL7 Monitor Warrenty Problem
PSP UK + 1GB 225 11 month warrenty & Sandisk duo 1GB 58 delivered
 
Abuse Report - Digital Center - Register - Top
Copyright © 2002-2014, Digital Center. Privacy Policy