[Scuddie]

I have two Western Digital WD1600JS drives (SATA II) running in RAID 0 on an ASUS A8N5X board (SATA I), making a nice and friendly ~300GB volume.  Problem is, at the most random times, I will get a BSOD with a 0X000000D1 error on nvatax64.dll, and it rightfully pisses me off.  Problem is, I cant find a tool that can detect whether the problem is with a drive, the controller, or the driver itself because I have a logical volume setup.  This has been happening since god knows when, and while it hasnt caused anything more than a chkdsk repoting an orphaned file or two, it's really becoming a thorn in my side.  Any ideas on what I can do?

[Ashrak]

Get Seagate lol

[Scuddie]

Wow!  Terrific suggestion, I only wish I would have thought of it sooner.  Boy do I feel like an idiot.  I bow to your mental superiority.

[BlackDove]

....burn.

[Ashrak]

 

[Cyker]

I have two Western Digital WD1600JS drives (SATA II) running in RAID 0 on an ASUS A8N5X board (SATA I), making a nice and friendly ~300GB volume.  Problem is, at the most random times, I will get a BSOD with a 0X000000D1 error on nvatax64.dll, and it rightfully pisses me off.  Problem is, I cant find a tool that can detect whether the problem is with a drive, the controller, or the driver itself because I have a logical volume setup.  This has been happening since god knows when, and while it hasnt caused anything more than a chkdsk repoting an orphaned file or two, it's really becoming a thorn in my side.  Any ideas on what I can do?

This is 64-bit Windows?

In cdfreaks, nVidia's ATA drivers have a reputation for causing problems with SATA CD/DVD burners, and the general advice is usually to remove them and use the Microsoft ones built in to Windows.

Might help, if you don't mind the risk...

[Scuddie]

Well, I was just about to e-mail nVidia yesterday about whether replacing the SATA driver with the Microsoft version would adversely affect the RAID stripe when, you guessed it, nvatax64.dll failed again.  However, my PC would not restart and after running chkdsk from recovery console, I could not boot into windows at all.  I had apparently corrupt lsass.exe, my registry, and half the vital system32 files.  I had lost my OS install.  Oh well...  Since XP64 was obviously damaged beyond repair (I tried a repair install), I took it upon myself to kill the entire windows install and install XP32.  It runs way smoother than XP64 and I dont need special drivers!  Yay!  I'm finally rid of that disgrace of an OS that is XP64!

Moral of the story:  XP64 sucks, and hack jobs of 32bit drivers to suit a hackjob 64bit OS will only cause problems.  I have not once again had my hard drives crash.  Yippee.

[Kazan]

Get Seagate lol

before I even read his final post i knew this was absolutely wrong

WD > Seagate


WD & Seagate > all others though


it was pure drivers - drive problems don't cause driver crashes