PC froze followed by a 'buzzing' sound from my headset

[Zygor91]

Hello,

This occured while I was playing Diablo 3, I had to restart my pc manually.

My recent upgrade: Hyperx fury 1600 2x4 Ram yesterday.

I ran Prime 26.6 blend test in one hour all tests passed! (720k passed) - temps didn't go higher than 62 in cores since I use noctua nh-d14 and I don't overclock!

System specification:

CPU: I7 4790k
Mobo: Asus Z97-AR
SSD: Samsung 850 Evo 250gb
GPU: Gigabyte gtx 650 Ti 2gb
PSU: Corsair 600 80+

My recent upgrades last week, CPU, & Mobo.

What do you guys think?

 

[coovargo]

Most likely a bad memory module. I've had this before. Test them individually, preferably with Memtest86.

 

[Zygor91]

Most likely a bad memory module. I've had this before. Test them individually, preferably with Memtest86.

Thanks for your quick reply, I will do that later and report back since I have to go

 

[Zygor91]

Thanks all for your help.

I ran memtest86 for 10hours without any error! but I forgot to use ram individually.

GPU idle: 27-29, load: 40-50

When I bought this SSD I didn't uninstall previous drivers like sound, network etc when I moved to 1150 mobo from AM3+. What do you guys think I should do? still curious

 

[coovargo]

I still think it could be a memory error. When I had bad RAM it would take an average of 72 hours of standard use to come across the error. I could never get it to show in memtest either, not because memtest is a bad test, but because it takes a long time to extensively test each module. The times I would BSOD the error message was always the same in the log. The only way I figured it out is the next time the PC crashed I took one of the modules out and just ran it normally, and when it did it the next time, put the one I took out back in, and take the next one out. After about 3 weeks of no crash I decided to RMA the set. Never crashed since. As for voltage, I keep DRAM at 1.6 on my system.

It's possible you have a driver conflict, though sound/network would probably be unlikely since the OS will generally use the drivers it has hardware for. My understanding is that driver conflicts almost always result in a BSOD, where general hardware issues like faulty memory, insufficient PSU power, CPU overheating, GPU overheating, poor USB driver-device compatibility (Something like DSTools comes to mind, a USB/Bluetooth controller driver for PS3/PS4 controllers), can result in the system getting "Stuck" on error.

 

[Zygor91]

I still think it could be a memory error. When I had bad RAM it would take an average of 72 hours of standard use to come across the error. I could never get it to show in memtest either, not because memtest is a bad test, but because it takes a long time to extensively test each module. The times I would BSOD the error message was always the same in the log. The only way I figured it out is the next time the PC crashed I took one of the modules out and just ran it normally, and when it did it the next time, put the one I took out back in, and take the next one out. After about 3 weeks of no crash I decided to RMA the set. Never crashed since. As for voltage, I keep DRAM at 1.6 on my system.

It's possible you have a driver conflict, though sound/network would probably be unlikely since the OS will generally use the drivers it has hardware for. My understanding is that driver conflicts almost always result in a BSOD, where general hardware issues like faulty memory, insufficient PSU power, CPU overheating, GPU overheating, poor USB driver-device compatibility (Something like DSTools comes to mind, a USB/Bluetooth controller driver for PS3/PS4 controllers), can result in the system getting "Stuck" on error.

I rather want to have defect RAM than anything else! If this occurs again or continuously I will RMA. I forgot to mention that I don't get BSOD or any report from the 'bluescreenviewer'. I also suspect that it's the RAM.

Thank you again for the help & others.