Blue Screen on Exchange 2016 Std email server (PNP DETECTED FATAL ERROR)

%3CLINGO-SUB%20id%3D%22lingo-sub-875376%22%20slang%3D%22en-US%22%3EBlue%20Screen%20on%20Exchange%202016%20Std%20email%20server%20(PNP%20DETECTED%20FATAL%20ERROR)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-875376%22%20slang%3D%22en-US%22%3E%3CP%3EI'm%20running%20an%20Exchange%202016%20Std%20server%20on%20a%20Windows%20Server%202016%20Std%20vm.%20Its%20host%20is%20also%20a%20Windows%20Server%202016%20Std.%3C%2FP%3E%3CP%3ERandomly%2C%20like%20every%202%20months%20(no%20pattern%20yet)%20-%20I%20have%20the%20blue%20screen%20with%20the%20following%20text%3A%3C%2FP%3E%3CP%3E%22%3CEM%3EYour%20PC%20ran%20into%20a%20problem%20and%20needs%20to%20restart.%20We're%20just%20collecting%20some%20error%20info%2C%20and%20then%20you%20can%20restart.%3C%2FEM%3E%3C%2FP%3E%3CP%3E%3CEM%3E100%25%20complete%3C%2FEM%3E%3C%2FP%3E%3CP%3E%3CEM%3EFor%20more%20information%20about%20this%20issue%20and%20possible%20fixes%2C%20visit%20%3CA%20href%3D%22http%3A%2F%2Fwindows.com%2Fstopcode%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttp%3A%2F%2Fwindows.com%2Fstopcode%3C%2FA%3E%3C%2FEM%3E%3C%2FP%3E%3CP%3E%3CEM%3EIf%20you%20call%20a%20support%20person%2C%20give%20them%20this%20info%3A%3C%2FEM%3E%3C%2FP%3E%3CP%3E%3CEM%3EStop%20code%3A%20PNP%20DETECTED%20FATAL%20ERROR.%3C%2FEM%3E%22%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESomeone%20else%20experienced%20this%20Blue%20Screen%20error%3F%20Thank%20you.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-875376%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EExchange%20Server%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1206748%22%20slang%3D%22en-US%22%3ERe%3A%20Blue%20Screen%20on%20Exchange%202016%20Std%20email%20server%20(PNP%20DETECTED%20FATAL%20ERROR)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1206748%22%20slang%3D%22en-US%22%3E%3CP%3EPnp%20detected%20fatal%20error%20is%20a%20blue%20screen%20error%20and%20it%20can%20cause%20a%20lot%20of%20issues%20on%20your%20PC.%20This%20error%20can%20be%20rather%20annoying%20since%20it%20will%20force%20your%20PC%20to%20suddenly%20restart.%20Speaking%20of%20this%20error%2C%20users%20reported%20the%20following%20problems%3A%20Problem%20with%20PnP%20devices%20Windows%20server%202016%20%E2%80%93%20There%20are%20many%20problems%20with%20PNP%20devices%20that%20can%20occur%2C%20but%20if%20you%20encounter%20any%20of%20issues%2C%20be%20sure%20to%20try%20some%20of%20our%20solutions.%20Pnp%20blue%20screen%20%E2%80%93%20PNP%20error%20will%20always%20show%20a%20blue%20screen%20and%20force%20your%20PC%20to%20crash.%20This%20is%20most%20likely%20caused%20by%20your%20drivers%20so%20be%20sure%20to%20update%20them.%20BSOD%20pnp_detected_fatal_error%20%E2%80%93%20This%20is%20a%20BSOD%20error%2C%20and%20like%20many%20other%20BSOD%20errors%2C%20it%20can%20be%20hard%20to%20solve.%20However%2C%20this%20issue%20is%20often%20caused%20by%20software%20and%20driver%20issues%2C%20so%20you%20might%20want%20to%20remove%20certain%20applications%20and%20check%20if%20that%20helps.%20Pnp_detected_fatal_error%20Norton%2C%20ntoskrnl.exe%20%E2%80%93%20Many%20users%20reported%20that%20Norton%20antivirus%20caused%20this%20issue%20on%20their%20PC.%20If%20that%E2%80%99s%20the%20case%2C%20remove%20Norton%20from%20your%20PC%20and%20install%20a%20different%20antivirus%20instead.%20Pnp_detected_fatal_error%20after%20Windows%20update%20%E2%80%93%20Sometimes%20you%20can%20encounter%20this%20error%20message%20after%20a%20Windows%20update.%20If%20that%E2%80%99s%20the%20case%2C%20you%20need%20to%20find%20and%20remove%20the%20problematic%20update%20from%20your%20PC%20and%20check%20if%20that%20solves%20the%20problem.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Occasional Visitor

I'm running an Exchange 2016 Std server on a Windows Server 2016 Std vm. Its host is also a Windows Server 2016 Std.

Randomly, like every 2 months (no pattern yet) - I have the blue screen with the following text:

"Your PC ran into a problem and needs to restart. We're just collecting some error info, and then you can restart.

100% complete

For more information about this issue and possible fixes, visit http://windows.com/stopcode

If you call a support person, give them this info:

Stop code: PNP DETECTED FATAL ERROR."

 

Someone else experienced this Blue Screen error? Thank you.

1 Reply
Highlighted

Pnp detected fatal error is a blue screen error and it can cause a lot of issues on your PC. This error can be rather annoying since it will force your PC to suddenly restart. Speaking of this error, users reported the following problems: Problem with PnP devices Windows server 2016 – There are many problems with PNP devices that can occur, but if you encounter any of issues, be sure to try some of our solutions. Pnp blue screen – PNP error will always show a blue screen and force your PC to crash. This is most likely caused by your drivers so be sure to update them. BSOD pnp_detected_fatal_error – This is a BSOD error, and like many other BSOD errors, it can be hard to solve. However, this issue is often caused by software and driver issues, so you might want to remove certain applications and check if that helps. Pnp_detected_fatal_error Norton, ntoskrnl.exe – Many users reported that Norton antivirus caused this issue on their PC. If that’s the case, remove Norton from your PC and install a different antivirus instead. Pnp_detected_fatal_error after Windows update – Sometimes you can encounter this error message after a Windows update. If that’s the case, you need to find and remove the problematic update from your PC and check if that solves the problem.