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

[Balvedius]

Edit: Make that 2 BSOD's today

I bought each part of the computer separately so the warranties may vary.

This is a screenshot of the temps, the only real difference between what they are in that and after the computer being is use for a while is the graphics card may be around 40 degrees and the processor around 50.

 

[koolkat77]

Okay. Please upload the latest dmp files.

 

[Balvedius]

As requested

The last 3 or 4 are the most relevent

 

[koolkat77]

I see that one of the Gigabyte stuff is still there on your computer:

Start Menu\Programs\GIGABYTE	Public:Start Menu\Programs\GIGABYTE	Public

Weren't you able to uninstall it? I would suggest you to do a clean install once again to see if the BSOD-s are software related... Do not install any of the software that were pointed out on previous pages.

 

[Balvedius]

The destination which you have mentioned contains a shortcut called "@BIOS".

I am able to go into into the control panel and find "@BIOS" to remove it, however with that kind of a name I wasn't sure if uninstalling it would cause more problems.

Should I proceed in removing it?

 

[koolkat77]

The destination which you have mentioned contains a shortcut called "@BIOS".

I am able to go into into the control panel and find "@BIOS" to remove it, however with that kind of a name I wasn't sure if uninstalling it would cause more problems.

Should I proceed in removing it?

Yup.

 

[Balvedius]

Its been removed, I shall let you know if any further problems arise

 

[koolkat77]

Okay

BTW, Run the tools below and delete anything they find:

• Anti-rootkit utility TDSSKiller

ESET online scanner:

• Free Online Virus Scanner | ESET

 

[Balvedius]

Well, I've BSOD'd twice since then, so I've run both tools and they each haven't found anything.

I've changed something in my bios that was allowing my RAM to go at 1600Mhz (the setting was at "Profile 1", I believe I set it to the other value which is "disabled", could be wrong) (the RAM I ordered was 1600Mhz), so now it says the value is at 1300Mhz (may help, idk)

I'm just unsure why is it happening so much more frequently today (or at all). Our power did go out today due to lightning/thunder ect. causing the comp to shut down but that's all I can think of.

Seeing how another BSOD is imminent (that's just my guess based on today) would turning on Driver Verifier again and then sending the dmp file help?

Edit: Just to note, in my "add/remove programs" there is 1 other program under GIGABYTE (not listed under "All Programs/GIGABYTE") called "ON_OFF Charge B11.1102.1" which to my knowledge is to allow charging of USB devices when the computer is turned off. Could this also be a culprit?

 

[Vir Gnarus]

Yes, this is one of those gimmicky mobo utilities. You'll wanna remove it.

Did you have your system hooked up to a surge protector at the time of the power outage? If not, the PSU may have bugged out or the motherboard. Personally, I think the motherboard/PSU have been causing these problems the whole time.

Judging from the erratic BSOD behavior and the fact it's so prevalent, and considering we're dealing with new parts, it's evident we're dealing with a bad part or configuration. The behavior seems pretty iconic for a bad PSU/Mobo, but one cannot determine which without proper tools and testing procedures. Your best bet right now is to buy replacements and cross fingers.

 

[Balvedius]

I'm posting this in hopes that somehow the last 4 logs or so decide to say that "this driver is herpa derping" so I'll post the latest zip file.

The BSOD's seem to be far less random as I appear to get 1 every 4 days or so, but as mentioned previously, if I knew a better way of looking for the problem (other than BluescreenView (unless there's some better way in it to find the problem)) I also removed that ON_OFF CHARGE utility.

I also just went into the BIOS and loaded the default settings, but had to change something to AHCI from IDE or else I couldn't get past the windows logo.

 

[Balvedius]

An update: Using windows debugger, I looked through the dmp files and although the IMAGE_NAME all showed up with memory_corruption, the PROCESS_NAME would quite often show up with svchost.exe and the DEFAULT_BUCKET_ID as VISTA_DRIVER_FAULT.

Now from what I can tell, svchost.exe is something that potentially chews through your memory causing your computer to slow down, but I'm confused about the VISTA_DRIVER_FAULT part as I'm using Windows 7, could I have possibly downloaded the wrong driver sometime back?

I'll be turning on driver verifier again in hopes that I'll get a more details dmp to look at. But could svchost.exe be a cause of the BSOD?

 

[Balvedius]

More updates, since I had turned on DV I have BSOD'd twice, yet I dont think that the BSOD was able to finish as I was given no DMP file for the crash.

So I've turned it off and checked windows updates with the important updates being security updates and one called "nVidia - Graphics Adapter WDDM1.1" which I have heard I wouldn't want to download through windows updates (something about graphics stuff from windows updates I heard is a no no). However if the 44 optional updates, theres a large amount of "Update for Windows 7 for x64-based Systems" which I thought would have come with the service pack.

It may be obvious but could downloading these updates fix the problem? I'm trying to progress along by myself but I'm unsure about where to go.

 

[Vir Gnarus]

Svchost is just as its name implies, a service host. It is provided by Windows to host one or more services under its process environment. That's why often times you'll see more than one svchost process running. You can check which services are hosted by that particular service host by grabbing Process Explorer, then dbl-clicking the process and checking the Services tab.

As for DV, can you try to get DV running again and let it crash once more, and provide us details present on the bluescreen? We'll need the bugcheck code, the 4 parameters in the parentheses next to it, and the name of the driver it says may be causing it.

