IP 35 Pro esata crashes Vista

[gquiring]

I have an IP 35 Pro M/B for the past 8 months now with no issues running Vista 32. I bought my first E Sata drive from WD (MyBook 1TB). I plug the drive in and Vista sees the drive and I can copy files to and from the drive. Within a few minutes of using or not using the drive my box just locks up and boots. Vista comes back and says my NVidia 8800 driver is the cause.

I updated my IP 35 bios, Nvidia 8800 drivers and have the latest Vista updates including SP1. The box just boots randomly with no warnings. I don't even have to use the drive and it will boot. If I unplug the E Sata drive the boots stop.

The system has 4gig ram, SB X-Fi, Quad 6600 chip. No overclocking.

[Lvcoyote]

How do you have the jmicron controller set to in BIOS?? Should be set to IDE and make sure your using the latest Jmicron drivers. When installing these drivers choose the standard IDE install when prompted.

[gquiring]

BIOS is set to IDE. I installed the latest beta drivers R1.17.39.01 and same issue. I do get a blue screen error now PFN_LIST_CORRUPT. If I unplug the esata drive no issues. I can't even get the box to boot reliable if the drive is on.

[BUFF]

iirc the WD Mybook eSata cable/connector is known to cause problems.
again iirc trimming it back to give a better connection helps.

[gquiring]

iirc the WD Mybook eSata cable/connector is known to cause problems.
again iirc trimming it back to give a better connection helps.

I am not using the WD eSata cable, it did not come with one.

[BUFF]

well, it's the insulation around the connector then that needs trimmed.
I don't have a Mybook, just recalling from the abit forum where people have been through similar before.

These problems only seem to come up on WD Mybooks (& not even the Pro versions of those) so it seems to be mainly a WD problem more than an abit one.

Of course the fact that Vista is blaming the nVidia drivers may mean that in your case it perhaps is OS related, would be interesting to know if you had the same problem under XP?

[gquiring]

Is there a good photo some place to show how much has to be trimmed? My cable is a serial ATA 26AWG E189529 AWM style 272530V VW-1 VEGA TECH.

[gquiring]

I don't have XP loaded so I can't test that. I need 5 posts before I can embed a URL. Sorry for breaking up the responses......

[gquiring]

Here is what my cable looks like:

[gquiring]

I trimmed my cables back about 2mm. I don't think it will solve the problem. The cables were not restricted when getting plugged in. With the trimming I can see them sticking out so it looks like they were going in all the way. Below is the cable after it was trimmed and plugged into the WD drive.

[gquiring]

It crashed with the trimmed cable. Blue screen, I was not quick enough to see the error.

[serulin]

Hey gquiring,

Did you ever fix your problem? I have almost the exact same problem as you and specs too.

Computer:
core 2 duo e6750 OCED 3.2ghz
4 gb ram
8800 gts 512
vista 32bit
1 sata II internal drive
1 ide internal drive
1 esata drive

My system was stable until I bought this new HD. Its a laptop drive and I put it in a enclsoure that supports esata and usb 2.0

Everything works if I just plug it in to transfer or leave it there for a while. But after around 20 minutes. The screen just goes black and nothing works. If i do ctrl alt delete it gives me a bsod. And when it reboots vista says its related to nvidia drivers.

So basically theres no problems with drivers or using the hard drive for less than 20ish minutes. But after that it crashes. Most of the time im away and come back to this. I havn't stayed long enough on my computer yet to watch it and see what happens. Im testing right now if I dont plug in my external to see if it crashes. And so far its ok. Ill try leaving it in on usb 2.0 only afterwords.


Anyone else have any suggestions? fixes? ideas? Any help is appreciated!

[gquiring]

Hey gquiring,

Did you ever fix your problem? I have almost the exact same problem as you and specs too.

Yes, the latest Jmicron drivers resolved my issue.

[watercooled]

I also had a similar problem with the JMicron controller on my Gigabyte motherboard. I just moved everything to the Intel ICH-9 controller SATA ports then disabled the JMicron controller in BIOS. Problem solved.

[serulin]

Yea i just fixed it too. My problem was that I was using jmicron for my ata drive and then ich9 for my sata main drive. So when I got this external esata i guess something was messing up with the older drivers.

I had to disable the old jmicron controller in safe mode, install the new one *cuz for some reason it doesnt replace it* then change my jmicron from ide to ahci. So now ich9 and jmicron are both at ahci. It gave me a blue screen the first time i changed it in bios but then after it restarted it worked...

Anyways thats my experience with this.

Thanks for your guys's as well, hopefully it can help others in the future who read this thread as i did.