TSGL: IRQL_NOT_LESS_OR_EQUAL stop error

[Tilman Brandl]

Hi Don,

I don't offer an answer, just an idea: I've read about something 
similar - well, some of these famous stop errors anyway - in one of Fred 
Langa's latest newsletters. Have a look at 
http://www.langa.com/newsletters/2006/2006-09-21.htm#3  The solution 
there was to delete and then recreate the page file (but better see the 
details ...).

My guess is that i'ts one of those beautiful creations from Redmond - 
Windows in sort of a 'Sorcerer's Apprentice mode'

Tilman

-----Ursprüngliche Nachricht----- 
Von: "Don Penlington" <deepend at tpg.com.au>
An: "Tech Support Guy Mailing List" <list at tsgserver.com>
Gesendet: Sonntag, 24. September 2006 03:26
Betreff: Re: TSGL: IRQL_NOT_LESS_OR_EQUAL stop error


> Justin wrote:
>>It's a driver issue, it's odd that it happens in safe mode, normally
>>it's the other way around.
>>
>>try updating the motherboard drivers and video card driver (it's
>>normally caused by the video card).>>
>
> Thanks Justin.
>
> I agree, it's very odd indeed. Certainly doesn't seem to point to a 
> driver
> issue, as I can't think of any driver
> which might load at Safe but not Normal mode. Nor can I think of any
> conflict that could exist in those circumstances.
>
> I just installed a brand new video card yesterday but that had no 
> effect on
> the problem. Same problem existed both before and after the new video 
> card.
>
> Mobo drivers are off the CD that came with it. I'll try updating them. 
> It's
> a Gigabyte mobo I think, so should be pretty standard.
>
> As everything seems to be working OK normally, it's not too much worry 
> at
> the moment.  However, I fear this may be symptomatic of some deeper 
> problem
> lurking, and the fact that Safe Mode is inaccessible is a worry in 
> case of
> any future difficulties.
>
> Although I didn't go through all Google's 74000 answers, I couldn't 
> spot
> any instance of it happening in Safe Mode only. That combo seems to 
> rule
> out all the usual explanations.
>
> Maybe someone out there can think of a logical answer.
>
> I thought possibly of a MBR virus (is there such a thing?) but full 
> AVG
> virus check and Spybot checks seem to come up clean.
>
> Could a MBR corruption cause this effect? If so, what can I do about 
> that?
>
> I'll take a BartPE CD over and try running that. If that fails, it 
> might
> point to something, though I'm not sure what.
>
> Don Penlington