DocHouse

Attempted another integration and was greeted with a 0x0A DRIVER_IRQL_NOT_LESS_OR_EQUAL blue screen...

Hi Everyone, I recently noticed some odd behavior from vLite with regards to integrating patches into my Vista Ultimate x64 build recently. After the last few rounds of patches, I decided it was time to do another round of integrations, and tracked down all of the necessary patches. When I tried to integrate the hotfixes though (roughly 20 of them), vLite took about 3 hours to get through them all! The process seems to have worked (at the time of writing, I am testing the image out in VMware), but I'm wondering if anyone has noticed this on their systems and has perhaps found a cause for the extreme slowness? My system is perfectly capable of handling this operation (specs below), and i've only noticed this in the past couple of weeks. The creation of the slipstreamed ISO went fine (took about 20 seconds) and is bootable. The extreme slowness of the hotfix integration has me puzzled though. I'm hoping this has nothing to do with the system itself, but I thought I should see if anyone had any ideas for a possible explanation? vLite version: 1.2 Final CPU: Core 2 Quad Q9550 RAM: 8GB G.Skill DDR3-1600 @ 7-7-7-18 Mobo: Asus P5K3 Deluxe OS: Vista Ultimate x64 SP1 HDDs: 1 x 500GB Seagate 7200.10 (Boot), 4 x 1TB Seagate 7200.11 (3 in RAID 0, one as a stand-alone drive) The Vista sources are on the standalone 1TB drive, the hotfixes are on the 500GB boot volume. Edit: I should note that I have re-produced this by removing the modded sources and copying back from my RTM Vista DVD. SP1 integration takes the usual time (30-40 minutes on this system), but integrating the post-SP1 hotfixes takes 2-3 hours each time. No single hotfix seems to be hanging up the program either, as I watched the progress of the integration twice. The progress did not jump at any point, the entire operation just seems slow for some reason.