Backup Image Process BSODs

[Interrupt]

I'm having a problem creating an image backup of one of my computer's 85% full main hard drive (C drive) in any program I try. (Not the same computer as my other BSOD problem to which there is another thread dedicated.)

I'm using Driveimage XML (as recommended by RR) to create the image with the split large file setting enabled and Fast, but not super compressed enabled (by my estimations it should take around 6-8 hours to complete). Shadow volume is optionally selected. The error is a BSOD as follows:

KERNEL_STACK_INPAGE_ERROR
0x00000077
Physical Memory Dump

Gateway GM5048
Intel D945GCZ
Pent D 930 dual core 3.0 GHz
XP Media Center Edition
1 Gig DDR2 Dual Channel RAM x4 (4 gig total; limited by OS)
500 GB 7200 RPM SATA2 hard drive.
System runs optimally despite it's age.

Backup Drive - a network shared 2 TB Hitachi, physically located within this system. Previously formatted, but now functioning as a shared network drive and a secondary drive for myself (works great).

Imaging programs tried - Clonezilla (which stops and recommends a CHKDSK) and, now Driveimage XML for which I like but can't seem to get working.

Presumably the error occurs late at night during the proccess of backing up because it starts and runs fine.

Where I'm at/What I think - At the moment I'm running a (exceptionally long) CHKDSK (scheduled prior to doing the backup just in the event that it error-ed out). I'm considering defragging the hard drive afterwards (I have Ultimate Defrag and can use regular defrag if someone here prefers it). From years of use my initial thought is general wear and tear and drive corruption (again, drive works fine... just creating a drive image gives me trouble).

Ideally I'd like to create a copy of the drive/backup the drive in case of problems.

[Foggy]

Troubleshooting "Stop 0x00000077" or "KERNEL_STACK_INPAGE_ERROR"

[Interrupt]

Troubleshooting "Stop 0x00000077" or "KERNEL_STACK_INPAGE_ERROR"

Unfortunately that covers SO much that this may take forever to troubleshoot or fix. At the moment I finished the CHKDSK and will retry. If it fails again? Defrag and retry. Already checked on the page file and it is set at 3 gigs... *shrugs* I really don't know how else to troubleshoot it: the RAM is nearly brand new and has been working great, so don't think it's that. But I'll keep trying to follow things in there. Thank you Foggy for the link, maybe something there will work.

As always, if anyone has any additional suggestions such would be appreciated.

[Interrupt]

Well the defrag made the computer recover data faster when just opening and closing programs in storage, but unfortunately I still keep getting the BSOD when trying to image the disk. Chkdsk reports no errors either.

[Foggy]

Is the drive full? They need a little wiggle room so if you don't have any room get rid of some unnecessary Junk.

[Interrupt]

It is kind of full, I mean it has 100 gig wiggle room but for a 500 gig drive that may mean things are getting a little tight (the initial drive, I mean, not the one I was backing up to... that one was empty). Regardless I opted for an NTBackup for the files in the meantime, it works. May not be as elegant but at least I don't BSOD-out.

Thanks to all that helped. Just chalking all this up to the fact that some day soon I really need a new PC, lol.