Windows 10: Random BSOD, system service exception - nvlddmkm.sys

Last few weeks I get "random" BSOD. It happened while playing multiple games (vermintide, civilization 6, overwatch and even hearthstone or once just when watching streams).

It happens once every few days. I can play any of those games or even more without any issues between that (no fps drops or other issues)

I tried older nvidia drivers as well as the newest one, I have run windows scan disk and memory test without any issues.

Win 10 64bit, i5 6500, nvidia 1060 6gb, 2x 8gb ram

:)

 

Anniversary update BSOD Error-System Thread Exception Not Handled (Nvlddmkm.sys)

Original Title : Windows 10 1607 BSOD

Hello everyone,

After installing Windows 10 Anniversary Update my computer started to get BSOD (System Thread Exception Not Handled) (Nvlddmkm.sys), ONLY, when installing updates from WU and when booting in safe mode.

 

System_Thread_Exception_Not_Handled(nvlddmkm.sys) error code and BSOD on Windows 10 computer.

Hi

I've recently started facing this issue. BSOD and 'system thread exception not handled', nvlddmkm.sys

My laptop then restarts and works as usual.

I cannot explain what triggers the exception and so far the system has been able to recover. Is there a permanent solution to the problem?

Thank you

 

The files are in a foreign language and cannot be scanned or read.
Please change the default language to English and re-post the zip so that the files can be troubleshooted.
Language - Add, Remove, and Change in Windows 10 General Tips Tutorials
BSOD - Posting Instructions - Windows 10 Forums

Please update the system specs in the "My Computer" section:
How To Fill Out Your System Specs
System Specs - Fill in at Ten Forums:
System Specs - Fill in at Ten Forums General Tips Tutorials
In the left corner below in your post you find 'My System Specs'.
After clicking it you can find a link a little below that says 'Update your System Spec', click on this link to get to the page where you can fill in your system specs.
System Info - See Your System Specs - Windows 7 Help Forums


Include PSU. cooler, case, peripherals and anything attached to the computer by wired or wireless (mouse, keyboard, headset, printer, xbox, etc.)




Code: 07.11.2017 19:46 Windows Error Reporting Chybný blok , typ 0
Název události: BlueScreen
Reakce: Není k dispozici.
ID souboru CAB: 0

Podpis problému:
P1: 3b
P2: c0000005
P3: fffff80067908ee1
P4: ffff9480c2046320
P5: 0
P6: 10_0_15063
P7: 0_0
P8: 256_1
P9:
P10:

Připojené soubory:
\\?\C:\WINDOWS\Minidump\110717-8281-01.dmp
\\?\C:\Windows\Temp\WER-11609-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4110.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER412F.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4140.tmp.txt

Tyto soubory mohou být k dispozici zde:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_3b_b66e485ba36a74475b9bcfc333f3c02f09c216c_00000000_cab_0344413f

Symbol analýzy:
Opětovné hledání řešení: 0
ID hlášení: 8490d4e2-22b9-4f33-af40-e9b7af6b2672
Stav hlášení: 4
Zakódovaný interval: 02.11.2017 18:19 Windows Error Reporting Chybný blok , typ 0
Název události: BlueScreen
Reakce: Není k dispozici.
ID souboru CAB: 0

Podpis problému:
P1: 3b
P2: c0000005
P3: fffff800783a8ee1
P4: ffffa4001f0f1320
P5: 0
P6: 10_0_15063
P7: 0_0
P8: 256_1
P9:
P10:

Připojené soubory:
\\?\C:\WINDOWS\Minidump\110217-6812-01.dmp
\\?\C:\Windows\Temp\WER-10171-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER40D1.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER40E1.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER40F2.tmp.txt

Tyto soubory mohou být k dispozici zde:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_3b_c436ef59ff53b665562fa4e51fe7a1e47c0124c_00000000_cab_034040f1

Symbol analýzy:
Opětovné hledání řešení: 0
ID hlášení: 0ed54f28-0ef0-4cf9-bf3f-70a591825679
Stav hlášení: 4
Zakódovaný interval: 04.11.2017 23:26 Windows Error Reporting Chybný blok , typ 0
Název události: BlueScreen
Reakce: Není k dispozici.
ID souboru CAB: 0

Podpis problému:
P1: 3b
P2: c0000005
P3: fffff8016cbd8bc4
P4: ffff9281e1fd22f0
P5: 0
P6: 10_0_15063
P7: 0_0
P8: 256_1
P9:
P10:

Připojené soubory:
\\?\C:\WINDOWS\Minidump\110517-7375-01.dmp
\\?\C:\Windows\Temp\WER-10718-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3DF3.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3E12.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3E13.tmp.txt

Tyto soubory mohou být k dispozici zde:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_3b_58808e33027e935f7ff1c8d71ddd1bbaad733e_00000000_cab_03403e22

