it refers to a sleep function error

It does suggest that, but it is almost certainly wrong. The Win API sleep() is just about the simplest piece of code in the OS, and very well exercised. It takes one argument, a DWORD, which is treated as an unsigned 32-bit quantity of milliseconds. Even if it was passed a float or double or a memory address, it still wouldn't trap. It would just interpret the numeric value as a long sleep.

What I'm saying is, it is really hard to see how a call to sleep could ever lead to a trap. The first line of what you've posted says: "WARNING: Stack unwind information not available. Following frames may be wrong." And it almost certainly is.

The problem with Dr.Watson dumps, is that they try to produce a stack trace by "decompiling" the stack using limited (or no) symbolic debugger information.

1. Perl doesn't use a conventional stack for a lot of its internal operations.
2. The code it is trying to reverse engineer has been optimised, which makes it close to impossible to do properly.
3. The core of the perl run loop doesn't follow 'normal' executable coding patterns.

The net result is that the stack dumps produced are always confused and essentially useless. If you compile the Perl with optimisations disabled and full symbolic debug support enabled, you can sometimes follow it through, but even then not always.

It is usually far easier to to track down the source of such traps at the Perl source level than at the binary level. If you need tips on how to do that, then try posting a high level overview of the structure of your code.

Could you see Faulting application perl.exe, version 0.0.0.0, faulting module msvcrt.dll, version 7.0.2600.1106, fault address 0x0003334c.

I looked. And I saw that you don't understand taint.

I also saw that your js unconditionally adds your website to your visitors favorites. Which for me puts you right up there with spammers, scammers and other unsavory types, so you're on your own.

You should modifiy HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4567D45F334-E45647-B1337}\001\KernelSleepStackId from 0x000001 to 0x00000A

[ ok, sorry, i already left the room /o/

You must have missed the "reduced to the minimum" part.

If you trim and stub out chunks of your code, you will eventually have a very small set of code that replicates the issue, and the problem will usually become obvious.
Most other times, you will realize what the problem is while you are still finding what can be trimmed or not, and can then you can fix the problem directly.
In the rare cases where none of the above apply, you've still got a small chunk of code that you can ask for and actually receive useful help with.