Snapshot of desktop & nvdia BLUES SCREEN

windows 10 and Fences 6 beta

nvlddmkm

 

 

\Device\Video3

Restarting TDR occurred on GPUID:100

3,997 views 6 replies
Reply #1 Top

This sounds like an OS/driver problem. Please supply the bsod code. Try updating your OS and driver.

Reply #2 Top

My Nvidia driver is up-to-date - GeForce 

 I kept Windows 10 at build 1803 because I was having problems with the next Windows upgrade working.

Reply #3 Top

Can you try this? From an elevated cmd prompt run sfc /scannow .

Maybe corrupted system files prevented the W10 update and are causing more problems? Doing a DISM could help.

What was the bsod code?

Reply #4 Top

i ran that about 1 week ago in safe mode

 

The result merely said that some faults were found but could not be fixed

 

No specific errors were listed

Reply #5 Top

bsod   INTERRUPT_EXCEPTION_NOT_HANDLED

 

ALSO

 

NVIDIA did a hotfix not this last time but the time before which seems to have cured some of the other BODS I was having 

POOL HEADER  being one of them

 

After the hotfix they all seem to list JUST the nvidia problem I posted above which allowed me to narrow it done to the driver

 

If I had to pin down that last driver that worked it would be seem to me the one before Jan 2024

 

 

Reply #6 Top

Quoting hap8192736, reply 5

bsod INTERRUPT_EXCEPTION_NOT_HANDLED
End of hap8192736's quote

I found this guide online regarding that error:

http://rynexis.liveblog365.com/2024/12/21/fixing-interrupt-exception-not-handled-a-7-step-guide/?i=1

I'd bet part of your problem is indeed nVidia's driver. Have you tried their customer/tech support?

Quoting hap8192736, reply 2

I kept Windows 10 at build 1803 because I was having problems with the next Windows upgrade working.
End of hap8192736's quote

Perhaps you should start with at least an sfc /scannow 

Both are run from elevated command prompts. The reason is that inability to upgrade can occur when system files are corrupt or missing. It happened to me upgrading from 1803 and the sfc /scannow fixed the problem.