📎 AI Summary:
The thread discusses ongoing daily BSOD issues experienced by the original poster, Ian Britten, who used PowerShell instructions for troubleshooting but did not provide a crash dump file. A responder, kemical, advises adjusting system settings to enable small memory dump files and recommends running system scans like sfc/scannow and dism to repair potential file issues. The overall sentiment indicates a collaborative effort to diagnose and fix the BSOD problem, with helpful technical guidance provided.
The thread discusses ongoing daily BSOD issues experienced by the original poster, Ian Britten, who used PowerShell instructions for troubleshooting but did not provide a crash dump file. A responder, kemical, advises adjusting system settings to enable small memory dump files and recommends running system scans like sfc/scannow and dism to repair potential file issues. The overall sentiment indicates a collaborative effort to diagnose and fix the BSOD problem, with helpful technical guidance provided.
Solution
kemical
Essential Member
Hi Ian,
unfortunately there isn't a dump file attached. I'm not sure if it's the powershell instructions or your not configured to produce them.
Check your settings are like thus:
Open the run application.
Type sysdm.cpl in the run box and click ok.
Look across the top of the system properties box for 'Advanced' and click that.
Look for 'Startup and Recovery' near the bottom and click 'settings'.
Near the bottom you'll see a drop down menu under the heading 'write debugging information'.
In the drop down menu choose ' small memory dump (256KB)'
Under 'small dump directory' make sure it says %SystemRoot%\Minidump.
Click ok and your good to go.
If your settings are like the above and you have a page file of more then 200mb (needed for dump file creation) try running the other application for data collection.
You may have to wait until you bsod again before a dump file is created.
In the meantime try running these scans and see if the help:
File scans
Right click on the Start menu icon and from the revealed list choose 'admin command prompt'. Type:
sfc /scannow
press enter and await results
In the same command prompt and after the above scan has finished type:
dism /online /cleanup-image /restorehealth
Press enter and await results (longer this time).
If the first scan found files it could not repair but the second scan is successful, run the first scan again using the same command prompt box and this time it should repair the files found.
unfortunately there isn't a dump file attached. I'm not sure if it's the powershell instructions or your not configured to produce them.
Check your settings are like thus:
Open the run application.
Type sysdm.cpl in the run box and click ok.
Look across the top of the system properties box for 'Advanced' and click that.
Look for 'Startup and Recovery' near the bottom and click 'settings'.
Near the bottom you'll see a drop down menu under the heading 'write debugging information'.
In the drop down menu choose ' small memory dump (256KB)'
Under 'small dump directory' make sure it says %SystemRoot%\Minidump.
Click ok and your good to go.
If your settings are like the above and you have a page file of more then 200mb (needed for dump file creation) try running the other application for data collection.
You may have to wait until you bsod again before a dump file is created.
In the meantime try running these scans and see if the help:
File scans
Right click on the Start menu icon and from the revealed list choose 'admin command prompt'. Type:
sfc /scannow
press enter and await results
In the same command prompt and after the above scan has finished type:
dism /online /cleanup-image /restorehealth
Press enter and await results (longer this time).
If the first scan found files it could not repair but the second scan is successful, run the first scan again using the same command prompt box and this time it should repair the files found.
