Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Getting Whea_uncorrectable_error BSOD while gaming


  • Please log in to reply
2 replies to this topic

#1 Snickers101

Snickers101

  • Members
  • 3 posts
  • OFFLINE
  •  

Posted 03 January 2017 - 05:26 PM

Windows 10

64 BIT

Did a fresh install of Windows 10 on my SSD when i got my new Motherboard, CPU, Ram. I bought this SSD when i bought the other components. 

Purchased a copy of Windows 7 from Microcenter and did an upgrade . Installed the Windows 7 on the SSD and upgraded from there.

My hardware is fairly new.  No hardware is more than 1 year old besides my HDD. I havent tried refreshing or reinstalling Windows 10 yet. 

My System:

Intel Core I7 6700K 

Gigabyte H110M-A

Crucial 16GB 2x8GB DDR4

Seasonic SSR G series 650W 

Asus Strix 1070-08G 

Corsair 400C

PNY 240GB SSD

WD 1TB HDD

 

I ran the program and the attachment is post here. \

Quick Refresher of whats happening: I recently upgraded my memory and got a new headset. I installed the drivers for the Asus Strix Wireless and ive had no issues. But then i started to encounter blue screens while gaming for long periods (6 hours). No im not overclocking anything and im pretty positive i dont have any virus'.  I got the error Clock_Watchdog_Timeout. I got this error twice so i decided to swap my old memory in. The new memory was the Team Vulcan 16Gb Kit DDR4 . I swapped my old Crucial Memory back in and everything seemed to be stable until i got another error saying Whea_uncorrectable_error. I dont know whats wrong. I hope its just a software issue. I know its not my memory. I did have Intel RST installed and i did just uninstall it. I hope this works but if not ill update my post. Thats basically a summary of everything recently .Thanks

Attached Files


Edited by Snickers101, 04 January 2017 - 01:49 PM.


BC AdBot (Login to Remove)

 


#2 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,091 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:08:16 AM

Posted 05 January 2017 - 09:49 AM

I do not suggest running without the Intel RST software.  I'm sure that many people are able to do this, but I wouldn't advise it with a system that's having problems.

If the errors changed when you changed the RAM, what makes you so sure that RAM isn't a problem?

FYI - the CLOCK WATCHDOG error can be software or hardware (but more often than not is hardware).  The WHEA_UNCORRECTABLE_ERROR is also able to be software or hardware - but is most often seen as a hardware problem.

Please start with these free hardware diagnostics:  http://www.carrona.org/hwdiag.html
Please run ALL of the tests and let us know the results.

 

Your UEFI/BIOS (version F5) dates from 2016.  Please check at the manufacturer's website to see if there are any UEFI/BIOS updates available for your system.  This is just in case there has been a more recent update.
FYI - W8 and W10 communicate more with the UEFI/BIOS than previous versions of Windows, so it's important to ensure that the UEFI/BIOS is kept up to date (and that outdated UEFI/BIOS' may be the cause of some compatibility issues).

Although you appear to have a reasonable number of Windows Update hotfixes for this version of your OS, please double check for any new Windows Updates.  It only takes one update to cause a problem, so it's essential that you have all of them.  The actual number is not important.  Rather it's important that you checked manually, installed any available updates, and didn't experience any errors when checking or updating.

MSI Afterburner and Riva Tuner (along with EVGA Precision) are known to cause BSOD's in some Windows systems (it's driver is usually RTCore64.sys).  Please un-install them immediately!

The memory dumps are a bit unusual for this sort of error.  They show signs of hardware problems (?maybe hard drive/SSD ?) and signs of driver issues. 

