Hardware Malfunction NI PCI 8252 in Windows 7 x64

Hi everyone,
I need some help with this PCI card as it is giving me an error before reaching the Log On screen in Windows 7. This card works perfectly fine in Windows XP, but not Windows 7. The documentation for this card did not state anything related to Windows Vista/7, so I'm not sure if it is fully compatible with Windows 7.
I've performed the following tests below:
1. Insert PCI Card to a WinXP Environment and it worked fine.
2. Re-image the computer (HP) to a fresh Win7 and it failed.
3. Test PCI card with a different machine (DELL), failed.
4. Updated BIOS on the HP Machine, failed.
My machine is running on Windows 7 x64. Any other ideas that could possibly be giving me this error?

Hi vangjer,
The driver for that card is actually from Microsoft (it is the standard OHCI driver Windows ships with) and that error you are seeing comes from something much lower than what the IMAQdx driver interacts with. That error means something on the firewire chipset acted in a way the motherboard didn't like. I've seen similiar reports of incompatibilities on older 1394a cards using the VIA chipsets (what the 8252 uses) such as http://arstechnica.com/civis/viewtopic.php?f=11&t=1138921.
Here's my two suggestions to try:
- Try switching the OHCI driver for the card to the legacy one. Microsoft make some significant changes to the driver in Windows 7 which fixed some old bugs (and brought some new ones), but it was a complete re-write and the VIA chipset certainly pre-dated it. Some directions for swapping it are here: http://www.studio1productions.com/Articles/Firewire-1.htm . This still may not fix it (since it could stem from a motherboard incompatibility that just happens to be triggered by a different configuration by Windows 7) but seems worth a shot.
- Upgrade to a newer 1394b chipset (like what the PCIe 8253 contains). Ones such as these with the TI chipset work really well and I've never seen any incompatibilies.
Eric

Similar Messages

Sudden motion sensor - hardware malfunction - beach ball lag related

Hello,
I have a macbook pro 13" bought in July 2009 with the 160Gb Hitachi 5400 rpm hardrive and 2Gb Ram. I also have the beach ball lag problem and have been reading many posts about it on this and other forums. However, I noticed today that in my System Profiler - Hardware overview, my sudden motion sensor (sms) is indicated as State: Disabled. I look at the state of the sms through the terminal window (sudo pmset -g) and is says sms 1!!! Something is wrong there! Then I executed "sudo dmesg | grep -i error | grep -i sms" to check whether there are any errors about SMS. and I get the following line:
SMS::checkForInvalidInts ERROR: we appear to have a hardware malfunction
SMS::setupInts ERROR bad hardware detected, disabling the interrupts
Then I looked in the Console at the System.log and realized that everytime the beachball lag was occurring, I was getting the same message in the system log:
Aug 23 17:07:28 localhost kernel[0]: SMS::checkForInvalidInts ERROR: we appear to have a hardware malfunction
Aug 23 17:07:28 localhost kernel[0]: SMS::setupInts ERROR bad hardware detected, disabling the interrupts
Although there are many posts on the beach ball lag and on the firmware updates, I don't seem to be able to find any information about this error what it means and how it might be fixed.
I also tried to test the SMS. When I enable SMS through the terminal command, I hear a click if I move my computer up and down through the air. When I disable SMS through the terminal command, I don't hear the click. So I'm very confused!
Has anybody got a similar issue with their sms and have they been able to resolve it?
Thank you very much.
Noemi

Hey, have you called Apple? I have the exactly same problem as you. Hope apple will give us a update for fixing this problem.

How do I troubleshoot a blue screen on a Pavilion dv4-1123us with "hardware malfunction call hardware vendor for support" message?

I keep getting this screen and before I have to call and pay and wanted to see if there was something that I could do.
Pavilion dv4-1123us get blue screen with "hardware malfunction call hardware vendor for support"
This question was solved.
View Solution.

I would say its just a conicidence and recommend you to do a system restore. As its an intermittent problem, you never know if you face same issue once again.
//Click on Kudos and Accept as Solution if my reply was helpful and answered your question//
I am an HP employee!!

Using a laptop for image acquisition in combination with PCI-1428/PCI-8252

