BSOD while running Firefox(?), BCCode:10d

[calebefuller]

I've been running into a bluescreen roughly 20-30 minutes into every Windows 7 session - as far as I can tell, the error code indicates some kind of driver conflict - if someone could take a look at the memory dump for me and confirm that this is the case, and possibly tell me what to do to fix it or which driver to roll back, I'd appreciate it. Attached are the two most recent memory dump files, and the xml documents windows generated with those two crashes. I'm sorry to bother anyone, I'm just at my wits end, and apparently all my computer savvy from 10 years ago amounts to a hill of beans now. Thanks for any replies.

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 1033

Additional information about the problem:
BCCode: 10d
BCP1: 00000005
BCP2: 00000000
BCP3: 00001024
BCP4: 8512B860
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

This message has been identical across all the crashes, so apparently I only have one problem that's been causing this trouble.

 

[zigzag3143]

We do need the DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.

If you are overclocking STOP



You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.

To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

The procedure:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.
*If the files are too large please upload them to a file sharing service like "Rapidshare" and put a link to them in your reply.

To ensure minidumps are enabled:

* Go to Start, in the Search Box type: sysdm.cpl, press Enter.
* Under the Advanced tab, click on the Startup and Recovery Settings... button.
* Ensure that Automatically restart is unchecked.
* Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
* Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
* OK your way out.
* Reboot if changes have been made.

 

[calebefuller]

Sorry about that

Apologies - I didn't realize that the files hadn't attached with the initial post. And I don't overclock, unless my brother set it up at some point. Thanks for the advice, though. Now attached are the 3 latest dump files and the sysdata file which generated with one of the crashes.

And thanks for the tip on Safe Mode, as well, it hasn't crashed as such yet. Also I've already ran a ram check and an updated Norton scan, so with any luck, it's not viral or physical defect.

 

[zigzag3143]

A couple of issues


These crashes were Related to xusb21.sys Windows Common Controller from Microsoft. Upgrading to SP-1 should fix this issue. One item of note. The date on this file is different than the OS files and may be malware so I suggest you run malwarebytes and then update to sp-1

Please download the free version of Malwarebytes.
Update it immediately.
Do a full system scan
Let us know the results at the end.

Malwarebytes : Download free malware, virus and spyware tools to get your computer back in shape!


Please run the System Update Readiness Tool (SURT) and then update to SP-1


32 Bit

Download: System Update Readiness Tool for Windows 7 (KB947821) [February 2012] - Microsoft Download Center - Download Details

64 Bit

Download: System Update Readiness Tool for Windows 7 for x64-based Systems (KB947821) [February 2012] - Microsoft Download Center - Download Details


Now update to SP-1

Learn how to install Windows 7 Service Pack 1 (SP1)



This driver needs updating.

Related to MRESP50.SYS PCAUSA NDIS 5.0 SPR Protocol Driver from Printing Communications Assoc., Inc.


Other old drivers needing updating

timntr.sys    8/29/2007 8:13:12 AM        0x8938b000    0x893f5380    0x0006a380    0x46d562d8                        
tifsfilt.sys    8/29/2007 8:37:17 AM        0x8a875000    0x8a87e340    0x00009340    0x46d5687d                        
tdrpman.sys    11/12/2007 9:35:28 AM        0x89468000    0x894c0540    0x00058540    0x473856a0                        
snapman.sys    11/22/2007 4:19:58 AM        0x894c9000    0x894e7a60    0x0001ea60    0x47453bae                        
nvm62x32.sys    10/17/2008 5:00:39 PM        0x8f03a000    0x8f08ec80    0x00054c80    0x48f8fcf7                        
mcdbus.sys    2/24/2009 6:42:13 AM        0x8f167000    0x8f183800    0x0001c800    0x49a3cf05                        
lirsgt.sys    3/7/2009 11:17:27 AM        0x8a815000    0x8a819880    0x00004880    0x49b29007

How To Find Drivers:

- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

- - The most common drivers are listed on this page: Driver Reference Driver Reference
Driver Reference Table

 

[calebefuller]

Do I need to uninstall other antiviral software to avoid compatibility problems or overlap?

 

[calebefuller]

Guess not - it didn't detect any of my other spyware or antiviral software as conflicts. And mother of pearl, it looks like somebody's been playing with porn or p2p on my computer. Attached is the antivirus file you requested, and thank you, by the way - that's a whole mess of infections that my copy of Norton didn't.

 

[calebefuller]

Okay, I *think* my problem might be solved. The driver you specified is responsible for handling Xbox 360 remotes, and low and behold, I plugged one in Saturday to play some old school Halo. I updated it, and now Windows 7 appears to be running as well as ever. I'm going to go ahead and update the drivers you listed, and thanks a lot ZigZag - this worked way better than throwing the whole thing out a window. That was solution number 2. Have a good night.

 

[zigzag3143]

Okay, I *think* my problem might be solved. The driver you specified is responsible for handling Xbox 360 remotes, and low and behold, I plugged one in Saturday to play some old school Halo. I updated it, and now Windows 7 appears to be running as well as ever. I'm going to go ahead and update the drivers you listed, and thanks a lot ZigZag - this worked way better than throwing the whole thing out a window. That was solution number 2. Have a good night.

Im glad you are working and fingers crossed that is the issue. It was actually you that did the heavy lifting.