📎 AI Summary:
The thread discusses a recurring error related to process crashes on an older Toshiba Satellite laptop, with the original poster seeking help to identify the issue. Contributors suggest using a debugging tool to generate memory dumps for troubleshooting and provide guidance on how to set up crash logs, though the original poster admits difficulty in replicating or forcing the error. Overall, the exchanges are helpful, with the community offering troubleshooting steps and encouragement, but the exact cause of the error remains unresolved.
The thread discusses a recurring error related to process crashes on an older Toshiba Satellite laptop, with the original poster seeking help to identify the issue. Contributors suggest using a debugging tool to generate memory dumps for troubleshooting and provide guidance on how to set up crash logs, though the original poster admits difficulty in replicating or forcing the error. Overall, the exchanges are helpful, with the community offering troubleshooting steps and encouragement, but the exact cause of the error remains unresolved.
Solution
holdum333
Banned
- Joined
- Mar 27, 2016
- Messages
- 1,242
@Josephur ! Thanks for your reply friend! I have done all your suggestions except I'm not sure about 3 and 4.
I have my PC set to defrag on default setting. I'm thinking on Wednesdays. Will check that out.
I never turn my PC off. I do restart occasionally and also shut down occasionally, but for the most part it's on 24/7
I appreciate your help friend.
Here's a thought! I have a external drive plugged in 24/7. Could some thing be going on there??
I have my PC set to defrag on default setting. I'm thinking on Wednesdays. Will check that out.
I never turn my PC off. I do restart occasionally and also shut down occasionally, but for the most part it's on 24/7
I appreciate your help friend.
Here's a thought! I have a external drive plugged in 24/7. Could some thing be going on there??
holdum333
Banned
- Joined
- Mar 27, 2016
- Messages
- 1,242
Sorry @Neemobeer ,but this is where your tool ended up. U
ntil it does different, this is where it will stay!!
ntil it does different, this is where it will stay!!
Last edited by a moderator:
holdum333
Banned
- Joined
- Mar 27, 2016
- Messages
- 1,242
Hi @Josephur Had to Pee!
My chipset drivers are in my included with my AMD drivers. I do not understand that at all, but when I Google this is what I'm told.
Go figure! Oh Well! I have the latest AMD drivers! Thanks for your reply!
The AMD display-driver package contains the chipset software. If things don't work out right after a clean install of Windows, it's because that was not installed as the very first thing - prior to any other driver. Install the TVAP before any other Toshiba utility.
My chipset drivers are in my included with my AMD drivers. I do not understand that at all, but when I Google this is what I'm told.Go figure!
Oh Well! I have the latest AMD drivers! Thanks for your reply!The AMD display-driver package contains the chipset software. If things don't work out right after a clean install of Windows, it's because that was not installed as the very first thing - prior to any other driver. Install the TVAP before any other Toshiba utility.
- Joined
- Jan 28, 2013
- Messages
- 2,419
Hi Gary,
It's very important to temporarily disable your AV prior to install with tools like DEBUG or any other diagnostic programs! The AV program (Defender, Norton, McAfee, Malwarebytes, etc.) will often BLOCK key processes in the installer or the installer scripts from installing properly into your computer. You may wish to disable your AV, your Antispyware program, and your Firewall (Microsoft or 3rd party), and uninstall and reinstall the DEBUG app. It's something minor that our experienced guys expect that you know to do, so it's not mentioned here. However, much of your experience is outside the corporate world and this is something the average user does not know about. It's ubiquitous to Techs, Engineers, Programmers, etc.
Also, tools like Debug don't like lots and lots of processes running, so it's best to remove all non-Microsoft services from the Startup (can do this through MSCONFIG.EXE), and reboot; then re-attempt install of DEBUG. Sometimes that will make a difference. I often use SAFE MODE, but DEBUG often won't work in SAFE MODE on many machines, and even if it does, it might not catch a scheduled process such as weekly defrags. It certainly wouldn't hurt for you to try these 2 configurations, and see if you get different results on the crash dumps. Resubmit them and our crash dump analysts can take a look and see if there's anything new or different there.
And personally, I'd unplug that external USB drive while running DEBUG, if your defrag script is attempting to write to the external USB that will show up (though your screenshot shows you unchecked it on the DEBUG program config).
BBJ
It's very important to temporarily disable your AV prior to install with tools like DEBUG or any other diagnostic programs! The AV program (Defender, Norton, McAfee, Malwarebytes, etc.) will often BLOCK key processes in the installer or the installer scripts from installing properly into your computer. You may wish to disable your AV, your Antispyware program, and your Firewall (Microsoft or 3rd party), and uninstall and reinstall the DEBUG app. It's something minor that our experienced guys expect that you know to do, so it's not mentioned here. However, much of your experience is outside the corporate world and this is something the average user does not know about. It's ubiquitous to Techs, Engineers, Programmers, etc.
Also, tools like Debug don't like lots and lots of processes running, so it's best to remove all non-Microsoft services from the Startup (can do this through MSCONFIG.EXE), and reboot; then re-attempt install of DEBUG. Sometimes that will make a difference. I often use SAFE MODE, but DEBUG often won't work in SAFE MODE on many machines, and even if it does, it might not catch a scheduled process such as weekly defrags. It certainly wouldn't hurt for you to try these 2 configurations, and see if you get different results on the crash dumps. Resubmit them and our crash dump analysts can take a look and see if there's anything new or different there.
And personally, I'd unplug that external USB drive while running DEBUG, if your defrag script is attempting to write to the external USB that will show up (though your screenshot shows you unchecked it on the DEBUG program config).
BBJ
holdum333
Banned
- Joined
- Mar 27, 2016
- Messages
- 1,242
Hi Bear! Thanks! I know about disabling AVs before trying these things, but I'm old and I seem to forget
Thanks for your reply and reminding me. I'll give it another go latter. I've done some things @Josephur suggested.
I'm going to wait to see if that helped. Thanks for your reply friend!
Thanks for your reply and reminding me. I'll give it another go latter. I've done some things @Josephur suggested.
I'm going to wait to see if that helped. Thanks for your reply friend!
- Joined
- Jan 28, 2013
- Messages
- 2,419
Welcome, Bro!
BBJ
BBJ
Similar threads
- Article
- Solved
