Agilent 532xx driver bug Counter?

Similar Questions

• Agilent 4156 bug or Labview driver bug?

  Hello

  I use Labview 8.5 for Agilent 4156C for certain measures customerized control. Now, I have a problem. I need to configure at least 3 SMEs. I chose SMU 1-3.  I'm changing the sample program that come with the 4156C under labview driver installation. The problem is that when I use the Sub - VI Channe configure from 4156 Panel to change the configuration of SMU3 and SMU4, there is a message of error-1074000000. I choose simply SMU1 or SMU2 for the same operation, all right. What I did wrong, or there might be a few bugs? Thank you!

  BTW, when I was looking for drivers for this equipment, I found 3 possible pilots with the keyword 'Agilent Technologies 4156C' and 'HP 4156C '. Are there different between these 3 drivers?

  Evander

  
  

• HP Envy x 360 15-aq000nb QWERTY: azerty keyboard driver bug for <>------generating ctrl instead of mapping

  "Nine" HP Envy x 360 with Belgian azerty keyboard

  2 right of the space bar, marked as <>key positions-generates these values, but generates the code for the CTRL key instead.

  This may be a virus or other problem, because it is a new system "comes out of the box". I really suspect of a "Bug" here to test available for this particular model azerty

  The keyboard driver is standard supplied with the operating system of microsoft, called "Belgian Azerty comma.

  The operating system is on the last patch level

  HP drivers are on the last patch level

  I guess it must be declared as 'a problem' and not an 'incident '.

  See you soon,.

  Stefan

  An update on this:

  The keyboard permanently sends the keyvalue 'CTRL RIGHT'. I wouldn't not because in the majority of keyboard layouts, the button to the right of the "ALT GR" is indeed the RIGHT CTRL. But not on this Belgian AZERTY keyboard. He the key on this post is marked > <------(you access the backslash pressing alt gr with the key, you access the > organizing the passage)

  So I guess it's a problem of HP and a defect of product in a lot of these PC.

  I used after derivation of the to solve for me (but I guess there is still a bug for HP):

  Using the free software SharpKeys. http://SharpKeys.codeplex.com/
  I remapped in the registry (E0_1D) right CTRL key 0 x 0056 (00_56)

  This solved it for me.

  Hope that HP takes knowledge to check if there is a production fault in this batch of HP envy

  See you soon,.

  Stefan

• Agilent E3645A driver as a power source for Labview 6.1

  NOR expensive.

  I have a Labview 6.1 and I want to order a supply of Agilent E3645A, but I can't find any driver that works with this version. You can give them?

  Kind regards.

  Oldest message than you can find in the thread Downconvert . Be prepared to wait a while as 6.1 is very old.

  p.s. next time, post to the control instrument Board because as he says, this forum is for the DMM OR.

