![]() Missing image name, possible paged-out or corrupt data.ĭebugger can not determine kernel base addressĪn expected clock interrupt was not received on a secondary processor in an Did you say you had a BSOD occur in safe mode? So i can't run the dump file report fully, but I will at least post some key elements below. So I am unable to read any module or system information. Unfortunately the dump analysis is completely inconclusive. There are million commands I could run for the clock watchdog, but it could turn into a wormhole, and when you have all your information to hand, I suspect it will be more effective to simply run through remaining drivers, then test safe mode and go from there. But we want to eliminate software/firmware first as to avoid any unnecessary pain. If the issue is still occuring after that point, I'd probably be looking at hardware diagnosis. How new is the clean install? I'd be tempted to try clean re-installing again using Media Creation tool here: Thus why I think the safe mode and clean boot state is important, as it will help us identify where thr problem might be. ![]() No problem at all, I can see from the driver list it does look a little less like hardware. If you're wondering what the software I use as a whole to do all the automatic hard work (commands) and running the report you see there, It is my own program (states in the links provided at the top everything I use ) If your wondering what I use to simply run commands on the dump files, it's WinDBG from SDK package.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |