Multiple BSODs

[Dr. Xeno Pootis]

Since 7/15/16 I've been having multiple BSODs and I can't seem to find out what is the problem. 

 

I have Windows 10 Pro 64-bit, my PC is about 4 months old now, I have not tried to reinstall Windows, and my specs are:

• i5-6600k 4.5 GHz
• ASUS Z170-A
• Corsair Vengeance LPX DDR4-2400 16 GB
• XFX R9 390X
• 850 EVO 500 GB SSD
• WD Blue 1 TB HDD
• EVGA GS 650w PSU

Thanks in advance.

Dump Files here: https://drive.google.com/file/d/0B8bdN8W0NxRjaEFzdHh4MG5VVlU/view?usp=sharing

[Q..]

Does it happen under system load?

[Dr. Xeno Pootis]

2 minutes ago, Q.. said:

Does it happen under system load?

It has been happening during games, where my GPU was on 100% Load with 80c

Most notably, Planetside 2

[Brian Furious]

It might be the power supply. 

 

Try to run the CPU at stock speed and see if the system crashes again.

[Q..]

PSU whould b my guess.

[Dr. Xeno Pootis]

Ok I made my CPU run at stock speed, I'll check back to see if it BSODs

[pwn_intended]

Sounds either like unstable OC or possibly a faulty PSU. Try toning down the cpu/gpu clocks a little before committing to a new psu.

[Dr. Xeno Pootis]

Ok, I had my first BSOD with CPU running at stock speed.

It said Critical Structure Corruption (win32k.sys)

Dump file here: https://drive.google.com/file/d/0B8bdN8W0NxRjR19td2MwdGNrWlk/view?usp=sharing

[Captain_WD]

11 hours ago, Dr. Xeno Pootis said:

~snip~

Hey there

 

I'm sorry to hear about the BSOD issues. Could you share a screenshot of the BSOD with the code? 

If this happens under heavy GPU load I would try running a stress test to see if the same BSOD occurs.

Try resetting your BIOS and bringing all your speeds to stock ones, run the system in safe mode and then try forcing the GPU to 100% load and see if the BSOD occurs again.

 

I'd also try running some diagnostic tests on the storage devices just to be on the safe side that your data is safe. There are diagnostic tools available on the manufacturers' websites. Check if the drives pass the tests. For the WD Blue drive that would be WD Data Lifeguard Diagnostic.  

 

Post back if you have any questions! 

 

Captain_WD.

[xBartGR]

Actually i'm getting the same problem more or less. Haven't figured yet what could be... i'm going to open a new thread

[Dr. Xeno Pootis]

Ok, no more critical structure corruption BSODs

 

However, I did get a new BSOD called Driver_IRQL_Not_Less_or_Equal, nothing else.

It happened after about 8 hours of my PC being on, with 6 hours having the GPU on 100% load

 

Dump file here: https://drive.google.com/file/d/0B8bdN8W0NxRjaUtrVVN3eWRCQ0E/view?usp=sharing

[xBartGR]

After 3 days of flawless work for me, another bsod showed.
Have you figured out something?

[Damocles]

Blue screens of minor inconveniences occur when the system detects either a hardware fault or a system file corruption. If your system is stable and the error is random, then it's likely a hardware issue. To be sure, go to CMD, run as admin, type in "sfc /scannow". If it say's it's all good, it's pretty much hardware error. Else, it will try to fix it or you can use "dism /online /cleanup-image /restorehealth". If both failed, tell me, It's a lot more complicated than a simple corruption but still there's a fix besides the dreaded reinstall.

 

I see you have the same mobo as me, check to see if you have the latest bios 1801 as some of these updates do improve stability. Power supply failure doesn't always yield BSODs, they usually make black screens of "I can't handle 651 watts of this". PSU BSOD's are when the capacitors are cheap, yielding unstable constant power, which isn't the case for EVGA. Unless of course, 1/100,000 you got a defective one.

 

If hardware is the culprit, go to bios and set to default, or better yet clear cmos. The first time you boot afterwards you should go into the bios and see if the voltages are normal as the mobo does do guesswork here to determine stable voltages. Sometimes people get stable at 1.2V stock CPU but it's not unheard of for the mobo to determine 1.35V to be safe at stock, you'd simply have a bad ASIC quality chip.