Windows 10: bsod freezing playing gta v bf1 error 0x124 and 0x3B

hi guys i hope to get my problem's solution here
before everything my pc specs are written on my page profile
so my pc freeze or crash(restart it self) while playing gta v or bf1 i mean no bsod while in the game
however i do get bsod sometimes if i'm lucky and not crashed while playing and that happen if i quit the game before do anything wrong but it looks like it's still hot and the i can hear a louder fanDESKTOP-LFAU6I0-08_03_2018__03927_16.zipDESKTOP-LFAU6I0-08_03_2018__03927_16.zip
when i bought my pc it was so unbelievable quite i can't be sure if it is on or off just from the mobo lights in behind
unfortunately that did not last long
i crashed a lot of times with bsod and without especially if pc is in a heavy load like playing or browsing so much on download a heavy files etc
i changed my gpu and psu and it did nothing
cleared cmos in case there is something wrong with the mobo settings
but still the same
just today i had 2 bsod with a different bugcheck
the bugcheck parameter with 0x0000003b happened while stress testing the cpu with prime95 after 1 hour
but the temps were just fine with average of 60
oh and like i say even at idle the computer becomes much louder than before
thanks in advance

:)

 

frequent windows event 4101(Display driver nvlddmkm stopped responding and has successfully recovered.)

Been having the exact same problem lately. It was only with GTA V until the last week or so and now Destiny 2 is starting to do it as well. GTA V won't play for more than 5 minutes before it just freezes and kicks me out to desktop. I've done everything
the internet has said and then some. I'm using GTX 1080 extreme gaming editions as well, seems a lot of people are having this issue with these cards.

 

Running GTA5-PC (STEAM DLC) with older Sony Vaio laptop

Hi Carl,

We understand that you really want to play GTA V. For you to play the game smoothly, we would suggest that you need to purchase a new laptop or PC that will meet the system requirements of GTA V.

 

There were 2 BSOD mini dump files.
The bugchecks were
3B
0x124
BSOD can be caused by misbehaving hardware or software drivers, or malfunctioning hardware.
The 0x124 WHEA is typically related to an underlying hardware problem.
For the WHEA there will be testing of each major hardware component: CPU, GPU, Drive, RAM
Debugging the BSOD files displayed 1 hardware and 1 software driver.


Please make sure that all tests /steps have images posted 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 /restorehealth
4) powercfg.exe /hibernate off
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 sure that there is no over clocking while troubleshooting.

7) Sometimes there are problems in the bios that produce bsod.
The BIOS: BIOS Version/Date American Megatrends Inc. F24a, 11/01/2018
8) Please check to see if this is the most up to date version.

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

10) To ensure that there are no improper bios settings please reset the bios.
11) Sometimes there can be failure to boot after resetting the bios.
12) Backup the computer files to another drive or to the cloud.
13) Make a backup image using Macrium:
Macrium Software | Macrium Reflect Free:
Macrium Software | Macrium Reflect Free

14) 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

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

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

17) 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

18) Uninstall ESET:
Uninstallers (removal tools) for common Windows antivirus softwareESET Knowledgebase
(Make sure that Windows defender is turned on)

19) uninstall the Nvidia GPU driver using DDU (display driver uninstaller)
20) re-install the Nvidia GPU driver from the Nvidia website
21) make sure that you check the clean install box and if available install the physx driver.
Display Driver Uninstaller Download version 17.0.8.2
Display Driver Uninstaller: How to use - Windows 7 Help Forums
NVIDIA
Download Display Driver Uninstaller - MajorGeeks

22) When testing for WHEA hardware errors we need to systematically check CPU, GPU, RAM and drive.

Once the bios is reset and there is no overclocking:

23) 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

24) Run Prime95 - Stress Test Your CPU
Prime95 - Stress Test Your CPU Windows 10 Performance Maintenance Tutorials
Prime95 - Stress Test Your CPU Windows 10 Tutorials
a) Record the maximum temperature and post the maximum temperature into the thread
b) Record test duration and post the uninterrupted test duration into the thread
c) Aim for testing > 3 hrs and abort testing as needed for freezing, temperature changes (see link)
d) Use the Microsoft snipping tool to post images into the thread.
Take Screenshot in Windows 10 Windows 10 General Tips Tutorials
Take Screenshot in Windows 10 Windows 10 Tutorials