Symbol analýzy:
Opětovné hledání řešení: 0
ID hlášení: ee9d4253-a3cc-4d55-9bd1-eed2500c425e
Stav hlášení: 4
Zakódovaný interval: 18.11.2017 23:42 Windows Error Reporting Chybný blok , typ 0
Název události: BlueScreen
Reakce: Není k dispozici.
ID souboru CAB: 0

Podpis problému:
P1: 3b
P2: c0000005
P3: fffff803f2b68f50
P4: ffff8f81aa559210
P5: 0
P6: 10_0_15063
P7: 0_0
P8: 256_1
P9:
P10:

Připojené soubory:
\\?\C:\WINDOWS\Minidump\111917-7031-01.dmp
\\?\C:\WINDOWS\TEMP\WER-10546-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3C8C.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3C9B.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3C9C.tmp.txt

Tyto soubory mohou být k dispozici zde:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_3b_698565e98aab7cdcc8254c39436cfd2d45aa4_00000000_cab_03303cab

Symbol analýzy:
Opětovné hledání řešení: 0
ID hlášení: 9d91efc8-c9ea-41ba-8e49-6ca246e6ce26
Stav hlášení: 4
Zakódovaný interval: 16.11.2017 10:58 Windows Error Reporting Chybný blok , typ 0
Název události: BlueScreen
Reakce: Není k dispozici.
ID souboru CAB: 0

Podpis problému:
P1: 3b
P2: c0000005
P3: fffff80e4aff83b5
P4: ffffe701daacf320
P5: 0
P6: 10_0_15063
P7: 0_0
P8: 256_1
P9:
P10:

Připojené soubory:
\\?\C:\WINDOWS\Minidump\111617-7156-01.dmp
\\?\C:\Windows\Temp\WER-10343-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3BD0.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3BEF.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3BF0.tmp.txt

Tyto soubory mohou být k dispozici zde:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_3b_3e1bf182a6add14bffcc6431130d2a2ad60ad48_00000000_cab_03483bef

Symbol analýzy:
Opětovné hledání řešení: 0
ID hlášení: c838ef4b-bac7-4bc4-9b8b-bf48038ef02c
Stav hlášení: 4
Zakódovaný interval: 15.11.2017 16:35 Windows Error Reporting Chybný blok , typ 0
Název události: BlueScreen
Reakce: Není k dispozici.
ID souboru CAB: 0

Podpis problému:
P1: 50
P2: fffff80b00000000
P3: 0
P4: fffff80bb169779a
P5: 2
P6: 10_0_15063
P7: 0_0
P8: 256_1
P9:
P10:

Připojené soubory:
\\?\C:\WINDOWS\Minidump\111517-8171-01.dmp
\\?\C:\Windows\Temp\WER-11812-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER41FA.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER420A.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER421A.tmp.txt

Tyto soubory mohou být k dispozici zde:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_50_4f37cc6c2fb4631ce85c7ec4163ccbc2c75ab49_00000000_cab_03444219

Symbol analýzy:
Opětovné hledání řešení: 0
ID hlášení: e1ff73a3-42d9-4904-ae98-e5f1dbd90368
Stav hlášení: 4
Zakódovaný interval: 26.08.2017 8:56 Windows Error Reporting Chybný blok , typ 0
Název události: BlueScreen
Reakce: Není k dispozici.
ID souboru CAB: 0

Podpis problému:
P1: 9f
P2: 3
P3: ffffe38b737f6060
P4: ffffd081db730870
P5: ffffe38b7b311310
P6: 10_0_15063
P7: 0_0
P8: 256_1
P9:
P10:

Připojené soubory:
\\?\C:\WINDOWS\Minidump\082617-8218-01.dmp
\\?\C:\Windows\Temp\WER-10390-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4D54.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4D64.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4D75.tmp.txt

Tyto soubory mohou být k dispozici zde:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_9f_2ec7dae1b6d54968608b22a6ca5b921ca95b867e_00000000_cab_03484d74

Symbol analýzy:
Opětovné hledání řešení: 0
ID hlášení: 0a33579d-1492-44e9-b7ae-9637a48188ad
Stav hlášení: 4
Zakódovaný interval:[/quote] Code: 02.11.2017 18:19 Windows Error Reporting Chybný blok 0x3B_nvlddmkm!mapFind_IMPL, typ 0
Název události: BlueScreen
Reakce: Není k dispozici.
ID souboru CAB: 9962156a-a4b3-47a6-b327-320a35373dd0

Podpis problému:
P1: 3b
P2: c0000005
P3: fffff800783a8ee1
P4: ffffa4001f0f1320
P5: 0
P6: 10_0_15063
P7: 0_0
P8: 256_1
P9:
P10:

Připojené soubory:
\\?\C:\WINDOWS\Minidump\110217-6812-01.dmp
\\?\C:\Windows\Temp\WER-10171-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER40D1.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER40E1.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER40F2.tmp.txt

Tyto soubory mohou být k dispozici zde:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_3b_c436ef59ff53b665562fa4e51fe7a1e47c0124c_00000000_cab_1564924d

