BSOD errors for free!

[Achilles2]

This morning I walked into work to find my computer hung on a Windows Update that I had started after leaving work yesterday. It said it was installing update 5/14 (I think) and that I shouldn't turn off the computer. Obviously I had to shut off the computer because it told me not to. When I tried turning it on I started getting several different BSODs.

Here are some of the ones I got:
BUGCODE_USB_DRIVER (0xFE)
PAGEFAULT_IN_NONPAGED_AREA (0x50)
IRQL_NOT_LESS_OR_EQUAL (0x0A)
DRIVER_IRQL_NOT_LESS_OR_EQUAL (a warning about rdyboost.sys)
BAD_POOL_HEADER (0x19)
BAD_POOL_CALLER (0xC2)
0xD1 (usbport.sys)
0x7E (volsnap.sys)

Computer: Windows 7 Professional 64bit pro, 6gb ddr667 fb ram, 2x(4x2.66ghz xeon cpu)
I recently recovered my computer from a Symatec bacupexec restore because I was getting a possibly related (I have no idea what caused it) bsod at startup.

I can't boot into windows no matter what I try. I've tried safe mode, last working config, install cd crashes.. if I get lucky I'll get far enough into startup that it will run chkdsk during which it will delete a bunch of stuff ("deleting index entry <hex number that varies> in index $I30 of file 219038") but after it restarts I get some random BSOD again.

Also, I had an option to enable boot logging so I attached that. It look like it stops at AFD.SYS for some reason.

I could restore again but that takes ~10 hours.. plus it could be that my computer has some deep emotional issues that cause it to go bsod crazy like this whenever it gets mad at me. those issues might be stuck in the restore point too.

Edit: I found a file called memory.dmp in my Windows directory (dual booting fedora so I can see all my windows files).. it's ~330mb so I can't upload it but if anyone has any advice for deciphering some useful info out of it let me know.

 

[Maguscreed]

Sounds and looks like a failing hard drive.

 

[Achilles2]

Sounds and looks like a failing hard drive.

I was sort of beginning to wonder if all these errors might just be pointing to a hardware issue.. only thing that seems odd is that I have a partition on the same hard drive with Fedora (what I'm using now) and I have had absolutely no problems with it. I don't know anything about how hard drives fail, but can parts of them be failing while other parts work fine? (e.g. a portion of the disc is scratched or something similar..)

 

[Maguscreed]

It is possible for physical sections to go bad before others, or simply for the mechanical parts to stop seeking to certain locations.

 

[Achilles2]

It is possible for physical sections to go bad before others, or simply for the mechanical parts to stop seeking to certain locations.

I just ran a diagnostics test on my computer (program came with the computer.. it has a bunch of different tests). It said it scanned the entire hard drive and didn't find any errors. Looks like it's time to buy a sledgehammer.