Hardware clocking error # 200550, PCI-5122

The PCI-5122 does not pass the self test. It
says "error 200550 occured. Possible reason: Hardware clocking error
occured". I'm not using any external clock and my PC is 3Ghz pentium
with Windows XP and Labview 7.0. Uninstall/install of NI_Scope and NI DAQmx didn't
help.
By the way, if I put PCI-5911 card instead of PCI-5122 into the same PCI slot, it works fine.

Hello Danraz,
It sounds like you have followed all of the recommended steps for troubleshooting for this type of error. As one additional step you could test it in another PC if you have one available. Unfortunately, you will most likely need to send your board in for repair. Please contact support to make arrangements. You will be asked to provide them the serial number of your board in order to have the board repaired, and they may also verify your troubleshooting steps at this time.
Regards,
Jennifer O.
Product Support Engineer - High Speed Digitizers

Similar Messages

Hardware Clocking Error PCI-5122

I tried to run the vi attached (which i've run many times before) and my computer bluescreen. When it rebooted, I could no longer use my PCI-5122 digitizer card. When I try to do a device test or device reset in MAX, it tells me that theres a hardware clocking error.. I was using an external trigger for the aquisition, but don't think I was using an external reference clock. Could someone help me fix this?
Thanks
NI Hardware: PXI-7853R, PCI-5122, PCI-6733, PXI-1036, PCI-MIO-16E-4, PCI-6110
Computer Hardware: Xeon Quad Core - 2.33 Ghz, 8 GB RAM
Software: Labview 2009, Labview FPGA 2009, Vista 64-bit, MAX 4.6, DAQmx 9.0, NI-SCOPE 3.5
Solved!
Go to Solution.
Attachments:
OPO Monitor.vi ‏53 KB

Hi,
This error may be the result of a hardware failure where the only
solution is a repair or replacement. There are however, some basic
troubleshooting steps that have been known to correct this issue
without a return.
Reboot the PC or PXI controller.
Try a different PCI or PXI slot.
Update the driver to the latest version.
If possible try the card on a different machine.
If these steps to not correct the issue then it is likely the
board requires repair which can be arranged by contacting National
Instruments Technical support (in france: 01 57 66 24 24).
Best regards,
Thomas B. | CLAD
National Instruments France
#adMrkt{text-align: center;font-size:11px; font-weight: bold;} #adMrkt a {text-decoration: none;} #adMrkt a:hover{font-size: 9px;} #adMrkt a span{display: none;} #adMrkt a:hover span{display: block;}
>> Inscrivez-vous gratuitement aux Journées Techniques : de l'acquisition de données au contrôle/com...

DAQmx Error -200550

Currently I have a PXI-1000B, and I have opnly ever used the same card in the same slot. I have a much faster sampling card and I'd like to try it out but I receive this error message when trying to use it. The interesting problem is that there is a exact duplicate of the card that I am using right now in another slot and it also does not work, giving the same error message. I did not setup the lab so I don't know if there was a procedure to make the one slot operational that the other haven't recieved. Do I need to set up the clock somehow?
DAQmx Error -200550 occurred:
Hardware clocking error occurred.
If you are using an external reference or sample clock, make sure it is connected and within the jitter and voltage level specifications. Also, verify that its rate matches the specified clock rate. If you are generating your clock internally, please contact National Instruments Technical Support.
Status Code: -200550
Thanks

Hopefully this covers everything:
We have a NI PXI-1000B crate & several digitizer modules (2 PXI-5122 and 1 PXI-5152) in our lab. We have been heavily using one of the PXI-5122 with no problems, but need to move on to using the faster PXI-5152.
We find that we cannot read out either the 2nd 5122 or the 5152. They both consistently fail with "hardware clocking - error 200550". This occurs both while attempting to test the cards in MAX as well as while trying to sample with them. There is one difference between the errors, when rebooting the system, when the drivers access the cards the 5122 cards behave in the same way with green lights, however the 5152 flashes a red light before resuming a green light for access.
We have swapped modules and slots. Both the bad 5122 and the 5152 produce the same error in different slots, including the one the good 5122 normally operates in. We have also moved the good 5122 and it works fine in different slots, including the ones the bad modules fail in.
The bad 5122 was once repaired (replaced fuse) at NI for the same problem, but we have no history of repairs to the 5152. We "inherited" this setup from a technician who is now in another lab but reachable, so we don't know the exact history of the set-up.
It seems strange that both bad modules exhibit the same error. We're happy to try any other suggested tests here before sending them for repair. Any suggestions would be much appreciated.

PCI-5122 Unregistered error -218802

Hi,
I am using the digitizer PCI-5122 (256 MB / channel) with Labview 8.2, NI-Scope 3.4 and windows XP.
Starting off with the NI example "niScope EX Multi Record Fetch More Than Available Memory.vi"
everything was running fine first, but now I encounter a problem with the following configuration:
sample rate: 20 MHz
external trigger (to start a record): 20 kHz
min record length: any (I tried 1 or 1000)
number of records: larger than 105,000 (the error does not occur for values < 100,000)
The error message reads as follows:
> Error occurred at: niScope Multi Fetch Cluster.vi:1
> <err>Driver Status: (Hex 0xFFFCA94E)
> Unregistered error -218802 occurred:
> No error occurred.
>
> Component Name: nimxslu proxy
> File Name: This is NOT an error in nimxslu. See nimxsl/tStatus2KernelProxyWrapper.cpp for information
> Line Number: 290
> Status Code: -218802
Do you have any suggestions how to solve this problem? I need to acquire many more records
and also will need to use the "records > available memory" function later on.
Many thanks,
Hanno

Hi Hanno,
The cause of this error is actually unrelated to its message. When
acquiring a record of data into onboard memory, the record's timestamp
must also be stored. There is a finite buffer on the host for these
timestamps, and it can only hold 100,000 values. If the board attempts
to store more than 100,000 records at once, an error will occur from
the overwrite attempt.
The solution to seeing this error is to use the timestamps on the host before they are overwritten. You can:
Fetch records while the acquisition is in progress
Fetch more records at a time, so that fewer are left in onboard memory after each fetch
Decrease
the trigger rate so that records can be fetched before their timestamps
are overwritten. If the trigger is not under your direct ontrol, you
can use the "Trigger Holdoff" property to throttle the trigger rate.
regards,
Tobias

Apple hardware test error 4mem/9/40000000: 0x8475d598

Any help would be appreciated I'm at work and my MBP crashed twice (Running Traktor Pro 2 with Drobo Mini as an external HD via Thunderbolt. second display daisy chained on VGA with a rotating desktop image to the TV's ) ...Just got this error code from my late late 2011 15in MBP after it randomly restarted and I ran the hardware test
apple hardware test error 4mem/9/40000000: 0x8475d598
This was after it crashed earlier and I got this report:
Anonymous UUID:       5948A12D-654D-DE02-D43C-4073A8690165
Sat Jun 21 17:31:41 2014
panic(cpu 0 caller 0xffffff8000a2ebe9): "Spinlock acquisition timed out: lock=0xffffff8024478110, lock owner thread=0x8000000000000000, current_thread: 0xffffff8025f64cf0, lock owner active on CPU 0xffffffff, current owner: 0x8000000000000000"@/SourceCache/xnu/xnu-2422.100.13/osfmk/i386/locks_i386.c:36 5
Backtrace (CPU 0), Frame : Return Address
0xffffff81eb5f3ec0 : 0xffffff8000a22fa9
0xffffff81eb5f3f40 : 0xffffff8000a2ebe9
0xffffff81eb5f3f70 : 0xffffff8000ac989d
0xffffff81eb5f3fb0 : 0xffffff8000af3c76
BSD process name corresponding to current thread: com.apple.WebKit
Mac OS version:
13D65
Kernel version:
Darwin Kernel Version 13.2.0: Thu Apr 17 23:03:13 PDT 2014; root:xnu-2422.100.13~1/RELEASE_X86_64
Kernel UUID: ADD73AE6-88B0-32FB-A8BB-4F7C8BE4092E
Kernel slide:     0x0000000000800000
Kernel text base: 0xffffff8000a00000
System model name: MacBookPro8,2 (Mac-94245A3940C91C80)
System uptime in nanoseconds: 18623716072818
last loaded kext at 18480408803348: com.apple.driver.AppleIntelMCEReporter 104 (addr 0xffffff7f833c5000, size 49152)
last unloaded kext at 18566085554385: com.apple.driver.AppleIntelMCEReporter 104 (addr 0xffffff7f833c5000, size 32768)
loaded kexts:
com.TrustedData.driver.VendorSpecificType00 1.7.0
com.drobo.SCSI.ThunderBolt 1.1 [66012]
net.kromtech.kext.Firewall 2.3.6
com.attotech.driver.ATTOiSCSI 3.4.1b1
com.apple.driver.AppleBluetoothMultitouch 80.14
com.apple.filesystems.smbfs 2.0.2
com.apple.driver.AppleHWSensor 1.9.5d0
com.apple.filesystems.autofs 3.0
com.apple.driver.AudioAUUC 1.60
com.apple.driver.AGPM 100.14.15
com.apple.iokit.IOBluetoothSerialManager 4.2.4f1
com.apple.driver.AppleMikeyHIDDriver 124
com.apple.driver.AppleMikeyDriver 2.6.1f2
com.apple.driver.AppleUpstreamUserClient 3.5.13
com.apple.iokit.IOUserEthernet 1.0.0d1
com.apple.kext.AMDFramebuffer 1.2.2
com.apple.Dont_Steal_Mac_OS_X 7.0.0
com.apple.driver.AppleHDA 2.6.1f2
com.apple.driver.AppleHWAccess 1
com.apple.AMDRadeonX3000 1.2.2
com.apple.driver.AppleMCCSControl 1.1.12
com.apple.driver.AppleIntelHD3000Graphics 8.2.4
com.apple.driver.AppleSMCPDRC 1.0.0
com.apple.iokit.BroadcomBluetoothHostControllerUSBTransport 4.2.4f1
com.apple.driver.AppleSMCLMU 2.0.4d1
com.apple.driver.AppleMuxControl 3.5.26
com.apple.driver.AppleLPC 1.7.0
com.apple.driver.ACPI_SMC_PlatformPlugin 1.0.0
com.apple.driver.SMCMotionSensor 3.0.4d1
com.apple.kext.AMD6000Controller 1.2.2
com.apple.driver.AppleIntelSNBGraphicsFB 8.2.4
com.apple.driver.AppleThunderboltIP 1.1.2
com.apple.driver.AppleUSBTCButtons 240.2
com.apple.driver.AppleUSBTCKeyboard 240.2
com.apple.driver.AppleIRController 325.7
com.apple.AppleFSCompression.AppleFSCompressionTypeDataless 1.0.0d1
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib 1.0.0d1
com.apple.BootCache 35
com.apple.iokit.SCSITaskUserClient 3.6.6
com.apple.driver.XsanFilter 404
com.apple.driver.AppleUSBHub 666.4.0
com.apple.iokit.IOAHCIBlockStorage 2.5.1
com.apple.driver.AppleSDXC 1.5.2
com.apple.iokit.AppleBCM5701Ethernet 3.8.1b2
com.apple.driver.AirPort.Brcm4331 700.20.22
com.apple.driver.AppleFWOHCI 5.0.2
com.apple.driver.AppleAHCIPort 3.0.0
com.apple.driver.AppleUSBEHCI 660.4.0
com.apple.driver.AppleSmartBatteryManager 161.0.0
com.apple.driver.AppleACPIButtons 2.0
com.apple.driver.AppleRTC 2.0
com.apple.driver.AppleHPET 1.8
com.apple.driver.AppleSMBIOS 2.1
com.apple.driver.AppleACPIEC 2.0
com.apple.driver.AppleAPIC 1.7
com.apple.driver.AppleIntelCPUPowerManagementClient 217.92.1
com.apple.nke.applicationfirewall 153
com.apple.security.quarantine 3
com.apple.driver.AppleIntelCPUPowerManagement 217.92.1
com.apple.iokit.IOSCSIBlockCommandsDevice 3.6.6
com.apple.iokit.IOSCSIParallelFamily 3.0.0
com.apple.driver.AppleThunderboltDPOutAdapter 3.1.7
com.apple.driver.AppleThunderboltPCIUpAdapter 1.4.5
com.apple.driver.IOBluetoothHIDDriver 4.2.4f1
com.apple.driver.AppleMultitouchDriver 245.13
com.apple.driver.AppleUSBAudio 2.9.5f4
com.apple.kext.triggers 1.0
com.apple.iokit.IOSerialFamily 10.0.7
com.apple.iokit.IOSurface 91.1
com.apple.iokit.IOBluetoothFamily 4.2.4f1
com.apple.driver.DspFuncLib 2.6.1f2
com.apple.vecLib.kext 1.0.0
com.apple.iokit.IOAudioFamily 1.9.7fc2
com.apple.kext.OSvKernDSPLib 1.14
com.apple.iokit.IOAcceleratorFamily 98.20
com.apple.driver.AppleSMBusController 1.0.11d1
com.apple.iokit.IOBluetoothHostControllerUSBTransport 4.2.4f1
com.apple.driver.AppleSMBusPCI 1.0.12d1
com.apple.driver.AppleBacklightExpert 1.0.4
com.apple.driver.AppleGraphicsControl 3.5.26
com.apple.driver.IOPlatformPluginLegacy 1.0.0
com.apple.driver.IOPlatformPluginFamily 5.7.0d11
com.apple.driver.AppleSMC 3.1.8
com.apple.kext.AMDSupport 1.2.2
com.apple.AppleGraphicsDeviceControl 3.5.26
com.apple.iokit.IONDRVSupport 2.4.1
com.apple.driver.AppleHDAController 2.6.1f2
com.apple.iokit.IOGraphicsFamily 2.4.1
com.apple.iokit.IOHDAFamily 2.6.1f2
com.apple.iokit.IOFireWireIP 2.2.6
com.apple.driver.AppleUSBMultitouch 240.9
com.apple.driver.AppleThunderboltDPInAdapter 3.1.7
com.apple.driver.AppleThunderboltDPAdapterFamily 3.1.7
com.apple.driver.AppleThunderboltPCIDownAdapter 1.4.5
com.apple.iokit.IOUSBHIDDriver 660.4.0
com.apple.driver.AppleUSBMergeNub 650.4.0
com.apple.driver.AppleUSBComposite 656.4.1
com.apple.iokit.IOSCSIMultimediaCommandsDevice 3.6.6
com.apple.iokit.IOBDStorageFamily 1.7
com.apple.iokit.IODVDStorageFamily 1.7.1
com.apple.iokit.IOCDStorageFamily 1.7.1
com.apple.driver.AppleThunderboltNHI 2.0.1
com.apple.iokit.IOThunderboltFamily 3.2.7
com.apple.iokit.IOAHCISerialATAPI 2.6.1
com.apple.iokit.IOSCSIArchitectureModelFamily 3.6.6
com.apple.iokit.IOUSBUserClient 660.4.2
com.apple.iokit.IOEthernetAVBController 1.0.3b4
com.apple.driver.mDNSOffloadUserClient 1.0.1b5
com.apple.iokit.IO80211Family 630.35
com.apple.iokit.IONetworkingFamily 3.2
com.apple.iokit.IOFireWireFamily 4.5.5
com.apple.iokit.IOAHCIFamily 2.6.5
com.apple.iokit.IOUSBFamily 677.4.0
com.apple.driver.AppleEFINVRAM 2.0
com.apple.driver.AppleEFIRuntime 2.0
com.apple.iokit.IOHIDFamily 2.0.0
com.apple.iokit.IOSMBusFamily 1.1
com.apple.security.sandbox 278.11
com.apple.kext.AppleMatch 1.0.0d1
com.apple.security.TMSafetyNet 7
com.apple.driver.AppleKeyStore 2
com.apple.driver.DiskImages 371.1
com.apple.iokit.IOStorageFamily 1.9
com.apple.iokit.IOReportFamily 23
com.apple.driver.AppleFDEKeyStore 28.30
com.apple.driver.AppleACPIPlatform 2.0
com.apple.iokit.IOPCIFamily 2.9
com.apple.iokit.IOACPIFamily 1.4
com.apple.kec.corecrypto 1.0
com.apple.kec.pthread 1
Model: MacBookPro8,2, BootROM MBP81.0047.B27, 4 processors, Intel Core i7, 2.2 GHz, 16 GB, SMC 1.69f4
Graphics: Intel HD Graphics 3000, Intel HD Graphics 3000, Built-In, 512 MB
Graphics: AMD Radeon HD 6750M, AMD Radeon HD 6750M, PCIe, 512 MB
Memory Module: BANK 0/DIMM0, 8 GB, DDR3, 1333 MHz, 0x857F, 0x483634314755363746393333334700000000
Memory Module: BANK 1/DIMM0, 8 GB, DDR3, 1333 MHz, 0x857F, 0x483634314755363746393333334700000000
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0xD6), Broadcom BCM43xx 1.0 (5.106.98.100.22)
Bluetooth: Version 4.2.4f1 13674, 3 services, 23 devices, 1 incoming serial ports
Network Service: Wi-Fi, AirPort, en1
PCI Card: scsi, SCSI Bus Controller, Thunderbolt@195,0,0
Serial ATA Device: Samsung SSD 840 EVO 250GB, 250.06 GB
Serial ATA Device: MATSHITADVD-R   UJ-8A8
USB Device: FaceTime HD Camera (Built-in)
USB Device: Hub
USB Device: BRCM2070 Hub
USB Device: Bluetooth USB Host Controller
USB Device: Apple Internal Keyboard / Trackpad
USB Device: Hub
USB Device: Duet USB
USB Device: IR Receiver
Thunderbolt Bus: MacBook Pro, Apple Inc., 22.1
Thunderbolt Device: Mini, Drobo, 1, 26.3