Symbol analýzy:
Opětovné hledání řešení: 0
ID hlášení: 0ed54f28-0ef0-4cf9-bf3f-70a591825679
Stav hlášení: 268435456
Zakódovaný interval: 16.11.2017 10:58 Windows Error Reporting Chybný blok 0x3B_nvlddmkm!tlsEntryAcquire, typ 0
Název události: BlueScreen
Reakce: Není k dispozici.
ID souboru CAB: 09a949c8-43e4-4062-8e7b-fe1ab29b9eea

Podpis problému:
P1: 3b
P2: c0000005
P3: fffff80e4aff83b5
P4: ffffe701daacf320
P5: 0
P6: 10_0_15063
P7: 0_0
P8: 256_1
P9:
P10:

Připojené soubory:
\\?\C:\WINDOWS\Minidump\111617-7156-01.dmp
\\?\C:\Windows\Temp\WER-10343-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3BD0.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3BEF.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3BF0.tmp.txt

Tyto soubory mohou být k dispozici zde:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_3b_3e1bf182a6add14bffcc6431130d2a2ad60ad48_00000000_cab_16c49366

Symbol analýzy:
Opětovné hledání řešení: 0
ID hlášení: c838ef4b-bac7-4bc4-9b8b-bf48038ef02c
Stav hlášení: 268435456
Zakódovaný interval: 04.11.2017 23:26 Windows Error Reporting Chybný blok 0x3B_nvlddmkm!tlsEntryAcquire, typ 0
Název události: BlueScreen
Reakce: Není k dispozici.
ID souboru CAB: 5ca510c9-8cbf-41e4-a27c-f119dedd3ede

Podpis problému:
P1: 3b
P2: c0000005
P3: fffff8016cbd8bc4
P4: ffff9281e1fd22f0
P5: 0
P6: 10_0_15063
P7: 0_0
P8: 256_1
P9:
P10:

Připojené soubory:
\\?\C:\WINDOWS\Minidump\110517-7375-01.dmp
\\?\C:\Windows\Temp\WER-10718-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3DF3.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3E12.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3E13.tmp.txt

Tyto soubory mohou být k dispozici zde:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_3b_58808e33027e935f7ff1c8d71ddd1bbaad733e_00000000_cab_16f49049

Symbol analýzy:
Opětovné hledání řešení: 0
ID hlášení: ee9d4253-a3cc-4d55-9bd1-eed2500c425e
Stav hlášení: 268435456
Zakódovaný interval: 18.11.2017 23:42 Windows Error Reporting Chybný blok 0x3B_nvlddmkm!tlsEntryAcquire, typ 0
Název události: BlueScreen
Reakce: Není k dispozici.
ID souboru CAB: 9f21668b-c567-4d60-ad5f-b5ce56aa02a7

Podpis problému:
P1: 3b
P2: c0000005
P3: fffff803f2b68f50
P4: ffff8f81aa559210
P5: 0
P6: 10_0_15063
P7: 0_0
P8: 256_1
P9:
P10:

Připojené soubory:
\\?\C:\WINDOWS\Minidump\111917-7031-01.dmp
\\?\C:\WINDOWS\TEMP\WER-10546-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3C8C.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3C9B.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3C9C.tmp.txt

Tyto soubory mohou být k dispozici zde:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_3b_698565e98aab7cdcc8254c39436cfd2d45aa4_00000000_cab_166888b8

Symbol analýzy:
Opětovné hledání řešení: 0
ID hlášení: 9d91efc8-c9ea-41ba-8e49-6ca246e6ce26
Stav hlášení: 268435456
Zakódovaný interval: 07.11.2017 19:47 Windows Error Reporting Chybný blok 0x3B_nvlddmkm!tlsEntryAcquire, typ 0
Název události: BlueScreen
Reakce: Není k dispozici.
ID souboru CAB: f472d6a1-d107-492b-b7b8-038e27fcaf25

Podpis problému:
P1: 3b
P2: c0000005
P3: fffff80067908ee1
P4: ffff9480c2046320
P5: 0
P6: 10_0_15063
P7: 0_0
P8: 256_1
P9:
P10:

Připojené soubory:
\\?\C:\WINDOWS\Minidump\110717-8281-01.dmp
\\?\C:\Windows\Temp\WER-11609-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4110.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER412F.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4140.tmp.txt

Tyto soubory mohou být k dispozici zde:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_3b_b66e485ba36a74475b9bcfc333f3c02f09c216c_00000000_cab_15fc9182

Symbol analýzy:
Opětovné hledání řešení: 0
ID hlášení: 8490d4e2-22b9-4f33-af40-e9b7af6b2672
Stav hlášení: 268435456
Zakódovaný interval: 26.08.2017 8:56 Windows Error Reporting Chybný blok 0x9F_3_POWER_DOWN_Ddi_dxgkrnl!DpiRequestIoPowerState, typ 0
Název události: BlueScreen
Reakce: Není k dispozici.
ID souboru CAB: cd73e9bc-51b8-4084-b577-9de7f386ab27

