- Local time
- Today, 13:12
- Joined
- Feb 28, 2001
- Messages
- 27,182
OK, then it isn't the SYSTEM bugcheck but the Access bugcheck. Therefore of lesser scope. Nonetheless, that "re-open after crash" is something that other Office programs do. So does Firefox. Haven't crashed Edge yet, but when IE was their browser, it did that too. If you search for "auto-restart crashed task" you would find articles that suggest there is a registry setting for this purpose. Therefore, the restart is a Windows function, I think. Split this problem into two parts.
Here is an article on the CLR.DLL crash. It suggests a possible interaction with an antiviral package and further suggests temporarily turning off the A/V as a test. There is another suggestion that if you have a mapped drive that its network timeout is too quick. Read through the article for a couple of ideas. I have to admit at least one laugh... in the article, the person who filed it was saying that when he talked to tech people, that nobody else was seeing this error.
I'll keep looking for other stuff, but things are getting thin here.
Here is an article on the CLR.DLL crash. It suggests a possible interaction with an antiviral package and further suggests temporarily turning off the A/V as a test. There is another suggestion that if you have a mapped drive that its network timeout is too quick. Read through the article for a couple of ideas. I have to admit at least one laugh... in the article, the person who filed it was saying that when he talked to tech people, that nobody else was seeing this error.
Possible .Net issue causing application crashes
This has been a frustrating issue to troubleshoot. Here are the details. We have an application that crashes about 4-5 times a da... | Windows 10
community.spiceworks.com
I'll keep looking for other stuff, but things are getting thin here.