F5F Stay Refreshed Hardware Desktop Question Mysterious problem I believed resolved yet occurred again, code 43

Question Mysterious problem I believed resolved yet occurred again, code 43

Question Mysterious problem I believed resolved yet occurred again, code 43

J
Jumpyy
Member
64
12-13-2019, 07:59 PM
#1
I've tried three different graphics cards, so I assumed the issue was with the GPU. But after installing a brand new RTX 2060 last week, my PC restarted again when gathering info on code 43. Checking my previous posts shows why I'm still confused. Could something other than a GPU be causing this?
J
Jumpyy
12-13-2019, 07:59 PM #1

I've tried three different graphics cards, so I assumed the issue was with the GPU. But after installing a brand new RTX 2060 last week, my PC restarted again when gathering info on code 43. Checking my previous posts shows why I'm still confused. Could something other than a GPU be causing this?

I
ItzRicky__
Member
62
12-13-2019, 10:21 PM
#2
complete system specifications available. The PSU model and brand are included.
I
ItzRicky__
12-13-2019, 10:21 PM #2

complete system specifications available. The PSU model and brand are included.

S
Stev0076
Junior Member
5
12-16-2019, 01:23 AM
#3
BN626 BeQuiet! Pure Performance 11 500 Watt, 3 years old
Win 10 pro
I9 10900kf 3.7ghz
32gb ddr4 ram unknown speed
1tb ssd
Not sure about the wifi adapter (do you really need one if your mobo already has it, or is it just enough that it supports it? Always wondered that)
S
Stev0076
12-16-2019, 01:23 AM #3

BN626 BeQuiet! Pure Performance 11 500 Watt, 3 years old
Win 10 pro
I9 10900kf 3.7ghz
32gb ddr4 ram unknown speed
1tb ssd
Not sure about the wifi adapter (do you really need one if your mobo already has it, or is it just enough that it supports it? Always wondered that)

P
panda1234
Junior Member
14
12-16-2019, 12:17 PM
#4
I attempted to locate the dmp file, but it wasn't found. There were some warnings and a critical message in the event log as well.
P
panda1234
12-16-2019, 12:17 PM #4

I attempted to locate the dmp file, but it wasn't found. There were some warnings and a critical message in the event log as well.