Hp pci bus parity error

hp pci bus parity error

"If the parity error is coming up as soon as the BIOS tries to boot, and especially if it fails at memory address "0000" consistently, this is a. This error generally means that there is a problem is a driver. You should run HP Support Assistant to check for updated drivers. If this fails to resolve the. www.techrepublic.com › Topics › Hardware › Desktop.

Hp pci bus parity error - congratulate

I think your motherboard has failed.

Your PCI bus slots are wired to an 8 bit parallel data bus. The basic way to constantly monitor this is to add a nineth bit. Then the circuits that put the data on the bus count the number of bits in the word and if it is an even number of bits usually adds a parity bit so the word contains an odd number of bits. This is called "odd parity". Even parity can be used, the the usual convention is odd. Then once the data arrives, it's checked. If you picked up or lost a bit, the system flags an error.

Yes, there's an obvious flaw in the system. What if you pickup or lose two bits? Parity checking will not be able to detect that. A more complex ( read expensive) system can correct a single bit error and detect a 2 bit error.

You have this system for the PCI bus, but not the PCIe bus. Remember, PCI Express is basically a serial bus



Google "parity error" or "parity checking".

 

NMI Parity Check/Memory Parity Error

Windows Operating System (OS) users may encounter the NMI Parity Check/Memory Parity Error during the computer start-up process. The error is normally displayed when a computer hangs or stops responding during the Windows start-up process, and may be the result of a number of hardware or hardware configuration problems.

What does the NMI Parity Check/Memory Parity Error Look Like?

A number of error codes can be displayed when the error occurs. These include:

NMI: Parity Check/Memory Parity Error, NMI: Bus Timeout, NMI: Software NMI generated, NMI: Eisa IOCHKERR board x, NMI: Channel Check/IOCHK, or NMI: Fail-safe timer

The error codes typically start with the “*** Hardware Malfunction” message and a display message indicating that the computer or system has been “halted” follows.

Why does the NMI Parity Check/Memory Parity Error Occur?

The NMI Parity Check/Memory Parity error typically occurs if a computer hardware component is damaged, malfunctions, or if an incompatible driver is installed on the computer.

How to Fix the NMI Parity Check/Memory Parity Error

Most hardware problems that trigger this error involve the computer’s RAM, motherboard, cache memory, or a hardware adapter on the computer. The following are troubleshooting steps that can be taken to identify the cause of the error:

Verify Your Computer’s Memory

Step 1 – Remove any new RAM modules that have been installed on the computer.

Step 2 – Restart the computer to see if the error message continues to be displayed.

Step 3 – If the error is eliminated, then replace the RAM modules that were installed. If it persists, repeat the process but only leave the minimum amount of RAM necessary to boot the computer in order to determine if the computer has faulty RAM.

Step 4 – Replace the faulty RAM modules if they are the source of the problem.

The Microsoft RAM diagnostic tool found at: http://oca.microsoft.com/en/windiag.asp may also be used in order to help identify faulty computer modules.

Verify the Adapters on the Computer

Step 1 – Remove all adapters that are not required to run or start the computer. Most Windows computers can be run with only the video and drive subsystem controller adapters.

Step 2 – Restart the computer. If the error does not appear, then the problem is one of the adapters removed in step 1.

Step 3 – Reinstall one adapter at a time until the error is displayed again. This determines the adapter that was the source of the error. Visit the adapter manufacturer’s website and download and install the latest version.

Step 4 – Re-seat all adapter hardware cards if the error is not eliminated to ensure that this is not the cause of the problem.

Verify the Computer BIOS

Step 1 – Ensure that the latest revision of the computer’s BIOS and firmware configuration are installed.

Step 2 – Open the BIOS and change the configuration to “load Fail-safe defaults” or “BIOS defaults,” set “Plug and Play OS” to “No,” and disable anti-virus protection options located in the BIOS.

Step 3 – Restart the computer to see if the error has been corrected.

Check for Driver Updates

If Windows OS was recently upgraded or new hardware installed, then an outdated device driver may be the cause of the error.

Step 1 – Ensure that Windows Updates is configured to automatically update the computer from the “Windows Updates” application found in the computer’s “Control Panel.” Manually update the Operating System. Restart the computer after completing the manual Windows update.

Step 2 – If any new hardware was installed, remove the hardware drivers in the “Add/Remove Programs” menu after updating the OS in Step 1 and restart the computer.

Step 3 – Check the other device drivers installed on the computer for updates if the error is still being displayed and an update as required. Restart the computer after each device driver update to complete troubleshooting it.

General discussion

  • PCI Parity Error on system startup

    by twuf · about 19 years, 10 months ago

    When booting 1st thing in morning- Dell Pentium III Win98 (nothing changed) i get BSOD – “system error -Memory parity error detected -system halted”. When i hit off buttom or restart, the black screen comes up and quickly displays five lines of typeall saying “PCI Parity Error on Bus/Device Function 008h”. When computer reboots it does so in Safe mode or Normal ok. and computer runs fine for the rest of the day. Is this telling me a ROM Chip is going bad or what?

All Comments

    • PCI Parity Error on system startup

      by ann777 · about 19 years, 10 months ago

      In reply to PCI Parity Error on system startup

      Unplug the computer
      Open the system and ground yourself to the metal part of the system.
      Disconnect your memory from the systemboard and then reseat the same memory in the same slot.
      Repeat with each memory SIMM.
      You might also want to make sure that everything else in the system (any daughterboard cards) are properly seated as well.
      Close the system and power it up.

      Generally the usual (quick) fix with parity errors is to reseat the memory. If your system has been moved recently or the general on/off (heating and cooling) of a system will tend to expand/contract against the connectors and cause this slippage problem.

      If the problem persists, then yes, look at the individual chips abd run diagnostics to see which memory address(es) are affected (and thus which chips).

    • PCI Parity Error on system startup

      by maxwell edison · about 19 years, 10 months ago

      In reply to PCI Parity Error on system startup

      At first glance I would think that you have some RAM that has gone bad or is going bad. If you have any extra RAM or some from another machine, you might try new (different) RAM.

      I also saw this problem described on Microsoft article Q232768, “Error Message: Memory Parity Error Detected. System Halted”.

      http://support.microsoft.com/default.aspx?scid=KB;EN-US;q232768&

      REMOVE SPACES from the pasted URL

    • PCI Parity Error on system startup

      by darts32 · about 19 years, 10 months ago

      In reply to PCI Parity Error on system startup

      Can you tell me if you have an ATI Rage Fury video adapter? It has something to do with one of your PCI cards. If you have the ATI card try the Microsoft Knowledge Base Article – Q232768.

      • PCI Parity Error on system startup

        by twuf · about 19 years, 10 months ago

        In reply to PCI Parity Error on system startup

        I do have ATI Rage adapter and updated the driver. So far computer hasn’t crashed. Maybe that is the answer. Thanks

    • PCI Parity Error on system startup

      by twuf · about 19 years, 10 months ago

      In reply to PCI Parity Error on system startup

      This question was closed by the author

