WHEA UNCORRECTABLE ERROR usually occurs while gaming

[DutchOperative]

I have been getting this "WHEA UNCORRECTABLE ERROR" BSOD every once in a while. This almost always occurs after several hours of gaming. I have ran numerous tests (Prime95, Furmark, Memtest86) but have been unable to isolate a problem with my hardware. I have also checked to insure that all of my drivers are up to date and that my system is virus free. At this point I don't really know how to proceed and would greatly appreciate any advice. Could it be an OS issue. I am considering doing a clean install of the OS.

 

[DutchOperative]

Anyone.....anyone, Bueller......Bueller

 

[Boozad]

Bumping your own thread will move it off the unanswered list, most of the time that reduces the chances of anybody checking out your thread.

Your logs are also incomplete, missing several important files we require to fully understand the situation. Run the DM Log collector linked in here http://www.sevenforums.com/bsod-help-support/96879-blue-screen-death-bsod-posting-instructions.html and post up the new logs.

And stop duplicating your threads.

 

[DutchOperative]

Wow....I'm new to the site and I assumed that my post would be lost in the forum as I posted it INCREDIBLY late last night and am ignorant to how the site functions. I think I will just pose this question on another site. The so called "bump" was just me poking fun at my frustration with this issue. Feel free to delete this thread.

 

[Boozad]

What? I'm offering you advice and you want to delete the thread? That's a new one on me.

 

[Layback Bear]

No big deal Gav. We get all kinds.
They ask for free help and then get angry the the free help isn't fast enough.

That's okay because we have other members that need your help.

 

[DutchOperative]

I didn't intend to come off as difficult or ungrateful for the service provided by those on this site. I simply asked him to delete the thread as I assumed that my logs were ineffective in isolating the problem. The x124 error as I understand it points to a hardware error that is best identified through hardware tests. I only came to this understanding after I had posted the thread. Sorry for the confusion.

 

[Boozad]

0x124s usually are hardware related, but on this site we've identified software as the cause of some. Without complete logs this is difficult to determine, hence me asking for complete ones. If you don't want to provide them, that's fine.

 

[DutchOperative]

Oh....sorry.....my mistake. I actually overlooked the latter half of your initial reply where you stated that my log files were incomplete . I hastily assumed you were just directing me to the parameters for posting on the BSOD forum after I re-posted my thread. Sorry for the miscommunication.

 

[Boozad]

I'll look at these tonight after work, bear with me and I'll reply later.

 

[DutchOperative]

Thank you so much, and again I apologize for the misunderstanding.

 

[Boozad]

It's not a problem.

 

[Boozad]

The logs are complete now but the msinfo32 file is corrupt, could you try it one more time please. If there's no joy this time round we'll start with the stress and diagnostic tests. I really could do with the msinfo32 file but we can work around that if absolutely necessary.

 

[DutchOperative]

Sure, no problem. Give me just a second and I'll attempt to reupload them.

 

[DutchOperative]

I re-ran the DMlogcollector but I think the msinfo32 is still corrupt unfortunately.....

 

[Boozad]

One more option. Click Start, type in msinfo32 and hit enter. Click File then click Export... Choose the location to save then upload the resulting file.

 

[DutchOperative]

Here is the resulting file

 

[Boozad]

It will take me a while to work through it as a text document but at least it's there. First off there's this:

  [FONT=&quot]Device      PNP Device ID     Error Code  [/FONT]
  [FONT=&quot]AODDriver4.2.0    ROOT\LEGACY_AODDRIVER4.2.0\0000     This device is not present, is not working properly, or does not have all its drivers installed.     [/FONT]
  [FONT=&quot] [/FONT]
  [FONT=&quot][USB][/FONT]
  [FONT=&quot] [/FONT]
  [FONT=&quot]Device      PNP Device ID     [/FONT]
  [FONT=&quot]Standard OpenHCD USB Host Controller      PCI\VEN_1002&DEV_4397&SUBSYS_43971002&REV_00\3&267A616A&0&90      [/FONT]
  [FONT=&quot]Standard OpenHCD USB Host Controller      PCI\VEN_1002&DEV_4397&SUBSYS_43971002&REV_00\3&267A616A&0&98      [/FONT]
  [FONT=&quot]ASMedia XHCI 1.0 Controller   PCI\VEN_1B21&DEV_1142&SUBSYS_85BF1043&REV_00\4&1F27578A&0&00AA      [/FONT]
  [FONT=&quot]Standard OpenHCD USB Host Controller      PCI\VEN_1002&DEV_4397&SUBSYS_43971002&REV_00\3&267A616A&0&B0      [/FONT]
  [FONT=&quot]ASMedia XHCI 1.0 Controller   PCI\VEN_1B21&DEV_1142&SUBSYS_85BF1043&REV_00\4&28B85F88&0&00A9      [/FONT]
  [FONT=&quot]Standard OpenHCD USB Host Controller      PCI\VEN_1002&DEV_4399&SUBSYS_43991002&REV_00\3&267A616A&0&A5      [/FONT]
  [FONT=&quot]Standard Enhanced PCI to USB Host Controller      PCI\VEN_1002&DEV_4396&SUBSYS_43961002&REV_00\3&267A616A&0&92      [/FONT]
  [FONT=&quot]Standard Enhanced PCI to USB Host Controller      PCI\VEN_1002&DEV_4396&SUBSYS_43961002&REV_00\3&267A616A&0&9A      [/FONT]
  [FONT=&quot]Standard Enhanced PCI to USB Host Controller      PCI\VEN_1002&DEV_4396&SUBSYS_43961002&REV_00\3&267A616A&0&B2[/FONT]

In Device Manager with USB Controllers expanded do you have any :warn: showing?

I'm also seeing lots of Windows Updates failing to install. Have you noticed any problems with this at all?

[FONT=&quot]Event Name: [COLOR=Red]WindowsUpdateFailure[/COLOR]
Response: Not available
Cab Id: 0

Problem signature:
P1: 7.6.7600.320
P2[/FONT]

Do you have Service Pack 1 installed?

[FONT=&quot]C:\ProgramData\Microsoft\Windows\WER\ReportArchive\NonCritical_[COLOR=Red]7.6.7600[/COLOR][/FONT]

 

[DutchOperative]

I am not seeing any warnings concerning my drivers.

As for the failed updates I am receiving these errors when I attempt to update.

WindowsUpdate_800B0100
WindowsUpdate_80070490
WindowsUpdate_8024200D

And I do have Service pack 1 installed

 

[Boozad]

Open an elevated command prompt, type in or copy and paste sfc /scannow and hit enter. I'll post up the diagnostic and stress tests after this step.