bollocks

I recently installed Asus' fly on the wall overclocking utillity: AI Booster. After installing I had a play with it and applied one of the boost presets (110% boost). Unfortunately my system froze up, so I restarted and that's where my problems began.

Instead of starting up I'd get the system error: DRIVER_IRQL_NOT_LESS_OR_EQUAL

Tried one more restart but got the same error message once again except this time it said something about Atapi.sys - F83965ED.

Anyways, decided I'd had enough (was going to fdisk the drive at some point over christmas anyways) and wiped my HD whithin XP on my mate's computer. Booted up with WinXP SP2 disk and started to install except I only got as far as the last 'confirmation to install' screen (if that makes sense), when I recieved another BSOD containing the same information as previously stated.

Thought maybe it could be a problem with my BIOS? Then it was suggested my memory could be faulty. Either way, thought I'd have another attempt at re-installing XP, except this time I tried the setup on the HD that I'd previously been using as a slave. No luck, same error messages. Just to clarify, the BSOD appears after the XP boot disk starts up and I select the option to install Windows.

Can anyone shed any light on my situation? Apologies if none of that made any sense.

__________________
Why's Snoop Dog carry an umbrella?

Fo' Drizzle

Martel

Google for memtest, download the ISO, and burn it out to a CD. Then let it run on your system for a few hours and you'll find out for sure if your RAM is having issues. I would doubt that just a little tweaking like that could kill your RAM, but if it was kinda faulty to begin with that may have pushed it over the edge.

Random bluescreens and errors installing windows almost always point to bad RAM in my experience.

__________________
Anamnesis

bollocks

Cheers

__________________
Why's Snoop Dog carry an umbrella?

Fo' Drizzle

dogzilla

I don't know exactly how this utility works. If it updates the parameters the BIOS uses, then your memory controller might still be using the overclocking parameters. One thing I'd suggest is looking at the memory timing settings in the BIOS and make sure they are set to the default values.

feelgood

Hey bollocks, I was wondering if you had previous experience in overclocking? I'm asking because I find that inexperienced person tinkling around with overclocking usually runs into trouble. I know it from personal experience.

__________________
Looking out the window, that's an act of war. Staring at my shoes, that's an act of war. Committing an act of war? Oh you better believe that's an act of war

Dilbert1234567

hehe, tinkle...

enter bios and see if you are still overclocked. if your not, sounds like you may have damaged something. swap out comonents until you narrow it down.

__________________
Donate Blood!

"Love is not finding the perfect person, but learning to see an imperfect person perfectly." -Sam Keen

bollocks

Went into Bios and reset to default settings. I also checked my CPU clock... Still running at 2.4ghz. Tried installing XP again but still recieving the same error messages.

Been playing around with Ultimatebootdisk in the mean time. Used the Boot & Nuke ultillity to wipe my HD again and also ran Memtest for a good 3 hours... No errors. However, after I skip passed these DOS commands and onto the menu driven feature of the 'Ultimatebootdisk' I get the error:

lsass.exe System Error
An invalid parameter was passed to a service or function.

Hmmm...

How do I look at the memory timing settings? Cheers

EDIT: All sorted. Used the Boot & Nuke utility one more time, except this time used a different, more secure wipe method.

Booted up and installed XP with no errors. Everything seems to be working ok now.

__________________
Why's Snoop Dog carry an umbrella?

Fo' Drizzle

Deltona Couple

If the memory modules that you have installed are not built for overclocking, then you may have burned one of your memory chips. do you have more than one memory stick? If so, try booting and installing only ONE chip to see if it runs stable.

__________________
"It is not that I have failed, but that I have found 10,000 ways that it DOESN'T work!" --Thomas Edison

dogzilla

Happy to see you are up and running.

Anyway, FYI,

If this had been a bios problem, I would expect resetting to default settings would clear any memory overclock settings in the bios.

To look at the settings, once you get in the bios setup screens, look for a bios settings tab labeled hardware, memory, or something like that. The panel has a number of settings labeled CAS, etc (I think). These are specific to the particular type and speed of memory, so unless you have documentation for your memory that states what these numbers should be, your best bet would be just to pick a 'set defaults' option.