Windows 10: Nikon Coolscan 4000ED Causes BSOD When Powered On

I have a rather serious problem with Windows 10 Pro that I did not have with Windows 7 Pro... when I power on my Nikon slide scanner, Windows abruptly halts and I lose all my work.


This happened the first time I hooked it up, even before I installed drivers and software for the scanner. Windows 10 apparently does not handle IEEE1394 hardware coming online without a fatal error.


Even after installing drivers and software to use the scanner, it still crashes Windows with a BSOD halt when powered on.


I don't remember Windows being this fragile, except back in 1992 or so with Windows for Workgroups.


What is being done to make Windows more robust when dealing with IEEE1394 devices connecting?

:)

 

Using Nikon Coolscan with Windows 10

Official Nikon support for that scanner ended with Windows Vista.

This isn't free, but consider:

Nikon CoolScan 4000 ED Driver and Software | VueScan

You can download a free trial to see whether it works for you. I'm not sure, but the Vuescan drivers may support other software as well.

 

Using Nikon Coolscan with Windows 10

I have managed to get my Nikon Coolscan LS-40 working on Windows 10 using the Windows 7 driver solution *chuckle. Did you ever reach a positive solution? If not I'll post the procedure.

 

Using Nikon Coolscan with Windows 10


This is a very long shot but I am hoping that someone might be able to help me out.

The scanner I am messing with really belongs to my brother who has lent it to me to try and scan my 10 carousels of old slides. (I am really just planning on picking out my favorite ones - not all 1,400 slides.) My brother warned me that I might have trouble with drivers. Ahem...

I've tried so many things to get this scanner working over the past few weeks that my head is spinning (though it may also be that I am just getting over the flu). But, first, here's where I stand now:

The device and firewire controller both appear to be working correctly according to device manager. (Can't figure out how to paste images here.)
IEEE 1394 host controllers > 1394 OHCI Compliant Host Controller (Legacy)
Imaging Devices > Nikon SUPER COOLSCAN 4000 ED

Alas, Nikon Scan 4.0 shows: "Nikon Scan was unable to find any active devices"

In past experiments, I've had very-limited success in getting both Nikon Scan 4 and Vuescan to see the scanner and even create scans of slides before ending back up with the above message.

In spite of many years of IT experience, I am not enough of a Windows hack to be able to do the same thing twice and get the same results (very frustrating). It seems that, even if I try to "uninstall" everything (drivers, software, etc), I don't think that Windows actually clears it all out.

I have been from one end of the Internet to the other finding and trying different "solutions". My attempts have included:

1. Trying to follow the instructions to the letter on: "Getting your Nikon Coolscan to work on W7 x64" (That trick got me the closest to getting the scanner to work - at least for a few minutes - with Nikon Scan.)
2. Various compatibility combinations for Nikon Scan.exe (Interestingly, Windows seems to remember those settings even after uninstalling and reinstalling Nikon Scan!)
3. VueScan gets the same message, though it has found and been able to drive the scanner for a short time. (Heck, I'd be willing to pay the Vuescan license if it worked reliably.)
4. I was going to set up a VirtualBox and run WinXP until I figured out that VirtualBox doesn't support guest connectivity to Firewire interfaces. Ahem...
5. I also found a place that suggested installing the "Legacy" driver for my Firewire controller. Hence, the "IEEE 1394 host controllers > 1394 HOCI Compliant Host Controller (Legacy)"

I've tried a lot of stuff that I just can't remember just now. It is particularly frustrating, though, that I can't seem to do the same thing twice.

Things I haven't tried yet include:

1. Finding, downloading, and installing Nikon Scan 3 software instead of Scan 4. Does anyone think that might help?
2. I have an old computer sitting in another room that I am thinking about installing Win XP onto (the scanner box still has the old XP drivers).

I am just reaching out in hopes that someone may have some other ideas I could try.

Thanks, in advance, for any help you can provide.

Regards,

Bob