Windows 10: PNP_DETECTED_FATAL_ERROR on shutdown or restart? partmgr.sys (partmgr.

Hey all! I'm hoping someone could shed some light on this particular error that has me stumped. I feel that perhaps it's a driver update or a windows update, but I cannot pinpoint the exact cause of this error. It's frustrating to say the least. I do have a computing background and normally I can fix majority of the issues. However, I've spend countless hours researching this problem and it seems to be extremely difficult to pinpoint.

I would say this started about a week ago. Perhaps after the 2004 update or 20H2 update? I don't exactly know. The issue seems to happen regardless of what USB devices I have installed. I've tried the following.

Windows 10, 64-bit

1. Use a different USB mouse.
2. Uninstall and Reinstall all mouse drivers and software.
3. Use a different keyboard.
4. Uninstall and Reinstall all keyboard drivers and software.
5. Use only the keyboard without the mouse.
6. Use only the mouse without the keyboard.
7. Update all USB Chipset drivers.

Nothing above worked. I still get the PNP_DETECTED_FATAL_ERROR on shutdown or restart. I only have a mouse and keyboard on my PC via the USB ports. I did notice some oddities which are the following.

• If I disconnect the mouse and reattach it, I won't get a BSOD when I shutdown or restart that time. However, any future shutdown or restarts will cause a BSOD. The same applies to the keyboard. This also applies to several different keyboards and mice. It's not one specific one.

The really odd part is I recall an instance when I was playing a game and in the middle of the game the mouse disconnected and then reconnected. I thought nothing of it and figured it was just windows updating in the background or something. I can't say the issue has occurred since then, but it seems quite a coincidence.



Any help you guys could give would be great!!!.



---------------------------------------------------------------------------------------------------------


==================================================
Dump File : 010821-13765-01.dmp
Crash Time : 1/8/2021 4:49:13 PM
Bug Check String : PNP_DETECTED_FATAL_ERROR
Bug Check Code : 0x000000ca
Parameter 1 : 00000000`00000002
Parameter 2 : ffffcd8d`71588530
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : partmgr.sys
Caused By Address : partmgr.sys+22d1e
File Description : Partition driver
Product Name : Microsoft Windows Operating System
Company : Microsoft Corporation
File Version : 10.0.19041.1 (WinBuild.160101.0800)
Processor : x64
Crash Address : ntoskrnl.exe+3f5780
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\WINDOWS\Minidump\010821-13765-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 19041
Dump File Size : 1,267,852
Dump File Time : 1/8/2021 7:46:25 PM
==================================================

==================================================
Dump File : 010821-14046-01.dmp
Crash Time : 1/8/2021 11:47:27 PM
Bug Check String : PNP_DETECTED_FATAL_ERROR
Bug Check Code : 0x000000ca
Parameter 1 : 00000000`00000002
Parameter 2 : ffffa78d`3e7df0a0
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : partmgr.sys
Caused By Address : partmgr.sys+22d1e
File Description : Partition driver
Product Name : Microsoft Windows Operating System
Company : Microsoft Corporation
File Version : 10.0.19041.1 (WinBuild.160101.0800)
Processor : x64
Crash Address : ntoskrnl.exe+3f5780
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\WINDOWS\Minidump\010821-14046-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 19041
Dump File Size : 1,088,724
Dump File Time : 1/8/2021 11:51:33 PM
==================================================

--------------------------------------------------------------------------------------

Speccy Snapshot

http://speccy.piriform.com/results/1...Ip4mJFNbgq2Iyy

• I did the MemTest86 and did about 3 passes and nothing came up. No errors whatsoever on the memory.

:)

 

FSX + Acceleration error code 1-80004005

Hi... thanks for the great help.

on my PC only partmgr was listed under Upperfilters, but it was small caps. I changed it to PartMgr and worked like a charm.

Cheeers!

 

Hard drive/ OS issue

a guy suggested :

• shutdown
• unhooked HDD
• restarted
• yay !!
• reconnected HDD
• restarted
• yay !!

also , try method 3
How do I unlock the drive where Windows 10 is installed?

 

Windows 10 Pro 64bit 1607 Update Deactivated FSX

Resolved...well it took several steps...had to manually search and delete any Microsoft Flight Simulator entry in the registry related specifically to fsx.exe. This allowed the Remove to work from the DVD. Then reinstalled FSX and activated. Launched and it worked. Then I installed the Acceleration pack. Launched and got the activation error again. Went into the registry and looked for the UpperFilters setting in the MS FSX registry key HKEY_LOCAL_MACHINE\SYSTEM\CURRENTCONTROLSET\CONTROL\CLASS
\{4D36E967-E325-11CE-BFC1-08002BE10318} and modified it..deleted the partmgr and typed PartMgr and restarted FSX with Accel Pack, it immediately asked for activation and entered the product key and it activated successfully. This was a 24 hour pain.....but back to normal after the 1607 update.