BSOD trouble

[Cinders_Knight]

Thanks for anytime spent looking at this.  I did my first build a year or two ago, and got bsod's on a fairly regular basis (sometimes after just a few moments others it would run for 24-48 hours without issue) and got lazy and just went back to using the laptop.  I've had some free time so decided to tinker with her a bit to see If I could fix the issue.  I just did a fresh format / re-install of the OS yesterday and have updated the drivers and am again getting the bsod's.   So here I am.

 

 

• OS - Windows 8.1
• x64
• What OS was originaly installed on the system?  Windows 8.1
• Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from a retailer)?  Full Retail
• Age of system (hardware)  - 2 years  (very low usage)
• Age of OS installation - have you re-installed the OS?  Yes
• CPU model  AMD 7870k black
• Video Card model  2x AMD Radeon HD 7700 Crossfired    
• MotherBoard - Gigabyte GA-f2a88x UP4 rev3
• Power Supply - Corsair CX750M
• System Manufacturer
• Exact model number (if OEM or laptop)
• Laptop or Desktop?   Desktop
  
   

I've uploaded the dump files to google drive - they should be accessible here.

I am having the same problem as described in here (spoilered below) about which I was unable to find a solution listed so I do not have a second zip file for the perfmon report.

Spoiler

On 7/9/2015 at 1:48 PM, Colt_0pz said:

it tells me "The operator or administrator has refused the request" and im on my admin account and i ran cmd as admin

Again thanks for any help offered,and if any additional information is needed from my end let me know and I'll do my best to get it over here.

[johnukguy]

Install Windows 10 or 7 is my honest advice as a last resort. Other than that, check that you don't have a lot of dust inside the case, or on the CPU cooler and test your RAM as that might also be a culprit here. You can also try upping the CPU voltage very slightly and see if that helps.

[iHDCool]

7 hours ago, johnukguy said:

Install Windows 10 or 7 is my honest advice as a last resort. Other than that, check that you don't have a lot of dust inside the case, or on the CPU cooler and test your RAM as that might also be a culprit here. You can also try upping the CPU voltage very slightly and see if that helps.

I don't think that upping the CPU voltage would help.

I've had a lot of problems with BSODs (Luckily now anymore)

Now what I suggest you doing is to search and download BlueScreenView from Nirsoft or w.e that is, it checks for the blue screens that happened lately and sometimes it can tell you what drive might be causing them. Most of the times, BSODs are caused by hardware failures or corrupt windows files. Last time I had a BSOD it was because my HDD started to fail. Anyways, after you check with blue screen view program, check the hard disk by CMD.prompt there's some cmd to use chkdsk /f or w.e it is (i forgot it atm), do a RAM test (there's also a program for this I think) and tell us how it goes. 

[Cinders_Knight]

20 hours ago, johnukguy said:

Install Windows 10 or 7 is my honest advice as a last resort. Other than that, check that you don't have a lot of dust inside the case, or on the CPU cooler and test your RAM as that might also be a culprit here. You can also try upping the CPU voltage very slightly and see if that helps.

If I can't find any other solutions I may change the version of windows - However my line of thinking was that by doing a fresh install I'd run down the chances of it being caused by an error in the windows files.  While the stock cooler isn't the best it is keeping temps in an acceptable range -  With little uptime on the machine the case has stayed pretty clean so far.  *bit about testing ram included below* I'm not at all familiar with manually adjusting the voltage on my CPU.  While overclocking is on the list for this machine, its something I need to learn, and was thinking would be best left to after I've already got the system in a stable state.
 

12 hours ago, iHDCool said:

I don't think that upping the CPU voltage would help.

I've had a lot of problems with BSODs (Luckily now anymore)

Now what I suggest you doing is to search and download BlueScreenView from Nirsoft or w.e that is, it checks for the blue screens that happened lately and sometimes it can tell you what drive might be causing them. Most of the times, BSODs are caused by hardware failures or corrupt windows files. Last time I had a BSOD it was because my HDD started to fail. Anyways, after you check with blue screen view program, check the hard disk by CMD.prompt there's some cmd to use chkdsk /f or w.e it is (i forgot it atm), do a RAM test (there's also a program for this I think) and tell us how it goes. 

I dove into the chkdsk as I'm about to head out for a while - will try to grab bluescreenview when I get back home for the day.

I was however very quickly reminded of a problem which plagued me the last time I attempted to troubleshoot this which is I don't think I've been able to get the system through a chkdsk without a bsod crash. Which then reboots the system - prompting it to run the chkdsk again.

-------

Home now and yup -  On restart it runs chkdsk but hits a bsod before completing it causing the system to restart and then running chkdsk again.  How can I cancel the chkdsk from running on startup?

[johnukguy]

When the disk check starts, there's usually a prompt to hit any key to cancel it.

[Cinders_Knight]

1 hour ago, johnukguy said:

When the disk check starts, there's usually a prompt to hit any key to cancel it.

Yup this ended up being the case, though it said that I'd have several seconds to do it the prompt itself was only up for a flash and after several times of furiously hitting keys I was able to get it to stop.

Have been thinking of other things I can try doing to whittle down the list of things a bit.  I'm currently running a Memtest, as well I updated the Bios to the most current non beta version. In the brief description this said that it was "Update APU AGESA code for Godavari support"  Which is the codename for the microarchitechture refresh implemented in the APU I have.  Fingers crossed that after I've got at least 10 passes in that I may found the issue has resolved itself.

Once memtest is done I'll add in a few more .dmp files.   I did also grab blue screen viewer - not quite sure how to interpret the data I see there though.

[johnukguy]

The BS viewer really has limited usefulness unfortunately. I do suspect though that it is a RAM issue.

[iHDCool]

7 hours ago, johnukguy said:

The BS viewer really has limited usefulness unfortunately. I do suspect though that it is a RAM issue.

It's a starter.. You can't just guess the problem of the guy's BSOD.... It can be most of his hardware or even software... that's where bluescreenview comes in handy.. 

[johnukguy]

Not really. Many BSOD error messages may for example indicate a file associated with a graphics card when in fact it's a RAM issue or a voltage/overheating issue.

[Cinders_Knight]

Gigabyte GA-f2a88x UP4  AMD 7870k  was having somewhat random, and frequent BSOD's mostly for Kernel_Security_Check_Failure and occasional irql_not_less_or_equal

As an update the board - rev. 3.0  came with version F4 of the bios - Version F7 was an "Update APU AGESA code for Godavari support"  after flashing bios up to F7 my system after about a week has not had any more bsod occurrences.  Considering it resolved for now .... hopefully forever =D