See this topic for the solution.

Ms has released  KB951126

"A multiprocessor computer that is running a Microsoft Windows operating system stops responding on a black screen after you resume the computer from hibernation "

I don't think it's related to that: the Windows XP installation disk which I used has the Service Pack 3 integrated, and the hotfix for KB951126 is included.

I have tried again integrating only the following testpack:

+ DP_Chipset_wnt5_x86-32_80604.7z

but the result is unfortunately the same. The system doesn't recover properly from the standby nor from the hibernation: a black screen appears and a shutdown is required to make the system work again.

I think your Problem not releated to Chipset DriverPack ,

Ms has released  KB951126

"A multiprocessor computer that is running a Microsoft Windows operating system stops responding on a black screen after you resume the computer from hibernation "

Link  http://support.microsoft.com/kb/951126

What kind of addon cards and/or "off the motherboard" hardware is in your system?
Some hardware just does not like standby/hibernation and will not recover; the result is often a hung system.

This is the list of my hardware generated with PC Wizard, in case it can be of any help. I doubt it's an hardware problem because, as I wrote earlier, when I used the drivers downloaded from the Intel web site the standby and hibernation worked fine.

Some hardware just does not like standby/hibernation and will not recover; the result is often a hung system.

+ DP_Chipset_wnt5_x86-32_80604.7z

but the result is unfortunately the same. The system doesn't recover properly from the standby nor from the hibernation: a black screen appears and a shutdown is required to make the system work again.

+ DP_Chipset_wnt5_x86-32_806A_PUBLIC.7z
+ DP_Chipset_wnt5_x86-32_80604.7z

DriverPacks BASE picked up only the first of the two during the integration.

I downloaded the official chipset driver pack and used nLite to integrate it with a Windows XP installation disk (initially I wasn't aware of the testpacks and I wasn't aware of DriverPacks BASE either). The disk didn't work with my hardware because during installation I got the error "Setup did not find any hard disk drives".

After doing a little research I discovered the problem was due to the lacking of the "Mobile Intel 965 Express Chipset Family" drivers in the chipset driver pack, so I downloaded them from the Intel web site  (I saved them here), and integrated them into another installation disk with nLite. Then the installation process went through and was successful.

I had many problems with other devices back then, but I clearly remember the standby and hibernation were working fine.

What else can I do to help you find the problem?

(And, by GOD, Krige had to be shown the lights, but he learns this quite fast..).
Compare the results like a scientist would.
If you can use same Same hardware, and if on this hardware there were NO problems with officially released DriverPacks, and there are issues with a new testpack testbuild we want to KNOW.

Of course we want to know about issues about officially released DriverPacks, and we want to know what you did to fix the issue (which driver you used to solve the issue, a link to it..)

I have often said I like to use the NOOB approach.
When I have to test a DriverPacks testpack, I run a live test on a testplank I know I had issues with.
It goes live with an autopartition, autoformat, and 22 minutes later I know about 'holes' or "whole".

after I see 'whole", do not think I don't look further. I run the testplank through tests (but I don't always use hibernation.. I don't buy laptops for testing. I test on the hardware I have available and I kept quite a few difficult 'crapola' motherboards to test on.
((which means I am in breach of an agreement. We asked the testers they do NOT personally invest in testing materials..))

that is why we say dont ask for them. We must test them first

i will take stable over current every time...  
which is not to say we don't want to be current. We do.
just let some other poor shlub work out the bugs for us first ;P 
Then we add them... after they are tested and known good .

this is the same reason we do not include beta or leaked drivers.

let us know what you did to resolve this so we can update the packs for everyone.

Thanks for reporting the issues it makes DriverPacks better for everone.
you guys are DriverPacks heros of the day...

I have to say though that the system wasn't affected by this problem when I used the official chipset driver pack, which at the moment doesn't include the drivers mentioned in my first message of this topic, in conjunction with the ones downloaded from the Intel web site.