F5F Stay Refreshed Hardware Desktop WHEA triggers during startup repeatedly

WHEA triggers during startup repeatedly

WHEA triggers during startup repeatedly

Pages (3): Previous 1 2 3 Next
K
Kusiu4444
Member
170
05-11-2016, 04:54 AM
#11
There was a brief flash right before the login window usually shows up, typically at 10. The short glitchy lines that appear after the desktop seem like the WHEA, but the BIOS was just released a while back and I checked it yesterday. It doesn’t seem too serious, though—I’m worried it might impact the GPU during these shortages. I recorded the first one yesterday – link provided. The second flash is hard to capture clearly even with my eyes. It happens before I can launch HWinfo.
K
Kusiu4444
05-11-2016, 04:54 AM #11

There was a brief flash right before the login window usually shows up, typically at 10. The short glitchy lines that appear after the desktop seem like the WHEA, but the BIOS was just released a while back and I checked it yesterday. It doesn’t seem too serious, though—I’m worried it might impact the GPU during these shortages. I recorded the first one yesterday – link provided. The second flash is hard to capture clearly even with my eyes. It happens before I can launch HWinfo.

C
Ced4sen
Junior Member
7
05-13-2016, 08:48 PM
#12
What are your specifications? This could be related to the motherboard or BIOS, though it might also stem from a Ryzen issue. It seems mysterious—there’s often a recurring problem. Here are some threads that discuss similar issues: one mentions persistent WHEA errors on X570 platforms, and another points out the lack of a guaranteed fix. Please note, I’m not certain about the exact cause, but it could vary. I don’t understand why it isn’t logged clearly either.
C
Ced4sen
05-13-2016, 08:48 PM #12

What are your specifications? This could be related to the motherboard or BIOS, though it might also stem from a Ryzen issue. It seems mysterious—there’s often a recurring problem. Here are some threads that discuss similar issues: one mentions persistent WHEA errors on X570 platforms, and another points out the lack of a guaranteed fix. Please note, I’m not certain about the exact cause, but it could vary. I don’t understand why it isn’t logged clearly either.

T
Tavado
Senior Member
505
05-14-2016, 12:31 AM
#13
The system features an i5-10600K CPU, Asus TUF-GAMING-Z490-PLUS motherboard, 2x8GB 3000Mhz DDR4 RAM with Crucial Ballistix (Micron E-die), a MSI GTX 1060 GPU, and a 1TB Adata SX8200 Pro SSD. It includes a PSU from Corsair, a TUF VG279QM cooling case, a Harry 3 storage drive, and a Zalman CNPS20X keyboard with mechanical switches, mouse, and audio features. Additional components are Creative Sound Blaster Z, Audioengine A5+, and ISK HF2010 OS running Windows 10.
T
Tavado
05-14-2016, 12:31 AM #13

The system features an i5-10600K CPU, Asus TUF-GAMING-Z490-PLUS motherboard, 2x8GB 3000Mhz DDR4 RAM with Crucial Ballistix (Micron E-die), a MSI GTX 1060 GPU, and a 1TB Adata SX8200 Pro SSD. It includes a PSU from Corsair, a TUF VG279QM cooling case, a Harry 3 storage drive, and a Zalman CNPS20X keyboard with mechanical switches, mouse, and audio features. Additional components are Creative Sound Blaster Z, Audioengine A5+, and ISK HF2010 OS running Windows 10.

A
116
05-14-2016, 03:36 AM
#14
It's interesting you're on Intel—it makes me wonder if the issue isn't AMD's fault but rather a problem with the motherboard manufacturers. I believe the problem might be related to PCIE3/4 compatibility, which can sometimes cause harmless or problematic behavior. On my machines (1050ti, 1060, 1070, and 3070), all of them experienced the same error on the same B350 board, with the hardware vendor ID pointing to NVIDIA. Maybe @Radium_Angel has some insights; it's definitely a curious situation.
A
Assassin_AndyZ
05-14-2016, 03:36 AM #14

