Memory Test Failure:

I was digging in my computer drawers for a plastic thing to hold one of my SD cards, and then I found a RAM chip that is 512MB. I need lots of these for the imacs, but I tried to install it, and it didn't work......
It is a Dell Memory. Make your next upgrade Dell Certified Memory. and there is also the sticker with the M with the circle around it and the small OS9-style font and a bar code.
It came with one of my imacs!!!!! It was inside it already. I don't remember if I took it out before or after one of the imacs stopped functioning. (also...could that be the cause of the damage of my first 500mhz imac??????)
I put it in a dark blue 400mhz imac and it has 10.3.9 and 9.2.2 but I have it set to boot into 9.2.2 and it said "Memory Test Failure" or something like that. Everything booted successfully. And then I went to System Profiler. And it did not say 512MB.
My very first mac was a power mac g3 and it had issues. I thought it would be any number of things. I dismantled it. While I did not have any 512 modules (I want and need lots of them) I decided, reluctlantly, to put in some of the 256mb modules in the imac. And...
One of the modules caused the imac to never boot. I took that one out. I put another one of them in and instead of the chime, it there was a sound that was similar length, but it sounded like a common stand-alone analog television not recieving any signals. That static noise with the white "snow"?? It sounded like that. "BZZZZ"!! I took that one out. There are two 256mbs, but I want 2 512mbs,
and...
THAT is what was wrong with the power mac G3?!?!?!?!?!?! I already took it apart, thinking there wasn't anything easily fixable on it!!!! }=S I guess I will put it together again... But that won't happen until I have some more RAM chips... I do not like 64 mb and 128 mb chips. }=S
All 4 of the 256mbs were functioning. I bought them as used, and it said that it will fit in g3s. Why are 2 of the 256mbs not functioning any more???? I once had Tiger on Power Mac g3. It is a blue and white g3. Could Tiger's Dashboard have zapped the ram chips??!!!!!!!
Anyways, for every imac, I would like 2 512 modules. Which ones will work??? Ones that are certified Dell are obviously not. XD
and will dashboard zap the memory?????? I do not have Tiger installed, but if I install it, will it damage the memory????? =S

Which iMac do you have? All iMac G3 models only have two memory slots.
What iMac do you have?
Query by serial number
"A serial number is a unique, identifying number or group of numbers and letters assigned to an individual piece of hardware or software. It's used for various things depending on the product / brand but what is your Mac's serial number for and more importantly... what is it hiding and what can it do for you ?"
http://www.appleserialnumberinfo.com/Desktop/index.php
or
http://www.chipmunk.nl/klantenservice/applemodel.html
( hint by K Shaffer )
You could buy an external DVD drive. It needs to be firewire and bootable by Mac OS. If you have another PPC with firewire, you could try target Disk mode and installed tiger that way.
You need to figure out the level of your firmware before installing 10.2 or greater. ( The PC name for firmware is BIOS. ) Installing 10.2 with a down level firmware will most likely make your iMac unusable and difficult to fix.
Open Firmware, boot into Open Firmware.
Power on your iMac while holding down commandoption+of
The first output line contains the firmware level. Mine reads:
Apple PowerMac4,1 4.1.9f1 BootRom built on 09/14/01 at 13.18.04
Copyright 1994-2001 Apple Computer Inc.
On my machine, I have 4.1.9f1.
What firmware do you need?
http://docs.info.apple.com/article.html?artnum=86117
For a slot loading iMac, this article indicates that you need to be running 9.1 or later version of Mac OS Classic.
http://docs.info.apple.com/article.html?artnum=75130
"The iMac Firmware Update 4.1.9 will only run on iMac computers with lot-loading CD or DVD drives running Mac OS 9.1 or later from a local drive. If you are using Mac OS X you must boot from a local Mac OS 9.1 or later writeable partition (not a CD, or network disk) prior to following the update instructions."
You can download the Mac OS 9 updates from the Apple site.
http://support.apple.com/kb/HT1387?viewlocale=en_US
For tiger, you need 256meg of memory.

Similar Messages

Memory test failure ID 94g95h-0007nq-mfpx1g-003j03 .... What does it mean?

Hi,I ran a memory test because i kept getting Blue screens with different messages such as (memory management failure- bad pool header and other kinds). Once the test began it returned with failure with this id 94g95h-0007nq-mfpx1g-003j03 why is that? and what is the solution? Thank you

The hard drive has failed or is failing fast and will need to be replaced. If you are still in warranty HP will send a replacement. If not a retail laptop SATA hard drive can be used. Just be sure to get one of at least equal capacity as the original in order to use Recovery Discs. It can be larger, but not smaller capacity.For instance you have a 640GB hdd so you could use a 750GB hdd but not a 500GB hdd.
Your Maintenance & Service Guide shows how to replace hdd:
http://h10025.www1.hp.com/ewfrf/wc/manualCategory?cc=us&dlc=en&docname=c03292555&lc=en&product=52530...
******Clicking the Thumbs-Up button is a way to say -Thanks!.******
**Click Accept as Solution on a Reply that solves your issue to help others**