Podpis problému:
P1: 9f
P2: 3
P3: ffffe38b737f6060
P4: ffffd081db730870
P5: ffffe38b7b311310
P6: 10_0_15063
P7: 0_0
P8: 256_1
P9:
P10:

Připojené soubory:
\\?\C:\WINDOWS\Minidump\082617-8218-01.dmp
\\?\C:\Windows\Temp\WER-10390-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4D54.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4D64.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4D75.tmp.txt

Tyto soubory mohou být k dispozici zde:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_9f_2ec7dae1b6d54968608b22a6ca5b921ca95b867e_00000000_cab_170c7ca2

Symbol analýzy:
Opětovné hledání řešení: 0
ID hlášení: 0a33579d-1492-44e9-b7ae-9637a48188ad
Stav hlášení: 268435456
Zakódovaný interval:[/quote] Code: 15.11.2017 16:36 Windows Error Reporting Chybný blok AV_R_INVALID_nvlddmkm!tlsEntryRelease, typ 0
Název události: BlueScreen
Reakce: Není k dispozici.
ID souboru CAB: 301018d5-3d78-48a3-9f8b-576525ca5603

Podpis problému:
P1: 50
P2: fffff80b00000000
P3: 0
P4: fffff80bb169779a
P5: 2
P6: 10_0_15063
P7: 0_0
P8: 256_1
P9:
P10:

Připojené soubory:
\\?\C:\WINDOWS\Minidump\111517-8171-01.dmp
\\?\C:\Windows\Temp\WER-11812-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER41FA.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER420A.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER421A.tmp.txt

Tyto soubory mohou být k dispozici zde:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_50_4f37cc6c2fb4631ce85c7ec4163ccbc2c75ab49_00000000_cab_1644920e

Symbol analýzy:
Opětovné hledání řešení: 0
ID hlášení: e1ff73a3-42d9-4904-ae98-e5f1dbd90368
Stav hlášení: 268435456
Zakódovaný interval: 10.06.2017 11:20 Windows Error Reporting Chybný blok LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys_Pascal_3D, typ 0
Název události: LiveKernelEvent
Reakce: Není k dispozici.
ID souboru CAB: 48349092-0438-4a1e-9374-a159e2da8fdf

Podpis problému:
P1: 141
P2: ffffc201a2e64010
P3: fffff8064e8cfb28
P4: 0
P5: 1890
P6: 10_0_15063
P7: 0_0
P8: 256_1
P9:
P10:

Připojené soubory:
\\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20170610-1320.dmp
\\?\C:\Windows\Temp\WER-566778750-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9F3D.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9F4D.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9F6D.tmp.txt
\\?\C:\Windows\Temp\WERE773.tmp.WERDataCollectionStatus.txt

Tyto soubory mohou být k dispozici zde:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_d0a925a968605c9d7a6eab0ee9dff2773286f_00000000_cab_236cee09

Symbol analýzy:
Opětovné hledání řešení: 0
ID hlášení: 7a5b8372-0708-4e70-b649-60786e1e4a5f
Stav hlášení: 268435456
Zakódovaný interval:[/quote]

 

done, I was also updating my pc info meanwhile, should be done now

 

Welcome to Ten Forums BSOD forum:

The debugging of the mini dump files indicated 2 misbehaving drivers.
1 was a hardware driver and 1 was a software driver.
There is insufficient free space on drive C.
There is mismatched RAM.
The BIOS needs updating.
Windows fast startup failed.

For all tests and results please post images into the thread.
If there is a problem posting images please use one drive or drop box share links.

Perform the following steps:

1) Open administrative command prompt and type or copy and paste:
2) sfc /scannow
3) dism /online /cleanup-image /restorehealth
4) chkdsk /scan
5) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread.

6) Modify the free space on Drive C: so that there is at least 25 GB of free space.

7) Turn off windows fast startup:
Turn On or Off Fast Startup in Windows 10 Performance Maintenance Tutorials

8) Uninstall ESET
Uninstallers (removal tools) for common Windows antivirus softwareESET Knowledgebase

9)Turn on Windows defender

10) Make sure that there is no over clocking while troubleshooting.

11) Sometimes there are problems in the bios that produce bsod.
The BIOS: Version/Date American Megatrends Inc. 0503, 1/25/2016
12) Please check to see if this is the most up to date version > update to 2017/11/02 version
13) Post into the thread the URL or hyperlink for the computer's BIOS and drivers.

14) To ensure that there are no improper bios settings please reset the bios.
15) Sometimes there can be failure to boot after resetting the bios.
16) So please make sure your files are backed up.
17) Please make a backup image with Macrium:
Macrium Software | Macrium Reflect Free:
Macrium Software | Macrium Reflect Free
18) Place the backup image onto another drive or into the cloud.

19) And please create a brand new restore point.

How to Clear Your Computers CMOS to Reset BIOS Settings:
How to Clear Your Computers CMOS to Reset BIOS Settings
3 Ways to Reset Your BIOS - wikiHow:
3 Ways to Reset Your BIOS - wikiHow

