i tryed useing the program you say i need too use for helping you, but it does not complet i just stops. i dont know if i need to give it more time but i stod for 3 hours~ stuck or something at "0:42:45,82: Creating sysinfo file"
If the logfiles cannot be posted we can't see what the problem is. It could be worth running a few system check commands such as sfc /scannow and chkdsk /f in a command prompt to see if there are any file corruptions.
in what you say?
okay i did both and the Drive Error Checking in Windows 10 said "OK"
and the SFC Command in Windows 10 said:
Windows PowerShellCopyright (C) 2016 Microsoft Corporation. All rights reserved.PS C:\Windows\system32>PS 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.PS C:\Windows\system32>
so nothing is wrong it seems but i get that BSOD anyway
A WHEA error aka bugcheck 0x124 is usually a hardware problem and the method of solving this is to find which bit of hardware is causing the problem.
We generally suggest working through a whole range of tests:
Warning
If you're overclocking your system, revert back to stock clocks now.
Note
Test the system once the overclock is removed before continuing with the steps outlined below.
Part One: CPU Stress Test
Part Two: MemTest86+ RAM Diagnostic
Part Three: Hard Drive Diagnostics
Part Four: GPU Stress Test
Run Prime95 to stress test your CPU. Prime95 - Stress Test Your CPU - Windows 10 Forums
Your CPU temperatures will rise quickly while under this stress test. Keep a keen eye on them and abort the test if overheating occurs.
MemTest86+ needs to be run for at least 8 passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.
- 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.
Run Furmark for around 30 minutes.
Your GPU temperatures will rise quickly while Furmark is running. Keep a keen eye on them and abort the test if overheating occurs.
Please see posting instructions: BSOD - Posting Instructions - Windows 10 Forums
Please use English as the default language: Language - Add, Remove, and Change in Windows 10 Windows 10 General Tips Tutorials
Please post the information below in case the DM log collector malfunctions:
1) In the left lower corner type msinfo32 > wait 5 to 10 minutes for it to fully load > click file > save to desktop as *.nfo file > post into thread using one drive or drop box share link.
2) in the left lower corner type dxdiag > wait 5 to 10 minutes for it to fully load > click next page multiple times > save all information > post share link using one drive or drop box into the thread.
3) Open administrative command prompt and type or copy and paste:
get-eventlog System > $env:homeDrive$env:homePath\Desktop\system.txt
Post the event log into the thread using a one drive or drop box share link.
4) Open administrative command prompt and type or copy and paste:
type %SystemRoot%\System32\drivers\etc\hosts >> "%USERPROFILE%\Desktop\hosts.txt"
Post the host log into the thread using a one drive or drop box share link.
im sory zbook but im not very good at computers and that just gives no sense for me. what left lower corner? tryed in the program DM log but can type anything in there.
Open administrative command prompt and type or copy and paste:
dism /online /cleanup-image /restorehealth
chkdsk /scan
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
In the left lower corner just to the right of the Windows icon is blank or displays "type here to search". If you type msinfo32 the best match will be system information desktop application. For dxdiag the best match will be dxdiag run command. The dxdiag will take longer to load and you may not know whether or not it has completely loaded. So click on next page then next page, then next page, etc. Give it lots of time to load then save all information.
For the event log use this command (different from the earlier command) in administrative power shell:
Get-EventLog system | Format-List > $env:homeDrive$env:homePath\Desktop\system.txt
Give the DM log collector another try as this is the optimal way to submit the troubleshooting logs. Please give it a lot of extra time to load and then post the zip into the thread.
Please let us know your progress.
Which steps worked? Which steps did not work?
Quote