Windows 7 x64 refuses to start with MX414 connected(BSOD 7E)

fpompert · Post by **fpompert** » Tue Jun 16, 2009 1:12 pm

Hi Guys!

I'm having difficulties making my (new) MX414 work on the Windows 7 x64 machine I have.

I've installed the latest 2.07 FTDI drivers after connecting the MX414 while inside Windows, and created some nice LCDC screens for it , for now it works flawlessly

However after a reboot, Windows 7 crashes with a BSOD - 7E BugCheck when the MX414 is attached. If I remove the display until after the windows splash screen is passed, and then connect it, it works perfectly

It seems that the FTDI drivers do not yet support Windows 7, and I've read on a competitor's forum that Vista SP2 may be affected as well, there too have I read messages of users that cannot reboot when the FTDI device is attached.

I've tried older driver versions to no avail, and I've upgraded my Windows 7 from RC1 build 7100 to 7201, but that didn't help either...

I also have an old worn out MX620 PLED screen which I replaced with the MX414, and connecting the MX620 results in the same BSOD at boot time.

Do other people have the same problem booting their system with Vista SP2 and/or Windows 7 with their display connected?

Specs:

Core 2 Quad Q6600@3200MHz
Gigabyte EP45-UD3P Intel P45
8GB PC6400 DDR2
Geforce 8800GTX
4xSamsung SLC SSD Raid array
600W PSU

Post by **Ray** » Tue Jun 16, 2009 2:16 pm

Do you happen to have a minidump of such a bsod? They usually hide in c:\windows\minidumps and are around 64kb in size with the date in the filename, if you happen to find a few you can zip two or three up and attach 'm to a post?

fpompert · Post by **fpompert** » Tue Jun 16, 2009 2:24 pm

Ray, I've attached them to this post, hopefully they're of any use.

Post by **Ray** » Tue Jun 16, 2009 3:07 pm

Since ms only supplies debugging symbols for public builds (7201 being not one of them) they are not as usefull as i hoped but still enough to pinpoint the driver causing the bsod.

061609-14742-01.dmp iastor.sys
061609-15178-01.dmp ftdibus.sys
061609-15834-01.dmp ftdibus.sys
061609-15943-01.dmp ftdibus.sys

I noticed the drivers included in the 207 package are not the newest available from ftdi directly, so I prepared a new driver package with ftdi 2.04.16 (2.4.06 previosly) drivers.

Please give them a whirl and let me know if that improves things.

Greetings,
Ray

fpompert · Post by **fpompert** » Tue Jun 16, 2009 3:37 pm

I've tried them but unfortunately no effect.

What notices me is that ftdibus.sys still reports version 2.04.06? Driver version for the MX4 itself reports 2.4.16.0

I've attached the dump files for the 7100 build of 7, as well as a dump file with the new driver (with 7201).

Post by **Ray** » Tue Jun 16, 2009 3:46 pm

Hmmz thats not right, i think i might have accidentally copied the wrong files to the wrong location when packaging that up. Lets do that again but proper this time.

These ones should be better.

fpompert · Post by **fpompert** » Wed Jun 17, 2009 12:06 am

Those seem to do the trick!

Have rebooted a dozen times and no more BSOD! Thanks