Random BLue screens

Well, it's not very clear what's to blame on this one. Please run Driver Verfier according to these instructions:

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
If that doesn't work, post back and we'll have to see about fixing the registry entry off-line.

More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users

Summary of the BSOD:

Code:

Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue Jun  1 19:14:08.954 2010 (GMT-4)
System Uptime: 0 days 6:18:15.093
BugCheck 3B, {c0000005, fffff80002cdb497, fffff88008cf8060, 0}
Probably caused by : ntkrnlmp.exe ( nt!PspReturnQuota+47 )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  svchost.exe

I hope that these dump files will contain some useful info, but the Driver Verifier dump files are the one's that are most likely to have the info that we need.

One of the dump files blames your Intel storage drivers - so I'd suggest updating them first.
 Intel(R) Matrix Storage Manager

Summary of the BSOD's:

Code:

Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Wed Jun  2 00:11:39.532 2010 (GMT-4)
System Uptime: 0 days 0:26:46.046
BugCheck BE, {fffff880014919e8, 8000000003a67121, fffff88003b47840, b}
*** WARNING: Unable to verify timestamp for iaStor.sys
*** ERROR: Module load completed but symbols could not be loaded for iaStor.sys
Probably caused by : iaStor.sys ( iaStor+f163 )
BUGCHECK_STR:  0xBE
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue Jun  1 23:43:49.303 2010 (GMT-4)
System Uptime: 0 days 4:28:42.817
BugCheck 1A, {5003, fffff70001080000, ee, f0000000dc}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+21b86 )
BUGCHECK_STR:  0x1a_5003
PROCESS_NAME:  CurseClient.ex

The stuff in RED below will make the system stop so you can read the BSOD:

Windows 7:
Go to Start and type in "sysdm.cpl" (without the quotes) and press Enter
Click on the Advanced tab
Click on the Startup and Recovery Settings button
Ensure that "Automatically restart" is unchecked
Under the Write Debugging Information header select "Small memory dump (64 kB)" in the dropdown box
Ensure that the Small Dump Directory is listed as "%systemroot%\Minidump" (without the quotes)
Click OK twice to exit the dialogs, then reboot for the changes to take effect.

You must remove the current iaStor.sys file and replace it with a new one (because of the error).
If you don't, it's likely that the error will keep occurring.
The easiest way is to uninstall the current software and then to install the updated software.

To further complicate things, it appears that they've changed the name to Rapid Storage Technology (RST)
The latest version is at this link: Â Intel(R) Rapid Storage Technology
The previous links don't have the most updated version.

Intel version is 9.6.0.1014 dated 23 Mar 2010
MSI version is 9.5.0.1037 dated 08 Jan 2010

Your call...

1 - check in C:\Windows for a file named MEMORY.dmp Let us know if it's there or not.

2 - The drivers are for the controller - it does RAID and it does non-RAID.