Need Urgent BSOD Help

[ThaneMartin4]

My computer has been spouting BSODs for the past week now, at seemingly random times, and for random reasons. At first they didn't affect the computer, but now winload.exe missing. I used my Windows 8.1 USB and went back to a previous state (THANK GOODNESS FOR AVAST!!!!), with it now working (seemingly) normal. I am writing this in desperation, so ANY help is greatly appreciated! Uploaded with this is the minidump file created by the original BSOD. (All later ones were lost in the rollback)
Thanks!

 

SPECS: 

Pentium G3258 @4.0GHz 1.12v (Seemingly stable, took 4 hours in Prime95 not going above 70-75 degrees)

R9 270 @ 955MHz Core 1400 Memory (Stable through all tests)

8Gb of RAM (New DIMM installed recently, shortly before BSOD, any reccomended tests would be greatly appreciated)

H81M-P33 Most recent BIOS and all drivers and up to date

550 watt PSU (If that may be causing the issue)

 

P.S The minidump seems to think that the error was caused by Intel, although it didn't elaborate due to me not having the correct symbols (not without a lack of trying)

[STRMfrmXMN]

My computer has been spouting BSODs for the past week now, at seemingly random times, and for random reasons. At first they didn't affect the computer, but now winload.exe missing. I used my Windows 8.1 USB and went back to a previous state (THANK GOODNESS FOR AVAST!!!!), with it now working (seemingly) normal. I am writing this in desperation, so ANY help is greatly appreciated! Uploaded with this is the minidump file created by the original BSOD. (All later ones were lost in the rollback)

Thanks!

 

SPECS: 

Pentium G3258 @4.0GHz 1.12v (Seemingly stable, took 4 hours in Prime95 not going above 70-75 degrees)

R9 270 @ 955MHz Core 1400 Memory (Stable through all tests)

8Gb of RAM (New DIMM installed recently, shortly before BSOD, any reccomended tests would be greatly appreciated)

H81M-P33 Most recent BIOS and all drivers and up to date

550 watt PSU (If that may be causing the issue)

 

P.S The minidump seems to think that the error was caused by Intel, although it didn't elaborate due to me not having the correct symbols (not without a lack of trying)

@ionbasa knows many things. I'll tag him.

 

Have you done all Windows updates? I know Haswell compatibility on Windows 7 was established through an update.

[evilarceus]

Try cleaning your PC with CCleaner or MalwareBytes.

 

Also, when has this started happening? If it's Intel, my only trace would be this update from Microsoft: https://support.microsoft.com/en-us/kb/3064209

[ThaneMartin4]

I take it that the minidump was not uploaded. If it is allowed I may be able to use dropbox or something. Also, I had no idea that avast had that backup thing installed. Is the data just written to the drive, or is it cached?

[ionbasa]

@ionbasa knows many things. I'll tag him.

 

Have you done all Windows updates. I know Haswell compatibility on Windows 7 was established through an update.

@STRMfrmXMN : Yes, thanks for tagging me.

 

I take it that the minidump was not uploaded. If it is allowed I may be able to use dropbox or something. Also, I had no idea that avast had that backup thing installed. Is the data just written to the drive, or is it cached?

No it wasn't. Could you please post the minidump. I'll run it through the Windbg.

[ThaneMartin4]

I am not sure if this is good or bad news, but things took a turn for the worse overnight, to the point where I could not even use my computer, even to the point of not being able to reset windows because the drive was locked. I have since reverted to before this was started, and no crashes have occurred since. If you REALLY want the minidump I can get it back, although it would be annoying. Also, I did previously run the minidump through windbg and I found that the error was in my CPU, although I didn't have the correct symbols so it could not elaborate.

Thanks for all of your help anyways!

[ionbasa]

I am not sure if this is good or bad news, but things took a turn for the worse overnight, to the point where I could not even use my computer, even to the point of not being able to reset windows because the drive was locked. I have since reverted to before this was started, and no crashes have occurred since. If you REALLY want the minidump I can get it back, although it would be annoying. Also, I did previously run the minidump through windbg and I found that the error was in my CPU, although I didn't have the correct symbols so it could not elaborate.

Thanks for all of your help anyways!

If issues still arise, please post back with whatever minidump files you have. 

 

Was the missing symbol related to Intel iGPU or for the CPU? If you know your error was somehow caused by the CPU, I would recommend checking your overclock multiplier/bus speed/voltage. You mentioned you added more RAM recently. Depending of the DIMM and channel config, it could be an unstable overclock/bus issues.

[ThaneMartin4]

If issues still arise, please post back with whatever minidump files you have. 

 

Was the missing symbol related to Intel iGPU or for the CPU? If you know your error was somehow caused by the CPU, I would recommend checking your overclock multiplier/bus speed/voltage. You mentioned you added more RAM recently. Depending of the DIMM and channel config, it could be an unstable overclock/bus issues.

I think that it was because of my overclock, which strangely was running fine with stable temperatures prior. 4.0GHz 1.12v at around 75C when testing using prime 95. With no overclock now, it is running fine.