Good afternoon! (Well, down here anyway),
It is still fairly cold up here. Got some snow overnight as well. Oh well, darker days mean brighter ones to follow. A good 6°C is the best I can hope for these days.
As for the manufacturer drivers - don't worry about that... I didn't even think of it. Consider it a mistake on my part rather than neglect on your part. I probably should have checked after getting drivers from Microsoft.
I used to use Dial-up... I think about 8 or 9 years ago
. It was good enough for me at the time. I bet if I went back, I would die waiting for pages to load.
That's too bad about the SFC log. Well, good that there's no errors there, but unfortunately the scans still show some errors.
Even more unofortunate, though, is that I came home to a blue screen twice more during the weekend. Fortunately, it's not nearly as often as it used to be, not by a long shot. To be honest, I think I can live with a blue screen error every 40 hours or so. Obviously there's some underlying error that we just can't seem to find, and it will always be on the back of my mind. I won't be in such a hurry to find it. Anyway, I have included here the latest two BSOD minidumps. Hopefully they reveal something the others have not - but I think I can foresee the unfortunate result of that.
Fortunately, I can still transfer files as required. Between two of my home network laptops, I set up a torrent for BitComet to transfer a fair 35GB worth of files for a second test. During this second test, the transfer was nearly completed at 31.29GB before the blue screen error. A total of 35 hours transfer time (approximately). This is acceptable for me on a non-standard basis, considering most of my work with clients is capped at 15GB, and that's on a very rare occasion.
However, on the flip side, I am a perfectionist with a little bit of OCD in me, so in the back of my mind, I'm always going to want to fix what's broken. I'll know the issue is there so I'll continue searching.
I ran all the scans I could think of again - memtest, anti-virus (I did housecall and AVG, and I borrowed NOD32 from a friend and ran that as well), SFC scan again (same errors as before), checkdisk... I am just re-downloading and installing that hotfix that was posted here twice earlier.
So far, no dice with the scans, I have no idea what the problem is. I am beginning to think that the wireless card simply overheats and something with that causes the system to reboot. I will attempt to schedule time to run the laptop for a good 3 or 4 days without wireless next time and pray that it works. at this point, I don't care if I have to replace hardware, I just want to know WHAT to replace!
At any rate, I still owe you a lot. We are definitely gaining some ground here and I never would have thought of these things on my own. So thank you very much for the assistance!
Take your time reviewing the BSOD reports. If others on the forum have posted errors - give them priority if need be before coming back to this topic and looking over any of this. Enjoy whatever is left of the weekend!
Thanks a lot!
-Rob
P.S. Sorry I hadn't replied back in a few days!!
P.P.S. I hope you don't mind, but I have sent (/am sending) a complete SFC scan to you're e-mail address. (Update: I am rebooting to safe mode to run the SFC scan. I find that on Vista, even in elevated mode the cmd commands still get denied access to certain areas, I'll upload the entire report when complete).
(Edit - Apparently I missed a BSOD that I never uploaded from before...)