• HP Pavilion g7-2251dx: Windows 10 IDT high definition Audio Driver Bug report.

  OK after upgrading Windows 8.1 for Windows 10 Home (The Free Upgrade) I have noise problems.

  IDT Sound Drivers (IDT High Definition Audio Codec):

  Speakers integrated into the laptop: they its OK but not as they did in point 8.1 of Windows.

  I've tested on the following:

  Music (sounded OK)
  Played a Youtube video (sounded OK)
  Played a video that I recorded on my PC (its OK)
  Played a show or a movie on Netflix (sounded OK)

  The portable built-in Microphone seems to be working well.
  
  Turtle Beach headset Z11: they sound like basically no Bass Mono instead of stereo there and The Sound is low even though the volume to 100.

  I've tested on the following:
  Play music (sounded bad)
  Played a Youtube video (sounded bad)
  Played a video that I saved on my PC (sounded bad)
  Played a show or a movie on Netflix (bad sound)
  
  In Windows 8.1 speakers embedded in the laptop and the Turtle Beach headset Z11 resembled stereo and strong (perfect).
  
  The helmet Microphone seems to be working very well.
  
  I plugged my headphones Z11 of Turtle Beach to HP from my sister who still has windows 8.1 and my Turtle Beach Z11 helmet sounded very good.

  I plugged my Z11 of Turtle Beach headset in my other sisters that has Windows 10 HP (she has upgraded to Windows 7) and my Z11 of Turtle Beach headset resembled Mono Stereo Instead of.

  It is also plugged into his ear and they looked like Mono Stereo Instead of.
  
  I tested another helmet my Turtle Beach Headset (This Headset plugs into the USB Port) P11 The Sound is perfect it sounds like stereo and not like Mono.

  However when I spoke into the microphone, I could hear my voice coming through the headset speakers (mainly the hearing talk me)
  -------------------------------------------------------------------------------------------
  Microsoft high definition Audio drivers:

  These major works of Drivers so if you just want to use these drivers:

  Uninstall driver IDT
  Restart your computer
  Next adjustment of Volume and other settings
  Right-click of your Volume icon in hand right corner
  or
  Right-click on start (the white Windows icon located to the left of the bottom of your screen)
  Click on Control Panel
  Click on hardware and sound
  Click sound
  Right click on the second peripheral speakers (or according to your to are called)
  Click on properties
  Now just go through each tab and change what you want to change.

  I only click on the Advanced tab, and then change the default Format for 16-bit platforms, 48000 Hz (DVD quality)
  Because that was what the default Format on Windows 8.1
  I also click on record and change the setting of the microphone 2 listed.

  Speakers integrated into the laptop: they its OK but not as they did in Windows 8.1

  I've tested on the following:
  Music (sounded OK)
  Played a Youtube video (sounded OK)
  Played a video that I recorded on my PC (its OK)
  Played a show or a movie on Netflix (sounded OK)

  The portable built-in Microphone seems to be working well.

  Z11 headphones Turtle Beach:

  I've tested on the following:
  Play music (sounded great)
  Played a Youtube video (sounded great)
  Played a video that I saved on my PC (sounded great)
  Played a show or a movie on Netflix (sounded great)

  The helmet Microphone seems to be working very well.

  Always noticed his Mono with your helmet?

  Try this:
  Plug in your headphones
  Right-click of your Volume icon in hand right corner
  or
  Right-click on start (the white Windows icon located to the left of the bottom of your screen)
  Click on Control Panel
  Click on hardware and sound
  Click sound
  Right click on the second peripheral speakers (or according to your to are called)
  Click on disable
  Right click on the second peripheral speakers (or according to your to are called)
  Click on Enable
  Now your sound is heard as stereo instead of Mono.

  --------------------------------------------------------------------------------------------
  I tried the sound of setting here is what I tried:

  I uninstalled IDT audio driver I went into Control Panel and uninstalled the IDT Audio driver.

  Then I restarted my computer and I reinstalled the drivers of HP's Windows 8.1.

  After restarting my computer again, I checked to see if everything was back to normal, but it is not yet sounded even.
  
  When I right click on the "speaker" icon and then choose playback devices here is what was posted:
  The top unit is called:
  Its digital display (AMD high definition Audio Device) not connected
  OK, this is Normal.
  
  The central device is called:
  Speaker / device by default HP (IDT High Definition Audio Codec)
  OK, this device is also Normal.
  
  The background feature is called:
  Communication by default communication device Headphones (IDT High Definition Audio Codec)
  OK in Windows 8.1 this device has been disabled by default but in Windows 10 it is activated and listed as default communications device.

  So I thought that if I just disabled it my Turtle Beach P11 helmet would return to normal, but it didn't she sounded still, I even restarted my computer.
  
  OK, so I tried to set the Communications headset as device by default but when I right click and click on set as default device it wouldn't let me.
  
  I then disabled speaker / HP and tried to set it as default device it wouldn't let me.
  
  When I disabled speaker / HP Groove Music said he could not detect an Audio device in order to activate the speaker / HP and people with disabilities
  Helmet of communication.
  ---------------------------------------------------------------------------------------
  My computer is a HP Pavilion 2251dx g7

  Audio ID:

  Computer built-in Laptop speakers:
  HDAUDIO\FUNC_01 & VEN_111D & DEV_76D9 & SUBSYS_103C184B & REV_1001
  HDAUDIO\FUNC_01 & VEN_111D & DEV_76D9 & SUBSYS_103C184B
  
  Turtle Beach z11 headphone 3.5 mm Jack:
  Sorry no Audio for this one hardware ID that he doesn't use the same above, I think.
  
  P11 headphones from Turtle Beach USB:
  USB\VID_10F5 & PID_0231 & REV_0100 & MI_00
  USB\VID_10F5 & PID_0231 & MI_00
  
  If you need more info let me know.

  Thanks for reading all of this I hope that soon, there is a Solution.
  ------------------------------------------------------------------------------------------
  A temporary Solution:

  After you have solved the problem by reading through countless messages try every difficulty that none of them I went into Control Panel and he took a glance at the the Dolby Advanced Audio Control Panel now I never tested with this before so far but I was able to fix the Audio questions here is exactly what I did :

  When you use your built-in Laptop speakers or possibly other speakers:
  Right-click on start (the white Windows icon located to the left of the bottom of your screen)
  Click on Control Panel
  Click on hardware and sound
  Click Dolby Advanced Audio
  Click on listening experience
  Check Dolby Advanced Audio

  I've tested on the following:
  Play music (sounded great)
  Played a Youtube video (sounded great)
  Played a video that I saved on my PC (sounded great)
  Played a show or a movie on Netflix (sounded great)

  When you use your headset from Turtle Beach Z11 or possibly other headphones:
  Right-click on start (the white Windows icon located to the left of the bottom of your screen)
  Click on Control Panel
  Click on hardware and sound
  Click Dolby Advanced Audio
  Click on listening experience
  Uncheck Dolby Advanced Audio now, your headset should ring loud instead of sound like Mono and stereo and crappy.

  I've tested on the following:
  Play music (sounded great)
  Played a Youtube video (sounded great)
  Played a video that I saved on my PC (sounded great)
  Played a show or a movie on Netflix (sounded great)

  You need to keep the box checked when you use your built-in Laptop speakers, otherwise they will sound like Mono and crappy.
  
  So basically when you plug in your headphones uncheck the box.
  
  So basically when you disconnect your headset check box.
  
  If you have messed with the implementation in and want to return to the default value:
  Click Advanced settings
  Click on Reset

  IDT Sound Drivers (IDT High Definition Audio Codec):
  Always noticed his Mono with your helmet?

  Try this:
  Plug in your headphones
  Right-click of your Volume icon in hand right corner
  or
  Right-click on start (the white Windows icon located to the left of the bottom of your screen)
  Click on Control Panel
  Click on hardware and sound
  Click sound
  Right click on the speakers of intermediate device / HP (or according to the your are called)
  Click on disable
  Right click on the speakers of intermediate device / HP (or according to the your are called)
  Click on Enable
  Now your sound is heard as stereo instead of Mono.

  Microsoft high definition Audio drivers:
  Always noticed his Mono with your helmet?

  Try this:
  Plug in your headphones
  Right-click of your Volume icon in hand right corner
  or
  Right-click on start (the white Windows icon located to the left of the bottom of your screen)
  Click on Control Panel
  Click on hardware and sound
  Click sound
  Right click on the second peripheral speakers (or according to your to are called)
  Click on disable
  Right click on the second peripheral speakers (or according to your to are called)
  Click on Enable
  Now your sound is heard as stereo instead of Mono
  ----------------------------------------------------------------------------------------
  I'm testing all my games to ensure that the work of games and the sound works.

  I use my temporary Solution to test all the games.

  After resetting my PC the sound worked fine with my temporary Solution.

  Castlevania: Lord of Shadow Ultimate Edition:

  The sound was great on my Turtle Beach Z11 helmet.

  Castlevania: Lord of Shadow 2:

  The sound was great on my Turtle Beach Z11 helmet.

  Darksiders Pack franchise:
  Darksiders II:

  The sound was great on my Turtle Beach Z11 helmet.

  Darksiders:

  The sound was great on my Turtle Beach Z11 helmet.

  Deus Ex Human Revolution - Director s Cut:

  Download still can not test it yet.

  The Elder Scrolls IV: Oblivion Game of the Year Edition:

  The sound was great on my Turtle Beach Z11 helmet.

  The Elder Scrolls V: Skyrim legendary Edition:

  The sound was great, but even with my temporary fix the sound on my headset Turtle Beach Z11 was low I actually had to put the Volume slider almost up just to hear everything correctly.

  Fallout New Vegas Ultimate Edition:

  The sound was great on my Turtle Beach Z11 helmet.

  Grand Theft Auto IV: Complete Edition:

  The sound was great on my Turtle Beach Z11 helmet.

  Metal Gear Rising statement:

  The sound was great on my Turtle Beach Z11 helmet.

  Soul Murder Suspect:

  The sound was great on my Turtle Beach Z11 helmet.

  Quantum Conundrum:

  The sound was great on my Turtle Beach Z11 helmet.

  Saints Row Franchise ultimate Pack:
  Saints Row 2: download still can not test it yet.

  Saints Row third: download still can not test it yet.

  Saints Row IV:

  The sound was great on my Turtle Beach Z11 helmet.

  Sleeping Dogs final edition:

  Download still can not test it yet

  Thief: Master thief Edition:

  The sound was great on my Turtle Beach Z11 helmet.
  ------------------------------------------------------------------------------------------
  I could not Downgrade from Windows 8.1 because it said that files deleted even if windows.old was still there, so I just did a Reset instead.

  Thanks to my temporary fix Audio problems are gone, but I hope that HP releases new drivers, so I can't use my temporary Solution.

  Also I hope HP or Microsoft releases new drivers for the Synaptics TouchPad so that people can save their settings.

  This has been corrected by James Yerkes on Microsoft Community:

  Open regedit.exe

  Navigate to:
  HKEY_LOCAL_MACHINE\SOFTWARE\Synaptics\SynTP\Install

  Note it's the LOCAL MACHINE, not the CURRENT USER.

  Search for a key in the installation folder called DeleteUserSettingsOnUpgrade

  Double click and change the value to 0

  Now go back in the Panel of Synaptics, put all how you like and restart.

  in any case if someone has problems with Windows 10 Post here and I'll see if I can help you but I recommend resetting your PC in recovery Menu so that most of the problems will be solved then I would install all my drivers from the manufacturer.

  I am currently using window 8.1 1 driver from AMD and HP drivers.
  -------------------------------------------------------------------------------------------------
  This may not work for everyone, but if you have the same laptop and headphones I don't then it should work.

  I posted this as well on Microsoft Community:

  http://answers.Microsoft.com/en-us/Windows/Forum/windows_10-other_settings/Windows-10-IDT-high-defin...

  ---------------------------------------------------------------------------------------------------

  Hey everyone here is an update.

  Since microsoft rolled out updates for windows 10 mainly the updated driver to update I had is no longer using the old methods such as the use of the old HP drivers to this windows 10 drivers working for my laptop then everything works fine.

  I always use drivers from AMD for My APU (CPU and graphics card), but everything else is Microsoft I using Microsoft drivers for the month now and have had no problem.

  I hope that everyone knows success with these drivers.

