At a loss... =(, bluescreens after multiple upgrades...

Randy has just requested I find likes to the latest AMD Chipset drivers and they can be grabber from here.

And the realtek driver for your network adapter should be from here Realtek
Whenever your MoBo manufacturer seems to have older drivers, always try the actual device manufacturer's website. Actually that should normally be your first go to spot.

Hi, Randy.

Good news:

My PC seems to be running more stable. I'm not getting bsod as often...

Bad news:

I just got bsod'd again. Here is my most recent dump.

And I'm going to uninstall my realtek and amd driver and update with the new ones directly from the manufacturers website. I'll update this again when I receive another bsod.

I have a question:

I was wondering if I need the AMD Catalyst installed on my pc? It appears the AMD Catalyst is a driver for my onboard ATi graphics card. The thing is, I'm not using my onboard graphics card because I'm using an nVidia in my PCI-e slot.

Is it possible that the AMD Catalyst driver is somehow conflicting with my nVidia card? or is that not possible?

Thanks.

Originally Posted by Lisa Huang

I have a question:

I was wondering if I need the AMD Catalyst installed on my pc? It appears the AMD Catalyst is a driver for my onboard ATi graphics card. The thing is, I'm not using my onboard graphics card because I'm using an nVidia in my PCI-e slot.

Is it possible that the AMD Catalyst driver is somehow conflicting with my nVidia card? or is that not possible?

Thanks.

Not exactly sure what you are talking about here, but if you are referrencing the Catalyst Installer, which is part of the package from the AMD link that Rich (nmsuk) linked above, don't worry about it. It's just the installer interface go give you something pretty to look at while the chipset drivers are being installed. It is not going to install drivers for and ATI video card that you don't have enabled.
Go ahead and get your chipset drivers installed because you are still getting;

Code:

BugCheck 1E, {0, 0, 0, 0}
Probably caused by : usbohci.sys ( usbohci!OHCI_ProcessDoneAsyncTd+24 )
KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

Which is likely linked to this;

Code:

fffff880`02ffb0f8  fffff880`045dc1f4Unable to load image usbfilter.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for usbfilter.sys
*** ERROR: Module load completed but symbols could not be loaded for usbfilter.sys
 usbfilter+0x21f4

usbfilter.sys AMD USB Filter Driver
Which is likely linked to your chipset driver

Bsod again... twice. =(

1) NTFS_FILE_SYSTEM

and

2) QUOTA_UNDERFLOW

Minidumps attached below.

Time to beat on your hard drive (system drive) for a while. (Back up critical data first)
Remove or otherwise physically disable / disconnect any hard disk other than the Operating System disk. USB, FireWire, eSATA, (spinners, or Solid State of any kind)
Launch an elevated command prompt and type
ChkDsk C: /R
Answer yes (Y) when prompted and reboot.
Let it finish all five states and see what that produces in the way of worthwhile information.
Check with your Hard Drive manufacturer's website and obtain their vendor specific proprietary disk diagnostic utility and use that to perform more extensive / exhaustive (whatever they call it) tests on the drive and see if that finds anything of value.

Hi, Randy!

I bet you're waiting on this update, huh? :P

Well I just wanted to say that I've successfully self diagnosed my BSOD problem. It took a lot of hard work...., countless hours of scouring the internet for information... and a lot of trial and error... but I believe my system to be completely stable for the time being.(Been running it for 24 hours, no bsod)


First things first...
After the last advice you gave me about running a HD scan, I tried CHKDSK and the Seagate HD tool and I had received no errors. I was gonna come back and ask you what to do next but I decided it would be more efficient to take matters in to my own hands...

So...

I downloaded Windows Debugger. I started researching on how to use it and looked back on my prevous minidumps. I tried finding a solution to my usbohci.sys BSOD but kept hitting a wall. Every thread I found on the internet with that same problem was unsolved. I called my friend up and told him to bring his copy of Windows 7 over so I could try a fresh install again. I reformatted my PC with his copy and after Windows was done installing, the first thing I did was disable all windows updates, then, downloaded the AMD chipset driver directly from the AMD website.

Next, I downloaded my sound card driver(VIA Audio), network interface card driver(Realtek) andlastly my graphics driver all directly from their own websites. Keep in mind, these are all the latest drivers. After rebooting up my pc, I downloaded all the important and recommended windows update excluding the drivers that windows update wanted to install i.e ATK0110 from asus and my mouse, keyboard USB drivers.

After the windows updates, I installed my Microsoft sidewinder keyboard and Razor Lachesis mouse USB drivers directly from their website.

I rebooted my pc, used it for a while and still was receiving BSODS. I then downloaded Windows debugger and looked at the most recent minidump....

This time however, it wasn't the same bsod I was getting before. I was getting new ones like Serial.sys and Usbccgp.sys

So I thought to myself: "Well I'm doing something right because those are different bsods! I'm going somewhere."

So I looked up tutorials on how to use Driver Verifier to troubleshoot incompatible drivers. I loaded verifier and checked all third party drivers upon start up. Rebooted my PC and right when after I logged in to windows.... BAM! I got hit with the bluescreen... this time however, it blamed Lachesis.sys

Odd?I knew right away that was my mouse driver so I rebooted in safemode and uninstalled it. I rebooted back in normal mode and was able to get in. Since I had verifier on, I was confident in my ability to troubleshoot any new bsod that would come up. I kept verifier on and was playing a game, a few hours later I got hit with another BSOD.Verifier identified the problem as Afd.sys

I googled Afd.sys and found another tech support forum where a person was also having trouble with this bsod. I then found out that Afd.sys is a windows component that deals with networking and if you are receiving this bsod then most likely it is not Afd.sys but the driver that goes through the networking Afd.sys which would be your network interface driver: In my case, Realtek.

So I thought to myself, "How could this be the case? I have the latest realtek driver from their website..." and then I remember reading an article somewhere that says sometimes motherboard manufacturers will modify or change their drivers they receive from from companies in order to enhance performance and stability.

I went straight to Asus and downloaded the old 2009 realtek network driver off their website, installed it, and I have not received a single bsod within the last 24 hours. Keep in mind this is with verifier still on :P

So to conclude this:

- Latest chipset driver installed
- Latest graphics driver installed
- Uninstalled usb mouse driver
- Latest keyboard driver installed
- Latest audio driver installed
- Old manufacturer network driver installed

I guess we can say that driver updating really is a double edged sword because it can either improve stability or cause incredible instability. The only problem I have now is that after I stopped receiving bsods, I am now experiencing sluggish moments where my audio makes a loud buzzing noise and skips like it's going to bluescreen but doesn't. It also produces high CPU usage and I found the culprit to be audio endpoint builder from looking at my resource monitor but can't find a solution at the moment. :\

But, yeah! Thank you for sticking with me through this and for anyone else who is reading this in the future:

MAKE SURE YOU INSTALL YOUR MOBO DRIVERS FIRST AND THEN GRADUALLY UPDATE ONLY IF YOU NEED TO. Also, using windows debugger and verifier helps a whole lot!

WOW!
Thanks for the followup and I'm glad to hear that you have managed to resolve your problem. An excellent job of self troubleshooting, congratulations.
It's particularly great that you have the self confidence and the skill set to not only install windbg and take a look at your own dumps but that you decided to incorporate DV into your diagnosis.
Hope to continue to see you around the forum. You can hang out in the BSOD sub-forum and help resolve some crash dumps with your new found skills.
Best wishes and continued crash free operation.
Randy

LOL! Thanks, Randy. :P

But I'm still a novice and nowhere near to being a tech support expert, yet.

However, I think I'm starting to develop a soft spot for troubleshooting