It's interesting you're on Intel—it makes me wonder if the issue isn't AMD's fault but rather a problem with the motherboard manufacturers. I believe the problem might be related to PCIE3/4 compatibility, which can sometimes cause harmless or problematic behavior. On my machines (1050ti, 1060, 1070, and 3070), all of them experienced the same error on the same B350 board, with the hardware vendor ID pointing to NVIDIA. Maybe @Radium_Angel has some insights; it's definitely a curious situation.

J
JessBrearley
Member
195
05-14-2016, 09:05 PM
#15
We can evaluate some hardware to confirm everything is functioning properly. RAM testing with MemTest86 works well on Intel systems and can be done via Disk Genius (though the interface has a bit of a clutter). HDTune offers another option for drive diagnostics, though the free version may interfere with power settings. Stress and burn-in tests are more challenging to perform on the motherboard. Check Windows Logs under System for any Red error marks; the HWI should display these until they’re removed from the Event Log, which might still be available if it’s quite old.
J
JessBrearley
05-14-2016, 09:05 PM #15

We can evaluate some hardware to confirm everything is functioning properly. RAM testing with MemTest86 works well on Intel systems and can be done via Disk Genius (though the interface has a bit of a clutter). HDTune offers another option for drive diagnostics, though the free version may interfere with power settings. Stress and burn-in tests are more challenging to perform on the motherboard. Check Windows Logs under System for any Red error marks; the HWI should display these until they’re removed from the Event Log, which might still be available if it’s quite old.

X
XoxNinjaxoX
Junior Member
13
05-14-2016, 10:06 PM
#16
The DistributedCOM components all failed to launch. An error occurred during startup: "2147943140". The process encountered issues with key generation and binding. Additional details indicate a network conflict preventing connection. No further suspicious activity detected.
X
XoxNinjaxoX
05-14-2016, 10:06 PM #16

The DistributedCOM components all failed to launch. An error occurred during startup: "2147943140". The process encountered issues with key generation and binding. Additional details indicate a network conflict preventing connection. No further suspicious activity detected.

T
T_Hint
Junior Member
19
05-14-2016, 10:13 PM
#17
They’re not major concerns (even though they mentioned otherwise). Everything’s fine. I wouldn’t worry about it unless it’s really affecting things or causing problems.
T
T_Hint
05-14-2016, 10:13 PM #17

They’re not major concerns (even though they mentioned otherwise). Everything’s fine. I wouldn’t worry about it unless it’s really affecting things or causing problems.

K
KrYnoMoRe
Junior Member
13
05-15-2016, 03:33 AM
#18
the log shows 17 warnings, just a notification—no critical issues detected. this isn't a crash or system failure.
K
KrYnoMoRe
05-15-2016, 03:33 AM #18

the log shows 17 warnings, just a notification—no critical issues detected. this isn't a crash or system failure.

L
LOL0
Member
191
05-15-2016, 04:45 AM
#19
You’re likely to see many mistakes in the event viewer, unless there are serious issues. Fraudsters exploit this data to trick seniors into scams. However, HWInfo64 displays only critical WHEA errors—avoid these if possible.
L
LOL0
05-15-2016, 04:45 AM #19

You’re likely to see many mistakes in the event viewer, unless there are serious issues. Fraudsters exploit this data to trick seniors into scams. However, HWInfo64 displays only critical WHEA errors—avoid these if possible.

A
ariel_8888
Member
214
05-15-2016, 12:12 PM
#20
thats the thing though, it doesn't, critical whea is insta bsod ... (afaik) these are "correctable hardware errors" hence no crash. and as the theory goes its simply a bug/ false alarm (probably on pcie3/4 enabled devices)
A
ariel_8888
05-15-2016, 12:12 PM #20

thats the thing though, it doesn't, critical whea is insta bsod ... (afaik) these are "correctable hardware errors" hence no crash. and as the theory goes its simply a bug/ false alarm (probably on pcie3/4 enabled devices)

Pages (3): Previous 1 2 3 Next