20) Run memtest86+ version 5.01 for at least 8 passes.
Memtest86+ - Advanced Memory Diagnostic Tool
This may take hours so plan to run it overnight.
Please make sure you use the Memtest86+ version 5.01 with the link below.
Memtest86+ - Advanced Memory Diagnostic Tool
The testing is done not by time but by passes.
The more passes the better.
There are a significant number of false negatives if fewer than 8 passes are made.
A false negative is a test pass when there is malfunctioning RAM.
There is 16 GB of RAM on the computer.
Memtest86+ version 5.01 testing takes approximately 1 - 2 hours /GB RAM
Just 1 error is a fail and you can abort testing.
Then test 1 RAM module at a time in the same DIMM each for 8 or more passes.
When Memtest86+ has completed 8 or more passes use a camera or smart phone camera to take a picture and post an image into the thread.
Memory problems. - Microsoft Community
MemTest86+ - Test RAM BSOD Tutorials

21) The best way to fix the misbehaving Nvidia driver is to uninstall everything Nvidia using Display driver uninstaller and install new drivers from the computer manufacturer's website or from the Nvidia website.
The computer manufacturer's web site is preferred.
When using the Nvidia web site be sure the "clean install" box is checked and only install the graphics driver and the physx driver.
Official Display Driver Uninstaller DDU Download
Display Driver Uninstaller Download version 17.0.7.2
Display Driver Uninstaller: How to use - Windows 7 Help Forums
NVIDIA

