vsmraid.sys bsod on W7 installation

[John440b]

I'm trying to do a clean windows 7 64 bit installation. I get past the country selection and get BSOD with:
DRIVER_IRQL_NOT_LESS_OR_EQUAL... VSMRAID.SYS ADDRESS FFFFF8800IB7F6FD BASE at FFFFF88001B72000, datestamp 4983a701.

The gigabyte EP45-UD3P mobo has the latest bios. I read on other posts that the raid driver needs to be updated. However, the driver is on the win 7 installation disk and the system crashes before I have the option to load custom drivers.

Any help appreciated...

 

[zigzag3143]

I'm trying to do a clean windows 7 64 bit installation. I get past the country selection and get BSOD with:
DRIVER_IRQL_NOT_LESS_OR_EQUAL... VSMRAID.SYS ADDRESS FFFFF8800IB7F6FD BASE at FFFFF88001B72000, datestamp 4983a701.

The gigabyte EP45-UD3P mobo has the latest bios. I read on other posts that the raid driver needs to be updated. However, the driver is on the win 7 installation disk and the system crashes before I have the option to load custom drivers.

Any help appreciated...

We need the actual DMP file. use these to find and upload it to us. http://www.sevenforums.com/crash-lockup-debug-how/34900-1-novice-how-ask-help-bsod-problem.html

Ken

 

[John440b]

I'm trying to do a clean windows 7 64 bit installation. I get past the country selection and get BSOD with:
DRIVER_IRQL_NOT_LESS_OR_EQUAL... VSMRAID.SYS ADDRESS FFFFF8800IB7F6FD BASE at FFFFF88001B72000, datestamp 4983a701.

The gigabyte EP45-UD3P mobo has the latest bios. I read on other posts that the raid driver needs to be updated. However, the driver is on the win 7 installation disk and the system crashes before I have the option to load custom drivers.

Any help appreciated...

Further to the ongoing Drama...

The problem up to this point was that the installation never survived long enough to mount a disk system much less create a crashdump file. The only consistent indication was the reference to the vsmraid.sys file. Remember too, that this is a clean installation, NOT an uprade.

After reviewing similar posts on other forums I noticed a common theme with systems having over 2Gb of Ram. Out of desperation I removed 6 out of 8 Gb of ram from the machine and ran setup again. "Low and Behold" the system installed this time.

Now before you all stand up and say "Well of course it was a memory problem"... This system was running 32 bit Windows 7 RC for nearly a year on the same 8 Gb of Ram.

When I physically increase ram from 2 to 4 Gb the machine BSOD's within seconds of login. I have tried each stick of ram singly and in pairs with the same result. Single stick of RAM, machine runs, pairs of ram BSOD.

That said, i now think the memory is mostly red herring, because now that I have an installed operating system I am getting crash dumps and those dumps are telling me exactly what I asked about in the first place. "How do I update VSMRAID.SYS"

 

[CCurtis]

I have a very similar problem (see http://www.sevenforums.com/crashes-debugging/77593-bsod-asus-a8v-vsmraid-sys.html) Have you tried just 3GB of RAM?

 

[CCurtis]

Apologies for cross-posting (I think that's the term). If I knew how to just point to another post, I would have (see "Crashes and Debugging" post "BSOD ASUS A8V vsmraid.sys").

I was having the same kind of problem, which appeared to be related to trying to use more than 2GB of RAM. I also went through Memtest, etc. and decided RAM was ok. Then I thought it might actually be my C: drive. I ran the comprehensive WD disk test using WinDLG 1.13 (after wasting time trying to get the current version 1.17 to work and discovering all the forum messages about how it doesn't work currently) which revealed no problems, and then SpeedFan 4.40 (which I couldn't get to see the drives until the author told me to run it in Admin mode) which also showed no problems. Then, for completely unknown reasons, the gremlins went away. I am now running 4GB (4x1GB ... the same ones I started out with), memory hole enabled, and the system seems completely stable. I didn't install any new software, drivers or otherwise, so who knows?? Did you get your problem resolved?