• SanDisk usb flash driver BUG

  can someone help me with this? #VOLUME #_ WPDBUSENUMROOT\UMB\2 & 37C186B & 1 & STORAGE? _USBSTOR #DISK & VEN_SANDISK & PROD_U3_TITANIUM & REV_8. 01 WPDBUSENUMROOT\UMB\2 #087843079E9367F7 & 0 # & 37C186B & 1 & STORAGE #VOLUME # _____? _USBSTOR #DISK & VEN_SANDISK & PROD_U3_TITANIUM & REV_8. 01 WPDBUSENUMROOT\UMB\2 #087843079E9367F7 & 0 # & 37C186B & 1 & STORAGE #VOLUME # _____? _USBSTOR #DISK & VEN_SANDISK & PROD_U3_TITANIUM & REV_8. 01 #087843079E9367F7 & 0 #.

  http://U3.SanDisk.com/

• BSOD: For the Bug Check Code: 0000009F is probably caused by: nt Driver

  I recently met a problem with BSOD when I was afk or configure my computer to Hibernate, whereby Soluto has picked up the information on:

  Bug check code: 0000009F, probably caused by: nt DRIVER_POWER_STATE_FAILURE driver bug check has a value of 0x0000009F. This bug check indicates that the driver is in an inconsistent or invalid power state.
  How should I proceed? I got the message about 3 times prior.

  RS

  It was linked to rimvndis6_AMD64.sys RIM Tunnel driver of Research In Motion Limited.  I would like to re - install the latest driver available.

  If you continue to plant I would remove Avast & replace it with MSE

  Avast can be a cause of BSOD.

  Please delete and replace by Microsoft Security Essentials at LEAST FOR TESTER

  http://files.avast.com/files/eng/aswclear5.exe
  http://www.Microsoft.com/security_essentials/

