Product: Bitdefender Total Security 2017 (fully updated)
Operating system: Windows 10 (fully updated)
Shortly after upgrading from Bitdefender Total Security 2016 to 2017 Microsoft Word 2013 crashes whenever I try to save documents. I reinstalled MS Office from CD and also repaired it using the full online repair procedure. The problem persists.
Is this fault coincidental with the Bitdefender uograde or have others experienced this problem? I would appreciate any advice.
Here is the report from Whocrashed:
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Sun 21/05/2017 07:42:53 your computer crashed
crash dump file: C:\WINDOWS\Minidump\052117-24578-01.dmp
This was probably caused by the following module: classpnp.sys (0xFFFFF8031F404B97)
Bugcheck code: 0xD1 (0x2C, 0x2, 0x0, 0xFFFFF8031F404B97)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\classpnp.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: SCSI Class System Dll
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Sun 21/05/2017 07:42:53 your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: classpnp.sys (CLASSPNP!ClassDeviceControl+0x2137)
Bugcheck code: 0xD1 (0x2C, 0x2, 0x0, 0xFFFFF8031F404B97)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\classpnp.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: SCSI Class System Dll
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.