Windows 10: Random BSODs usbohci.sys

Hello EternalMuffin. That same thing happened to me while running version 5.01. It asks to press a button for multi core CPUs, I did and it froze. I ran it again without pressing anything and it started itself in a couple of seconds and ran with no problem. Is it normal for your CPU to reach that temp?

 

My CPU only reaches that temp when I'm playing a CPU intense game. Like when playing Ultra HD games


EDIT: When I first ran memtest I didn't press anything, the second time I did SMP and it worked fine. Here is a picture of the second memtest:

 

A revealing news that the RAM is not failing.

Now, it is usbohci that is failing.
Code: BugCheck D1, {28, 2, 1, fffff80137e2206e} Probably caused by : usbohci.sys ( usbohci!OHCI_PollIsoEndpoint+d2 ) Followup: MachineOwner ---------[/quote] The OHCI device is SB700 OHCI2, a component of AMD chipset. But there is no chipset deiver listed for download: GIGABYTE - Motherboard - Socket AM3+ - GA-970A-DS3P (rev. 1.0)
. The BIOS is the latest; too.

In this situation, I think it would be better to perform a clean install. Dont install any driver there other than the graphics driver, let windows update all the other drivers.

See how it goes. Let us know.

 

Okay, I have reset the computer. While it was resetting it crashed and then it wouldn't reinstall windows, so I had to put windows 10 on a USB and boot it from that. Right now windows is updating everything, even the graphics driver.

EDIT: It crashed, "IRQL_Not_Less_or_Equal"

 

Actually there were two BSODs as the reports say. The first one is 0x1A and the second one is 0xA. But you are reporting for only one BSOD; and there is only one dump in the zip.

The dump says ....
Code: BugCheck A, {bf7c4008, 2, 0, fffff802c1c24682} Probably caused by : PCIIDEX.SYS ( PCIIDEX!BmFlush+2c ) Followup: MachineOwner ---------[/quote] Code: 00 fffff802`c352b258 fffff802`c1ddf2e9 nt!KeBugCheckEx 01 fffff802`c352b260 fffff802`c1dddac7 nt!KiBugCheckDispatch+0x69 02 fffff802`c352b3a0 fffff802`c1c24682 nt!KiPageFault+0x247 03 fffff802`c352b530 fffff802`c1c23dc4 hal!HalpDmaFreeMapRegisters+0x1a 04 fffff802`c352b560 fffff802`c1c3a6ac hal!IoFreeMapRegistersV2+0x60 05 fffff802`c352b5a0 fffff800`b79911bc hal!HalPutScatterGatherList+0x18b6c 06 fffff802`c352b600 fffff800`b7afcf3f PCIIDEX!BmFlush+0x2c 07 fffff802`c352b630 fffff800`b7afcbbf ataport!IdeProcessCompletedRequests+0x14b 08 fffff802`c352b7f0 fffff802`c1ce0b60 ataport!IdePortCompletionDpc+0x18f 09 fffff802`c352b8c0 fffff802`c1ce0279 nt!KiExecuteAllDpcs+0x270 0a fffff802`c352ba10 fffff802`c1dd753a nt!KiRetireDpcList+0xe9 0b fffff802`c352bc60 00000000`00000000 nt!KiIdleLoop+0x5a[/quote] The failing module is the IDE mode storage controller driver. IDE mode is almost castoff nowadays. But what does this mean?

It may mean any of the following:

• A disk environment related issue. Either the SATA port is failing or the HDD itself.
• A bad sort of malware/rootkit. Did you format all the system partitions of the HDD (EFI, Recovery and C) before performing the clean install? If not, a malware infection from the previous installation will nicely be carried forward. The malware that makes ataport fail resides in the hidden system partitions, not in C.
• A failing motherboard. If there is no adequate cause of a BSOD with a system native driver flagged as failing, even just after a clean install, then the notion goes on it. But that is a notion, as we cannot test a motherboard.

What should do now .....

Check the disk environment .....

Check for some malware. Dont depend on your resident antivirus for that. Scan the system for possible virus infection with the following programs.

• Anti-rootkit utility TDSSKiller
• Windows Defender Offline

Let us know the situation upto these steps.