But some of these memory dumps are from a while ago - so they may have been fixed.  Also, there's not much in the way of good diagnostics for SSD's - so keep that in mind for later on (if we don't fix it).

I would suggest running Driver Verifier if all of the hardware diagnostics pass.  Please follow these instructions when running Driver Verifier:  http://www.carrona.org/verifier.html

 

Please update your Razer drivers to the latest, W10 compatible version available from the Razer website (just a hunch on my part).

 

Analysis:
The following is for information purposes only. The following information contains the relevant information from the blue screen analysis:
**************************Tue Jan  3 15:47:25.532 2017 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\010317-22812-01.dmp]
Windows 10 Kernel Version 14393 MP (8 procs) Free x64
Built by: 14393.576.amd64fre.rs1_release_inmarket.161208-2252
System Uptime:2 days 2:06:03.187
*** ERROR: Module load completed but symbols could not be loaded for intelppm.sys
Probably caused by :GenuineIntel
BugCheck 124, {0, ffffa881e634d028, be000000, 800400}
BugCheck Info: WHEA_UNCORRECTABLE_ERROR (124)
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffffa881e634d028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000800400, Low order 32-bits of the MCi_STATUS value.
BUGCHECK_STR:  0x124_GenuineIntel
PROCESS_NAME:  System
FAILURE_BUCKET_ID: 0x124_GenuineIntel_PROCESSOR_MAE
CPUID:        "Intel® Core™ i7-6700K CPU @ 4.00GHz"
MaxSpeed:     4000
CurrentSpeed: 4008
  BIOS Version                  F5
  BIOS Release Date             03/07/2016
  Manufacturer                  Gigabyte Technology Co., Ltd.
  Product Name                  To be filled by O.E.M.
  Baseboard Product             H110M-A-CF
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Nov 25 23:51:52.772 2016 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\112716-4781-01.dmp]
Windows 10 Kernel Version 14393 MP (8 procs) Free x64
Built by: 14393.447.amd64fre.rs1_release_inmarket.161102-0100
System Uptime:0 days 1:21:26.426
Probably caused by :ntkrnlmp.exe ( nt!PopNotifyShutdownListener+10 )
BugCheck A, {ffffb90203d5cad0, ff, 0, fffff80068457c64}
BugCheck Info: IRQL_NOT_LESS_OR_EQUAL (a)
Arguments:
Arg1: ffffb90203d5cad0, memory referenced
Arg2: 00000000000000ff, IRQL
Arg3: 0000000000000000, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80068457c64, address which referenced memory
BUGCHECK_STR:  AV
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
FAILURE_BUCKET_ID: AV_nt!PopNotifyShutdownListener
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Nov 14 20:04:16.484 2016 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\111516-4781-01.dmp]
Windows 10 Kernel Version 14393 MP (4 procs) Free x64
Built by: 14393.447.amd64fre.rs1_release_inmarket.161102-0100
System Uptime:1 days 1:21:49.150
Probably caused by :ntkrnlmp.exe ( nt!PopNotifyShutdownListener+10 )
BugCheck A, {ffffd7034b6d3460, ff, 0, fffff802fddf6c64}
BugCheck Info: IRQL_NOT_LESS_OR_EQUAL (a)
Arguments:
Arg1: ffffd7034b6d3460, memory referenced
Arg2: 00000000000000ff, IRQL
Arg3: 0000000000000000, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff802fddf6c64, address which referenced memory
BUGCHECK_STR:  AV
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
FAILURE_BUCKET_ID: AV_nt!PopNotifyShutdownListener
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Jan  1 00:00:00.000 1969 (UTC - 0:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\121016-9187-01.dmp]



3rd Party Drivers:
The following is for information purposes only. My recommendations were given above. The drivers that follow belong to software or devices that were not developed by Microsoft.  You can find links to the driver information and where to update the drivers in the section after the code box:

**************************Tue Jan  3 15:47:25.532 2017 (UTC - 5:00)**************************
XtuAcpiDriver.sys           Thu Feb 26 07:51:57 2015 (54EF16ED)
RTKVHD64.sys                Tue Jul  7 07:13:02 2015 (559BB43E)
iaStorA.sys                 Mon Jul 27 05:26:48 2015 (55B5F958)
TeeDriverW8x64.sys          Tue Jul 28 13:35:42 2015 (55B7BD6E)
rzpnk.sys                   Wed Sep 16 20:16:35 2015 (55FA0663)
rzpmgrk.sys                 Thu Sep 17 14:42:44 2015 (55FB09A4)
Rt64win7.sys                Thu Oct  1 06:24:08 2015 (560D09C8)
rzendpt.sys                 Wed Jun 15 23:43:23 2016 (5762205B)
rzudd.sys                   Wed Jun 15 23:43:26 2016 (5762205E)
intelppm.sys                Fri Jul 15 22:10:43 2016 (578997A3)
nvhda64v.sys                Thu Sep 29 09:25:06 2016 (57ED1632)
nvvad64v.sys                Fri Nov 25 10:43:56 2016 (58385C3C)
nvlddmkm.sys                Sun Dec 11 13:13:24 2016 (584D9744)
BEDaisy.sys                 Mon Dec 12 06:46:58 2016 (584E8E32)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Nov 25 23:51:52.772 2016 (UTC - 5:00)**************************
hiber_storport.sys          Fri Jul 15 22:21:57 2016 (57899A45)
nvvad64v.sys                Thu Sep 22 12:46:30 2016 (57E40AE6)
nvlddmkm.sys                Tue Oct 25 15:38:31 2016 (580FB4B7)


http://www.carrona.org/drivers/driver.php?id=XtuAcpiDriver.sys
http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys
http://www.carrona.org/drivers/driver.php?id=iaStorA.sys
http://www.carrona.org/drivers/driver.php?id=TeeDriverW8x64.sys
http://www.carrona.org/drivers/driver.php?id=rzpnk.sys
http://www.carrona.org/drivers/driver.php?id=rzpmgrk.sys
http://www.carrona.org/drivers/driver.php?id=Rt64win7.sys
http://www.carrona.org/drivers/driver.php?id=rzendpt.sys
http://www.carrona.org/drivers/driver.php?id=rzudd.sys
http://www.carrona.org/drivers/driver.php?id=intelppm.sys
http://www.carrona.org/drivers/driver.php?id=nvhda64v.sys
http://www.carrona.org/drivers/driver.php?id=nvvad64v.sys
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
http://www.carrona.org/drivers/driver.php?id=BEDaisy.sys
http://www.carrona.org/drivers/driver.php?id=hiber_storport.sys
http://www.carrona.org/drivers/driver.php?id=nvvad64v.sys
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys

 
My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.

#3 Snickers101

Snickers101
  • Topic Starter

  • Members
  • 3 posts
  • OFFLINE
  •  

Posted 08 January 2017 - 03:04 AM

So far no blue screens . The ram is fine . There are no issues with them. The cpu is fine as I ram Intels diagnosis. I only currentry running my system with no issues ever since I removed the Intel Raid Storage Technology . I do have Riva and Msi after burner for recording benchmarks but I don't have them on startup . Let's see if this continues to be good




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users