I am not too confident about PCMCIA framegrabbers so that I would like to use either a cameralink camera with the PCI-1428 or a Firewire one with PCI-8252.
Are there any obstacles accommodating the PCI cards in an PCI Expansion box?

You could do it, but why? Just get a firewire card for the laptop and go direct. You can get them with external power supplies to power the camera. It will work just the same and you won't have to lug around a big box with all your other equipment.
Bruce
Bruce Ammons
Ammons Engineering

Ralink (Mediatek) Bluetooth PCIe Adapter for Windows 8.1 driver missing

plz send me solution ralink Bluetooth PCIe Adapter for Windows 8.1 driver missing

Hi:
This is the latest W8.1 BT driver for that card.
http://h20565.www2.hp.com/hpsc/swd/public/detail?swItemId=ob_139921_1

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...

[how to]x-fi extreme pci-e - mic working at windows 7 x64

Hi folks,
after spending like 7 hours trying and trying to get my mic to work with the PCI Express X-Fi Xtreme Audio under windows 7 x64, I finally found the way!
> Uninstall all creative software from program-list, without restarting yet, then uninstall driver from device-manager (ger?te manager). Check box "remove driver". reboot.
> Install only! http://support.creative.com/downloads/download.aspx?nDownloadId=0962? XFXA_PCDRV_LB__04_0000.exe
After rebooting, do NOT use the web update, just cancel the **bleep** and f*** all the software crap no one even needs.
After that U go here http://creative.techinhiding.com/2009/03/creative-console-updated-soundblaster-audigy-windows-7-drivers/
or download directly http://techinhiding.com/creativeblog/softwares/CreativeConsole_Mar09.exe
After doing that U can start the creative audio console from the start menu, go to button on the right (connections/anschl?sse) und switch FlexiJack to microphone! That?s it.
Good Luck and less gray hairs for you!
ps: Thank you creative for sucking even more than ATI one year ago!
pps: If someone knows, how I get SPDIF + normal 3.5mm output to work simultanously, please tell me...

mmmh I hope that this thread about solving the problem of the microphone which wouldn?t work under windows 7 might be helpful for some people...

PCI Simple communications controller driver suitable for Windows 7 x64

Hi,
I'm looking for a PCI Simple communications controller driver suitable on Windows 7 x64.
Does this have anything to do with Bluetooth? Because the Bluetooth is not working 100%, Nokia Suite does not recognize the Bluetooth device on my laptop.
The Bluetooth symbol is in the taskbar, but only when i use "fn"+f12(wireless com.) after startup
I have a HP envy 17 j009ed.
Kid regards,
NickdB

NickdB
Identical system, you find the drivers bios etc. here
http://h30434.www3.hp.com/t5/Notebook-Operating-Systems-and-Software/Windows-7-64bits-drivers-for-En...
Say thanks by clicking the "Kudos! Star" which is on the left.
Make it easier for other people to find solutions, by marking my answer with "Accept as Solution" if it solves your issue.

Tecra A8 BSOD - Hardware malfunction

Hi every one.
I have Tecra A8 and there's problem come to me all the time.
Blue screen with this message:
Hardware malfunction; the system has halted. Call your hardware vendor for support
I changed the hard drive & the RAM but it doesnt work
Any one had this before

This sounds not good buddy.
Looks like a serious hardware problem. Maybe its related to the motherboard.
I think you should do what is written in the message: Call your hardware vendor support.
Therefore I would recommend contacting the local Toshiba authorized service provider.
Good luck

Iphone 4s is not recognised by my pc; I get a message to say that the device malfunctioned and not recognised by windows

My iphone 4s is suddenly not recognised by my pc; I get a message to say that the USB device is not recognised, and that the last device malfunctioned and not recognised by windows.

Hey Jacky,
Welcome to Apple Support Communities.
Take a look at the article linked below, it provides information and troubleshooting suggestions that can help you resolve the issue with your iPhone 4s not being recognized by iTunes on your PC.
iPhone, iPad, or iPod not recognized in iTunes for Windows - Apple Support
Cheers,
-Jason

HP SERVER SCSI U320 PCI-E ADAPTER [412911-B21] windows 7 x64 driver?

