KEEP GETTING BLUE SCREENS (BSOD) CODED WHEA_UNCORRECTABLE ERROR AND CLOCK_WATCHDOG_TIMEOUT URGENT HELP!

[The Hellblazer]

My PC Specs:
Processor:İntel core i7 7700K 4.2 GHz
Graphic Card: Geforce GTX 960 2GB
Ram: 16 GB DDR4

(Error codes of Blue Screens (BSOD) are given on the title)

First of all i used to run this game with no problems with average 40-50 FPS with Geforce Experience's optimised quality options on a PC with intel core i5 3470 3.2GHz(Processor) , Geforce GTX 960 2 GB(Vİdeo card) , 8 GB DDR3 RAM . With Geforce Experience's optimised quality options my new PC can run 60-80 FPS so i play the game with 65 FPS limit (so i don't see it at 50-60 FPS)

(New and old PC's Geforce Experience's optimised quality options are the same)
(In-game VRAM meter says ''2457 / 2016'' with Geforce Experience's optimised quality options)
(I don't use any overclock)

Recently i bought all better parts of a Desktop PC except video card , HDD , monitor , speakers , keyboard and mouse. But when i play Watch Dogs 2 on this new PC it gives me Blue Screen (BSOD) randomly.Sometimes during a main mission sometimes during a co-op session sometimes while free-roaming and time periods between Blue Screens (BSOD) aren't equal i mean there's no pattern.

(Windows 10 is installed on my recently bought SDD)
(Windows Update says my PC is updated)
(I use 382.53 Nvidia Graphic Driver (previous driver) because 384.76 driver (latest driver) crashes the game and some people say 384.80 hotfix driver doesn't solve the problem. Other than that every driver is updated to the latest)

I finished 4 other games with my new PC with Geforce Experience's optimised quality options without any problems. So far i get Blue Screen (BSOD) only when i play Watch Dogs 2

I only once got CLOCK_WATCHDOG_TIMEOUT Blue Screen (BSOD) after a bit increasing visual quality later i reduced it to Geforce Experience's optimised quality options and never got that again but now everytime i get Blue Screen (BSOD) it's WHEA_UNCORRECTABLE_ERROR and everytime i get BlueScreen (BSOD) my PC tells me to wait and i see a percentage. After it's 100% my PC restarts itself and i'm back on desktop as if i just started my PC.

Need help

[lakupupu]

Go to Win. Powershell and type sfc/scannow
After that, just to be sure, put
Dism /Online /Cleanup-Image /RestoreHealth.

[The Hellblazer]

Originally posted by rebeL:

Go to Win. Powershell and type sfc/scannow
After that, just to be sure, put
Dism /Online /Cleanup-Image /RestoreHealth.

''sfc/scannow : The term 'sfc/scannow' is not recognized as the name of a cmdlet, function, script file, or operable prog
ram. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1
+ sfc/scannow
+ ~~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (sfc/scannow:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException''

it says these in red after typing ''sfc/scannow''
Also putting Dism /Online /Cleanup-Image /RestoreHealth gives ''Error 740''

[The Hellblazer]

Originally posted by rebeL:

Originally posted by The Hellblazer:

''sfc/scannow : The term 'sfc/scannow' is not recognized as the name of a cmdlet, function, script file, or operable prog
ram. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1
+ sfc/scannow
+ ~~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (sfc/scannow:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException''

it says these in red after typing ''sfc/scannow''
Also putting Dism /Online /Cleanup-Image /RestoreHealth gives ''Error 740''

My fault, it's sfc /scannow with no period.
I don't know about the other command though.

Typied ''sfc /scannow'' after verification was complete it said ''Windows Resource Protection did not find any integrity violations.'' in white

[The Hellblazer]

More suggestions?

[skruideli]

Research on google and internet suggests that this may be hardware related. If you are overclocking, you could try removing the Overclock and see if that helps.

If not, you might want to run some sort of CPU or video card stress test to see how they behave under extreme loads. You might also want to run memtest 86+ off of something like ubuntu live usb stick.

Also, you could try to dig up the exact information of what crashed in windows event viewer. Usually the crash report will point to a file that was the source of the crash.