This can be solved by updating the si3112.sys to version 1.00.51 with the download http://www.siliconimage.com/docs/SiI3x12A-Serial%20ATA%20(SATA)%20Windows%20RAID%20Driver.zip for win2k/xp. You may have to uninstall your sata raid device that uses this driver then use these drivers as the install location for when it refinds the device after reboot. Or regular updating may work.
What i can't solve is the constant rebooting of the computer...
Windows has been randomly (I think) crashing to the dreaded blue screen with something like the following message. This is all from memory, so bear with any mistakes or leave-outs.
"A problem has been detected and windows has been stop to prevent any damage from happenning to your computer.
DRIVER_IRQL_NOT_LESS_OR_EQUAL
If you see this screen for the first time, restart your computer. If this screen keep happering, follow these step:
be sure that all the new hardware and software are correctly install.....yaddah yaddah yaddah.
Then there's something about a specific file: si3112r.sys.
From what I can find out, this file has somehting to do with my RAID setup. The sile is in all of the directories that have something to to with the RAID setup. My RAID controller is a Silicon Image Sil 3512. My machine setup is as follows:
AMD Athlon 64 3200+ (2.0 GHz)
Gigabyte K8N Pro (version F8G) mobo
1 GB RAM
MSI 256MB Nvidia Geforce 5600
2 120GB SATA Hard drives (1 Maxtor, 1 Seagate)
Running Windows XP Pro (SP2)
I've had the machine for nearly a year, but this problem only started recently; within the last two months. The reboot occurs apparently in totally random fashion; sometimes, there'll be a program (game or something) running, other times the system will be idle.
I've seen issues similar to this posted, but following the advice in those threads didn't help me. Specifically, somebody was encountering almost the exact same message on a blue screen (the only difference was that, on my screen, the specific file was mentioned), and the general consensus was a memory problem that could be diagnosed and corrected with Memtest86. I couldn't get that program to run, so here I am. Plus, I'm just plain tired and frustrated with searching for a solution that suits my problem.
Thanks for the reply, but this is an considerably old post, and the problem was solved by a new mobo November 04. That's my bad, dude. Shoulda deleted it a year ago. Agian, thanks.
Comments
What i can't solve is the constant rebooting of the computer...
Thanks for the reply, but this is an considerably old post, and the problem was solved by a new mobo November 04. That's my bad, dude. Shoulda deleted it a year ago. Agian, thanks.