#DRIVER IRQL NOT LESS OR EQUAL FIX VISTA PC#
#DRIVER IRQL NOT LESS OR EQUAL FIX VISTA WINDOWS#

#DRIVER IRQL NOT LESS OR EQUAL FIX VISTA WINDOWS#

After trying to log into windows XP about 5-7 times, I decided to try to boot into vista. IRQL_NOT_LESS_OR_EQUAL was the problem, but I didn't manage to get any other information. Once I did that, logged into windows again and it logged into Google Talk fine, so I thought My problem was gone, but before even a minute of being logged in, I got another BSOD, this time I managed to read the top before it reset.

After Google Talk gave me that error about the clock/date being invalid, I remembered I forgot to set the dates in the CMOS after I reset the CMOS.

I restarted the PC, logged into windows XP again, but Google Talk gave me an error about the certificate was invalid, something like that, and that the clock/date was the problem, when I go to click OK, I get a BSOD that only flashed for a fraction of a second, too fast to see what it said.

#DRIVER IRQL NOT LESS OR EQUAL FIX VISTA PC#

When the timer got down to 53 seconds, the screen went white and the PC froze. Once I reset the BIOS, I tried to boot into windows XP, which worked fine, then when I tried to log into my account I got some error about lsass.exe failed, and the computer would restart in 1 minute. It booted up fine, and I set the BIOS back how I had them, but when I tried to boot into windows I got an error about ntoskrnl.exe is corrupt or missing, and when I tried to boot into Vista (Dual Boot) and got a similar problem, but with hal.dll or something, so I spent probably an hour trying to figure out what caused it, and it turns out a simple BIOS reset fixed it. This is where it wouldn't boot up, because I set them too low, so I had to reset the CMOS with the jumper on the motherboard. In the end nTune put the timings at 5-6-5-18, so I went back into the BIOS and on accident, I set it to 3 CAS latency, with 4-4-4-12 timings. Anyways, I ran nTune's 'Fine Tuning' option, for 3 hours, but wasn't happy with the memory timings because the RAM supports 4 #CAS Latency, with 4-4-4-12 timings, and nTune decides to back everything down that it has tuned, when the computer crashes/restarts, so when it was too high FSB clocks that caused it to crash, it would lower everything else it had tuned. I have to use my dad's computer, which he uses for work, because My computer died and we don't have the money to fix it, and I wanted to overclock it, which I REALLY shouldn't have since my dad depends on using it for work. I really need help with this, I've spent all last night, and some of today (I've been sick) trying to fix his PC with no luck, and he's really behind on work now, and he depends on this computer to use for his work.

Driver irql not less or equal fix vista