VIAMRaid.sys go to BSOD

[HerryCZ]

Hi,

dear all

I have MB ASUS A7V880 with KT880 chipset (VT8237 SC). When I use older version of 4 in 1 I can't read SMART informations from both SATA drives. I can see only one HDD twice. I try instal new 4 in 1 drivers (ver 516) and I can see both HDD's separatly (It's correct), but randomly windows go to BSOD with error message about viamraid.sys file. When I reinstal VIA Raid controler driver to previous version I can't read SMART info from both HDD's but windows is without BSODs.

FYI
Device : VIA Raid Controler - 3149
Driver version with BSOD : 5.1.6000.574 - 22.1.2008
Driver version without BSOD : 5.1.600.562 - 12.7.2007
South Chip and SATA : VT8237

Thank you for your help and excuse me for my english

BR

Roman Herot

[Phant]

Originally Posted by HerryCZ

I try instal new 4 in 1 drivers (ver 516) and I can see both HDD's separatly (It's correct), but randomly windows go to BSOD with error message about viamraid.sys file.

Hi Roman,

It seems, that the V-RAID driver 5.70A (viamraid.sys 5.1.6000.574) coming with the Hyperion package 5.16A has problems (here under Windows XP). I have the same mainboard and since running this driver also have BSODs here and there (mainly under havy disk load). After changing back to the V-RAID driver 5.60A (viamraid.sys 5.1.6000.562) everything seems to be ok again.

So my suggestion: Use the Hyperion package 5.15A (can be found under "Old drivers" on the Hyperion webpage).

Cheers
Phant

[Cyfyr]

Same problem here as the original poster. I'm using the same chipset I think in asus a8v motherboard with Vista 32bit. I was wondering if it was a problem with Vista Service Pack 1.. but I think it was installed at the same time as the 5.16A driver package.

I'll try going back and installing the older via driver package... if I can boot Vista again.. it's been refusing to even boot now.

[Cyfyr]

Well, in my case, reverting to older drivers didn't help.. but it seems that removing the extra ethernet card I had installed has helped. Possibly a conflict somewhere. If the BSOD returns I'll report back.

[Edit] Still getting BSOD in Vista DRIVER_IRQL_NOT_LESS_OR_EQUAL viamraid.sys

[Phant]

Just a little update: The current package 5.17a has run quite well here for some days or even weeks, although it contains the same V-RAID driver 5.70a as the 5.16a package. Until today: BSOD for viamraid.sys!

So Hyperion Pro 5.15a still is the package to be used (at least with the Asus A7V880 running Win XP).

Phant

[HerryCZ]

Yes, I try to use new version, but still have problems. My resolution I have a new MB with AMD790FX chipset and haven't problems. And old MB have still problems but I sold it.

[Phant]

Just an update:

Under Windows XP I still experience BSODs with the V-RAID driver. With the 5.18A Hyperion package the BSODs were quite seldom (one or two times in a couple of weeks), but still there (allthough it contains the same V-RAID driver as the 5.16A package, see above). Now with a new version of the V-RAID driver (in Hyperion package 5.20A) a BSOD occured a few minutes after reboot.

On my Asus A7V880 (KT880 chipset) I will continue to use the V-RAID driver 5.60A (from the Hyperion 5.15A package). This never made any problems.

Overview:
Hyperion Pro (V-RAID) -> Result
5.15A (5.60A) -> Good
5.16A (5.70A) -> Bad
5.17A (5.70A) -> A bit better
5.18A (5.70A) -> Much better, seldom BSOD
5.20A (5.80A) -> Bad again
5.21A (5.80A) -> Good (at least after two weeks running)

[EDIT]See also my post below.[/EDIT]

[NinetyOne]

Have also a A7V880, same problems.
Same BSOD with IRQ less or equal.
Was running 5.17 without any problems at all besides the smart stuff which was just as wrong as the first poster said.

My System:
A7V880
Sempron 3000+
4x512MB Kingston Ram @166
Audigy LS
ATI HD 3650.

I only have BSOD during heavy traffic to external usb device and games.

[Phant]

It seems that the current Hyperion Pro package 5.21a runs fine on my machine now (no BSODs in two weeks). Although the VRAID driver hasn't changed since the 5.20a package, there definitely have been changes in other parts of the package (maybe some INF settings or driver parameters?).