BSOD NVSTOR64.sys irql not less ot equal to zero

Please help me with this Vista X64 error message,

driver_irql_not_less_or_equal

nvstor64.sys - address fffff9800053cb0a base at fffff98000537000, datestamp
458d544e

collecting data for crash dump ...
initializing disk for crash dump ...

"Tokraspy" <Tokraspy@discussions.microsoft.com> wrote in message
news:D5A90702-197A-4F2F-8A4A-DA9FDDE564AA@microsoft.com...
> Please help me with this Vista X64 error message,
>
> driver_irql_not_less_or_equal
>
> nvstor64.sys - address fffff9800053cb0a base at fffff98000537000,
> datestamp
> 458d544e
>
> collecting data for crash dump ...
> initializing disk for crash dump ...


Your nVidia drivers are causing the crash. Try upgrading to the latest ones
if possible.

ss.

tried that and the error becomes, bsod:-

a clock interrupt was not received on a secondary processor within the
allocated time interval

just not understanding whats goin on!


"Synapse Syndrome" wrote:

> "Tokraspy" <Tokraspy@discussions.microsoft.com> wrote in message
> news:D5A90702-197A-4F2F-8A4A-DA9FDDE564AA@microsoft.com...
> > Please help me with this Vista X64 error message,
> >
> > driver_irql_not_less_or_equal
> >
> > nvstor64.sys - address fffff9800053cb0a base at fffff98000537000,
> > datestamp
> > 458d544e
> >
> > collecting data for crash dump ...
> > initializing disk for crash dump ...
>
>
> Your nVidia drivers are causing the crash. Try upgrading to the latest ones
> if possible.
>
> ss.
>
>
>

"Tokraspy" <Tokraspy@discussions.microsoft.com> wrote in message
news:C0B7EC18-2E3C-41DD-AA7A-A884F6954433@microsoft.com...
> tried that and the error becomes, bsod:-
>
> a clock interrupt was not received on a secondary processor within the
> allocated time interval
>
> just not understanding whats goin on!
>
>
> "Synapse Syndrome" wrote:
>
>> "Tokraspy" <Tokraspy@discussions.microsoft.com> wrote in message
>> news:D5A90702-197A-4F2F-8A4A-DA9FDDE564AA@microsoft.com...
>> > Please help me with this Vista X64 error message,
>> >
>> > driver_irql_not_less_or_equal
>> >
>> > nvstor64.sys - address fffff9800053cb0a base at fffff98000537000,
>> > datestamp
>> > 458d544e
>> >
>> > collecting data for crash dump ...
>> > initializing disk for crash dump ...
>>
>>
>> Your nVidia drivers are causing the crash. Try upgrading to the latest
>> ones
>> if possible.
>>
>> ss.
>>
>>
>>
You have to start with what you do understand, the error message points to
an issue with your nVidia drivers, implication being, all else stems from
that. Fix your drivers and see if the error disappears.

Preliminarily, it seems the GPU did not properly send or sent corrupted
information to the CPU, or information that could not be read or simply was
not received by one of the cores on what appears to be a system with a dual
core processor. Nonetheless, the fault appears to be an issue with the
graphics card, you need to check for the latest Vista Compatible drivers for
your card.



--
Michael Solomon
Backup is a PC user's best friend
DTS-L.Org: http://www.dts-l.org/

[isepiq]

Re: A clock interrupt was not received on a secondary processor within

This is a defective core on a multi-core CPU message. Several people on other forums have fixed this by getting their CPU replaced. It will usually happen randomly every time your computer happens to hit on, or try to use that one defective core. At other times, while using or stressing only core 0, it will probably run just fine. Sometimes you can turn off the defective core in your BIOS, if you run a program that will tell you which core it is. You have Core 0 & 1 in a Dual Core CPU, & Core 0, 1, 2, & 3 in a 4 Core System. If you give them your credit card number (AMD) they may be willing to send you a new CPU first, then you send the defective one back. If AMD does not get the defective one back, or determines that the one you sent is not defective, they may charge your credit card. Google CPU-Z or other programs to stress test your CPU first.

IMHO
isepiq