Jump to content



Photo

Intel graphics driver problem!


  • Please log in to reply
4 replies to this topic

#1 KENNY P

KENNY P

    Neowinian

  • Joined: 24-May 12

Posted 03 January 2014 - 15:28

I have a Dell XPS 8700 - 4th gen i7 running Windows 8.1 with Intel 4600 graphics

 

Ever since 8.1, my dual monitor support is gone.

 

In the device manager, on the Intel display adapter, I get "Windows has stopped this device because it has reported problems. (Code 43)"

 

I can revert to previous driver (an old one) and it will work, but crash on things randomly (full screen videos, etc)

 

Any ideas?




#2 Jason S.

Jason S.

    Neowinian Senior

  • Tech Issues Solved: 5
  • Joined: 01-September 03
  • Location: Cleveland, Ohio

Posted 03 January 2014 - 15:36

are you downloading the latest driver directly from Intel's site?



#3 +Brando212

Brando212

    Neowinian Senior

  • Tech Issues Solved: 13
  • Joined: 15-April 10
  • Location: Omaha, NE
  • OS: Windows 8.1
  • Phone: Sony Xperia ZL, Nokia Lumia 925

Posted 03 January 2014 - 15:40

make sure you're using the latest official intel driver & not the dell provided one

 

latest version looks like it should be 15.33.8.64.3345 (could also be read by the computer as 10.18.10.3345) from their download center https://downloadcent...100&FamilyId=39



#4 OP KENNY P

KENNY P

    Neowinian

  • Joined: 24-May 12

Posted 03 January 2014 - 20:00

Sorry I didn't include

 

Am running latest INTEL driver from site 10.18.10.3345

 

Now getting this under device status:

This device is not working properly because Windows cannot load the drivers required for this device. (Code 31)

{Operation Failed}
The requested operation was unsuccessful.
 

 

 (i've reinstalled drivers several times too)



#5 +snaphat (Myles Landwehr)

snaphat (Myles Landwehr)

    Electrical & Computer Engineer

  • Tech Issues Solved: 29
  • Joined: 23-August 05
  • OS: Win/Lin/Bsd/Osx
  • Phone: dumb phone

Posted 04 January 2014 - 02:29

Looks like a known issue: https://communities..../message/209370; the current workaround appears to be installing older revisions of the driver.