Question 3060 Ti : Windows has stopped this device (Code 43) ?

u700

Honorable
Feb 21, 2019
24
4
10,515
Hello.

Last night my PC froze on boot screen.

Now it boots into windows, but only runs at 1024 x 768 and the GPU has a yellow exclamation mark in device manager with the error:

" Windows has stopped this device because it has reported problems. (Code 43) "

I updated the Nvidia drivers, but it didn't help.

I have dual-boot, so I logged into another OS (windows 11) and the exact same thing happens.

GPU-Z says GPU memory is 0MB and bus width and bandwidth unknown ?

Thanks
 

Ralston18

Titan
Moderator
Update your post to include full system hardware specs and OS information.

Include PSU: make, model, wattage, age, condition (original to build, new, used, refurbished)?

Disk drive(s): make, model, capacity, how full?

Look in Reliability History/Monitor and Event Viewer for additional error codes and information.
 

u700

Honorable
Feb 21, 2019
24
4
10,515
My system specs:
PSU: Cooler Master MWE Gold V2 850W
Mobo: Gigabyte B560M AORUS PRO Micro ATX
CPU : 10700KF
Boot drive (Windows 10) : SK hynix Gold P31 2TB PCIe NVMe Gen3 M.2 2280 Internal SSD (800GB Free space left)
Boot drive (Windows 11) Kingston NV1 2 TB, 700GB system partition (150GB Free)
Game drive : Samsung 870 Evo 2 TB 2.5" Sata SSD

All components were bought new when I built my PC in 2020.

UPDATE: I got the GPU tested by a computer shop and it works fine in their system.

I tested again with live linux thumb drive (POP OS) to rule out Windows problems, and the issue persists. During boot, some kind of error shows about GPU initialization, and the desktop environment is locked to 1024x768 resolution, just like on Windows. This POP OS thumb drive used to work perfectly fine in the past on this same computer.
 

u700

Honorable
Feb 21, 2019
24
4
10,515
Ok, for those interested, I found what the problem was. I took my PC to a computer shop for hardware diagnosis, and they found the problem was actually being caused by a fault in the CPU. Replacing the CPU solved the issue.
 
  • Like
Reactions: Imperat0r