Vista x64: Need help interpreting MiniDump logs

LONG VERSION:
So, today my Vista started crashing whenever I would Restart. This morning I restarted so I could boot into Ubuntu, without realizing it, I had a BSOD, but the computer booted into Ubuntu fine, as it's the default in GRUB.

My Vista Partitions wouldn't mount (I eventually realized this was because Windows didn't shutdown properly, and thus was "still using" the partitions). So, I decided to boot back into Vista and get a clean shutdown. I booted, and immediately "Restart" and boom BSOD. Did this another time, BSOD. I tried to boot a third time, and lo and behold I get a BSOD on startup (something to do with TCPIP.SYS?

I was able to nerd my way into getting the Dump files into .txt. I have attached them. The first 3 happened at Shutdown, the 4th shortly after booting into Vista.

If anyone can give me an idea of what is going on, I would REALLY appreciate it. I am booted fine into Vista right now, but I don't want to leave this problem un-resolved if it could potentially beef my system and data later...I would rather re-image and go through the pain of reinstalling and re-customizing my rig.

 

Click me.



.

 

Thanks for that Silas, but that's the link I used to get to the log in the first place.

I prefer to go the DIY route, but unfortunately I'm in a bit over my head on this one. =\

UPDATE: I have Rebooted (w/o a BSOD) and booted successfully since last post.

 

dump3.txt mentions "avguard.exe" which may be your antivirus program... a Google search suggests Avira. Are you running that? Could you try disabling it?

dump4.txt mentions "inspect.sys" which Google suggests might be Comodo. Are you running that? Could you try disabling it? (And using Windows' built-in firewall instead for a while.)

Also run a mem test if you haven't already.

One of the other dump files mentioned dwm.exe... which is the window manager... which shouldn't be a problem in itself, but... make sure your video drivers are up-to-date.

EDIT: Oh sorry I didn't read your post carefully, I didn't realize you couldn't boot. Umm... try pressing F8 at bootup and do system repair or system restore.

 

Tx Swarm,

You nailed all of them, I'm running Comodo and Avira...you actually read it right the first time. I am in Vista, and since I first posted (in Ubuntu) I haven't had any problems...not sure what's up with that.

I am going to run a memtest right now though.

I'm running 169.25 nVidia, shouldn't be a problem, but I'll look into something a little more current.

UPDATE: MemTest was clean.

 

I still don't know if either of those programs is the problem though... sometimes stuff appears in the stack trace even if it's not the root cause. Still, I would quit running those programs for a while until you figure this out.

Also, you can try my general-purpose BSOD-fixing tips, which are:
- Update to the latest BIOS for your machine
- Go into Windows' Device Manager and disable any hardware you've never used on this machine. This might include stuff like: modem, smart card reader, expresscard reader, firewire. Be aggressive here -- if you ever need one of these devices, it only takes 10 seconds to re-enable it.
- Go into BIOS and disable any devices not present in your machine. This might include stuff like: serial port, parallel port, WWAN.

 

You checked your hdd for corrupted files?

 

Now that you mention the hdd, this gets me thinking.

The first time the system crashed (unbeknownst to me), I then had problems with those Vista Partitions mounting. (I have 2 partitions that were created by Vista, the OS, and my 'Files' partition).

B/C I didn't realize Vista crashed when I restart it, I tried several things to get my "files" partition to Mount in Ubuntu, including a couple 'force' mount commands. I wonder if this caused some corruption, or at least changed files enough to cause further problems when I booted back into Vista.

I will bootup and do a diskcheck, and we'll go from there.

UPDATE: I was in Ubuntu, and was working on an Excel File with Office 2007 (via Crossover). I'm not sure if this is related, but I booted into Windows so I could schedule a disk check for both Vista partitions. I restarted and got the BSOD again. Upon reboot, the disk checks ran and some repairs were made (not sure if these happened b/c of the crashed restart or because of changing files while in Ubuntu...I've not had problems with that in the past):

C (Vista OS installation):
Cleaning up 108 unused index entries from index $SII of file 0x9.
Cleaning up 108 unused index entries from index $SDH of file 0x9.
Cleaning up 108 unused security descriptors.

D: (my Files drive)
Cleaning up 5 unused index entries from index $SII of file 0x9.
Cleaning up 5 unused index entries from index $SDH of file 0x9.
Cleaning up 5 unused security descriptors.

The USN Journal length 0x5b8508 in file 0x222a is less the
largest USN encountered, 0x5b8560, plus eight in file 0x20.
Repairing Usn Journal $J data stream.

I can get the Dump file from the crash.

 

Not sure if this helps solve the mystery, but this morning I decided to try a new video driver (178.13). When I went into Control Panel to remove the nVidia drivers, it gave the error msg that it was already uninstalled and askded to remove it from the "Programs and Features list".

Well, it wasn't really gone, so I suspect something a little fishy is/was up. After uninstalling the driver I had a clean boot (no BSOD).

Another oddity, is that Vista always boots in Power Saver mode