25) 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 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.
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

26) Run HD Sentinel: (free or trial edition)
Hard Disk Sentinel - HDD health and temperature monitoring
Hard Disk Sentinel - HDD health and temperature monitoring
a) click disk > surface test > post image into the thread
(this may take several hours to complete)
b) Post images of each of these tabs into the thread:
Overview tab
Temperature
SMART
Disk performance
(In case the HD Sentenial free version is not able to perform the disk surface scan please use HD Tune: HD Tune website Full error scan)

Take Screenshot in Windows 10 Windows 10 General Tips Tutorials
Take Screenshot in Windows 10 Windows 10 Tutorials

27) Run FurMark - GPU Stress Test Windows 10 Performance Maintenance Tutorials
FurMark - GPU Stress Test Windows 10 Performance Maintenance Tutorials:
FurMark - GPU Stress Test Windows 10 Tutorials
Please make note of the importance of temperature monitoring and aborting the test in the GPU link.
a) Record the maximum temperature and post the maximum temperature into the thread.
b) Record the test duration and post the uninterrupted test duration into the thread.
c) Aim for testing 1 hour.
d) Use the Microsoft snipping tool to post images into the thread.
Take Screenshot in Windows 10 Windows 10 General Tips Tutorials
Take Screenshot in Windows 10 Windows 10 Tutorials

28) All of these tests should be done with the bios reset and no over clocking.

29) For each of the above tests please record maximum temperatures.

30) And please make sure that you use the Microsoft snipping tool to post images of each into the thread.
Take Screenshot in Windows 10 Windows 10 General Tips Tutorials

31) Open administrative command prompt and type or copy and paste: chkdsk /x /f /r
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

Run the command on all drives using the syntax: chkdsk /x /f /r C: or chkdsk /x /f /r D: changing the drive letter to the applicable drive.
This may take many hours to run so plan to run it overnight.

32) Use the information in this link to find the chkdsk report in the event viewer. Copy and paste into notepade > save to desktop > post into the thread using one drive or drop box share link:
Read Chkdsk Log in Event Viewer in Windows 10 Windows 10 Performance Maintenance Tutorials
Read Chkdsk Log in Event Viewer in Windows 10 Windows 10 Tutorials

33) These were displayed as problem devices:

Microsoft Streaming Tee/Sink-to-Sink Converter
SW\{CFD669F1-9BC2-11D0-8299-0000F822FE8A}\{0A4252A0-7E70-11D0-A5D6-28DB04C10000}
45

Microsoft Streaming Tee/Sink-to-Sink Converter
SW\{CFD669F1-9BC2-11D0-8299-0000F822FE8A}\{CF1DDA2C-9743-11D0-A3EE-00A0C9223196}
45

Open device manager > click view > show hidden devices > expand all rows > look for either yellow triangles with a black exclamation mark or unknown device > post images into the thread

34) For any BSOD please use the BETA log collector and post a new zip into the thread:
(extract > open)
log collector v2-beta08.zip
If there are problems using the beta log collector then use the DM log collector:
BSOD - Posting Instructions - Windows 10 Forums
The beta log collector is preferred as it collects more information for the troubleshooting.