Pavilion DV2000 - NMI: parity check / memory parity error

  • NMI:Parity error blue screen

    I have problem with blue screen with any program at any time. It is as it should be a hardware problem. When I run the Diagnostics on my computer everything seems to check out OK.

    Hello drichardson3,

    ·         You get this error blue screen randomly on your computer?

    ·         What exactly is the diagnostic test that you have run on the computer?

    The checking of NMI Parity error is an error related to a defective hardware on your computer. This is mainly caused by a faulty RAM.

    To resolve this problem, you may need to check on the RAM, I suggest you contact the manufacturer of your computer to check the hardware that does not work properly.

    Thank you
    Irfan H, Engineer Support Microsoft Answers. Visit our Microsoft answers feedback Forum and let us know what you think.

  • With PCI-6229 NMI Parity error

    Currently, I'm trying to get a PCI-6229 to work with one of our lab computers. We'll use LabVIEW 8.5.1 with DAQmx 6.7.1 to program the card. Using our measurement VI owner, the computer will crash at some point (not really in reproducible way) with a blue screen saying "NMI: Parity Check / Memory parity error. All the tests of auto and examples of NOR (delivered with LabVIEW) perform well however.

    Most likely, this problem is not a RAM issue (MemTest I tried, different memory chips, different memory banks). Also, the PCI computer bus works very well otherwise (for any other acquisition cards for example). Annoying enough, the card seems to do a great job in an old and slow computer. Which is maybe something to look at? Or are there other ideas?
    Our workplace is a Fujitsu-Siemens of Celsius M460 with BIOS version 6.00 rel. 1.09 running Windows XP (32-bit version). The software to use with the card is LabVIEW 8.5.1 with DAQmx 6.7.1.

    Dear Lutz,

    I could reproduce the blue screen, and
    changed your program in order to avoid the race condition. What is
    actually happens is you want 2 tasks over time the
    AOSampleClock as a source before the task of AO started.

    When
    programming as in the example I sent you (see attachment VI), you
    shouldn't deal with this blue screen problem more. However, I recognize
    that such a thing should not happen even when it's 'bad' programming... I'm going to
    inform the development so that it will be corrected with the next DAQmx
    version of the driver.

    Merry Christmas,

    P. Lawrence

    National Instruments

  • Hardware malfunction: NMI Parity error

    Screen blue/hardware malfunction/call your provider of support material / parity memory check error / NMI:parity / this happens more frequently

    The RAM in your computer seems to be failing. Run the memory in memory diagnostic tool by typing in the search box of the start menu by pressing Enter.

    Use the scanner on this site http://www.crucial.com/ to find out what type of memory, you have to buy if it needs to be replaced.

  • HP Pavilion G6: A broad check memory failed

    Hey all

    My HP Pavilion G6 has been giving me the BSOD (0x7A) recently so I ran some checks computer diagnostic provided from the HP recovery partition. HD and memory short tests came positive, but the failure of verification of the extended memory with the following failure ID: 9GE3L0-6567MK-MFPX01-401003.

    I also run windows memory test diagnostic and it came positive.

    Can you help me?

    You can test yourself by removing the bars of memory.

    Put one of them into the soDIMM slot then power and closest to you inside the laptop on the laptop.

    If Notepad boots into Windows and do not present problems or the faiols the test of memory, while you have not installed the module has problems and needs to be replaced by an identical to one that is installed.

    If the problem persists, then try to replace the module installed with the other and run the same test.

  • Satellite Pro A100 - NMI memory parity error parity check

    Sometimes I get this BSOD error during 2 months.
    Hardware malfunction call your provider for support NMI: Parity Check / Memory Parity Error * the system stopped *.

    It can occur if the laptop is asleep, or even refreshing a screen save or Stand-By condition.
    Model PSAAPE - 00s00KEN 2 GB installed. I checked that the memory is installed correctly. It's a laptop very clean with no dust clutter things. Aside from the Ram "goes wrong" and developing a fault, can anyone suggest another cause? It doesn't seem to be an obvious solution to this problem on a forum I've seen so far. Maybe it's my RAM that fails (but it seems to do it when he is not be underlined!) It could be the video drivers... who knows? I hope somebody.

    Hello!

    In your case, I would check the RAM, I think that's the problem.

    You can do this with Memtest86:
    http://Memtest86.com/
    Memtest86 is a diagnostic tool to check the RAM. Here, you can also download a CD image.
    It s easy to use. Run the test of 3-4 hours and then you will see if the RAM has some errors.

    Good bye

  • Hardware malfunction NMI: parity check / memory parity error * the system stopped *.

    I installed ENLWI-G2 802.11 g Wireless PCI Adapter in my Dell Optiplex 760 with XP SP3 32-bit Windows. But it gives me a blue screen with the error:

    Hardware malfunction NMI: parity check / memory parity error * the system stopped *.

    How to solve this error?

    Try to switch on the memory modules. Ask the MS site for more information on the specific error.

  • Satellite P200 - Parity Check / Memory Parity Error

    Hi all experts!

    After updating a driver, I get this above mentioned message.
    + Message ' hardware malfunction NMI Parity Check / Memory Parity Error.

    But just at the moment where the P200 falls in sleep mode. I can't wake up and have to do a hard reboot. Windows is starting and works perfectly and everything seems to be okay!

    Any idea?

    Thanks in advance!
    YB

    Hello

    This behavior can occur if a hardware component malfunctions, or if it has installed the damaged or incompatible drivers.
    I think that you should remove the driver updated or installed first.
    If this does not work, test the laptop with preinstalled system cool.

    Finally if this is insufficient, a hardware malfunction might be possible.
    In this case the RAM modules need to be tested as the first part.

  • How can I fix "memory parity error" - a hardware malfunction?

    My video display keeps going out and lose pixels.  Occasionally, I get an error message "memory parity error" and "malfunction of equipment."  -What it means and I can fix it?

    You forgot to give us information on your computer, so all I can give you is general advice.

    1. in the case of a desktop computer, connect it to another monitor. If all goes well, replace the original monitor. If the problem persists when connected to the test screen, replace your video card.

    2. in the case of a laptop computer, contact technical support of computer mftr... There is a hardware problem, probably with the video chip, which you can't fix yourself. MS - MVP - Elephant Boy computers - don't panic!

  • MD3000 Raid Controller Module memory parity error

    MD3000 has two controllers. One of the controller does not have. SO I replaced it with a used controller, without work. All errors are gone, except a "RAID Controller Module memory consistency error".

    Recovery Guru recommends steps that I followed without success.

    Need help in this forum.

    Paul

    Hello Paul,

    What you need to do is on the replacement controller to pull the raid battery and wait about 2 minutes then reinsert it again. Also I want to try to do is to Flash the firmware on the system as well.

    Please let us know if you have any other questions.

  • Serial communication - ignore parity error

    I have a question about how LabVIEW opens a serial port for communication. I communicate with a device that uses a protocol owner. It sets and clears the parity bit to indicate the nature of the response. For example, the orders are sent with the parity bit higher while responses are sent with the weak parity bit (unless the answer is at the end of the transmission, in which case the device sets the parity bit high to indicate).

    My problem is the way that LabVIEW opens the serial port for communication. Using Portmon, that I captured the control indicators, that it sends to Windows to configure serial communication:

    IOCTL_SERIAL_SET_LINE_CONTROL Serial0 SUCCESS StopBits: 1 Parity: MARK WordLength: 8IOCTL_SERIAL_SET_CHAR Serial0 SUCCESS EOF:0 ERR:0 BRK:0 EVT:0 XON:11 XOFF:13IOCTL_SERIAL_SET_HANDFLOW Serial0 SUCCESS Shake:1 Replace:44 XonLimit:64 XoffLimit:64

    Note the values 'Shake' and 'replace '. In my view, they are originally bytes with parity errors is removed. A separate RS232 Comm Debug tool that I use with success looks like this:

    IOCTL_SERIAL_SET_LINE_CONTROL Serial0 SUCCESS StopBits: 1 Parity: NONE WordLength: 8IOCTL_SERIAL_SET_CHAR Serial0 SUCCESS EOF:0 ERR:0 BRK:0 EVT:0 XON:11 XOFF:13IOCTL_SERIAL_SET_HANDFLOW Serial0 SUCCESS Shake:0 Replace:80000000 XonLimit:128 XoffLimit:128

    Notice the difference in values. By using this tool, Windows does not packages with parity errors - that's what I want. Is there any way to change how LabVIEW opens the serial communication port to achieve?

    I tried to change the parity, where the ILO is defined differently, but I think that I am running in a race condition; LabVIEW can not run the code and change the mode of fast enough parity before the next byte of data is sent by the device.

    Ravens fan: the parity bit, in the proprietary protocol, that I use, is not used for parity checking. Basically, the protocol uses a 9-bit serial communication. The parity bit must be paid or compensated according to what byte do (if it is a command, if it is the end of transmission, etc.).

    I found an old post on this page which seems to answer my question (my apologies for not completely research before posting... I learn the right use/search phrases that I find more information). I download the 3.4.1 version of VISA now.

  • What does "a parity error was detected on \Device\ide\idePort0" mean and how can I fix?

    I have a Pentium 4, XP SP3, 2 HDs installed, and I don't think I have SCSI but in my registry, it shows the HDs and two CD - RW and DVD drives listed under SCSI and there is no topic such as IDE, Atapi or AT (the area I'm talking about in the registry is: \HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\) so I don't know what is happening in this area...? Anyway, everything else refers to above devices IDE or Atapi etc..

    As well as the above parity error, I noticed a little more that I will add here:

    "The driver has detected an error on \Device\Harddisk0\D controller" (this is an ALL NEW HD)

    "The device, \Device\Harddisk1\D, has a bad block" (it's second HD giving the same error msg, the last HD failed and this is used)

    "The device, \Device\CdRom0, has a bad block" (this is my CD - RW drive, which seems to work very well, it's the DVD player that is not working properly)

    "While validating this \Device\Serial0 was really a serial port, a fifo was detected. The fifo will be used. »

    All of these errors are coming together for the most part. Please help as I just replaced a hard drive failing during the summer, now it is looking like another is a failure, but I want to know if something else in my computer can cause drives to fail, or causing errors in some way, or any other information anyone can give me to help before you start the process of replacing a HD failure (again!)

    Thank you... Denise

    Hi groovydee,

    Method 1

    I suggest you reinstall the controller and chipset drivers by contacting the manufacturer of the computer, check to see if it helps.

    Method 2

    If the previous step fails, then you need to check disk scan on the hard drive to scan and difficulty of bad sectors on the disk.

    How to perform disk error checking in Windows XP

    http://support.Microsoft.com/kb/315265

    Note: While running chkdsk on the drive if bad sectors are found on the hard drive, then chkdsk attempts to repair this area if all the data available in this area may be lost.

  • start using SD in Pavilion dv2000 memory card

    Hello

    I wanted to boot from SD memory card in my HP Pavilion dv2000 laptop. What should be the BIOS for this setting.

    Thank you!

    Shivchal

    I don't think that you can start from your reador of card for laptop

    but you can start from your SD card using a USB card reader

    But u should create this card as bootable,

    There are many free application on the internet, just google,

    and make your bootable SD card, then use it.

    I used "USB_MultiBoot_10" and I create a portable bootable computer cos XP instalation disk of my father, dvd does not work.

    I do not have the link at the moment. but I got frm google search.

    Have FUN BRO,

  • Series parity errors, and clearing the error replacement character

    I have a situation where I have to change the parity on the last byte of an outgoing message.  E problem is that when I try to play, I get a parity error and the error replacement character appears in the output.  I have a few extra bytes and a few bytes lost due to masking.  This thread stated that visa 3.4.1 there is a configuration INI directive which would disable the error replacement character.  I installed 4.4.1 and were not able to make it work properly.  I'm curious to know if anyone knows if this setting without papers is always available and how to make it work.

    Thank you.

    Thanks to Tyler of OR helped me to determine the appropriate location to use.  The entry is valid, I just used the wrong visaconf.ini file.  The correct file is located in
    (

  • Error: A parity error was detected on \Device\Ide\IdePort0 at system startup

    Original title: Windows XP error 11

    Event Viewer maintains with the following messages appears at the start of windows xp,

    The driver has detected an error of the Comptroller on \Device\Harddisk0\D.

    A parity error was detected on \Device\Ide\IdePort0.

    Hi plogmine,

    We recommend that you change the setting of firewall/security at different levels and then try to access files and folders on the network.

    See this article for more information: http://support.microsoft.com/kb/814112

    Visit our Microsoft answers feedback Forum and let us know what you think.

  • DL380 G4 Won't Boot

    Posted by christh0mas

    One of my servers, an old Proliant DL380 G4 recently shut itself down and when booting, it displays this error and will not proceed any further:  "PCI bus parity error slot ?".  I have tried shutting it down and reseating all cards on the motherboard but this did not help.  While searching on this error around the internet, I found that it indicates a problem with the motherboard.  I do have a spare server of the same model as this and I thought about swapping the motherboard out with it.  I am concerned that my RAID array will be broken if I do this and all of my data will be lost.  The RAID config on this server is different than the other server but they do both use the same array controller card. 

    What do you think?  Am I OK swapping the motherboard or will this spell disaster?  I’d rather not have to rebuild this server so I’m hoping there’s something that can be done to resurrect it.

    Thanks in advance.
    -Chris

    • Chad.w
      Chad.wThis person is a Verified Professional
      This person is a verified professional.
      Verify your account to enable IT peers to see that you are a professional.

      Well, if your motherboard is toast, it is going to have to be replaced. So, replace it and either it works or it doesn't. My experience with HP arrays is that the drives will report their configuration to the array controller so you should be ok.

      Was this post helpful?thumb_upthumb_down
    • The RAID config is in the drives, so you should be OK with the swap.

      Was this post helpful?thumb_upthumb_down
    • This same thing happened to this server a few weeks ago.  I shut it off for a few minutes, started it back up and it booted normally.  Unfortunately, that didn't happen this time.  I'll try swapping out the motherboards in the AM.

      Thanks for the input.

    • Jono

      I've had a few dl380's do that and swapped the drives and controller to a spare without a problem

      Was this post helpful?thumb_upthumb_down
    • Ahh, that sounds much easier than swapping the entire motherboard.  I'll give that a shot.

      Thanks.

    • I have had a problem where it wont boot if any USB device is connected. (eg USB ext HD for backup). Early proliant. Possibility??

    • Thanks Jono.  Swapping the controller and drives did the trick.  Phew!

      Was this post helpful?thumb_upthumb_down
    • christh0mas wrote:

      Thanks Jono.  Swapping the controller and drives did the trick.  Phew!

      Phew!  Phew! 

    • Document control/access solution to prevent opening specific documents

      Document control/access solution to prevent opening specific documents

      Best Practices & General IT

      Hey all,Before I get into the problem at hand, I realize this may be a multi phase problem and the document side of it may only be resolving a specific portion of the problem, but I have to start somewhere.The issue to cut off the fat and make it as simpl...

    • Testing Touch Screen

      Testing Touch Screen

      Hardware

      Hi, We have a touch screen on a CNC machine on our production floor that's causing issues. Bottom 1/2" or so of the screen never registers a touch. The rest of it works sometimes, but sometimes you might try to hit a button but the touch registers a few i...

    • Spark! Pro Series - September 2nd, 2022

      Spark! Pro Series - September 2nd, 2022

      Spiceworks Originals

      Oh to be the bearer of bad news. Such is my lot in life today. It is over, as surely as the sun rises in the east, it is over. Ignore the calendar, it will corrupt your mind with thoughts that there are a few weeks...

    • What are your thoughts on the concept of  "quiet quitting"?

      What are your thoughts on the concept of "quiet quitting"?

      IT & Tech Careers

      Whether you were surfing social media, listening to a podcast/news, or just chatting with friends, you have probably heard of the term/concept of "quiet quitting". I know this isn't a new term/concept but it has seen a recent surge in discussion especiall...

    • How Old is too Old (Servers, not staff;-)

      How Old is too Old (Servers, not staff;-)

      Hardware

      kind of a re-hash of an old question (2012), I'm currently removing old kit from our racks & given some of it is now rapidly heading for 13 years + old & has only just been removed from service (Poweredge 2970 anybody?) I was wondering what the consensus ...

    SRDB ID Synopsis Date
    47430 Sun Fire[TM] 12K/15K: PCI SERR PCI error occurred on device #x  29 Oct 2002


    A Sun Fire[TM] 12K/15K domain panics with the following pci serr panic string:

    WARNING: pcisch-19: PCI fault log start: PCI SERR PCI error occurred on device #0 dwordmask=0 bytemask=0 pcisch-19: PCI primary error (0):pcisch-19: PCI secondary error (0):pcisch-19: PBM AFAR 0.00000000:WARNING: pcisch19: PCI config space CSR=0xc2a0<signaled-system-error,detected-parity-error> pcisch-19: PCI fault log end. panic[cpu128]/thread=2a10001fd20: pcisch-19: PCI bus 3 error(s)!

    NOTE: The stack itself can be different, depending on each specific case. What matters is the CSR values (specifically the "detected-parity-error" bit).

    SOLUTION SUMMARY:

    See FIN I0852-1 for details.

    From the FIN:

    The pcisch driver may panic on Sun Fire 15000 domains due to a parity error on the PCI Bus. In most cases this is due to a faulty hardware component. However, in some cases the panic cannot be corrected by replacing a hardware FRU. This second scenario may result in multiple unexpected domain failures if not corrected. This FIN describes how to diagnose and correct this type of pcisch driver panic.

    With every other panic of this nature, a hardware replacement has resolved the case. However, with one customer, repeated hardware replacements did not resolve the issue. The customer's issue has since been replicated on multiple machines in an engineering environment. There are some unique factors that are needed to create this scenario:

    A. To date, this problem has only been seen on 375-3030 (Crystal+) cards.

    B. All the panics have been in slot 2 of the I/O Boat (Slot 2 is the lower left position)

    C. Schizo 2.3 seems to bring the problem out with more regularity.

    D. Veritas software (specifically adding mirrors to volumes) seems to increase the likelihood of failure.

    Action:

    From the FIN:

    To diagnosis the pcisch panic from the above stack, follow these steps:

    a) Use the /etc/path_to_inst file on the domain or the cfgadm/rcfgadm commands to isolate the slot. For example, using the two methods with the panic above (pcisch-19):

    # grep pcisch /etc/path_to_inst "/[email protected],600000" 7 "pcisch" "/[email protected],700000" 0 "pcisch" "/[email protected],700000" 4 "pcisch" "/[email protected],600000" 19 "pcisch" <---------- "/[email protected],600000" 17 "pcisch" "/[email protected],600000" 5 "pcisch" "/[email protected],600000" 11 "pcisch" "/[email protected],600000" 15 "pcisch" "/[email protected],600000" 1 "pcisch" "/[email protected],600000" 3 "pcisch" "/[email protected],700000" 8 "pcisch" "/[email protected],700000" 12 "pcisch" "/[email protected],600000" 13 "pcisch" "/[email protected],700000" 16 "pcisch" "/[email protected],700000" 18 "pcisch" "/[email protected],700000" 6 "pcisch" "/[email protected],600000" 9 "pcisch" "/[email protected],700000" 2 "pcisch" "/[email protected],700000" 14 "pcisch" "/[email protected],700000" 10 "pcisch" "/[email protected],700000" 20 "pcisch" "/[email protected],600000" 21 "pcisch" "/[email protected],700000" 22 "pcisch" "/[email protected],600000" 23 "pcisch"

    In this case, instance 19 is "/[email protected],600000". To translate that into a slot location, break down the 9d into binary <10011101>, then add a space to obtain <100 1110 1>. That address now breaks down to slot 4 (100), skip the middle section (1110), pci 1 (or the pci slot on the left).

    The other option is to use the conversion which the dynamic reconfiguration interface provides:

    In this case, the issue is on expander 4 (ex4), I/0 board (b1), slot 2.

    b) Once you identify the correct location, there are three FRUs which could be causing the parity error: the hsPCI (p/n: 501-6302-03 or lower and 501-5397-11 or lower) also called the I/O boards), the 3.3v cassette (p/n: 501-5599-07), or the adapter itself.

    To narrow down the problem, employ standard hardware troubleshooting techniques and move/replace one hardware FRU at a time (CPRE recommends moving/replacing the adapter, then the cassette, and finally the PCI). If the problem follows a FRU (on a move) or no longer panics (on a replacement), CPAS the offending FRU.

    In the event that you are unable to follow this process, it may become necessary to replace all three FRUs at once. However, this is not recommended as this could impact FRU availability and will increase service costs to Sun.

    c) Once you identify a failing FRU and have taken appropriate action, track the machine's availability for an appropriate amount of time. Depends on the time taken to identify a failing FRU, the recommendation is to run the machine for twice as long as the panic interval. In some cases, that is 1 hour, while in others that is 24 days. If the problem persists or shows up on another pcisch instance, the machine could be experiencing the problem reported in Bug 4699182. Please escalate to CPRE.

    d) Once CPRE verifies the customer is experiencing this issue, choose a "workaround" option (of two) listed in the "Corrective Action" section.

    The root cause for pcisch driver panics, which are unrelated to faulty hardware, is still under investigation. There is no final fix at this time. In the meantime, use the recommended workarounds mentioned in the Corrective Action section below.

    CORRECTIVE ACTION:

    The following recommendation is provided as a guideline for authorized Enterprise Services Field Representatives who may encounter the above mentioned problem.

    Troubleshoot pcisch driver panics on F15K domains as outlined above. If the problem is determined NOT to be caused by faulty hardware, implement one of the two workarounds below.

    A. Replace the 375-3030 (Crystal+) cards with 375-3019 (Amber) cards (for slot 2 only). This has been shown to alleviate the issue after extensive testing. Since 375-3030 cards in slot 0 have not shown the problem to date, they do not need replacement.

    OR

    B. Move all 375-3030 cards to slot 0. This assumes there are enough I/O boats.

    INTERNAL SUMMARY: SUBMITTER: Joshua Freeman APPLIES TO: AFO Vertical Team Docs/HAS, Hardware/Sun Fire /15000 ATTACHMENTS:

    Copyright (c) 1997-2003 Sun Microsystems, Inc.

    Pavilion DV2000 - NMI: parity check / memory parity error

  • NMI:Parity error blue screen

    I have problem with blue screen hp pci bus parity error any program at any time. It is as it should be a hardware problem. When I run the Diagnostics on my computer everything seems to check out OK.

    Hello drichardson3,

    ·         You get this error blue screen randomly on your computer?

    ·         What exactly is the diagnostic test that you have run on the computer?

    The checking of NMI Parity error is an error related to a defective hardware on your computer. This is mainly caused by a faulty RAM.

    To resolve this problem, you may need to check on the RAM, I suggest you contact the manufacturer of your computer to check the hardware that does not work properly.

    Thank you
    Irfan H, Engineer Support Microsoft Answers. Visit our Microsoft answers feedback Forum and let us know what you think.

  • With PCI-6229 NMI Parity error

    Currently, I'm trying to get a PCI-6229 to work with one of our lab computers. We'll use LabVIEW 8.5.1 with DAQmx 6.7.1 to program the card. Using our measurement VI owner, the computer will crash at some point (not really in reproducible way) with a blue screen saying "NMI: Parity Check / Memory parity error. All the tests of auto and examples of NOR (delivered with LabVIEW) perform well however.

    Most likely, hp pci bus parity error, this problem is not a RAM issue (MemTest I tried, different memory chips, different memory banks). Also, the PCI computer bus works very well otherwise (for any other acquisition cards for example). Annoying enough, the card seems to do a great job in an old and slow computer. Which is maybe something to look at? Or are there other ideas?
    Our workplace is a Fujitsu-Siemens of Celsius M460 with BIOS version 6.00 rel. 1.09 running Windows XP (32-bit version). The software to use with the card is LabVIEW 8.5.1 with DAQmx 6.7.1.

    Dear Lutz,

    I could reproduce the blue screen, and
    changed your program in order to avoid the race condition. What is
    actually happens is you want 2 tasks over time the
    AOSampleClock as a source before the task of AO started.

    When
    programming as in the example I sent you (see attachment VI), hp pci bus parity error, you
    shouldn't deal with this blue screen problem more. However, I recognize
    that such a thing should not happen even when it's 'bad' programming. I'm going to
    inform the development so that it will be corrected with the next DAQmx
    version of the driver.

    Merry Christmas,

    P. Lawrence

    National Instruments

  • Hardware malfunction: NMI Parity error

    Screen blue/hardware malfunction/call your provider of support material / parity memory check error / NMI:parity / this happens more frequently

    The RAM in your computer seems to be failing. Run the memory in memory diagnostic tool by typing in the search box of the start menu by pressing Enter.

    Use the scanner on this site http://www.crucial.com/ to find out what type of memory, you have to buy if it needs to be replaced.

  • HP Pavilion G6: A broad check memory failed

    Hey all

    My HP Pavilion G6 has been giving me the BSOD (0x7A) recently so I ran some checks computer diagnostic provided from the HP recovery partition. HD and memory short tests came positive, but the failure of verification of the extended memory with the following failure ID: 9GE3L0-6567MK-MFPX01-401003.

    I also run windows memory test diagnostic and it came positive.

    Can you help me?

    You can test yourself by removing the bars of memory.

    Put one of them into the soDIMM slot then power and closest to you inside the laptop on the laptop.

    If Notepad boots into Windows and do not present problems or the faiols the test of memory, while you have not installed the module has problems and needs to be replaced by an identical to one that is installed.

    If the problem persists, then try to replace the decompiler error 796 unhandled construct in list installed with the other and run the same test.

  • Satellite Pro A100 - NMI memory parity error parity check

    Sometimes I get this BSOD error during 2 months.
    Hardware malfunction call your provider for support NMI: Parity Check / Memory Parity Error * the system stopped *.

    It can occur if the laptop is asleep, or even refreshing a screen save or Stand-By condition.
    Model PSAAPE - 00s00KEN 2 GB installed. I checked that the memory is installed correctly. It's a laptop very clean with no dust clutter things. Aside from the Ram "goes wrong" and developing a fault, can anyone suggest another cause? It doesn't seem to be an obvious solution to this problem on a forum I've seen so far. Maybe it's my RAM that fails (but it seems to do it when he is not be underlined!) It could be the video drivers. who knows? I hope somebody.

    Hello!

    In your case, I would check the RAM, I think that's the problem.

    You can do this with Memtest86:
    http://Memtest86.com/
    Memtest86 is a diagnostic tool to check the RAM. Here, you can also download a CD image.
    It s easy to use. Run the test of 3-4 hours and then you will see if the RAM has some errors.

    Good bye

  • Hardware malfunction NMI: parity check / memory parity error * the system stopped *.

    I installed ENLWI-G2 802.11 g Wireless PCI Adapter in my Dell Optiplex 760 with XP SP3 32-bit Windows. But it gives me a blue screen with the error:

    Hardware malfunction NMI: httpsendrequest error 12045 check / memory parity error * the system stopped *.

    How to solve this error?

    Try to switch on the memory modules. Ask the MS site for more information on the specific error.

  • Satellite P200 - Parity Check / Memory Parity Error

    Hi all experts!

    After updating a driver, I get this above mentioned message.
    + Message ' hardware malfunction NMI Parity Check / Memory Parity Error.

    But just at the moment where the P200 falls in sleep mode. I can't wake up and have to do a hard reboot. Windows is starting and works perfectly and everything seems to be okay!

    Any idea?

    Thanks in advance!
    YB

    Hello

    This behavior can occur if a hardware component malfunctions, or if it has installed the damaged or incompatible drivers.
    I think that you should remove the driver updated or installed first.
    If this does not work, test the laptop with preinstalled system cool.

    Finally if this is insufficient, a hardware malfunction might be possible.
    In this case the RAM modules need to be tested as the first part.

  • How can I fix "memory parity error" - a hardware malfunction?

    My video display keeps going out and lose pixels.  Occasionally, I get an error message "memory parity error" and "malfunction of equipment."  -What it means and I can fix it?

    You forgot to give us information on your computer, hp pci bus parity error, so all I can give you is general advice.

    1, hp pci bus parity error. in the case of a desktop computer, connect it to another monitor, hp pci bus parity error. If all goes well, replace the original monitor. If the problem persists when connected to the test screen, replace your video card.

    2. in the case of a laptop computer, contact technical support of computer mftr. There is a hardware problem, probably with the video chip, which you can't fix yourself. MS - MVP - Elephant Boy computers - don't panic!

  • MD3000 Raid Controller Module memory parity error

    MD3000 hp pci bus parity error two controllers. One of the hp pci bus parity error does not have. SO I replaced it with a used controller, without work. All errors are gone, except a "RAID Controller Module memory consistency error".

    Recovery Guru recommends steps that I followed without success.

    Need help in this forum.

    Paul

    Hello Paul,

    What you need to do is on the replacement controller to pull the raid battery and wait about 2 hp pci bus parity error then reinsert it again. Also I want to try to do is to Flash the hp pci bus parity error on the system as well.

    Please let us know if you have any other questions.

  • Serial communication - ignore parity error

    I have a question about how LabVIEW opens a serial port for communication. I communicate with a device that uses a protocol owner. It sets and clears the parity bit to indicate the nature of the response. For example, the orders are sent with the parity bit higher while responses are sent with the weak parity bit (unless the answer is at the end of the transmission, in which case the device sets the parity bit high to indicate).

    My problem is the way that LabVIEW opens the serial port for communication. Using Portmon, that I captured the control indicators, that it sends to Windows to configure serial communication:

    IOCTL_SERIAL_SET_LINE_CONTROL Serial0 SUCCESS StopBits: 1 Parity: MARK WordLength: 8IOCTL_SERIAL_SET_CHAR Serial0 SUCCESS EOF:0 ERR:0 BRK:0 EVT:0 XON:11 XOFF:13IOCTL_SERIAL_SET_HANDFLOW Serial0 SUCCESS Shake:1 Replace:44 XonLimit:64 XoffLimit:64

    Note the values 'Shake' and 'replace '. In my view, they are originally bytes with parity errors is removed. A separate RS232 Comm Debug tool that I use with success looks like this:

    IOCTL_SERIAL_SET_LINE_CONTROL Serial0 SUCCESS StopBits: 1 Parity: NONE WordLength: 8IOCTL_SERIAL_SET_CHAR Serial0 SUCCESS EOF:0 ERR:0 BRK:0 EVT:0 XON:11 XOFF:13IOCTL_SERIAL_SET_HANDFLOW Serial0 SUCCESS Shake:0 Replace:80000000 XonLimit:128 XoffLimit:128

    Notice the difference in values. By using this tool, hp pci bus parity error, Windows does not packages with parity errors - that's what I want. Is there any way to change how LabVIEW opens the serial communication port to achieve?

    I tried to change the parity, where the ILO is defined differently, but I think that I am running in a race condition; LabVIEW can not run the code and change the mode of fast enough parity before the next byte of data is sent by the device.

    Ravens fan: the parity bit, in the proprietary protocol, hp pci bus parity error, that I use, hp pci bus parity error, is not used for parity checking. Basically, the protocol uses a 9-bit serial communication. The parity bit must be paid or compensated according to what byte do (if it is a command, hp pci bus parity error, if it is the end of transmission, etc.).

    I found an old post on this page which seems to answer my question (my apologies for not completely research before posting. I learn the right use/search phrases that I find more information). I download the 3.4.1 version of VISA now.

  • What does "a parity error was detected on \Device\ide\idePort0" mean and how can I fix?

    I have a Pentium avi request format error, XP SP3, 2 HDs installed, and I don't think I have SCSI but in my registry, it shows the HDs and two CD - RW and DVD drives listed under SCSI and there is no topic such as IDE, Atapi or AT (the area I'm talking about in the registry is: \HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\) so I don't know what is happening in this area.? Anyway, everything else refers to above devices IDE or Atapi etc.

    As well as the above parity error, I noticed a little more that I will add here:

    "The driver has detected an error on \Device\Harddisk0\D controller" (this is an ALL NEW HD)

    "The device, \Device\Harddisk1\D, has a bad block" (it's second HD giving the same error msg, the last HD failed and this is used)

    "The device, \Device\CdRom0, has a bad block" (this is my CD - RW drive, which seems to work very well, it's the DVD player that is not working properly)

    "While validating this \Device\Serial0 was really a serial port, a fifo was detected. The fifo will be used. »

    All of these errors are coming together for the most part. Please help as I just replaced a hard drive failing during the summer, now it is looking like another is a failure, but I want to know if something else in my computer can cause drives to fail, or causing errors in some way, or any other information anyone can give me to help before you start the process of replacing a HD failure (again!)

    Thank you. Denise

    Hi groovydee,

    Method 1

    I suggest you reinstall the controller and chipset drivers by contacting the manufacturer of the computer, check to see if it helps.

    Method 2

    If the previous step fails, then you need to check disk scan on the hard drive to scan and difficulty of bad sectors on the disk.

    How to perform disk error checking in Windows Hp pci bus parity error While running chkdsk on the drive if bad sectors are found on the hard drive, then chkdsk attempts to repair this area if all the data available in this area may be lost.

  • start using SD hp pci bus parity error Pavilion dv2000 memory card

    Hello

    I wanted to boot from SD memory card in my HP Pavilion dv2000 laptop. What should be the BIOS for this setting.

    Thank you!

    Shivchal

    I don't think that you can start from your reador of card for laptop

    but you can start from your SD card using a USB card reader

    But u should create this card as bootable,

    There are many free application on the internet, just google,

    and make your bootable SD card, then use it.

    I used "USB_MultiBoot_10" and I create a portable bootable computer cos XP instalation disk of my father, dvd does not work.

    I do not have the link at the moment. but I got frm google search.

    Have FUN BRO,

  • Series parity errors, and clearing the error replacement character

    I have a situation where I have to change the parity on the last byte of an outgoing message.  E problem is that when I try to play, I get a parity error and the error replacement character appears in the output.  I have a few extra bytes and a few bytes lost due to masking.  This thread stated that visa 3.4.1 there is a configuration INI directive which would disable the error replacement character.  I installed 4.4.1 and were not able to make hp pci bus parity error work properly.  I'm curious to know if anyone knows if this setting without papers is always available and how to make it work.

    Thank you.

    Thanks to Tyler of OR helped me to determine the appropriate location to use.  The entry is valid, I just used the wrong visaconf.ini file.  The correct file is located in
    (

  • Error: A parity error was detected on \Device\Ide\IdePort0 at system startup

    Original title: Windows XP error 11

    Event Viewer maintains with the following messages appears at the start of windows xp,

    The driver has detected an error of the Comptroller on \Device\Harddisk0\D.

    A parity error was detected on \Device\Ide\IdePort0.

    Hi plogmine,

    We recommend that you change the setting of firewall/security at different levels and then try to access files and folders on the network.

    See this article for more information: http://support.microsoft.com/kb/814112

    Visit our Microsoft answers feedback Forum and let us know what you think.

  • General discussion

    • PCI Parity Error on system startup

      by twuf · about 19 years, 10 months ago

      When booting 1st thing in morning- Dell Pentium III Win98 (nothing changed) i get BSOD – “system error -Memory parity error detected -system halted”, hp pci bus parity error. When i hit off buttom or restart, the black screen comes up and quickly displays five lines of typeall saying “PCI Parity Error on Bus/Device Function 008h”. When computer reboots it does so in Safe mode or Normal ok. and computer runs fine for the rest of the day. Is this telling me a ROM Chip is going bad or what?

    All Comments

      • PCI Parity Error on system startup

        by ann777 · about 19 years, hp pci bus parity error, 10 months ago

        In reply to PCI Parity Error on system startup

        Unplug the computer
        Open the system and ground yourself to the metal part of the system.
        Disconnect your memory from the systemboard and then reseat the same memory in the same slot.
        Repeat with each memory SIMM.
        You might also want to make sure that everything else in the system (any daughterboard cards) are properly seated as well.
        Close the system and power it up.

        Generally the usual (quick) fix with parity errors is to reseat the memory. If your system has been moved recently or the general on/off (heating and cooling) of a system will tend to expand/contract against the connectors and cause this slippage problem.

        If the problem persists, then yes, look at the individual chips abd run diagnostics to see which memory address(es) are affected (and thus which chips).

      • PCI Parity Error on system startup

        by maxwell edison · about 19 years, 10 months ago

        In reply to PCI Parity Error on system startup

        At first glance I would think that you have some RAM that has gone bad or is going bad. If you have any extra RAM or some from another machine, you might try new (different) RAM.

        I also saw this problem described on Microsoft article Q232768, “Error Message: Memory Parity Error Detected. System Halted”.

        http://support.microsoft.com/default.aspx?scid=KB;EN-US;q232768&#038;

        REMOVE SPACES from the pasted URL

      • PCI Parity Error on system startup

        by darts32 · about 19 years, 10 months ago

        In reply to PCI Parity Error on system startup

        Can you tell me if you have an ATI Rage Fury video adapter? It has something to do with one of your PCI cards. If you have the ATI card try the Microsoft Knowledge Base Article – Q232768.

        • PCI Parity Error on system startup

          by twuf · about 19 years, hp pci bus parity error, 10 months ago

          In reply to PCI Parity Error on system startup

          I do have ATI Rage adapter and updated the driver. So far computer hasn’t crashed. Maybe that is the answer. Thanks

      • PCI Parity Error on system startup

        by twuf · about 19 years, 10 months ago

        In reply to PCI Parity Error on system startup

        This question was closed by the author

    NMI Parity Check/Memory Parity Error

    Windows Operating System (OS) users may encounter the NMI Parity Check/Memory Parity Error during the computer start-up process. The error is normally displayed when a computer typedef error c2371 redefinition different basic types or stops responding during the Windows start-up process, and may be the result of a number of hardware or hardware configuration problems.

    What does hp pci bus parity error NMI Parity Check/Memory Parity Error Look Like?

    A number of error codes can be displayed when the error occurs. These google chrome gmail bad request error 400 Parity Check/Memory Parity Error, NMI: Bus Timeout, NMI: Software NMI generated, NMI: Eisa IOCHKERR board x, NMI: Channel Check/IOCHK, or NMI: Fail-safe timer

    The error codes typically start with the “*** Hardware Malfunction” message and a display message indicating that the computer or system has been “halted” follows.

    Why does the NMI Parity Check/Memory Parity Error Occur?

    The NMI Parity Check/Memory Parity error typically occurs if a computer hardware component is damaged, malfunctions, or if an incompatible driver is installed on the computer.

    How to Fix the NMI Parity Check/Memory Parity Error

    Most hardware problems that trigger this error involve the computer’s RAM, motherboard, cache memory, or a hardware adapter on the computer. The following are troubleshooting steps that can be taken to identify the cause of the error:

    Verify Your Computer’s Memory

    Step 1 – Remove any new RAM modules that have been installed on the computer.

    Step 2 – Restart the computer to see if the error message continues to be displayed.

    Step 3 – If the error is eliminated, then replace the RAM modules that were installed. If it persists, repeat the process but only leave the minimum amount of RAM necessary to boot the computer in order to determine if the computer has faulty RAM.

    Step 4 – Replace the faulty RAM modules if they are the source of the problem.

    The Microsoft RAM diagnostic tool found at: http://oca.microsoft.com/en/windiag.asp may also be used in order to help identify faulty computer modules.

    Verify the Adapters on the Computer

    Step 1 – Remove all adapters that are not required to run or start the computer. Most Windows computers can be run with only the video and drive subsystem controller adapters.

    Step 2 – Restart the computer. If the error does not appear, then the problem is one of the adapters removed in step 1.

    Step 3 – Reinstall one adapter at a time until the error is displayed again. This determines the adapter that was the source of the error. Visit the adapter manufacturer’s website and download and install the latest version.

    Step 4 – Re-seat all adapter hardware cards if the error is not eliminated to ensure that this is not the cause of the problem.

    Verify the Computer BIOS

    Step 1 – Ensure that the latest revision of the computer’s BIOS and firmware configuration are installed.

    Step 2 – Open the BIOS and change the configuration to “load Fail-safe defaults” or “BIOS defaults,” set “Plug and Play OS” to “No,” and disable anti-virus protection options located in the BIOS.

    Step 3 – Restart the computer to see if the error has been corrected.

    Check for Driver Updates

    If Windows OS was recently upgraded or new hardware installed, then an outdated device driver may be the cause of the error.

    Step 1 – Ensure that Windows Updates is configured to automatically update the computer from the “Windows Updates” application found in the computer’s “Control Panel.” Manually update the Operating System. Restart the computer hp pci bus parity error completing the manual Windows update.

    Step 2 – If any new hardware was installed, remove the hp pci bus parity error drivers in the “Add/Remove Programs” menu after updating the OS in Step 1 and canon error 5200 reset the computer.

    Step 3 – Check the other device drivers installed on the computer for updates if the error is still being displayed and an update as required. Restart the computer after each device driver update to complete troubleshooting it.

    I think your motherboard has failed.

    Your PCI bus slots are wired to an 8 bit parallel data bus. The basic way to constantly monitor this is to error accessing .big fifa a nineth bit. Then the circuits that put the data on the bus count the number of bits in the word and if it is an even number of bits usually adds a parity bit so the word contains an odd number of bits. This is called "odd parity". Even parity can be used, the the usual convention is odd. Then once the data arrives, it's checked, hp pci bus parity error. If error 2013 during query mysql picked up or lost a bit, the system flags an error.

    Yes, there's an obvious flaw in the system. What if you pickup or lose two bits? Parity checking will not be able to detect that. A more complex ( read expensive) system can correct a single bit error and detect a 2 bit error.

    You have this system for the Hp pci bus parity error bus, but not the PCIe bus. Remember, PCI Express is basically a serial bus



    Google "parity error" or "parity checking".

     

    DL380 G4 Won't Boot

    Posted by christh0mas

    One of my servers, an old Proliant DL380 G4 recently shut itself down and when booting, it displays this error and will not proceed any further:  "PCI bus parity error slot ?".  I have tried shutting it down and reseating all cards on the motherboard but this did not help.  While searching on this error around the internet, I found that it indicates a problem with the motherboard.  I do have a spare server of the same model as this and I thought about swapping the motherboard out with it.  I am concerned that my RAID array will be broken if I do this and all of my data will be lost.  The RAID config on this server is different than the other server but they do both use the same array controller card. 

    What do you think?  Am I OK swapping the motherboard or will this spell disaster?  I’d rather not hp pci bus parity error to rebuild this server so I’m hoping there’s something that can be done to resurrect it.

    Thanks in advance.
    -Chris

    • Chad.w
      Chad.wThis person is a Verified Professional
      hp pci bus parity error This person is a verified professional.
      Verify your account to enable IT peers to see that you are a professional.

      Well, if your motherboard is toast, it is going to have to be replaced. So, replace it and either it works or it doesn't. My experience with HP arrays is that the drives will report their configuration to the array controller so you should be ok.

      Was this post helpful?thumb_upthumb_down
    • The RAID config is in the drives, so you should be OK with the swap.

      Was this post helpful?thumb_upthumb_down
    • This same thing happened to this server a few weeks ago.  I shut it off for a few minutes, started it back up and it booted normally.  Unfortunately, that didn't happen this time.  I'll try swapping out the motherboards in the AM.

      Thanks for the input.

    • Jono

      I've had a few dl380's do that and swapped the drives and controller to a spare without a problem

      Was this post helpful?thumb_upthumb_down
    • Ahh, that sounds much easier than swapping the entire motherboard.  I'll give that a shot.

      Thanks.

    • I have had a problem where it error 0251 system cmos checksum bad boot if any USB device is connected. (eg USB ext HD for backup). Early proliant. Possibility??

    • Thanks Jono.  Swapping the controller and drives did the trick.  Phew!

      Was this post helpful?thumb_upthumb_down
    • christh0mas wrote:

      Thanks Jono.  Swapping the controller and drives did the trick.  Phew!

      Phew!  Phew! 

    • Document control/access solution to prevent opening specific documents

      Document control/access solution to prevent opening specific documents

      Best Practices & General IT

      Hey all,Before I get into the problem at hand, I realize this may be a multi phase problem and the document side of it may only be resolving a specific portion of the problem, but I have to start somewhere.The issue to oki error 142 fatal error off the fat on error resume next vba excel make it as simpl.

    • Testing Touch Screen

      Testing Touch Screen

      Hardware

      Hi, We have a touch screen on a CNC machine on our production floor that's causing issues. Bottom 1/2" or so of the screen never registers a touch. The rest of it works sometimes, but sometimes you might try to hit a button but the touch registers a few i.

    • Spark! Pro Series - September 2nd, 2022

      Spark! Pro Series - September 2nd, 2022

      Spiceworks Originals

      Oh to be the bearer of bad news. Such is my lot in life today. It is over, as surely as the sun rises in the east, it is over. Ignore the calendar, it will corrupt your mind with thoughts that there are a few weeks.

    • What are your thoughts on the concept of "quiet quitting"?

      What are your thoughts on the concept of "quiet quitting"?

      IT & Tech Careers

      Whether you were surfing social media, listening to a podcast/news, or just chatting with friends, you have probably heard of the term/concept of "quiet quitting". I know this isn't a new term/concept but it has seen a recent surge in discussion especiall.

    • How Old is too Old (Servers, not staff;-)

      How Old is too Old (Servers, not staff;-)

      Hardware

      kind of a re-hash of an old question (2012), I'm currently removing old kit from our racks & given some of it is now rapidly heading for 13 years + old & has only just been removed from service (Poweredge 2970 anybody?) I was wondering what the consensus .

    0 Comments

    Leave a Comment