How do I tweak the BSoD messages?

[PeregrineX]

(I'm not sure if this is in the correct section...)

Hey, I was wondering if it was possible to edit the ntoskrnl.exe (or ntkrnlpa.exe) to give me custom BSoD messages, like, for example, instead of "A problem has been detected..." I would change it to an insult of some sort.

Here's what I have done so far (in this order):

--Make a copy of ntkrnlpa.exe and edit the first line of the BSoD in a hex editor
--Sign it using coderforlife's signer.exe (search it)
--Boot into windows installation disc and copy the modified ntkrnlpa into System32

But whenever I boot back into Windows, it automatically boots into Startup Repair, and I have to do a System Restore.

Any thoughts?

 

[Layback Bear]

Why would you want to do such a thing?

How do I tweak the BSoD messages?

The proper BSOD messages are very important if you ever get a BSOD.

I serious doubt that the BSOD Team can work with your created messages. They need to be kept unaltered.

 

[LMiller7]

I can't help with this and wouldn't even if I could.

This article by Raymond Chen, a developer with Microsoft since before Windows 95, warns about this sort of thing:
https://blogs.msdn.microsoft.com/oldnewthing/20030805-00/?p=42993/

The article refers to changing the boot logo in XP but that isn't important. The point isn't the desired outcome but the method used to accomplish it, namely modifying ntoskrnl.exe.

 

[axe0]

Modifying the kernel files lets you face some serious (boot) problems which won't be fixable without a reinstallation or a proper backup as you already have noticed.

It is best to leave the system files intact without any edits from your side.

Also to note, modifying the ntoskrnl.exe or ntkrnlpa.exe files won't change the stop codes.