Code: 11/7/2017 7:46 PM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Není k dispozici. Cab Id: 0 Problem signature: P1: 3b P2: c0000005 P3: fffff80067908ee1 P4: ffff9480c2046320 P5: 0 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\110717-8281-01.dmp \\?\C:\Windows\Temp\WER-11609-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4110.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER412F.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4140.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_3b_b66e485ba36a74475b9bcfc333f3c02f09c216c_00000000_cab_0344413f Analysis symbol: Rechecking for solution: 0 Report Id: 8490d4e2-22b9-4f33-af40-e9b7af6b2672 Report Status: 4 Hashed bucket: 11/2/2017 6:19 PM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Není k dispozici. Cab Id: 0 Problem signature: P1: 3b P2: c0000005 P3: fffff800783a8ee1 P4: ffffa4001f0f1320 P5: 0 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\110217-6812-01.dmp \\?\C:\Windows\Temp\WER-10171-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER40D1.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER40E1.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER40F2.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_3b_c436ef59ff53b665562fa4e51fe7a1e47c0124c_00000000_cab_034040f1 Analysis symbol: Rechecking for solution: 0 Report Id: 0ed54f28-0ef0-4cf9-bf3f-70a591825679 Report Status: 4 Hashed bucket: 11/4/2017 11:26 PM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Není k dispozici. Cab Id: 0 Problem signature: P1: 3b P2: c0000005 P3: fffff8016cbd8bc4 P4: ffff9281e1fd22f0 P5: 0 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\110517-7375-01.dmp \\?\C:\Windows\Temp\WER-10718-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3DF3.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3E12.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3E13.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_3b_58808e33027e935f7ff1c8d71ddd1bbaad733e_00000000_cab_03403e22 Analysis symbol: Rechecking for solution: 0 Report Id: ee9d4253-a3cc-4d55-9bd1-eed2500c425e Report Status: 4 Hashed bucket: 11/18/2017 11:42 PM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Není k dispozici. Cab Id: 0 Problem signature: P1: 3b P2: c0000005 P3: fffff803f2b68f50 P4: ffff8f81aa559210 P5: 0 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\111917-7031-01.dmp \\?\C:\WINDOWS\TEMP\WER-10546-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3C8C.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3C9B.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3C9C.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_3b_698565e98aab7cdcc8254c39436cfd2d45aa4_00000000_cab_03303cab Analysis symbol: Rechecking for solution: 0 Report Id: 9d91efc8-c9ea-41ba-8e49-6ca246e6ce26 Report Status: 4 Hashed bucket: 11/16/2017 10:58 AM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Není k dispozici. Cab Id: 0 Problem signature: P1: 3b P2: c0000005 P3: fffff80e4aff83b5 P4: ffffe701daacf320 P5: 0 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\111617-7156-01.dmp \\?\C:\Windows\Temp\WER-10343-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3BD0.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3BEF.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3BF0.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_3b_3e1bf182a6add14bffcc6431130d2a2ad60ad48_00000000_cab_03483bef Analysis symbol: Rechecking for solution: 0 Report Id: c838ef4b-bac7-4bc4-9b8b-bf48038ef02c Report Status: 4 Hashed bucket: 11/15/2017 4:35 PM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Není k dispozici. Cab Id: 0 Problem signature: P1: 50 P2: fffff80b00000000 P3: 0 P4: fffff80bb169779a P5: 2 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\111517-8171-01.dmp \\?\C:\Windows\Temp\WER-11812-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER41FA.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER420A.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER421A.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_50_4f37cc6c2fb4631ce85c7ec4163ccbc2c75ab49_00000000_cab_03444219 Analysis symbol: Rechecking for solution: 0 Report Id: e1ff73a3-42d9-4904-ae98-e5f1dbd90368 Report Status: 4 Hashed bucket: 8/26/2017 8:56 AM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Není k dispozici. Cab Id: 0 Problem signature: P1: 9f P2: 3 P3: ffffe38b737f6060 P4: ffffd081db730870 P5: ffffe38b7b311310 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\082617-8218-01.dmp \\?\C:\Windows\Temp\WER-10390-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4D54.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4D64.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4D75.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_9f_2ec7dae1b6d54968608b22a6ca5b921ca95b867e_00000000_cab_03484d74 Analysis symbol: Rechecking for solution: 0 Report Id: 0a33579d-1492-44e9-b7ae-9637a48188ad Report Status: 4 Hashed bucket:[/quote] Code: 11/2/2017 6:19 PM Windows Error Reporting Fault bucket 0x3B_nvlddmkm!mapFind_IMPL, type 0 Event Name: BlueScreen Response: Není k dispozici. Cab Id: 9962156a-a4b3-47a6-b327-320a35373dd0 Problem signature: P1: 3b P2: c0000005 P3: fffff800783a8ee1 P4: ffffa4001f0f1320 P5: 0 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\110217-6812-01.dmp \\?\C:\Windows\Temp\WER-10171-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER40D1.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER40E1.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER40F2.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_3b_c436ef59ff53b665562fa4e51fe7a1e47c0124c_00000000_cab_1564924d Analysis symbol: Rechecking for solution: 0 Report Id: 0ed54f28-0ef0-4cf9-bf3f-70a591825679 Report Status: 268435456 Hashed bucket: 11/16/2017 10:58 AM Windows Error Reporting Fault bucket 0x3B_nvlddmkm!tlsEntryAcquire, type 0 Event Name: BlueScreen Response: Není k dispozici. Cab Id: 09a949c8-43e4-4062-8e7b-fe1ab29b9eea Problem signature: P1: 3b P2: c0000005 P3: fffff80e4aff83b5 P4: ffffe701daacf320 P5: 0 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\111617-7156-01.dmp \\?\C:\Windows\Temp\WER-10343-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3BD0.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3BEF.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3BF0.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_3b_3e1bf182a6add14bffcc6431130d2a2ad60ad48_00000000_cab_16c49366 Analysis symbol: Rechecking for solution: 0 Report Id: c838ef4b-bac7-4bc4-9b8b-bf48038ef02c Report Status: 268435456 Hashed bucket: 11/4/2017 11:26 PM Windows Error Reporting Fault bucket 0x3B_nvlddmkm!tlsEntryAcquire, type 0 Event Name: BlueScreen Response: Není k dispozici. Cab Id: 5ca510c9-8cbf-41e4-a27c-f119dedd3ede Problem signature: P1: 3b P2: c0000005 P3: fffff8016cbd8bc4 P4: ffff9281e1fd22f0 P5: 0 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\110517-7375-01.dmp \\?\C:\Windows\Temp\WER-10718-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3DF3.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3E12.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3E13.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_3b_58808e33027e935f7ff1c8d71ddd1bbaad733e_00000000_cab_16f49049 Analysis symbol: Rechecking for solution: 0 Report Id: ee9d4253-a3cc-4d55-9bd1-eed2500c425e Report Status: 268435456 Hashed bucket: 11/18/2017 11:42 PM Windows Error Reporting Fault bucket 0x3B_nvlddmkm!tlsEntryAcquire, type 0 Event Name: BlueScreen Response: Není k dispozici. Cab Id: 9f21668b-c567-4d60-ad5f-b5ce56aa02a7 Problem signature: P1: 3b P2: c0000005 P3: fffff803f2b68f50 P4: ffff8f81aa559210 P5: 0 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\111917-7031-01.dmp \\?\C:\WINDOWS\TEMP\WER-10546-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3C8C.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3C9B.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3C9C.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_3b_698565e98aab7cdcc8254c39436cfd2d45aa4_00000000_cab_166888b8 Analysis symbol: Rechecking for solution: 0 Report Id: 9d91efc8-c9ea-41ba-8e49-6ca246e6ce26 Report Status: 268435456 Hashed bucket: 11/7/2017 7:47 PM Windows Error Reporting Fault bucket 0x3B_nvlddmkm!tlsEntryAcquire, type 0 Event Name: BlueScreen Response: Není k dispozici. Cab Id: f472d6a1-d107-492b-b7b8-038e27fcaf25 Problem signature: P1: 3b P2: c0000005 P3: fffff80067908ee1 P4: ffff9480c2046320 P5: 0 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\110717-8281-01.dmp \\?\C:\Windows\Temp\WER-11609-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4110.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER412F.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4140.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_3b_b66e485ba36a74475b9bcfc333f3c02f09c216c_00000000_cab_15fc9182 Analysis symbol: Rechecking for solution: 0 Report Id: 8490d4e2-22b9-4f33-af40-e9b7af6b2672 Report Status: 268435456 Hashed bucket: 8/26/2017 8:56 AM Windows Error Reporting Fault bucket 0x9F_3_POWER_DOWN_Ddi_dxgkrnl!DpiRequestIoPowerState, type 0 Event Name: BlueScreen Response: Není k dispozici. Cab Id: cd73e9bc-51b8-4084-b577-9de7f386ab27 Problem signature: P1: 9f P2: 3 P3: ffffe38b737f6060 P4: ffffd081db730870 P5: ffffe38b7b311310 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\082617-8218-01.dmp \\?\C:\Windows\Temp\WER-10390-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4D54.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4D64.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4D75.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_9f_2ec7dae1b6d54968608b22a6ca5b921ca95b867e_00000000_cab_170c7ca2 Analysis symbol: Rechecking for solution: 0 Report Id: 0a33579d-1492-44e9-b7ae-9637a48188ad Report Status: 268435456 Hashed bucket:[/quote] Code: 11/15/2017 4:36 PM Windows Error Reporting Fault bucket AV_R_INVALID_nvlddmkm!tlsEntryRelease, type 0 Event Name: BlueScreen Response: Není k dispozici. Cab Id: 301018d5-3d78-48a3-9f8b-576525ca5603 Problem signature: P1: 50 P2: fffff80b00000000 P3: 0 P4: fffff80bb169779a P5: 2 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\111517-8171-01.dmp \\?\C:\Windows\Temp\WER-11812-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER41FA.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER420A.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER421A.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_50_4f37cc6c2fb4631ce85c7ec4163ccbc2c75ab49_00000000_cab_1644920e Analysis symbol: Rechecking for solution: 0 Report Id: e1ff73a3-42d9-4904-ae98-e5f1dbd90368 Report Status: 268435456 Hashed bucket: 6/10/2017 11:20 AM Windows Error Reporting Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys_Pascal_3D, type 0 Event Name: LiveKernelEvent Response: Není k dispozici. Cab Id: 48349092-0438-4a1e-9374-a159e2da8fdf Problem signature: P1: 141 P2: ffffc201a2e64010 P3: fffff8064e8cfb28 P4: 0 P5: 1890 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20170610-1320.dmp \\?\C:\Windows\Temp\WER-566778750-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9F3D.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9F4D.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9F6D.tmp.txt \\?\C:\Windows\Temp\WERE773.tmp.WERDataCollectionStatus.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_d0a925a968605c9d7a6eab0ee9dff2773286f_00000000_cab_236cee09 Analysis symbol: Rechecking for solution: 0 Report Id: 7a5b8372-0708-4e70-b649-60786e1e4a5f Report Status: 268435456 Hashed bucket:[/quote]
Code: Name NVIDIA GeForce GTX 1060 6GB PNP Device ID PCI\VEN_10DE&DEV_1C03&SUBSYS_37161458&REV_A1\4&2D78AB8F&0&0008 Adapter Type GeForce GTX 1060 6GB, NVIDIA compatible Adapter Description NVIDIA GeForce GTX 1060 6GB Adapter RAM (1,048,576) bytes Installed Drivers C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_c791f781cd94491f\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_c791f781cd94491f\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_c791f781cd94491f\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_c791f781cd94491f\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_c791f781cd94491f\nvldumd.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_c791f781cd94491f\nvldumd.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_c791f781cd94491f\nvldumd.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_c791f781cd94491f\nvldumd.dll Driver Version 23.21.13.8831 INF File oem7.inf (Section136 section) Color Planes Not Available Color Table Entries 4294967296 Resolution 1920 x 1080 x 60 hertz Bits/Pixel 32 Memory Address 0xF6000000-0xF6FFFFFF Memory Address 0xE0000000-0xEFFFFFFF Memory Address 0xF0000000-0xF1FFFFFF I/O Port 0x0000E000-0x0000E07F IRQ Channel IRQ 16 I/O Port 0x000003B0-0x000003BB I/O Port 0x000003C0-0x000003DF Memory Address 0xA0000-0xBFFFF Driver c:\windows\system32\driverstore\filerepository\nv_dispi.inf_amd64_c791f781cd94491f\nvlddmkm.sys (23.21.13.8831, 16.20 MB (16,989,296 bytes), 11/16/2017 12:16 PM)[/quote]