Code: 07/03/2018 20:37 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 124 P2: 0 P3: ffff848eb6b40028 P4: f2000000 P5: 10019 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\030718-12625-01.dmp \\?\C:\Windows\TEMP\WER-17328-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER591C.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER593B.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER595C.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_124_70dbd8ac4ac43fea1472a68875318cfefcecfdd_00000000_cab_0344596a Analysis symbol: Rechecking for solution: 0 Report ID: 10ce2fd7-8360-4de5-9cd6-9e06c632bbc7 Report Status: 4 Hashed bucket:04/03/2018 0:54 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 124 P2: 0 P3: ffffbd0eefd40028 P4: b2000000 P5: 10019 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\030418-11765-01.dmp \\?\C:\Windows\TEMP\WER-16796-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER57F4.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5805.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5825.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_124_c1d1f4fbd12243e553bc9a275b65253dbea2a48_00000000_cab_03485822 Analysis symbol: Rechecking for solution: 0 Report ID: 0b71451a-3490-417e-80d9-625f8a39d065 Report Status: 4 Hashed bucket: 07/03/2018 23:19 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 3b P2: c0000005 P3: fffff9d2ede66854 P4: ffffce8d41bfdba0 P5: 0 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\030718-11546-01.dmp \\?\C:\Windows\TEMP\WER-17140-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER58BE.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER58DE.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER58FE.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_3b_2bc2e787d0cd393b1c143435b75ff86f1ed9cfe2_00000000_cab_034058fd Analysis symbol: Rechecking for solution: 0 Report ID: 1aec4253-e8c6-471d-a856-8661cbe4ba5d Report Status: 4 Hashed bucket:[/quote] Code: 04/03/2018 0:55 Windows Error Reporting Fault bucket 0x124_GenuineIntel_PROCESSOR_TLB, type 0 Event Name: BlueScreen Response: Not available Cab Id: 0d778f11-736d-48fd-abd5-1e107b9c6819 Problem signature: P1: 124 P2: 0 P3: ffffbd0eefd40028 P4: b2000000 P5: 10019 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\030418-11765-01.dmp \\?\C:\Windows\TEMP\WER-16796-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER57F4.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5805.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5825.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_124_c1d1f4fbd12243e553bc9a275b65253dbea2a48_00000000_cab_0f1cffcc Analysis symbol: Rechecking for solution: 0 Report ID: 0b71451a-3490-417e-80d9-625f8a39d065 Report Status: 268435456 Hashed bucket:07/03/2018 20:38 Windows Error Reporting Fault bucket 0x124_GenuineIntel_PROCESSOR_TLB, type 0 Event Name: BlueScreen Response: Not available Cab Id: 59aa2776-1f7c-4fe5-9d23-2873c35fc2f4 Problem signature: P1: 124 P2: 0 P3: ffff848eb6b40028 P4: f2000000 P5: 10019 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\030718-12625-01.dmp \\?\C:\Windows\TEMP\WER-17328-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER591C.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER593B.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER595C.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_124_70dbd8ac4ac43fea1472a68875318cfefcecfdd_00000000_cab_124488e6 Analysis symbol: Rechecking for solution: 0 Report ID: 10ce2fd7-8360-4de5-9cd6-9e06c632bbc7 Report Status: 268435456 Hashed bucket:[/quote] Code: 07/03/2018 23:20 Windows Error Reporting Fault bucket IP_MISALIGNED_win32kbase.sys, type 0 Event Name: BlueScreen Response: Not available Cab Id: af2ef177-1168-418c-a345-39ccda82b142 Problem signature: P1: 3b P2: c0000005 P3: fffff9d2ede66854 P4: ffffce8d41bfdba0 P5: 0 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\030718-11546-01.dmp \\?\C:\Windows\TEMP\WER-17140-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER58BE.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER58DE.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER58FE.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_3b_2bc2e787d0cd393b1c143435b75ff86f1ed9cfe2_00000000_cab_22608df7 Analysis symbol: Rechecking for solution: 0 Report ID: 1aec4253-e8c6-471d-a856-8661cbe4ba5d Report Status: 268435456 Hashed bucket:04/03/2018 0:55 Windows Error Reporting Fault bucket LKD_0x1A1_WIN32K_CALLOUT_WATCHDOG_nt!KiSwapContext, type 0 Event Name: LiveKernelEvent Response: Not available Cab Id: fdb5e9ea-e56c-4801-aa15-d1e340211315 Problem signature: P1: 1a1 P2: ffffaf85a4e66700 P3: 0 P4: 0 P5: 0 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\LiveKernelReports\PoW32kWatchdog\PoW32kWatchdog-20180302-2124.dmp \\?\C:\Windows\TEMP\WER-16796-0.sysdata.xml \\?\C:\Windows\LiveKernelReports\PoW32kWatchdog-20180302-2124.dmp \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5795.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER57B5.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER57D5.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_1a1_6de77e7499234d5b6dfcadef8cbd5c2d9118994b_00000000_cab_0f1c9a9a Analysis symbol: Rechecking for solution: 0 Report ID: 0613b244-d663-4a79-84b0-f65900d1feae Report Status: 268435456 Hashed bucket:[/quote] Code: Event[3082]: Log Name: System Source: Microsoft-Windows-WHEA-Logger Date: 2018-03-07T22:39:41.151 Event ID: 19 Task: N/A Level: Warning Opcode: Info Keyword: N/A User: S-1-5-19 User Name: NT AUTHORITY\LOCAL SERVICE Computer: DESKTOP-LFAU6I0 Description: A corrected hardware error has occurred. Reported by component: Processor Core Error Source: Corrected Machine Check Error Type: Internal parity error Processor APIC ID: 10 The details view of this entry contains further information. Event[3083]: Log Name: System Source: Microsoft-Windows-WHEA-Logger Date: 2018-03-07T22:40:41.151 Event ID: 19 Task: N/A Level: Warning Opcode: Info Keyword: N/A User: S-1-5-19 User Name: NT AUTHORITY\LOCAL SERVICE Computer: DESKTOP-LFAU6I0 Description: A corrected hardware error has occurred. Reported by component: Processor Core Error Source: Corrected Machine Check Error Type: Internal parity error Processor APIC ID: 0 The details view of this entry contains further information. Event[3084]: Log Name: System Source: Microsoft-Windows-WHEA-Logger Date: 2018-03-07T22:46:41.150 Event ID: 19 Task: N/A Level: Warning Opcode: Info Keyword: N/A User: S-1-5-19 User Name: NT AUTHORITY\LOCAL SERVICE Computer: DESKTOP-LFAU6I0 Description: A corrected hardware error has occurred. Reported by component: Processor Core Error Source: Corrected Machine Check Error Type: Internal parity error Processor APIC ID: 10 The details view of this entry contains further information. Event[3085]: Log Name: System Source: Microsoft-Windows-WHEA-Logger Date: 2018-03-07T22:47:41.151 Event ID: 19 Task: N/A Level: Warning Opcode: Info Keyword: N/A User: S-1-5-19 User Name: NT AUTHORITY\LOCAL SERVICE Computer: DESKTOP-LFAU6I0 Description: A corrected hardware error has occurred. Reported by component: Processor Core Error Source: Corrected Machine Check Error Type: Internal parity error Processor APIC ID: 0 The details view of this entry contains further information. Event[3086]: Log Name: System Source: Microsoft-Windows-WHEA-Logger Date: 2018-03-07T22:48:41.151 Event ID: 19 Task: N/A Level: Warning Opcode: Info Keyword: N/A User: S-1-5-19 User Name: NT AUTHORITY\LOCAL SERVICE Computer: DESKTOP-LFAU6I0 Description: A corrected hardware error has occurred. Reported by component: Processor Core Error Source: Corrected Machine Check Error Type: Internal parity error Processor APIC ID: 0 The details view of this entry contains further information. Event[3087]: Log Name: System Source: Microsoft-Windows-WHEA-Logger Date: 2018-03-07T22:48:41.151 Event ID: 19 Task: N/A Level: Warning Opcode: Info Keyword: N/A User: S-1-5-19 User Name: NT AUTHORITY\LOCAL SERVICE Computer: DESKTOP-LFAU6I0 Description: A corrected hardware error has occurred. Reported by component: Processor Core Error Source: Corrected Machine Check Error Type: Internal parity error Processor APIC ID: 10 The details view of this entry contains further information. Event[3088]: Log Name: System Source: Microsoft-Windows-WHEA-Logger Date: 2018-03-07T22:50:41.150 Event ID: 19 Task: N/A Level: Warning Opcode: Info Keyword: N/A User: S-1-5-19 User Name: NT AUTHORITY\LOCAL SERVICE Computer: DESKTOP-LFAU6I0 Description: A corrected hardware error has occurred. Reported by component: Processor Core Error Source: Corrected Machine Check Error Type: Internal parity error Processor APIC ID: 4 The details view of this entry contains further information. Event[3089]: Log Name: System Source: Microsoft-Windows-WHEA-Logger Date: 2018-03-07T22:50:41.151 Event ID: 19 Task: N/A Level: Warning Opcode: Info Keyword: N/A User: S-1-5-19 User Name: NT AUTHORITY\LOCAL SERVICE Computer: DESKTOP-LFAU6I0 Description: A corrected hardware error has occurred. Reported by component: Processor Core Error Source: Corrected Machine Check Error Type: Internal parity error Processor APIC ID: 10 The details view of this entry contains further information. Event[3090]: Log Name: System Source: Microsoft-Windows-WHEA-Logger Date: 2018-03-07T22:51:41.151 Event ID: 19 Task: N/A Level: Warning Opcode: Info Keyword: N/A User: S-1-5-19 User Name: NT AUTHORITY\LOCAL SERVICE Computer: DESKTOP-LFAU6I0 Description: A corrected hardware error has occurred. Reported by component: Processor Core Error Source: Corrected Machine Check Error Type: Internal parity error Processor APIC ID: 6 The details view of this entry contains further information. Event[3091]: Log Name: System Source: Microsoft-Windows-WHEA-Logger Date: 2018-03-07T22:51:41.151 Event ID: 19 Task: N/A Level: Warning Opcode: Info Keyword: N/A User: S-1-5-19 User Name: NT AUTHORITY\LOCAL SERVICE Computer: DESKTOP-LFAU6I0 Description: A corrected hardware error has occurred. Reported by component: Processor Core Error Source: Corrected Machine Check Error Type: Internal parity error Processor APIC ID: 8 The details view of this entry contains further information. Event[3092]: Log Name: System Source: Microsoft-Windows-WHEA-Logger Date: 2018-03-07T22:51:41.152 Event ID: 19 Task: N/A Level: Warning Opcode: Info Keyword: N/A User: S-1-5-19 User Name: NT AUTHORITY\LOCAL SERVICE Computer: DESKTOP-LFAU6I0 Description: A corrected hardware error has occurred. Reported by component: Processor Core Error Source: Corrected Machine Check Error Type: Internal parity error Processor APIC ID: 10 The details view of this entry contains further information. Event[3093]: Log Name: System Source: Microsoft-Windows-WHEA-Logger Date: 2018-03-07T22:52:41.151 Event ID: 19 Task: N/A Level: Warning Opcode: Info Keyword: N/A User: S-1-5-19 User Name: NT AUTHORITY\LOCAL SERVICE Computer: DESKTOP-LFAU6I0 Description: A corrected hardware error has occurred. Reported by component: Processor Core Error Source: Corrected Machine Check Error Type: Internal parity error Processor APIC ID: 4 The details view of this entry contains further information. Event[3094]: Log Name: System Source: Microsoft-Windows-WHEA-Logger Date: 2018-03-07T22:52:41.151 Event ID: 19 Task: N/A Level: Warning Opcode: Info Keyword: N/A User: S-1-5-19 User Name: NT AUTHORITY\LOCAL SERVICE Computer: DESKTOP-LFAU6I0 Description: A corrected hardware error has occurred. Reported by component: Processor Core Error Source: Corrected Machine Check Error Type: Internal parity error Processor APIC ID: 8 The details view of this entry contains further information. Event[3095]: Log Name: System Source: Microsoft-Windows-WHEA-Logger Date: 2018-03-07T22:56:41.151 Event ID: 19 Task: N/A Level: Warning Opcode: Info Keyword: N/A User: S-1-5-19 User Name: NT AUTHORITY\LOCAL SERVICE Computer: DESKTOP-LFAU6I0 Description: A corrected hardware error has occurred. Reported by component: Processor Core Error Source: Corrected Machine Check Error Type: Internal parity error Processor APIC ID: 10 The details view of this entry contains further information. Event[3096]: Log Name: System Source: Microsoft-Windows-WHEA-Logger Date: 2018-03-07T23:01:41.150 Event ID: 19 Task: N/A Level: Warning Opcode: Info Keyword: N/A User: S-1-5-19 User Name: NT AUTHORITY\LOCAL SERVICE Computer: DESKTOP-LFAU6I0 Description: A corrected hardware error has occurred. Reported by component: Processor Core Error Source: Corrected Machine Check Error Type: Internal parity error Processor APIC ID: 8 The details view of this entry contains further information. Event[3097]: Log Name: System Source: Microsoft-Windows-WHEA-Logger Date: 2018-03-07T23:02:41.150 Event ID: 19 Task: N/A Level: Warning Opcode: Info Keyword: N/A User: S-1-5-19 User Name: NT AUTHORITY\LOCAL SERVICE Computer: DESKTOP-LFAU6I0 Description: A corrected hardware error has occurred. Reported by component: Processor Core Error Source: Corrected Machine Check Error Type: Internal parity error Processor APIC ID: 0 The details view of this entry contains further information. Event[3098]: Log Name: System Source: Microsoft-Windows-WHEA-Logger Date: 2018-03-07T23:02:41.150 Event ID: 19 Task: N/A Level: Warning Opcode: Info Keyword: N/A User: S-1-5-19 User Name: NT AUTHORITY\LOCAL SERVICE Computer: DESKTOP-LFAU6I0 Description: A corrected hardware error has occurred. Reported by component: Processor Core Error Source: Corrected Machine Check Error Type: Internal parity error Processor APIC ID: 4 The details view of this entry contains further information. Event[3099]: Log Name: System Source: Microsoft-Windows-WHEA-Logger Date: 2018-03-07T23:02:41.151 Event ID: 19 Task: N/A Level: Warning Opcode: Info Keyword: N/A User: S-1-5-19 User Name: NT AUTHORITY\LOCAL SERVICE Computer: DESKTOP-LFAU6I0 Description: A corrected hardware error has occurred. Reported by component: Processor Core Error Source: Corrected Machine Check Error Type: Internal parity error Processor APIC ID: 6 The details view of this entry contains further information. Event[3100]: Log Name: System Source: Microsoft-Windows-WHEA-Logger Date: 2018-03-07T23:03:41.155 Event ID: 19 Task: N/A Level: Warning Opcode: Info Keyword: N/A User: S-1-5-19 User Name: NT AUTHORITY\LOCAL SERVICE Computer: DESKTOP-LFAU6I0 Description: A corrected hardware error has occurred. Reported by component: Processor Core Error Source: Corrected Machine Check Error Type: Internal parity error Processor APIC ID: 10 The details view of this entry contains further information.[/quote] Code: Event[545]: Log Name: System Source: Disk Date: 2018-03-02T13:28:10.249 Event ID: 51 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-LFAU6I0 Description: An error was detected on device \Device\Harddisk2\DR3 during a paging operation. Event[546]: Log Name: System Source: Disk Date: 2018-03-02T13:28:10.249 Event ID: 51 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-LFAU6I0 Description: An error was detected on device \Device\Harddisk2\DR3 during a paging operation. Event[547]: Log Name: System Source: Disk Date: 2018-03-02T13:28:10.250 Event ID: 51 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-LFAU6I0 Description: An error was detected on device \Device\Harddisk2\DR3 during a paging operation. Event[548]: Log Name: System Source: Disk Date: 2018-03-02T13:28:10.250 Event ID: 51 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-LFAU6I0 Description: An error was detected on device \Device\Harddisk2\DR3 during a paging operation. Event[549]: Log Name: System Source: Disk Date: 2018-03-02T13:28:10.251 Event ID: 51 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-LFAU6I0 Description: An error was detected on device \Device\Harddisk2\DR3 during a paging operation.[/quote]
Code: nvlddmkm.sys Fri Feb 23 13:54:48 2018 (5A907188)[/quote] Code: Name NVIDIA GeForce GTX 1080PNP Device ID PCI\VEN_10DE&DEV_1B80&SUBSYS_859B1043&REV_A1\4&FC7F53B&0&0018 Adapter Type GeForce GTX 1080, NVIDIA compatible Adapter Description NVIDIA GeForce GTX 1080 Adapter RAM (1,048,576) bytes Installed Drivers C:\Windows\System32\DriverStore\FileRepository\nvaki.inf_amd64_1cce6cb8fb27a94d\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nvaki.inf_amd64_1cce6cb8fb27a94d\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nvaki.inf_amd64_1cce6cb8fb27a94d\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nvaki.inf_amd64_1cce6cb8fb27a94d\nvldumdx.dll Driver Version 23.21.13.9101 INF File oem41.inf (Section062 section) Colour Planes Not Available Colour Table Entries 4294967296 Resolution 2560 x 1440 x 165 hertz Bits/Pixel 32 Memory Address 0xDE000000-0xDF0FFFFF Memory Address 0xC0000000-0xD1FFFFFF Memory Address 0xD0000000-0xD1FFFFFF I/O Port 0x0000E000-0x0000EFFF IRQ Channel IRQ 16 I/O Port 0x000003B0-0x000003BB I/O Port 0x000003C0-0x000003DF Memory Address 0xA0000-0xBFFFF Driver c:\windows\system32\driverstore\filerepository\nvaki.inf_amd64_1cce6cb8fb27a94d\nvlddmkm.sys (23.21.13.9101, 16.71 MB (17,524,720 bytes), 03/03/2018 1:32)[/quote]
Code: ===============================================================================Common Platform Error Record @ ffff848eb6b40028 ------------------------------------------------------------------------------- Record Id : 01d3b5b2e422603d Severity : Fatal (1) Length : 928 Creator : Microsoft Notify Type : Machine Check Exception Timestamp : 3/7/2018 20:35:09 (UTC) Flags : 0x00000000 =============================================================================== Section 0 : Processor Generic ------------------------------------------------------------------------------- Descriptor @ ffff848eb6b400a8 Section @ ffff848eb6b40180 Offset : 344 Length : 192 Flags : 0x00000001 Primary Severity : Fatal Proc. Type : x86/x64 Instr. Set : x64 Error Type : TLB error Flags : 0x00 Level : 1 CPU Version : 0x00000000000406f1 Processor ID : 0x0000000000000004 =============================================================================== Section 1 : x86/x64 Processor Specific ------------------------------------------------------------------------------- Descriptor @ ffff848eb6b400f0 Section @ ffff848eb6b40240 Offset : 536 Length : 128 Flags : 0x00000000 Severity : Fatal Local APIC Id : 0x0000000000000004 CPU Id : f1 06 04 00 00 08 10 04 - bf fb fe 7f ff fb eb bf 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 Proc. Info 0 @ ffff848eb6b40240 =============================================================================== Section 2 : x86/x64 MCA ------------------------------------------------------------------------------- Descriptor @ ffff848eb6b40138 Section @ ffff848eb6b402c0 Offset : 664 Length : 264 Flags : 0x00000000 Severity : Fatal Error : GTLBL1_ERR (Proc 4 Bank 2) Status : 0xf200000000010019[/quote]

 

