Usually BSOD's I see have a "<filename>.sys" named. This is usually associatable with either specific hardware, or general hardware areas to help limit the search. Do you have a .sys filename named ?
Quote:
|
<stupid thing just INSISTS on putting in URL tags! aaargh !> - BitComet Version 1.00 *
|
If any of the software is cracked, that could be your problem. Keygens are usually infected. AVG misses stuff sometimes. I'd check the HJT log, double-check AVG against TrendMicro's Housecall.
Check this:
http://www.softwarepatch.com/windows...x0000000a.html
Says these errors are common with Vista, and can be related to the "storeport.sys" driver. Maybe a virtual drive ?
Check your hardware manager for flagged items. Check "show hidden devices" to see the sneaky ones.
It's XP-related, but probably applies to Vista as well. Some basic troubleshooting methods. Remove & uninstall as much hardware as possible and see if the problem goes away. How long will it run without a BSOD ? Can you get it to run longer or indefinately if the wireless is disconnected. 30 days of use might have fried the on-board NIC. You might try cracking the box opening and removing the NIC and see what happens.
http://support.microsoft.com/kb/314063