Cisco Aironet 1310 flash memory test

Dear Cisco Support Community
i have a problem on one of my 1310 wireless bridge it is stucked on flash memory test and after resetting the baudrate to 115200
all i see on the bridge is status and Ethernet Leds are blinking green.
Can you please help me?

LED Indications
During access point operation the LEDs provide status information as shown in Table 5-1.
Table 5-1 LED Signals
Message
type
Ethernet
LED
Status
LED
Radio
LED
Meaning
Boot loader status
Green
Green
DRAM memory test.
Amber
Red
Board initialization test
Blinking green
Blinking green
Flash memory test.
Amber
Green
Ethernet initialization test.
Green
Green
Green
Starting Cisco IOS.
Association status
Green
At least one wireless client device is associated with the unit.
Blinking green
No client devices are associated; check the unit's SSID and WEP settings.
Operating status
Green
Blinking green
Transmitting/receiving radio packets.
Green
Ethernet link is operational.
Blinking green
Transmitting/receiving Ethernet packets.
Boot loader errors
Red
Red
DRAM memory test failure.
Red
Red
File system failure.
Red
Red
Ethernet failure during image recovery.
Amber
Green
Amber
Boot environment error.
Red
Green
Red
No Cisco IOS image file.
Amber
Amber
Amber
Boot failure.
Operation errors
Green
Blinking amber
Maximum retries or buffer full occurred on the radio.
Blinking amber
Transmit/receive Ethernet errors.
Blinking amber
General warning.
Configuration reset
Amber
Resetting the configuration options to factory defaults.
Failure
Red
Red
Red
Firmware failure; try disconnecting and reconnecting unit power.
Firmware upgrade
Red
Loading new firmware image.
Controller status
Alternating green, red, and amber1
Connecting to the controller. Note If the access point remains in this mode for more than five minutes, the access point is unable to find the controller. Ensure a DHCP server is available or that controller information is configured on the access point.
Message
type
Ethernet
LED
Status
LED
Radio
LED
Meaning
1 This status indication has the highest priority and overrides other status indications.

865PE NEO2 FSIR fails memory tests

This is the second MB that I've had this problem with, so something is causing them to fail. Here's the story:
New install, 865PE Neo2 FSIR + P4 2.6GHz 800MHz FSB, 2 x Crucial PC3200 256MB DDR, everything seems ok, XP installs with no problems.
About a month down the road I'm plagued by sudden reboots, Microsoft Error Reporting says RAM, says to DL and run it's DOS memory check utility. I get the utility, create bootable CD and run the utility, computer fails all RAM checks. I pull each RAM stick in turn and re-run the check with each stick separately, still fails all tests. Shortly after this, the board refuses to POST. Ship the board back to New Egg for replacement.
Installed replacement MB with 4 x 256MB Crucial PC3200, Microsoft DOS memory check program passes, no problems. About 2 weeks later I run into minor instability so I run the same memory check again, the board fails all tests????? I pull all Crucial memory sticks and put in a test stick of Corsair XMS 3200; same result, failure of all memory tests.
At this point, WinXP still runs, but this is the same pattern that the other board showed, right until it quit altogether.
It occurs to me that I DID flash BIOS to 1.9 between the time I first tested the RAM and got a pass and the time I tested and got a failure, could this be a coincidence? I can't remember if I updated the BIOS on the first board or not, so this may mean nothing.
System Specs:
MSI 865PE NEO2 FSIR
P4 2.6GHz, 800MHz FSB (all defaults, no overclock, Vantec HS)
Crucial CT3264Z40B.8T PC3200, CL3 256MB (2 Modules)
Crucial CT3264Z40B.8T2 PC 3200, CL3 256MB (2 Modules)
(Tested with same results with single Corsair CMX512-3200C2PT 512MB)
Antex True Power 430W PS
ATI Radeon 9600 Pro
All PCI slots open
Seagate 120GB System drive, 7,200RPM primary master
IBM 30GB drive, 7,200RPM primary slave
LiteOn DVD ROM secondary master
Sony CDRW secondary slave
2 x IBM 30GB drives on Promise PATA.
I know I'm probably gonna have to RMA this board, but I'd really like to know what is causing this so I can avoid it next time.
If anyone has any ideas I'd sure appreciate it.
Scott

