Notifications
Clear all
Topic starter
I have had an issue on a laptop that runs windows 10. My user gets a blue screen of death about twice a week and it seems to be getting more frequent. As centricity is the only program that is loaded onto this machine and I have already gone through the work arounds to make it work on windows 10, I am wondering if anyone else has experienced this problem as well?
I don't think it is a hardware issue as the computer is new but I want to get community input on this before I move to the next phase of investigating the problem.
Posted : May 17, 2018 10:25 am
What version of Centricity are you using?
Posted : May 17, 2018 10:30 am
Topic starter
12.2.2.4212
Posted : May 17, 2018 10:33 am
Hmmm. You shouldn’t have a problem with Windows 10 on the version. What is the user doing when they get the blue screen
Posted : May 17, 2018 10:47 am
Topic starter
Most of the time nothing, centricity is just running in the background. I think I just stumbled on a different cause for this though. I use Webroot AV which seems to have a few issues on windows 10. I am going to try uninstalling that and seeing what happens
Posted : May 17, 2018 10:50 am
I don’t think it’s centricity but i would recommend looking at the event logs and see what is happening before the crash.
Posted : May 17, 2018 10:52 am
Topic starter
I tried that, the event logs are not being generated. I have changed those settings so that it will be saving those logs but I think you are right and centricity is not the cause of this issue
Posted : May 17, 2018 10:57 am
The Windows system event log usually shows a crash event indicating that windows stopped unexpectedly with a stop code of 0xnnnnnnnn. That stop code is often not very helpful, but sometimes it is. I start there first.
You should also be getting crash dumps in the (I believe) c:\windows\minidump folder. The crash dump will also identify the stop code and related info.
Use windbg to analyze the dump files. http://msdn.microsoft.com/en-US/windows/hardware/hh852360 . Open windbg, then
- Set the symbols path to SRV*<your local folder for symbols>* http://msdl.microsoft.com/download/symbols .
- Open the minidump file
- Click on the !analyze v link
Often windbg will identify the process that caused the crash. A lot more detail is shown by windbg, but so far I've avoided that rabbit hole.
-dp
Posted : May 18, 2018 1:14 am
