I had similar problems with an oem drive controller using a promise chip. If
you have something different to try. It could help

"jallaballa" <jallaballa@discussions.microsoft.com> wrote in message
news:C625B406-E35B-44A7-A1A0-4212D3AF2864@microsoft.com...[color=blue][color=green]
>> Ok sorry that didn't help. It was a flyer. Just saw a problem similar
>> to
>> yours in the XP newsgroup and that's how it was resolved. The next step
>> would be to look at the video driver.
>>
>> --
>> Rock [MVP - User/Shell]
>>
>>[/color]
>
> I updated my driver to the catalyst that came out jan 29 but that didn't
> help. I made some more screen shots after I discovered that only one of
> the
> two cpu's are used during the spikes. I know that it's not actually two
> cpu's
> but it looks that way in task manager because of the hyperthreading. Maybe
> Vista doesn't like hyperthreading?
>
> [url]http://i7.tinypic.com/35lxbo3.png[/url] problem
> [url]http://i5.tinypic.com/2remdn7.png[/url] plain
>
> This time I rebooted the computer, installed the new video driver and let
> it
> idle. Then I took the first screen shot and when it started freezing again
> I
> closed all applications and let it idle again. The red marks are cpu
> spikes
> created by me when i opened snipping tool and when i made the window
> larger.[/color]