Quote
Originally posted by jwspicer
As they say - been there, done that. Always flash using DOS, and always keep backup, so I went back to the original BIOS for the board. No luck. Apparently once the screwup is done - it stays that way.
--BUT--
Suspect it is the reallocation for the P4 EE that is the issue. Reason is that Memtest86 has been running on that box for 9 hours now with NO error. However, it also shows only 104K of reserved memory. My other 865 board with onboard RAID (an ASUS P4P800 Deluxe) shows 687K reserved. So either the ASUS is wasting a lot of space, or the MIS is no longer correctly indicating the amount of memory reserved by the BIOS (including the Promise BIOS) at startup. Then Microsoft's utility is not correctly scanning. But Memtest, which probes for the "correct" setting, is. (The Memtest86 version is 3.0, and the test was done with the Promise enabled and drives attached (so the BIOS loads) and all the other setup was as it would be normally (standard IBOS options, etc.)
So who's right? And if MS' tool has the problem, does that indicate Windows XP reads memory the same way? Hmmm...
Hmm, I haven't tried reverting BIOS, but I'm typing this on the affected machine (which Memtest 86 says is fine) with only the two RAM chips it likes and so far no problems; I've run PCMark4 and 3DMark4 benchmarks all night and no problems, it was still happily churning away on 3DMark this morning. I guess either one of the Crucial sticks it doesn't like is bad or Crucial changed something in a revision to the chips it doesn't like.
Just a FYI, the Crucial sticks it DOESN'T like are CT3264Z40B.8T2
The sticks it DOES like (at slow or fast performance, forget about turbo or ultra turbo) are CT3264Z40B.8T
Both pairs are PC3200, CL3, 256MB DIMM's, single sided.
I think you're right about Microsoft's RAM tester being buggy, I can't believe ANYTHING could run if the RAM was actually giving the errors it shows, EVERY test shows things like "expected result 11111111 actual result ff1e0001" The Microsoft tester does run fine on the other 5 computers here; a mix of laptops and desktops; none using this board. It also ran on this board when it was installed, I guess the BIOS upgrade must be the cause.
Scott

HP Pavilion DV7; System will not boot; Memory Test Failed using Advanced System Diagnostics

Not sure exactly how, but I managed to contracted several variants of the nasty Rovnix virus and now my system will not even boot into Safe Mode after trying to restore to several different restore points. Enabled bootlogging, but not sure how to retrieve the log.
Currently am able to get into HP Advanced Diagnostics and began Start-Up Test. Test failed on Memory Module:
Failure ID: Q0AE6C-5LS79T-MFH15G-406N03
Any next steps or directional assistance would be greatly appreciated. Thank you in advance!

Hello @GarrettBishop,
Welcome to the HP Forums, I hope you enjoy your experience! To help you get the most out of the HP Forums I would like to direct your attention to the HP Forums Guide First Time Here? Learn How to Post and More.
I have read your post on how your notebook computer has failed a memory test in the advanced system, and I would be happy to assist you in this matter!
Since the Failure ID has come up with Q0AE6C-5LS79T-MFH15G-406N03, I recommend contacting our technical support at 800-474-6836. If you live outside the US/Canada Region, please click the link below to get the support number for your region.
http://www8.hp.com/us/en/contact-hp/ww-phone-assist.html
I hope this helps!
Regards
MechPilot
I work on behalf of HP
Please click “Accept as Solution ” if you feel my post solved your issue, it will help others find the solution.
Click the “Kudos, Thumbs Up" on the right to say “Thanks” for helping!

[svn:fx-trunk] 7728: Reverting change 7716 after it caused a bunch of test failures.

Revision: 7728
Author:   [email protected]
Date:     2009-06-10 14:58:37 -0700 (Wed, 10 Jun 2009)
Log Message:
Reverting change 7716 after it caused a bunch of test failures.
Modified Paths:
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/common/MxmlConfiguration.java

Did I understand you right that you said that even using a PCI NIC in those systems gave the same errors? That would likely mean that any corruption is in the hardware... the nForce4 chipset or Hypertransport or maybe even mbrd traces? I think there are enough systems out there running satisfactorily that that is not a viable explanation: Hypertransport errors would cause all kinds of hard disk problems as well as with other I/O devices. Are you sure that nothing is (unintentionally) overclocked and have you checked the memory with Orthos http://sp2004.fre3.com/beta/beta2.htm?
There are a couple of things about the nForce NI though: most important is that the TCP offloading is broken and I've had to disable Checksum Offloading and Segmentation Offloading in the Advanced Properties of the nForce Network Controller in Device Manager. This also means that the Active Armor is broken and consequently the nVidia Firewall and NAM (Network Access Manager) are useless. IOW if NAM is installed get rid of it - I've no idea what it might do with other NIs installed in the system... hopefully nothing but then.......
A couple of points to clear up: 1) are you only getting the errors on an internet connection and LAN connections work OK? 2) What are those nForce systems connected to... a hub or switch and through to a router? 3) I'm not sure what "outbound packet errors" means - is it due to the OS seeing that the packets are malformed before they go to the NI, or is it due to the NI getting error responses from the device on the other end of the "wire"?

HP Pavilion g6: Memory test fail id - U0E17L-5SV7NP-MFGH4K-406W03

