📎 AI Summary:
The thread discusses a user experiencing Windows Blue Screen of Death (BSOD) issues, likely caused by outdated drivers and large memory dump files. The responder advises reducing dump file size, updating drivers from the motherboard support page, removing third-party antivirus software, and running system scans to resolve the problem. The overall sentiment is helpful and troubleshooting-focused, leading to recommended steps for diagnosis and solution.
The thread discusses a user experiencing Windows Blue Screen of Death (BSOD) issues, likely caused by outdated drivers and large memory dump files. The responder advises reducing dump file size, updating drivers from the motherboard support page, removing third-party antivirus software, and running system scans to resolve the problem. The overall sentiment is helpful and troubleshooting-focused, leading to recommended steps for diagnosis and solution.
Solution
kemical
Essential Member
- Joined
- Aug 28, 2007
- Messages
- 36,163
Hi,
it sounds like from you say that your dump file is a full memory dump. These type of dump files can run to some gigabytes in size and your better off reducing the size of the dump simply as it's easier to post.
Please change your system settings 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.
You will need to blue screen again before the smaller sized dump file is created but please post when you do.
In the meantime try these tips:
Find command prompt, right click on it, choose properties and then run as administrator. Type or copy and paste:
sfc /scannow
press enter and await results
If you added anything new recently like an app or a driver see if removing it helps.
Update your system drivers using your system support page:
Link Removed
Please post the smaller dump file.
it sounds like from you say that your dump file is a full memory dump. These type of dump files can run to some gigabytes in size and your better off reducing the size of the dump simply as it's easier to post.
Please change your system settings 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.
You will need to blue screen again before the smaller sized dump file is created but please post when you do.
In the meantime try these tips:
Find command prompt, right click on it, choose properties and then run as administrator. Type or copy and paste:
sfc /scannow
press enter and await results
If you added anything new recently like an app or a driver see if removing it helps.
Update your system drivers using your system support page:
Link Removed
Please post the smaller dump file.
kemical
Essential Member
- Joined
- Aug 28, 2007
- Messages
- 36,163
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {2b, 2, 0, fffff80002ef2f43}
Probably caused by : ntkrnlmp.exe ( nt!KiProcessExpiredTimerList+103 )
Followup: MachineOwnerboth dump files relate to memory allocation and is probably being caused by an incorrect driver.
I can see your running Norton AV and we always ask that third party Anti virus suites be removed as they are often at the root of these issues.
Looking over your drivers i can see that they are extremely old with many dating from 2014.
Please update your drivers using the versions found on your motherboard support site:
Link Removed
Look for command prompt in the start menu, right click on it, choose properties followed by run as administrator.
Type:
sfc /scannow
press enter and await results
If the bsod continues please run the driver verifier and post the results. This guide is quite easy to follow but please post back if issues arise:
Check for Bad Drivers in Windows with Driver Verifier - Make Tech Easier
Post any new dumps as the more we see the better.