I downloaded Windows 10 when it was released and have had no problems with it ... until I updated my Microsoft Office to 2016. Ever since then, if I have Office open I get the BSoD, with it saying either Unexpected_Store_Exception, or Critical_Process_Died. I have no other virus software, so it's not the incompatibility with Defender. I have run all of my maintenance software, rebooted my computer, etc. I'm at a loss for what else to do.
BSoD after downloading Microsoft Office 2016
- Thread starter kjung
- Start date
- Joined
- Nov 19, 2013
- Messages
- 13,411
- Reaction score
- 2,319
I'll have a quick look if you want to copy the contents of your C:\Windows\minidump folder into a new folder on your desktop, zip it up and attach it to your next post.
If I see anything scary I'll let you know.
If I see anything scary I'll let you know.
Hi, i'm new and sorry for my english. I can't find a solution for a lot of differently BSOD (PAGE FAULT.... MEMORY MANAGEMENT, SYSTEM THREAD... SYSTEM SERVICE... CORRUPTED PAGE...). I attach zip zip minidump file to the message, can you help me to solve this problem, Thanks.
- Joined
- Nov 19, 2013
- Messages
- 13,411
- Reaction score
- 2,319
First you have several old drivers on your system that could use some attention... Update or Upgrade or uninstall if neither are possible.
It may be a driver issue so you should probably do your best to determine if there are resources available to update these starting with GizmoDrv.SYS and older first, virtual drive software can sometimes cause havoc. Use Google to sort through them to see if you can determine their respective software affiliations.
You mention in your post "a lot of" but your attachment only included one dump file.
Test your system memory with MemTest86+
http://www.memtest.org/
Burn the ISO to a CD and boot your system from that and test the memory with six passes, unless it starts throwing errors early on in the process. In which case you will need to test individual memory modules in individual slots to determine which one is causing the issue.
Test your hard drive with the native Check Disk utility.
Right click the Start Button and choose Command Prompt (Admin) and in the command prompt window type
chkdsk C: /R
hit enter
answer Y when prompted
hit enter
type
exit
hit enter
reboot the system and let it run, do not interrupt it. When it has finished and automatically rebooted your system examine the report in Event Viewer paying particular attention to bytes in bad sectors near the bottom of the report.
Code:
SSPORT.sys 8/11/2005
ASMMAP64.sys 7/2/2009
npf.sys 6/25/2010
AsUpIO.sys 8/2/2010
GizmoDrv.SYS 4/29/2011
point64.sys 5/27/2012
AsIO.sys 8/22/2012
HECIx64.sys 12/17/2012
btath_bus.sys 1/21/2013
epcwmiacpi64.sys 7/2/2013
semav6msr64.sys 1/24/2014
LHidEqd.Sys 3/18/2014
LEqdUsb.Sys 3/18/2014
LHidFilt.Sys 3/18/2014
LMouFilt.Sys 3/18/2014
netr28x.sys 6/13/2014
SamsungRapidDiskFltr.sys 9/16/2014
SamsungRapidFSFltr.sys 9/16/2014
eudskacs.sys 12/14/2014
eubakup.sys 12/14/2014
EUBKMON.sys 12/14/2014
EuFdDisk.sys 12/14/2014You mention in your post "a lot of" but your attachment only included one dump file.
Which I don't believe holds any particular significance
Which I suspect does.
Test your system memory with MemTest86+
http://www.memtest.org/
Burn the ISO to a CD and boot your system from that and test the memory with six passes, unless it starts throwing errors early on in the process. In which case you will need to test individual memory modules in individual slots to determine which one is causing the issue.
Test your hard drive with the native Check Disk utility.
Right click the Start Button and choose Command Prompt (Admin) and in the command prompt window type
chkdsk C: /R
hit enter
answer Y when prompted
hit enter
type
exit
hit enter
reboot the system and let it run, do not interrupt it. When it has finished and automatically rebooted your system examine the report in Event Viewer paying particular attention to bytes in bad sectors near the bottom of the report.
Last edited:
Thank you, i have to update the drivers you find. Yes, files was "a lot" but i clean something, just remain 4. But in the 99% of the files was mentioned "ntkrnlmp.exe" like "guilty". I'm finding that problem seems happen when i'm working with Word 2016 with i file open from OneDrive folder.
Thanks a lot.
Thanks a lot.
The error condition is to be found in the use of virtual memory. I have a Samsung SSD evo. Moving VM to an HDD seems to be no problems.