Hi,I have a HP Pavilion g6 Notebook (Prodect id - QC399AV).The laptop is not booting and, I get a message "Windows failed to start. A rececnt hardware or software might be the cause" On doing a memory test, I get following failure id - U0E17L-5SV7NP-MFGH4K-406W03. The Hard disk test had passed. Can any on let me know what this error means, and how i can fix this. Do let me know if this is related to Operating system, and if i have to reinstall them. I am not able to do a factory reset (as Laptop does not boot), let me know how i can get the operating system image in DVD/USB. Thanks,Sujesh Prasannan

Hi,
Your notebook is listed as coming with a 500Gb ( 5400rpm ) Hard Drive, but you may as well replace this with a 500Gb ( 7200rpm ) HDD as there's no real difference in cost and it'll give you a bit more performance - the drive on the following link is an example that would be fine for your notebook.
500Gb Hard Drive
The procedure to replace the Hard Drive starts on Page 53 of your Maintenance & Service Guide.
Once done, simply use your Recovery DVDs to reinstall the Operating System on the new drive - this procedure is described in the HP document Here.
If you don't have your Recovery Discs, you can order a replacement set using the link below.
Order HP Recovery Discs.
If you have any problem with this link, order them directly from HP.
If you live in the US, contact HP Here.
If you are in another part of the world, start Here.
Regarding the battery, my best advice would be to replace the HDD first and get everything up and running - you can then use the utility on the following link to see if there's any issue with your current battery.
http://h20239.www2.hp.com/techcenter/battery/battery_ts.htm
Best regards,
DP-K
****Click the White thumb to say thanks****
****Please mark Accept As Solution if it solves your problem****
****I don't work for HP****
Microsoft MVP - Windows Experience

V120 Fails Core Memory Test

I have a V120 which will not get past the Core Memory Test. I have tried installing a different 256MB DIMM card into all 4 slots to no avail. The system recognizes when and in which slot the card is installed, but I am getting the same error message.
Any recomendations would be appreciated.
Thanks

No, It is not making it past the LOM to get to the console at all. The only way of seeing the memory failure is by setting the bootmode to diag. The boot up just hangs after the memory test until I return to the LOM prompt.

Start-Up Test failure on Pavilion DV6

I have a Pavilion dv6 and it has developed what appears to be a hard drive problem.
It usually starts OK but has started crashing and then trying to repair the hard drive.
I have run the Start-Up Test and it failed as per below:
Memory test: PASSED
SMART Check: PASSED
Short DST: FAILED
FAILURE ID: RLL7HH-5KJ71D-MFH14J-60RW03
PRODUCT ID: LR733PA#ABG
HARD DISK DETAILS:
Toshiba MK6465GSX
HP P/N: 594920-001
260GB.
Is this simply a hard disc failure, or something more serious.
P.S. I have found that if I remove the battery pack for several minutes, the computer will start and run OK for upto 15 minutes..