The Apple Hardware Test error indicates a RAM issue. Install the original RAM and see if that improves the situation.
Also these items may perhaps be conributing causes:
TrustedData.driver.VendorSpecificType00 1.7.0
.drobo.SCSI.ThunderBolt 1.1 [66012]
.kromtech.kext.Firewall 2.3.6
attotech.driver.ATTOiSCSI 3.4.1b1
Ciao.

X121e randomly wake up from suspended status and real time clock error

Hi all
Previously I considered my x121e suffer from overheating issue and causes real time clock error (RTC). However, after more testing and investigation, I believe the problem is related to other hardware issues and I like to hear people opinion before sending the laptop back to Lenovo.
The machine goes into suspend status either pressing the power button or closing the lid from Windows7 (clean install) without problem. However, it would wake up itself randomly, "beep" twice and screen shows RTC and CMOS checksum error. This happen more often when I am holding the machine (i.e. some movement/vibration). I wonder:
- Is it the RTC battery problem, cause the RTC to wake up the machine?
- Other hardware failure?
The laptop has a clean OS installed/recovered. Latest 1.16 Bios installed. No USB or memory card attached. Ram replaced and not the cause.
Please advise
Howard

Hello,
I am unsure; you would have to contact Lenovo directly and find out how they handle this situation. They may want the ThinkPad X121e back so they can run thorough diagnostics on it, just in case the problem is something else. That way it gets fixed the first time.
Regards,
Aryeh Goretsky
I am a volunteer and neither a Lenovo nor a Microsoft employee. • Dexter is a good dog • Dexter je dobrý pes
S230u (3347-4HU) • X220 (4286-CTO) • W510 (4318-CTO) • W530 (2441-4R3) • X100e (3508-CTO) • X120e (0596-CTO) • T61p (6459-CTO) • T43p (2678-H7U) • T42 (2378-R4U) • T23 (2648-LU7)
Deutsche Community Comunidad en Español Русскоязычное Сообщество

