Windows 10: Getting green boxes on monitor, then pc restarts.

I have Asus Gtx 650Ti Boost, after 4-6 hours of playing game or browsing internet, on my monitor i get green boxes all over the screen then pc restarts, and after restart pc boots normal without lines, one day after restart i let pc works for about 12 hours, but everything is normal. I replaced the thermal paste, and replacing thermal paste didn't help. Then i tried to reflow the card i used heat gun for 10 min, but still i didn't fix the problem. If anyone knows how to fix problem let me know. Here is some pic of problem https://imgur.com/a/7zvkY

:)

 

windows 10 update 10/17/2017

windows 10 home i7-6700 3.40 ghz 64 bit asus version 1709

After installing the latest update 10/17/2017.

when my pc wakes up from sleep my HDMI monitor has red and green vertical lines and the mouse has a square box. There is nothing I can do with it then. After force restart everything works find until pc goes to sleep again. I have remove the HDMI cable and
plug it back in, the monitor said it has no signal.

 

Green Screen

I was waiting to get the new build 15007 and the PC just shut down and gave me a green screen, after I restart the PC I got another green screen after I restarted the PC.

It's a nonstop Green screen.

 

Run the beta version of the log collector and post a zip into this thread.
(extract > open)
If you have problems opening the beta log collector then use the DM log collector:
BSOD - Posting Instructions - Windows 10 Forums

Update the specs in the "My Computer" section:
System Specs - Fill in at Ten Forums:
System Specs - Fill in at Ten Forums Windows 10 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, USB wireless network card, etc.)

 

-Tue_03_06_2018_234646_77.zip

 

There were no BSOD mini or memory dump files.
The logs start on January 28, 2018 had displayed imminent drive failure since Jaunuary 28, 2018.
The logs displayed problems with the Nvidia GPU since January, 28, 2018.
The logs displayed numerous BSOD.
The bugchecks were:
119
133
124
There were problems with dump file formation.
.
For all tests /steps please post images into the thread.
If there are any problems posting images please use one drive or drop box share links.

1) Open administrative command prompt and type or copy and paste:
2) sfc /scannow
3) dism /online /cleanup-image /scanhealth
4) dism /online /cleanup-image /restoreheath
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) Make a brand new restore point

7) Backup all files to another drive or to the cloud

8) Make a backup image using Macrium:
Macrium Software | Macrium Reflect Free

9) Make sure that there is no over clocking during the troubleshooting

10) Run HD Tune:
HD Tune website
Post images into the thread for test results on each of these tabs:
a) Health (SMART)
b) Benchmark
c) Full error scan

11) Sometimes there are problems in the bios that produce bsod.
The BIOS: Version/Date American Megatrends Inc. V17.17, 4/22/2015 SMBIOS Version 2.6
12) Please check to see if this is the most up to date version.

13) Open the website for the computer or motherboard manufacturer to view the drivers and post a URL or hyperlink into the thread.

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) Make sure that you have backed up the files and made a backed up image
.
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

17) If the computer has Ccleaner > click windows tab > scroll down to system and advanced > post an image into the thread

18) In the left lower corner search type clean > open disk cleanup > scroll up and down > post images into the thread

19) In the left lower corner search type: system or system control > open system control panel > on the left pane click advanced system settings
a) > on the advanced tab under startup and recovery > click settings > post an image of the startup and recovery into the thread.
b) > on the advanced tab under performance > click on settings > under performance options > click on the advanced tab > under virtual memory > click on change > post an image of the virtual memory tab into the thread

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.
a) 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 8 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.
b) When Memtest86+ version 5.01 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 Windows 10 Tutorials

21) Open administrative command prompt and type or copy and paste:
chkdsk /x /f /r
This may take many hours so plan to run overnight

C:\Windows\system32>chkdsk /x /f /r
The type of the file system is NTFS.
Cannot lock current drive.

Chkdsk cannot run because the volume is in use by another
process. Would you like to schedule this volume to be
checked the next time the system restarts? (Y/N)

Type: Y
reboot

22) Use the information in this link to find the chkdsk report in the event viewer. Copy and paste > notepad > save to the desktop > post into the thread
Read Chkdsk Log in Event Viewer in Windows 10 Windows 10 Tutorials



