[svinyard]

I'm having the BSOD issue every time I plug in my USB HP (Adaptec AVC-3610) dual tuner. Vista Ultimate 32bit, Dell C521, Dual AMD 64 Athlon, 1GB ram, umm... , ATI 1300 video.

Attached are the dumps
MiniDumps.zip

Please Hep me! I havn't seen my stories in about a month! I have no idea how Heroes is doing after the whole march madness thing.

[svinyard]

Originally Posted by EvanTribley

I had a similar issue when I plugged my Adaptec AVC-3610 into my Vista HP laptop. I would get a blue screen crash and it would start a reboot cycle until finally it would login. I also reinstalled Vista using the upgrade, but I did not have to reinstall XP to do this. It also allowed me to do a clean install. I am curious that we had such a different experience reinstalling Vista.

I would suggest installing the drivers one at a time, and if you are downloading them from Windows Update, I suggest checking the ATI website for updated drivers. Also do a memory test on the RAM because it seems Vista is much more "cranky" than XP if something is not working 100% the way it expects it to.

What did you do to fix yours?

[Rollin' Rog]

Please re-upload your dumpchecks -- there is something wrong with the current attachment url.

Then I will split your posts off to a separate thread and post any relevant results from the debug.

[EvanTribley]

I honestly don't know. I have the HP Dual Tuner, same thing as the AVC-3610. I am running an AMD Mobile Sempron. Here is everything I did (this was over a week of trying things):

1. System restore before driver install and tried to reinstall tuner, still got BSOD
2. System restore again, went to HP website and tried to install HP Dual Tuner drivers for MCE 2005, still BSOD
3. Reinstalled Windows Vista Home Premium using my digital locker download, still got BSOD
4. Ordered Vista DVD from Microsoft, got BSOD then used DVD to "repair" Windows. It said there were no errors found, but after that TV Tuner drivers installed correctly and worked fine.

I also posted on the Windows Vista community site but got no real help there. Maybe try to use the Vista DVD to repair after rebooting from BSOD. That is my best guess of what did it, but I am honestly not sure.

[svinyard]

Here is the upload again
HERE

[Rollin' Rog]

Ok, I've only done the last 2 -- but from those it is pretty clear that this device is the culprit:

http://www.runscanner.net/getmd5.asp...s=avcuwil2.sys


I'm spliting your posts off now to a separate thread so hope you don't miss it.

I don't know what to tell you except to contact support from the Device vendor and see what they have to say. I assume you've done a removal and reinstall of the device and its drivers?

I think I would remove the device physically -- uninstall the drivers -- then go into the BIOS/CMOS setup and reload the defaults -- you might also want to try physically resetting the CMOS with the onboard jumper or by removing the battery for a bit.

The error message mentions something about a possibly corrupt resource list. If they are talking about CMOS data -- that might fix it or force a reassesment of resources.

BugCheck C2, {99, 94540330, 0, 0}

*** WARNING: Unable to verify timestamp for avcuwil2.sys
*** ERROR: Module load completed but symbols could not be loaded for avcuwil2.sys
Probably caused by : avcuwil2.sys ( avcuwil2+b0e7 )

Followup: MachineOwner
---------

1: kd> !analyze -v
*************************************************************************** ****
* *
* Bugcheck Analysis *
* *
*************************************************************************** ****

BAD_POOL_CALLER (c2)
The current thread is making a bad pool request. Typically this is at a bad IRQL level or double freeing the same allocation, etc.
Arguments:
Arg1: 00000099, Attempt to free pool with invalid address (or corruption in pool header)
Arg2: 94540330, Address being freed
Arg3: 00000000, 0
Arg4: 00000000, 0

Debugging Details:
------------------


BUGCHECK_STR: 0xc2_99

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_RC

PROCESS_NAME: System

CURRENT_IRQL: 0

LOCK_ADDRESS: 81d2e020 -- (!locks 81d2e020)

Resource @ nt!PiEngineLock (0x81d2e020) Available

WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.


WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.

[svinyard]

Thanks for the scan. I have indeed completely removed the device and the drivers, but soon after a windows update in which the drivers are again downloaded from MS, things become immediately disquiet. I have even convinced Dell to provide a new mobo, so that is ruled out. It seems the device itself, in conjunction with the vista drivers, is just not agreeable to vista. I refuse to go down with this ship, so I have reverted back to MCE2005 (solid so far) until further notice. Maybe when SP1 comes out (beta now) I'll try it again.