• Streaming (record) data of Agilent 6674 interface GPIB-USB powered

  Hello

  I would like to save the output in more than 200 HZ to my power supply CC 6674 A Agilent with LabVIEW 8.2. Agilent 82357 A GPIB-USB interface is used to connect the power to the computer. And I used the instrument for Agilent 66XX driver I downloaded from OR.

  For reading continuous data, I put the read.vi in a while loop and data saved by writing in the file lvm. (just for the starter, not a good sense, though) Please see the attachment.

  The problem I have is that I can only save data in ~ 10 HZ then that what I need is at least 200 HZ.

  It's my first time to the instrument control and I just had a little experience in the acquisition of data before. I had some confusion as below: no I have gained a point each time the while loop is executed? If so, I guess that the time for each loop (and therefore my data rate) depends on my operating system and the computer I have.

  How many points will be acquired whenever the read.vi is run? That depends on the set 'count bytes' in vi or a single point anything? Are there other ways to get the data more efficiently? (want to write your own driver etc...) Any help would be much appreciated.

  See you soon,.

  Bohan

  The rate at which you can run the VI is dependent on the instrument/GPIB bus and use of Scripture on a Measurment file. Yes, you get a voltage reading and a current reading with each iteration and the number of bytes read is so that you can get a complete reading.

  I suggest you delete the entry in the file of the measurement of the loop to see how long takes of the instrument. That would be your maximum rate. If it's fast enough, use a different method to save the data. Architecture of producer/consumer if you pass the data to another loop via a queue would be a way.

