Intel
Rules
-
Be civil. Uncivil language, slurs, and insults will result in a ban. If you can't say something respectfully, don't say it at all.
-
No Unoriginal Sources, Referral links or Paywalled Articles.
-
All posts must be related to Intel or Intel products.
-
Give competitors' recommendations only where appropriate. If a user asks for Intel only (i.e. i5-12600k vs i5-13400?) recommendations, do not reply with non-Intel recommendations. Commenting on a build pic saying they should have gone AMD/Nvidia is also inappropriate, don't be rude. Let people enjoy things.
-
CPU Cooling problems: Just like 95C is normal for Ryzen, 100C is normal for Intel CPUs in many workloads. If you're worried about CPU temperatures, please look at reviews for the laptop or CPU cooler you're using.
view the rest of the comments
Are you getting BSOD (Blue Screen)? If so, you can check the crash file and analyze it to find exactly what is crashing.
Upon restart you may also look at the Event Viewer. Look in the critical events section.
If no blue screen or windows has recovered from a serious error message after reboot, and no critical events, may try some troubleshooting.
Might try the usual tests:
Run Windows Disk Check and set to fix and run at startup from the admin command line CMD:
chkdsk /f /r
run the built in 'Windows Memory Diagnostic' on reboot:
http://hs.windows.microsoft.com/hhweb/content/m-en-us/p-6.2/id-4edd5f80-def2-4d32-965c-116d49fb9872/
Run system file checker at the admin command prompt CMD:
sfc /scannow
--For blue screens:
If you are getting blue screens, may need to analyze the crash file. I recommend setting the dmp file to a quick memory dmp first and re-create the crash. This way the file won't be a large file the size of running ram.
To verify your current dmp file config:
Start > Run > type in
SystemPropertiesAdvanced
Select settings under Startup and recovery
verify System Failure has both options checked.
Verify the drop down is set to Small Memory Dump. This option will create the crash file with processes and other blue screen data.
https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/small-memory-dump
Verify the directory for the crash file.
----------------
To read the crash file after the Blue Screen:
Install:
https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/
Download WinDbg
Install the WinDbg
Run WinDbg
Click File Top Left
In the list, select 'Open dump file'
The default location is in c:\Windows\ or %SystemRoot%\
select the minidump file to open it
once it loads, it make take a minute,
in the center area of the debugger, there is a place to type in commands
enter the command type in:
!analyze -v
Examine the dump file
when the report finishes, look in the list and sections for crash error specifics. There may be an application, or other information that will tell you what exactly crashed.
For example, I had an issue where a gigabyte control center, installed a cloud application, and was listed in the analysis. This helped me isolated the issue and it helped me to remove that specific application.
I'm actually not getting blue screens.
It's all about my tabs going "not responding" and I can't click anywhere before it comes back to normal