chkdsk and \Device\Harddisk1\DR1 has a bad block

I'll start with my two questions, then go to the backstory part:

1. How do I force Windows to run a chkdsk on a certain disk, not now, but at bootup?
2. What do a seeming explosion of Event ID 7 (bad block) errors mean, on a disk I believed to be robust?

Now the background.

In viewing my event log yesterday, I noticed, from a week previously, there were two errors "The device, \Device\Harddisk1\DR1, has a bad block."

I guess that's worth another question - I have three hard disks; how do I know which one it's referencing?

My computer configuration has three physical HDs. C is the 250-gig boot drive and has all the software and OS files, and the page/swap file. D is the 500 gig "data" drive with the documents, program data, etc. There's no swap file on it. F, also 250 gig, is mirrored from D using the MirrorFolder software.

I ran chkdsk on C, and of course Windows would only do that on restart. The chkdsk took about 90 minutes on the 250 gig drive, and found no errors, no lost sectors, no bad anything.

This morning before going off to work, I figured I'd check D. To my shock and disappointment, the chkdsk just started running. That's why I asked question 1 above - I'd love to know a way to delay a chkdsk until during the boot sequence.

In a relatively short time, it had gone through the first three of five steps and had started on the file data portion.

There were two "The device, \Device\Harddisk1\DR1, has a bad block." errors while I was still home (I'm looking at the event log; I had not noticed them at that time, and the chkdsk progress count continued). These were about two minutes apart.

Then starting 19 minutes later, and continuing all day, 2, 4, 5, whatever number of seconds apart, the bad block error message was logged. More than 6,400 errors.

When I got home from work, the computer was on, everything I had running was still going, but I could not click out of the chkdsk, and as I tried alt/tabbing and then ctrl-alt-del, the mouse pointer finally froze, and I force-restarted the computer.

My D drive and F drive have been in the computer since it was built five years ago. They never give me a problem. The MirrorFolder data suggests that the files sync fine. I've never had a disk-related BSOD with this computer.

And the Error 7 "The device, \Device\Harddisk1\DR1, has a bad block" messages logged in my event viewer, which goes back to September 7, 2015, are thus:

• 1 on September 10, 2015
• 2 on 1/12/2016, four seconds apart
• 6,383 today when running chkdsk

What might I do here?

With no visible problems, and with only three logged such errors prior to today, I'm inclined to play ostrich for a bit and ignore it. For all I know, the 6,383 errors today were all on one block - is there a way for chkdsk, or some other utility, to report on the block and identify what file is associated with it? And/or just mark it as bad?

Suggestions needed, please!

I know it's bad form to bump my own thread, but I have somewhat new information, and a repeat of a question I'd asked in the original post.

Left to its own normal uses, my computer has been fine. And, again, immediately prior to all this, I imaged the C drive in full, with no errors, then got a wealth of them when running chkdsk on my D drive.

Last night, knowing that it was during the file contents part of chkdsk that I had the worst errors, and that about 25% of the filespace on D is three images of C, I figured I'd do a virus check on those image files - just to see what happened when those three big files were scanned. The scan took a while, but they're big files, so I wasn't concerned, and in the end, it ended normally.

(By the way I image to an external hard drive in January, April, July, October, and just for speed and convenience image to D the other eight months of the year - so I always have an external image of my system drive that is three months old or newer).

Then tonight I looked at the event viewer and I noticed 38 errors in the past 24 hours. HUH? Sure enough, 37 of them are disk errors.

This time the message read "The device, \Device\Harddisk2\DR2, has a bad block." - if you recall the message I got when chkdsking D earlier in the week said "The device, \Device\Harddisk1\DR1, has a bad block."

So first, again, what's the difference between Harddisk1\DR1 and Harddisk2\DR2? In both cases this week, it was the same drive (D) that had activity at the time the errors were logged.

And second, what should I do? Okay, I know what I should do - my C drive is a year old but my D and F drives are five years old and I should replace them sooner on my terms, than later under catastrophic circumstances.

But I really would like to know which disk (or, gak, disks, plural) is/are failing, and where. And if possible, I'd like to just benignly identify and segregate the bad sectors.

Many on sevenforums have recommended spinrite, which I purchased in 2008, still have, and it did work seeming miracles on a very messed up laptop back then.

I just don't know if I want to invest all the time needed to run it on a 500-gig disk.