• OF DRIVER POWER STATE FAILURE

  Hello

  Seen a lot of posts on this but nothing I found to help me.  I get an error in the failure State on Windows 7 64 driver when the computer goes into mode "Eve".  Instead of waking up the computer is off and when I restart I get an error saying that windows is not stopped correctly and he asks me if I want to start in safe mode.

  I need to find the device / driver that is the cause.  I downloaded my minidump files in the following location:

  https://www.dropbox.com/s/w03xb8svk335pg7/minidump.zip?DL=0

  Hoping someone can help on this issue and I would like to know if there is something usable in it.

  Thanks in advance!

  PS:

  I also had a utility called whocrashed, he read the dump file and told me the following...

  Thursday, April 23, 2015 3:03:54 AM GMT crashed your computer
  crash dump file: C:\Windows\Minidump\MEMORY. DMP
  Uptime: 1 day, 11:40:39
  This was probably caused by the following module: ntkrnlmp.exe (nt! KeBugCheckEx + 0x0)
  Bugcheck code: 0x9F (0x3, 0xFFFFFA8009AC6A10, 0xFFFFF80005A5E518, 0xFFFFFA800CE613B0)
  Error: DRIVER_POWER_STATE_FAILURE
  Bug control description: this bug check indicates that the driver is in an inconsistent or invalid power state.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
  The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

  Thursday, April 23, 2015 3:03:54 AM GMT crashed your computer
  crash dump file: C:\Windows\Minidump\042315-19796-01.dmp
  Uptime: 1 day, 11:40:39
  This was probably caused by the following module: ntkrnlmp.exe (nt! KeBugCheckEx + 0x0)
  Bugcheck code: 0x9F (0x3, 0xFFFFFA8009AC6A10, 0xFFFFF80005A5E518, 0xFFFFFA800CE613B0)
  Error: DRIVER_POWER_STATE_FAILURE
  Bug control description: this bug check indicates that the driver is in an inconsistent or invalid power state.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
  The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

  CM

  This phenomenon was linked to Rt64win7.sys 8101E/8168/8169 NDIS 6.2 64-bit driver Realtek Corporation.  I remove the current driver and install the latest driver available.

• Power outage of State driver

  When I close the lid of my laptop and re - open, I have a blue screen. Here is the stupid analysis accident I get:

  crash dump file: C:\Windows\Minidump\112613-10483-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x75BC0)
  Bugcheck code: 0x9F (0x3, 0xFFFFFA8005899A10, 0xFFFFF80000B9C3D8, 0xFFFFFA800DC4C010)
  Error: DRIVER_POWER_STATE_FAILURE
  file path: C:\Windows\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &
  Bug control description: this bug check indicates that the driver is in an inconsistent or invalid power state.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
  The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

  Any help I could get would be greatly appreciated.

  TS

  These were related to the device driver wireless Extensible athrx.sys from Atheros Communications, Inc., but my gut says it's your Kaspersky.

  I would like to re - install your driver Atheros and if you continue to plant I would remove Kaspersky and replace it with MSE

  Kaspersky is a common cause of BSOD.

  
  http://support.Kaspersky.com/downloads/utils/kavremover10.zip
  http://www.Microsoft.com/security_essentials/