Code: Event[415]: Log Name: System Source: Disk Date: 2018-01-28T02:06:18.938 Event ID: 52 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-LJRBNPL Description: The driver has detected that device \Device\Harddisk0\DR0 has predicted that it will fail. Immediately back up your data and replace your hard disk drive. A failure may be imminent.[/quote] Code: Event[416]: Log Name: System Source: Microsoft-Windows-DiskDiagnostic Date: 2018-01-28T02:06:20.223 Event ID: 1 Task: N/A Level: Critical Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: DESKTOP-LJRBNPL Description: Windows Disk Diagnostic detected a S.M.A.R.T. fault on disk SAMSUNG HD502HJ ATA Device (volumes C:\;E:\). This disk might fail; back up your computer now. All data on the hard disk, including files, documents, pictures, programs, and settings might be lost if your hard disk fails. To determine if the hard disk needs to be repaired or replaced, contact the manufacturer of your computer. If you can't back up (for example, you have no CDs or other backup media), you should shut down your computer and restart when you have backup media available. In the meantime, do not save any critical files to this disk.[/quote] Code: Event[699]: Log Name: System Source: Service Control Manager Date: 2018-01-28T17:16:41.408 Event ID: 7023 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-LJRBNPL Description: The NvContainerLocalSystem service terminated with the following error: A generic command executable returned a result that indicates failure.[/quote] Code: Event[868]: Log Name: System Source: volmgr Date: 2018-01-29T17:42:34.330 Event ID: 46 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-LJRBNPL Description: Crash dump initialization failed![/quote] Code: Event[6824]: Log Name: System Source: Disk Date: 2018-03-06T22:19:50.928 Event ID: 52 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: COF1 Description: The driver has detected that device \Device\Harddisk0\DR0 has predicted that it will fail. Immediately back up your data and replace your hard disk drive. A failure may be imminent.[/quote] Code: Event[6649]: Log Name: System Source: Microsoft-Windows-DiskDiagnostic Date: 2018-03-05T21:25:18.264 Event ID: 1 Task: N/A Level: Critical Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: COF1 Description: Windows Disk Diagnostic detected a S.M.A.R.T. fault on disk SAMSUNG HD502HJ ATA Device (volumes C:\;E:\). This disk might fail; back up your computer now. All data on the hard disk, including files, documents, pictures, programs, and settings might be lost if your hard disk fails. To determine if the hard disk needs to be repaired or replaced, contact the manufacturer of your computer. If you can't back up (for example, you have no CDs or other backup media), you should shut down your computer and restart when you have backup media available. In the meantime, do not save any critical files to this disk.[/quote] Code: Event[541]: Log Name: System Source: Display Date: 2018-01-28T16:00:17.479 Event ID: 4101 Task: N/A Level: Warning Opcode: Info Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-LJRBNPL Description: Display driver nvlddmkm stopped responding and has successfully recovered.[/quote] Code: Event[6517]: Log Name: System Source: Display Date: 2018-03-03T14:41:28.450 Event ID: 4101 Task: N/A Level: Warning Opcode: Info Keyword: Classic User: N/A User Name: N/A Computer: COF1 Description: Display driver nvlddmkm stopped responding and has successfully recovered.Event[6518]: Log Name: System Source: Display Date: 2018-03-03T14:41:31.482 Event ID: 4101 Task: N/A Level: Warning Opcode: Info Keyword: Classic User: N/A User Name: N/A Computer: COF1 Description: Display driver nvlddmkm stopped responding and has successfully recovered.Event[6519]: Log Name: System Source: Display Date: 2018-03-03T14:41:34.502 Event ID: 4101 Task: N/A Level: Warning Opcode: Info Keyword: Classic User: N/A User Name: N/A Computer: COF1 Description: Display driver nvlddmkm stopped responding and has successfully recovered.[/quote] Code: Event[3186]: Log Name: System Source: Microsoft-Windows-WHEA-Logger Date: 2018-02-12T23:42:49.697 Event ID: 20 Task: N/A Level: Error Opcode: Info Keyword: N/A User: S-1-5-19 User Name: NT AUTHORITY\LOCAL SERVICE Computer: COF1 Description: A fatal hardware error has occurred.Component: AMD NorthbridgeError Source: Machine Check ExceptionError Type: 11Processor APIC ID: 0The details view of this entry contains further information.[/quote] Code: Event[6480]: Log Name: System Source: Microsoft-Windows-WER-SystemErrorReporting Date: 2018-03-03T14:28:54.888 Event ID: 1005 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: COF1 Description: Unable to produce a minidump file from the full dump file.[/quote] Code: 2/13/2018 1:44 PM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 119 P2: 2 P3: ffffffffc000000d P4: ffff888cc3dcd960 P5: ffffa286b80b36f0 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\021318-20375-01.dmp \\?\C:\Windows\TEMP\WER-247859-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4757.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4787.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER47B7.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_119_8091397ae5c8b9651bdf858f65dbdcf1d86c1768_00000000_cab_1f7c4ac1 Analysis symbol: Rechecking for solution: 0 Report Id: 581db7ff-bcc1-46c2-bca4-ba9073392393 Report Status: 2049 Hashed bucket:2/13/2018 1:44 PM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 119 P2: 2 P3: ffffffffc000000d P4: ffff888cc3dcd960 P5: ffffa286b80b36f0 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\021318-20375-01.dmp \\?\C:\Windows\TEMP\WER-247859-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4757.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4787.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER47B7.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_119_8091397ae5c8b9651bdf858f65dbdcf1d86c1768_00000000_036047c3 Analysis symbol: Rechecking for solution: 0 Report Id: 581db7ff-bcc1-46c2-bca4-ba9073392393 Report Status: 4 Hashed bucket: 2/1/2018 10:47 AM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 119 P2: 5 P3: ffff9a81556eb000 P4: ffff9a8155ef7ad0 P5: 1cc20 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\020118-22109-01.dmp \\?\C:\Windows\TEMP\WER-116515-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD057.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD058.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD078.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_119_ee92b74c68aa908f3d47211c81c7b7e9fc14ea_00000000_cab_050ed6fd Analysis symbol: Rechecking for solution: 0 Report Id: ffbbe75a-c9e9-45f3-8e83-dab61814ddb9 Report Status: 2049 Hashed bucket: 2/1/2018 10:47 AM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 119 P2: 5 P3: ffff9a81556eb000 P4: ffff9a8155ef7ad0 P5: 1cc20 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\020118-22109-01.dmp \\?\C:\Windows\TEMP\WER-116515-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD057.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD058.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD078.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_119_ee92b74c68aa908f3d47211c81c7b7e9fc14ea_00000000_032ed075 Analysis symbol: Rechecking for solution: 0 Report Id: ffbbe75a-c9e9-45f3-8e83-dab61814ddb9 Report Status: 4 Hashed bucket: 2/27/2018 9:52 PM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 119 P2: 5 P3: ffffca8c9e0a0000 P4: ffffca8c9e0b3ad0 P5: 24212 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\022718-22796-01.dmp \\?\C:\Windows\TEMP\WER-312656-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1A85.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1AB5.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1AD5.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_119_3b4d4fe8c7c50523e754f47e5e27ae81bfe36e_00000000_cab_11891f09 Analysis symbol: Rechecking for solution: 0 Report Id: 0d525a2e-dc21-4046-90dc-6c1f8b8d3caa Report Status: 2049 Hashed bucket: 2/27/2018 9:52 PM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 119 P2: 5 P3: ffffca8c9e0a0000 P4: ffffca8c9e0b3ad0 P5: 24212 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\022718-22796-01.dmp \\?\C:\Windows\TEMP\WER-312656-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1A85.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1AB5.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1AD5.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_119_3b4d4fe8c7c50523e754f47e5e27ae81bfe36e_00000000_03711ad2 Analysis symbol: Rechecking for solution: 0 Report Id: 0d525a2e-dc21-4046-90dc-6c1f8b8d3caa Report Status: 4 Hashed bucket: 2/23/2018 9:52 PM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 119 P2: 5 P3: ffffe00b2d7a1000 P4: ffffe00b2d78e800 P5: 88026 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\022318-19703-01.dmp \\?\C:\Windows\TEMP\WER-126734-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1EA6.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1F53.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1FD1.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_119_af692963b0e9356de9c4a9c544857ba8d0197d_00000000_cab_1a37e187 Analysis symbol: Rechecking for solution: 0 Report Id: c3978896-948c-48b6-aa69-202fd8d34e56 Report Status: 2049 Hashed bucket: 2/23/2018 9:51 PM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 119 P2: 5 P3: ffffe00b2d7a1000 P4: ffffe00b2d78e800 P5: 88026 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\022318-19703-01.dmp \\?\C:\Windows\TEMP\WER-126734-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1EA6.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1F53.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1FD1.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_119_af692963b0e9356de9c4a9c544857ba8d0197d_00000000_0363204b Analysis symbol: Rechecking for solution: 0 Report Id: c3978896-948c-48b6-aa69-202fd8d34e56 Report Status: 4 Hashed bucket: 1/30/2018 3:39 PM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 119 P2: 5 P3: ffffe20cc8838000 P4: ffffe20ccb3e8ad0 P5: 27e3b P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\013018-25531-01.dmp \\?\C:\Windows\TEMP\WER-248437-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2E33.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2E36.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2E57.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_119_8b3f515aab0d5e8aba50e841e1bfde87e25692_00000000_cab_238c3063 Analysis symbol: Rechecking for solution: 0 Report Id: fb268aa0-c40e-4564-8c7d-3d2d17adc4e4 Report Status: 2049 Hashed bucket: 1/30/2018 3:39 PM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 119 P2: 5 P3: ffffe20cc8838000 P4: ffffe20ccb3e8ad0 P5: 27e3b P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\013018-25531-01.dmp \\?\C:\Windows\TEMP\WER-248437-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2E33.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2E36.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2E57.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_119_8b3f515aab0d5e8aba50e841e1bfde87e25692_00000000_03442e6f Analysis symbol: Rechecking for solution: 0 Report Id: fb268aa0-c40e-4564-8c7d-3d2d17adc4e4 Report Status: 4 Hashed bucket: 2/11/2018 3:06 PM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 119 P2: a P3: 106985 P4: 106986 P5: ffff9a06efddf010 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\021118-19750-01.dmp \\?\C:\Windows\TEMP\WER-246609-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER13F3.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1403.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1433.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_119_8ee53d69f66b435322c5909ee05931a9cab1635_00000000_cab_1bb81ccb Analysis symbol: Rechecking for solution: 0 Report Id: 83b84141-3e95-48b2-b3bf-ee39b1e6dcc7 Report Status: 2049 Hashed bucket: 2/11/2018 3:05 PM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 119 P2: a P3: 106985 P4: 106986 P5: ffff9a06efddf010 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\021118-19750-01.dmp \\?\C:\Windows\TEMP\WER-246609-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER13F3.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1403.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1433.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_119_8ee53d69f66b435322c5909ee05931a9cab1635_00000000_03301430 Analysis symbol: Rechecking for solution: 0 Report Id: 83b84141-3e95-48b2-b3bf-ee39b1e6dcc7 Report Status: 4 Hashed bucket: 2/21/2018 6:59 PM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 124 P2: 0 P3: ffff980d27199038 P4: 0 P5: 0 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\022018-25656-01.dmp \\?\C:\Windows\TEMP\WER-36687-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2FD0.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER305D.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER306D.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_124_f03f12d92aaaf7c1f46fc9660dabd3410f81c_00000000_cab_0321fb2c Analysis symbol: Rechecking for solution: 0 Report Id: 5a78fe3d-1422-4dc1-ba4b-e12884204d35 Report Status: 2049 Hashed bucket: 2/20/2018 7:54 PM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 124 P2: 0 P3: ffff980d27199038 P4: 0 P5: 0 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\022018-25656-01.dmp \\?\C:\Windows\TEMP\WER-36687-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2FD0.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER305D.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER306D.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_124_f03f12d92aaaf7c1f46fc9660dabd3410f81c_00000000_037a309b Analysis symbol: Rechecking for solution: 0 Report Id: 5a78fe3d-1422-4dc1-ba4b-e12884204d35 Report Status: 4 Hashed bucket: 2/13/2018 12:56 PM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 124 P2: 0 P3: ffffa286b5eb08f8 P4: 0 P5: 0 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\021218-19609-01.dmp \\?\C:\Windows\TEMP\WER-27953-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF1FC.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF24A.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF25B.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_124_aea77d4daaa375262dcb13de36ca7a26747f99b_00000000_cab_00f2d2c5 Analysis symbol: Rechecking for solution: 0 Report Id: af2a3c6d-1210-4d1c-a7aa-e4eb8ed54263 Report Status: 2049 Hashed bucket: 2/12/2018 10:44 PM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 124 P2: 0 P3: ffffa286b5eb08f8 P4: 0 P5: 0 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\021218-19609-01.dmp \\?\C:\Windows\TEMP\WER-27953-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF1FC.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF24A.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF25B.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_124_aea77d4daaa375262dcb13de36ca7a26747f99b_00000000_0365f269 Analysis symbol: Rechecking for solution: 0 Report Id: af2a3c6d-1210-4d1c-a7aa-e4eb8ed54263 Report Status: 4 Hashed bucket: 2/23/2018 6:52 PM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 124 P2: 0 P3: ffffe00b2b5058f8 P4: 0 P5: 0 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\022218-20140-01.dmp \\?\C:\Windows\TEMP\WER-28921-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9198.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER91C8.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER91E8.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_124_f6bf70d3fe4ef9817aa8ad2c655c5be355555c_00000000_cab_1f4a757d Analysis symbol: Rechecking for solution: 0 Report Id: 461c01b5-5212-4580-b246-8e99f89afb76 Report Status: 2049 Hashed bucket: 2/22/2018 9:49 PM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 124 P2: 0 P3: ffffe00b2b5058f8 P4: 0 P5: 0 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\022218-20140-01.dmp \\?\C:\Windows\TEMP\WER-28921-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9198.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER91C8.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER91E8.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_124_f6bf70d3fe4ef9817aa8ad2c655c5be355555c_00000000_035e9205 Analysis symbol: Rechecking for solution: 0 Report Id: 461c01b5-5212-4580-b246-8e99f89afb76 Report Status: 4 Hashed bucket: 2/9/2018 1:47 PM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 133 P2: 1 P3: 1e00 P4: fffff80090a9b370 P5: 0 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\020918-19703-01.dmp \\?\C:\Windows\TEMP\WER-166703-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER22B1.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER22B6.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER22E6.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_133_82127033fad52021f96533465f995281c2db34a_00000000_cab_16f7424a Analysis symbol: Rechecking for solution: 0 Report Id: d3d8c077-3658-424a-8b1e-ac0c7e4448a0 Report Status: 2049 Hashed bucket: 2/9/2018 1:47 PM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 133 P2: 1 P3: 1e00 P4: fffff80090a9b370 P5: 0 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\020918-19703-01.dmp \\?\C:\Windows\TEMP\WER-166703-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER22B1.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER22B6.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER22E6.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_133_82127033fad52021f96533465f995281c2db34a_00000000_033322ea Analysis symbol: Rechecking for solution: 0 Report Id: d3d8c077-3658-424a-8b1e-ac0c7e4448a0 Report Status: 4 Hashed bucket: 2/10/2018 3:00 PM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 133 P2: 1 P3: 1e00 P4: fffff801c008d370 P5: 0 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\021018-19781-01.dmp \\?\C:\Windows\TEMP\WER-109750-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF1FD.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF22D.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF23D.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_133_58b4fbb94b2b023bf184cc2ccca441fc6cf767_00000000_cab_0385f44e Analysis symbol: Rechecking for solution: 0 Report Id: e2379b8a-47b6-4204-ae18-5941d71db3ac Report Status: 2049 Hashed bucket: 2/10/2018 3:00 PM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 133 P2: 1 P3: 1e00 P4: fffff801c008d370 P5: 0 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\021018-19781-01.dmp \\?\C:\Windows\TEMP\WER-109750-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF1FD.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF22D.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF23D.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_133_58b4fbb94b2b023bf184cc2ccca441fc6cf767_00000000_0329f23a Analysis symbol: Rechecking for solution: 0 Report Id: e2379b8a-47b6-4204-ae18-5941d71db3ac Report Status: 4 Hashed bucket: 2/24/2018 1:33 PM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 133 P2: 1 P3: 1e00 P4: fffff80308e8c370 P5: 0 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\022418-22265-01.dmp \\?\C:\Windows\TEMP\WER-300781-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WEREBE4.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WEREC14.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WEREC34.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_133_65a201be377b57a8129190a3ed97868382b91_00000000_cab_1819047c Analysis symbol: Rechecking for solution: 0 Report Id: 4ca0bd02-31c3-4982-95d7-27e9d7eb8842 Report Status: 2049 Hashed bucket: 2/24/2018 1:33 PM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 133 P2: 1 P3: 1e00 P4: fffff80308e8c370 P5: 0 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\022418-22265-01.dmp \\?\C:\Windows\TEMP\WER-300781-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WEREBE4.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WEREC14.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WEREC34.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_133_65a201be377b57a8129190a3ed97868382b91_00000000_035cec41 Analysis symbol: Rechecking for solution: 0 Report Id: 4ca0bd02-31c3-4982-95d7-27e9d7eb8842 Report Status: 4 Hashed bucket:[/quote]

 

