[Vexx109]

so i am having issues with BSOD
i am getting the stop code of:
0x000000c5 (0x00000000000008f9, 0x000000000000002, 0x00000000000000000, 0xfffff80003bfedd3)

i am using Bluescreenviewer and it tells me that it is the NTOSkrnl.exe that is bugging out the dump files are attatched

 

[Vexx109]

Re: BSOD

My system specs are:
CPU:Intel I2500k
Mobo: Gigabyte Z68A-D3H-B3
GPU: XFX HD radeon M/N: HD-487A-ZD
RAM: G.Skill Ripjaw 4x2 DDR3 1600
HDD: Seagate Barracuda Green 1.5TB

 

[VirGnarus]

Re: BSOD

Are these all occurring inside a VM? The reason I ask is that 3 of them report the Virtual Box Net Filter driver attempting to corrupt the Executive pool (in reality, they just are just referencing the same bad address erroneously). When DV was active, it caught your Etron USB 3.0 hub driver creating a scenario that would cause a deadlock (freezing up your system). This was initially created by it coming across a c0000001 error, which means "The requested operation was unsuccessful." I cannot determine what operation it was that failed with only a minidump.

Anyways, the Etron USB 3.0 hub is part of your motherboard. I see that the driver for it is dated from Feb 2011, so you'll want to check for both motherboard chipset drivers and any BIOS update as well. the VirtualBox net filter driver is dated from Nov 2011, which isn't that old, but check to make sure there's an update for VirtualBox. Otherwise, you may need to resort to another VM solution.

 

[Vexx109]

Re: BSOD

yea, the etron USB i updated. and fixed with a driver scan. i also uninstalled Virtual box which is what seemed to be causing my problem. thank you for the support =)

 

[VirGnarus]

Re: BSOD

Good to hear. Come back if you see it reoccurring.

Also, as a recommendation for the future, I assume when you say "driver scan" you mean you used a 3rd-party software to find and scan for updates for your drivers. These are never recommended, as there has been plenty of cases where not only do they "update" the driver with older versions, but also have updated them with drivers for other hardware. Your best option for finding updates in the future would be to simply find them yourself and manually install them yourself. That is the safest and surest manner which you can install drivers.

 

[Vexx109]

no, i used the stock "Update Device Drivers" that comes with windows. and yea, i try to stay away from anything like driver genius they have only caused me hell in the past T_T

 

[VirGnarus]

The "Update Device Drivers" that comes with Windows only searches through those drivers which are within Microsoft's own database of drivers. As such, it typically is not as up-to-date as from the original manufacturer or OEM's website (and, like the 3rd-party junk, I've occasionally had it install bad drivers for the hardware). Again, the manual method of finding and installation is preferred. But glad to see this one actually provided you an appropriate update.

Anyways, have a good one, mate!

 

[bat4]

Sorry to dig up an old thread. This is just to confirm, the Etron drivers below 0.101 are known to cause random BSOD even if you are not using the USB 3.0 ports.
Some links to similar issues:
Solved Random BSOD Driving me crazy! - Page 8 - Windows 7 Forums
[CRASH] Getting BSOD on new build!! HELP!

Now, I am wondering how is it possible to qualify as WHQL some drivers which are causing BSOD for so many users?

 

[VirGnarus]

Thanks for the update, I'll definitely keep this in mind in the future. As for the whole WHQL thing, I've always thought it more a certification to authenticate the driver. While it does involve a lot of QC work (hence the name), there's always going to be stuff out in the open that slips through lab testing.