thanks man for the fast reply i'll do them all and till you here the results
appreciated

 

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 /restorehealthDeployment Image Servicing and Management toolVersion: 10.0.16299.15Image Version: 10.0.16299.248[==========================100.0%==========================] The restore operation completed successfully.The operation completed successfully.C:\Windows\system32>powercfg.exe /hibernate offC:\Windows\system32>

and yes my friend i have updated bios to the latest version
and i am sorry that i didn't mention that i reinstalled the windows just week ago but the problem still exist ....from september
i will check the rest
thank you

 

hello...i checked all the points and here are what iv'e get
as for the first 5 points i posted them before above
now point number 6
(6 there is no over clocking at all
(7 like i said iv'e updated the bios to the latest version F24a for month maybe
(8 i have the latest drivers from gigabyte..i have app center too if you need any information from it
(9 i have done a million times reset the bios to default settings and just to make sure that everything are correct i removed the battery and cleared cmos jumper...so 100% no overclocking
(10 from week ago i did a clean reinstall to the windows...so i don't think that i should make a restore point or backup
(15 i downloaded ccleaner and here you are the imagesAttachment 180173 Attachment 180174
(16 as for disk cleanup too Attachment 180176 Attachment 180177
(17 images for bothAttachment 180178 Attachment 180179
(18 i did
19+20+21 all done

(23 i have choosed speccy
(24 the maximum temperature for core number 5 of 6 was 70 but the average all cpu cores were 65
(24 as for the test duration it wat 3h and 34m Attachment 180180

(25 also the memtest86 give me no errors at all Attachment 180181
(26 i ran hdtune with both drive c and d for c no problems for i got bsod during the test but the test was just fine everything is ok
Attachment 180184 also good to mention that i did a surface test with hard disk sentinel on c drive and everything was fine












the rest will be next

 

(27 the temperature target in asus tweak ii is 83 and when i play gta v or bf1 it always been 82 and it is the same with furmark
so i guess it's fine



the link from onedrive here פריטים ששותפו 9-3-2018

as for the device manager it's fine nothing wired

 

and here the beta log collector file attachments

 

The attachments in the post were not able to be opened.
Please use another method to insert attachments.

 

1) For startup and recovery system failure:
a) un-check automatically restart
b) reboot > confirm the setting change

2) For Ccleaner un-check:
a) Memory Dumps
b) Windows Log Files