Hey all, I've just splashed out and built the rig below. I've literally made no changes to the BIOS but experiencing random BSOD's "WHEA_UNCORRECTABLE_ERROR". This usually happens when using something productive, i.e. Premiere Pro, or Photoshop. However I've been gaming for hours and it's stable - which to me says it's something to do with the cores working in tandem? Here's the rig.
Motherboard model: ASUS ROG Strix X299-E
UEFI Version: 0503 (I've just looked and there appears to be 0802 so I'll give that a bash, but I have a feeling it's not this)
SSD/HDDs: Samsung 250GB EVO NVMe / Corsair F3 120GB SSD / WD Black 2TB
PSU:Corsair RMi Series RM750i
USB Devices: Roland Quad Capture USB 2.0 Audio / Anker USB Hub
PCIe device: Firewire PCIe card
Monitor: 2X 23" LG W2353V-PF@1080P
CPU Cooler: AIO Be Quiet. BW003 Fan 280 mm
PC CASE: Corsair CC-9011100-WW Carbide Series 400Q V2
Operating system: MS Activated=yes. Windows 10 x64 (version 1703 / OS Build 15063.608)
Drivers Installed: Latest NVidia Drivers (385.41)
Any third Party temp/voltage software installed: Just AI Suite 3. Average CPU temperature is between 28°C-38°C
System Overclocked (provide details)? BIOS is as is, set to Auto. However, it jumps up to 4Ghz although I haven't asked it to do this. I've also turned off ASUS Multicore, but that didn't help. My guess is it's to do with the auto overclock? But really given the temps I'm getting, I'm surprised it's giving this error. Maybe it's a simple BIOS update, but I'm guessing not?
Does anyone have any ideas? I'm feeling a bit gutted atm
I had this happen to my sig rig a couple over the weekend. Same OS, same GPU drivers. Showed up as one of the CPU cores had a hiccup running a process (or a process hiccuped a core) and BSOD'd my system. It hasn't happened since so I'm not worried about it. No need to worry about a one off BSOD.
I had this happen to my sig rig a couple over the weekend. Same OS, same GPU drivers. Showed up as one of the CPU cores had a hiccup running a process (or a process hiccuped a core) and BSOD'd my system. It hasn't happened since so I'm not worried about it. No need to worry about a one off BSOD.
I'm getting the exact same thing on my TUF Mark 1 when running Realbench.
I've been struggling with it for days, doesn't matter what BIOS version I use, I'm also running the same nvidia driver (385.41), plus the same CPU, GPU and ram as you.
It only just started since upgrading to 0802, but like I said rolling back to previous versions still results in the same error.
At first I thought it was my overclock I'd been running for the last 4 weeks, but I can rung Realbench fine on one occasion, if I try to run it again it will Bluescreen, it's random.
Prime95 is fine.
Can't even run Divinity Original Sin 2 at the previous overclock for some reason, it just hard locks.
I'm completely stumped at the moment.
I did just rolled back to the previous Nvidia Driver and the Divinity hard locks have stopped, going to try Realbench now.
Ok I just did a 15 minute Realbench run at my previous 4.6Ghz OC and it passed, it usually bluescreens a couple of minutes in.
Divinity has stopped hard locking as well.
It's so strange, I did a 2 hour Realbench run yesterday and it passed, fire up Divinity hard lock within minutes.
Not doing it as of now, will test further.
Try rolling back your Nvidia drivers and see if it helps for now.
Odd it happened after updating the UEFI. If that's the case I would upgrade the Intel Lan driver along with the Intel Management Engine driver since a UEFI can upgrade the firmware of those devices.
Odd it happened after updating the UEFI. If that's the case I would upgrade the Intel Lan driver along with the Intel Management Engine driver since a UEFI can upgrade the firmware of those devices.
I was using a different one (0705) and getting the BSOD. Upgraded to 0802 today and not seen a BSOD since....although I should run a benchmark to verify.
I was using a different one (0705) and getting the BSOD. Upgraded to 0802 today and not seen a BSOD since....although I should run a benchmark to verify.
Run Prime95 with AVX and check your temperatures with Real Temp. Premiere Pro and Photoshop both use AVX. I've seen multiple people never have issues until running these applications. After you see your temperatures hitting 100c+ you can thank Intel for glueing on the IHS.
Run Prime95 with AVX and check your temperatures with Real Temp. Premiere Pro and Photoshop both use AVX. I've seen multiple people never have issues until running these applications. After you see your temperatures hitting 100c+ you can thank Intel for glueing on the IHS.
Run Prime95 with AVX and check your temperatures with Real Temp. Premiere Pro and Photoshop both use AVX. I've seen multiple people never have issues until running these applications. After you see your temperatures hitting 100c+ you can thank Intel for glueing on the IHS.
I tried it for 15mins - seemed stable. The CPU temps were between 48-51 according to RealTemp. Quickly back into the 30s after. Sound about right? Or do I need to leave it for hours?
I tried it for 15mins - seemed stable. The CPU temps were between 48-51 according to RealTemp. Quickly back into the 30s after. Sound about right? Or do I need to leave it for hours?
I tried it for 15mins - seemed stable. The CPU temps were between 48-51 according to RealTemp. Quickly back into the 30s after. Sound about right? Or do I need to leave it for hours?
That's way too low for any Intel processor that isn't de-lidded. Please run Prime95 28.10 with Small FFTs
This is an older thread, you may not receive a response, and could be reviving an old thread. Please consider creating a new thread.
Related Threads
?
?
?
?
?
Ask a question
Ask a question
Overclock.net
27.8M posts
541.2K members
Since 2004
A forum community dedicated to overclocking enthusiasts and testing the limits of computing. Come join the discussion about computing, builds, collections, displays, models, styles, scales, specifications, reviews, accessories, classifieds, and more!