[SOLVED] System time is +4hrs from hardware clock

Hello again.
Now I can't set up my system`s time properly. (Set system time from hardware clock)
Timezone is GMT+4 (Europe/Samara) and hardware clock (RTC) is set to proper time so does UTC.
But system`s time itself is 4 hours in the future from HW clock!
# hwclock --hctosys --utc
does nothing.
# timedatectl set-local-rtc 1
or
# timedatectl set-time "$mytime"
both do nothing and output following error:
Failed to issue method call: The name org.freedesktop.PolicyKit1 was not provided by any .service files
Also, removing /etc/adjtime does nothing!
How can I fix it?
Last edited by eruditorum (2012-11-25 10:52:14)

ewaller,
hwclock from util-linux 2.22.1
Using /dev interface to clock.
Last drift adjustment done at 1353744432 seconds after 1969
Last calibration done at 1353744432 seconds after 1969
Hardware clock is on UTC time
Assuming hardware clock is kept in UTC time.
Waiting for clock tick...
...got clock tick
Time read from Hardware Clock: 2012/11/25 05:40:17
Hw clock time : 2012/11/25 05:40:17 = 1353822017 seconds since 1969
Sun 25 Nov 2012 09:40:17 AM SAMT -0.907738 seconds
Last edited by eruditorum (2012-11-25 04:35:10)

KDM crash - hardware clock

I had some problems with a computer running KDE4 at work. KDM would crash back to console. Login in from console as root and switch between run levels back and forth - init 3 and back to init 5 - would get KDM up and running with no problem though.
Fix:
- in BIOS hardware clock was two hours back in time, adjusting it correctly mad KDM start correctly
From kdm.log:
kdmgreet(2657)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"
This message is persistent even though KDM now starts. Intriguingly, at least for me, is the fact that the log after adjustment of time is two hours ahead of time. During crashes is was correct. System time was and is correct (ntpd).
Two questions:
- how come KDM log doesn't adhere to neither system or BIOS hardware clock?
- is it reasonable that such a "small" error causes KDM to crash?
The first question seems to be answered by the fact that kdm.log complaints about not being able to connect to D-Bus server. However why doesn't it? Dbus is started as it should, and no other services seem to

To restate the problem:
Microsoft Windows expects the hardware clock on the machine upon which it is running to be local time. Linux machines and others set and use the hardware clock as UTC (aka GMT) time. Thus, when a machine can be dual-booted,
there is a discrepancy in the reported time. You can modify the other operating system parameters to deal with a hardware clock in local time, or you can change Windows to cope with a UTC hardware clock.
While it is possible to kluge the time zone as is mentioned below, a simpler solution is to
synchronize Windows time with a NIST server ("time.windows.gov", e.g.) vs. the default Windows time server "time.windows.com". You can do this in the "Internet Time" tab when you click on the date/time on the system bar. Once it refreshes,
the time in Windows will be the correct local time, vs. the previously incorrect time.
One drawback of this method is that after booting into Windows, the incorrect time will be displayed until a refresh is performed against the NIST server. You can adjust how often this occurs on the "Internet Time" tab as
well. Another drawback is, of course, that you need an Internet connection.
I triple-checked that using this method does NOT change the hardware clock, which is good. I have used this method for a while. Your results may vary. Hope this helps.

Real Time Clock Error - Check Date and Time settings, System CMOS Checksum bad

Hello everybody,
Can help anyone to resolve my problem.
I have an Thinkpad W520 (42823FG), BIOS 8BET60WW 1.4 When I disconect AC power and remove battery and connect again, I see this message on screen:
"Real Time Clock Error - Check Date and Time settings, System CMOS Checksum bad
Press Esc to continue or F1 to enter Setup"
Is this a system board problem or CMOS battery problem ?
Thank you

Hello and welcome,
It's probably (hopefully) just the CMOS battery. The easiest way to find out is to just replace that battery.
Page 85 of the Hardware Maintenance Manual:
Hardware Maintenance Manual
Here's an example of the battery. I'm not recommending (or not) this vendor:
http://www.ebay.com/itm/New-Lenovo-ThinkPad-W500-W510-W520-W530-W700-W701-W701ds-CMOS-RTC-Backup-BAT...
Z.
The large print: please read the Community Participation Rules before posting. Include as much information as possible: model, machine type, operating system, and a descriptive subject line. Do not include personal information: serial number, telephone number, email address, etc. The fine print: I do not work for, nor do I speak for Lenovo. Unsolicited private messages will be ignored. ... GeezBlog
English Community Deutsche Community Comunidad en Español Русскоязычное Сообщество

Computer Clock Error

Hello
I'm a new Mac user. I just bought iBook G3 500 with Tiger on it. Every time I turn it on, I see clock error message. "Your computer's clock is set to a date before March 24th, 2001. This may cause some applications to behave erratically." And actually date & time is set at Dec 31, 1969. Of course, I changed the time and date and locked it. But once I turn it off and back on, it happens again. System error?

HI, Moonhill.
Unlike most other Macs, iBook's do not have a backup battery, which provides a trickle of power needed to retain settings in PRAM and NVRAM, such as system date and time.
iBooks use the system battery, i.e. the main battery, and a tiny capacitor to perform the functions of a backup battery in Macs so equipped. If you briefly remove the system battery and do not have the A/C adapter connected, the capacitor is supposed to retain the PRAM and NVRAM settings for a limited time. If this capacitor has failed — and it can happen on iBooks — then the date/time settings and other values in PRAM and NVRAM will not be retained if you remove the battery and the computer is also disconnected from A/C. In such a case, the computer has to be serviced to replace the capacitor.
I'm not sure if the Apple Hardware Test that should have been included with your computer will test this capacitor, but you can try it: see my "Apple Hardware Test" FAQ for comprehensive advice on using the Apple Hardware Test in troubleshooting, including running the test in Loop Mode.
Otherwise, if there is an Apple Retail Store in your area, I suggest you take the iBook there for examination.
Good luck!
Dr. Smoke
Author: Troubleshooting Mac® OS X
Note: The information provided in the link(s) above is freely available. However, because I own The X Lab™, a commercial Web site to which some of these links point, the Apple Discussions Terms of Use require I include the following disclosure statement with this post:
I may receive some form of compensation, financial or otherwise, from my recommendation or link.

Can anyone tell me what apple hardware test error code apple hardware 4MOT/4/40000002: Exhaust-1153 or 1209 means? I am running a MacBook Pro.

Can anyone tell me what apple hardware test error code apple hardware 4MOT/4/40000002: Exhaust-1153 or 1209 means? I am running a MacBook Pro

The motor on the exhaust fan has failed or is failing.

ZEN Vision 'Hardware Problem' error mess

Model No: ZEN Vision - PMC-HD0002
Error occurred as a result of a firmware upgrade.I can access 'recovery mode' &?have attempted several further firmware upgrades.It loads, rebuilds, reboots, starts then the 'hardware problem' error message returns.The device is currently stating, in 'recovery mode', that the following firmware is loaded v.42.0_0.0.9.I have removed all data (format all), run 'clean up' & 'rebooted' then upgraded firmware but with no success.?Any ideas will be greatly received & appreciated.

hi.
i have exactly the same problem.
did you manage to find any answer?
how did you access the recovery mode?
your response will be greatly appreciated.
thanks!

Mac mini server: Hardware test error on Hard Drive

Mac mini server: Hardware test error on Hard Drive
'checking for slow read failures': ERROR - Target device access failure - Test failed.
CAN I ACCESS HD (which is our data server) EVER AGAIN? IF SO, HOW?
Meanwhile we wonder if this is really a hardware error. It all happened during writing a time machine backup.
Probably while writing it, some data was relocated by accident, but we can not 100%-sure remember the sequence of actions :/
This is our trauma history:
- time machine got increasingly slower in writing a backup
- we quit the backup
- we switched off the mac mini (on power button)
- we switched on the mac mini
- we stopped time machine to the rules
- we shut down mac mini via command
- we booted the mac mini in save mode
- we see a loading bar
- no progress after 10th of loading bar
- switched off (power button)
- when we now switch on the loading bar below the apple-logo is all we see + the little wheel
- we started with cmd+alt+p+r pressed
- mac mini restarted but showed the loading bar scenario without progress again
- we started with 'd' pressed and did the hardware test (see above)
- we started with 'alt' pressed but it does not give us the recoverydrive to run the last backup
ANY IDEAS?
IS IT A SOFTWARE- OR HARDWARE ERROR?
THX IN ADVANCE!

BDAqua wrote:
I thnk Intenal 2.5" Drives for servers is silly, & Ithink the Minis & iMacs re poorly cooled.
I'd get Temprature Monitor & see what temps they're running.
Is Temperature Monitor an app or a device? If it's a temperature problem then that is essentially a design problem. Two drive failures in the same Mac mini server in four months combined with the fact that they're not really user serviceable already has me 90% on the way back to more pragmatically designed Linux servers. I think it would be foolish to waste any more money on these minis for my business hosting.

What are the meanings of Apple Hardware Test error codes 4m0t/4/40000003:hdd-1300 and 4m0t/4/40000003:hdd-1308?

what are the meanings of Apple Hardware Test error codes 4m0t/4/40000003:hdd-1300 and 4m0t/4/40000003:hdd-1308?

Thanks - Even though I'm years out of warranty I got chat help from Apple (I said they should help me since the codes aren't published.) We covered three different questions, and although I didn't get a specific decoding of the error code, I got confirmation of what other comments here imply - it might have helped that I indicated I'd already been here - and useful links to how to do back ups, including to CD(s). (I don't have a lot of data on this computer yet)
Now I need to figure out how to decide how hot-to-the-touch is "too hot" for the metal frame at the top of the iMac to decide whether I'm getting adequate fan performance or insufficient. While chatting I initially reported it was cool at the bottom and warm at the top. Apple hadn't asked, but their response prompted me to feel it again, and I'd say the top was hot, not warm - I updated but Apple didn't comment further except to conclude after addressing the other questions that I should take it in for further assessment - don't really want to bother with that.

Hardware clock and system clock don't match

hello. i recently upgraded to kde 4.7, and i don't know if it's the culprit or not, but my system clock is now ahead of the hardware clock by the timezone offset.
my timezone is Asia/Manila, which is UTC+8. so if the correct time is 00:00, the system time is 08:00.
i dual boot with windows so the HARDWARECLOCK setting in /etc/rc.conf is set to localtime.
interestingly, the commands "hwclock --show" and "date" both show PHT as the timezone, but with the aforementioned time skew. to illustrate:
# hwclock --show
Fri 05 Aug 2011 10:45:02 AM PHT -0.500309 seconds
# date
Fri Aug 5 18:45:02 PHT 2011
running "hwclock --hctosys" fixes the problem while logged in, but restarting the computer reverts the problem. i could put a daemon that runs the command at startup, but i never needed to do that before and i'm not inclined to at the moment. i think this is just a misconfiguration somewhere.
thanks for any help you could give.

hello. it is
hwclock from util-linux 2.19.1
Using /dev interface to clock.
Last drift adjustment done at 1312511647 seconds after 1969
Last calibration done at 1304274137 seconds after 1969
Hardware clock is on local time
Assuming hardware clock is kept in local time.
Waiting for clock tick...
...got clock tick
Time read from Hardware Clock: 2011/08/05 12:08:46
Hw clock time : 2011/08/05 12:08:46 = 1312517326 seconds since 1969
Fri 05 Aug 2011 12:08:46 PM PHT -0.690104 seconds

Hardware clocking error # 200550, PCI-5122

Similar Messages

Maybe you are looking for