Code: Event[7774]: Log Name: System Source: Microsoft-Windows-Kernel-Boot Date: 2017-08-26T10:56:05.978 Event ID: 29 Task: N/A Level: Error Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: DESKTOP-77GTHS2 Description: Windows failed fast startup with error status 0xC0000001.[/quote] Code: Event[13150]: Log Name: System Source: volmgr Date: 2017-11-16T11:58:20.743 Event ID: 161 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-77GTHS2 Description: Dump file creation failed due to error during dump creation.[/quote] Code: Event[2109]: Log Name: System Source: Display Date: 2017-06-10T13:20:10.678 Event ID: 4101 Task: N/A Level: Warning Opcode: Info Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-77GTHS2 Description: Display driver nvlddmkm stopped responding and has successfully recovered.[/quote] Code: Event[12170]: Log Name: System Source: Microsoft-Windows-WER-SystemErrorReporting Date: 2017-11-02T19:19:27.976 Event ID: 1018 Task: N/A Level: Information Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-77GTHS2 Description: The dump file at location: C:\WINDOWS\MEMORY.DMP was deleted because the disk volume had less than 25 GB free space.[/quote] Code: Event[12345]: Log Name: System Source: Microsoft-Windows-WER-SystemErrorReporting Date: 2017-11-05T00:26:29.268 Event ID: 1018 Task: N/A Level: Information Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-77GTHS2 Description: The dump file at location: C:\WINDOWS\MEMORY.DMP was deleted because the disk volume had less than 25 GB free space.[/quote] Code: Event[12568]: Log Name: System Source: Microsoft-Windows-WER-SystemErrorReporting Date: 2017-11-07T20:46:41.051 Event ID: 1018 Task: N/A Level: Information Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-77GTHS2 Description: The dump file at location: C:\WINDOWS\MEMORY.DMP was deleted because the disk volume had less than 25 GB free space.[/quote] Code: Event[13094]: Log Name: System Source: Microsoft-Windows-WER-SystemErrorReporting Date: 2017-11-15T17:35:55.283 Event ID: 1018 Task: N/A Level: Information Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-77GTHS2 Description: The dump file at location: C:\WINDOWS\MEMORY.DMP was deleted because the disk volume had less than 25 GB free space.[/quote] Code: Event[13626]: Log Name: System Source: Microsoft-Windows-WER-SystemErrorReporting Date: 2017-11-19T00:42:25.879 Event ID: 1018 Task: N/A Level: Information Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-77GTHS2 Description: The dump file at location: C:\WINDOWS\MEMORY.DMP was deleted because the disk volume had less than 25 GB free space.[/quote] Code: Drive: C: Free Space: 16.5 GB Total Space: 113.9 GB File System: NTFS Model: KINGSTON SHFS37A120G[/quote] ehdrv.sys ESET Support: ESET Knowledgebase
Downloads: Downloads for Home
nvlddmkm.sys nVidia Video drivers Download Drivers | NVIDIA
Get from OEM for laptops

 