Typically, a failed Short DST is an indication that the hard drive has failed or is about to fail. This is most likely a simple hard drive failure and not a sign of anything more serious. Replacing the drive with a new 640GB or larger drive should solve your issue. Once you install the new drive, you will need to use the HP Recovery Media you previously created to retun the computer to a factory like condition.
If you have any further questions, please don't hesitate to ask.
Please click the White KUDOS "Thumbs Up" to show your appreciation
Frank
{------------ Please click the "White Kudos" Thumbs Up to say THANKS for helping.
Please click the "Accept As Solution" on my post, if my assistance has solved your issue. ------------V
This is a user supported forum. I am a volunteer and I don't work for HP.
HP 15t-j100 (on loan from HP)
HP 13 Split x2 (on loan from HP)
HP Slate8 Pro (on loan from HP)
HP a1632x - Windows 7, 4GB RAM, AMD Radeon HD 6450
HP p6130y - Windows 7, 8GB RAM, AMD Radeon HD 6450
HP p6320y - Windows 7, 8GB RAM, NVIDIA GT 240
HP p7-1026 - Windows 7, 6GB RAM, AMD Radeon HD 6450
HP p6787c - Windows 7, 8GB RAM, NVIDIA GT 240

System failed memory test

I am really new to Solaris so please forgive me if I sound really dumb. I was able to install Solaris 10, turned off my computer and now all I recieve is System failed memory test. Please help have tried different memory sticks and still recieve the same message.

is this a bios message? id suggest running a mem test if this is coming before the os starts up [http://www.memtest.org/]
if you have the mother board diag tools on cd, run those as well. unless this is a sparc system?

MS 6507 Wont stop memory testing

I have a new (yes i know it is old) MS6507 mobo with a PIV 1.8GHz, 512MB (2 x 256MB) GeForce2 MX440 64MB
When i power it on all that happens is the Bios details are shown along with the CPU spec.
The memory test runs through, when it reaches the max memory it restarts to count again. This is all that happens until power is switched off.
The "esc & del" keys are not active in fact the keyboard has the "Caps / Num & Scroll" lights on all the time.
I have replaced memory, keyboard as well as disabled HDD and Optical drives and still have the same problem.
I have tried resetting the CMOS settings.
Do i have a dead mobo?
regards
Tony

I dont think so, I just think that the Memory Check-Sum Option in the BIOS is either Stuck in the Check Memory Loop, or you have a Bad RAM Module, Have you tried to BOOT with a Different Memory Module?...........Sean REILLY875

MacBook Pro 2,2 won't pass memory test at boot

Hi Apple and Mac folks,
I have a MacBook Pro 2,2 15", 2007 year model, equipped with 2,16 GHz Intel Core 2 Duo and 2 GB 667 Mhz factory-installed DDR2 SDRAM, running Mac OS X 10.4.11. SMC version is 1.12f5.
Three months ago, when I was installing the Safari beta and the installation requested a reboot, the machine wouldn't start at all. It didn't give me any startup chime; the only thing to be heard was the initial movement from the DVD scanning mechanism (?), but after that nothing happened. If I waited for a while I could assume that the CPU was working, since I could hear the fans spinning up. But the screen was black and the computer wouldn't load any CDs or DVDs or even listen to any keyboard commands. The only thing that was working was the force shutdown by the 10-second press on the start button.
After some trial and error I realized that the system would reboot without problems if I let it rest (cool down?) for about 15 minutes. Sometimes, connecting an external hard drive via FireWire would also help the system to start up, bit it seemed to work rather randomly.
I ran the Apple hardware test and it reported an error on one of the SDRAM modules the first time I checked, but running the more thorough test wouldn't report any error and the system didn't show any signs of errors whatsoever once it was up and running.
I have also tried to reset PRAM and SMC, but it does not alleviate the reboot problem.
Since I then suspected that I had a faulty memory module I decided to upgrade the system with 2 Kingston DDR2 2GB SODIMM modules (yes, I know it only supports 3GB of memory, but I wanted the modules to work in pair). Unfortunately, the system exhibits the same problems with the new modules, and now things are getting even worse - now the 15-minute cool down period does not seem to be sufficient to get the system to pass (as I suspect) the initial memory test.
Last night I had to fiddle around, switching memory modules around in the slots to get the system restarted. I could get it rebooted once with one of the older 1 GB modules in the upper slot, and once it rebooted with an older module in the lower slot. Things seemed to act quite randomly and the previous cooling period method didn't seem to make any difference. Finally, I sort of gave up and put back the two new 2 GB modules and tried a last restart while having an external hard drive attached via FireWire and then it gave me the chime and restarted!
My interpretation of the problem is that the system has some kind of glitch (maybe not the correct term for a small gap in the circuits?) in the circuits connecting one or both of the SODIMM modules and that this glitching is getting worse as the system grows older.
So, I have three questions to you:
1. Is there any way to turn off or circumvent the initial memory check, so that I can temporarily live with this problem and not risk having an unusable system at next reboot?
2. Have you heard about this kind of problem before and maybe have knowledge about what part of the system that would have to be replaced and what it will cost me if I bring the computer to a service station (I'm located in Sweden).
3. Are there any SMC or EFI updates I should try before going to service?
Thanks for any help on this,
Ulf

cornelius wrote:
The firewire bridge is the most likely component in a FW HDD to fail. I have seen it a few times, and all that was needed was to remove the drive from the case and place it in a new firewire enclosure. I insist on getting an enclosure with an Oxford chipset, as they are the most reliable.
Hi again Cornelius,
first of all, thanks for the support in the struggle troubleshooting this issue.
Secondly, I don't think the problems has to do with the cabinet of the externa FW drive, but rather the problem would be located in the FW port in the computer.
Doing some research today, I found indications on that the AHT actually is installed on the hard drive of MacBooks after 2007. So, I decided to see if I could launch the AHT from my internal hard drive. Reboot needed, so hold your thumbs...
Reboot. Dead computer. Attached firewire disc. Dead computer. Let computer rest and cool down for half an hour. Restart -> dead computer. Connected firewire drive -> chime and boot!
Pressed D to load ATH. System gave me a dimmed screen with a text box telling me that I had to reboot the computer. I gave OK to that and the computer restarted normally, but reported an abnormal shutdown and gave me the opportunity to send a report about a kernel panic to Apple.
When the system came up the attached FW disc was not reachable. Looking in the system log, I find the following error message repeated:
Jun 26 16:24:49 Ulf-Kronman kernel[0]: FireWire GUID ffffffffffffffff is invalid!
The research on the net is getting me more and more confused: Is the ATH really located on the hard drive of MacBooks? Is the Power On Self Test really run at reboot? According to this wikipedia note (http://en.wikipedia.org/wiki/Power-on_self-test) the test is not run at reebot:
" Apple's Macintosh computers also perform a POST after a cold boot. In the event of a fatal error, the Mac will not make its startup chime. "
But my problems occur both when I cold start and when I reboot.
Isn't a lack of chime a very un-Apple-like way of reporting an error? Where/how can I get some more information about what's going on before the chime? And how do I know if the Self Test is run or not? System profiler only reports that self-test at start hasn't found any errors, but only when the system starts (due to that it not has found any errors )
Somewhere I saw instructions for doing a
Terminal> sudo nvram boot-args="-x -v"
to get a report of whats going on during startup. Could that be a way to proceed or is there a leaner way to get info out of the self test?
I'll continue to some research on the FireWire GUID, whatever that is.
Regards,
Ulf

Error message when trying to recover HD: PXE-E61 Media test failure

Hi all, new to forums, lots of good info and support here.
Got the BSOD last week. Have been trying all of the various fixes mentioned on the board, to no avail. I went back multiple pages looking for alternatives to try. After stepping away for a few days, I got farther today than I did when I was frustrated. F12, chose to boot HDD, and got the following LOOPING error message:
PXE-E61 Media test failure check cable
PXR-MDF exiting PXE rom
Which gives me hope that I may not have to replace my hard drive.
I have a satellite L455-5975, and have ordered recovery disc from acclaim ('0' option didn't work for me, which makes me wonder if Toshiba time limits that support, but that's off topic)
So it looks to me like my RealTek Ethernet Controller might be the problem? Any thoughts or suggestions? Anything I can do or should I wait for recovery disk to arrive? I worry that the recovery disk isn't going to do what I need. Do I need to replace the ethernet controller, or is this a sign of a hard drive issue? I consider myself 'fairly' tech savvy, but I've never taken a computer apart/put one together myself. It would definitely cost less for me to replace HD myself than putting it in the shop. So I'm willing to try that option if need be.
I appreciate any help/support! Reading some of the previous posts make me wonder if rather than investing more money in the satellite, if I shouldn't instead be saving up to buy a new(er) model.

Creedym...
I have a very similar problem with my mini-notebook model NB305.
I'm getting the same message and can't get past F2 or F12.
Bottom line; I ordered the recovery data from Toshiba on-line by model number ---not by type. They sent two DVDs. My unit doesn't have an optical drive.
First call to "John"---yes, you can copy the data to a thumb drive and use that.
Almost two hours of transferring --- the NB305 did not respond to the thumb drive.
Second call to "Paul". After some consultation on his part with someone else he told me that they don't make a thumbdrive (USB) recovery disk for my model, that's why I received two DVDs. ! I would have take it to a shop where they etc...
I haven't decided what to do next. Maybe purchase an external drive rather than take it to a repair shop where it will probably cost more than buying an inexpensive external drive.
t.

ICMP Timeout Alarm due to TCP Protocol Memory Allocation Failure ?

Hello Experts ,
>> Device uptime suggests there was no reboot
ABCSwitch uptime is 28 weeks, 13 hours, 50 minutes
System returned to ROM by power-on
System restarted at 13:09:45 UTC Mon Aug 5 2013
System image file is "flash:c2950-i6k2l2q4-mz.121-22.EA12.bin"
>> But observed logs mentioning Memory Allocation Failure for TCP Protocol Process ( Process ID 43) due to Memory Fragmentation
003943: Feb 18 02:14:27.393 UTC: %SYS-2-MALLOCFAIL: Memory allocation of 36000 bytes failed from 0x801E876C, alignment 0
Pool: Processor Free: 120384 Cause: Memory fragmentation
Alternate Pool: I/O Free: 682800 Cause: Memory fragmentation
-Process= "TCP Protocols", ipl= 0, pid= 43
-Traceback= 801C422C 801C9ED0 801C5264 801E8774 801E4CDC 801D9A8C 8022E324 8022E4BC
003944: Feb 18 02:14:27.397 UTC: %SYS-2-CFORKMEM: Process creation of TCP Command failed (no memory).
-Process= "TCP Protocols", ipl= 0, pid= 43
-Traceback= 801E4D54 801D9A8C 8022E324 8022E4BC
According to Cisco documentation for Troubleshooting Memory issues on Cisco IOS 12.1 (http://www.cisco.com/c/en/us/support/docs/ios-nx-os-software/ios-software-releases-121-mainline/6507-mallocfail.html#tshoot4 ), which suggests the TCP Protocols Process could not be started due to Memory being fragmented
Memory Fragmentation Problem or Bug
This situation means that a process has consumed a large amount of processor memory and then released most or all of it, leaving fragments of memory still allocated either by this process, or by other processes that allocated memory during the problem. If the same event occurs several times, the memory may fragment into very small blocks, to the point where all processes requiring a larger block of memory cannot get the amount of memory that they need. This may affect router operation to the extent that you cannot connect to the router and get a prompt if the memory is badly fragmented.
This problem is characterized by a low value in the "Largest" column (under 20,000 bytes) of the show memory command, but a sufficient value in the "Freed" column (1MB or more), or some other wide disparity between the two columns. This may happen when the router gets very low on memory, since there is no defragmentation routine in the IOS.
If you suspect memory fragmentation, shut down some interfaces. This may free the fragmented blocks. If this works, the memory is behaving normally, and all you have to do is add more memory. If shutting down interfaces doesn't help, it may be a bug. The best course of action is to contact your Cisco support representative with the information you have collected.
>>Further TCP -3- FORKFAIL logs were seen
003945: Feb 18 02:14:27.401 UTC: %TCP-3-FORKFAIL: Failed to start a process to negotiate options.
-Traceback= 8022E33C 8022E4BC
003946: Feb 18 02:14:27.585 UTC: %TCP-3-FORKFAIL: Failed to start a process to negotiate options.
-Traceback= 8022E33C 8022E4BC
003947: Feb 18 02:14:27.761 UTC: %TCP-3-FORKFAIL: Failed to start a process to negotiate options.
-Traceback= 8022E33C 8022E4BC
003948: Feb 18 02:14:27.929 UTC: %TCP-3-FORKFAIL: Failed to start a process to negotiate options.
-Traceback= 8022E33C 8022E4BC
003949: Feb 18 02:14:29.149 UTC: %TCP-3-FORKFAIL: Failed to start a process to negotiate options.
-Traceback= 8022E33C 8022E4BC
According to Error Explanation from Cisco Documentation (http://www.cisco.com/c/en/us/td/docs/ios/12_2sx/system/messages/122sxsms/sm2sx09.html#wp1022051)
suggests the TCP handles from a client could not be created or initialized
Error Message %TCP-3-FORKFAIL: Failed to start a process to negotiate options.
Explanation The system failed to create a process to handle requests from a client. This condition could be caused by insufficient memory.
Recommended Action Reduce other system activity to ease memory demands.
But I am still not sure about the exact root cause is as
1.The GET/GETNEXT / GET BULK messages from SNMP Manager (Here, IBM Tivoli Netcool ) uses default SNMP Port 161 which is
   UDP and not TCP
2. If its ICMP Polling failure from IBM Tivoli Netcool , ICMP is Protocol Number 1 in Internet Layer of TCP/IP Protocol Suite and TCP is Protocol                 Number 6 in the Transport Layer of TCP/IP Protocol Suite .
So I am still not sure how TCP Protocol Process Failure could have caused ICMP Timeout . Please help !
Could you please help me on what TCP Protocol Process handles in a Cisco Switch ?
Regards,
Anup

Hello Experts ,
>> Device uptime suggests there was no reboot
ABCSwitch uptime is 28 weeks, 13 hours, 50 minutes
System returned to ROM by power-on
System restarted at 13:09:45 UTC Mon Aug 5 2013
System image file is "flash:c2950-i6k2l2q4-mz.121-22.EA12.bin"
>> But observed logs mentioning Memory Allocation Failure for TCP Protocol Process ( Process ID 43) due to Memory Fragmentation
003943: Feb 18 02:14:27.393 UTC: %SYS-2-MALLOCFAIL: Memory allocation of 36000 bytes failed from 0x801E876C, alignment 0
Pool: Processor Free: 120384 Cause: Memory fragmentation
Alternate Pool: I/O Free: 682800 Cause: Memory fragmentation
-Process= "TCP Protocols", ipl= 0, pid= 43
-Traceback= 801C422C 801C9ED0 801C5264 801E8774 801E4CDC 801D9A8C 8022E324 8022E4BC
003944: Feb 18 02:14:27.397 UTC: %SYS-2-CFORKMEM: Process creation of TCP Command failed (no memory).
-Process= "TCP Protocols", ipl= 0, pid= 43
-Traceback= 801E4D54 801D9A8C 8022E324 8022E4BC
According to Cisco documentation for Troubleshooting Memory issues on Cisco IOS 12.1 (http://www.cisco.com/c/en/us/support/docs/ios-nx-os-software/ios-software-releases-121-mainline/6507-mallocfail.html#tshoot4 ), which suggests the TCP Protocols Process could not be started due to Memory being fragmented
Memory Fragmentation Problem or Bug
This situation means that a process has consumed a large amount of processor memory and then released most or all of it, leaving fragments of memory still allocated either by this process, or by other processes that allocated memory during the problem. If the same event occurs several times, the memory may fragment into very small blocks, to the point where all processes requiring a larger block of memory cannot get the amount of memory that they need. This may affect router operation to the extent that you cannot connect to the router and get a prompt if the memory is badly fragmented.
This problem is characterized by a low value in the "Largest" column (under 20,000 bytes) of the show memory command, but a sufficient value in the "Freed" column (1MB or more), or some other wide disparity between the two columns. This may happen when the router gets very low on memory, since there is no defragmentation routine in the IOS.
If you suspect memory fragmentation, shut down some interfaces. This may free the fragmented blocks. If this works, the memory is behaving normally, and all you have to do is add more memory. If shutting down interfaces doesn't help, it may be a bug. The best course of action is to contact your Cisco support representative with the information you have collected.
>>Further TCP -3- FORKFAIL logs were seen
003945: Feb 18 02:14:27.401 UTC: %TCP-3-FORKFAIL: Failed to start a process to negotiate options.
-Traceback= 8022E33C 8022E4BC
003946: Feb 18 02:14:27.585 UTC: %TCP-3-FORKFAIL: Failed to start a process to negotiate options.
-Traceback= 8022E33C 8022E4BC
003947: Feb 18 02:14:27.761 UTC: %TCP-3-FORKFAIL: Failed to start a process to negotiate options.
-Traceback= 8022E33C 8022E4BC
003948: Feb 18 02:14:27.929 UTC: %TCP-3-FORKFAIL: Failed to start a process to negotiate options.
-Traceback= 8022E33C 8022E4BC
003949: Feb 18 02:14:29.149 UTC: %TCP-3-FORKFAIL: Failed to start a process to negotiate options.
-Traceback= 8022E33C 8022E4BC
According to Error Explanation from Cisco Documentation (http://www.cisco.com/c/en/us/td/docs/ios/12_2sx/system/messages/122sxsms/sm2sx09.html#wp1022051)
suggests the TCP handles from a client could not be created or initialized
Error Message %TCP-3-FORKFAIL: Failed to start a process to negotiate options.
Explanation The system failed to create a process to handle requests from a client. This condition could be caused by insufficient memory.
Recommended Action Reduce other system activity to ease memory demands.
But I am still not sure about the exact root cause is as
1.The GET/GETNEXT / GET BULK messages from SNMP Manager (Here, IBM Tivoli Netcool ) uses default SNMP Port 161 which is
   UDP and not TCP
2. If its ICMP Polling failure from IBM Tivoli Netcool , ICMP is Protocol Number 1 in Internet Layer of TCP/IP Protocol Suite and TCP is Protocol                 Number 6 in the Transport Layer of TCP/IP Protocol Suite .
So I am still not sure how TCP Protocol Process Failure could have caused ICMP Timeout . Please help !
Could you please help me on what TCP Protocol Process handles in a Cisco Switch ?
Regards,
Anup

HP Pavilion g6-2330dx. "No Boot Device. Insert boot disk and press any key" Memory test failed

Hi. So I am trying to help a friend with her laptop. It's a HP Pavilion g6-2330dx.
Product #: D1C01UA#ABA
Serial #: [Personal Information Removed]
Windows 8
ADATA 4GB RAM
Toshiba 640GB HDD from the looks of it.
The laptop is unable to boot into Windows, so I suspect the hard drive. But I ran the hard drive test and it passed all the tests. The SMART test and both the short and long test. I ran the tests multiple times and it passed each time. I tried reseating the hard drive and still no go. I also removed the HDD and connected it to my desktop PC to see if it detects and it did. Ran the Windows 7 own HDD test and it passed.
Currently, there doesnt seem to be any operating system at all on the HDD. When I check, there is a C: drive of ~90GB partition that is ~90GB free, but inside there are Windows files/folders. There is also a D: drive Recovery partition that says ~26GB with only ~2GB free, but when I go inside there's only ~350MB worth of data.
So then I ran the memory test (in BIOS) and it failed immediately. I reseated the RAM module. I tried the other slot. It still failed. So is it safe to say the memory is the cause of this problem?
Pressing the F11 key that is supposed to take me to the System Recovery only leads me back to the black screen with "No Boot Device. Insert boot disk and press any key"
I even tried to install Windows 7 to see if it'll work. I was able to get the laptop to boot/read off the Windows 7. But when I click to install, it asks for a boot device driver or something like that.
My friend doesn't have the recovery disk either. I guess she lost it.
Anyway, is it as simple as replacing the memory or could it actually be the HDD (even though it passes)?
EDIT: This is what the System Log in BIOS says
0021           Time: 10/13/2014
03F0           Time: 10/13/2014
03F0           Time: 10/13/2014
The date was the first time I ran the tests. I havent received those numbers (error codes?) since.
EDIT: Just for kicks, I ran Memtest 2.11 just now (forgot I had the disc) and it immediately went red with thousands of errors, hah.

Hi bghs,
Welcome to the HP Forums!
It is a fantastic place to find answers and information.
For you to have the best experience in the HP forum I would like to direct your attention to the HP Forums Guide Learn How to Post and More
I understand that you were unable to boot into Windows, and you suspected the hard drive and tested it, but it passed both short and long test. With that being said and the fact that it also passed leads me to believe the hard drive is fine.
You tested the memory and it failed. You tried reseating and swapping slots but they still failed the test.
I would test each card individual with the memtest to determine if it is just one or both cards that have an issue.
When you installed it in another computer, you did see the recovery partition. Once the memory issue is resolved, if you are still unable to boot into Windows, I suggest you do a recovery with the minimized image.   Here is a link to Performing an HP System Recovery (Windows 8) to assist you with that process.
I hope this helps.
Sparkles1
I work on behalf of HP
Please click “Accept as Solution ” if you feel my post solved your issue, it will help others find the solution.
Click the “Kudos, Thumbs Up" on the bottom right to say “Thanks” for helping!

Memory Test Failure:

Similar Messages

Maybe you are looking for