FAQ FAQ  Forum Search   Register Register  Login Login

WHEA_uncorrectable_error?

Post Date: 2013-07-15
 Post Reply Post Reply
Author
  Topic Search Topic Search  Topic Options Topic Options
cheegrah View Drop Down
Newbie
Newbie


Joined: 01 Jul 2013
Online Status: Offline
Posts: 11 		  Quote cheegrah Quote  Post ReplyReply bullet Topic: WHEA_uncorrectable_error?
    Posted: 15 Jul 2013 at 4:30pm
Really enjoying the new system so far, but I have found that after playing a game like Far Cry 3 for about an hour, my PC crashes with the text "WHEA_uncorrectable_error" and tells me to search online for the problem, I did a search which basically stated that the hardware may be unstable and i have no idea how to determine which piece of hardware is acting up, has anyone else had this issue/know how to resolve it? This is making my games unplayable, i just lost about an hour of saves on FC3.

My specs are a 4670k @ 4.2GHz and a gtx 770 with 8gb of ram.



Edited by cheegrah - 15 Jul 2013 at 4:31pm
Back to Top
AndydViking View Drop Down
Senior Member
Senior Member


Joined: 10 Sep 2009
Online Status: Offline
Posts: 733 		  Quote AndydViking Quote  Post ReplyReply bullet Posted: 16 Jul 2013 at 2:11pm
You have to list all your specs in detail.  Please also list your motherboard manufacturer and model along with your current bios version.  From everything I can read about this error it's most likely a bios thing or could be cause by some overclock voltages that are off. 

So...
1.  Please list your full specs (every part of your computer & your operating system)
2.  Please save your overclock profile
3.  Set your settings to defaults
4.  Set your RAM XMP profile to the correct profile (your advertised specs)
5.  Boot back into windows and try doing what causes the error
6.  If you still get the error we can try different things
7.  If you do not get the error then call DS and have them tweak your overclock further
8.  Report back and let us know how it's going.  If you did not get any errors we still need to make sure no windows files were corrupted.  I can show you how to test and try and fix this if that's the case.
9.  Side Note:  Never hurts to run memtest 86+ (run overnight) but I am really looking at a CPU/motherboard issue or voltage configuration in your overclock issue

questions:
1.  Do you get any other errors or warnings in event viewer?


Edited by AndydViking - 16 Jul 2013 at 2:12pm
Back to Top
ArkansasWoman777 View Drop Down
DS Veteran
DS Veteran

Email address used to purchase matched with forums account email.

Joined: 19 Aug 2012
Online Status: Offline
Posts: 4314 		  Quote ArkansasWoman777 Quote  Post ReplyReply bullet Posted: 16 Jul 2013 at 2:26pm
Just an update He posted this in Technical Assistance and said when he turned off overclock everything went to working fine.
"Captain Sirius Black"
Storm Trooper
i5 3570k

Ordered: 11-27-12
Stage 1: 11-29-12
Stage 2: 12-2-12
Stage 3: 12-2-12
Stage 4: 12-4-12
Stage 5: 12-4-12
Stage 6: 12-10-12
Stage 7: 12-12-12
Back to Top
AndydViking View Drop Down
Senior Member
Senior Member


Joined: 10 Sep 2009
Online Status: Offline
Posts: 733 		  Quote AndydViking Quote  Post ReplyReply bullet Posted: 16 Jul 2013 at 2:37pm
Originally posted by ArkansasWoman777

Just an update He posted this in Technical Assistance and said when he turned off overclock everything went to working fine.


Oh OK thank you ArkansasWoman777.  That helps a lot.  LOL, I suppose I would have been waiting for a while for a reply if you didn't come and help out.  Well, it looks like it was just like I thought.  It was some overclock settings off.  These 4th gen Intels are very sensitive to voltage.
Back to Top
Alex View Drop Down
Admin Group
Admin Group

Digital Storm Supervisor


Joined: 04 Jun 2012
Online Status: Offline
Posts: 16314 		  Quote Alex Quote  Post ReplyReply bullet Posted: 16 Jul 2013 at 2:37pm
If turning overclocking fixes the issue, just contact our team so we can help you fine-tune the overclock and get it stable.
Back to Top
 Post Reply Post Reply

Forum Jump Forum Permissions View Drop Down



This page was generated in 0.03125 seconds.