Windows 10: BSOD appears after/while playing a game and randomly

Hello.

As the title say, I have multiple BSOD while playing games (Overwatch or ESO), sometime right after I close the game or, more rarely, after I boot up the computer.

The first BSOD (DRIVER_VERIFIER_DETECTED_VIOLATION) I get, was a driver issue with my mouse (Logitech G500s). Name of the driver: lgbusenum.sys.
So I uninstall the program, Logitech Gaming Software and purchased a new mouse from an other brand.

But I still to get other kind of BSOD related to EMORY_MANAGEMENT or KERNEL_SECURITY_CHECK_FAILURE.

Here is the detailed result from WhoCrashed:

On Fri 02/06/2017 22:34:55 your computer crashed
crash dump file: C:\Windows\Minidump\060217-3437-02.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C310)
Bugcheck code: 0x1A (0x41792, 0xFFFFD98000020128, 0x10000, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


On Fri 02/06/2017 22:34:55 your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1A (0x41792, 0xFFFFD98000020128, 0x10000, 0x0)
Error: MEMORY_MANAGEMENT
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Fri 02/06/2017 21:36:33 your computer crashed
crash dump file: C:\Windows\Minidump\060217-3437-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C310)
Bugcheck code: 0x139 (0x3, 0xFFFFBE81C2C9D5F0, 0xFFFFBE81C2C9D548, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The kernel has detected the corruption of a critical data structure.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


Detailed computer:
Asus Z170 Pro Gaming (Last Bios 3402)
i5 6600K @ 4.3Ghz
16 GO DDR4 Fury 2666Mhz
SSD 850 EVO 500GB
GTX 970 EXOC (Last drivers)
Windows 10 64 Pro Build 15063

All drivers are up to date (from Asus website)

I did sfc scannow, no errors
SSD so no CHKDSK ?
Crystal Disk Info say the SSD is 100% Good with blue icon
Recent format (3 days ago)
I did viruses scan and no malwares
I did a 12 hours memtest and no errors

Possibly culprit:
Overclocked my CPU to 4.6 Ghz was stable but the one time, the weather was very hot (36° outside), so may be the CPU was overheating ?
CPU Voltage AUTO with CM (Performance mode)
Seems have BSOD with hot weather

Current temps with HWMonitor:
CPU : Package ~55°C (with games) - 34°C idle
GPU : ~50°C (also with games) - 40°c idle

First issue in almost 2 years

:)

 

Getting random BSODS and getting PAGE_FAULT_IN_NONPAGED_AREA BSOD while installing Windows 7.

Original Title: PAGE_FAULT_IN_NONPAGED_AREA

Computer keeps getting this error after reinstalling windows 10 on new m.2 ssd. Computer gets into BSOD randomly. One moment i maybe playing games and it crashed. Other moments can be when i am just web browsing. Tried installing windows 7 and suddenly this
BSOD appeared PAGE_FAULT_IN_NONPAGED_AREA (FNETHYRAMAS.SYS).

Thanks in advance.

 

While playing game a blue screen appears and receive a message kernel secuirty check failure error

Sir i tryed reset and even clean install this week.

nothing worked

i still found this error.

 

Hello Crowzer *Smile

There are no crash dumps in the log files. This could be because you are running a clean-up program like CCleaner which is deleting the mini-dump files. Please disable it or configure it to not delete mini-dumps.

Remove all overclocking while troubleshooting - if this causes the BSOD to cease it is the most likely cause.

Wait for some more BSODs and then post a new set of files.

 

Ok, I'll do that !
It's bad that ccleaner delete dump files.

 

Change CCleaner so it doesn't do that.

Attachment 138075

 

Also make sure that your dump settings are optimally configured to record dumps:

BSOD Finding and fixing them - Microsoft Community

Download and install whocrashed. Click on tools > crash dump test > type ACCEPT in capital letters. It then creates a BSOD. Then reopen whocrashed and view the analysis. This will confirm that you are optimally setup to record minidump once Ccleaner is modified to no longer clean the needed files.


In another thread all of the logs were in a foreign language and we were not able to read them. If you have the option to create the logs in english we then will be able to review them for both bsod and other problems

 

Hello !
Long time I didn't get any BSOD but now, it back in.

Here the zip file and this time, with the .dump file.

 

The logs are in a foreing language and cannot be scanned or read. Please re-post using English as the default language so that the logs can be troubleshooted:

Language - Add, Remove, and Change in Windows 10 Windows 10 General Tips Tutorials

BSOD - Posting Instructions - Windows 10 Forums

 

My bad.
Here the zip file in English

 

Hi Crowzer ,

It's been approximately 2 months.
Welcome back.

There was 1 bsod mini dump file debugged and this did not display a definitive misbehaving driver.
The event logs however indicate that the Nvidia graphics driver service terminated unexpectedly and the windows error reporting indicated that it was a faulting application.

Windows failed fast start up.

Open administrative command prompt and type or copy and paste:


1) sfc /scannow
2) dism /online /cleanup-image /restorehealth
3) 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
4) 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. Enter the computer's serial or product number and the operating system to view available drivers.

If you use 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

5) Turn off Windows fast startup:


Turn On or Off Fast Startup in Windows 10 Windows 10 Performance Maintenance Tutorials

6) Please post a one drive or drop box share link of the Memory.dmp file:
%SystemRoot%\MEMORY.DMP or C:\Windows\MEMORY.DMP

7) Run HDTune on the drives:

HD Tune website

to check the health,
scan for errors, no quick scan but full scan
run a benchmark.


It may take some time, but please take the time you need to perform it properly.
When above is done please make screenshots of the following
the health,
the error scan,
the benchmark incl. following
transfer rate,
access time,
burst rate,
cpu usage.
Take Screenshot in Windows 10 Windows 10 General Tips Tutorials

8) open administrative command prompt and type or copy and paste: chkdsk /x /f /r
This may take many hours so plan to run overnight
9) post the chkdsk results into the thread:
Read Chkdsk Log in Event Viewer in Windows 10 Windows 10 Performance Maintenance Tutorials

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

Sometimes there are problems in the bios that produce bsod.


11) To ensure that there are no improper bios settings please reset the bios.


Sometimes there can be failure to boot after resetting the bios.

12) So please make sure your files are backed up.

13) Please make a backup image with Macrium:
Macrium Software | Macrium Reflect Free:
Macrium Software | Your Image is Everything

14) And please create a 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



15) Please update the system specs:
How To Fill Out Your System Specs
How To Fill Out Your System Specs
System Specs - Fill in at Ten Forums:
System Specs - Fill in at Ten Forums Windows 10 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

Please also include information on anything connected by wireless or wired to the computer: headset, xbox, printer, etc.








