Need help determining the source of my problem.

Justfortrolls

Reputable
Mar 3, 2014
158
0
4,690
This has been going on for a while. I'll be playing a game and the display will crash, making some sort of windows noise, but still showing BIOS code AA. I thought it was the power supply, but I changed to a 1200 Axi and after a day of working perfectly the same problem arose. Im thinking it may be windows 10 at this point, but I'd like some input before I revert to windows 8. All graphics drivers are up to date. Its an x99 based system with top of the line components. Thanks for replies, looking forward to solving this problem.
 
make sure the mb bios is up to date. in the bios make sure xmp profile is on and ram speed is set right. there beed a known issue with the newer amd drivers and there gpu over heating. try using msi afterburner make sure the gpu fan are spining up to keep the card cool also make sure there working. as you replaced the power supply open the side of the case if it a small case with few fans see if the mb vrm are over heating or failing.
 

mamasan2000

Distinguished
BANNED
AMD fixed the fan-not-spinning-faster within days so get latest Crimson drivers if you have AMD Graphics card.

What kind of Windows noise is it? Any error codes?

Nvidia seems to have even bigger problems with latest GPU drivers.
https://forums.geforce.com/default/topic/901916/geforce-drivers/gtx-titan-damaged-after-using-v359-06-drivers-with-just-cause-3/
 

Justfortrolls

Reputable
Mar 3, 2014
158
0
4,690

It's hard to explain the sound, but its just a typical windows sound if you know what i mean. I have a Titan X.
 

Vic 40

Titan
Ambassador
Maybe give some system specs,

Download hwinfo32,
http://www.hwinfo.com/download32.html
open it,
click run,
close the top window which is the system summary,
click save report at the left top,
in the next window at the bottom check=⓪ "short text report" after that next,you'll get to see what is in your pc,
copy that by clicking "copy to clipboard" and right click and paste in you next post.
 

Justfortrolls

Reputable
Mar 3, 2014
158
0
4,690

Computer: ASUS All Series
CPU: Intel Core i7-5930K (Haswell-E, R2)
3500 MHz (35.00x100.0) @ 1199 MHz (12.00x99.9)
Motherboard: ASUS RAMPAGE V EXTREME
Chipset: Intel X99 (Wellsburg-X)
Memory: 16384 MBytes @ 1066 MHz, 15.0-15-15-36
- 4096 MB PC22400 DDR4 SDRAM - Corsair CMK16GX4M4A2666C16
- 4096 MB PC22400 DDR4 SDRAM - Corsair CMK16GX4M4A2666C16
- 4096 MB PC22400 DDR4 SDRAM - Corsair CMK16GX4M4A2666C16
- 4096 MB PC22400 DDR4 SDRAM - Corsair CMK16GX4M4A2666C16
Graphics: EVGA e-GeForce GTX Titan X
NVIDIA GeForce GTX TITAN X, 12288 MB GDDR5 SDRAM
Drive: Samsung SSD 850 PRO 512GB, 500.1 GB, Serial ATA 6Gb/s @ 6Gb/s
Drive: TSSTcorp CDDVDW SH-224DB, DVD+R DL
Sound: Intel Wellsburg PCH - High Definition Audio Controller [B1]
Sound: NVIDIA GM200 - High Definition Audio Controller
Network: Intel Ethernet Connection I218-V
Network: Broadcom BCM4360 802.11ac Wireless Network Adapter
OS: Microsoft Windows 10 Home Build 10240
Also just had the same crash when i flipped up the initial windows log in screen to log in.
 

Vic 40

Titan
Ambassador

As already said by smorizio, enable XMP to make the ram work at rated specs.With 1066mhz it runs at 2133mhz right now being ddr ram,it should be able to run at 2666mhz.

I haven't reead the manual for the motherboard,but what does "AA" mean as post code?

I also assume you have the Samsung software running at boot,disable it after boot to see if that helps when gaming.

Try steps given one by one.
 

Justfortrolls

Reputable
Mar 3, 2014
158
0
4,690


AA just means the system booted and is running. I'm about to try the XMP profile change and i'll post again with results.
 
Anything in Event viewer, or BSODs being logged? AA should indicate everything is fine(normal operation) on ASUS motherboards. If normal Windows sounds are still heard, it seems likely to be a driver crash, or some kind of communication signal loss to monitor. Being that AA is still displayed, it seems like your system is still running, just no visuals. Windows 8 worked fine then w/ your current setup?