Could use some help!

[infidels66]

Hey guys,

Been a longtime reader but this is my first post.

I recently built a new gaming desktop.

Mobo - Asus Maximus VI Hero
CPU - 4770K
RAM -8g gskill trident @ 2400
Cooler - H80I
GPU - Asus 780 DCU2
Used an older PSU - Corsair TX750
SSD - 240g sandisk extreme (18 months old )
OS- Windows 8.1

My rig runs great, temps are average or lower and It's passed several CPU/Mem stress tests. However, when playing BF4 I have gotten "WHEA UNCORRECTABLE ERROR". I'm having trouble identifying what the issue is. This BSOD happened three times and I assumed it was the GPU.. so I exchanged it for another. Played 12-15 full BF4 matches with zero issues until today.. It happened again with the replaced GPU.

-CPU and memory have passed every stress test.
-Temperatures are fine
-Same BSOD with two different GPU's ( Both were ASUS GTX780 DCU2 )

I have the latest Nvidia drivers, they were released March 10th. This is fresh windows 8.1 install eight days old.

could this be a PSU issue or possibly the new Nvidia drivers?

Any feedback would help

Thanks

-Rob

 

[Bad_Kitty13]

are you overclocking your cpu? if so what voltages are you using

 

[infidels66]

are you overclocking your cpu? if so what voltages are you using

I haven't started to OC yet. I plan too but wanted to make sure everything was working properly.

 

[Bad_Kitty13]

here is some troubleshooting procedures
http://www.reviversoft.com/blog/2013/09/a-guide-to-the-whea_uncorrectable_error-blue-screen-of-death/
if you get to the end post your result

 

[jnkweaver]

try this
http://www.tomshardware.com/answers/id-1761409/uncorrectable-error-occurred.html

 

[infidels66]

here is some troubleshooting procedures
http://www.reviversoft.com/blog/2013/09/a-guide-to-the-whea_uncorrectable_error-blue-screen-of-death/
if you get to the end post your result

Results from chkdsk - Also checked my dump files from my crashes and it's definitely not a driver issue.

However, In my current state (Hungover).... I realized after setting my motherboard to "default settings", I had set the Auto OC feature on.. I was running at 4.2 with no change to voltage.. I'm going out on a limb and going to assume that was the issue.. It coincides with the time line.. haha.

Sorry for wasting you're time. I'll post if I BSOD again!

Thanks

Checking file system on C:
The type of the file system is NTFS.

A disk check has been scheduled.
Windows will now check the disk.

Stage 1: Examining basic file system structure ...
128256 file records processed. File verification completed.
2643 large file records processed. 0 bad file records processed.
Stage 2: Examining file name linkage ...
177184 index entries processed. Index verification completed.
0 unindexed files scanned. 0 unindexed files recovered.
Stage 3: Examining security descriptors ...
Cleaning up 1144 unused index entries from index $SII of file 0x9.
Cleaning up 1144 unused index entries from index $SDH of file 0x9.
Cleaning up 1144 unused security descriptors.
CHKDSK is compacting the security descriptor stream
Security descriptor verification completed.
24465 data files processed. CHKDSK is verifying Usn Journal...
36502096 USN bytes processed. Usn Journal verification completed.

Stage 4: Looking for bad clusters in user file data ...
128240 files processed. File data verification completed.

Stage 5: Looking for bad, free clusters ...
35024302 free clusters processed. Free space verification is complete.
CHKDSK discovered free space marked as allocated in the volume bitmap.

Windows has made corrections to the file system.
No further action is required.

233888767 KB total disk space.
93479616 KB in 99452 files.
73768 KB in 24468 indexes.
0 KB in bad sectors.
238171 KB in use by the system.
65536 KB occupied by the log file.
140097212 KB available on disk.

4096 bytes in each allocation unit.
58472191 total allocation units on disk.
35024303 allocation units available on disk.

 

[Bad_Kitty13]

no waste of time at least now you know. that is why i ask if you were overclocking, it tends to cause it sometimes even if test confirm it is stable. you shouldnt have any more bsod with that code on it anymore. especially auto oc on haswell tends to send errors in windows os. and the best cure for a hangover is to keep drinking 😛