Support For 760GM-P23 (FX) | Motherboard - The world leader in motherboard design | MSI Global


Chkdsk was executed in read-only mode. A volume snapshot was not used. Extra errors and warnings may be reported as the volume may have changed during the chkdsk run. Checking file system on D:\Volume label is ESD-ISO.Stage 1: Examining basic file system structure ... 1280 file records processed. File verification completed. 0 large file records processed. 0 bad file records processed. Stage 2: Examining file name linkage ... 1480 index entries processed. Index verification completed. 0 reparse records processed. 0 reparse records processed. Stage 3: Examining security descriptors ...Security descriptor verification completed. 100 data files processed. Windows has scanned the file system and found no problems.No further action is required. 7564287 KB total disk space. 4159376 KB in 981 files. 400 KB in 102 indexes. 14871 KB in use by the system. 13040 KB occupied by the log file. 3389640 KB available on disk. 8192 bytes in each allocation unit. 945535 total allocation units on disk. 423705 allocation units available on disk.


Microsoft Windows [Version 10.0.16299.248](c) 2017 Microsoft Corporation. All rights reserved.C:\Windows\system32>sfc /scannowBeginning 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.C:\Windows\system32>dism /online /cleanup-image /scanhealthDeployment Image Servicing and Management toolVersion: 10.0.16299.15Image Version: 10.0.16299.248[==========================100.0%==========================] No component store corruption detected.The operation completed successfully.C:\Windows\system32>ujdism /online /cleanup-image /restoreheathdism /online /cleanup-image /restoreheathdism /online /cleanup-image /restoreheath'ujdism' is not recognized as an internal or external command,operable program or batch file.C:\Windows\system32>vdism /online /cleanup-image /restoreheathdism /online /cleanup-image /restoreheathdism /online /cleanup-image /restoreheatheventvwr.msceventvwr.mscv'vdism' is not recognized as an internal or external command,operable program or batch file.C:\Windows\system32>dism /online /cleanup-image /restoreheathDeployment Image Servicing and Management toolVersion: 10.0.16299.15Image Version: 10.0.16299.248Error: 87The restoreheath option is not recognized in this context.For more information, refer to the help.The DISM log file can be found at C:\Windows\Logs\DISM\dism.logC:\Windows\system32>

 

