Problem after changing motherboard (Asus P4SP-MX) 2

[OOP]

Hi,

Just recently changed my old motherboard to ASUS P4SP-MX, 1.6GHz(remain the same), 256DDR RAM, win XP. But problem arise soon after i changed it.
Sometimes at any point of time, the system will encounter an error and prompts a blue screen as follows;

<<
A problem has been detected and windows has shut down to prevent damage to your computer.

IRQL_NOT_LESS_OR_EQUAL

***Stop:0x0000000A(0x..<<more address here>>..)

Beginning dump of physical memory
physical memory dump complete

Contact your computer admin if it happens again>>

I've downloaded the lastest BIOS and have it updated in my system. Please advise if someone has encountered this problem before. Any help/comment is appreciated, thanks.

 

[paparazi]

OOP
I'm guessing that you didn't clean install Windows?
Your current installation was configured for the previous motherboards chipset and so the new motherboards differant setup is creating conflicts and reporting errors.
You are actually lucky that the system even boots, often with such a hardware change the PC won't even get into Windows.
My recommendation is to backup what you can, format and reinstall Windows etc.
Martin

Start by questioning and soon you will be anwering.
So please take but remember to return and give when you can.

 

[OOP]

Thanks guys, sounds like i've to format and reinstall again. The error happens frequently (within an hour after starting system..). Will update here again if the problem persists. Thanks again. Good luck to me!!

 

[OOP]

Hello! I'm back!

A lot have happened to my computer last two days, i discovered that the error happened as early as during installation of window xp...That must means that either i have a wrong BIOS setting or connected the motherboard in a wrong way...am i correct??

There were times that during halfway thr' the installation, it halt and prompts the blue screen. But during that instant, i have a totally clean harddisk so it must means something's wrong to my motherboard.

I went into the BIOS setting and changed some IRQ settings.
A couple of strange default setting is that the BIOS actually inputs a 'No' to some of the componets such as mouse. I changed it to 'Yes' to indicate that i am using..wonder if i did it wrong.

ok, till now everything is going smoothly and i hope that i will NEVER EVER HAD TO SEE THE ERRORRR AGAIN. Any comments or advice to share?

 

[OOP]

Oh...it comes back again!!!

This time the system auto reboot and i didnt get the error type. But i manage to copy the error report details as follows;

C:\WINDOWS\Minidump\Mini052704-01.dmp
C:\DOCUME~1\Owner\LOCALS~1\Temp\WER1.tmp.dir00\sysdata.xml

...I think i'll change the hard disk and try again....(hopefully it works)

 

[OOP]

........think luck is not on my side. My spare hard disk is faulty.. But i dont think its the problem with my harddisk right, moreover its less than one year old.

 

[Freestone]

Your original STOP 0x0000000A had nothing to do with IRQs, but from

"Stop error 0x0000000A (Stop 0x0A) shows that there was an attempt in kernel mode to touch pageable memory at too high a process internal request level (IRQL). This error usually occurs when a driver uses an incorrect memory address. Other possible causes of this error are an incompatible device driver, a general hardware problem, and incompatible software.

 

[Freestone]

Take two.

Your original STOP 0x0000000A had nothing to do with IRQs, but from

http://support.microsoft.com/?kbid=314063

"Stop error 0x0000000A (Stop 0x0A) shows that there was an attempt in kernel mode to touch pageable memory at too high a process internal request level (IRQL). This error usually occurs when a driver uses an incorrect memory address. Other possible causes of this error are an incompatible device driver, a general hardware problem, and incompatible software."

Since you fail during an install, I suspect a hardware problem. My first suspect would be memory.

This link provides other pointers to troubleshooting:

http://support.microsoft.com/?kbid=314063

What stop number are you getting during an install?

 

[OOP]

The link u provided is useful and very relevant to my existing problem. After browsing thr' the troushooting guide, what i can confirm is that the new motherboard i installed (ASUS P4SP-MX) is compatible with Win Xp and its the only hardware that i changed. Will go according to the guide if the problem persists. Actually i dont mind if the error happens once in a blue moon...
Thanks a lot, freestone.

 

[Freestone]

You're welcome, OOP. Being you are a programmer, you must be detailed oriented, but be sure not to assume all possible future blue screens are caused by the same error. Note the STOP code each time as different STOPs have different troubleshooting paths...

 

[paparazi]

OOP
Nearly always memory related.
Go in the bios and set low performing default options, leave just one stick of memory in the machine
Try again
Swop out the memory.
Fixed?
Martin

Start by questioning and soon you will be answering.
So please take but remember to return and give when you can.

 

[OOP]

First of all, would like to apologize for the late update. I was testing out my system for a couple of days before updating any info here.

Paparazi is right, my DDRam is fautly. I never suspect it when i was troubleshooting the system since i bought it together with the motherboard assuming that it always worked. I had the culprit exchanged a few days ago and everything is working fine now. Thanks for everything for the last few weeks. Case closed!