Hi,
the card 412911-B21, can be installed on windows 7 x64?
I only found these drivers: http://goo.gl/woBrl
Thank you

Hello Mr. Wells,
Thank you for your question.
However, the Small Business Support Community is limited to Cisco Small Business Products, and the Aironet products are considered as a Enterprise level devices.
I recommend you to post this question on the on the correct forum, in order to get a better response.
You can move your post using the Actions panel on the right.
Best regards,
Diego Rodriguez
Cisco Small Business Community Engineer

Using NI-IMAQ imgSnap (ANSI C) with Windows 7 x64

Hello,
I am trying to perform some basic image acquisition using ANSI C calls to NI-IMAQ (as distributed by the November 2009 release of NI Vision). I am developing on Windows 7 x64.
Setup seems to work fine, but when I make the following call:
void* theTempBuffer = NULL; Int32 theRetVal = imgSnap(mSession, &theTempBuffer);
I get the following error:
This 32-bit device is operating on a 64-bit OS with more than 3GB of physical memory. This configuration could allocate 64-bit memory which is unsupported by the device. To solve this problem, reduce the amount of physical memory in the system.
I see this whether I compile to a 32-bit or 64-bit target. I would have concluded that the PCI-1422 simply isn't supported under Windows 7 x64, but the card (and attached camera) work fine for snapping or grabbing images when I go to the Measurement & Automation Explorer.
Thanks for your help.
Solved!
Go to Solution.

Hi KKRand,
Currently you are using a non-supported combination. Due to the hardware limitations of the 1422 board, it is limited to 32-bit DMA. Due to IMAQ's C API where users have the ability to allocate their own buffers to be acquired into, we have no way to enforce that this memory is below the 32-bit boundary for *all* use cases of our C API.
Because of this, we officially do not support using the IMAQ C API on a board with this 32-bit DMA limitation on a 64-bit system and more than 3GB of memory because we cannot guarantee that a user's application will run without any modifications. These limitations do not apply if you use an API like LabVIEW where the user does not control the memory allocation directly or you have a newer board with 64-bit DMA support.
Measurement & Automation Explorer can get around this limitation because it uses limits its use of our API to ensure that memory is allocated properly to guarantee that it is below the 32-bit boundary if you have an affected board/system combination. With possibly a little modifications to your app, you should be able make it able to work as well, but as I mentioned it is not an officially supported combination.
The modifications to your application are:
- Make all allocations of image buffers that you will use for acquisition from that board be allocated by calling into imgCreateBuffer() as opposed to allocating them by other means (new, malloc, on the stack, etc). Memory allocated in this manner must be released by calling imgDisposeBuffer().
- Disable enforcement of checking this condition by calling a private function exported from imaq.dll as "int niimaquDisable32bitPhysMemLimitEnforcement(SESSION_ID boardid)"
The first part is likely already satisfied in your case because the high-level imgSnap() allocates the memory for you and thus ensures that it meets our requirements. You'd have to add the second to your application. Keep in mind this is unsupported. We currently do not check that all buffers in your bufferlist were allocated in this manner and so if you allocated a buffer by some other means you would get a run-time configuration failure when and if any memory ever fell past the 32-bit boundary when you start acquiring.
This behavior might change in the future, but from a support standpoint it is unlikely that we'd officially support this configuration since it is highly dependent how the user's application is written (if it relies on its own memory allocations). What we wanted to avoid was customers starting with simple usage of our API (like a high-level Snap()) and finding it working but then later going and allocating their own buffers and seeing a failure.
Hope this helps,
Eric

USB EHCI chipsets causing Windows 7 x64 failures in Pavilion

