Timed BSOD with Crashing; Generic B-Code

Paliris

Honorable
Apr 22, 2013
2
0
10,510
Specs:
CPU: AMD FX-8120 8-Core Black Edition FD8120FRGUBOX
Mobo: GIGABYTE GA-990FXA-UD3
RAM: Corsair XMS3 4 GB *4
GPU's: SAPPHIRE AMD Radeon HD 6870 1GB *2 (Crossfire)
HDD's: Crucial m4 64GB (C: )
OCZ Technology 256GB Vertex 4 (Games)
Seagate Barracuda 2 TB (Everything Else)
PSU: Corsair 850W
OS: Windows 7 Home Premium SP 1

BCode: F4 (NDIS_INTERNAL_ERROR) (very rare :( )
0x0000000000000003
0xFFFFFA800AE7FB30
0xFFFFFA800Ae7FE10
0xFFFFF80003594350

I've been having trouble over the past few days with BSOD'ing and the accompanying crash/restart.
I frequently leave my computer on overnight, and have never had a problem, until I woke up a few days ago to a BSOD. I thought it was no big deal, but it turned out that I needed to boot windows from disk and do a system restore to a previous update.
I thought I was in the clear until it happened again about an hour after I rebooted... and then the hour after that, and the hour after that. It's not exactly 60 minutes, but close enough every time to be somewhat suspicious. I should note that it didn't require me to boot from disk again, just that first time.

The problem seems to occur regardless of what is going on; high-end gaming results in the same error as playing free cell for an hour, or watching a video. (That said, the result of using the internet or playing a game after the hour tends to be a crash, while watching a video tends to BSOD).

My temps on my CPU rarely top 40, GPU rarely 60, so I highly doubt it is a temperature problem.
I have already run anti-virus on all of my drives using both MBAM and MSE, which was my first inclination, as I haven't added any new software or hardware to my knowledge in a while before the event, although I am not saying driver conflict/failure is a non-issue. Nothing popped up.
Although memtest showed 3 errors (all within the block move checker) with 7 passes, it turned out to be nothing (with much further testing), simply slot 3 generating the errors regardless of the stick of RAM in it. Leaving nothing in the slot changed nothing. Although I wouldn't be shocked to find out I have bad memory, I decided this wasn't causing my errors. The event viewer shows essentially nothing of note failing at the hour mark, and my drivers are generally up to date. I've run chkdsk with no errors, and my PSU is good; I've no reason to suspect my video cards.

For whatever reason, these BSOD's aren't generating minidumps or MEMORY.DMP files, but I was able to generate a minidump when I intentionally caused a BSOD using driver sweeper, which I can link to if someone says it is useful (using bluescreenview, it said usbport.sys caused the crash).

If anyone has any advice on a direction to go, or a piece of hardware I should investigate more thoroughly, I would be most appreciative to hear it.
 

random stalker

Honorable
Feb 3, 2013
764
0
11,360
dunno... I bet my 7 cents on a disk failure /the usual cause of f4/, and another 3 at bad drivers /the usual cause for system screwing up/...
1. I'd run chkcsk from recovery console: chkdsk /f /r
2. I'd check for any drivers that had been updated lately and reinstall them...