BSOD Shortly after logging on to user profile.

As the title states, I'm experiencing frequent BSODing (this is sudden, I've never had BSOD issues with Windows 7 before) shortly after logging on to my user profile. I don't know if the problem is affecting other profiles or not, but I'm currently logged on in Safe Mode with networking, and everything is fine so far.

To my knowledge, no recent system changes were made. Before I got off of the PC earlier in the day, it was working fine. Another person had been using it for a bit (the joys of a shared PC, I know), so I walked over and started it up while I made myself something to eat.. when I noticed it had restarted on its own (so I guess it also BSODed while at the logon screen also). I sat down, let it restart, logged on my profile, and another BSOD occurred. I booted to safe mode, ran a quick scan with MSSE (which found nothing), restarted normally.. another BSOD.

The Event Viewer has the following errors:

1. The PnP-X IP Bus Enumerator service depends on the Function Discovery Provider Host service which failed to start because of the following error:
The dependency service or group failed to start.

2. DCOM got error "1084" attempting to start the service NVSvc with arguments "" in order to run the server:
{DCAB0989-1301-4319-BE5F-ADE89F88581C}

3. The Network List Service service depends on the Network Location Awareness service which failed to start because of the following error:
The dependency service or group failed to start.

4. The following boot-start or system-start driver(s) failed to load:
AFD
DfsC
discache
MpFilter
NetBIOS
NetBT
nsiproxy
Psched
rdbss
SCDEmu
spldr
tdx
Wanarpv6
WfpLwf

And many others. One in particular involving a "GPClient", which I searched google for, and led me here. I read the thread it directed me to, in which the individual had removed AVAST and Daemon Tools, and seemed to have their problem fixed.

In any event, here are the contents of the Windows\Minidump folder, as suggested in the other thread I read.

A little additional information:

I tried once more to start the PC normally.. and I noticed that it was taking substantially longer to "fully" start up (ie: ability to access programs without having to wait on startup items (services, etc.) to start), so as soon as I could I opened up the event viewer and mashed F5 a bunch to refresh the entries. Right before the BSOD that I knew was coming, I saw a bunch of errors labeled "disk," and one labeled "atapi".

Strange thing is, those entries don't show up when viewing in safe mode. (safe mode still runs fine at this point)

So after seeing that, I ran chkdsk with option 1. It apparently completed while I was AFK and I came back to the logon screen. Of course another BSOD came, but this time I didn't see any disk-related errors in the event viewer before hand.

This time I've gone back and ran chkdsk once more, with both options. (the GUI version from within Windows, while in safe mode obviously. It asked to schedule it for the next boot.)

It's seemingly stuck at 14% of step 4. I see the following lines on the screen:

Usn Journal verification completed.
CHKDSK is verifying file data (step 4 of 5)...
14 percent complete. (15 of 474864 files processed)

And it's been sitting there for about an hour now. I don't even hear my hard drive spinning, and PC temps (there's an LED on my motherboard with a temp indicator) are normal.. so it doesn't seem to be doing anything at all. It seems to be either froze, or just stuck where attempting to read what I suspect is a bad sector, severely corrupted data, etc.

So it's looking like my HD is actually going bad. Troublesome, but thankfully it has a 5 year warranty (which is still active) in the event I had to send it back.

Any thoughts?

And after reading the guideline thread.. here's the zip file from the SF_Diagnostic_Tool. :)

Attachment 285459

Here's the screenshot from CDI. Following the second link to test shortly.

Attachment 285468

Both the quick and extended tests from the Data Lifeguard program both immediately failed, so it seems the hard drive is indeed the issue. Thankfully it's still under warranty and I have the purchase information, so.. I guess I'm going to have to try and extract what data from it I can, if any, and start that whole process.

Thanks for the help!