• My computer keeps restarting with a driver failure

  I have a laptop Acer Aspire that I have had for about 9 months. I've noticed a few problems over the last 4 months with this computer. It keeps restarting now. Sometimes after it restarts once it starts up perfectly fine but other times he keeps just restarting without end I tried to do a clean boot, cleaning the registry, the chkdsk, the sfc and update the display driver (since sometimes random color banding appears on the screen instead of a reboot or the Office would just go crooked with lines paralyzed at startup programs open to the top or icons). But im still getting the same problem and recently I got a blue screen on a driver failure.

  These are the details that I received from whocrashed:
  crash dump file: C:\Windows\Minidump\101713-49764-01.dmp
  Uptime: 03:29:14
  This was probably caused by the following module: ntkrnlmp.exe (nt! KeBugCheckEx + 0x0)
  Bugcheck code: 0x9F (0x3, 0xFFFFFA8007855A10, 0xFFFFF800064223D8, 0xFFFFFA8006974880)
  Error: DRIVER_POWER_STATE_FAILURE
  Bug control description: this bug check indicates that the driver is in an inconsistent or invalid power state.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
  The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.
  Any help will be appreciated

  S

  There was only a single file DMP here

  Your other machine crash is connected to AODDriver2.sys AMD OverDrive Service pilot from Advanced Micro Devices.

  I would like to re - install the most recent driver available (even if the same date) and if you're overclocking STOP

  In addition I would like to remove and replace Kaspersky with MSE

  Kaspersky is a common cause of BSOD.

  
  

  I remove and replace it with Microsoft Security Essentials at LEAST FOR TESTER.

  http://support.Kaspersky.com/downloads/utils/kavremover10.zip
  http://www.Microsoft.com/security_essentials/

• Out of State driver BSOD

  So last week I lived an accident by Acer Aspire V3 - 551 - X 489 laptop computer was hibernating. A few days ago I had another accident of BSOD while my pc was a hibernation. The error was DRIVER_POWER_STATE_FAILURE.

  After reviewing the dump mini reports with WhoCrashed I found the culprit: ntoskrnl.exe

  --------------------------------------------------------------------------------------------------------------

  We Dim, 2014-03-09 10:59:31 PM GMT crashed your computer
  crash dump file: C:\Windows\Minidump\030914-68047-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x5A440)
  Bugcheck code: 0x9F (0x3, 0xFFFFFA8008BA2060, 0xFFFFF80208868770, 0xFFFFFA80079AFA80)
  Error: DRIVER_POWER_STATE_FAILURE
  file path: C:\Windows\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &
  Bug control description: this bug check indicates that the driver is in an inconsistent or invalid power state.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
  The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

  ------------------------------------------------------------------------------------------------------------------

  I tried the sfc/scannow command in the command prompt. I don't know if it worked because it shows that windows finds corrupted files, but have been unable to fix some the audit of 54%.

  What should I do now? Any suggestions on how I should fix this problem.

  Kevin

  This phenomenon was related to a driver of Windows (R) Win 7 btfilter.sys DDK 2 years of Atheros.  I'd install the most recent driver available.

  Let us know the results of DISM.

• Strange bug with brush in Photoshop CC 2014 (EDIT - added example photo)

  Hello world

  Longtime Photoshop user, Photoshop CC 2014 running on a Mac Pro (mid 2010, 2x2.66 GHz 6 - Core Intel Xeon with 64 GB of RAM and a graphics card than NVIDIA Quadro K5000) running OS X El Capitan v10.11.3. I do all of my work out of SSDS (and use SSDS as my "scratch disks").

  I am a CC Subscriber but have not yet updated to 2015 for CC in Photoshop.

  I've been running in a strange bug while using the Brush tool. I'll do my best to describe it-when I paint on an existing layer, I get a strange series of pixelated lines and squares that I paint - and when I use the brush to 'cover' the squares, they disappear. When I resize, these squares disappear, and when I went to use Screen Grab (so I could take a snapshot of this issue), they also disappear - so I can't take a screenshot of the issue. These strange square and the lines do not appear to be part of my real file, but obviously, they make it impossible to work using the painting tools.

  * EDIT * I managed to capture an example of what I speak, please see the picture below:

  

  These weird lines and squares are often the same color as my background color, or the same colors (but offset) of the layer I'm working on that.

  I recently installed an update of El Capitan (v10.11.3) and this problem appeared after that, so I wonder if this is Mac related, but I would appreciate any advice on how to solve this problem.

  Thanks a lot for reading and look forward to answering questions!

  This is a driver bug in the web for MacOS of Nvidia drivers.

  Contact NVidia to see if they still have a driver with the available bug fixed.

