Windows strikes again ==>WHEA error - A fatal hardware error has occurred.

WHEA error - A fatal hardware error has occurred. A record describing the condition is contained in the data section of this event.
Can anyone help regarding that error on event log? My computer basically freeze today, and had even given some BSOD errors sometimes this is the critical error I found in windows, system log is shared below, along with the BSOD errors. Any help will be truly appreciated.

*drive.google.com/file/d/1fNHNsEblKgr53QByN5Jro6mdEdlbmTwH/view?usp=sharing

*drive.google.com/file/d/1UWfXhh0kP3kifgDMSFG6AxwLyw4JxqDX/view?usp=sharing

Code:

Bug Check String  : THREAD_STUCK_IN_DEVICE_DRIVER

Looks like some bug in a driver. Have you installed some device recently or updated some driver?

Desmond David said:
Code:

Bug Check String : THREAD_STUCK_IN_DEVICE_DRIVER

Looks like some bug in a driver. Have you installed some device recently or updated some driver?

Well, I had updated both amd and nvidia drivers to latest version, and disabled microsoft from automatically force installing a old version of amd driver, which is the one approved by my laptop manufacturer(I updated from ver. 20.4 to 20.9 I think).............

I did this about one month ago.

Try reinstalling them perhaps. Also why do you need to install both AMD and Nvidia drivers at the same time?

Desmond David said:
Also why do you need to install both AMD and Nvidia drivers at the same time?

I use NVIDIA optimus, so my display driver is amd (integrated in processor) and for games and other 3d applications its NVIDIA.

Æsoteric Positron said:
Well, I had updated both amd

I updated it a month ago, and got BSOD with driver issue. Reinstalled windows and it was fixed. It was AMD Graphics driver.

Also if possible change the title from windows to BugDows

RumbaMon19 said:
I updated it a month ago, and got BSOD with driver issue. Reinstalled windows and it was fixed. It was AMD Graphics driver.

Oh, you reinstalled the whole windows? If the problems occurs frequently then I may have to do that as a last resort, but I hope a windows update fixes it instead ........

RumbaMon19 said:
Also if possible change the title from windows to BugDows

Request accepted

Is it really a bug in Windows? Seems like a buggy driver to me. But given the state of Windows 10 it is still very plausible.

Desmond David said:
Is it really a bug in Windows? Seems like a buggy driver to me. But given the state of Windows 10 it is still very plausible.

Well, since reinstallation of windows helped ig it was a result of some complicated conflict caused by the complicated nature of windows.

Æsoteric Positron said:
Oh, you reinstalled the whole windows? If the problems occurs frequently then I may have to do that as a last resort, but I hope a windows update fixes it instead .....

Yes, That was becoming to frequent, sfc /scannow not working and all, added it was full of some unusefull apps,(119 to be approx) and i was lazy to uninstall so I took a backup of everything and reinstalled. Windows Installs faster now, Literally took 15 minutes to all the backup, reinstall, and restore work.

Æsoteric Positron said:
Request accepted

lolz

Desmond David said:
Is it really a bug in Windows? Seems like a buggy driver to me. But given the state of Windows 10 it is still very plausible.

Actually the driver, especially the one released in june is buggy. Added, windows has many bugs, like sometimes the volume icon in notification panel disappears.

RumbaMon19 said:
Yes, That was becoming to frequent, sfc /scannow not working and all, added it was full of some unusefull apps,(119 to be approx) and i was lazy to uninstall so I took a backup of everything and reinstalled. Windows Installs faster now, Literally took 15 minutes to all the backup, reinstall, and restore work.

RumbaMon19 said:
Actually the driver, especially the one released in june is buggy. Added, windows has many bugs, like sometimes the volume icon in notification panel disappears.

Oops. Windows got accused wrongly this time, I have the latest drivers though, maybe (I hope) these were just flukes.