Ryzen 1500x Voltage Configuration? Need help!

Can someone tell me if this looks okay? View on imgur

First off, I haven't touched any overclocking settings; everything in my BIOS is sitting firmly on automatic. That voltage spike only seems to flash on the screen for a split second before it settles back down to where it belongs. On average, I’m seeing about 0.8v.

I'm just a bit worried that my processor might turn into a pile of ash before I even get a chance to actually use it properly. I've had some people tell me that the voltage is way too high, while others insist that's just how XFR is supposed to behave and that it's perfectly fine. In my state of anxiety, I'm stuck between a rock and a hard place, and I don't dare tweak a single setting for fear of completely bricking the whole thing.

Look, not all processors are created equal, you know? Some of them just pull way more juice than others. But honestly, if you check out your CPU temperature, everything looks totally normal. You really shouldn't sweat it unless those numbers start climbing way higher than they should be, which isn't happening here.

If you decide to crank up that voltage and start overclocking, the absolute most important thing is making sure you've got a solid cooler under there. You've gotta keep those temps in check, because if things start hitting, say, over 140°F, then you've actually got a reason to worry.

And I’m hoping that holds true. Over the last hour or so, my VCORE hasn't even touched 1.040v, even while I was jumping between heavy gaming sessions and just browsing the web.

I'm running into some BSOD issues lately; right before the restart, I get hit with a BAD_POOL_CALLER error, and it seems to happen almost exclusively while I'm gaming.

Here is what I pulled up on on WhoCrashed.

crash dump file: C:\Windows\Minidump\010818-19156-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x142900)
Bugcheck code: 0xC2 (0x7, 0x126C, 0x40C000D, 0xFFFFE001EC762730)
Error: Corporation BAD_POOL_CALLER 2
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft ® Windows ® Operating system company : Microsoft Corporation description : NT kernel & system
company: Microsoft Corporation
description: NT kernel & system
Bug check description: This indicates that the current thread is making a bad pool request.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: rtwlanu.sys (rtwlanu+0x44854)
Bugcheck code: 0xC2 (0x7, 0x126C, 0x40C000D, 0xFFFFE001EC762730)
Error: BAD_POOL_CALLER
file path: C:\Windows\system32\drivers\rtwlanu.sys
product: Realtek wlan wireless USB 2.0 adapter company
company: Realtek Semiconductor Corporation
description: Realtek WLAN USB NDIS Driver 39163
Bug check description: This indicates that the current thread is making a bad pool request.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: rtwlanu.sys (Realtek WLAN USB NDIS Driver 39163, Realtek Semiconductor Corporation ).
Google query : rtwlanu.sys Realtek Semiconductor Corporation BAD_POOL_CALLER

Two crash dumps were located and parsed, and they point directly toward a third-party driver as the culprit behind these system crashes. It would be a smart move to hunt down the latest updates for these drivers on the manufacturer's site. Click on The links below to search with Google for updates for Thes Drivers :

That voltage looks way too high if you're planning on pushing any serious overclocking. It seems like you might have ended up with a board running an older BIOS version, which makes the voltage act a bit erratic. Maybe the LLC setting is cranked up too high, causing the board to overvolt.

From what I can find online, it should hover around 1.35V when using XFR—nothing much higher than that.

It shouldn't be too hard to troubleshoot this... just hop into the BIOS, go to Voltage Configuration, set the CPU Voltage to an Offset of -100mV, and run a quick stress test. If that option is available, you could also try setting the Load Lin Calibration (LLC) to its lowest value (on an ASRock board, that’s usually the highest number, maybe 3 or 5).

...or you could just flash the BIOS to the latest version first and see if that fixes everything on its own.😉

The last possibility is that it's just reading the voltage incorrectly, though I wouldn't bet on it. Maybe check it again using HWInfo.

crimsonstag84 said:That voltage level is basically a recipe for extreme overclocking; it's way too high for standard use. It looks like you might have ended up with a motherboard running a subpar BIOS version, which is causing the voltage to spike like crazy. There's a good chance the Load Lin Calibration is set to its most aggressive mode, leading the board to overvolt everything.

From what I can gather from looking things up online, with XFR enabled, you should be seeing something closer to 1.35V, nothing much higher than that.

It isn't exactly rocket science to test this and get it sorted out... just head into the BIOS, go to Voltage Configuration, set the CPU Voltage to an Offset of -100mV, and run a quick stress test to see how it holds up. If it's available, you could also try setting the Load Lin Calibration(LLC) to its lowest value (on an ASRock board, that’s usually the highest number, likely 3 or 5).

...or honestly, just flash the BIOS to the latest version first, and that might clear the whole thing right up.😉

The last possibility is that the reading itself is just wrong, though I wouldn't bet on it. You might want to double-check the numbers using HWInfo.

At this point, I'm actually less worried about the voltage and more preoccupied with this constant BSOD -.-. Do you happen to have any inkling of what might be causing that?

Jerry Williams10 said:Honestly, I'm less worried about the other stuff now and more preoccupied with this BSOD -.-. Any idea what might be causing it?

Realtek WLAN Wireless USB 2.0 Adapter
company: Realtek Semiconductor Corporation
description: Realtek WLAN USB NDIS Driver 39163

It looks like a driver is acting up—maybe try a clean reinstall and see if that clears things up?

I went ahead and ran Driver Booster, and it flagged that Realtek driver as being faulty. It ended up downloading and installing some fresh drivers, so now we just wait and see if that actually fixes things.

So apparently some AMD processors are hitting a BSOD because they haven't been properly updated lately, and there was this whole security vulnerability thing popping up with both Intel and AMD chips—though with AMD it was just that Spectre flaw which they were trying to patch through those Windows security updates.
Man, that BSOD might actually be what's killing you.
Here's the link

I’m going to wait and see if these Blue Screens of Death make another appearance, though things seem to have stabilized since I installed those Realtek drivers. Yesterday was actually my first full day without any hiccups since the PC arrived last week.

As for the voltage, it looks like everything is within the expected range. At least, that’s what the folks over at the official AMD forums are saying. Apparently, it only spikes to that level for about a millisecond just to give certain processes a little extra kick; if it stayed pinned at that voltage constantly, then we’d definitely have something to worry about.