I use Acronis TIH 2012 to backup the primary and logical partitions on my pavilion g6 notebook, currently running windows 7 x64 with 8Gb RAM. I have a problem on this particular notebook, it looks like a hardware compatibility issue, and this query is about the USB hardware of the notebook compared to other pavilion machines. The problemI can successfully backup the primary partition (C: drive) of the internal SATA HDD to a separate logical drive on that internal HDD, but when I try to backup the C: drive to an external USB3 drive the backup starts, creates two 4.7Gb files (out of a usual 6 files in the set) on the external drive and then fails. Fails HARD - usually I need to completely remove power (mostly by removing the battery) and do a cold boot to get control back. The failure seems to occur when the software thinks the usb drive has disconnected. The softwareThe TIH application is a 32bit item that works fine on a 32bit windows 7 platform (desktop and laptop) both using external usb3 drives as the target. Those machines however only only 4gb RAM installed. Other software - eg windows explorer and demanding video editing programs - work fine using data on the external usb drive. Pavilion hardwareA member (joey) on the Acronis forum has reported a case where a specific combination - windows 7 x64, more than 4Gb RAM and the nvidia EHCI chipset - caused his Pavilion a6403 system to malfunction using an external usb3 drive with this combination. Microsoft issued a specific hotfix for this - see the Kb article here https://support.microsoft.com/en-us/kb/976972which Joey reports as correcting the problem. The questionMy notebook and Joey's are members of the HP pavilion family. Both use the same windows 7 x64 OS, and have more than 4Gb RAM. Does my g6-2002 use the same nvidia EHCI usb controller chipsets as the a6403? In short, could his problem and mine be the same one? Thanks, Davidk10

Quote from: Bas on 19-November-10, 22:57:34
Those few need extra drivers.
As they are USB3.0 ports: http://eu.msi.com/index.php?func=downloaddetail&type=driver&maincat_no=1&prod_no=2025
Yea as I stated earlier, after installing these drivers all the usb ports stopped working in the current windows 7 install.

SCXI and Aquisition with Windows 7 x64

Our IT just updated our laptops and we received Windows 7 x64.
For data acquisition, we use SCXI hardware in the SCXI-1000DC chassis and a SCXI-1600 USB DAQ Card. In the process of getting my NI hardware configured on the new laptop, I discovered NI does not support Windows 7 x64 for the SCXI-1600. The other options to connect the SCXI-1000 to a laptop are the DAQcard-6062E and the DAQcard-6036E, neither which support Windows 7 x64. According to the information below, there are no plans to support x64.
What are my options to continuing using the hardware we have invested in with the laptop running Windows 7 x64?
Re: scxi and drivers?
[ New ]
04-13-2010 01:09 PM
For those USB devices, there are not currently plans to add support for 64-bit operating systems. This is due to incompatibilities between the USB design of these older devices and the USB implementation in 64-bit version of Windows.
Regards,
Seth B.
Product Support Engineer | Multifunction Data Acquisition | National Instruments
“Engineers like to solve problems. If there are no problems handily available, they will create their own problems.”- Scott Adams
Have some feedback about our products, or can't find a product to suit your needs? Let us know! Visit the Data Acquisition Idea Exchange!.
Solved!
Go to Solution.

You will need the NI SCXI-1349 connector block and the SH68-68-EP cable. The SCXI-1349 plugs in to the back of your SCXI module and the cable connects the 1349 to the USB M Series Mass Termination device. All of the rest of the setup is identical to any PCI/PXI E Series device. The USB M Series device will be the Analog-to-Digital converter for the system instead of the SCXI-1600.
Seth B.
Staff Test Engineer | National Instruments
Certified LabVIEW Developer
Certified TestStand Developer
“Engineers like to solve problems. If there are no problems handily available, they will create their own problems.”- Scott Adams

Re: Tecra A10-PTSB1E Windows 7 x64 Device Driver Missing

We've done a clean install of Windows 7 x64, downloaded and installed the Windows 7 x64 specific drivers/files from [http://uk.computers.toshiba-europe.com/innovation/download_drivers_bios.jsp?service=UK] but still have an unknown hardware device showing in Device Manager as -
Other devices
PCI Simple Communications Controller
Hardware ID shows as PCI\VEN_8086&DEV_2A44&CCSUBSYS_00011179
A quick Google appears to show that this is some sort of Intel Management Device
Any anyone throw somemore light on this?

Here's the offical reply from Toshiba -
{quote:title=Toshiba wrote:}We are sorry to hear you have had trouble locating the driver software you require. Unfortunately the driver software you need is still undergoing the research/approval service with which we approve all of our driver software.
We can only advise at this time that the software you require is being processed and will be added to the driver download section of our website in due course.{quote}

Hardware Malfunction NI PCI 8252 in Windows 7 x64

Similar Messages

Maybe you are looking for