Windows 7: BSOD while playing using computer, ntoskrnl.exe+7f1c0

I did a quick google search for Driver Sweeper and found this Guru3D - Driver Sweeper

Though it doesn't say that Intel drivers are supported. I also uninstalled the control center as a quick google shows that it's used for overclocking and viewing temperatures and whatnot.



Do you know how else I could go about removing the storage drivers? Could using Driver Fusion (used to remove display drivers previously) work?

Edit: Upon looking in Driver Fusion, the only intel drivers I see are the Intel Display and Chipset

The Guru3D version is a stripped down variation that caters specifically to certain devices (notably graphics cards). Driver Fusion apparently is the new full version, but I haven't tried it personally.

If you wish, you may attempt to do a manual removal or at least disable them. Start with Autoruns. In the Drivers tab there should be listed items called "iaStor". Uncheck (do not delete) these entries, then restart the PC. You may wanna create a system restore point prior for worst case scenarios, though typically if your system fails to reboot you can just go into Safe Mode and use Autoruns to re-enable em. Test stability of system afterwards.

I used Autoruns and disabled all entries beggining with "iaStor" (iaStor, iaStorA, iaStorF, iaStorV) and the computer bluescreened upon starting, but has been restored to a previous point (where intel control centre exsists, but I doubt that was the problem anyway)

I just want to ask another quick thing, when I installed my MOBO drivers (a bit ago) I got them from http://ee.gigabyte.com/products/page...v_10/download/ which now says it has a hotfix for the latest rapid storage technology (I dont have the latest, I'm still not sure if I have it)

Yet I came across this GIGABYTE - Motherboard - Socket 1155 - GA-Z77-D3H (rev. 1.1) which is the rev1.1 as opposed to the rev 1.0 of the first link, would downloading all the drivers of the 2nd link possibly hopefuly maybe fix the problems?

Depending on your own motherboard. You need to verify if your mobo is in fact rev 1.0 or 1.1 version, as this is referring to an actual hardware change and not some driver/software difference. If you find you do in fact have rev 1.1, you'll want to install BIOS and drivers catering only to that revision (not before uninstalling all drivers for rev 1.0).

After checking the box for my mobo, it says that its a rev 1.0.

So could redownloading the correct drivers again (aka: updating them) fix the problem? It's just that I'm somewhat worried that I may download the incorrect drivers. (example, VGA has 4 drivers available, all the same thing just different versions. As well as a couple different versions of Rapid Storage Technology which is both listed near the top and bottom of the downloads list.) And being on Australian internet, I cant really afford to keep downloading files of that size over and over as it stacks up and I prefer not having dial up speed until the month resets it.

So I guess what I'm asking is if you know what things from the first link I'll want to download, as I don't want to download things to fix the problem, but only make it worse.

So would you have any idea on which of the drivers I will want to download?

Urk, sorry, this passed under my radar.

Download the Rapid Storage with the hotfix, as well as the SATA preinstall driver if you do not have it already and you are using your motherboard's SATA connectors and not a storage controller (and you have BIOS SATA mode set to AHCI or RAID). Not sure why it repeats twice with different filesizes, just get both and start with the first one.

Get the Intel INF Installation, the audio, USB and LAN drivers.

Don't download any entry in the SATA/RAID section. Looks like older versions.

Make sure to make restore point prior to installing all these.

That's cool if it passed under your radar, there's many to help and I appreciate every bit of advice.

I'll try to get around downloading said drivers soon (when I'm not almost falling asleep and have time to muck around with them) so I'll keep you posted.

Thought I'd say something so you know I haven't fallen into a deep well.

After doing...well...nothing, I'm yet to experience a BSOD for quite a while. The world of Windows confuses me...