• LabVIEW 7.1 IVI - C Wrappers and VISA property node do not work together?

  Hello world

  I want to use the property node VISA with LabVIEW 7.1 Wrapper of two companies different well known instrument, Rodhe-Schwarz and Agilent Technologies.
  The two companies releasead their IVI - C for NI LabVIEW 7.1 drivers version NI Instrument Driver network and they are ready to be installed and used.

  I found a bug manifested that the LabVIEW 7.1 version that the bug is not present in whhen versions 8.0 LabVIEW or LabVIEW 8.6 than these IVI LabVIEW of LabVIEW 7.1 wrappers are used.

  Everyone could exeperience this bug if they have LabVIEW 7.1 installed and are trying to use the version of LabVIEW 7.1 of these wrappers which are published in NI Instrument Driver Network under the links below.

  Agilent ag81150ni IVI Driver for LabVIEW 7.1 install from here. Used in simulation that by definition simulate = 1

  http://sine.NI.com/apps/UTF8/niid_web_display.download_page?p_id_guid=55798957B1A633BDE0440003BA7CCD...

  Rodhe Schwarz rsngpt IVI Driver for LabVIEW 7.1 install from here. Used in simulation that by definition simulate = 1

  http://sine.NI.com/apps/UTF8/niid_web_display.download_page?p_id_guid=E3B19B3E91D6659CE034080020E748...

  After the installation of these two complete drivers close LabVIEW 7.1, if it was open, and then restart LabVIEW 7.1. You can see two new ready to be used as LabVIEW 7.1 IVI drivers in the LabVIEW Instrument Driver pallet wrappers in a LabVIEW 7.1 VI test.

  Open a new white VI and of the use of the Instrument Driver Palette two VI known, initialized with Options.vi and Close.vi adding them on the block diagram, connect all THMs. Accept all default settings except simulate parameter which must be defined as = 1 simulation.

  The two VI run OK mode of simulation without errors.

  Now select a property in the advanced Panel of VISA node and press this node between 'Initialize them with Options' and 'Close' VI and make all necessary in-out connections and error.

  Run these two simple screws of simulation

  1. When I run pilot Rodhe Schwarz IVI the property node going OK until the end. No error
  2. Whne I run Agilent IVI driver the property node is always out of the error Code 7.

  Question is why they behave different with regard to the property of node when it is used with the LabVIEW 7.1 envelopes? BTW, the failing VI of wrappers Agilent LabVIEW 7.1 works very well in labVIEW 8.0 and 8.6. That means that this problem is limited only the version of LabVIEW 7.1.

  I posted the same question on the set of LabVIEW and nobody chose their interest in there so I decided to post here. As this question is also linked to IVI, VISA drivers, it is possible the person of this group to get a clue about this annoying behavior.

  I've attached screenshots of the PNG files that show the difference of different behavior of VISA property between these two drivers node.

  ScreenTestShots.zip (152 kb)

  Thank you

  Sorin

  
  

