Start a Conversation

Unsolved

This post is more than 5 years old

13602

May 25th, 2010 14:00

issue with the E6510 cab drivers...

trying to load e6510's witht he drivers here on MDT2010. is anyone else seeing this blue screen error:

0x10D The Windows Driver Framework has detected that a violation has occured.

1 Message

May 26th, 2010 07:00

I had this same issue. I believe I had a conflict with another driver because I combined all windows 7 drivers into one folder. So I created a new folder with just the 6510 drivers in them and made a new
selection profile just for the drivers of the 6510 and then made a new task sequence that just injected those drivers with windows 7. updated deployment then I installed the image and it worked no more BSOD. Hope that helps. But for some reason I had missing driver for the fall sensor so I had to add that separately.

9 Posts

May 26th, 2010 08:00

this may have been a hardware issue. we have another 6510 here that installed just fine. Dell support is capturing the original system. We do have out drivers segregated by system type already but i'll keep your other steps/suggestions for reference. thanks...

1 Message

November 3rd, 2010 16:00

I had this issue as well. By accident I found that if I have a dell mouse connected during the install this happens. Disconnecting the mouse and then installing works. I can connect the mouse after the install just fine. I do have a common driver library for all our computers so this could be a driver issue.

3 Posts

March 14th, 2011 11:00

We are having issues with the E6510 and WDS / MDT2010, as well. After adding the drivers, we can get into the initial boot selection, but the imaging is just super slow and eventually does not complete.

1.1K Posts

March 14th, 2011 22:00

If you are deploying Windows 7 there is a recent update to the Win7 E6510 driver cab (A05 is current). Is that the version you are using?

5 Posts

March 16th, 2011 15:00

The problem I had was with the USB key. Adding all drivers to the USBKey caused the blue screen. I changed my selection profile so it only used the WinPE key, E6510 drivers, and desktops.

As far as drivers every system I have has it's own drivers. It takes more time but makes it easier to update and find issues. I believe the earlier drivers from the M4400 or M6400 was the culprit for why I was getting the error. The PE enviroment doesn't need that many drivers.

By the way...the Intel video driver is out of date for all HD series. I had to download the Intel driver from the Intel site and then blend them into the Dell CAB files. I have only done it on the E6410 so far. It fixed the brightness in the Intel properties from going to full brightness after clicking on a UAC pop up that dimmed the screen. In order to do this you need to extract the CAB file...delete the whole video directory under the Intel RXXXXXX version in the Dell CAB listing and then copy the entire Intel version over. Delete all drivers from MDT in the OOB section for the E6410 and reimport them back.
No Events found!

Top