BSOD crash when using Media Centre on Windows 7 64bit

Furby42

New member
Local time
2:39 PM
Messages
2
I'm currently using a new system bought last month. I hadn't had any issues so far, however upon installing a tv tuner pci card and using media centre, when I clicked to close media centre I received a bluescreen crash.

This has now happened several times, but only when using media centre, and as far as Im aware it is triggered only by attempting to close it (sometimes it does close without any problems).
I have limited knowledge regarding toubleshooting in this area, and after doing the basics (checking all obvious drivers are up-to-date, running memory and hard drive checks, and taking a look at the minidump file), I am stuck for what to do.

I would greatly appreciate any help!
 

My Computer My Computer

OS
Windows 7 (64 bit)
Is this a USB tuner card? If so I'd suspect an incompatibility between the device/drivers and Windows.
What is the exact make and model of the card? (see below if it was picked up by the dump file analysis)

The single memory dump file blames usbport.sys - a Windows file.
Windows files aren't usually to blame (they're 4th in my list of possibilities - 3rd party drivers, incompatibilities, hardware issues, Windows issues) so we look at them last.
Since 3rd party drivers are the most common reason - and the STOP 0xA error that you got is most often caused by 3rd party drivers - we need a tool to force the 3rd party driver to reveal itself (if possible).

That tool is Driver Verifier. Please run it according to these directions:
Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:
Code:
Delete these registry keys (works in XP, Vista, Win7):
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel

More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users

Interestingly, the only older driver that revealed itself in the memory dump is AF15BDA.sys (Tue Nov 20 05:19:55 2007) - a component of the DigitalNow TinyTwin DVB-T Receiver. Please update that driver from the manufacturer's website immediately: DigitalNow

Summary of the BSOD:
Code:
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sun Jun 13 08:05:26.024 2010 (UTC - 4:00)
System Uptime: 0 days 2:35:36.085
BugCheck A, {fffff8800d3c4ff8, 2, 1, fffff8000361702e}
Probably caused by : USBPORT.SYS ( USBPORT!USBPORT_Core_iCompleteDoneTransfer+45f )
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
 

My Computer My Computer

Computer Manufacturer/Model Number
Home built (x64), Lenovo x61s Tablet, Samsung Netbook
OS
Win7 x64 + x86
CPU
Intel i7 920, other Intel chips, and the Atom in the netbook
Motherboard
Asus P6T Deluxe
Memory
12 gB; 4 gB Lenovo; 1 gB Samsung netbook
Graphics Card(s)
ATI 4870
Sound Card
Yes, I have one of these
Monitor(s) Displays
32" Sharp Aquos TV
Screen Resolution
800x600 - I have vision issues
Hard Drives
4 - 150 gB Velociraptors in RAID 5
Promise controller
PSU
1000 watt (can't recall the brand)
Case
Antec 300
Cooling
Big honking cooler that was rated highly at Toms Hardware
Keyboard
Microsoft Natural
Mouse
Logitech Trackman
Internet Speed
Cable
Other Info
GeekSquad UPS
CyberPower UPS
DLink DNS-323 NAS (2 tB)
Netgear wireless router as an access point
Netgear wired router FSV-318
Home network consists of
4 desktop computers (2 Vista, 2 Win7)
1 netbook (Win7)
4 laptop computers (XP, 2-Vista, Win7)
Wii and XBox 360
Hi there, thanks very much for your help.
Ive gone through checking, deleting and updating all old drivers, as well as running chkdsk, and this seems to have solved the problem.

Ive opened and closed media centre as well as using my computer normally in order to try and crash it, and havent had a blue screen thus far, so Im thinking it was dodgey drivers that were doing, so hopefully you wont be hearing from me again.

Thanks once more for the help!!!!
 

My Computer My Computer

OS
Windows 7 (64 bit)
Back
Top