Random Reboots while idling.

[parkside.ally]

I've been following a couple of threads about random reboots of Win XP and believe I have a similar problem, but the reboots never happen while the computer is in use. Only when it's left idling for a while. We experience about a dozen reboots per day some with the BSOD. I've captured the "memory.dmp" and will post that as well. Near as I can tell from the discussions I've read, I'm most likely looking at a drive problem. I'm using a VIA software raid 0 with 2 250MD SATA disks. I've forgotten the brand of the 2 drives on this machine. I believe they are WD's. Any thoughts would be appreciated.
Here's the last minidump. I hope it's not too much for one post.
Thanks.


KERNEL_STACK_INPAGE_ERROR (77)
The requested page of kernel data could not be read in. Caused by
bad block in paging file or disk controller error.
In the case when the first arguments is 0 or 1, the stack signature
in the kernel stack was not found. Again, bad hardware.
An I/O status of c000009c (STATUS_DEVICE_DATA_ERROR) or
C000016AL (STATUS_DISK_OPERATION_FAILED) normally indicates
the data could not be read from the disk due to a bad
block. Upon reboot autocheck will run and attempt to map out the bad
sector. If the status is C0000185 (STATUS_IO_DEVICE_ERROR) and the paging
file is on a SCSI disk device, then the cabling and termination should be
checked. See the knowledge base article on SCSI termination.
Arguments:
Arg1: c0000185, status code
Arg2: c0000185, i/o status code
Arg3: 00000000, page file number
Arg4: 05477000, offset into page file

Debugging Details:
------------------

ERROR_CODE: (NTSTATUS) 0xc0000185 - The I/O device reported an I/O error.

DISK_HARDWARE_ERROR: There was error with disk hardware

BUGCHECK_STR: 0x77_c0000185

DEFAULT_BUCKET_ID: DRIVER_FAULT

PROCESS_NAME: System

LAST_CONTROL_TRANSFER: from 80520bf5 to 8053354e

STACK_TEXT:
f89e1cf0 80520bf5 00000077 c0000185 c0000185 nt!KeBugCheckEx+0x1b
f89e1d60 804e80c6 c02a5dd4 c02a5dd4 00000001 nt!MiMakeOutswappedPageResident+0x362
f89e1d8c 804e6b39 007e9660 00000000 82bc3b30 nt!MmInPageKernelStack+0xf0
f89e1da4 804e6b1c 827e96c0 8057d0f1 00000000 nt!KiInSwapKernelStacks+0x16
f89e1dac 8057d0f1 00000000 00000000 00000000 nt!KeSwapProcessOrStack+0x89
f89e1ddc 804f827a 804e6a98 00000000 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16

STACK_COMMAND: kb

FOLLOWUP_IP:
nt!MiMakeOutswappedPageResident+362
80520bf5 cc int 3

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!MiMakeOutswappedPageResident+362

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 45e54711

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: 0x77_c0000185_nt!MiMakeOutswappedPageResident+362

BUCKET_ID: 0x77_c0000185_nt!MiMakeOutswappedPageResident+362

Followup: MachineOwner

 

[Route44]

Two things stand out for me: 1) Memory corruption. Run MemTest86+ for a minimum of the 7 passes. If you have any errors you have faulty RAM that needs to replaced. If you have more than one stick then you will need to run the test to determine if which one or if all sticks are faulty one stick at a time.

2) Disk failure. Have you run a diagnostics on your harddrive to see if it is failing? I strongly suggest that you a) do so A.S.A.P and b) back up your important data either in an external harddrive or burn a few DVDs. I'd do both.

Also, an 0x77 error can indicate page of kernel data requested from the pagefile could not be found or read into memory. This message also can indicate disk hardware failure, disk data corruption, or possible virus infection.

 

[parkside.ally]

O.K. thanks. I'll run the memtest and get back to you. I've already done the back-up and will continue with the diagnostics on the disks. Also, I failed to mention that the machine has been running perfectly for over a year! This problem only recently started happening. I run NAV and keep it updated as well as Windows update. I also try to keep the dust at bay inside the case, though I'm not prerfect. I'll get the other diagnostics done and repost.
Thanks