Question Pc crashes with BSOD,or just leaves wierd pixel traces of the last screen that was showen

[Cobaa]

Hello,

I need some help figuring out what is wrong with my pc. For the last month,, my pc just keeps crashing, with BSOD(dxgkrnl.sys) or just crashing and leaving traces of the last screen in pixels. I tried checked my memory with the windows checker, i benchmarked my psu because I replaced it like 2 months ago, because a capacitor blew inside. And I tried a few other things like updating all my drivers, and re-installing windows. But I noticed my gpu hot spot gets like 106 celsius. That I fixed by re-applying thermal paste in the gpu. But i really do not know what to do, so I am hoping u guys can help me. I'm going to add all the minidumps, and event logs below and of course the sys info and drivers.

Thank you for helping.

Jan

Link to Events/drivers/sysinfo/minidumps:
https://we.tl/t-VFGM9kz6br

 

[johnbl]

first fix attempt would be to install current gpu drivers from nvidia
Official Drivers | NVIDIA

---------------
the most current bugcheck is in the graphic driver. it tried to jump to a unknown function.
the addresses looked valid (real kernel address) but was not vaiid.

only issue i see is the graphic kernel driver is newer that the graphics sound driver.
you might try to update them both to the current version.

the rest of the windows install looks good, no corrupt files.

I would test with a updated gpu and gpu sound driver if you get the same type of bugcheck I would pull the gpu and try a different card.

-----------
machine info:
BIOS Version 0607
BIOS Release Date 05/29/2020
Manufacturer ASUSTeK COMPUTER INC.
Product PRIME Z490-A
Processor Version Intel(R) Core(TM) i7-10700K CPU @ 3.80GHz
Processor Voltage 8ah - 1.0V
External Clock 100MHz
Max Speed 8300MHz
Current Speed 3762MHz (<* slight underclock*)

bios and intel me udate (cpu secruity fix) here:
PRIME Z490-A｜Motherboards｜ASUS USA




---------
will take a quick look at the other bugchecks
bugcheck in dxgkrnl bad memory address used, looks valid

all the other bugchecks were in dxgkrl and were
dxgkrnl!SubmitPresentHistoryToken
calling
dxgkrnl!PrepareIndependentFlipToken
and getting an access violation.

hopefully updating the GPU driver will fix the problem
nvhda64v.sys Tue Jul 19 05:45:37 2022
nvlddmkm.sys Wed Dec 21 21:15:38 2022

try the drivers directly from nvidia
Official Drivers | NVIDIA
install the basic driver with the hd sound
no real need for all the extras

 

[Cobaa]

first fix attempt would be to install current gpu drivers from nvidia
Official Drivers | NVIDIA

---------------
the most current bugcheck is in the graphic driver. it tried to jump to a unknown function.
the addresses looked valid (real kernel address) but was not vaiid.

only issue i see is the graphic kernel driver is newer that the graphics sound driver.
you might try to update them both to the current version.

the rest of the windows install looks good, no corrupt files.

I would test with a updated gpu and gpu sound driver if you get the same type of bugcheck I would pull the gpu and try a different card.

-----------
machine info:
BIOS Version 0607
BIOS Release Date 05/29/2020
Manufacturer ASUSTeK COMPUTER INC.
Product PRIME Z490-A
Processor Version Intel(R) Core(TM) i7-10700K CPU @ 3.80GHz
Processor Voltage 8ah - 1.0V
External Clock 100MHz
Max Speed 8300MHz
Current Speed 3762MHz (<* slight underclock*)

bios and intel me udate (cpu secruity fix) here:
PRIME Z490-A｜Motherboards｜ASUS USA




---------
will take a quick look at the other bugchecks
bugcheck in dxgkrnl bad memory address used, looks valid

all the other bugchecks were in dxgkrl and were
dxgkrnl!SubmitPresentHistoryToken
calling
dxgkrnl!PrepareIndependentFlipToken
and getting an access violation.

hopefully updating the GPU driver will fix the problem
nvhda64v.sys Tue Jul 19 05:45:37 2022
nvlddmkm.sys Wed Dec 21 21:15:38 2022

try the drivers directly from nvidia
Official Drivers | NVIDIA
install the basic driver with the hd sound
no real need for all the extras

Ok thank you, I will install it today and test tomorrow.And ill let you know if it worked.