This scanner can be used quickly to find various drive option replacements:
Crucial System Scanner | Crucial.com
When the drive is replaced there will be a new operating system with new drivers.
So this should take care of multiple problems at the same time.

Were you able to use Macrium to make a backup image or did it post errors preventing the backup image?
Have you backed up all of the files with the imminent drive failure?
For the administrative command prompt command copy and paste:
dism /online /cleanup-image /restorehealth
Indicate whether it completed successfully or found problems.
When available please update the tests /steps in post #4.

 

Personally, it sounds like bad caps on the video card.

 

No all capacitors are okey. If some of them are bad i would always have green lines on screen.

 

When available please update the progress with the tests /steps in post #4.

 

I replaced hard drive but same thing is happening.

 

1) Please update the progress for each of the steps in post #4.
2) For the replaced HD run baseline tests with HD Tune:
HD Tune website
Post images of the test results of each of these tabs into the thread.
a) Health (SMART)
b) Benchmark
c) Full error scan
3) Run the beta log collector and post a new zip into this thread:
log collector v2-beta08.zip
(extract > open)
4) Choose one of the temperature monitoring software applications: Speecy, HW monitor, Speed fan:Speccy - Free Download - Piriform: Speccy - System Information - Free
Speccy - System Information - Free Download
HWMONITOR | Softwares | CPUID: HWMONITOR | Softwares | CPUID
HWMONITOR | Softwares | CPUID
SpeedFan - Access temperature sensor in your computer: SpeedFan - Access temperature sensor in your computer
SpeedFan - Access temperature sensor in your computer

 

(2018-03-12 21 30).zip







Attachment 180686