Code: Windows PowerShellCopyright (C) Microsoft Corporation. All rights reserved. PS C:\WINDOWS\system32> sfc /scannow Beginning system scan. This process will take some time. Beginning verification phase of system scan. Verification 100% complete. Windows Resource Protection did not find any integrity violations. PS C:\WINDOWS\system32> dism /online /cleanup-image /restorehealth Deployment Image Servicing and Management tool Version: 10.0.16299.15 Image Version: 10.0.16299.64 [==========================100.0%==========================] The restore operation completed successfully. The operation completed successfully. PS C:\WINDOWS\system32> chkdsk /scan The type of the file system is NTFS. Stage 1: Examining basic file system structure ... 450816 file records processed. File verification completed. 25372 large file records processed. 0 bad file records processed. Stage 2: Examining file name linkage ... 41894 reparse records processed. 599764 index entries processed. Index verification completed. 0 unindexed files scanned. 0 unindexed files recovered to lost and found. 41894 reparse records processed. Stage 3: Examining security descriptors ... Security descriptor verification completed. 74475 data files processed. CHKDSK is verifying Usn Journal... 33943512 USN bytes processed. Usn Journal verification completed. Windows has scanned the file system and found no problems. No further action is required. 116639743 KB total disk space. 100097272 KB in 266243 files. 194916 KB in 74476 indexes. 0 KB in bad sectors. 563851 KB in use by the system. 65536 KB occupied by the log file. 15783704 KB available on disk. 4096 bytes in each allocation unit. 29159935 total allocation units on disk. 3945926 allocation units available on disk. PS C:\WINDOWS\system32>[/quote]

 

1) What is Xtreme.exe?

2) Since the nvidia driver is shown in every of the last 5 dumps, the problem could be the nvidia driver itself or the graphics card.

Pleas uninstall the nvidia driver using DDU and reinstall:


Display Driver Uninstaller: How to use
Display Driver Uninstaller (DDU) is a small software that can help the user to uninstall the display driver from the users PC. It can uninstall the driver for all the lead display chip developers, viz. Nvidia, AMD and Intel.
Please also check the graphics card using FurMark:





Diagnostic Test

GPU TEST


Run FurMark - GPU Stress Test - Windows 10 Forums





Note Run Furmark for around 30 minutes.

Warning Your GPU temperatures will rise quickly while Furmark is running. Keep a keen eye on them and abort the test if overheating occurs.
Take a Screenshot and post it here.

 

Xtreme.exe is gpu software from gigabyte (my gpu manufacturer)

I have done the driver reinstall with DDU, as well as some other steps from previous post + updated windows to 1709 and reinstalled eset. Now waiting if next BSOD occurs.