New
#11
Ok got that going. Ill give it another go when I can and see if i can recreate the issue again.
Ok got that going. Ill give it another go when I can and see if i can recreate the issue again.
got the drivers updated and gave it a couple days. Just now got 2 more of the same error. uploading new logs
As usual, USB OHCI has something to do with your BSODs.
Here are your controllers: All AMD Chipset.Code:BugCheck D1, {124, 2, 1, fffff880056adcec} Probably caused by : usbohci.sys ( usbohci!OHCI_ProcessDoneIsoTd+30 ) Followup: MachineOwner ---------
No code has to be inserted here.
Descriptions here:
PCI\VEN_1002&DEV_4397 | vendev.org
PCI\VEN_1002&DEV_4398 | vendev.org
PCI\VEN_1002&DEV_4399 | vendev.org
Upload the list of all the third party drivers Using NirSoft DriverView :
- Download and execute Driverview
- View > Hide Microsoft Drivers
- Edit > Select all
- File > Save Selected Items
- In the Save dialog, Set the path to desktop, Put "Driverview" in the name field, and save.
- Zip the .txt file and upload it.
It may give us a ray of light here, at least we can hope.
ok uploaded driverview txt.
wonder if it might be a short in the motherboard itself and needs to be replaced. And if so, i dont know if i should go with a different board altogether or just replace with the same one.
So this is the driver controlling your USBs.
And it is a part of the chipset driver. Description here: Driver Reference Table - usbfilter.sysCode:================================================== Driver Name : usbfilter.sys Address : 0x053CE000 End Address : 0x053DF000 Size : 0x00011000 Load Count : 1 Index : 86 File Type : System Driver Description : AMD USB Filter Driver Version : 2.0.10.273 Company : Advanced Micro Devices Product Name : AMD USB Filter Driver Modified Date : N/A Created Date : N/A Filename : C:\Windows\system32\DRIVERS\usbfilter.sys File Attributes : Service Name : usbfilter Service Display Name: AMD USB Filter Driver ==================================================
At this point of time, I would suggest you to go for a Clean Reinstall - Factory OEM Windows 7 with the up-to-date chipset drive.
If the issue persists, we may narrow it down to a motherboard failure; but not before a clean reinstall.
Gonna go with a new board. Got 2 errors after clean install. Great excuse to by a new 8core cpu