• Need help multiple BSOD

  Hey all,.

  I have several BSOD errors.  I reinstalled win 7 after having a BSOD error different loading windows.  I did the format of the hard drive, so it must be cool.

  I have updated all the drivers, including the BIOS.  Any help is appreciated because I'm banging my head on the wall here :)

  OneDrive .dmp and error logs

  Crash dump directory: C:\Windows\Minidump

  Dumps are enabled on your computer.

  Wednesday, September 17, 2014 21:03:57 this computer crashed
  crash dump file: C:\Windows\Minidump\091714-35646-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x75BC0)
  Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFA0000, 0xFFFFF80002CBA22B, 0x0)
  Error: "KMODE_EXCEPTION_NOT_HANDLED"
  file path: C:\Windows\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &
  Bug control description: This indicates that a kernel-mode program generated an exception which did not catch the error handler.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
  The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

  Wednesday, September 17, 2014 21:03:57 this computer crashed
  crash dump file: C:\Windows\memory.dmp
  This was probably caused by the following module: ntkrnlmp.exe (nt! KeBugCheckEx + 0x0)
  Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFA0000, 0xFFFFF80002CBA22B, 0x0)
  Error: "KMODE_EXCEPTION_NOT_HANDLED"
  Bug control description: This indicates that a kernel-mode program generated an exception which did not catch the error handler.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
  The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

  Wednesday, September 17, 2014 7:58:58 PM GMT crashed your computer
  crash dump file: C:\Windows\Minidump\091714-38984-02.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x75BC0)
  Verification of error code: 0 x 18 (0xFFFFFA800A2BA2B0, 0 x 0, 4 x 0, 0xFFFFFFFFFFFFFFFF)
  Error: REFERENCE_BY_POINTER
  file path: C:\Windows\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &
  Bug control description: This indicates that the reference of an object count is illegal for the current state of the object.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware problem. This could be a case of corruption of memory. The corruption of memory more often happens because of software errors in the defective drivers buggy, not because of RAM modules.
  The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

  Wednesday, September 17, 2014 17:26:14 CEST your computer crashed
  crash dump file: C:\Windows\Minidump\091714-58141-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x75BC0)
  Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFA8000, 0xFFFFFA8008A24BB0, 0x0)
  Error: "KMODE_EXCEPTION_NOT_HANDLED"
  file path: C:\Windows\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &
  Bug control description: This indicates that a kernel-mode program generated an exception which did not catch the error handler.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
  The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

  Wednesday, September 17, 2014 17:20:10 CEST your computer crashed
  crash dump file: C:\Windows\Minidump\091714-39780-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x75BC0)
  Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFA0000, 0xFFFFF80002C5622B, 0x0)
  Error: "KMODE_EXCEPTION_NOT_HANDLED"
  file path: C:\Windows\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &
  Bug control description: This indicates that a kernel-mode program generated an exception which did not catch the error handler.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
  The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

  Wednesday, September 17, 2014 17:16:05 CEST your computer crashed
  crash dump file: C:\Windows\Minidump\091714-38984-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x75BC0)
  Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFA8000, 0xFFFFFA80081DCBB0, 0x0)
  Error: "KMODE_EXCEPTION_NOT_HANDLED"
  file path: C:\Windows\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &
  Bug control description: This indicates that a kernel-mode program generated an exception which did not catch the error handler.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
  The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

  Wednesday, September 17, 2014 4:10:54 PM GMT crashed your computer
  crash dump file: C:\Windows\Minidump\091714-36114-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x75BC0)
  Verification of error code: 0 x 50 (0x0, 0xFFFFF80002D1236E, 0xFFFFF8A003BCB000, 0x0)
  Error: PAGE_FAULT_IN_NONPAGED_AREA
  file path: C:\Windows\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &
  Bug control description: This indicates that invalid system memory was referenced.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
  The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

  10:35:38 AM GMT on Wednesday, September 17, 2014 crashed your computer
  crash dump file: C:\Windows\Minidump\091714-42837-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x75BC0)
  Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFA8000, 0xFFFFFA80080FDBB0, 0x0)
  Error: "KMODE_EXCEPTION_NOT_HANDLED"
  file path: C:\Windows\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &
  Bug control description: This indicates that a kernel-mode program generated an exception which did not catch the error handler.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
  The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

  Not a problem, thanks.

  KMODE_EXCEPTION_NOT_HANDLED (1e)

  This indicates that a kernel-mode program generated an exception which did not catch the error handler.

  Bugcheck 1E, {ffffffffc0000005, fffff80002cba22b, 0, fffa0000}

  0: kd > fffff80002cba22b ln
  (fffff800'02cba1ec)   nt! RtlImageNtHeaderEx + 0x3f |  (fffff800'02 ca 9108) nt! MiDoReplacement

  The exception is produced in nt! RtlImageNtHeaderEx + 0x3f.

  ---------------------------

  1. AppleCharger.sys is listed and charged, which is the driver GIGABYTE on / off Charge. See here for more information - http://www.gigabyte.us/MicroSite/185/on-off-charge.htm

  Very annoying software, so please uninstall ASAP!

  2 remove and replace Norton with Microsoft Security Essentials for purposes of troubleshooting temporary, as it is most likely cause conflicts:

  Removal of Norton- https://support.Norton.com/SP/en/us/home/current/solutions/kb20080710133834EN_EndUserProfile_en_us;JSESSIONID=841A6D40BA6872C47697C6C6B19C8E11.4?entsrc=redirect_pubweb&PVID=f-home

  MSE - http://Windows.Microsoft.com/en-us/Windows/Security-Essentials-download 

  3 navigate to services.msc and disable the nVidia Streaming Service card and then restart the computer.

  Kind regards

  Patrick