HDs cause PC to reboot

[Maztrim]

I turned my PC on this morning and after about 30 second it rebooted itself. I then did a bare bones boot and tracked the culprit down to my two stripped HDs. WD Raptor 10,000 rpm. While the computer is on I can access the drives. This is the error message I received:

A Problem Has Been Detected and Windows Has Shut Down To Prevent Damage To Your Computer
Driver_TRLQ_Not_Less_Or_Equal

Technical Information:

***STOP: 0x000000D1 (0x0000002A, 0x0000000A, 0x0000000, 0xBA6FCAFB)

*** SI3112r.sys - Address BA6FCAFB base at BA6F5000, Datastamp 3ed7e3b9

Beginning Dump Of Physical Memory
Physical Memory Dump Complete



Any ideas what the problem could be? The HDs don't have anything important on them but I'd rather not have to scrap them.
Also, no new software was added to the HDs since a few days before this problem occurred.

[Paul Komski]

While the computer is on I can access the drives.By what method?

If this was a one-off then run chkdsk /R from the command prompt and scan your system for malware. If the array is inaccessible but the individual drives are seen in the BIOS and are accessible from a diagnostic utility then you could check the drives with the utility, zero them (not mandatory), rebuild the array and clean reinstall.

[Maztrim]

The drives are accessible through normal methods. ie. clicking on the drive under "my computer". How can I run chkdsk /R if the PC reboots after 20-30 seconds?

[Maztrim]

Never mind that above post.....

[Paul Komski]

See if the system continues to reboot if you boot into Safe Mode (F8 during startup).

[Maztrim]

Booted fine in safemode. Ran chkdsk and came back with 0 bad sectors. What's my next step? Format?

Also, the bad drives don't have my OS on them. Not sure if that makes any difference.

[Paul Komski]

STOP errors and other BSODs can be very hard to track down. It seems unlikely that your array or the drives it contains are the root cause. Some aberrant or corrupted software would seem the most likely culprit at the moment but bad RAM would be another hardware contender.

Try starting normally but after disabling as many programs as possible using msconfig. If that solves the problem then try adding the startup programs one by one. This can be a lengthy process to get to the bottom of and with no guarantee of success.

A scan for viruses and malware might also be wise. Examining the Dr Watson logs and the memory dumps can give some indication sometimes but its not something I'm very experienced with. The fact that SI3112r.sys is mentioned in the BSOD doesnt mean that those drivers are primarily at fault but that they are simply involved in the chain of events leading to the BSOD. For example any file i/o to the hard drives might be using the drivers.

[Maztrim]

I'll try what you mentioned. In the end I'll probably end up formating the drives anyway since there isn't anything important on them. Thanks for the help Paul.