Pattern not found on injection.

Question

Pattern not found on injection.

elf-XNSR opened this issue a year ago · 16 comments

Since around September 11th multiple people have experience a "Pattern not found" error on injection, I'm not really sure what causes it, but restarting your PC usually fixes the issue entirely.

segiqt commented a year ago

same

Answer 1 · 2023-09-21T12:39:00.000Z

We could try to dump the module if the signature wasn't found. Maybe this will help in finding out what went wrong.

Answer 2 · 2023-09-21T12:39:11.000Z

i can confirm

Answer 3 · 2023-09-21T13:13:16.000Z

We could try to dump the module if the signature wasn't found. Maybe this will help in finding out what went wrong.

since we don't know how to recreate it yet this would either rely on user submission or us getting it out of luck, im not opposed to the idea though

Answer 4 · 2023-09-21T13:57:58.000Z

Another thing I've noticed is that the signature in #1058 is one of the signature I've remade.
It was previously: A1 ? ? ? ? 8B 11 68 + 0x8
and I changed it to: 68 ? ? ? ? 50 50 FF 12 + 0x1

But I don't see how this could cause an issue, especially since the signature is unique (the old one wasn't).

Answer 5 · 2023-09-21T14:02:29.000Z

Here dis shit happend yesterday to me >:)
Dere the Crash Dump :3
https://www.mediafire.com/file/q1yq0dohc1erzxw/Crash_FW_a2ab.dmp/file
https://www.mediafire.com/file/0d11c6jv78xtu8m/Crash_FW_a2d4.dmp/file

Answer 6 · 2023-09-21T14:05:28.000Z

The crash dump will only include where the issue happened, but we know it happened in CSignature::Find()

Answer 7 · 2023-09-21T14:07:36.000Z

Here dis shit happend yesterday to me >:) Dere the Crash Dump :3 https://www.mediafire.com/file/q1yq0dohc1erzxw/Crash_FW_a2ab.dmp/file https://www.mediafire.com/file/0d11c6jv78xtu8m/Crash_FW_a2d4.dmp/file

Previous:
55 8B EC 83 EC 28 56 8B 75 10 57 8B 7D 14 8B C7 99 83 E7 03 83 E2 03

New:
55 8B EC 83 EC ? 56 8B 75 ? 57 8B 7D ? 8B C7

Another weird case... Is it possible that our sig scanner has issues with wildcards? But that would not explain why it only happens sometimes.

Answer 8 · 2023-09-21T14:18:55.000Z

Here dis shit happend yesterday to me >:) Dere the Crash Dump :3 https://www.mediafire.com/file/q1yq0dohc1erzxw/Crash_FW_a2ab.dmp/file https://www.mediafire.com/file/0d11c6jv78xtu8m/Crash_FW_a2d4.dmp/file

Previous: 55 8B EC 83 EC 28 56 8B 75 10 57 8B 7D 14 8B C7 99 83 E7 03 83 E2 03

New: 55 8B EC 83 EC ? 56 8B 75 ? 57 8B 7D ? 8B C7

Another weird case... Is it possible that our sig scanner has issues with wildcards? But that would not explain why it only happens sometimes.

or why after it happens it won't stop happening on the same sig until you restart your PC.

Answer 9 · 2023-09-23T00:22:36.000Z

can confirm

Answer 10 · 2023-09-24T09:02:29.000Z

i had the same problem, restarting didnt help anything but moving steam to documents fixed it for me.

Answer 11 · 2023-10-06T19:50:26.000Z

i have the same problem, same error, heres the crash dump
Crash_FW_54c6.zip

Answer 12 · 2023-10-19T13:52:52.000Z

If this happens again, please create a full dump of the game using Process Explorer and send a link to Fedoraware(at)protonmail.com:

Answer 13 · 2023-11-11T21:50:20.000Z

Solution! If you have Bakkesmod opened quit it, quit steam, load Fedoraware again and it should fix the problem

Answer 14 · 2024-02-13T11:35:53.000Z

Happens to me too, the fix "load fedoraware again" doesn't work for me

Answer 15 · 2024-02-14T13:38:18.000Z

still having the same issue