Code: Windows failed fast startup with error status 0xC00000D4.[/quote] Code: Event[10283]: Log Name: System Source: Microsoft-Windows-Kernel-Boot Date: 2017-08-28T16:16:05.656 Event ID: 29 Task: N/A Level: Error Opcode: Info Keyword: N/A User: S-1-5-18 User Name: AUTORITE NT\Système Computer: DESKTOP-F9HD6NA Description: Windows failed fast startup with error status 0xC00000D4.[/quote] Code: Event[8283]: Log Name: System Source: Disk Date: 2017-07-29T13:02:01.877 Event ID: 51 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-F9HD6NA Description: An error was detected on device \Device\Harddisk1\DR1 during a paging operation.[/quote] Code: Event[10360]: Log Name: System Source: Service Control Manager Date: 2017-08-28T19:56:16.740 Event ID: 7031 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-F9HD6NA Description: The NVIDIA Display Container LS service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 1000 milliseconds: Redémarrer le service.[/quote] Code: Windows Error Reporting:+++ WER0 +++:Fault bucket 116432538090, type 5Event Name: BEX64Response: Non disponibleCab Id: 0Problem signature1: NVDisplay.Container.exeP2: 1.2.0.0P3: 599b62c4P4: NvXDCore.dll_unloadedP5: 8.17.13.8541P6: 599b6624P7: 00000000000c0ab1P8: c0000005P9: 0000000000000008P10: +++ WER1 +++:Fault bucket , type 0Event Name: BEX64Response: Non disponibleCab Id: 0Problem signature1: NVDisplay.Container.exeP2: 1.2.0.0P3: 599b62c4P4: NvXDCore.dll_unloadedP5: 8.17.13.8541P6: 599b6624P7: 00000000000c0ab1P8: c0000005P9: 0000000000000008P10:[/quote] Code: 8/28/2017 5:56 PM Application Error Faulting application name: NVDisplay.Container.exe, version: 1.2.0.0, time stamp: 0x599b62c4 Faulting module name: NvXDCore.dll_unloaded, version: 8.17.13.8541, time stamp: 0x599b6624 Exception code: 0xc0000005 Fault offset: 0x00000000000c0ab1 Faulting process id: 0x644 Faulting application start time: 0x01d32008325281be Faulting application path: C:\Program Files\NVIDIA Corporation\Display.NvContainer\NVDisplay.Container.exe Faulting module path: NvXDCore.dll Report Id: 0ef73541-f8bc-4a91-873c-c756419cc49c Faulting package full name: Faulting package-relative application ID:[/quote] Code: 6/2/2017 7:40 PM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Non disponible Cab Id: 0 Problem signature: P1: 139 P2: 3 P3: ffffbe81c2c9d5f0 P4: ffffbe81c2c9d548 P5: 0 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\060217-3437-01.dmp \\?\C:\Windows\Temp\WER-4078-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1C03.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1C13.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1C14.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_139_5e2ec7c44b2d56524f48b80fcb92b68b6565d0_00000000_cab_291adb14 Analysis symbol: Rechecking for solution: 0 Report Id: 78c87695-42a8-4136-b3ca-0a9c0a6bab33 Report Status: 2049 Hashed bucket:6/2/2017 7:37 PM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Non disponible Cab Id: 0 Problem signature: P1: 139 P2: 3 P3: ffffbe81c2c9d5f0 P4: ffffbe81c2c9d548 P5: 0 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\060217-3437-01.dmp \\?\C:\Windows\Temp\WER-4078-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1C03.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1C13.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1C14.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_139_5e2ec7c44b2d56524f48b80fcb92b68b6565d0_00000000_02fc1c13 Analysis symbol: Rechecking for solution: 0 Report Id: 78c87695-42a8-4136-b3ca-0a9c0a6bab33 Report Status: 4 Hashed bucket:6/2/2017 8:35 PM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Non disponible Cab Id: 0 Problem signature: P1: 1a P2: 41792 P3: ffffd98000020128 P4: 10000 P5: 0 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\060217-3437-02.dmp \\?\C:\Windows\Temp\WER-3921-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1ED2.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1EE2.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1EE3.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_1a_217d4ebcfbbd8989a43fcbd0d48d959f67396865_00000000_cab_1f782068 Analysis symbol: Rechecking for solution: 0 Report Id: d0409615-0573-4750-a6a4-addd8556f155 Report Status: 2049 Hashed bucket:6/2/2017 8:35 PM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Non disponible Cab Id: 0 Problem signature: P1: 1a P2: 41792 P3: ffffd98000020128 P4: 10000 P5: 0 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\060217-3437-02.dmp \\?\C:\Windows\Temp\WER-3921-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1ED2.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1EE2.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1EE3.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_1a_217d4ebcfbbd8989a43fcbd0d48d959f67396865_00000000_02ec1ee2 Analysis symbol: Rechecking for solution: 0 Report Id: d0409615-0573-4750-a6a4-addd8556f155 Report Status: 4 Hashed bucket:6/1/2017 7:46 PM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Non disponible Cab Id: 0 Problem signature: P1: 3b P2: c0000005 P3: ffff8eea7be5a56b P4: ffff9580629fec90 P5: 0 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\060117-3265-01.dmp \\?\C:\Windows\Temp\WER-4937-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1CFD.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1D0D.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1D0E.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_3b_6e2d3e535fc3c8cbca5582b4ede2a1c088bed9_00000000_cab_098ad92f Analysis symbol: Rechecking for solution: 0 Report Id: d85bfcef-0f2d-4df5-bde5-a8fcb0540918 Report Status: 2049 Hashed bucket:6/1/2017 7:43 PM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Non disponible Cab Id: 0 Problem signature: P1: 3b P2: c0000005 P3: ffff8eea7be5a56b P4: ffff9580629fec90 P5: 0 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\060117-3265-01.dmp \\?\C:\Windows\Temp\WER-4937-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1CFD.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1D0D.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1D0E.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_3b_6e2d3e535fc3c8cbca5582b4ede2a1c088bed9_00000000_02f81d0d Analysis symbol: Rechecking for solution: 0 Report Id: d85bfcef-0f2d-4df5-bde5-a8fcb0540918 Report Status: 4 Hashed bucket:8/28/2017 2:19 PM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Non disponible Cab Id: 0 Problem signature: P1: 9c P2: 0 P3: ffff9401e0b0a820 P4: 0 P5: 0 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\082817-3453-01.dmp \\?\C:\Windows\Temp\WER-3843-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER20D6.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER20E5.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER20E6.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_9c_fecfda5460d7bbd563681d3c641ba556ac85c7a5_00000000_cab_12b6d94f Analysis symbol: Rechecking for solution: 0 Report Id: 94444363-dbc4-470c-8270-d22f92377c71 Report Status: 2049 Hashed bucket:8/28/2017 2:13 PM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Non disponible Cab Id: 0 Problem signature: P1: 9c P2: 0 P3: ffff9401e0b0a820 P4: 0 P5: 0 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\082817-3453-01.dmp \\?\C:\Windows\Temp\WER-3843-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER20D6.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER20E5.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER20E6.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_9c_fecfda5460d7bbd563681d3c641ba556ac85c7a5_00000000_02fc20e5 Analysis symbol: Rechecking for solution: 0 Report Id: 94444363-dbc4-470c-8270-d22f92377c71 Report Status: 4 Hashed bucket:6/1/2017 8:05 PM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Non disponible Cab Id: 0 Problem signature: P1: c4 P2: 2004 P3: ffffb808d094b248 P4: fffff806ea8501f0 P5: ffffd881e9b8f028 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\060117-3109-01.dmp \\?\C:\Windows\Temp\WER-4093-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1CDE.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1CE0.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1CF1.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_c4_c9b55d67795322dd19c253dce1249b5138db274_00000000_cab_0836d690 Analysis symbol: Rechecking for solution: 0 Report Id: 123ddc7a-ef03-42a5-9144-6f6b435ff3a8 Report Status: 2049 Hashed bucket:6/1/2017 8:02 PM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Non disponible Cab Id: 0 Problem signature: P1: c4 P2: 2004 P3: ffffb808d094b248 P4: fffff806ea8501f0 P5: ffffd881e9b8f028 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\060117-3109-01.dmp \\?\C:\Windows\Temp\WER-4093-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1CDE.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1CE0.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1CF1.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_c4_c9b55d67795322dd19c253dce1249b5138db274_00000000_02f41cee Analysis symbol: Rechecking for solution: 0 Report Id: 123ddc7a-ef03-42a5-9144-6f6b435ff3a8 Report Status: 4 Hashed bucket:6/1/2017 9:49 PM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Non disponible Cab Id: 0 Problem signature: P1: c4 P2: 2004 P3: ffffc70fc13cc068 P4: fffff80d2ade01f0 P5: ffffd801d27e8028 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\060117-11031-01.dmp \\?\C:\Windows\Temp\WER-12984-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER56BB.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER56BD.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER56CD.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_c4_3d9f1c3728ed4e1845991818a1fce7142f43519_00000000_cab_12a2d6de Analysis symbol: Rechecking for solution: 0 Report Id: 27875bbe-0dcf-4d7f-9a3f-7a3736d19448 Report Status: 2049 Hashed bucket:6/1/2017 9:38 PM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Non disponible Cab Id: 0 Problem signature: P1: c4 P2: 2004 P3: ffffc70fc13cc068 P4: fffff80d2ade01f0 P5: ffffd801d27e8028 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\060117-11031-01.dmp \\?\C:\Windows\Temp\WER-12984-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER56BB.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER56BD.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER56CD.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_c4_3d9f1c3728ed4e1845991818a1fce7142f43519_00000000_030c56ca Analysis symbol: Rechecking for solution: 0 Report Id: 27875bbe-0dcf-4d7f-9a3f-7a3736d19448 Report Status: 4 Hashed bucket:[/quote] Code: 6/11/2017 9:01 PM Application Error Faulting application name: NVDisplay.Container.exe, version: 1.2.0.0, time stamp: 0x591d35cc Faulting module name: NvXDCore.dll_unloaded, version: 8.17.13.8233, time stamp: 0x591d3473 Exception code: 0xc0000005 Fault offset: 0x00000000000c1951 Faulting process id: 0x624 Faulting application start time: 0x01d2dd088931db89 Faulting application path: C:\Program Files\NVIDIA Corporation\Display.NvContainer\NVDisplay.Container.exe Faulting module path: NvXDCore.dll Report Id: 8763741a-c835-4074-ab68-c7a5ef67c986 Faulting package full name: Faulting package-relative application ID:7/28/2017 4:15 PM Application Error Faulting application name: NVDisplay.Container.exe, version: 1.2.0.0, time stamp: 0x596e8f96 Faulting module name: combase.dll, version: 10.0.15063.296, time stamp: 0x91412db8 Exception code: 0xc0000005 Fault offset: 0x000000000001ded1 Faulting process id: 0xa40 Faulting application start time: 0x01d30528236ef5e6 Faulting application path: C:\Program Files\NVIDIA Corporation\Display.NvContainer\NVDisplay.Container.exe Faulting module path: C:\Windows\System32\combase.dll Report Id: f5e84fea-fa33-4fc7-84d0-9bd99223c6a0 Faulting package full name: Faulting package-relative application ID:8/28/2017 5:56 PM Application Error Faulting application name: NVDisplay.Container.exe, version: 1.2.0.0, time stamp: 0x599b62c4 Faulting module name: NvXDCore.dll_unloaded, version: 8.17.13.8541, time stamp: 0x599b6624 Exception code: 0xc0000005 Fault offset: 0x00000000000c0ab1 Faulting process id: 0x644 Faulting application start time: 0x01d32008325281be Faulting application path: C:\Program Files\NVIDIA Corporation\Display.NvContainer\NVDisplay.Container.exe Faulting module path: NvXDCore.dll Report Id: 0ef73541-f8bc-4a91-873c-c756419cc49c Faulting package full name: Faulting package-relative application ID:[/quote] Code: Name NVIDIA GeForce GTX 970PNP Device ID PCI\VEN_10DE&DEV_13C2&SUBSYS_113110DE&REV_A1\4&2D78AB8F&0&0008Adapter Type GeForce GTX 970, NVIDIA compatibleAdapter Description NVIDIA GeForce GTX 970Adapter RAM (1,048,576) bytesInstalled Drivers C:\Windows\System32\DriverStore\FileRepository\nv_desktop_ref4i.inf_amd64_ded2c0db75cf859b\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nv_desktop_ref4i.inf_amd64_ded2c0db75cf859b\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nv_desktop_ref4i.inf_amd64_ded2c0db75cf859b\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nv_desktop_ref4i.inf_amd64_ded2c0db75cf859b\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nv_desktop_ref4i.inf_amd64_ded2c0db75cf859b\nvldumd.dll,C:\Windows\System32\DriverStore\FileRepository\nv_desktop_ref4i.inf_amd64_ded2c0db75cf859b\nvldumd.dll,C:\Windows\System32\DriverStore\FileRepository\nv_desktop_ref4i.inf_amd64_ded2c0db75cf859b\nvldumd.dll,C:\Windows\System32\DriverStore\FileRepository\nv_desktop_ref4i.inf_amd64_ded2c0db75cf859b\nvldumd.dllDriver Version 22.21.13.8541INF File oem13.inf (Section024 section)Color Planes Not AvailableColor Table Entries 4294967296Resolution 1920 x 1080 x 60 hertzBits/Pixel 32Memory Address 0xF6000000-0xF70FFFFFMemory Address 0xE0000000-0xF1FFFFFFMemory Address 0xF0000000-0xF1FFFFFFI/O Port 0x0000E000-0x0000EFFFIRQ Channel IRQ 16I/O Port 0x000003B0-0x000003BBI/O Port 0x000003C0-0x000003DFMemory Address 0xA0000-0xBFFFFDriver c:\windows\system32\driverstore\filerepository\nv_desktop_ref4i.inf_amd64_ded2c0db75cf859b\nvlddmkm.sys (22.21.13.8541, 14.88 MB (15,600,248 bytes), 8/25/2017 7:30 PM)[/quote]

 

Thank for your reply! It really help me!

1), 2) & 3):

4) Done.

5) Done.

6) Will do later.

7)

benchmark :
Attachment 151546

Health :
Attachment 151547


Error scan :
Attachment 151548



8) & 9) Will do later.

10) I think the BSOD came from that. Actually, I tried to overclock my CPU to 4.6Ghz and it failled with BSOD in games. Now, my CPU is clocked to 4.5Ghz, and it runs smooth. The BSOD appeared right after (I meant in games) O/C over than 4.5Ghz.

In fact, I run it to 4.5Ghz over 3 months and no issues so far.

11) Done.

12), 13) & 14) Yes, all my files are backed up on my external DD.

15) Done