Have you done a memtest for 7+ hours, btw? You'll also want to do Prime95 Torture Test overnight on Blend settings, followed by another overnight run on Large FFTs setting, regardless if the previous one crashed/failed or not. If Blend is good but Large FFTs fails/crashes, RAM-to-CPU crosstalk is bad; if vice versa, internal CPU caches are bad; if both fail or crash, there is a hardware problem, but it cannot be determined. Most likely it'll be RAM, Mobo, CPU or PSU that's causing it.

Because these crashes involve operations with PFNs, It may be a problem with RAM or disk we're dealing with. With the disk, if you have an SSD I'll assume you installed the firmware update for it as well as updates for your BIOS and motherboard software (sometimes it's best to remove Intel's storage drivers cause they can conflict). Some SSDs like Samsung have software that will test its integrity. Otherwise, you'll have to test stability by removing the SSD. If you have just HDD(s), you can test with Seatools. I recommend running all tests (except Advanced). This is not a 100% guaranteed diagnosis of your drive, so it can still be bad if all tests pass, but it's very uncommon.

 

[Balvedius]

Hello Vir, I had just recently turned off DV and as I was just about to play a game I got a BSOD, this time however the BSOD finished and gave me a .dmp file. (which says in it "DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT" which is confusing as I appear to be way over my head)

To answer your questions, yes I have previously ran a few memtests, each of them for 8 passes and there were 0 errors found. I do not have an SSD and am using a single HDD.

Also as mentioned a while ago I hadn't been able to download Prime95 for some odd reason as it would download a quarter of it, then stop.

I've changed the settings so that it automatically doesn't restart when I get a BSOD and now DV is enabled again, but I also noticed that the debugging information was on "Kernel memory dump". Would changing it to "Small memory dump" possibly help?

 

[Vir Gnarus]

It automatically creates small dumps regardless of setting, so it's advised to keep it on kernel dump in case we need one of the big dump files. I'm afraid these dump files aren't going to help us much without Driver Verifier getting involved. Once you turn it on and can confirm that it is in fact 'running', then next crash we get we'll need to see either the dump file or at least what the blue screen shows up.

The Prime95 issue is pretty weird, have you tried a mirror site somewhere? There's no reason why the program should fail to download midway regardless of where you download it.

 

[Balvedius]

Ok, so DV was turned on and I got a BSOD. I let the number at the bottom (cant remember what it was) reach 100, which I can only assume meant it was done gathering the information needed for the .dmp file. Yet when I checked to find the .dmp file it doesnt appear to have created one, which seems odd. The past few times DV has been running and I got a BSOD, no dump file was created, yet it was created fine when DV is turned off. Maybe it's because I installed Windows Debugger and thats somehow changed a setting somewhere? idk...

I did however manage to write everything that appeared on the BSOD down on some paper, it went as follows.
It was a: Stop 0x0A
With (0x00005A8003C02B78) (0x0 -insert many 0's- 2) (0x0 -insert many 0's- 0) (0xFFFFF80003105EC5)
And it didn't say what driver it thought could be causing it.

Edit: Turns out it did create the dump file, and since them I turned DV off and I BSOD'd again, I'll attach the ZIP if you want it.

 

[Vir Gnarus]

There were some verifier-enabled crashes present here, but unfortunately they all say the same thing. It seems too conspicuously consistent to be hardware failure, but if Driver Verifier isn't catching it and it is in fact a bad driver, than it's one that is getting loaded later on instead of at Windows startup (since DV only lists drivers currently loaded at the time to check on).

I still recommend you run through all those Seatools tests, and if you haven't already, do a CHKDSK /R on all your drives, including external if present. Make sure to set it to detect bad sectors.

Any update on the Prime95 thing, btw?

As for drivers, either you have some sort of nasty rootkit infection (check, not fix, with Kaspersky's TDSSKiller), you got screwy storage drivers (e.g. you may wanna update/remove/reinstall intel rapid storage), or you just have a bad storage device somewhere.

 

[Balvedius]

Well Prime95 decided it wanted to download, so I'll ask this.

The link for the Prime95 tutorial given earlier on the the thread says to run Prime95 for 2 hours, yet you say to do an overnight run of it. Would the 2 hours be adequate?

Also I ran TDSSKiller and found nothing. And if I recall right, I have already done a chkdsk a couple of times.

As for intel rapid storage, in Add/Remove programs it isn't listed as I believe that I had previously removed it as per suggestion of someone in this thread. The only intel things listed are: "Intel Control Center" "Intel Management Engine Components" and "Intel USB 3.0 eXtensible Host Controller Driver"

 

[Vir Gnarus]

Overnight is recommended since it's necessary to reflect long-term usage of the CPU. Also, it typically reflects the instability of the system. If the system BSODs frequently and the CPU is suspect, then often when Prime95 is used it'll error in the first couple hours (sometimes instantly!). If BSODs are experienced less frequently then Prime95 may need to take several hours before an error may pop up.

About the rapid storage drivers, when did you uninstall this? Because I still see them listed as being loaded. In some cases drivers like these uninstall poorly due to buggy uninstallers, which often Driver Sweeper (free) does a good job cleaning up afterwards. See if that'll help take care of em. Also, I think the Intel Control Center may have these drivers built in, but that's just a guess.